Description of problem: Ever since later FC6 kernels, the Qlogic 2xxx driver doesn't load on boot with a 'can't find firmware' error during boot. This makes using it in production virtually impossible for RAID devices. Version-Release number of selected component (if applicable): Any Fedora kernel >= 2.6.22 How reproducible: Every boot. Steps to Reproduce: 1.Select >=2.6.22 kernel in any OS from Fedora Core 6 to FC8 (not tested 9) 2. 3. Actual results: Firmware error message on boot. FC devices not available after boot, unless rmmod and modprobe qla2xxx driver. Expected results: The qla2xxx driver should load fine as the firmware is available on the system, and even after creating a new initrd image with the firmware explicitly added, it still doesn't see the firmware. Additional info: This needs to be addressed as soon as possible, I'm unable to upgrade my existing systems past kernel 2.6.20 in FC6 because of this problem. There was mention of initramfs needing to be tweaked, but I'm unable to find /any/ reason at all for this to be a problem.
dwmw2 is poking at various firmware type things right now. Maybe he has some idea what went horribly wrong here.
Exactly what device is it? Can you instrument the scripts to check that the expected firmware really is being requested?
This is what I get when I have used the initrd that comes with the kernel, and when I've unpacekd initrd, added the firmware to it in /lib/firmware and repacked it and used it. qla2xxx 0000:02:07.0: Found an ISP2300, irq 26, iobase 0xffffc2000063a000 qla2xxx 0000:02:07.0: Configuring PCI space... qla2xxx 0000:02:07.0: Configure NVRAM parameters... qla2xxx 0000:02:07.0: Verifying loaded RISC code... qla2xxx 0000:02:07.0: Firmware image unavailable. qla2xxx 0000:02:07.0: Firmware images can be retrieved from: ftp://ftp.qlogic.com/outgoing/linux/firmware/. qla2xxx 0000:02:07.0: Failed to initialize adapter qla2xxx 0000:02:07.0: Found an ISP2300, irq 26, iobase 0xffffc2000107a000 qla2xxx 0000:02:07.0: Configuring PCI space... qla2xxx 0000:02:07.0: Configure NVRAM parameters... qla2xxx 0000:02:07.0: Verifying loaded RISC code... qla2xxx 0000:02:07.0: Allocated (412 KB) for firmware dump... scsi7 : qla2xxx qla2xxx 0000:02:07.0: qla2xxx 0000:02:07.0: LOOP UP detected (2 Gbps). Can you tell me how to get you the other info you need?
You shouldn't need to add the firmware to the initrd manually -- mkinitrd should include it automatically. This sounds like a mkinitrd problem.
Well, adding it to initrd was one of the possible solutions I was given in the mailing list. However, I got the same error even when I did that. When I built a new initrd with mkinitrd, I saw where the firmware was logged that it was found and/or added. I had a thought last night that maybe this is only a x86_64 problem, so I'm installing the i386 version to my test machine to see if I see the same problem.
I installed the x86 version of Fedora 7 and 8 on my test box and had the exact same problem, so it's not only a x86_64 bit issue. I don't have any other arch's so I can't say for sure if the rest are affected or not.
This message is a reminder that Fedora 8 is nearing its end of life. Approximately 30 (thirty) days from now Fedora will stop maintaining and issuing updates for Fedora 8. It is Fedora's policy to close all bug reports from releases that are no longer maintained. At that time this bug will be closed as WONTFIX if it remains open with a Fedora 'version' of '8'. Package Maintainer: If you wish for this bug to remain open because you plan to fix it in a currently maintained version, simply change the 'version' to a later Fedora version prior to Fedora 8's end of life. Bug Reporter: Thank you for reporting this issue and we are sorry that we may not be able to fix it before Fedora 8 is end of life. If you would still like to see this bug fixed and are able to reproduce it against a later version of Fedora please change the 'version' of this bug to the applicable version. If you are unable to change the version, please add a comment here and someone will do it for you. Although we aim to fix as many bugs as possible during every release's lifetime, sometimes those efforts are overtaken by events. Often a more recent Fedora release includes newer upstream software that fixes bugs or makes them obsolete. The process we are following is described here: http://fedoraproject.org/wiki/BugZappers/HouseKeeping
I can confirm that this bug still occurs in F9, and will test F10 after the holidays and will most likely update the bug again. This has been a problem since FC6, and I've seen virtually no movement on it so I'm willing to bet it will be a problem in F10 as well.
I can confirm I have the exact same problem on Fedora 10. This is what I see in dmesg: QLogic Fibre Channel HBA Driver: 8.02.01-k7 qla2xxx 0000:02:07.0: PCI INT A -> GSI 26 (level, low) -> IRQ 26 qla2xxx 0000:02:07.0: Found an ISP2300, irq 26, iobase 0xffffc20001040000 qla2xxx 0000:02:07.0: Configuring PCI space... qla2xxx 0000:02:07.0: Configure NVRAM parameters... udev: renamed network interface eth0 to eth2 qla2xxx 0000:02:07.0: Verifying loaded RISC code... firmware: requesting ql2300_fw.bin ppdev: user-space parallel port driver firewire_core: created device fw0: GUID 00e0810000302947, S400 qla2xxx 0000:02:07.0: Firmware image unavailable. qla2xxx 0000:02:07.0: Firmware images can be retrieved from: ftp://ftp.qlogic.com/outgoing/linux/firmware/. qla2xxx 0000:02:07.0: Failed to initialize adapter qla2xxx 0000:02:07.0: PCI INT A disabled I am still completely unable to upgrade my systems past FC6 because of this problem. I can't understand how this can still be a bug after 2 years. At least not a high priority one.
This message is a reminder that Fedora 10 is nearing its end of life. Approximately 30 (thirty) days from now Fedora will stop maintaining and issuing updates for Fedora 10. It is Fedora's policy to close all bug reports from releases that are no longer maintained. At that time this bug will be closed as WONTFIX if it remains open with a Fedora 'version' of '10'. Package Maintainer: If you wish for this bug to remain open because you plan to fix it in a currently maintained version, simply change the 'version' to a later Fedora version prior to Fedora 10's end of life. Bug Reporter: Thank you for reporting this issue and we are sorry that we may not be able to fix it before Fedora 10 is end of life. If you would still like to see this bug fixed and are able to reproduce it against a later version of Fedora please change the 'version' of this bug to the applicable version. If you are unable to change the version, please add a comment here and someone will do it for you. Although we aim to fix as many bugs as possible during every release's lifetime, sometimes those efforts are overtaken by events. Often a more recent Fedora release includes newer upstream software that fixes bugs or makes them obsolete. The process we are following is described here: http://fedoraproject.org/wiki/BugZappers/HouseKeeping
Fedora 10 changed to end-of-life (EOL) status on 2009-12-17. Fedora 10 is no longer maintained, which means that it will not receive any further security or bug fix updates. As a result we are closing this bug. If you can reproduce this bug against a currently maintained version of Fedora please feel free to reopen this bug against that version. Thank you for reporting this bug and we are sorry it could not be fixed.