Belkin F5D7010 ver 7

[gnelly]

UGHHH!!!
I updated to Feisty and I still can't seem to get this friggin' wireless card working!
This is THE only thing tanking my total abandonment of windoze!!

This what I get from NDISWRAPPER -l without card inserted;[/i][/b]
net8185 : driver installed

This with card inserted...
pcilib: Cannot open /sys/bus/pci/devices/0000:04:00.0/config
Unable to read the standard header from device 0000:04:00.0
net8185 : driver installed

Any suggestions?

[The Liquidator]

Re: Belkin F5D7010 ver 7

Hmmmm

I have an FSD7010 PCMCIA Wireless card which works perfectly in an old laptop of mine running MDV 2007. IIRC It has the Railink 2500 chip which has native Linux support. Unfortunately I don't know the version number, but if it's the same as mine, you shouldn't even need Ndiswrapper although I appreciate that manufacturers change components more frequently than ....well.

If you boot with the card inserted, go into system settings/network settings. Is the card detected?

Ian

[gnelly]

Re: Belkin F5D7010 ver 7

Thanks Liquidator.
No, the card is not detected. At one point I could see it in the Kinfocenter under PCI, at the very bottom. I know the card works under winbloze.

[gnelly]

Re: Belkin F5D7010 ver 7

Any ideas on how to get this thing goin'?
Thanks.
Man it would be nice to be wireless!

[SheeEttin]

Re: Belkin F5D7010 ver 7

How about "lspci"? It should appear at the bottom here too.
If you don't see it there, then it's not being recognized by the system at all. Try shutting down, then reseating the card.

[sakura1083]

Re: Belkin F5D7010 ver 7

Hi, I'm a total newbie on this and I recently installed Kubuntu on my old Windows XP laptop. I have the F5D7010 Belkin wireless card and I'm able to detect the network (which means I shouldn't need Ndiswrapper, right?) but I'm still unable to connect to Interned. Any Ideas?

[SheeEttin]

Re: Belkin F5D7010 ver 7

If you can see the access point, you shouldn't need ndiswrapper.
There's a kind of routine one should go through when troubleshooting network troubles, to see where the problem lies.
First thing is to ping localhost, to make sure there's nothing really wrong. Then you ping your router, to make sure you can reach it, then something past the router. Whatever doesn't succeed tells you where the problem is.
Anyway, you can skip to the router part. Open up a terminal and say "ping -c4 192.168.1.1", assuming your router's IP address is 192.168.1.1. If that works, try "ping -c4 google.com". If that works, your Internet access should be working fine.