Network Drivers for Redhat 7.2 on DL360 G3

[Oliver Charni]

Hello!

We recently purchased 2 new DL360 G3 with 2 Cpq Gbit NIC's. Problem is that now we installed RedHat 7.2 on these Machines but the Network Interfaces refuse to work. It doesnt even load the appropriate Drive(bcm5700 if im not wrong). When I try an 'insmod bcm5700' it says "No such Device", we also tried the eepro100, e100 and e1000 Drivers which allways worked on our DL380 G2 and G3 Machines. I only had experience on DL380's so far so im rather clueless which are the appropriate Network Drivers for DL360.

[K.C. Chan]

Can you list pci output and dmesg output; I am interested in what the server c as a chipset for your NIC.

[Oliver Charni]

Sorry, but i cant list any output. My only chance to access the server now is plug a monitor and keyboard in which makes it difficult to copy any output...

[K.C. Chan]

O.K, I don't need the whole output. I just want to C you post something like this:
eth0: Broadcom BCM4401 100Base-T found at mem faffe000, IRQ 11, node addr 000bdb97592a
bcm4400: eth0 NIC Link is Up, 100 Mbps full duplex


Then try to do locate "bcm4400"; This should tell you if you have this driver or not.

[Oliver Charni]

OK, I just looked in the Logs and there are no ethxx entries at all. The System doesnt load any Driver for the NIC so there cant be any Messages that the IF is up.

[Kodjo Agbenu · Accepted solution]

Hi,

In fact, the device reports as bcm5700, but the bcm5700 included in standard Linux kernels do not match these NICs.

The proper driver for your gigabit NICs is "tg3", not "bcm5700". You can also consider downloading the source code of the right "bcm5700" from HP web :

ftp://ftp.compaq.com/pub/products/servers/supportsoftware/linux/bcm5700-6.0.2d-1.src.rpm

To recompile it on your machine :

rpm -ivh bcm5700-6.0.2d-1.src.rpm
rpmbuild -bb --target=i686 /usr/src/redhat/SPECS/bcm5700.spec

To install it :

rpm -ivh /usr/src/redhat/RPMS/i686/bcm5700-6.0.2d-1.i686.rpm
depmod -ae


Then you can use bcm5700 as the NIC driver.


To summarize : either tg3 from genuine Red Hat kernel or bcm5700 rebuilt from HP sources.

Good luck.

Kodjo

[Karsten Breivik_1]

I I don't know the DL360 card. However, I see that you report that you tried the driver for the Intel PRO/100 card.

I experienced problems with the PRO/100 cards earlier on a box running RedHat 9.0. There seems it was a bug in the driver or on the card, and it is documented on the net. Not sure if the error was introduced in driver that came with the RH 9.0 distribution - the host used to work with 8.x.

I used this workaround to get the card up temporarily:
- unplugged the network cable
- rebooted the host
- logged in
- plugged in the cable
- ran dhcpcd of ifconfig (don't remember which)

This got the card working. A driver upgrade from redhat fixed my problem permanently.

http://www.scyld.com/network/eepro100.html is another resource

Perhaps this would help for your card as well?

[Oliver Charni]

As suggested it installed the 6.0.2 bcm5700 and now it works fine. thx for the help

[Dave Wade-Stein]

I've followed this thread with interest because I have a similar problem: Proliant DL320 running Redhat 7.2, and the Broadcom tg3 NIC is not recognized.

I downloaded bcm5700-6.0.2d-1.src.rpm as Kodjo Agbenu suggested, and during rpmbuild, I get this error:

/usr/include/linux/modversions.h: #error Modules should never use kernel-headers system headers,
/usr/include/linux/modversions.h: #error but rather headers from an appropriate kernel source package.
/usr/include/linux/modversions.h: #error Change -I/usr/src/linux/include (or similar) to
/usr/include/linux/modversions.h: #error -I/lib/modules/$(uname -r)/build/include
/usr/include/linux/modversions.h: #error to build against the currently-running kernel.

For what it's worth, the gcc line DOES have -I/lib/modules/$(uname -r)/build/include, so I don't understand the complaint.

Thanks,
Dave

[Dave Wade-Stein]

Well, I solved my own problem. Duh, it turns out we did not have kernel source loaded. I assumed the source was loaded when I installed 7.2, and didn't realize I had to specifically request it. I did an upgrade and added the kernel source and now everything works!