[COLUG] Intel Pro 1000 Problem on Debian

Nan Liu nan.liu at gmail.com
Wed Jul 19 12:54:02 EDT 2006


I'm running debian sarge 3.1 r0 AMD64, and experiencing some problems
with an Intel network card.

The intel cards are Pro/1000 PT Dual port. These are pci express
cards, but intel list them on their website using the standard e1000
drivers which have been working for ages in linux:

http://support.intel.com/support/network/adapter/1000ptdual/
http://downloadfinder.intel.com/scripts-df-external/File_Filter.aspx?Filename=e1000-

lspci sees the cards:

aspdir1:/home/nliu# lspci
...
0000:04:00.0 Ethernet controller: Broadcom Corporation NetXtreme
BCM5721 Gigabit Ethernet PCI Express (rev 11)
0000:05:00.0 Ethernet controller: Intel Corp.: Unknown device 105e (rev 06)
0000:05:00.1 Ethernet controller: Intel Corp.: Unknown device 105e (rev 06)

I force loaded the e1000 via modprobe
aspdir1:/home/nliu# modprobe e1000
aspdir1:/home/nliu# lsmod
Module                  Size  Used by
e1000                  78340  0
udf                    77064  1
...

dmesg only sees the nforce and broadcom network card:
aspdir1:/home/nliu# dmesg | grep eth
tg3: tg3_request_firmware (eth%d): Couldn't get firmware "tg3/tso-1.4.0".
tg3: eth%d: Firmware "tg3/tso-1.4.0" not loaded; continuing without TSO.
eth0: Tigon3 [partno(BCM95721) rev 4101 PHY(5750)]
(PCIX:100MHz:32-bit) 10/100/1000BaseT Ethernet 00:e0:81:5c:b4:0d
eth0: RXcsums[1] LinkChgREG[0] MIirq[0] ASF[1] Split[0] WireSpeed[1] TSOcap[0]
forcedeth.c: Reverse Engineered nForce ethernet driver. Version 0.29.
eth1: forcedeth.c: subsystem: 0108e:5348 bound to 0000:00:0a.0
tg3: eth0: Link is up at 1000 Mbps, full duplex.
tg3: eth0: Flow control is off for TX and off for RX.
eth0: no IPv6 routers present
tg3: eth0: Link is down.
tg3: eth0: Link is up at 100 Mbps, full duplex.
tg3: eth0: Flow control is off for TX and off for RX.

ifconfig only sees 2 network cards:

aspdir1:/home/nliu# ifconfig -a
eth0      Link encap:Ethernet  HWaddr 00:E0:81:5C:B4:0D
          inet addr:192.168.2.4  Bcast:192.168.2.255  Mask:255.255.255.0
          inet6 addr: fe80::2e0:81ff:fe5c:b40d/64 Scope:Link
          UP BROADCAST RUNNING MULTICAST  MTU:1500  Metric:1
          RX packets:466 errors:0 dropped:0 overruns:0 frame:0
          TX packets:400 errors:0 dropped:0 overruns:0 carrier:0
          collisions:0 txqueuelen:1000
          RX bytes:369175 (360.5 KiB)  TX bytes:48639 (47.4 KiB)
          Interrupt:5

eth1      Link encap:Ethernet  HWaddr 00:E0:81:5C:B4:0C
          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:11 Base address:0x9000

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:26 errors:0 dropped:0 overruns:0 frame:0
          TX packets:26 errors:0 dropped:0 overruns:0 carrier:0
          collisions:0 txqueuelen:0
          RX bytes:3594 (3.5 KiB)  TX bytes:3594 (3.5 KiB)

sit0      Link encap:IPv6-in-IPv4
          NOARP  MTU:1480  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:0
          RX bytes:0 (0.0 b)  TX bytes:0 (0.0 b)

Any suggestions? Am I missing anything obvious?

Thanks,

Nan


More information about the colug432 mailing list