Red Hat Bugzilla – Bug 235277
mkinitrd needs to pull in MODULE_FIRMWARE firmware
Last modified: 2013-09-02 02:20:43 EDT
We need the MODULE_FIRMWARE enablers already added to Fedora mkinitrd to be in
5.1 too so firmware updating can work.
This request was evaluated by Red Hat Product Management for inclusion in a Red
Hat Enterprise Linux maintenance release. Product Management has requested
further review of this request by Red Hat Engineering, for potential
inclusion in a Red Hat Enterprise Linux Update release for currently deployed
products. This request is not yet committed for inclusion in an Update
Any pointers to a mkinitrd package that allows RHEL5U1 firmware
loading/updating? Stock RHEL5U1 doesn't support it.
I believe this is in RHEL5.1. In order for this to work, your module needs to
make use of the MODULE_FIRMWARE macro, which it might not yet. What's the module?
The qla2xxx driver from 184.108.40.206.
The following MODULE_FIRMWARE instances exist:
And "modinfo -F firmware qla2xxx" shows:
I can also see mkinitrd copying the firmware to the initrd:
`/lib/firmware/ql2300_fw.bin' -> `/tmp/initrd.we3894/lib/firmware/ql2300_fw.bin'
But yet when I load that initrd it still doesn't load/find the firmware. And
the qla2xxx driver ultimately fails to load.
Could this be at all related to bug#378651 ?
Created attachment 292189 [details]
Fix for uninitialized flag in nash's hotplug.c
To respond to my comment#4, FC8's bug#378651 is the issue here. RHEL5U1 also
does NOT properly load firmware for the qla2xxx.
The attached patch fixes it for RHEL5U1 (as verified with a 220.127.116.11 kernel).
I really need RHEL5U2 to include this mkinitrd fix...
Fixed in mkinitrd-18.104.22.168-21 .
An advisory has been issued which should help the problem
described in this bug report. This report is therefore being
closed with a resolution of ERRATA. For more information
on the solution and/or where to find the updated files,
please follow the link below. You may reopen this bug report
if the solution does not work for you.
*** Bug 380641 has been marked as a duplicate of this bug. ***