Package: cdrom-detect Version: 0.38 (This is on a IBM bladecenter which has a USB cdrom drive.)
James Bromberger wrote: > I grabbed the 2.4.22-386 kernel and added a few of the modules for > testing: > ehci-usb seems to fail to laod (with no explanation in dmesg). > ohci-usb works > sr_mod works > tg3 works (ethernet) > > And I can access the CD ROM. With it unmounted, the installer still > fails to detect the cdrom drive; there is no /dev/cdrom symlink made > when the sr_mod detects the /dev/scsi1/host0/bus0/target0/lun0/cd. Lets file a bug to that effect. It sounds to me like cdrom-detect should fall back to prompting with a list of all disks (or at least all scsi disks) in the system if it cannot find a /dev/cdroms/ device. BTW, sr_mod will be available on the CD's in a couple of days. > The tg3 network interface I have is detected, but running udhcpc fails. > The installer meanwhile has bombed out and also complains about a > missing floppy still (these IBM blade machines have a USB floppy, not > one that the floppy controller (floppy.o) seems to recognise). Setting > the address manually seems to be OK. I'll bet you have a file in /dev for your USB floppy drive, if you have usb-storage loaded in addition to the modules listed above. Problem is the installer doesn't know it's a floppy drive as opposed to a scsi drive. It would know if you booted off the thing.. If there is a device entry for your USB floppy drive, I can make a similar change to have it prompt with a list of scsi devices if it cannot find an obvious floppy drive. -- see shy jo
signature.asc
Description: Digital signature
