WLAN: known issues and how to help
Philip Rhoades
phil at pricom.com.au
Tue Dec 2 16:16:13 CET 2008
Werner,
Werner Almesberger wrote:
> Philip Rhoades wrote:
>> out a few days ago. The first attempt only lasted a few hours but the
>> most recent one lasted 16.5 hours before I had to stop it! Is SHR an
>> older OS but more worked on ie less bugs?
>
> Interesting ! I don't know if SHR is doing anything differently or if
> this was just a random difference. When the network drops, does
> anything noteworthy get recorded in dmesg ? E.g., "AR6000 disconnected"
> or similar ?
I just tried my WLAN test with:
openmoko-asu-om-gta02.rootfs.jffs2
testing-om-gta01-20081201.uImage.bin
(it lasted a bit over four hours) and the only mentions of AR6000 using
dmesg are:
AR6000 Reg Code = 0x40000060
AR6000 connected event on freq 2472 with bssid 00:1c:10:09:8e:32
listenInterval=100, beaconInterval = 100, beaconIeLen = 0 assocReqLen=29
assocRespLen =22
AR6000 Reg Code = 0x80000114
Regards,
Phil.
--
Philip Rhoades
GPO Box 3411
Sydney NSW 2001
Australia
E-mail: phil at pricom.com.au
More information about the devel
mailing list