Problems with Belkin F5D7010 PCMCIA 1799:701f while trying WPA connection
Hi,
I want to get a wpa-connection running with a belkin F5D7010 PCMCIA card (pci-id: 1799:701f).
I tryed every kernel from 2.6.22 (self compiled, but wlan and WPA running well with other cards). Now I use 2.6.27-rc2
lspci -vvvv
06:00.0 Ethernet controller: Belkin Unknown device 701f (rev 20)
Subsystem: Belkin Unknown device 701f
Control: I/O+ Mem+ BusMaster+ SpecCycle- MemWINV+ VGASnoop-
ParErr- Stepping- SERR- FastB2B-
Status: Cap+ 66MHz- UDF- FastB2B+ ParErr- DEVSEL=medium
Quoted 1 line
TAbort- <TAbort- <MAbort- >SERR- <PERR+
Latency: 64 (8000ns min, 16000ns max), Cache Line Size: 32 bytes
Interrupt: pin A routed to IRQ 9
Region 0: I/O ports at 1800 [size=256]
Region 1: Memory at 2c000000 (32-bit, non-prefetchable)[size=1K]
Capabilities: [50] Power Management version 2
Flags: PMEClk- DSI- D1+ D2+ AuxCurrent=375mAPME(D0-,D1+,D2+,D3hot+,D3cold+)
Status: D0 PME-Enable- DSel=0 DScale=0 PME-
Capabilities: [60] Vital Product Data
dmesg while plug-in of the card:
pccard: CardBus card inserted into slot 1
pci 0000:06:00.0: supports D1
pci 0000:06:00.0: supports D2
pci 0000:06:00.0: PME# supported from D1 D2 D3hot D3cold
pci 0000:06:00.0: PME# disabled
rtl8180 0000:06:00.0: enabling device (0000 -> 0003)
rtl8180 0000:06:00.0: PCI INT A -> Link[LNKB] -> GSI 9 (level, low) -> IRQ 9 rtl8180 0000:06:00.0: setting latency timer to 64
phy2: Selected rate control algorithm 'pid'
phy2: hwaddr 00:17:3f:30:49:d4, RTL8185vD + rtl8225z2
iwconfig:
wlan0 IEEE 802.11bg ESSID:""
Mode:Managed Frequency:2.412 GHz Access Point: Not-Associated Tx-Power=27 dBm
Retry min limit:7 RTS thr:off Fragment thr=2352 B
Encryption key:off
Power Management:off
Link Quality:0 Signal level:0 Noise level:0
Rx invalid nwid:0 Rx invalid crypt:0 Rx invalid frag:0
Tx excessive retries:0 Invalid misc:0 Missed beacon:0
everything seems to be ok.
But starting wpa-supplicant with
wpa_supplicant -i wlan0 -d -c /etc/wpa_supplicant/test.conf
I get the following output:
Initializing interface 'wlan0' conf '/etc/wpa_supplicant/test.conf' driver 'default' ctrl_interface 'N/A' bridge 'N/A' Configuration file '/etc/wpa_supplicant/test.conf' -> '/etc/wpa_supplicant/test.conf'
Reading configuration file '/etc/wpa_supplicant/test.conf'
Priority group 0
id=0 ssid='my_secrect_ssid'
Initializing interface (2) 'wlan0'
SIOCGIWRANGE: WE(compiled)=22 WE(source)=21 enc_capa=0xf
capabilities: key_mgmt 0xf enc 0xf flags 0x0
WEXT: Operstate: linkmode=1, operstate=5
Own MAC address: 00:17:3f:30:49:d4wpa_driver_wext_set_wpawpa_driver_wext_set_key: alg=0 key_idx=0 set_tx=0 seq_len=0 key_len=0wpa_driver_wext_set_key: alg=0 key_idx=1 set_tx=0 seq_len=0 key_len=0wpa_driver_wext_set_key: alg=0 key_idx=2 set_tx=0 seq_len=0 key_len=0wpa_driver_wext_set_key: alg=0 key_idx=3 set_tx=0 seq_len=0 key_len=0 wpa_driver_wext_set_countermeasureswpa_driver_wext_set_drop_unencrypted
RSN: flushing PMKID list in the driver
Setting scan request: 0 sec 100000 usec
EAPOL: SUPP_PAE entering state DISCONNECTED
EAPOL: KEY_RX entering state NO_KEY_RECEIVE
EAPOL: SUPP_BE entering state INITIALIZE
EAP: EAP entering state DISABLED
Added interface wlan0RTM_NEWLINK: operstate=0 ifi_flags=0x1003 ([UP])
Wireless event: cmd=0x8b06 len=8
State: DISCONNECTED -> SCANNING
Starting AP scan (specific SSID)
Scan SSID - hexdump_ascii(len=8):
64 69 64 65 6c 64 75 6d dideldum
Trying to get current scan results first without requesting a new scan to speed up initial association Received 0 bytes of scan results (0 BSSes)
CTRL-EVENT-SCAN-RESULTS
Selecting BSS from priority group 0
Try to find WPA-enabled AP
Try to find non-WPA AP
No suitable AP found.
Setting scan request: 0 sec 0 usec
Starting AP scan (broadcast SSID)
Scan requested (ret=0) - scan timeout 5 secondsRTM_NEWLINK: operstate=0 ifi_flags=0x1003 ([UP])
Wireless event: cmd=0x8b19 len=8
Received 0 bytes of scan results (0 BSSes)
CTRL-EVENT-SCAN-RESULTS
Selecting BSS from priority group 0
Try to find WPA-enabled AP
Try to find non-WPA AP
No suitable AP found.
Setting scan request: 5 sec 0 usec
EAPOL: disable timer tick
Starting AP scan (specific SSID)
Scan SSID - hexdump_ascii(len=8):
64 69 64 65 6c 64 75 6d dideldum
Scan requested (ret=0) - scan timeout 30 secondsRTM_NEWLINK: operstate=0 ifi_flags=0x1003 ([UP])
Wireless event: cmd=0x8b19 len=8
Received 0 bytes of scan results (0 BSSes)
CTRL-EVENT-SCAN-RESULTS
Selecting BSS from priority group 0
Try to find WPA-enabled AP
Try to find non-WPA AP
No suitable AP found.
Setting scan request: 5 sec 0 usec
Starting AP scan (broadcast SSID)
Scan requested (ret=0) - scan timeout 30 secondsRTM_NEWLINK: operstate=0 ifi_flags=0x1003 ([UP])
Wireless event: cmd=0x8b19 len=8
Received 0 bytes of scan results (0 BSSes)
CTRL-EVENT-SCAN-RESULTS
Selecting BSS from priority group 0
Try to find WPA-enabled AP
Try to find non-WPA AP
No suitable AP found.
Setting scan request: 5 sec 0 usec
Starting AP scan (specific SSID)
Scan SSID - hexdump_ascii(len=8):
64 69 64 65 6c 64 75 6d dideldum
Scan requested (ret=0) - scan timeout 30 seconds
...
...
...
The config-file is running well with a rt73, rtl8187 and a b43 card. So it seems, that the pcmcia-card itself is the problem.
Any hints?
Best regards
Robert
P.S. wpa-supplicant is 0.6.4, wireless-tools are 29-1 from debian lenny.
Quoted 16 lines · Robert Goldner
Wireless event: cmd=0x8b19 len=8 Received 0 bytes of scan results (0 BSSes) CTRL-EVENT-SCAN-RESULTS
Selecting BSS from priority group 0
Try to find WPA-enabled AP
Try to find non-WPA AP
No suitable AP found.
Setting scan request: 5 sec 0 usec Starting AP scan (specific SSID)
Scan SSID -hexdump_ascii(len=8):
64 69 64 65 6c 64 75 6d dideldum
Scan requested (ret=0) - scan timeout 30 seconds
...
...
...
Quoted 5 lines
The config-file is running well with a rt73, rtl8187 and a b43 card. So it seems, that the pcmcia-card itself is the problem.
Any hints?
You are not getting any scan results in your wpa_supplicant output? Does the output of ifconfig show wlan0 to be up? If so, what does the output of 'iwlist wlan0 scan' show?
Larry
Quoted 21 lines · Larry Finger
Quoted 20 lines · Robert Goldner
Wireless event: cmd=0x8b19 len=8 Received 0 bytes of scan results (0 BSSes) CTRL-EVENT-SCAN-RESULTS
Selecting BSS from priority group 0
Try to find WPA-enabled AP
Try to find non-WPA AP
No suitable AP found.
Setting scan request: 5 sec 0 usec Starting AP scan (specific SSID)
Scan SSID -hexdump_ascii(len=8):
64 69 64 65 6c 64 75 6d dideldum
Scan requested (ret=0) - scan timeout 30 seconds
...
...
...The config-file is running well with a rt73, rtl8187 and a b43 card. So it seems, that the pcmcia-card itself is the problem.
Quoted 10 lines
Quoted 1 line
Any hints?
You are not getting any scan results in your
wpa_supplicantoutput? Does the output of ifconfig show wlan0 to be up? If so, what does the output of 'iwlist wlan0 scan' show?Larry
Signature · 3 lines
To unsubscribe from this list: send the line "unsubscribe linux-wireless" in the body of a message to [email protected] More majordomo info at http://vger.kernel.org/majordomo-info.html
Hi Larry,
very good point. There is a German saying like:
"who is able to read, has clear advantages..."
The ifconfig output seems good (like other working wlan cards), and the interface is up. But iwlist wlan0 scan does not find any wlan-network. Very strange, because I made this test very close to the access-point (about 30 cm distance). With other wlan-cards I get signal levels of ~80% of maximum. So maybe the receiving part is broken. I can not test the hardware with the windows-driver, because I don't have a windows-installation.
Robert
Quoted 2 lines · Robert Goldner
The ifconfig output seems good (like other working wlan cards), and the interface is up. But iwlist wlan0 scan does not find any wlan-network. Very strange, because I made this test very close to the access-point (about 30 cm distance). With other wlan-cards I get signal levels of ~80% of maximum. So maybe the receiving part is broken. I can not test the hardware with the windows-driver, because I don't have a windows-installation.
Just for the record, you should run iwlist as root. That is the only way you will get an active scan. In addition, it may take several tries; however, wpa_supplicant did all that before without finding any results. A broken card is a strong possibility. Do any of your colleagues have Windows?
Larry
Quoted 13 lines · Robert Goldner
Hi Larry,
very good point. There is a German saying like:
"who is able to read, has clear advantages..."The ifconfig output seems good (like other working wlan cards), and the interface is up. But iwlist wlan0 scan does not find any wlan-network. Very strange, because I made this test very close to the access-point (about 30 cm distance). With other wlan-cards I get signal levels of ~80% of maximum. So maybe the receiving part is broken. I can not test the hardware with the windows-driver, because I don't have a windows-installation.
Quoted 1 line
Robert
Can you try using the windows driver with ndiswrapper? That should also reveal if the card is broken.
Signature · 1 line
Vista: [V]iruses, [I]ntruders, [S]pyware, [T]rojans and [A]dware. :-)
Quoted 4 lines · Larry Finger
Quoted 2 lines · Robert Goldner
The ifconfig output seems good (like other working wlan cards), and the interface is up. But iwlist wlan0 scan does not find any wlan-network. Very strange, because I made this test very close to the access-point (about 30 cm distance). With other wlan-cards I get signal levels of ~80% of maximum. So maybe the receiving part is broken. I can not test the hardware with the windows-driver, because I don't have a windows-installation.
Quoted 13 lines
Just for the record, you should run iwlist as root. That is the only way you will get an active scan. In addition, it may take several tries; however,
wpa_supplicantdid all that before without finding any results. A broken card is a strong possibility. Do any of your colleagues have Windows?Larry
Signature · 3 lines
To unsubscribe from this list: send the line "unsubscribe linux-wireless" in the body of a message to [email protected] More majordomo info at http://vger.kernel.org/majordomo-info.html
My fried has an old laptop with windowsXP, and at his laptop the card detects my network (after installation of the driver). So the card itself seems to be ok. A WPA connection is not possible, because the windows-installation is very old (before SP1), so there is no WPA-support, but a WEP-connection was possible.
iwlist was run as root. I made an other try, boot with acpi=off, but the same result.
A try with ndiswrapper is not so easy, because my actual kernel uses 4k stacks, and this is not really compatible with ndiswrapper.
When I searched for the windows-driver, I got the information from belkin, that there are 7 different versions of the card possible. My card has a version 7000de, which means version 7. See
http://www.belkin.com/de/support/article/?lid=en&pid=F5D7010de&aid=7422&scid=342
(only in german, but saying that the first number of the version string means the needed software version).
Any ideas?
Robert