Bug 454200 - IDE HD and DVD drives are not detected
IDE HD and DVD drives are not detected
Status: CLOSED WORKSFORME
Product: Fedora
Classification: Fedora
Component: kernel (Show other bugs)
9
x86_64 Linux
low Severity low
: ---
: ---
Assigned To: Kernel Maintainer List
Fedora Extras Quality Assurance
http://forums.fedoraforum.org/showthr...
:
Depends On:
Blocks:
  Show dependency treegraph
 
Reported: 2008-07-06 10:42 EDT by Mark Slemko
Modified: 2008-07-27 00:13 EDT (History)
0 users

See Also:
Fixed In Version:
Doc Type: Bug Fix
Doc Text:
Story Points: ---
Clone Of:
Environment:
Last Closed: 2008-07-27 00:13:11 EDT
Type: ---
Regression: ---
Mount Type: ---
Documentation: ---
CRM:
Verified Versions:
Category: ---
oVirt Team: ---
RHEL 7.3 requirements from Atomic Host:
Cloudforms Team: ---


Attachments (Terms of Use)

  None (edit)
Description Mark Slemko 2008-07-06 10:42:50 EDT
Description of problem:
After install, and after updating the system, the IDE HD and DVD drives are not
detected on my system:
    * Asus P5K-SE (with the latest bios)
    * Single SATA drive (contains F9 - bootable)
    * Single EIDE cable with both the DVD burner and spare 80G HD

Version-Release number of selected component (if applicable):
the kernel is 2.6.25.9-76.fc9.x86_64

How reproducible:
For me - always.

Steps to Reproduce:
1. try to load a DVD with any content after boot
  
Actual results:
DVD not visible in system

Expected results:
* Should be able to mount DVD
* Should see the secondary HD too

Additional info:
After some trial and error trying to track down the problem (linked to in the
URL) JEO and I narrowed down that the initrd is not loading the pata_marvell
module appropriately. After specifying it as a preload using mkinitrd, the
system works as expected. 

This adjustment was not required in Fedora 8, for example, so something has
changed related to this. Additionally, the live F9 CD works and detects the
drives properly.
Comment 1 Mark Slemko 2008-07-27 00:13:11 EDT
It appears that the kernel release for F9 today - 2.6.25.11-97.fc9.x86_64 -
fixed this issue for me.

Note You need to log in before you can comment on or make changes to this bug.