Very Computer

Hi again,

I'm still stymied.  I can't get my linux box to ping to a WinNT box, or
vice versa.

I tried some different things today and this is what I found out.

A quick review.
After bootup, I ran "dmesg | grep eth".  That told me that the card had
been set up
with IRQ10, IO = 0xf800 etc, and it also said that I had a 100Mbit link
established
between the two machines.
Then I run ifconfig and it tells me the same things as far as IRQ and
IO.  It also
tells me that eth0 is UP as well as IP address and mask etc.

Here's where things fall apart.
When I ping from NT to Linux: (these transfers time out on the NT box)

After that, when I do an ifconfig, the RX count always stays at zero.
Then, I looked in /proc/interrupts and the interrupt count for my NIC is
also at zero.
My NIC (a Netgear FA312) is using IRQ10 according to ifconfig and
/proc/interrupts.

What would keep the interrupt count from incrementing?   Is it possible
that this
interrupt is masked?
If so, how do I enable it?  A BIOS setting? A linux setting?

Could a module problem prevent the IRQ count from incrementing?

Thanks a lot,
Jon Rook

Quote:>I'm still stymied.  I can't get my linux box to ping to a WinNT box, or
>vice versa.

    both ping themselves? Have you checked cabling, IP addresses,
masks and routes? Do you have firewalling rules blocking the ICMP
traffic? Check if the card really has configuration (/sbin/ifconfig, NT
has ipconfig - I guess).

Quote:>Here's where things fall apart.
>When I ping from NT to Linux: (these transfers time out on the NT box)

    This works: NT to linux ping?

Quote:>After that, when I do an ifconfig, the RX count always stays at zero.
>Then, I looked in /proc/interrupts and the interrupt count for my NIC is
>also at zero.
>My NIC (a Netgear FA312) is using IRQ10 according to ifconfig and
>/proc/interrupts.

>What would keep the interrupt count from incrementing?   Is it possible
>that this
>interrupt is masked?
>If so, how do I enable it?  A BIOS setting? A linux setting?

>Could a module problem prevent the IRQ count from incrementing?

    If the network is not up(?)

    I think this needs more log from your side. Change the ip addresses
if you do not wish to reveal them here.

    timo

Hi!,

Quote:> Hi again,

> I'm still stymied.  I can't get my linux box to ping to a WinNT box, or
> vice versa.

> I tried some different things today and this is what I found out.

> A quick review.
> After bootup, I ran "dmesg | grep eth".  That told me that the card had
> been set up with IRQ10, IO = 0xf800 etc, and it also said that I had a
> 100Mbit link established between the two machines.

> Then I run ifconfig and it tells me the same things as far as IRQ and
> IO.  It also tells me that eth0 is UP as well as IP address and mask etc.

> Here's where things fall apart.
> When I ping from NT to Linux: (these transfers time out on the NT box)

> After that, when I do an ifconfig, the RX count always stays at zero.
> Then, I looked in /proc/interrupts and the interrupt count for my NIC is
> also at zero. My NIC (a Netgear FA312) is using IRQ10 according to ifconfig
> and /proc/interrupts.

> What would keep the interrupt count from incrementing?   Is it possible
> that this interrupt is masked?
> If so, how do I enable it?  A BIOS setting? A linux setting?

Does the /proc/interrupts suggest that anything else is using the same IRQ as
well ?

How are the two machines linked to one another.  Are they connected directly
to one another using a "cross-over" cable or are they connected through a hub
?

See ya

Dean Thompson

--
+____________________________+____________________________________________+

| Bach. Computing (Hons)     | ICQ     - 45191180                         |
| PhD Student                | Office  - <Off-Campus>                     |
| School Comp.Sci & Soft.Eng | Phone   - +61 3 9903 2787 (Gen. Office)    |
| MONASH (Caulfield Campus)  | Fax     - +61 3 9903 1077                  |
| Melbourne, Australia       |                                            |
+----------------------------+--------------------------------------------+

Quote:> > Hi again,

> > I'm still stymied.  I can't get my linux box to ping to a WinNT box, or
> > vice versa.

> > I tried some different things today and this is what I found out.

> > A quick review.
> > After bootup, I ran "dmesg | grep eth".  That told me that the card had
> > been set up with IRQ10, IO = 0xf800 etc, and it also said that I had a
> > 100Mbit link established between the two machines.

> > Then I run ifconfig and it tells me the same things as far as IRQ and
> > IO.  It also tells me that eth0 is UP as well as IP address and mask etc.

> > Here's where things fall apart.
> > When I ping from NT to Linux: (these transfers time out on the NT box)

> > After that, when I do an ifconfig, the RX count always stays at zero.
> > Then, I looked in /proc/interrupts and the interrupt count for my NIC is
> > also at zero. My NIC (a Netgear FA312) is using IRQ10 according to ifconfig
> > and /proc/interrupts.

> > What would keep the interrupt count from incrementing?   Is it possible
> > that this interrupt is masked?
> > If so, how do I enable it?  A BIOS setting? A linux setting?

> Does the /proc/interrupts suggest that anything else is using the same IRQ as
> well ?

> How are the two machines linked to one another.  Are they connected directly
> to one another using a "cross-over" cable or are they connected through a hub
> ?

> See ya

> Dean Thompson

Thanks for your reply,

No, /proc/interupts only seems to indicate that eth0 is using that IRQ.

The two machines are linked by a cross-over cable that I have verified
using the same NT box and another machine.

I don't understand why the interrupt count wouldn't increment on
received packets.  I "know" they are received because I can see the
activity LED light up when I ping from the NT box to linux.  
Is there a way to mask (or disable) IRQs?  If so, how do I re-enable?

Thanks,
Jon Rook

I responded in yer most recent post.

LC