Re: Ether Card

[JY <yyamamot@example.com>]

Hi,
Correct, it is not a basic problem....  
Chequear the readiness is needed in the BIOS/CMOS....  
Also, I think that him but important it is to have patience to detect  
the appropriate values for "i/o =" and  "irq =."  
I got it but takes time, there will be something over there that helps to detect  
the values but quick?  
Thank you Tim for their suggestions.  
The Ethernet-HOWTO also helps.  
Jose Yamamoto

Tim Hurman wrote:
> Hi,
>
> This may not be as basic as yhou think. This look like the erros I see
> sometimes on the realtek 8139 cards. I found that there was an IRQ clash
> between two cards (realteks dont like irq sharing). To get round this I
> had t make sure that the system assigned all IRQs in the bios and tried to
> freee up as many interupts as possible so that the system could choose
> nice values. Also some cards (cheap pci cards) will only accept a certain
> values for thier IRQ. btw, the card had no actual hardware error, however
> it would not send packets, it just overran the buffer and produced an
> error message much like yours. Anyway, it's one thing to look for.
>
> Tim.
>
> On Sat, 7 Jul 2001, JY wrote:
>
> > Hello !
> > I am sorry
> > My problem is a basic problem...
> >
> >
> > 1. Ether card "COREGA"
> > 2. The TX errors not give me connected with an ether card ?
> > This COREGA card is bad ?
> >
> > Here the log's
> >
> > # ifconfig
> >
> > --------
> > eth0 Link encap:Ethernet HWaddr 00:90:FE:03:71:C2
> > inet addr:192.168.1.11 Bcast:192.168.1.255 Mask:255.255.255.0
> > UP BROADCAST RUNNING MULTICAST MTU:1500 Metric:1
> > RX packets:0 errors:0 dropped:0 overruns:0 frame:0
> > TX packets:0 errors:9 dropped:0 overruns:0 carrier:0
> > ^^^^^^^^^
> > what means that ???
> >
> > collisions:0 txqueuelen:100
> > Interrupt:10 Base address:0x1220
> >
> > lo Link encap:Local Loopback
> > inet addr:127.0.0.1 Mask:255.0.0.0
> > UP LOOPBACK RUNNING MTU:3924 Metric:1
> > RX packets:115 errors:0 dropped:0 overruns:0 frame:0
> > TX packets:115 errors:0 dropped:0 overruns:0 carrier:0
> > collisions:0 txqueuelen:0
> >
> > # modprobe
> > # dmesg | tail
> > ---------------
> > eth0: Tx timed out, lost interrupt? TSR=0x3, ISR=0x3, t=761.
> > eth0: Tx timed out, lost interrupt? TSR=0x3, ISR=0x3, t=1000.
> > eth0: Tx timed out, lost interrupt? TSR=0x3, ISR=0x3, t=1000.
> > eth0: Tx timed out, lost interrupt? TSR=0x3, ISR=0x3, t=1000.
> > eth0: Tx timed out, lost interrupt? TSR=0x3, ISR=0x3, t=1000.
> > eth0: Tx timed out, lost interrupt? TSR=0x3, ISR=0x3, t=1000.
> > eth0: Tx timed out, lost interrupt? TSR=0x3, ISR=0x3, t=1000.
> > eth0: Tx timed out, lost interrupt? TSR=0x3, ISR=0x3, t=1000.
> > eth0: Tx timed out, lost interrupt? TSR=0x3, ISR=0x3, t=1500.
> > VFS: Disk change detected on device fd(2,0)
> >
> > # ping 128.168.1.254
> > ---------------------
> >
> > PING 192.168.1.254 (192.168.1.254): 56 data bytes
> >
> > --- 192.168.1.254 ping statistics ---
> > 6 packets transmitted, 0 packets received, 100% packet loss
>