On Sun, Mar 25, 2007 at 07:24:25 -0700, Dave Stephenson wrote: [...]
> The network interface is integrated into the Asus M2N-e motherboard > > from lspci: > 00:08.0 Bridge: nVidia Corporation MCP55 Ethernet (rev a2) > > from ifconfig > eth0 Link encap:Ethernet HWaddr 00:18:F3:86:8C:92 > inet addr:192.168.0.7 Bcast:192.168.0.255 Mask: > 255.255.255.0 > UP BROADCAST RUNNING MULTICAST MTU:576 Metric:1 > RX packets:36594 errors:0 dropped:0 overruns:0 frame:0 > TX packets:29243 errors:0 dropped:0 overruns:0 carrier:0 > collisions:0 txqueuelen:1000 > RX bytes:15710931 (14.9 MiB) TX bytes:3214944 (3.0 MiB) > Interrupt:50 Base address:0x4000 > > 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:84 errors:0 dropped:0 overruns:0 frame:0 > TX packets:84 errors:0 dropped:0 overruns:0 carrier:0 > collisions:0 txqueuelen:0 > RX bytes:18472 (18.0 KiB) TX bytes:18472 (18.0 KiB) That looks normal to me. Your card should be supported by the "forcedeth" module. If I understand your previous email correctly then you have high transfer rates on your internal network, so maybe your slow external connection is not a hardware/driver issue. You can nevertheless check if you see any error messages when you run dmesg | grep -i forcedeth directly after boot. Maybe somebody else knows anything more specific about this card. (I changed the subject line to make it more noticeable.) It also cannot hurt if you post the output of /sbin/modinfo forcedeth (This will provide some more info about the driver, its version, etc.) -- Regards, Florian -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]