Operating System - Linux
1830481 Members
2651 Online
110005 Solutions
New Discussion

Re: NIC not found - Debian install on Proliant DL380

 
Allemann
New Member

NIC not found - Debian install on Proliant DL380

Hi there,
I am stuck with a small problem and would greatly appreciate it if you could give me a hand. I am currently trying to setup DEBIAN on my server and I am stuck with the network. Got two Broadcom 5700 with NC7781 chipset and I cannot get any module running. Downloaded serveral modules for the broadcom but any of those produced an error while installing. I would hate to switch to another distribution just to get the thing running, tried therefore to install an RTL8139.. but the PCIs are incompatible.

I am really desperate - If anybody solved the problem, I would greatly appreciate any help
Thank you

Pat
2 REPLIES 2
Vitaly Karasik_1
Honored Contributor

Re: NIC not found - Debian install on Proliant DL380

did you try bcm5700? (http://packages.debian.org/unstable/misc/bcm5700-source.html)

It works nice in RH with 2.4 kernels

Vitaly.
Dave Dewar
Trusted Contributor

Re: NIC not found - Debian install on Proliant DL380

hi,

I am not a linux guru I am afraid, however I was setting up an very old vectra with redhat7.3 for use as a firewall/router (my second linux build :-) ) at the weekend and was having similar problems to yourself getting linux to use the three nics I had in the box.

It turned out that my issue was a lack of available irq's. Linux didn't give me any hints in this respect, not where I was looking anyway, but I freed up a couple of irqs by turning off a serial port and mouse and viola, the next boot, it detected the nics and gave me driver install options :-) and then it was just a matter of setting up ip's dhcp options etc.

The odd thing was I spent about about four hours previous to this looking through the proc files, hwconf, dmesg, etc etc and they all said that linux had seen the hardware and allocated resources etc etc, and so I thought it was my ineptness at setting up the ip ranges and editing modules.conf that was the issue.

Cheers,

Dave Dewar