|
I recently purchased a NETGEAR 510c network adapter. The box it was in actually advertises it as "Linux Compatible", which was a delightfull sight to behold in a mainstream retail establishment!
However, I have had been unable to get it to work. The card is detected fine, although there is no entry for it in the pcmcia configuration file, this is not a problem for it shares the same manfid as both the "UMAX250 Fast Ethernet" and the "Ambicom AMB8100 Fast Ethernet", which both also use the tulip_cb driver. The card is detected [syslog output provided below], and then delivers the inevitable error of "eth0: Tx hung, 9 vs. 0. " After this, an attempt to ping a machine on the network [and this is quite strange] -DOES- suceed in at least lighting the activity lights on the hub... tcpdump run on another system demonstrates that the card is sucessfully sending out ARP requests for the desired system, but it fails to be capable of doing anything else, and after about 6 arp requests, the card then fails altogether and must be ejected+inserted to even do that much again. And advice would be greatly appreciated. Is it possible that I just have a bad card and should exchange this one? Or should I abbandon hope of cardbus 10/100 on my laptop? [I'm certainly not about to stop running linux ;) ] For whomever may have any assistance or advice to profer, thank you in advance for your time. --David Brooks
Aug 2 00:13:45 note kernel: Linux PCMCIA Card Services 3.1.18 Aug 2 00:13:45 note kernel: kernel build: 2.2.16 #2 Tue Aug 1 23:28:29 EDT 2000 Aug 2 00:13:45 note kernel: options: [pci] [cardbus] [apm] Aug 2 00:13:45 note kernel: PCI routing table version 1.0 at 0xfd3d0 Aug 2 00:13:45 note kernel: Intel PCIC probe: Aug 2 00:13:45 note kernel: Ricoh RL5C466 rev 02 PCI-to-CardBus at slot 00:13, mem 0xf0000000 Aug 2 00:13:45 note kernel: host opts [0]: [io 7/15/2] [mem 3/6/2] [no pci irq] [lat 32/176] [bus 32/34] Aug 2 00:13:45 note kernel: host opts [1]: [io 7/15/2] [mem 3/6/2] [no pci irq] [lat 32/176] [bus 35/37] Aug 2 00:13:45 note kernel: ISA irqs (default) = 3,4,5,7,9,10,11,15 polling interval = 1000 ms Aug 2 00:13:46 note cardmgr[601]: starting, version is 3.1.18 Aug 2 00:13:46 note cardmgr[601]: watching 2 sockets Aug 2 00:13:46 note kernel: cs: IO port probe 0x1000-0x17ff: clean. Aug 2 00:13:46 note kernel: cs: IO port probe 0x0100-0x04ff: excluding 0x220-0x22f 0x2a0-0x2af 0x330-0x337 0x370-0x37f 0x388-0x38f 0x398-0x39f 0x3e0-0x3e7 0x4d0-0x4d7 Aug 2 00:13:46 note kernel: cs: IO port probe 0x0a00-0x0aff: clean. Aug 2 00:14:01 note kernel: cs: cb_alloc(bus 32): vendor 0x1011, device 0x0019 Aug 2 00:14:01 note cardmgr[601]: initializing socket 0 Aug 2 00:14:01 note cardmgr[601]: socket 0: UMAX Technologies UMAX250 Fast Ethernet Aug 2 00:14:02 note cardmgr[601]: executing: 'modprobe cb_enabler' Aug 2 00:14:02 note cardmgr[601]: executing: 'modprobe tulip_cb' Aug 2 00:14:02 note kernel: cs: cb_config(bus 32) Aug 2 00:14:02 note kernel: fn 0 bar 1: io 0x100-0x17f Aug 2 00:14:02 note kernel: fn 0 bar 2: mem 0x600c0000-0x600c03ff Aug 2 00:14:02 note kernel: fn 0 rom: mem 0x60080000-0x600bffff Aug 2 00:14:02 note kernel: irq 3 Aug 2 00:14:02 note kernel: tulip_attach(device 20:00.0) Aug 2 00:14:02 note kernel: tulip.c:v0.91g-ppc 7/16/99 becker@cesdis.gsfc.nasa.gov (modified by danilo@cs.uni-magdeburg.de for XIRCOM CBE, fixed by Doug Ledford) Aug 2 00:14:02 note kernel: eth0: Digital DS21143 Tulip rev 65 at 0x100, 00:10:7A:15:CB:26, IRQ 3. Aug 2 00:14:02 note kernel: eth0: EEPROM default media type Autosense. Aug 2 00:14:02 note kernel: eth0: Index #0 - Media MII (#11) described by a 21142 MII PHY (3) block. Aug 2 00:14:02 note kernel: eth0: MII transceiver #1 config 1000 status 7849 advertising 01e1. Aug 2 00:14:02 note cardmgr[601]: executing: './network start eth0' Aug 2 00:14:24 note kernel: eth0: Setting full-duplex based on MII#1 link partner capability of 45e1. Aug 2 00:14:24 note kernel: eth0: Tx hung, 9 vs. 0.
|
Messages