I was wrong about the messages; they were showing up in kern.log AND syslog as expected but I think I have too many logs for the system log viewer application to handle smoothly.
I am attaching a syslog for 2.6.39-020639rc6.201105050227, I stopped networking, wrote reset to /sys/kernel/debug/ieee80211/phy0/ath5k/debug started networking again... I believe I did some of those more than once.
The network failed to start scanning until after I opened the netbook nearby whereupon the laptop connected to the AP.
I have a syslog where the network fails to even scan (not included here). I will try a couple more times to get a syslog where it scans but fails to connect.
I was wrong about the messages; they were showing up in kern.log AND syslog as expected but I think I have too many logs for the system log viewer application to handle smoothly.
I am attaching a syslog for 2.6.39- 020639rc6. 201105050227, I stopped networking, wrote reset to /sys/kernel/ debug/ieee80211 /phy0/ath5k/ debug started networking again... I believe I did some of those more than once.
The network failed to start scanning until after I opened the netbook nearby whereupon the laptop connected to the AP.
I have a syslog where the network fails to even scan (not included here). I will try a couple more times to get a syslog where it scans but fails to connect.