Description of problem: The kernel doesn't recognize any CD-ROM or DVD-ROM devices connected to the PATA port of my motherboard's JMicron 20360/20363. Version-Release number of selected component (if applicable): 2.6.17-1.2174_FC5smp How reproducible: Boot up to date FC5 on a motherboard with a JMicron controller (e.g. ASUS P5B Deluxe Wi-Fi) and a PATA CD or DVD connected to the PATA port. Note that the kernel will not see it. lspci shows this for the controller: 03:00.0 IDE interface: JMicron Technologies, Inc. JMicron 20360/20363 AHCI Controller (rev 02) Steps to Reproduce: 1. Boot kernel on appropriate motherboard 2. Notice that there is no /dev/cdrom and dmesg doesn't show it detecting any optical drives 3. Actual results: Optical drive is not recognized and no /dev entry is created for it Expected results: Optical drive *is* recognized and a /dev entry is created Additional info: I saw a note about this on LKML from Alan Cox stating that a fix was submitted after 2.6.18rc4 - could this fix be backported to FC5 please?
Patch included in 2.6.18-rc4-mm1. Possibly in RC5. http://www.uwsg.iu.edu/hypermail/linux/kernel/0608.2/0664.html Possible fixes: http://www.uwsg.iu.edu/hypermail/linux/kernel/0607.1/1730.html
Thanks, the all-generic-ide option got things to work properly.
A new kernel update has been released (Version: 2.6.18-1.2200.fc5) based upon a new upstream kernel release. Please retest against this new kernel, as a large number of patches go into each upstream release, possibly including changes that may address this problem. This bug has been placed in NEEDINFO state. Due to the large volume of inactive bugs in bugzilla, if this bug is still in this state in two weeks time, it will be closed. Should this bug still be relevant after this period, the reporter can reopen the bug at any time. Any other users on the Cc: list of this bug can request that the bug be reopened by adding a comment to the bug. In the last few updates, some users upgrading from FC4->FC5 have reported that installing a kernel update has left their systems unbootable. If you have been affected by this problem please check you only have one version of device-mapper & lvm2 installed. See bug 207474 for further details. If this bug is a problem preventing you from installing the release this version is filed against, please see bug 169613. If this bug has been fixed, but you are now experiencing a different problem, please file a separate bug for the new problem. Thank you.
2.6.18-1.2200.fc5 fixes this issue without requiring all-generic-ide.