Groups | Search | Server Info | Keyboard shortcuts | Login | Register [http] [https] [nntp] [nntps]

Groups > linux.debian.user > #177991 > unrolled thread

Error when compiling drivers for Asus PEB-10G/57811-1S

Started byLeslie Rhorer <lrhorer@mygrande.net>
First post2017-02-19 13:20 +0100
Last post2017-02-24 16:50 +0100
Articles 15 — 4 participants

Back to article view | Back to linux.debian.user

Contents

  Error when compiling drivers for Asus PEB-10G/57811-1S Leslie Rhorer <lrhorer@mygrande.net> - 2017-02-19 13:20 +0100
    Re: Error when compiling drivers for Asus PEB-10G/57811-1S Sven Hartge <sven@svenhartge.de> - 2017-02-19 14:10 +0100
    Re: Error when compiling drivers for Asus PEB-10G/57811-1S deloptes <deloptes@gmail.com> - 2017-02-19 19:40 +0100
    Re: Error when compiling drivers for Asus PEB-10G/57811-1S deloptes <deloptes@gmail.com> - 2017-02-19 19:40 +0100
    Re: Error when compiling drivers for Asus PEB-10G/57811-1S Leslie Rhorer <lrhorer@mygrande.net> - 2017-02-19 23:00 +0100
      Re: Error when compiling drivers for Asus PEB-10G/57811-1S deloptes <deloptes@gmail.com> - 2017-02-20 23:50 +0100
    Re: Error when compiling drivers for Asus PEB-10G/57811-1S Leslie Rhorer <lrhorer@mygrande.net> - 2017-02-19 23:50 +0100
    Re: Error when compiling drivers for Asus PEB-10G/57811-1S Mark Fletcher <mark27q1@gmail.com> - 2017-02-20 00:00 +0100
    Re: Error when compiling drivers for Asus PEB-10G/57811-1S Leslie Rhorer <lrhorer@mygrande.net> - 2017-02-20 07:40 +0100
    Re: Error when compiling drivers for Asus PEB-10G/57811-1S Leslie Rhorer <lrhorer@mygrande.net> - 2017-02-20 07:40 +0100
    Re: Error when compiling drivers for Asus PEB-10G/57811-1S Leslie Rhorer <lrhorer@mygrande.net> - 2017-02-22 00:50 +0100
      Re: Error when compiling drivers for Asus PEB-10G/57811-1S deloptes <deloptes@gmail.com> - 2017-02-22 08:40 +0100
    Re: Error when compiling drivers for Asus PEB-10G/57811-1S Leslie Rhorer <lrhorer@mygrande.net> - 2017-02-22 09:40 +0100
    Re: Error when compiling drivers for Asus PEB-10G/57811-1S Leslie Rhorer <lrhorer@mygrande.net> - 2017-02-22 22:10 +0100
      Re: Error when compiling drivers for Asus PEB-10G/57811-1S deloptes <deloptes@gmail.com> - 2017-02-24 16:50 +0100

#177991 — Error when compiling drivers for Asus PEB-10G/57811-1S

FromLeslie Rhorer <lrhorer@mygrande.net>
Date2017-02-19 13:20 +0100
SubjectError when compiling drivers for Asus PEB-10G/57811-1S
Message-ID<tcyD7-7hd-11@gated-at.bofh.it>
I purchased a couple of Asus PEB-10G/57811-1S 10G LAN adapters.  I am not finding any pre-built binaries nor a .deb reporitory for these cards, so I am attempting t o compile from scratch, but I get the following error during the make operation:

Backup/Server-Main/Temp/netxtreme2-7.10.42/bnx2-2.710.30/src/bnx2.c: In function ‘bnx2_rx_int’:
/Backup/Server-Main/Temp/netxtreme2-7.10.42/bnx2-2.710.30/src/bnx2.c:3753:7: error: ‘struct sk_buff’ has no member named ‘rxhash’
    skb->rxhash = rx_hdr->l2_fhdr_hash;
       ^
/usr/src/linux-headers-3.16.0-4-common/scripts/Makefile.build:268: recipe for target '/Backup/Server-Main/Temp/netxtreme2-7.10.42/bnx2-2.710.30/src/bnx2.o' failed

Does anyone have an ideas?  Are there any pre-built drivers for these cards for Debian Jessie?

[toc] | [next] | [standalone]

#177996

FromSven Hartge <sven@svenhartge.de>
Date2017-02-19 14:10 +0100
Message-ID<tczpw-7Mx-17@gated-at.bofh.it>
In reply to#177991
Leslie Rhorer <lrhorer@mygrande.net> wrote:

> I purchased a couple of Asus PEB-10G/57811-1S 10G LAN adapters.  I am
> not finding any pre-built binaries nor a .deb reporitory for these
> cards, so I am attempting t o compile from scratch,

Why? The bnx2 module is available in the default kernel and should
support those NIC out of the box.

Grüße,
Sven.

-- 
Sigmentation fault. Core dumped.

[toc] | [prev] | [next] | [standalone]

#178001

Fromdeloptes <deloptes@gmail.com>
Date2017-02-19 19:40 +0100
Message-ID<tcEyR-2lV-3@gated-at.bofh.it>
In reply to#177991
Leslie Rhorer wrote:

> bnx2
https://packages.debian.org/jessie/firmware-bnx2

[toc] | [prev] | [next] | [standalone]

#178002

Fromdeloptes <deloptes@gmail.com>
Date2017-02-19 19:40 +0100
Message-ID<tcEyS-2lV-11@gated-at.bofh.it>
In reply to#177991
Leslie Rhorer wrote:

> bnx2

most likely you'll need firmware for it as well

[toc] | [prev] | [next] | [standalone]

#178006

FromLeslie Rhorer <lrhorer@mygrande.net>
Date2017-02-19 23:00 +0100
Message-ID<tcHGq-4eE-13@gated-at.bofh.it>
In reply to#177991
Well, that's good to know, but it's not coming up.  I've never added an Ethernet adapter post-install, so I suspect I need to do something, but I am not sure what.  I did an lsmod, and the bnx2x module is loaded, but not being used.  I loaded the firmware, but I get this error during boot:

[   20.327836] bnx2x 0000:07:00.0: firmware: failed to load bnx2x/bnx2x-e2-7.8.19.0.fw (-2)
[   20.327840] bnx2x 0000:07:00.0: Direct firmware load failed with error -2
[   20.327842] bnx2x 0000:07:00.0: Falling back to user helper
[   20.328247] bnx2x: [bnx2x_func_hw_init:5506(eth3)]Error loading firmware
[   20.328252] bnx2x: [bnx2x_nic_load:2685(eth3)]HW init failed, aborting

[toc] | [prev] | [next] | [standalone]

#178033

Fromdeloptes <deloptes@gmail.com>
Date2017-02-20 23:50 +0100
Message-ID<td4Wm-2dF-13@gated-at.bofh.it>
In reply to#178006
Leslie Rhorer wrote:

> [ 20.327836] bnx2x 0000:07:00.0: firmware: failed to load
> [ bnx2x/bnx2x-e2-7.8.19.0.fw (-2) 20.327840] bnx2x 0000:07:00.0: Direct
> [ firmware load failed with error -2 20.327842] bnx2x 0000:07:00.0:
> [ Falling back to user helper 20.328247] bnx2x:
> [ [bnx2x_func_hw_init:5506(eth3)]Error loading firmware 20.328252] bnx2x:
> [ [bnx2x_nic_load:2685(eth3)]HW init failed, aborting

You need to upload the firware that suits your kernel - you either got older
or newer firmware. I won't expect it to work, or at least not in 10G
If you have custom kernel, it would explain the pain. try the native debian
kernel with the native firmware - I don't know if such is available, but if
card is supported it should be.
I prefer using custom kernel and download firmware from the support sites.

regards

[toc] | [prev] | [next] | [standalone]

#178007

FromLeslie Rhorer <lrhorer@mygrande.net>
Date2017-02-19 23:50 +0100
Message-ID<tcIsN-4KT-5@gated-at.bofh.it>
In reply to#177991
It's still not working, but the card is in the udev file, and ifconfig -a shows the interface.  When I try to bring it up, however, it gives me an error:

Backup:/# ifconfig -a                                                                                 
eth0      Link encap:Ethernet  HWaddr 08:62:66:a1:40:51                                                                                  
          inet addr:192.168.1.97  Bcast:192.168.1.255  Mask:255.255.255.0                                                                
          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)
          Interrupt:36 Memory:d3000000-d37fffff 

eth2      Link encap:Ethernet  HWaddr 50:46:5d:65:15:9c  
          inet addr:192.168.1.51  Bcast:192.168.1.255  Mask:255.255.255.0
          inet6 addr: fe80::5246:5dff:fe65:159c/64 Scope:Link
          UP BROADCAST RUNNING MULTICAST  MTU:1500  Metric:1
          RX packets:180057 errors:0 dropped:2 overruns:0 frame:0
          TX packets:1502041 errors:0 dropped:0 overruns:0 carrier:0
          collisions:0 txqueuelen:1000 
          RX bytes:24120043 (23.0 MiB)  TX bytes:2220773875 (2.0 GiB)

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:65536  Metric:1
          RX packets:58 errors:0 dropped:0 overruns:0 frame:0
          TX packets:58 errors:0 dropped:0 overruns:0 carrier:0
          collisions:0 txqueuelen:0 
          RX bytes:6254 (6.1 KiB)  TX bytes:6254 (6.1 KiB)

Backup:/# ifconfig eth0 192.168.1.97 up
SIOCSIFFLAGS: Cannot allocate memory
SIOCSIFFLAGS: Cannot allocate memory

[toc] | [prev] | [next] | [standalone]

#178009

FromMark Fletcher <mark27q1@gmail.com>
Date2017-02-20 00:00 +0100
Message-ID<tcICt-4ON-5@gated-at.bofh.it>
In reply to#177991
On Sun, Feb 19, 2017 at 03:54:32AM -0800, Leslie Rhorer wrote:
> I purchased a couple of Asus PEB-10G/57811-1S 10G LAN adapters.  I am not finding any pre-built binaries nor a .deb reporitory for these cards, so I am attempting t o compile from scratch, but I get the following error during the make operation:
> 
> Backup/Server-Main/Temp/netxtreme2-7.10.42/bnx2-2.710.30/src/bnx2.c: In function ‘bnx2_rx_int’:
> /Backup/Server-Main/Temp/netxtreme2-7.10.42/bnx2-2.710.30/src/bnx2.c:3753:7: error: ‘struct sk_buff’ has no member named ‘rxhash’
>     skb->rxhash = rx_hdr->l2_fhdr_hash;
>        ^
> /usr/src/linux-headers-3.16.0-4-common/scripts/Makefile.build:268: recipe for target '/Backup/Server-Main/Temp/netxtreme2-7.10.42/bnx2-2.710.30/src/bnx2.o' failed
> 
> Does anyone have an ideas?  Are there any pre-built drivers for these cards for Debian Jessie?
> 

As others on this thread have hinted, possibly less than completely 
clearly, this card is supported by the kernel and IF your particular 
kernel was built with support turned on, THEN all you should need is the 
firmware which is provided by a package deloptes pointed out.

I just checked in the stock Jessie kernel I am running, support for the 
BNX2 is included as a module. Assuming you are also using the stock 
Jessie kernel you get when you install Jessie (tell us if otherwise), 
you should have it as a module too. In that case, on detecting your 
hardware, if the hardware is healthy, udev should have automatically 
loaded the driver. So if you also install the firmware as deloptes 
pointed out, you should at least get the length of a functioning network 
card. Which is different from a functioning network connection you can 
actually use.

If you previously had another card installed, and that card is still 
present, you may have some futzing around to do to persuade the machine 
to bring up the new card and have it connect to the network. Let us know 
if that is so.

In the meantime, assuming you are using a stock kernel and not one you 
built yourself or had someone build for you, and assuming you have 
installed the firmware deloptes mentioned, what is the output of:

$ ip link

?

Mark

[toc] | [prev] | [next] | [standalone]

#178014

FromLeslie Rhorer <lrhorer@mygrande.net>
Date2017-02-20 07:40 +0100
Message-ID<tcPNE-175-13@gated-at.bofh.it>
In reply to#177991
The motherboard has a built-in Ethernet port.

[toc] | [prev] | [next] | [standalone]

#178015

FromLeslie Rhorer <lrhorer@mygrande.net>
Date2017-02-20 07:40 +0100
Message-ID<tcPND-175-7@gated-at.bofh.it>
In reply to#177991
Backup:/# ip link
1: lo: <LOOPBACK,UP,LOWER_UP> mtu 65536 qdisc noqueue state UNKNOWN mode DEFAULT group default 
    link/loopback 00:00:00:00:00:00 brd 00:00:00:00:00:00
2: eth2: <BROADCAST,MULTICAST,UP,LOWER_UP> mtu 1500 qdisc pfifo_fast state UP mode DEFAULT group default qlen 1000
    link/ether 50:46:5d:65:15:9c brd ff:ff:ff:ff:ff:ff
3: eth0: <BROADCAST,MULTICAST> mtu 1500 qdisc noop portid 086266a14051 state DOWN mode DEFAULT group default qlen 1000
    link/ether 08:62:66:a1:40:51 brd ff:ff:ff:ff:ff:ff


Also:

Backup:/# ifconfig -a
eth0      Link encap:Ethernet  HWaddr 08:62:66:a1:40:51  
          inet addr:192.168.1.91  Bcast:192.168.1.255  Mask:255.255.255.0
          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)
          Interrupt:36 Memory:d3000000-d37fffff 

eth2      Link encap:Ethernet  HWaddr 50:46:5d:65:15:9c  
          inet addr:192.168.1.51  Bcast:192.168.1.255  Mask:255.255.255.0
          inet6 addr: fe80::5246:5dff:fe65:159c/64 Scope:Link
          UP BROADCAST RUNNING MULTICAST  MTU:1500  Metric:1
          RX packets:47553 errors:0 dropped:2 overruns:0 frame:0
          TX packets:272930 errors:0 dropped:0 overruns:0 carrier:0
          collisions:0 txqueuelen:1000 
          RX bytes:15175818 (14.4 MiB)  TX bytes:392583400 (374.3 MiB)

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:65536  Metric:1
          RX packets:52 errors:0 dropped:0 overruns:0 frame:0
          TX packets:52 errors:0 dropped:0 overruns:0 carrier:0
          collisions:0 txqueuelen:0 
          RX bytes:5802 (5.6 KiB)  TX bytes:5802 (5.6 KiB)

[toc] | [prev] | [next] | [standalone]

#178054

FromLeslie Rhorer <lrhorer@mygrande.net>
Date2017-02-22 00:50 +0100
Message-ID<tdslX-1bG-9@gated-at.bofh.it>
In reply to#177991
It is a stock kernel from the current Debian repository.  The firmware was loaded using `apt-get install firmware-bnx2`.

[toc] | [prev] | [next] | [standalone]

#178056

Fromdeloptes <deloptes@gmail.com>
Date2017-02-22 08:40 +0100
Message-ID<tdzGO-6AS-7@gated-at.bofh.it>
In reply to#178054
Leslie Rhorer wrote:

> It is a stock kernel from the current Debian repository.  The firmware was
> loaded using `apt-get install firmware-bnx2`.

Try to find the firmware that matches - I think the message tells you which
version is required. Compare with what you hahve in /lib/firmware
Here in jessie with my custom kernel I
see /lib/firmware/bnx2x-e1h-5.2.13.0.fw
but you fail with bnx2x/bnx2x-e2-7.8.19.0.fw

This will solve your problem. IF not , try compile custom kernel

regards

[toc] | [prev] | [next] | [standalone]

#178059

FromLeslie Rhorer <lrhorer@mygrande.net>
Date2017-02-22 09:40 +0100
Message-ID<tdACR-7m8-1@gated-at.bofh.it>
In reply to#177991
Well, this seems odd.  I don't see any candidate which looks likely, to me, in /lib/firmware/bnx2:

Backup:/lib/firmware/bnx2# la
total 636
drwxr-xr-x 2 root root   4096 Feb 19 15:20 .
drwxr-xr-x 7 root root   4096 Feb 19 15:20 ..
-rw-r--r-- 1 root root  93172 Jun 15  2014 bnx2-mips-06-5.0.0.j3.fw
-rw-r--r-- 1 root root  92792 Jun 15  2014 bnx2-mips-06-6.2.1.fw
-rw-r--r-- 1 root root  92824 Jun 15  2014 bnx2-mips-06-6.2.3.fw
-rw-r--r-- 1 root root  96504 Jun 15  2014 bnx2-mips-09-5.0.0.j3.fw
-rw-r--r-- 1 root root 103868 Jun 15  2014 bnx2-mips-09-6.2.1a.fw
-rw-r--r-- 1 root root 103904 Jun 15  2014 bnx2-mips-09-6.2.1b.fw
-rw-r--r-- 1 root root   6600 Jun 15  2014 bnx2-rv2p-06-5.0.0.j3.fw
-rw-r--r-- 1 root root   5696 Jun 15  2014 bnx2-rv2p-06-6.0.15.fw
-rw-r--r-- 1 root root   7216 Jun 15  2014 bnx2-rv2p-09-5.0.0.j3.fw
-rw-r--r-- 1 root root   6104 Jun 15  2014 bnx2-rv2p-09-6.0.17.fw
-rw-r--r-- 1 root root   7800 Jun 15  2014 bnx2-rv2p-09ax-5.0.0.j3.fw
-rw-r--r-- 1 root root   6616 Jun 15  2014 bnx2-rv2p-09ax-6.0.17.fw

This is an AMD-64 system.

[toc] | [prev] | [next] | [standalone]

#178080

FromLeslie Rhorer <lrhorer@mygrande.net>
Date2017-02-22 22:10 +0100
Message-ID<tdMkG-7Gh-13@gated-at.bofh.it>
In reply to#177991
I found the issue.  The firmware I needed was bnx2x, not bnx2.

[toc] | [prev] | [next] | [standalone]

#178133

Fromdeloptes <deloptes@gmail.com>
Date2017-02-24 16:50 +0100
Message-ID<teqi6-2bp-9@gated-at.bofh.it>
In reply to#178080
Leslie Rhorer wrote:

> I found the issue.  The firmware I needed was bnx2x, not bnx2.

Amen!

[toc] | [prev] | [standalone]

Back to top | Article view | linux.debian.user

csiph-web