Re: Netgear FA510 trouble
*oops* Small typo sent this message to debian-devel :o)
On Tue, Feb 20, 2001 at 09:55:03PM +0100, Felix E. Klee wrote:
> Hi,
>
> I have trouble getting the Netgear FA510 Cardbus Fast Ethernet Card to
The cardbus version is called the "FA510C."
> work. While "cardctl ident" reports the correct card I cannot ping
> another computer connected via a cross over cable (but it works in W2k).
> I attached some data below.
>
> I appreciate any suggestion,
>
> Felix
>
>
> The data:
>
> > lsmod (after removing the sound card modules)
> tulip_cb 31952 2
> cb_enabler 2504 2 [tulip_cb]
> ppp_deflate 38816 0 (autoclean)
> bsd_comp 3704 0 (autoclean)
> ppp 19712 0 (autoclean) [ppp_deflate bsd_comp]
> slhc 4368 0 (autoclean) [ppp]
> ds 6376 1 [cb_enabler]
> i82365 22348 1
> pcmcia_core 44832 0 [cb_enabler ds i82365]
> nls_cp437 3872 3 (autoclean)
Do you have other cardbus/pcmcia cards working? Do you have any stuff built into your kernel? If neither of those are true, you need to `modprobe yenta_socket` Also, mine works with the normal tulip.o, so you might try building the desktop version of the driver :o)
This is the result on my box:
[xsdg@~]$lsmod
Module Size Used by
nls_cp437 4352 0 (autoclean)
nls_iso8859-1 2832 1 (autoclean)
smbfs 31056 1 (autoclean)
i2c-dev 3712 0
nfsd 66736 8 (autoclean)
tulip 33584 1
adm1021 4640 0
sensors 6112 0 [adm1021]
i2c-piix4 3712 0
i2c-core 12816 0 [i2c-dev adm1021 sensors i2c-piix4]
However, I have all of my cardbus/pcmcia stuff compiled into the kernel. The tulip driver is compiled as a module for the reason stated below.
>
> > cardctl ident
> Socket 0:
> product info: "NETGEAR", "FA510", "Fast Ethernet CardBus Card", "1.00"
> manfid: 0x9513, 0x0081
> function: 6 (network)
> PCI id: 0x1011, 0x0019
I have the same card (functioning), but I don't have this last "PCI id:" field. All other data is the same.
>
> > ifconfig (on the laptop)
> eth0 Link encap:Ethernet HWaddr 00:10:7A:15:B8:E1
> inet addr:192.168.0.5 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:12 dropped:0 overruns:0 carrier:0
> collisions:0 txqueuelen:100
> Interrupt:3 Base address:0x100
As someone stated earlier, I have only seen this occur when I boot up with the card in, however, that only occurs when the driver is built into the kernel. For that reason, I have only the tulip (not tulip_cb) driver compiled as a module.
>
> 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:2126 errors:0 dropped:0 overruns:0 frame:0
> TX packets:2126 errors:0 dropped:0 overruns:0 carrier:0
> collisions:0 txqueuelen:0
>
> > ifconfig (on the connected computer)
> eth0 Link encap:Ethernet HWaddr 00:0A:66:3C:F9:43
> 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:36 errors:0 dropped:0 overruns:0 frame:0
> TX packets:93 errors:0 dropped:0 overruns:0 carrier:0
> collisions:0 txqueuelen:100
> Interrupt:5 Base address:0xb000
>
> 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:14 errors:0 dropped:0 overruns:0 frame:0
> TX packets:14 errors:0 dropped:0 overruns:0 carrier:0
> collisions:0 txqueuelen:0
--xsdg
--
___________________________________________________
/ PROCRASTINATION: Hard Work Often Pays Off After \
\ Time, but Laziness Always Pays Off Now. /
/ http://xsdg.hypermart.net|xsdg@softhome.net \
\___________________________________________________/
--
To UNSUBSCRIBE, email to debian-devel-request@lists.debian.org
with a subject of "unsubscribe". Trouble? Contact listmaster@lists.debian.org
----- End forwarded message -----
--
___________________________________________________
/ PROCRASTINATION: Hard Work Often Pays Off After \
\ Time, but Laziness Always Pays Off Now. /
/ http://xsdg.hypermart.net|xsdg@softhome.net \
\___________________________________________________/
Reply to: