[elrepo] PSA: v5.2 requires a newer broadcom firmware for broadcom nics to work

[Alan Bartlett]

On Fri, 9 Aug 2019 at 15:03, Alan Bartlett <ajb at elrepo.org> wrote:
>
> On Wed, 7 Aug 2019 at 21:19, Dave Chiluk via elrepo
> <elrepo at lists.elrepo.org> wrote:
> >
> > Kernels newer than v5.2-rc1 are now shipping with
> > https://git.kernel.org/pub/scm/linux/kernel/git/torvalds/linux.git/commit/?id=32705592f94
> >
> > Without this firmware file, affected broadcom bnx2x network cards will
> > not be able to initialize and will report an error of
> > "
> > bnx2x XXXX:XX:XX.X: Direct firmware load for
> > bnx2x/bnx2x-e2-7.13.11.0.fw failed with error -2
> > bnx2x: [bnx2x_init_firmware:13542(em1)]Can't laod firmware file
> > bnx2x/bnx2x-e2-7.13.11.0.fw
> > "
> > This is kind of a big breaking change.
> >
> > That firmware file can be downloaded and installed into
> > /lib/firmware/bnx2x/bnx2x-e2-7.13.11.0.fw
> > from
> > https://git.kernel.org/pub/scm/linux/kernel/git/firmware/linux-firmware.git/tree/bnx2x/bnx2x-e2-7.13.11.0.fw
> >
> > My question is, does ELREPO provide updated linux-firmware rpms
> > anywhere?  Otherwise users are just going to have to download this
> > independently.
>
> Sorry for the delay in responding, Dave.
>
> As the linux-firmware package is relevant to the kernel package and I
> am responsible for the kernel-ml package sets, I have taken ownership
> of your request. I have now opened a RFE in the ELRepo Project
> bug-tracker [1], copying your above message verbatim.
>
> All being well I should have an updated package released to the
> elrepo-testing repository in the next, say, 24 hours. I will mention
> here once it is available. If you could then test the package and
> report back with your observations that will be appreciated, please. A
> positive report will result in the package being promoted from the
> elrepo-testing to the elrepo-extras repository.
>
> Alan.
>
> [1] https://elrepo.org/bugs/view.php?id=923

The following files have now been released to the elrepo-testing
repository and are currently synchronising across our network of
mirror sites.

src
linux-firmware-20190807-72.1.gitdff98c6.el7_7.elrepo.src.rpm

noarch
iwl1000-firmware-39.31.5.1-72.1.el7_7.elrepo.noarch.rpm
iwl100-firmware-39.31.5.1-72.1.el7_7.elrepo.noarch.rpm
iwl105-firmware-18.168.6.1-72.1.el7_7.elrepo.noarch.rpm
iwl135-firmware-18.168.6.1-72.1.el7_7.elrepo.noarch.rpm
iwl2000-firmware-18.168.6.1-72.1.el7_7.elrepo.noarch.rpm
iwl2030-firmware-18.168.6.1-72.1.el7_7.elrepo.noarch.rpm
iwl3160-firmware-22.0.7.0-72.1.el7_7.elrepo.noarch.rpm
iwl3945-firmware-15.32.2.9-72.1.el7_7.elrepo.noarch.rpm
iwl4965-firmware-228.61.2.24-72.1.el7_7.elrepo.noarch.rpm
iwl5000-firmware-8.83.5.1_1-72.1.el7_7.elrepo.noarch.rpm
iwl5150-firmware-8.24.2.2-72.1.el7_7.elrepo.noarch.rpm
iwl6000-firmware-9.221.4.1-72.1.el7_7.elrepo.noarch.rpm
iwl6000g2a-firmware-17.168.5.3-72.1.el7_7.elrepo.noarch.rpm
iwl6000g2b-firmware-17.168.5.2-72.1.el7_7.elrepo.noarch.rpm
iwl6050-firmware-41.28.5.1-72.1.el7_7.elrepo.noarch.rpm
iwl7260-firmware-22.0.7.0-72.1.el7_7.elrepo.noarch.rpm
iwl7265-firmware-22.0.7.0-72.1.el7_7.elrepo.noarch.rpm
linux-firmware-20190807-72.1.gitdff98c6.el7_7.elrepo.noarch.rpm

Please test, when time permits, and report back with your findings.

You can update your system with a command sequence similar to the following --

yum --disablerepo \* --enablerepo elrepo-testing clean expire-cache
yum --disablerepo \* --enablerepo elrepo-testing update linux-firmware

Alan.