** Description changed: Binary package hint: udev Hi, I have an IBM x3800 machine with the root disk connected to the on-board - aic94xx SAS controller. Sometimes, when I boot Gutsy or Hardy, I see - this from the kernel: + aic94xx SAS controller. Sometimes, when I boot Gutsy (kernel + 2.6.22-14-server/udev 113-0ubuntu16) or Hardy (kernel + 2.6.24-4-server/udev 117-3), I see this from the kernel: Loading, please wait... [ 163.773690] input: AT Translated Set 2 keyboard as /class/input/input1 Begin: Loading essential drivers... ... [ 163.963754] SCSI subsystem initialized [ 163.972561] aic94xx: Adaptec aic94xx SAS/SATA driver version 1.0.3 loaded [ 163.979628] ACPI: PCI Interrupt 0000:01:02.0[A] -> GSI 25 (level, low) -> IRQ 25 [ 163.987333] aic94xx: found Adaptec AIC-9410W SAS/SATA Host Adapter, device 0000:01:02.0 [ 163.995487] scsi0 : aic94xx [ 224.018245] aic94xx: Failed to load sequencer firmware file aic94xx-seq.fw, error -2 [ 224.026145] aic94xx: couldn't init seqs for 0000:01:02.0 [ 224.031565] aic94xx: couldn't init the chip [ 224.037066] ACPI: PCI interrupt for device 0000:01:02.0 disabled [ 224.043196] aic94xx: probe of 0000:01:02.0 failed with error -2 [ 224.087822] Capability LSM initialized Done. Begin: Running /scripts/init-premount ... Done. ...after a minute or two I get dumped into an (initramfs) prompt. If I rmmod aic94xx and modprobe aic94xx, the driver and firmware load correctly. Further digging reveals that udev doesn't start until init- premount, which means that there's nothing listening when the kernel asks for the aic94xx firmware, which explains why the first attempt to load aic94xx fails due to firmware load problems but the subsequent attempt succeeds. Solution: mv /usr/share/initramfs-tools/scripts/init-premount/udev to /usr/share/initramfs-tools/scripts/init-top/udev and regenerate the initramfs. I speculate that the qlaXXXX drivers might have the same issue, though I don't have any hardware to test that theory.
** Tags added: aic94xx firmware udev -- udev needs to load before "Loading essential drivers" so firmware_helper will work https://bugs.launchpad.net/bugs/183648 You received this bug notification because you are a member of Ubuntu Bugs, which is the bug contact for Ubuntu. -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
