On Fri, 6 Jun 1997 [EMAIL PROTECTED] 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
^^^^^
:
:ifconfig:
: eth0: Link encap 10Mbps Ethernet HWaddr 00 40 05 17 a9 a7
: inet addr: 128.174.57.79 Bcast 128.174.255.255 Nmask 255.255.0.0
: UP BROADCASTING RUNNING MULTICAST MTU: 1500 Metric: 1
: Rx packets:0 errors: 0 drops: 0 overruns: 0
^^^^^^^^^^^^
: Tx packets:87 errors: 0 drops: 0 overruns: 0
: Interrupt 3 Base Address 0x300
[snip]
I see your NIC is at IRQ 3 ... and if your ethernet is active, and you
say it is, 0 Rx packets means the kernel can't get at your NIC. I will
bet that you have a conflict with a serial port. Try moving the NIC to
IRQ 10 or something, or remove the serial port (this is not always
possible).
Try that and see what you come up with. I think if you move the NIC
card IRQ you will start to receive packets.
btw, removing serial support from the kernel and/or not loading the
serial module is not enough to solve this conflict ... I've had this
problem before.
--
Nathan Norman : Hostmaster CFNI : [EMAIL PROTECTED]
finger [EMAIL PROTECTED] for PGP public key and other stuff
Key fingerprint = CE 03 10 AF 32 81 18 58 9D 32 C2 AB 93 6D C4 72
--
--
TO UNSUBSCRIBE FROM THIS MAILING LIST: e-mail the word "unsubscribe" to
[EMAIL PROTECTED] .
Trouble? e-mail to [EMAIL PROTECTED] .
