PDA

View Full Version : Netgear FA511 PCMCIA Trouble



Jasper Gnubie
20th June 2004, 08:11 AM
Hey everyone,

I'm a brand gnubie linux user :D and I just installed Fedora Core 2 on my Dell Inspiron 3800 laptop. It's up and running but my Netgear ethernet card isn't working :confused:. As the system starts checking my hardware, I get the message:

"tulip device eth0 does not seem to be present, delaying initialization"

Once it's up and running, I've opened a terminal, switched to root, and issued the command /sbin/cardctl ident, and here's what I get:

product info: "NETGEAR, Inc.", "FA511", "Cardbus Mobile Adapter", "1.00"
manfid: 0x022d, 0x511a
function: 6 (network)

So my card is being recognized, but there are no leds, beeps, or anything going on. Any help would be greatly appreciated. I just want to get this thing up and running so I can start learning.

Thanks,
Jasper

peppix
17th July 2004, 11:49 AM
Hi,
you can try this solution, it seems a bug.
http://bugzilla.redhat.com/bugzilla/show_bug.cgi?id=125015

duplicate of
http://bugzilla.redhat.com/bugzilla/show_bug.cgi?id=123457


Bye
Peppe

neomatrix
7th August 2004, 09:19 AM
Hi All,

I am trying to configure NetGear FA511 on a 600E IBM Thinkpad laptop using the drivers from the Netgear CD.

The card is set up properly.

--When i start the pcmcia service, it gives two high beeps indicating the card is setup properly

The card control gives the followng output

[root@neomatrix redhat6.2]# cardctl ident
Socket 0:
no product info available
Socket 1:
product info: "NETGEAR, Inc.", "FA511", "CardBus Mobile Adapter", "1.00"
manfid: 0x022d, 0x511a
function: 6 (network)

--The text from dmesg is as follows

eth0: tulip_open() irq 11.
eth0: MII link partner 45e1, negotiated 05e1.
eth0: Done tulip_open(), CSR0 fff98000, CSR5 fc124010 CSR6 ff972113.
<7>eth0: Comet link status 786d partner capability 45e1.
eth0: Comet link status 786d partner capability 45e1.
eth0: Comet link status 786d partner capability 45e1.
eth0: Comet link status 786d partner capability 45e1.
eth0: Comet link status 786d partner capability 45e1.
eth0: Comet link status 786d partner capability 45e1.
eth0: Comet link status 786d partner capability 45e1.
eth0: Comet link status 786d partner capability 45e1.
eth0: Comet link status 786d partner capability 45e1.
eth0: Comet link status 786d partner capability 45e1.
eth0: Comet link status 786d partner capability 45e1.
eth0: Comet link status 786d partner capability 45e1.

The above output is given out to dmesg when i successfully ping to the dhcp/nameserver

The ping to the nameserver, happens with long delays and it ultimately stops and then suddenly starts again.

The output of ping is as followshostname and ip removed )
PING ns.xxxx.se () from 10.20.2.51 : 56(84) bytes of data.
64 bytes from ns.xxxx.se (): icmp_seq=0 ttl=64 time=4.7 ms
64 bytes from ns.xxxx.se (): icmp_seq=1 ttl=64 time=4004.3 ms
64 bytes from ns.xxxx.se (): icmp_seq=2 ttl=64 time=3012.5 ms
64 bytes from ns.xxxx.se (): icmp_seq=4 ttl=64 time=6004.7 ms


64 bytes from ns.xxxx.se (): icmp_seq=186 ttl=64 time=0.8 ms
64 bytes from ns.xxxx.se (): icmp_seq=193 ttl=64 time=0.6 ms
From neomatrix.xxxx.se (): Destination Host Unreachable
From neomatrix.xxxx.se (): Destination Host Unreachable
From neomatrix.xxxx.se (): Destination Host Unreachable
From neomatrix.xxxx.se (): Destination Host Unreachable
From neomatrix.xxxx.se (): Destination Host Unreachable
From neomatrix.xxxx.se (): Destination Host Unreachable
64 bytes from ns.xxxx.se (): icmp_seq=254 ttl=64 time=4.3 ms
64 bytes from ns.xxxx.se (): icmp_seq=261 ttl=64 time=33013.1 ms
64 bytes from ns.xxxx.se (): icmp_seq=269 ttl=64 time=25021.4 ms

--Other useful information you would like to see

[root@neomatrix /root]# lsmod
Module Size Used by
tulip_cb 34416 2
cb_enabler 2440 2 [tulip_cb]
ds 6344 2 [cb_enabler]
i82365 21732 2
pcmcia_core 44480 0 [cb_enabler ds i82365]


[root@neomatrix /root]# ifconfig
eth0 Link encap:Ethernet HWaddr 00:10:7A:69:21:BC
inet addr:10.20.2.51 Bcast:10.20.255.255 Mask:255.255.0.0
UP BROADCAST RUNNING MTU:1500 Metric:1
RX packets:1228 errors:0 dropped:0 overruns:0 frame:0
TX packets:1430 errors:0 dropped:0 overruns:0 carrier:0
collisions:0 txqueuelen:100
Interrupt:11 Base address:0x9000

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:234 errors:0 dropped:0 overruns:0 frame:0
TX packets:234 errors:0 dropped:0 overruns:0 carrier:0
collisions:0 txqueuelen:0

-- This is the output from tulip-diag ( a utility taken from the tulip project on sourceforge.net )

[root@neomatrix diag]# ./tulip-diag
tulip-diag.c:v2.06 1/8/2001 Donald Becker (becker@scyld.com)
http://www.scyld.com/diag/index.html
Index #1: Found a ADMtek AL985 Centaur-C adapter at 0xa00.
Comet duplex is reported in the MII status registers.
Transmit started, Receive started, half-duplex.
The Rx process state is 'Waiting for packets'.
The Tx process state is 'Idle'.
The transmit threshold is 128.
Comet MAC address registers 697a1000 ffffbc21
Comet multicast filter 8000000000000000.
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.

[root@neomatrix diag]# ./tulip-diag -a
tulip-diag.c:v2.06 1/8/2001 Donald Becker (becker@scyld.com)
http://www.scyld.com/diag/index.html
Index #1: Found a ADMtek AL985 Centaur-C adapter at 0xa00.
* 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.
ADMtek AL985 Centaur-C chip registers at 0xa00:
0x00: fff98000 ffffffff ffffffff 034e0000 034e0200 fc664010 ff972113 ffffffff
Comet duplex is reported in the MII status registers.
Transmit started, Receive started, half-duplex.
The Rx process state is 'Waiting for packets'.
The Tx process state is 'Idle'.
The transmit threshold is 128.
Comet MAC address registers 697a1000 ffffbc21
Comet multicast filter 8000000000000000.


[root@neomatrix diag]# ./tulip-diag -e
tulip-diag.c:v2.06 1/8/2001 Donald Becker (becker@scyld.com)
http://www.scyld.com/diag/index.html
Index #1: Found a ADMtek AL985 Centaur-C adapter at 0xa00.
Comet duplex is reported in the MII status registers.
Transmit started, Receive started, half-duplex.
The Rx process state is 'Waiting for packets'.
The Tx process state is 'Idle'.
The transmit threshold is 128.
Comet MAC address registers 697a1000 ffffbc21
Comet multicast filter 8000000000000000.
EEPROM 256 words, 8 address bits.
Ethernet MAC Station Address 00:10:7a:69:21:bc.
Default connection type 'Autosense'.
PCI IDs Vendor 1317 Device 1985 Subsystem 1385 511a
PCI min_grant 255 max_latency 255.
CSR18 power-up setting 0xa05c****.


[root@neomatrix diag]# ./tulip-diag -m
tulip-diag.c:v2.06 1/8/2001 Donald Becker (becker@scyld.com)
http://www.scyld.com/diag/index.html
Index #1: Found a ADMtek AL985 Centaur-C adapter at 0xa00.
Comet duplex is reported in the MII status registers.
Transmit started, Receive started, half-duplex.
The Rx process state is 'Waiting for packets'.
The Tx process state is 'Idle'.
The transmit threshold is 128.
Comet MAC address registers 697a1000 ffffbc21
Comet multicast filter 8000000000000000.
MII PHY found at address 1, status 0x786d.
MII PHY found at address 2, status 0x786d.
MII PHY found at address 3, status 0x786d.
MII PHY found at address 4, status 0x786d.


-- /proc files

[root@neomatrix diag]# cat /proc/interrupts
CPU0
0: 195511 XT-PIC timer
1: 9235 XT-PIC keyboard
2: 0 XT-PIC cascade
8: 1 XT-PIC rtc
11: 6614 XT-PIC i82365, eth0
12: 47677 XT-PIC PS/2 Mouse
13: 1 XT-PIC fpu
14: 440178 XT-PIC ide0
15: 4756 XT-PIC ide1
NMI: 0

[root@neomatrix diag]# cat /proc/devices
Character devices:
1 mem
2 pty
3 ttyp
4 ttyS
5 cua
7 vcs
10 misc
29 fb
36 netlink
128 ptm
136 pts
162 raw
254 pcmcia

Block devices:
1 ramdisk
2 fd
3 ide0
9 md
22 ide1



-- Kernel version and other information

root@neomatrix diag]# uname -r
2.2.14-5.0

THE PROBLEM :

Is there any specific reason for the connection to be so intermittent. The card works perfectly fine on Windows 98 .So there is no problem with the hardware.

I have a 100Mpbs connection, I get IP information through dhcp and authentication through MAC address . The mac address adopted by the card is same as the one regitered with the authentication server.

I hope somebody could help me with this ...