From Bugzilla Helper:
User-Agent: Mozilla/5.0 (Windows; U; Windows NT 5.1; en-US; rv:1.6)
Description of problem:
Trying to install FC2 T2 from CDs. Booting from CD1 with "linux xfs".
Starts loading modules like firewire, SCSI, etc... then get stuck on
"loading usb-storage". In ALT-F4 I can see it's trying to initialize
I have a firewire enclosure and a USB2.0 card reader connected.
Version-Release number of selected component (if applicable):
Steps to Reproduce:
1. USB2.0 card reader connected
2. Firewire enclosure (with 2 HDs in it) connected and switched on
3. Boot from CD1
4. Enter "linux xfs" at prompt
Actual Results: You get "loading usb-storage" forever on your screen
because it fails to initialize the usb-storage
Expected Results: Installation should move on to the next step
Note: if I disconnect the USB2.0 card reader the installation process
It was fine with FC2 T1...
does that work without passing "xfs" ?
No. Just hitting enter will give the same error. It's not related to xfs.
Same problem with FC2 Test3...
I have a slightly different problem: when I boot with my card reader
(empty) and hard drive (both usb 2.0) attached, the installer stops on
the blue screen. vt3 shows "removing usb-storage" but the rmmod never
succeeds and the installer never proceeds. When I unplug both
devices, the installer proceeds as normal. Worked with both FC2 test1
FC2 have that same problem (x86_86) My system is a Shuttle SN85G4
Athlon64 with build-in usb card reader/writter) "Loading usb-storage
Could not test it on FC2T3 because of the missing sata_sil driver.
Any workaround except remove the connections ?
This needs SysRq to diagnose, but on boot kernel it's no use
(no KALLSYMS). I don't have good ideas. A bad idea might be
to create a test kernel with usb-storage debugging compiled in,
then adding it into the iso. I just did that excercise on weekend,
it's pretty painful.
If anyone can make it hang while running an installed system,
it would be helpful. Installer environment is too limited.
Try to see if running kudzu makes this to happen while card
reader is empty (and when there's a card in it - it's a test
for START_STOP support).
Is this still a problem with current kernels ?
I don't get this pbm anymore with latest FC3T3. Although trying on a
different box than when I reported the pbm I still have a firewire
card and a USB card reader so the situation is pretty similar.
I'm using an Asus P4S800D-E Deluxe + internal USB card reader 7 in 1.
Frederic, this has to be closed. If bugs with common enough description
stay around other people cling to them instead of filing... Witness
Chad and Lars. If they still have problems, they need to file.