Leann,
Sorry for being late to respond but private matters kept me from answering 
earlier.
I've now confirmed that the e1000e.ko shipping with Ubuntu 8.04 Hardy *DOESN'T* 
work for me, whereas the latest driver from e1000.sf.net does.
Log excerpt:

May 18 10:41:10 ubuntu-ws kernel: [  348.097371] e1000e: Intel(R) PRO/1000 
Network Driver - 0.2.0
May 18 10:41:10 ubuntu-ws kernel: [  348.097378] e1000e: Copyright (c) 
1999-2007 Intel Corporation.

This is all that will be in the logs after loading the e1000e.ko shipped
with Ubuntu. After compiling version 0.2.9.5 from e1000.sf.net and
manually loading the new kernel module, the log looks like this:

May 18 10:45:29 ubuntu-ws kernel: [  606.857687] e1000e: Intel(R) PRO/1000 
Network Driver - 0.2.9.5
May 18 10:45:29 ubuntu-ws kernel: [  606.857693] e1000e: Copyright (c) 
1999-2008 Intel Corporation.
May 18 10:45:29 ubuntu-ws kernel: [  606.857789] ACPI: PCI Interrupt 
0000:03:00.0[A] -> GSI 28 (level, low) -> IRQ 26
May 18 10:45:29 ubuntu-ws kernel: [  607.034355] 0000:03:00.0: eth0: (PCI 
Express:2.5GB/s:Width x1) 00:1b:21:00:9e:f5
May 18 10:45:29 ubuntu-ws kernel: [  607.034361] 0000:03:00.0: eth0: Intel(R) 
PRO/1000 Network Connection
May 18 10:45:29 ubuntu-ws kernel: [  607.034441] 0000:03:00.0: eth0: MAC: 1, 
PHY: 4, PBA No: d50854-003
May 18 10:45:29 ubuntu-ws kernel: [  607.238827] 0000:03:00.0: eth0: MSI 
interrupt test failed!
May 18 10:45:29 ubuntu-ws kernel: [  607.238965] 0000:03:00.0: eth0: MSI 
interrupt test failed, using legacy interrupt.
May 18 10:45:29 ubuntu-ws kernel: [  607.242007] ADDRCONF(NETDEV_UP): eth0: 
link is not ready
May 18 10:45:32 ubuntu-ws kernel: [  610.070675] 0000:03:00.0: eth0: Link is Up 
1000 Mbps Full Duplex, Flow Control: RX/TX
May 18 10:45:32 ubuntu-ws kernel: [  610.072973] ADDRCONF(NETDEV_CHANGE): eth0: 
link becomes ready

My best guess is that the e1000e.ko version 0.2.0 doesn't know my card.

-- 
e1000 driver loaded for PCI 8086:10b9 instead of e1000e
https://bugs.launchpad.net/bugs/222831
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.

-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs

Reply via email to