I have a D-Link PCI card with a ADM8211 driver:
00:07.0 Network controller: ADMtek ADM8211 802.11b Wireless Interface
(rev 11)
A few years ago I used it in Linux with the out-of-tree driver without any
problems. I now have need of the card again in Linux, but the card doesn't
want to associate with the AP. I tried the card under Windows and it worked
well, so I know it's not hardware or configuration issues.
I am using kernel 2.6.29.1 with version 29 of the wireless_tools package and
wpa_supplicant 0.6.9. I have disabled wpa_supplicant and have tried
configuring the card directly with iwconfig:
iwconfig wlan0 essid (ssid) channel 1 mode managed \
key (some hex junk)
In the end, iwconfig reports:
wlan0 IEEE 802.11b ESSID:"(ssid)"
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:(some hex junk) Security mode:open
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
There are a few weird things I'm observing:
- The signal level and noise level are both at 0.
- Even when scanning, the signal strength is very low even though the AP is
4 feet away (Quality=0/100 Signal level:19/100). Windows reports a strong
signal.
- The kernel log only reports the following problems:
Apr 25 11:22:17 xyz wlan0: direct probe to AP 00:30:bd:60:d3:44 try 1
Apr 25 11:22:17 xyz wlan0: direct probe to AP 00:30:bd:60:d3:44 try 2
Apr 25 11:22:18 xyz wlan0: direct probe to AP 00:30:bd:60:d3:44 try 3
Apr 25 11:22:18 xyz wlan0: direct probe to AP 00:30:bd:60:d3:44 timed out
(the AP mac address is correct)
- When the card is loaded, there is a significant pause (about 15 seconds)
when I first try to do something with the card. For example, if I load the
module and use iwconfig as outlined above and then run iwconfig again to see
the configuration, it takes about 15 or 16 seconds for it to display. Also,
if any services (like ssh) want to bind the address when it first comes up,
sshd takes about 15 seconds to start. But, once this delay has happened,
everything else works fine. For example, if I run iwconfig again, it
displays the information immediately.
Would any of you have any pointers on how to debug the problem with this
card and fix it? I'm running a custom kernel, so I can reconfigure or patch
as necessary. (Distribution is Linux From Scratch; all other similar
systems with wireless networking work just fine.)
Thanks in advance.
--
Alf
@
On Monday 27 April 2009 02:03:17 pm you wrote:
> May want to try wireless-testing
I tried it and it work for a little bit. Here are the messages I received:
===== dmesg =====
Apr 29 06:51:54 cfg80211: Using static regulatory domain info
Apr 29 06:51:54 cfg80211: Regulatory domain: US
Apr 29 06:51:54 (start_freq - end_freq @ bandwidth), (max_antenn
a_gain, max_eirp)
Apr 29 06:51:54 (2402000 KHz - 2472000 KHz @ 40000 KHz), (600 mB
i, 2700 mBm)
Apr 29 06:51:54 (5170000 KHz - 5190000 KHz @ 40000 KHz), (600 mB
i, 2300 mBm)
Apr 29 06:51:54 (5190000 KHz - 5210000 KHz @ 40000 KHz), (600 mB
i, 2300 mBm)
Apr 29 06:51:54 (5210000 KHz - 5230000 KHz @ 40000 KHz), (600 mB
i, 2300 mBm)
Apr 29 06:51:54 (5230000 KHz - 5330000 KHz @ 40000 KHz), (600 mB
i, 2300 mBm)
Apr 29 06:51:54 (5735000 KHz - 5835000 KHz @ 40000 KHz), (600 mB
i, 3000 mBm)
Apr 29 06:51:54 cfg80211: Calling CRDA for country: US
Apr 29 06:51:54 adm8211 0000:00:07.0: PCI INT A -> GSI 18 (level, low
) -> IRQ 18
Apr 29 06:51:54 0000:00:07.0 (adm8211): Channel range: 1 - 11
Apr 29 06:51:54 0000:00:07.0 (adm8211): RFtype=1 BBPtype=1 Specific B
BP=0 Transceiver=0
Apr 29 06:51:54 phy0: Selected rate control algorithm 'minstrel'
Apr 29 06:51:54 phy0: hwaddr 00:40:05:90:3d:89, Rev 0x11
Apr 29 06:52:23 wlan0: authenticate with AP 00:30:bd:60:d3:44
Apr 29 06:52:23 wlan0: authenticated
Apr 29 06:52:23 wlan0: associate with AP 00:30:bd:60:d3:44
Apr 29 06:52:23 wlan0: RX AssocResp from 00:30:bd:60:d3:44 (capab=0x11
status=0 aid=95)
Apr 29 06:52:23 wlan0: associated
Apr 29 06:52:23 phy0: Allocated STA 00:30:bd:60:d3:44
Apr 29 06:52:23 phy0: Inserted STA 00:30:bd:60:d3:44
Apr 29 06:53:54 phy0: Removed STA 00:30:bd:60:d3:44
Apr 29 06:53:54 phy0: Destroyed STA 00:30:bd:60:d3:44
Apr 29 06:53:56 wlan0: authenticate with AP 00:30:bd:60:d3:44
Apr 29 06:53:56 wlan0: authenticated
Apr 29 06:53:56 wlan0: associate with AP 00:30:bd:60:d3:44
Apr 29 06:53:56 wlan0: RX ReassocResp from 00:30:bd:60:d3:44 (capab=0x11
status=0 aid=97)
Apr 29 06:53:56 wlan0: associated
Apr 29 06:53:56 phy0: Allocated STA 00:30:bd:60:d3:44
Apr 29 06:53:56 phy0: Inserted STA 00:30:bd:60:d3:44
Apr 29 07:13:39 wlan0: disassociated (Reason: 4)
Apr 29 07:13:39 phy0: Removed STA 00:30:bd:60:d3:44
Apr 29 07:13:39 phy0: Destroyed STA 00:30:bd:60:d3:44
Apr 29 07:13:40 wlan0: associate with AP 00:30:bd:60:d3:44
Apr 29 07:13:40 wlan0: deauthenticated (Reason: 9)
Apr 29 07:13:41 wlan0: direct probe to AP 00:30:bd:60:d3:44 try 1
Apr 29 07:13:41 wlan0: direct probe to AP 00:30:bd:60:d3:44 try 2
Apr 29 07:13:41 wlan0: direct probe to AP 00:30:bd:60:d3:44 try 3
Apr 29 07:13:41 wlan0: direct probe to AP 00:30:bd:60:d3:44 timed out
Apr 29 07:22:14 wlan0: direct probe to AP 00:30:bd:60:d3:44 try 1
Apr 29 07:22:14 wlan0: direct probe to AP 00:30:bd:60:d3:44 try 2
Apr 29 07:22:14 wlan0: direct probe to AP 00:30:bd:60:d3:44 try 3
Apr 29 07:22:14 wlan0: direct probe to AP 00:30:bd:60:d3:44 timed out
===== end dmesg =====
After that the card stopped working.
What I find odd are the delays in authenticating with the AP (about 30
seconds) and when the STA is inserted to the next report (about 90 seconds).
When the card works, it takes about 3 minutes for it to come up.
I also tried kernel 2.6.30-rc3 and that one didn't work. So there is
something in the wireless testing tree that fixes the situation, although
temporarily.
> or compat-wireless to see if the
> issue is still present.
Today's snapshot of compat-wireless didn't compile with a 2.6.29.1 kernel:
CC [M] /home/alberto/git/compat-wireless-2009-04-29/net/mac80211/led.o
/home/alberto/git/compat-wireless-2009-04-29/net/mac80211/led.c: In function
'ieee80211_led_init':
/home/alberto/git/compat-wireless-2009-04-29/net/mac80211/led.c:58: error:
invalid application of 'sizeof' to incomplete type 'struct led_trigger'
/home/alberto/git/compat-wireless-2009-04-29/net/mac80211/led.c:62: error:
dereferencing pointer to incomplete type
/home/alberto/git/compat-wireless-2009-04-29/net/mac80211/led.c:63: error:
implicit declaration of function 'led_trigger_register'
/home/alberto/git/compat-wireless-2009-04-29/net/mac80211/led.c:69: error:
invalid application of 'sizeof' to incomplete type 'struct led_trigger'
/home/alberto/git/compat-wireless-2009-04-29/net/mac80211/led.c:73: error:
dereferencing pointer to incomplete type
/home/alberto/git/compat-wireless-2009-04-29/net/mac80211/led.c:80: error:
invalid application of 'sizeof' to incomplete type 'struct led_trigger'
/home/alberto/git/compat-wireless-2009-04-29/net/mac80211/led.c:84: error:
dereferencing pointer to incomplete type
/home/alberto/git/compat-wireless-2009-04-29/net/mac80211/led.c:91: error:
invalid application of 'sizeof' to incomplete type 'struct led_trigger'
/home/alberto/git/compat-wireless-2009-04-29/net/mac80211/led.c:95: error:
dereferencing pointer to incomplete type
/home/alberto/git/compat-wireless-2009-04-29/net/mac80211/led.c: In function
'ieee80211_led_exit':
/home/alberto/git/compat-wireless-2009-04-29/net/mac80211/led.c:106: error:
implicit declaration of function 'led_trigger_unregister'
> This driver is old and the maintainer is no
> longer active
That's too bad.
--
Alf
@
On Sat, Apr 25, 2009 at 1:31 PM, Alf <[email protected]> wrote:
> I have a D-Link PCI card with a ADM8211 driver:
>
> =C2=A000:07.0 Network controller: ADMtek ADM8211 802.11b Wireless Int=
erface
> =C2=A0 =C2=A0(rev 11)
>
> A few years ago I used it in Linux with the out-of-tree driver withou=
t any
> problems. =C2=A0I now have need of the card again in Linux, but the c=
ard doesn't
> want to associate with the AP. =C2=A0I tried the card under Windows a=
nd it worked
> well, so I know it's not hardware or configuration issues.
>
> I am using kernel 2.6.29.1 with version 29 of the wireless_tools pack=
age and
> wpa_supplicant 0.6.9. =C2=A0I have disabled wpa_supplicant and have t=
ried
> configuring the card directly with iwconfig:
>
> =C2=A0iwconfig wlan0 essid (ssid) channel 1 mode managed \
> =C2=A0 =C2=A0key (some hex junk)
>
> In the end, iwconfig reports:
>
> =C2=A0wlan0 =C2=A0 =C2=A0 IEEE 802.11b =C2=A0ESSID:"(ssid)"
> =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 Mode:Managed =C2=A0Frequency:2.412=
GHz =C2=A0Access Point: Not-Associated
> =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 Tx-Power=3D27 dBm
> =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 Retry min limit:7 =C2=A0 RTS thr:o=
ff =C2=A0 Fragment thr=3D2352 B
> =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 Encryption key:(some hex junk) =C2=
=A0 Security mode:open
> =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 Power Management:off
> =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 Link Quality:0 =C2=A0Signal level:=
0 =C2=A0Noise level:0
> =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 Rx invalid nwid:0 =C2=A0Rx invalid=
crypt:0 =C2=A0Rx invalid frag:0
> =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 Tx excessive retries:0 =C2=A0Inval=
id misc:0 =C2=A0 Missed beacon:0
>
> There are a few weird things I'm observing:
>
> - The signal level and noise level are both at 0.
>
> - Even when scanning, the signal strength is very low even though the=
AP is
> 4 feet away (Quality=3D0/100 =C2=A0Signal level:19/100). =C2=A0Window=
s reports a strong
> signal.
>
> - The kernel log only reports the following problems:
>
> =C2=A0Apr 25 11:22:17 xyz wlan0: direct probe to AP 00:30:bd:60:d3:44=
try 1
> =C2=A0Apr 25 11:22:17 xyz wlan0: direct probe to AP 00:30:bd:60:d3:44=
try 2
> =C2=A0Apr 25 11:22:18 xyz wlan0: direct probe to AP 00:30:bd:60:d3:44=
try 3
> =C2=A0Apr 25 11:22:18 xyz wlan0: direct probe to AP 00:30:bd:60:d3:44=
timed out
>
> =C2=A0(the AP mac address is correct)
>
> - When the card is loaded, there is a significant pause (about 15 sec=
onds)
> when I first try to do something with the card. =C2=A0For example, if=
I load the
> module and use iwconfig as outlined above and then run iwconfig again=
to see
> the configuration, it takes about 15 or 16 seconds for it to display.=
=C2=A0Also,
> if any services (like ssh) want to bind the address when it first com=
es up,
> sshd takes about 15 seconds to start. =C2=A0But, once this delay has =
happened,
> everything else works fine. =C2=A0For example, if I run iwconfig agai=
n, it
> displays the information immediately.
>
> Would any of you have any pointers on how to debug the problem with t=
his
> card and fix it? =C2=A0I'm running a custom kernel, so I can reconfig=
ure or patch
> as necessary. =C2=A0(Distribution is Linux From Scratch; =C2=A0all ot=
her similar
> systems with wireless networking work just fine.)
May want to try wireless-testing or compat-wireless to see if the
issue is still present. This driver is old and the maintainer is no
longer active so your best bet is to try the latest and see if someone
is willing to help you with random bits of troubleshooting.
Luis