Re: Diver Problem!!!
Michael Esser <[email protected]> Wed, 14 Jan 2004 16:49:15 +0100
| Newsgroups | gmane.linux.drivers.tulip.general |
|---|---|
| Message-ID | <[email protected]> |
Hallo, well, its long time ago since the original message was sent. But i have a similiar problem, having a noname NIC-in-Hub pci card with 4 ports, with an ASIX A88141 chip. I'am trying to run this card with 2-4-24 kernel, using the drivers on the ftp server (v0.97 7/22/2003). Insmod 'pci-scan' and 'tulip' works, but no ping to another computer works... Were there any solutions to this problem - do the card work now? (aeehh, well 3 years later...) PS: what does it mean, having "... Transmit stopped, Receive stopped. The Rx process state is 'Stopped'. The Tx process state is 'Stopped'. ..." in the tulip-diag output? Is this good/bad or doesn't matter? Best regards, Michael Esser Jens Flucke wrote: >Dear Mr. Becker, >at first i want to say thanks to you for your work an tulip chip sets. But i >have the problem that my card does not works. I am using Suse Linux 7.0 with >Kernel 2.2.16. It is possible via "yast" to selcet the tulip chip for my >network card. But it does not work. So i hope that you can help me, because i >am not a programmer to solve the problem by myself. I hope that there are >enough informations for you to solve the problem. > >The PC-Card (PCI) is a 4 Port integrated HUB with the Tulip Chip. The >revision is A4. There is a label on it "NEF-4C". In the middle the is a great >IC with a fan on it. Near to this IC there is a second one wich is labeld >"ASIX AX 88141P 9904 US 1 ECR 56-3" I hope this will help you. > >The kernel give the following information: > >tara kernel: eth0: Transmit timed out, status 00160400, CSR 12 00000101, >resetting > >But with the command "ifconfig" you can the the eth0 device: > >eth0 Link encap:Ethernet HWaddr 00:50:00:00:0C:46 > inet addr:192.168.0.1 Bcast:192.168.0.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:25 dropped:0 overruns:0 carrier:0 > collisions:0 txqueuelen:100 > Interrupt:11 Base address:0x9800 > >Also a ping on the networkdevice workes fine: > >bash-2.04# ping tara >PING tara.somephreax.all (192.168.0.1): 56 data bytes >64 bytes from 192.168.0.1: icmp_seq=0 ttl=255 time=0.271 ms >64 bytes from 192.168.0.1: icmp_seq=1 ttl=255 time=0.173 ms >64 bytes from 192.168.0.1: icmp_seq=2 ttl=255 time=0.160 ms >64 bytes from 192.168.0.1: icmp_seq=3 ttl=255 time=0.157 ms >64 bytes from 192.168.0.1: icmp_seq=4 ttl=255 time=0.160 ms >--- tara.somephreax.all ping statistics --- >5 packets transmitted, 5 packets received, 0% packet loss >round-trip min/avg/max = 0.157/0.184/0.271 ms >bash-2.04# ping 192.168.0.1 >PING 192.168.0.1 (192.168.0.1): 56 data bytes >64 bytes from 192.168.0.1: icmp_seq=0 ttl=255 time=0.221 ms >64 bytes from 192.168.0.1: icmp_seq=1 ttl=255 time=0.173 ms >64 bytes from 192.168.0.1: icmp_seq=2 ttl=255 time=0.161 ms >64 bytes from 192.168.0.1: icmp_seq=3 ttl=255 time=0.167 ms >--- 192.168.0.1 ping statistics --- >4 packets transmitted, 4 packets received, 0% packet loss >round-trip min/avg/max = 0.161/0.180/0.221 ms > >With your diagnostics Programm you can see the following outputs: > >bash-2.04# ./tulip-diag >tulip-diag.c:v2.03 7/31/2000 Donald Becker ([email protected]) >http://www.scyld.com/diag/index.html >Index #1: Found a ASIX AX88140 adapter at 0x9800. >Port selection is 10mpbs-serial, half-duplex. >Transmit started, Receive started, half-duplex. >The Rx process state is 'Waiting for packets'. >The Tx process state is 'Reading a Tx descriptor'. >The transmit threshold is 72. >The MAC/filter registers are 00005000 0000460c 80000000 00000000. >Use '-a' or '-aa' to show device registers, >'-e' to show EEPROM contents, -ee for parsed contents, >or '-m' or '-mm' to show MII management registers. > >bash-2.04# ./tulip-diag -aa >bash: ./tulip-diag: Datei oder Verzeichnis nicht gefunden >bash-2.04# /usr/sbin/./tulip-diag -aa >tulip-diag.c:v2.03 7/31/2000 Donald Becker ([email protected]) >http://www.scyld.com/diag/index.html >Index #1: Found a ASIX AX88140 adapter at 0x9800. >* A potential Tulip chip has been found, but it appears to be active. >* Either shutdown the network, or use the '-f' flag to see all values. >Port selection is 10mpbs-serial, half-duplex. >Transmit started, Receive started, half-duplex. >The Rx process state is 'Waiting for packets'. >The Tx process state is 'Reading a Tx descriptor'. >The transmit threshold is 72. >bash-2.04# /usr/sbin/./tulip-diag -e >tulip-diag.c:v2.03 7/31/2000 Donald Becker ([email protected]) >http://www.scyld.com/diag/index.html >Index #1: Found a ASIX AX88140 adapter at 0x9800. >Port selection is 10mpbs-serial, half-duplex. >Transmit started, Receive started, half-duplex. >The Rx process state is 'Waiting for packets'. >The Tx process state is 'Reading a Tx descriptor'. >The transmit threshold is 72. >The MAC/filter registers are 00005000 0000460c 80000000 00000000. >EEPROM size is 6. >PCI Subsystem IDs, vendor 0000, device 0000. >CardBus Information Structure at offset 00000000. >Ethernet MAC Station Address 00:50:00:00:0C:46. >EEPROM transceiver/media description for the ASIX AX88140 chip. >Leaf node at offset 30, default media type 0003 (100baseTx). >CSR12 direction setting bits 0x1f. >1 transceiver description blocks: >21140 Non-MII transceiver for media 3 (100baseTx). >CSR12 control port setting 00, command 0x40 0x8b. >Media detection by looking for a 0 on bit 5 of the CSR12 control port. >bash-2.04# /usr/sbin/./tulip-diag -m >tulip-diag.c:v2.03 7/31/2000 Donald Becker ([email protected]) >http://www.scyld.com/diag/index.html >Index #1: Found a ASIX AX88140 adapter at 0x9800. >Port selection is 10mpbs-serial, half-duplex. >Transmit started, Receive started, half-duplex. >The Rx process state is 'Waiting for packets'. >The Tx process state is 'Reading a Tx descriptor'. >The transmit threshold is 72. >The MAC/filter registers are 00005000 0000460c 80000000 00000000. >No MII transceivers found! > > >May you help me. Whats the Problem? Please excuse, but i am newbie on >networking. Thanks!!! > >For your information. I want to connect directly via LAN to another computer, >using also linux with a realtex ? networkcard. > > >Best regards > >Jens Flucke > > _______________________________________________ tulip mailing list, [email protected] To change to digest mode or unsubscribe visit http://www.scyld.com/mailman/listinfo/tulip