> > *[ 1.382194] e1000e: Intel(R) PRO/1000 Network Driver - 1.5.1-k*
> (Really off-topic) but you are running a old version of e1000e, the
> latest is version 2.1.4 :-)
>
>
Ha! Good to know. It's the driver that Ubuntu 12.04 LTS packages.
>
> >
> > root@mannix:/home/mike# ethtool -t eth0 offline
> > The test result is FAIL
> > The test extra info:
> > Register test (offline) 0
> > Eeprom test (offline) 0
> > Interrupt test (offline) 0
> > Loopback test (offline) 0
> > Link test (on/offline) 1
> This self-test is only as good as the driver implementation. Each
> driver is left up to implementing the ethtool self-test command and I
> personally do not know of any wireless driver that does an extensive
> implementation. As far as the Intel wired Ethernet drivers, I know we
> implemented all the tests so that the results are actually helpful.
>
> This is just an FYI, so if you have issues with the self-test of a
> particular card, then it is not ethtool's fault, it is the driver's
> fault. :-)
>
> True. Those test results wee for the e1000e: Intel(R) PRO/1000 Network
Driver - 1.5.1-k and the Intel Corporation 82566MM Gigabit Network
Connection (rev 03)
I just found it confusing that the final test result was FAIL when all the
internal tests passed and the link test failed. I ran the test in offline
mode with no eth cable connected and I assumed the link test wouldn't be
tested in the offline mode. Ethtool ran the same tests and returned the
same results I the same results in online mode.
> 2. If you don't see any "eth" interfaces listed then run the command
"dmesg
> > | grep Ethernet" to get information on the physical card
> >
> > *lspci | grep Ethernet*
> > *00:19.0 Ethernet controller: Intel Corporation 82566MM Gigabit Network
> > Connection (rev 03)*
> > *
> > *
> >
> Things can be simpler here. ifconfig won't list devices that have not
> been up at least once.
> replace it with 'the command ip link". I haven't tested recently but I
> also believe that any ethernet
> devices known by the kernel via pci bus even without a configured driver
> will be identified.
>
>
Ah, I didn't know that about ifconfig. I removed the e1000e driver with
modprobe -r, verified it wasn't loaded with lsmod and ip link didn't list
itl
ip link
1: lo: <LOOPBACK,UP,LOWER_UP> mtu 16436 qdisc noqueue state UNKNOWN
link/loopback 00:00:00:00:00:00 brd 00:00:00:00:00:00
3: wlan0: <BROADCAST,MULTICAST,UP,LOWER_UP> mtu 1400 qdisc mq state UP qlen
1000
link/ether 00:1d:e0:00:89:53 brd ff:ff:ff:ff:ff:ff
So, we're still at the age old, thorny juncture of what's the quickest and
easiest way to determine if the source of one's networking problem is the
driver or the NIC. Based on my own experiences working as a Network
Engineer and Linux user for many years, I always look at the driver and net
config first as I've found a greater probability the problem is there than
with the hardware.
_______________________________________________
PLUG mailing list
[email protected]
http://lists.pdxlinux.org/mailman/listinfo/plug
