Fwd: [tulip] Asante PNIC II problems

ion ion@info-red.net
Wed Feb 6 14:53:01 2002


>
>Hi
>Im an triying to work whit an AsanteFAST 10/100 PCI Rev. B card
>, have tried under many kernel-driver conbinations whit diferent 
>error msgs but
>same vehaboir, it only works whit autoselect media (options=0) but 
>when some trafic is sent trougth the card error msgs come and i only 
>can get about 2-3Ks, sometimes nothing at all.
>if i do a ifdown eth0, ifup eth0 it works agayn until some data 
>(about 1MB) is trasmited and error msgs come agayn.
>
>Here is the info, the machine is a power mac runing kernel 2.4.18:
>
>Feb  1 14:24:05 localhost kernel: tulip.c:v0.93 11/7/2001  Written 
>by Donald Becker <becker@scyld.com>
>Feb  1 14:24:05 localhost kernel:   http://www.scyld.com/network/tulip.html
>Feb  1 14:24:05 localhost kernel:   The PCI BIOS has not enabled the 
>device at 0/112!  Updating PCI command 0080->0086.
>Feb  1 14:24:05 localhost kernel: eth0: Lite-On LC82C115 PNIC-II rev 
>37 at 0xc788c000, 00:00:94:B6:B3:8E, IRQ 25.
>Feb  1 14:24:06 localhost pumpd[470]: starting at Fri Feb  1 14:24:06 2002
>Feb  1 14:24:06 localhost pumpd[470]: configured interface eth0
>Feb  1 14:24:09 localhost kernel: eth0: Restarted Rx at 87 / 87.
>Feb  1 14:24:09 localhost kernel: eth0: N-Way autonegotiation status 
>45e1d0cc, 10baseT.
>Feb  1 14:24:10 localhost kernel: eth0: Restarted Rx at 119 / 119.
>Feb  1 14:24:11 localhost kernel: eth0: Restarted Rx at 151 / 151.
>Feb  1 14:24:12 localhost kernel: eth0: Restarted Rx at 183 / 183.
>Feb  1 14:24:14 localhost kernel: eth0: Restarted Rx at 215 / 215.
>Feb  1 14:24:15 localhost kernel: eth0: Restarted Rx at 248 / 248.
>and error msgs continue until i put it down
>
>i think that N-Way is not working good because the swich is 
>reporting 100MB FDX
>
>i have noted in the card leds (link, FDX, 100MB, ACT) with the tulip 
>driver that  the FDX led blinks like the ACT one. it is conected to 
>a 10/100 swich and it reports 100MB FDX. Under mac/os or windows the 
>card leds work normally so i think is a driver problem.
>
>triying now tulip-diag to get more info on whats hapening in the 
>card, any help whould be apreciated
>
>Thanks
>Ion
>