I have a Broadcom (now QLogic) NetXtreme II BCM5709 Ethernet controller with 4 ports but I can
only use the first 2. When I go into Yast -> Network Settings and look at this card it shows all 4
ports. The first 2 have all the information showing including MAC address. For the second 2, it
only shows the BusID. When I select either of these last 2 ports the YAST status message is:
“Unable to configure the network card because the kernel device (eth0, wlan0) is not
present. This is mostly caused by missing firmware. See dmesg output for details.”
I have configured the first two ports for my network needs and they work OK.
This network card uses the bnx2 driver. When I run this command after boot up:
dmesg | grep bnx2
I get these kernel messages:
7.982850] bnx2: QLogic bnx2 Gigabit Ethernet Driver v2.2.6 (January 29, 2014)
7.982875] bnx2 0000:05:00.0: enabling device (0000 -> 0002)
7.984106] bnx2 0000:05:00.0 eth0: Broadcom NetXtreme II BCM5709 1000Base-T (C0) PCI Express found at mem da000000, IRQ 18, node addr 00:10:18:96:50:10
7.984143] bnx2 0000:05:00.1: enabling device (0000 -> 0002)
7.985294] bnx2 0000:05:00.1 eth1: Broadcom NetXtreme II BCM5709 1000Base-T (C0) PCI Express found at mem d8000000, IRQ 19, node addr 00:10:18:96:50:12
7.985326] bnx2 0000:06:00.0: enabling device (0000 -> 0002)
7.985489] bnx2 0000:06:00.0: Firmware not running, aborting
7.985634] bnx2 0000:06:00.1: enabling device (0000 -> 0002)
7.985772] bnx2 0000:06:00.1: Firmware not running, aborting
8.156209] bnx2 0000:05:00.1 eth2: renamed from eth1
8.172175] bnx2 0000:05:00.0 eth1: renamed from eth0
17.261561] bnx2 0000:05:00.0 eth1: using MSIX
17.333682] bnx2 0000:05:00.1 eth2: using MSIX
20.145899] bnx2 0000:05:00.1 eth2: NIC Copper Link is Up, 1000 Mbps full duplex
20.145904] bnx2: , receive bnx2: & transmit bnx2: flow control ONbnx2:
21.017495] bnx2 0000:05:00.0 eth1: NIC Copper Link is Up, 1000 Mbps full duplex
21.017500] bnx2: , receive bnx2: & transmit bnx2: flow control ONbnx2:
The directory /lib/firmware/bnx2 has these files:
bnx2-mips-06-4.6.16.fw
bnx2-mips-06-5.0.0.j3.fw
bnx2-mips-06-5.0.0.j6.fw
bnx2-mips-06-6.0.15.fw
bnx2-mips-06-6.2.3.fw
bnx2-mips-09-4.6.17.fw
bnx2-mips-09-5.0.0.j15.fw
bnx2-mips-09-5.0.0.j3.fw
bnx2-mips-09-5.0.0.j9.fw
bnx2-mips-09-6.0.17.fw
bnx2-mips-09-6.2.1b.fw
bnx2-mips-09-6.2.1.fw
bnx2-rv2p-06-4.6.16.fw
bnx2-rv2p-06-5.0.0.j3.fw
bnx2-rv2p-09-4.6.15.fw
bnx2-rv2p-09-5.0.0.j10.fw
bnx2-rv2p-09-5.0.0.j3.fw
bnx2-rv2p-09ax-5.0.0.j10.fw
bnx2-rv2p-09ax-5.0.0.j3.fw
From all the research I’ve done it seems like the problem involves one or more
of these firmware files not being loaded properly (or maybe the wrong one?)
The YAST software manager shows the installed kernel-firmware being the
latest available.
Also, it looks like their could be a configuration problem with the initrd or with
udev.
Need some help on where to go from here.