I attached a three wire so-called 'TTL' level serial connection to the
Squeezebox Radio ('SB'). I soldered to the battery connector, not
wanting to mess up the beautiful gold-plated test connections near the
processor. I then connected a cheap usb-serial adapter, and ran it from
the Windows serial terminal application putty's serial connection at
115200 baud configured with 200000 lines of scrollback.
After digging around the syslogd and klogd busybox source files, I
determined that the standard bootup run from /etc/init.d/rcS starts both
with default log level values of 8, which should pass all kernel and
application debug messages. The /etc/init.d/wlan start command calls
/lib/atheros/loadAR6000l.sh script to load the ar6000.ko driver. This
folder contains some goodies such as bmiloader and wmiconfig, which are
there for us to investigate.
At this point, the AR6000 driver doesn't report much, e.g.:
[ 16.635816] AR6000 Reg Code = 0x40000060
[ 24.436491] channel hint set to 2412
[ 24.474506] AR6000 connected event on freq 2412 with bssid
60:a4:4c:xx:xx:xx listenInterval=100, beaconInterval = 100, beaconIeLen
= 22 assocReqLen=60 assocRespLen =93
[ 24.489689] Network: Infrastructure
I'm not sure how udhcpc is launched, but it reports:
Sending select for 192.168.xxx.xxx...
Lease of 192.168.xxx.xxx obtained, lease time 2013
adding dns 192.168.xxx.xxx
But then later:
[ 102.340664] AR6000 disconnected
[ 102.349013] AR6000 disconnected
[ 187.634459] channel hint set to 2412
[ 197.648873] AR6000 disconnected
[ 202.664586] channel hint set to 2412
[ 202.672031] AR6000 disconnected
and so forth forever. Not very informative.
This occurs even though a separate ssh shell is running a ping to the
central router with return times between 2 and 100 ms.
(BTW, ^C (e.g., to stop ping) doesn't work in the serial console. The
only way to break out is to reboot if you have lost your connection.)
No messages for disconnection or preceding issues. Also, there are no
messages from wpa_supplicant or udchpc, which should be on top of this,
I suppose.
There is some good news. From the serial console, you can restart the
network without rebooting:
/etc/init.d/wlan stop
/etc/init.d/wlan start
udhcpc -R -a -p/var/run/udhcpc.eth1.pid -b --syslog -ieth1 -HxXxXxXxX
-s/etc/network/udhcpc_action
where xXxXxXxX is the hostname
You can monitor things, somewhat, using ifconfig and iwconfig
BTW, I tried:
iwconfig eth1 rate auto
and it helped, maybe, a bit when I noticed the rate dropping to 5 Mbps
and not recovering, then disconnecting. This extended the life a bit,
but not forever.
Next Steps:
o Increase verbosity in existing ar6000 driver
o What exactly is this driver talking to? What is supposed to monitor
it? The system can lose its dhcp address before it loses its
association. It seems like something is not doing its job (besides
perhaps the 6102 chip being mis-configured or not capable enough).
o Experiment with wmiconfig and bmiloader.
I can upload the serial console output to this site, but I don't know
how.
------------------------------------------------------------------------
POMdev's Profile: http://forums.slimdevices.com/member.php?userid=70558
View this thread: http://forums.slimdevices.com/showthread.php?t=111663
_______________________________________________
Radio mailing list
[email protected]
http://lists.slimdevices.com/mailman/listinfo/radio
