[WBEL-users] Re: Trouble getting Intel Pro 100M NIC working

Randy Kelsoe randykel@swbell.net
Wed, 10 Nov 2004 16:39:07 -0600


Michael St. Laurent wrote:

>>What do you see if you do a 'lspci  |grep -i ether'?
>>    
>>
>
>03:09.0 Ethernet controller: Intel Corp.: unknown device 1064 (rev03)
>_______________________________________________
>  
>
Interesting. My Whitebox machines do not have an Intel Controller, but 
my Fedora Core 2 machine does, and here is the excerpt from an 'lspci -v':

01:08.0 Ethernet controller: Intel Corp. 82557/8/9 [Ethernet Pro 100] 
(rev 10)
        Subsystem: Intel Corp.: Unknown device 0070
        Flags: bus master, medium devsel, latency 32, IRQ 10
        Memory at eb026000 (32-bit, non-prefetchable)
        I/O ports at 9000 [size=64]
        Memory at eb000000 (32-bit, non-prefetchable) [size=128K]
        Capabilities: [dc] Power Management version 2
 
Have you tried a 'modprobe e100' to see what happens? You might also try 
running kudzu (service kudzu start) to see if it finds anything.

There are some diags with instructions that may help:

http://www.scyld.com/ethercard_diag.html#pci-diags

You may have a bad card/chipset for your NIC. You said that this is a 
built in NIC? Is it a PCI card, or is it integrated on your motherboard? 
If it is integrated on your mobo, then check your BIOS settings, though 
I don't think that will help. You might also try turning the NIC off in 
BIOS, rebooting, then re-enabling it in BIOS and reboot again to see if 
kudzu detects it.

One more thing to look at is the /proc/interrupts to see if it is 
sharing an interrupt with something else. If it is sharing an interrupt 
with something like a usb controller, rmmod the usb driver, and try a 
'modprobe e100'.