With FC3/Test 1, anaconda has forgotten how to deal with my USB CDROM.
I think it has something to do with the new kernel's ability to
identify the chipset of the USB/IDE bridge and it thinks it's a
harddrive. What I see on console 4 is:
<6>Initializing USB Mass Storage driver...
<6>scsi3 : SCSI emulation for SB Mass Storage devices
<5> Vendor: Revoltec Model: USB/IDE Bridge ( Rev: 0103
<5> Type: Direct-Access ANSI SCSI revision: 02
<5>SCSI device sdc: 322700 2048-byte hdwr sectors (661 MB)
<5>sdc: Write Protect is off
<7>sdc: Mode Sense: 00 76 11 00
<3>sdc: assuming drive cache: write through
<6> sdc: unknown partition table
<5>Attached scsi removable disk sdc at scsi3, channel 0, id 0, lun 0
<7>USB Mass Storage device found at 4
<6>usbcore: registered new driver usb-storage
<6>USB Mass Storage support registered.
Yeah, that's not a cd-rom drive as far as most of the world would be
Some additional info. It appears that there was a patch applied on
the 29th of last month
that may be the culprit. The USB/IDE bridge chip that "owns" the IDs
specified in the patch is the ALI M5621. On the linux USB device
overview (http://www.qbik.ch/usb/devices/showdev.php?id=2645) that
particular bridge is listed as working prior to the patch.
I was able to get FC3 installed by first connecting the USB cable so
that the BIOS could boot off it and then as soon as the kernel took
over, unplugging the USB cable and plugging in a firewire cable. Not
something that Joe Sixpack will probably want to do. =)
An update has been released for Fedora Core 3 (kernel-2.6.12-1.1372_FC3) which
may contain a fix for your problem. Please update to this new kernel, and
report whether or not it fixes your problem.
If you have updated to Fedora Core 4 since this bug was opened, and the problem
still occurs with the latest updates for that release, please change the version
field of this bug to 'fc4'.
FC4 works properly.