Bug 227505

Summary:	PATA not automatically recognised with ASUS P5B / JMICRON controller
Product:	[openSUSE] openSUSE 10.2	Reporter:	Olaf Amm <Olaf.Amm>
Component:	Installation	Assignee:	Steffen Winterfeldt <snwint>
Status:	RESOLVED DUPLICATE	QA Contact:	Jiri Srain <jsrain>
Severity:	Normal
Priority:	P5 - None	CC:	Olaf.Amm
Version:	Final
Target Milestone:	---
Hardware:	32bit
OS:	Other
Whiteboard:
Found By:	Customer	Services Priority:
Business Priority:		Blocker:	---
Marketing QA Status:	---	IT Deployment:	---
Attachments:	/var/log/messages YaST logs hwinfo --disk

Description Olaf Amm 2006-12-11 01:10:39 UTC

I have an ASUS P5B with JMicron controller. When installing OpenSuSE 10.2, it tries however to load AHCI drivers for PATA, and consequently, neither the CD drive with the installation source nor any PATA hard drives are found.

If I load *manually* pata_jmicron, it works. However, at least for beginners this is definetly a showstopper. Should load pata_jmicron automatically during installation if such a controller is present.

Comment 1 Matej Horvath 2006-12-11 22:30:35 UTC

Please attach your yast log files, your /var/log/messages and output of the 'hwinfo --disk'. Thank you.

Comment 2 Olaf Amm 2006-12-13 19:54:41 UTC

Created attachment 109623 [details]
/var/log/messages

Comment 3 Olaf Amm 2006-12-13 19:55:46 UTC

Created attachment 109624 [details]
YaST logs

Comment 4 Olaf Amm 2006-12-13 19:56:41 UTC

Created attachment 109625 [details]
hwinfo --disk

Comment 5 Olaf Amm 2006-12-13 19:59:12 UTC

The attachments are provided as requested. Note that all files come from the state *after* I fixed the bug manually! (Now permanently load pata_jmicron, edited via Yast->hardware->harddisk controller.)

Comment 6 Olaf Amm 2006-12-14 09:58:14 UTC

P.S.: I don't understand why you set the status of this bug and of bug 227506 to "normal". For users that do not have any technical Linux knowledge, do not know how to manually edit the respective configuration files, and do not even know about the existence and location of these configuration files, both bugs are absolute showstoppers. I think that if Linux wants to become more user-friendly for "normal" users, one should take this seriously.

Comment 7 Matej Horvath 2006-12-14 12:43:03 UTC

I understand you, that for the beginners it's a blocker. But I have to handle the bugs according to the bugzilla rules: https://bugzilla.novell.com/page.cgi?id=fields.html#bug_severity%3Ebugzilla%3C/a%3E%3Cbr%3EYou%20see%20some%20examples%20are%20duplicate%20...%20If%20in%20doubt%20don't%20change%20theseverity,%20let%20the%20maintainer%20do%20it.%20You%20will%20find%20out%20that%20somereporters%20alwaysset%20bugs%20to

Blocker is just for very serious bugs, for which doesn't exist any workaround, critical is for bugs, for which a workaround exists, but they cause loss of data etc.. Loading a module as a workaround is a typical 'normal' severity, because the workaround is simple and the module itself works perfectly.

Comment 8 Thomas Fehr 2006-12-14 13:30:22 UTC

Hardware detection and driver loading is not done by yast2-storage
but hwinfo. Reassigning to Steffem.

Comment 9 Steffen Winterfeldt 2007-01-22 15:23:20 UTC


*** This bug has been marked as a duplicate of bug 216165 ***