Re: RTL8139 problems ( final summary )

Chris Knipe (cknipe@beachfront.co.za)
Wed, 8 Dec 1999 23:31:29 +0200


Hi

Having seen this :) and my personal reply to you

I am quite sure to tell you you have a faulty network card... Realtek isnt
the bestest of nics arround there today.... I actually had a card a few
months ago that was able to send at 100% and receive packets at 0% :)

Cheers again
Me

----- Original Message -----
From: Petr Sebor <petr@scssoft.com>
To: <linux-net@vger.rutgers.edu>
Sent: Monday, December 06, 1999 5:12 PM
Subject: RTL8139 problems ( final summary )

>
> I hate replying to my own e-mails and flooding the list, but I have
another
> observations
> I think it is important to share :
>
> I was able to compile rtl8139 driver v1.08 as module ( otherwise I get
> errors )
> so I am now running this bad boy :
> rtl8139.c:v1.08 6/25/99 Donald Becker
> http://cesdis.gsfc.nasa.gov/linux/drivers/rtl8139.html
> eth2: RealTek RTL8139 Fast Ethernet at 0xec00, IRQ 9, 00:00:e8:81:53:54.
>
> Now, when I try to ping the host on the other side, I get this :
>
> root@ns:~$ ping 192.168.1.10
> PING 192.168.1.10 (192.168.1.10) from 192.168.1.1 : 56 data bytes
> 64 bytes from 192.168.1.10: icmp_seq=0 ttl=128 time=0.7 ms
> 64 bytes from 192.168.1.10: icmp_seq=1 ttl=128 time=0.8 ms
> >From ns.pixel (192.168.1.1): Destination Host Unreachable
> >From ns.pixel (192.168.1.1): Destination Host Unreachable
> >From ns.pixel (192.168.1.1): Destination Host Unreachable
>
> ( the successful ping count differs each time, from 1 successful to 12
> successful pings
> so far, since then, the host is always unreachable )
>
> Restarting the eth2 does the trick and gives me a chance to send several
> successful pings again.
> ie. ifconfig eth2 down; ifconfig eth2 192.168.1.1 netmask 255.255.255.0 up
>
> The ifconfig looks quite fine ( not speaking about the errors with the
> eth2 )
> eth2 Link encap:Ethernet HWaddr 00:00:E8:81:53:54
> inet addr:192.168.1.1 Bcast:192.168.1.255 Mask:255.255.255.0
> UP BROADCAST RUNNING MULTICAST MTU:1500 Metric:1
> RX packets:480 errors:135 dropped:0 overruns:119 frame:27
> TX packets:301 errors:0 dropped:0 overruns:0 carrier:0
> collisions:0 txqueuelen:100
> Interrupt:9 Base address:0xec00
>
> I am also randomly bombarded by this kind of messages:
> eth2: Oversized Ethernet frame, status 8000350a!
> eth2: Oversized Ethernet frame, status bbfbf31e!
>
> ( I don't know how to reproduce them, they simply pop up whenever they
> want )
>
> Sigh... Hope this gives somebody an idea ...
>
> Thanks,
> Petr
>
> --
> Petr Sebor
> Technology/Engine Development
> SCS Software [ http://www.scssoft.com ]
>
>
> -
> To unsubscribe from this list: send the line "unsubscribe linux-net" in
> the body of a message to majordomo@vger.rutgers.edu
>

-
To unsubscribe from this list: send the line "unsubscribe linux-net" in
the body of a message to majordomo@vger.rutgers.edu