Belkin Wireless PCMCIA F5D7010 v. 5000 Driver

[bobbear43]

OK, disabled firewall.
Same results.
vasm can connect.
dhcpcd does not connect.

How do I confirm that the firewall is turned off?

Also my wireless router uses 192.168.2.x
But I see how to configure that.

[bigpaws]

As root iptables -L

Bigpaws

[bobbear43]

Gave up on using the ndiswrapper approach.
Got instructions from developer on compiling madwifi driver.
Error was using extract utility and not tar to extract files.
make and make install ran correctly except in install procedure modprobe ath_pci wrote "eth0 ath_pci" in modprobe.conf instead of "ath0 ath_pci" -- corrected
Card is seen on boot .... green light on card ... but still no connection with dhcpcd.
VASM connects as before.
Posting output of install procedure in madwifi forum for assistance.
Will post results.

[bobbear43]

In case any assistance here.....
Continuing to follow instructions in http://madwifi.org/wiki/UserDocs/FirstTimeHowTo

make install ran with no errors

modprobe ath_pci --- no errors returned however wrote "eth0 ath_pci" in modprobe.conf instead of "ath0 ath_pci" --- corrected

vector:/~
root:# wlanconfig ath0 create wlandev wifi0 wlanmode sta
wlanconfig: ioctl: Input/output error
vector:/~

root:# iwconfig
lo no wireless extensions.
wifi0 no wireless extensions.
ath0 IEEE 802.11g ESSID:"Roberto"
Mode:Managed Frequency:2.437 GHz Access Point: Not-Associated
Bit Rate:0 kb/s Tx-Power:11 dBm Sensitivity=1/1
Retry:off RTS thr:off Fragment thr:off
Encryption key:off
Power Management:off
Link Quality=0/70 Signal level=-256 dBm Noise level=-256 dBm
Rx invalid nwid:0 Rx invalid crypt:0 Rx invalid frag:0
Tx excessive retries:0 Invalid misc:0 Missed beacon:0
vector:/~

root:# ifconfig ath0 up
vector:/~

root:# modprobe wlan_scan_sta
vector:/~

root:# wlanconfig ath0 list scan
vector:/~

root:# iwlist ath0 scan
ath0 No scan results

vector:/~
root:# iwconfig ath0 essid "Roberto"
vector:/~

root:# iwlist ath0 scan
ath0 No scan results

vector:/~
root:# dhcpcd -t 60 -d ath0
dhcpcd: MAC address = 00:11:50:70:5b:38
vector:/~

The last entry means that no communication occurred with the wireless router. Firewall in Linux is turned off. Router has no WEP/WPA and mac address filtering is turned off for this test.

Why Does VASM report that it connects with the router but dhcpcd does not?

[bobbear43]

Working in the madwifi forum with the developer who apparently wrote madwifi, I have come to the same state as the ndiswrapper approach. The developer told me that an access point must be configured with ath0, however the commands
iwconfig ath0 ap xxxxxx with the mac address of the router
or iwconfig ath0 ap any
both result in iwconfig showing Access Point "Not-Associated"
The help for iwconfig shows [ap {N|off|auto}] --- using auto results in Access Point "Invalid"
This card worked in the laptop when it ran Windoze. It also works currently in another Windoze latop I have.

Earlier post said iptables -L would tell me whether the firewall was working, but I see nothing in the output that tells me that. I do see the IP specification which was changed to 192.168.2.0 to match the IPs used by the router.

Again, VASM shows connecting ath0 to the router. Is this a valid result? dhcpcd continues not to connect.

[easuter]

bobbear43, the problems you are having resemble something very similar I experienced with an USB dongle equipped with the Ralink RT2570 chip.

The card used to work fine with kernel 2.4, but I never got it to work with kernel 2.6. iwconfig reported that it could see the SSID, the frequency was correct, but it was not able to associate to the AP no matter what. It also had a weird 0/70 signal strength.

I'm going to compile kernel 2.6.23 and see if its new wireless stack fixes the problem I was having. If it does, then it  might fix yours too (and I'll make a kernel package available for you in the repository).

[bobbear43]

same symptoms ..... 
pls tell me how to compile a kernel when we get to that ..... i have to admit that a LONG time ago i wrote hardware drivers in UNIX ..... but have forgotten many of the basics

[rbistolfi]

The new wiki has a great howto about kernel compiling:

http://vectorlinux.com/wiki/doku.php?id=howtos:kernel

[GrannyGeek]

I'm going to compile kernel 2.6.23 and see if its new wireless stack fixes the problem I was having.

Please let us now if the 2.6.23 kernel fixes the problem. If it does, I might try it on my recalcitrant laptop, although I've officially given up.
--GrannyGeek

[easuter]

I'm going to compile kernel 2.6.23 and see if its new wireless stack fixes the problem I was having.

Please let us now if the 2.6.23 kernel fixes the problem. If it does, I might try it on my recalcitrant laptop, although I've officially given up.
--GrannyGeek

Sure.
Although, it only *might* fix the problem. Lots of drivers haven't been ported to the new wireless stack yet, the Ralink 2x00 ones probably have, maybe Atheros too, but I'll only know that in a couple of hours from now.

[easuter]

Nope, none of my cards' drivers would work with the new wireless stack. 

I'll keep investigating this and see what I can come up with.

[GrannyGeek]

Nope, none of my cards' drivers would work with the new wireless stack. 

Alas.

Keep us posted if you find anything that works.
--GrannyGeek

[bobbear43]

I have searched all over for every reference for this particular card with any Linux. Not a single report that it is workiing. I think it is time to end this quest and try another card.

My sincere thanks to all who tried to help! 

[rbistolfi]

It is a shame that linux users still have to suffer this kind of things, I hope the release of the ati video cards specifications will be followed by others, as the wifi manufacturers. I am sorry you cant get it to work, bobbear43. I wish you better luck with the next challenge.