Bug#432042: firmware-qlogic: firmware not loading
Package: firmware-qlogic
Version: 0.4
Severity: important
I noticed that after installing firmware-qlogic my system was still failing
to load the firmware on boot,
qla2xxx 0000:10:00.0: Found an ISP2432, irq 169, iobase 0xffffc20000016000
qla2xxx 0000:10:00.0: Configuring PCI space...
PCI: Setting latency timer of device 0000:10:00.0 to 64
qla2xxx 0000:10:00.0: Configure NVRAM parameters...
qla2xxx 0000:10:00.0: Verifying loaded RISC code...
qla2xxx 0000:10:00.0: Firmware image unavailable.Jul 6 08:05:06 hedwig
kernel: qla2xxx 0000:10:00.0: Firmware images can be retrieved from:
ftp://ftp.qlogic.com/outgoing/linux/firmware/.
qla2xxx 0000:10:00.0: Attempting to load (potentially outdated) firmware
from flash.
qla2xxx 0000:10:00.0: Allocated (64 KB) for EFT...
qla2xxx 0000:10:00.0: Allocated (1413 KB) for firmware dump...
qla2xxx 0000:10:00.0: Waiting for LIP to complete...
qla2xxx 0000:10:00.0: Cable is unplugged...
scsi0 : qla2xxx
I looked at the package and saw that it provides hooks to initramfs, but
it's not clear that they were working. I looked at firmware-qlogic's
postinst and found this,
case "$1" in
configure)
if [ -x /usr/sbin/update-initramfs -a -e
/etc/mkinitramfs/initramfs.conf ] ; then
update-initramfs -u
fi
;;
I don't have that conf file on my system and it's not clear that I need it.
I ran "update-initramfs -u" by hand and then on the next reboot the
firmware loaded properly,
qla2xxx 0000:10:00.1: Found an ISP2432, irq 90, iobase 0xffffc2000001a000
qla2xxx 0000:10:00.1: Configuring PCI space...
PCI: Setting latency timer of device 0000:10:00.1 to 64
qla2xxx 0000:10:00.1: Configure NVRAM parameters...
qla2xxx 0000:10:00.1: Verifying loaded RISC code...
qla2xxx 0000:10:00.1: Allocated (64 KB) for EFT...
qla2xxx 0000:10:00.1: Allocated (1413 KB) for firmware dump...
qla2xxx 0000:10:00.1: Waiting for LIP to complete...
qla2xxx 0000:10:00.1: Cable is unplugged...
scsi1 : qla2xxx
Is there a reason the postinst is checking for that file?
This version is also the same in etch. Whatever the bug/fix, it would be
nice if it could be fixed in etch as well.
Thanks,
--
Matt Taggart
taggart@debian.org
Reply to: