On 12/04/2012 02:02 PM, Mike C. wrote: > Reading through the threads I realized this has become somewhat of a > convoluted topic. I wanted to figure out a sure-fire, quick and simple > approach not only for Rich but for myself and others that could be followed > and would help folks determine where the problem might be. > > So here's the method, I've come up with. > > 1. Run the command "ifconfig" from a terminal shell. > It the command results show an "eth" interface with a "HWaddr" then the > OS sees the NIC. Which means the NIC drvier module is loaded. Go to step 5 > * > * > *ifconfig eth0* > *eth0 Link encap:Ethernet HWaddr 00:1c:25:18:3c:78 * > * UP 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:20 Memory:fe000000-fe020000 * > > 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)* > * > * > 3.* *Then run the command "dmesg | grep Network" to get driver information > * > * > *dmesg | grep Network* > *[ 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 :-)
signature.asc
Description: OpenPGP digital signature
_______________________________________________ PLUG mailing list PLUG@lists.pdxlinux.org http://lists.pdxlinux.org/mailman/listinfo/plug