On Jun 6, cheng@fourier.csl.uiuc.edu wrote
: On Jun 6, Nathan E Norman wrote:
: >
: > ps. Between dmesg, ifconfig, and the proc filesystem you can poke
: > around and get a good idea of what Linux thinks is going on, and how
: > that meshes with what's supposed to be going on.
: >
: Thanks for the suggestions. I check with all these commands.
: Here is the message I get from those programs. They all seems pretty
: well.
:
: dmesg:
: NE*000 ethercard probe at 0x300 : 00 40 05 17 a9 a7
: eth0: NE2000 found at 0x300, using IRQ 3
Sure, that IRQ3 is right? Usually this is used for COM2, isn't it?
Probably you've an interrupt conflict.
Are there any interrupts shown in /proc/interrupts? Are the figures
changing according to expected net traffic? Or according to a connected
mouse/modem or whatever?
: IP address HW type Flags HW address Mask Device
: 128.174.57.65 0x1 0x0 00 00 00 00 00 00 *
The NIC can't find any other NIC. But that's what you know already ;-)
Heiko
--
email : heiko@lotte.sax.de heiko@debian.org heiko@sax.de
pgp : A1 7D F6 7B 69 73 48 35 E1 DE 21 A7 A8 9A 77 92
finger: heiko@sax.sax.de heiko@debian.org
Attachment:
pgpQtnx2c9t6_.pgp
Description: PGP signature