Broadcom 10GbE bnx2x driver installed, but not showing up in ifconfig

I’m trying to configure a Broadcom BCM57840 NetXtreme II 10 GigE. It shows up in lspci, and the bnx2x driver appears to be installed after running

modprobe -l | grep bnx

Shows

kernel/drivers/scsi/bnx2fc/bnx2fc.ko
kernel/drivers/scsi/bnx2i/bnx2i.ko
kernel/drivers/net/ethernet/broadcom/bnx2.ko
kernel/drivers/net/ethernet/broadcom/bnx2x/bnx2x.ko

I’ve added it using

modprobe bnx2x

. But I still cannot get them to show up as interfaces in ifconfig. Here’s an lspci -v of the one of the ports of the card. Note that even though it bnx2x appears to be installed, it does not show any driver being used.

01:00.0 Ethernet controller: Broadcom Corporation BCM57840 NetXtreme II 10 Gigabit Ethernet (rev 11)
        Subsystem: Broadcom Corporation Device 4000
        Flags: bus master, fast devsel, latency 0, IRQ 11
        Memory at 381fff000000 (64-bit, prefetchable) [size=8]
        Memory at 381ffe800000 (64-bit, prefetchable) [size=8]
        Memory at 381fff830000 (64-bit, prefetchable) [size=64]
        Expansion ROM at daa80000 [disabled] [size=512]
        Capabilities: [48] Power Management version 3
        Capabilities: [50] Vital Product Data
        Capabilities: [58] MSI: Enable- Count=1/8 Maskable- 64bit+
        Capabilities: [a0] MSI-X: Enable- Count=32 Masked-
        Capabilities: [ac] Express Endpoint, MSI 00
        Capabilities: [100] Advanced Error Reporting
        Capabilities: [13c] Device Serial Number 0c-c4-7a-ff-fe-1d-6e-90
        Capabilities: [150] Power Budgeting <?>
        Capabilities: [160] Virtual Channel
        Capabilities: [1b8] Alternative Routing-ID Interpretation (ARI)
        Capabilities: [220] #15
        Capabilities: [210] Address Translation Service (ATS)
        Capabilities: [300] #19

I tried installing the bnx drivers that came with the card in case a newer versions is required than the one that’s already installed (via a xxxx.src.rpm). But when I do the rpmbuild -bb I get pre-processor errors.

Any suggestions? Should I work on fixing the pre-processor errors or is there a way I can manually try to get the card to be usable?

Thanks for looking,
openSUSE rocks![/size][/size][/size][/size]

… but not showing up in ifconfig

How do you know? What did you expect to see and what did you see instead?
You provided a lot of usefull information, except this ifconfig listing.

The chipset details may be useful to know too

lspci -vn

It won’t show up as an interface unless you configure the device in YAST / Network Devices - just loading the module does nothing (except make it show up there)

For the ifconfig:

I’m am looking for each interface to show up as ethX, ethX+1, etc. so I can use the card’s 4 interfaces for streaming UDP packets.

lspci -vn 
01:00.0 0200: 14e4:16a1 (rev 11)
        Subsystem: 14e4:4000
        Flags: bus master, fast devsel, latency 0, IRQ 11
        Memory at 381fff000000 (64-bit, prefetchable) [size=8]
        Memory at 381ffe800000 (64-bit, prefetchable) [size=8]
        Memory at 381fff830000 (64-bit, prefetchable) [size=64]
        Expansion ROM at daa80000 [disabled] [size=512]
        Capabilities: [48] Power Management version 3
        Capabilities: [50] Vital Product Data
        Capabilities: [58] MSI: Enable- Count=1/8 Maskable- 64bit+
        Capabilities: [a0] MSI-X: Enable- Count=32 Masked-
        Capabilities: [ac] Express Endpoint, MSI 00
        Capabilities: [100] Advanced Error Reporting
        Capabilities: [13c] Device Serial Number 0c-c4-7a-ff-fe-1d-6e-90
        Capabilities: [150] Power Budgeting <?>
        Capabilities: [160] Virtual Channel
        Capabilities: [1b8] Alternative Routing-ID Interpretation (ARI)
        Capabilities: [220] #15
        Capabilities: [210] Address Translation Service (ATS)
        Capabilities: [300] #19

01:00.1 0200: 14e4:16a1 (rev 11)
        Subsystem: 14e4:4000
        Flags: bus master, fast devsel, latency 0, IRQ 10
        Memory at 381ffe000000 (64-bit, prefetchable) [size=8]
        Memory at 381ffd800000 (64-bit, prefetchable) [size=8]
        Memory at 381fff820000 (64-bit, prefetchable) [size=64]
        Expansion ROM at daa00000 [disabled] [size=512]
        Capabilities: [48] Power Management version 3
        Capabilities: [50] Vital Product Data
        Capabilities: [58] MSI: Enable- Count=1/8 Maskable- 64bit+
        Capabilities: [a0] MSI-X: Enable- Count=32 Masked-
        Capabilities: [ac] Express Endpoint, MSI 00
        Capabilities: [100] Advanced Error Reporting
        Capabilities: [13c] Device Serial Number 0c-c4-7a-ff-fe-1d-6e-90
        Capabilities: [150] Power Budgeting <?>
        Capabilities: [160] Virtual Channel
        Capabilities: [1b8] Alternative Routing-ID Interpretation (ARI)
        Capabilities: [220] #15
        Capabilities: [210] Address Translation Service (ATS)

01:00.2 0200: 14e4:16a1 (rev 11)
        Subsystem: 14e4:4000
        Flags: bus master, fast devsel, latency 0, IRQ 10
        Memory at 381ffd000000 (64-bit, prefetchable) [size=8]
        Memory at 381ffc800000 (64-bit, prefetchable) [size=8]
        Memory at 381fff810000 (64-bit, prefetchable) [size=64]
        Expansion ROM at da980000 [disabled] [size=512]
        Capabilities: [48] Power Management version 3
        Capabilities: [50] Vital Product Data
        Capabilities: [58] MSI: Enable- Count=1/8 Maskable- 64bit+
        Capabilities: [a0] MSI-X: Enable- Count=32 Masked-
        Capabilities: [ac] Express Endpoint, MSI 00
        Capabilities: [100] Advanced Error Reporting
        Capabilities: [13c] Device Serial Number 0c-c4-7a-ff-fe-1d-6e-94
        Capabilities: [150] Power Budgeting <?>
        Capabilities: [160] Virtual Channel
        Capabilities: [1b8] Alternative Routing-ID Interpretation (ARI)
        Capabilities: [220] #15
        Capabilities: [210] Address Translation Service (ATS)

01:00.3 0200: 14e4:16a1 (rev 11)
        Subsystem: 14e4:4000
        Flags: bus master, fast devsel, latency 0, IRQ 5
        Memory at 381ffc000000 (64-bit, prefetchable) [size=8]
        Memory at 381ffb800000 (64-bit, prefetchable) [size=8]
        Memory at 381fff800000 (64-bit, prefetchable) [size=64]
        Expansion ROM at da900000 [disabled] [size=512]
        Capabilities: [48] Power Management version 3
        Capabilities: [50] Vital Product Data
        Capabilities: [58] MSI: Enable- Count=1/8 Maskable- 64bit+
        Capabilities: [a0] MSI-X: Enable- Count=32 Masked-
        Capabilities: [ac] Express Endpoint, MSI 00
        Capabilities: [100] Advanced Error Reporting
        Capabilities: [13c] Device Serial Number 0c-c4-7a-ff-fe-1d-6e-94
        Capabilities: [150] Power Budgeting <?>
        Capabilities: [160] Virtual Channel
        Capabilities: [1b8] Alternative Routing-ID Interpretation (ARI)
        Capabilities: [220] #15
        Capabilities: [210] Address Translation Service (ATS)

Configure with Yast reply: I looked at the Network settings in Yast and it sees the 4 broadcom interfaces. However, the “edit” button is not clickable and a message saying that the “kernel device is not present”. Also that it is mostly caused by missing firmware and to check dmesg.

Here’s the dmesg info for the device and anything broadcom

    0.835490] pci 0000:01:00.0: [14e4:16a1] type 00 class 0x020000
    0.835504] pci 0000:01:00.0: reg 10: [mem 0x381fff000000-0x381fff7fffff 64bit pref]
    0.835516] pci 0000:01:00.0: reg 18: [mem 0x381ffe800000-0x381ffeffffff 64bit pref]
    0.835527] pci 0000:01:00.0: reg 20: [mem 0x381fff830000-0x381fff83ffff 64bit pref]
    0.835536] pci 0000:01:00.0: reg 30: [mem 0xdaa80000-0xdaafffff pref]
    0.835579] pci 0000:01:00.0: PME# supported from D0 D3hot
    0.835617] pci 0000:01:00.1: [14e4:16a1] type 00 class 0x020000
    0.835631] pci 0000:01:00.1: reg 10: [mem 0x381ffe000000-0x381ffe7fffff 64bit pref]
    0.835643] pci 0000:01:00.1: reg 18: [mem 0x381ffd800000-0x381ffdffffff 64bit pref]
    0.835654] pci 0000:01:00.1: reg 20: [mem 0x381fff820000-0x381fff82ffff 64bit pref]
    0.835663] pci 0000:01:00.1: reg 30: [mem 0xdaa00000-0xdaa7ffff pref]
    0.835706] pci 0000:01:00.1: PME# supported from D0 D3hot
    0.835740] pci 0000:01:00.2: [14e4:16a1] type 00 class 0x020000
    0.835754] pci 0000:01:00.2: reg 10: [mem 0x381ffd000000-0x381ffd7fffff 64bit pref]
    0.835765] pci 0000:01:00.2: reg 18: [mem 0x381ffc800000-0x381ffcffffff 64bit pref]
    0.835777] pci 0000:01:00.2: reg 20: [mem 0x381fff810000-0x381fff81ffff 64bit pref]
    0.835785] pci 0000:01:00.2: reg 30: [mem 0xda980000-0xda9fffff pref]
    0.835829] pci 0000:01:00.2: PME# supported from D0 D3hot
    0.835860] pci 0000:01:00.3: [14e4:16a1] type 00 class 0x020000
    0.835873] pci 0000:01:00.3: reg 10: [mem 0x381ffc000000-0x381ffc7fffff 64bit pref]
    0.835885] pci 0000:01:00.3: reg 18: [mem 0x381ffb800000-0x381ffbffffff 64bit pref]
    0.835897] pci 0000:01:00.3: reg 20: [mem 0x381fff800000-0x381fff80ffff 64bit pref]
    0.835905] pci 0000:01:00.3: reg 30: [mem 0xda900000-0xda97ffff pref]
    0.835948] pci 0000:01:00.3: PME# supported from D0 D3hot
...
    1.266239] pci 0000:01:00.0: Signaling PME through PCIe PME interrupt
    1.266241] pci 0000:01:00.1: Signaling PME through PCIe PME interrupt
    1.266243] pci 0000:01:00.2: Signaling PME through PCIe PME interrupt
    1.266245] pci 0000:01:00.3: Signaling PME through PCIe PME interrupt
...
  220.536226] bnx2x: Broadcom NetXtreme II 5771x/578xx 10/20-Gigabit Ethernet Driver bnx2x 1.72.10-0 (2012/02/20)

Maybe I need to find an updated broadcom driver.[/size][/size][/size][/size][/size][/size][/size][/size][/size][/size][/size][/size][/size][/size][/size][/size]

Do you have the kernel-firmware package installed?

Deano is right, you need the kernel-firmware package, it contains the bnx2x firmwares for various versions of the card.

Apart from the fact that you should follow the advice of the other two posters here, that is NOT what I asked for. How difficult is it to post the ifconfig output? You showed that you can perfectly post lspci output. What is the basic difference that you are not able to do a

ifconfig

and copy/paste the prompt, the command, the output and the next prompt between CODE tags in a post here?

It seems that you think that we are looking at the same details as you and thus that you can refrain from posting and tell us instead what you think we will look at when you would have posted it. This is not the case. The fact that you say you are looking for ethX devices proves this. These names are not used anymore.

Using yast to search for kernel-firmware shows this is installed:

kernel-firmware - Linux kernel firmware files
Version: 20120719git-2.9.1 Installed: 20120719git-2.9.1                                   
License: SUSE-Firmware ; GPL-2.0 ; GPL-2.0+ ; MIT
Package Group: System/Kernel
Source Package: kernel-firmware-20120719git-2.9.1

I apologize, I was confused at what you wanted… Output of ifconfig:

eth0      Link encap:Ethernet  HWaddr 00:E0:81:E3:E1:C4
          inet addr:192.168.0.51  Bcast:192.168.0.255  Mask:255.255.255.0
          inet6 addr: fe80::2e0:81ff:fee3:e1c4/64 Scope:Link
          UP BROADCAST RUNNING MULTICAST  MTU:1500  Metric:1
          RX packets:79996 errors:0 dropped:0 overruns:0 frame:0
          TX packets:17536 errors:0 dropped:0 overruns:0 carrier:0
          collisions:0 txqueuelen:1000
          RX bytes:33199977 (31.6 Mb)  TX bytes:3481243 (3.3 Mb)
eth1      Link encap:Ethernet  HWaddr 00:E0:81:E3:E1:C5
          UP BROADCAST MULTICAST  MTU:1500  Metric:1
          RX packets:0 errors:0 dropped:0 overruns:0 frame:0
          TX packets:0 errors:0 dropped:0 overruns:0 carrier:0
          collisions:0 txqueuelen:1000
          RX bytes:0 (0.0 b)  TX bytes:0 (0.0 b)
lo        Link encap:Local Loopback
          inet addr:127.0.0.1  Mask:255.0.0.0
          inet6 addr: ::1/128 Scope:Host
          UP LOOPBACK RUNNING  MTU:16436  Metric:1
          RX packets:29 errors:0 dropped:0 overruns:0 frame:0
          TX packets:29 errors:0 dropped:0 overruns:0 carrier:0
          collisions:0 txqueuelen:0
          RX bytes:3889 (3.7 Kb)  TX bytes:3889 (3.7 Kb)

Ok, after three days I have to recap. And that brought me to the fact that I can not find anywhere which version of openSUSE you use. Something that is normaly the first thing I ask for when people think we are clairvoyant, which is not the case.

Seeing your ifconfig output, I now doubt that this is 13.1. So please tell us before people give advice valid for the wrong version.

Oh you’re running 12.2 - well now, that might be a problem.

Have you tried the 13.1 LiveCD to see if the adapter works there? It may simply be an issue with the drivers+firmware being old (you may need to install kernel-firmware when running the LiveCD)

That’s quite old. Which openSUSE version are you using?
13.1 and 12.3 have 20130714git.

This seems to be 12.2 then. (so the wired network devices are still called ethX, and only that)

Two notes:

  • 12.2 is out of support since January already, see http://en.opensuse.org/Lifetime .
  • It’s possible that the driver in 12.2 did not support that device yet.
    The PCI ID of your card is listed in the output of “modinfo bnx2x” here on my 13.1 system, so I suppose it should work in 13.1 at least (kernel 3.11.10).

So, all in all I would recommend that you upgrade to a supported openSUSE release instead.
Maybe this alone would make it work. (but you should do that anyway)
If that doesn’t help, or if you cannot upgrade right now for whatever reason, try at least to install a newer kernel and kernel-firmware from:
http://download.opensuse.org/repositories/Kernel:/stable/standard/

I apologize, I was confused at what you wanted… Output of ifconfig:

So eth0 and eth1 seem to be working (eth0 even has an IP-Address).
I take it those are from a different card?

kernel-firmware is included in the LiveCD AFAIK, so this should not be necessary.

The LiveCD is having trouble with AST graphics and appears to be very similar to this thread.

But, I added nomodeset and was able to verify that the issue is the outdated drivers in use by 12.2.

The 13.1 Gnome LiveCD shows the Broadcom device using bnx2x via lspci. Ifconfig also shows the 10GbE ports.

Thank you!