That's pretty much what my ifconfig output looks like. Explorer has caused a general protection fault in module kernel32.dll. I'm sick of Winblows! ----- Original Message ----- From: "Geoff Shang" <gshang@xxxxxxxxx> To: <speakup at braille.uwo.ca> Sent: Saturday, October 05, 2002 6:54 PM Subject: Re: Network card problems > On Sat, 5 Oct 2002, Alex Snow wrote: > > > Nope, that's why I'm starting to think it's a dhcp issue. All it shows is > > the mac address of the adapter and lots of other crap about rx and tx > > packets etc. > > ummm. In my experience, it only shows you the RX and TX packets and stuff > if the interface is actually up and running, which suggests that it's > actually working. I might be wrong though, it's awhile since I've seen > ifconfig on a device that's not working. > > The output of a working interface should look like this: > > eth0 Link encap:Ethernet HWaddr 00:20:18:3D:09:B3 > inet addr:10.2.0.1 Bcast:10.2.0.255 Mask:255.255.0.0 > UP BROADCAST RUNNING MULTICAST MTU:1500 Metric:1 > RX packets:373766 errors:0 dropped:18 overruns:0 frame:6 > TX packets:369948 errors:0 dropped:0 overruns:0 carrier:0 > collisions:981 txqueuelen:100 > Interrupt:11 Base address:0x6100 > > Perhaps, if possible, you could send us your ifconfig output. If the link > light is coming on for a short spell during boot-up, perhaps listen to the > boot sequence to see what's happening. The relevant bit is not likely to > be in dmesg but you could look there anyway just in case. > > Geoff. > > > > _______________________________________________ > Speakup mailing list > Speakup at braille.uwo.ca > http://speech.braille.uwo.ca/mailman/listinfo/speakup >
