Bug 155851 - anaconda: oreder of installing modules
anaconda: oreder of installing modules
Status: CLOSED NOTABUG
Product: Fedora
Classification: Fedora
Component: anaconda (Show other bugs)
4
x86_64 Linux
medium Severity high
: ---
: ---
Assigned To: Anaconda Maintenance Team
Mike McLean
:
Depends On:
Blocks:
  Show dependency treegraph
 
Reported: 2005-04-24 13:58 EDT by W Agtail
Modified: 2007-11-30 17:11 EST (History)
0 users

See Also:
Fixed In Version:
Doc Type: Bug Fix
Doc Text:
Story Points: ---
Clone Of:
Environment:
Last Closed: 2005-04-24 14:57:10 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 W Agtail 2005-04-24 13:58:11 EDT
Description of problem:
usb_storage module loads before sata_sil module
would it be possible to change the order of installed modules?
I have two SATA internal drives and ks.cfg file on a USB/compactflash card.


Version-Release number of selected component (if applicable):
x86_64 FC4 test 2 ISO cd1
NB: the md5sum of this media appears to be incorrect - have tried 3 times from 3
different URLs.


How reproducible:
Every time

Steps to Reproduce:
1. Set BIOS to boot from CD
2. Insert CD (x86_64 ISO 1)
3. Insert CompactFlash Card with ks.cfg
4. linux ks=hd:sdc1/ks/ks.cfg
  
Actual results:
Unable to find ks.cfg from /dev/sdc1 (compact flash card)
CompactFlash Drive (usb_storage) becomes /dev/sda1
SATA disks (sata_sil) become sdc and sdd
No sign of sdb - ALT-F2, bash shell, 'fdisk -l'

Expected results:
SATA disks (sata_sil) become sda and sdb - as with FC3 (but couldn't get
LVM/RAID to work in ks.cfg).
CompactFlash Drive (usb_storage) become /dev/sdc - as with FC3

Additional info:
AMD Athlon 64 CPU
2 x internal SATA1 drives
1 x CDROM
1 x Floppy (IDE) / Media Card Reader (USB)
Comment 1 Jeremy Katz 2005-04-24 14:57:10 EDT
We have to load usb_storage early for cases where people don't probe or need a
driver disk.  This is why we then later do unloading to shuffle the module around.

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