Re: Installation problem with Peabird card

> > Ping from the laptop sometimes says Destination host unreachable, or
> > sometimes does work, but at a very low success rate (90% packets lost):
> >
> > _laptop_# ping 192.168.1.1  
> > PING 192.168.1.1 (192.168.1.1) from 192.168.1.2 : 56(84) bytes of data.
> > 64 bytes from 192.168.1.1: icmp_seq=38 ttl=255 time=213 usec
> > 64 bytes from 192.168.1.1: icmp_seq=51 ttl=255 time=213 usec
> > 64 bytes from 192.168.1.1: icmp_seq=58 ttl=255 time=198 usec
> > --- 192.168.1.1 ping statistics ---
> > 65 packets transmitted, 3 packets received, 95% packet loss
> > round-trip min/avg/max/mdev = 0.198/0.208/0.213/0.007 ms
> >
> > In the meanwhile, ping from the desktop to the laptop gives
> > ``duplicate'' packets, and the success rate is also very low (87% loss)
>
> This indicates that the hardware or driver is resetting the ring
> pointer.
>
> You should be getting driver messages when this happens.  What are they
> reporting?


You mean, on the desktop (where I get these ``duplicate'' packets) ?
I looked at the kernel messages, and I didn't see any complaint (neither 
on the laptop nor on the desktop). However, I tried again exactly the 
same procedure (ie running modprope rtl8139 ; ifconfig ; ping ; on the 
laptop)
Then the message was Destination host unreachable.
Then the _desktop_  was terribly slow for some time. And in the kernel 
messages there was:

  eth0: Too much work at interrupt, IntrStatus=0x0011.
(repeated an almost infinite number of times)

Therefore, I tried to use my other ethernet card on the desktop (eth1) 
and then, it worked.
I am puzzled because this first eth0 did work perfectly with my old 
PCMCIA ethernet card on the laptop.

OK now, It seems to work perfectly. I think I had some bad network 
parameters on the desktop (my second ethernet card had no netmask and no 
IP number [which I thought was the correct thing to do for some 
ppp-on-ethernet], I just changed this, and everything seems OK.

So, really, excuse me if I bothered you because of an unrelated problem, 
although I really would not have guessed where it came from. Of course, 
there still is this module which does not load automatically, but that's 
perfectly OK with me as long as the NIC works.

Thanks very much again for your patience and your very valuable help !

Vincent.