Reg: Access point association gets down with in 5min for MARVELL_SDIO_8688_WLAN_CARD
Dan Williams
dcbw at redhat.com
Thu Aug 6 11:50:24 EDT 2009
On Wed, 2009-08-05 at 10:05 +0530, praveen wrote:
> On Monday 27 July 2009 10:26:18 am praveen wrote:
> > On Friday 24 July 2009 05:06:33 pm praveen wrote:
> > > Hi All,
> > >
> > > I am using MARVELL_SDIO_8688_WLAN_CARD with PXA270 based reference board.
> > > I used the patch available with this list for 8688 card.
> > >
> > > After inserting the modules I get the following debug messages
> > >
> > > [root at REGULUS /tmp]#insmod libertas.ko
> > > [root at REGULUS /tmp]#
> > > [root at REGULUS /tmp]#insmod libertas_sdio.ko
> > > libertas_sdio: Libertas SDIO driver
> > > libertas_sdio: Copyright Pierre Ossman
> > > libertas: 00:1a:6b:9f:37:36, fw 10.38.1p25, cap 0x00000303
> > > libertas: PREP_CMD: command 0x0022 failed: 2
> > > libertas: eth1: Marvell WLAN 802.11 adapter
> > > [root at REGULUS /tmp]#
> > > [root at REGULUS /tmp]#
> > > [root at REGULUS /tmp]#
> > >
> > > Scanning the access point using iwlist gives following prints. In this
> > > all the channel and bit rates are wrong. I don't know why?
> > >
> > > [root at REGULUS /tmp]#./iwlist eth1 scan
> > > Warning: Driver for device eth1 has been compiled with version 22
> > > of Wireless Extension, while this program supports up to version 17.
> > > Some things may be broken...
> > >
> > > eth1 Scan completed :
> > > Cell 01 - Address: 00:1B:2F:4B:42:16
> > > ESSID:"econAP2"
> > > Mode:Managed
> > > Channel:-2.82593e-07
> > > Quality=70/100 Signal level=-75 dBm Noise level=-92
> > > dBm Encryption key:on
> > > Bit Rate:5.29981e-315 Mb/s
> > > Bit Rate:5.30499e-315 Mb/s
> > > Bit Rate:5.31211e-315 Mb/s
> > > Bit Rate:5.31729e-315 Mb/s
> > > Bit Rate:5.31276e-315 Mb/s
> > > Bit Rate:5.31794e-315 Mb/s
> > > Bit Rate:5.32312e-315 Mb/s
> > > Bit Rate:5.32636e-315 Mb/s
> > > Bit Rate:5.316e-315 Mb/s
> > > Bit Rate:5.32118e-315 Mb/s
> > > Bit Rate:5.3283e-315 Mb/s
> > > Bit Rate:5.32927e-315 Mb/s
> > > Cell 02 - Address: 00:11:95:76:8F:60
> > > ESSID:"econAP1"
> > > Mode:Managed
> > > Channel:2.05102e-314
> > > Quality=100/100 Signal level=-97 dBm Noise
> > > level=-92 dBm Encryption key:on
> > > Bit Rate:5.29981e-315 Mb/s
> > > Bit Rate:5.30499e-315 Mb/s
> > > Bit Rate:5.31211e-315 Mb/s
> > > Bit Rate:5.31729e-315 Mb/s
> > > Bit Rate:5.31276e-315 Mb/s
> > > Bit Rate:5.31794e-315 Mb/s
> > > Bit Rate:5.32312e-315 Mb/s
> > > Bit Rate:5.32636e-315 Mb/s
> > > Bit Rate:5.316e-315 Mb/s
> > > Bit Rate:5.32118e-315 Mb/s
> > > Bit Rate:5.3283e-315 Mb/s
> > > Bit Rate:5.32927e-315 Mb/s
> > > Cell 03 - Address: 00:1B:57:F1:24:99
> > > ESSID:"UTStarcom"
> > > Mode:Managed
> > > Channel:3.03586e-315
> > > Quality=100/100 Signal level=-98 dBm Noise
> > > level=-92 dBm Encryption key:off
> > > Bit Rate:5.29981e-315 Mb/s
> > > Bit Rate:5.30499e-315 Mb/s
> > > Bit Rate:5.31211e-315 Mb/s
> > > Bit Rate:5.31729e-315 Mb/s
> > > Bit Rate:5.32118e-315 Mb/s
> > > Bit Rate:5.32312e-315 Mb/s
> > > Bit Rate:5.32636e-315 Mb/s
> > > Bit Rate:5.32927e-315 Mb/s
> > > Bit Rate:5.31276e-315 Mb/s
> > > Bit Rate:5.316e-315 Mb/s
> > > Bit Rate:5.31794e-315 Mb/s
> > > Bit Rate:5.3283e-315 Mb/s
> > >
> > >
> > > I established the link with one of my access point using following
> > > commands ifconfig eth1 192.168.6.165 up
> > > ./iwconfig eth1 mode 2
> > > ./iwconfig eth1 essid "econAP1"
> > > ./iwconfig eth1 enc "s:ca188"
> > > ./iwconfig eth1 key 0123456789
> > > route add default gw 192.168.6.1 eth1
> > >
> > >
> > > After giving above commands my board get associated with the access
> > > point. See the output of below command
> > >
> > > [root at REGULUS /tmp]#./iwconfig eth1
> > > Warning: Driver for device eth1 has been compiled with version 22
> > > of Wireless Extension, while this program supports up to version 17.
> > > Some things may be broken...
> > >
> > > eth1 IEEE 802.11b/g ESSID:"econAP1"
> > > Mode:Managed Channel:-2.06365e+267 Access Point:
> > > 00:11:95:76:8F:60 Bit Rate:1.63394e-312 2b/s Tx-Power=15 dBm
> > > Retry limit:8 RTS thr=2347 B Fragment thr=2346 B
> > > Encryption key:0123-4567-89 Security mode:open
> > > Power Management:off
> > > Link Quality=12/100 Signal level=-89 dBm Noise level=-93 dBm
> > > Rx invalid nwid:0 Rx invalid crypt:0 Rx invalid frag:4496
> > > Tx excessive retries:6 Invalid misc:16 Missed beacon:0
> > >
> > >
> > > But with in 5min board lost the association with the access point. Please
> > > see the output of iwconfig once after association get lost
> > >
> > > [root at REGULUS /tmp]#./iwconfig eth1
> > > Warning: Driver for device eth1 has been compiled with version 22
> > > of Wireless Extension, while this program supports up to version 17.
> > > Some things may be broken...
> > >
> > > eth1 IEEE 802.11b/g ESSID:""
> > > Mode:Managed Channel:-2.06365e+267 Access Point:
> > > 00:00:00:00:00:00 Bit Rate:2.27054e-312 2b/s Tx-Power=15 dBm
> > > Retry limit:8 RTS thr=2347 B Fragment thr=2346 B
> > > Encryption key:0123-4567-89 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:4496
> > > Tx excessive retries:0 Invalid misc:16 Missed beacon:0
> > >
> > > Please give reply for the above issue.
> >
> > Hi All,
> >
> > Can any one help me to solve the above mentioned issue?
>
> Hi All,
>
> I got some improvements in my issue.
>
> The random bitrate while scanning using iwlist command is due to the
> application error. Once I used wirelesstools-version29 this error get solved.
> Now while scanning I am getting correct bitrates.
>
>
> Now the issue is the association get lost within 5 or 10 min and it is not
> automatically re-associate with the access point. I got automatic
> re-association patch from this list in the below link.
>
> http://lists.infradead.org/pipermail/libertas-dev/2007-October/000682.html
>
> I applied this patch to kernel linux-2.6.25. Actually some structure are
> changed in 2.6.25 kernel. Manually I applied the patch according to 2.6.25
> kernel.
>
> Now if I lost the association with access point it get automatically
> re-associated.
>
> while testing the board, with in 15hours the association get lost and
> re-associated for more than 130 times. From the debug message the
> EVENT: deauthenticated makes the association to loss.
>
> Is I am missing something, so that the association get lost for such much
> time?
>
> Please update why the association get lost frequently?
What do your AP logs say? If the firmware thinks it got
deauthenticated, then probably the AP kicked it off for some reason.
Seeing what the debug logs on your access point say would be a good
place to start.
Dan
More information about the libertas-dev
mailing list