Bob Copeland wrote: > On Wed, Apr 8, 2009 at 9:38 AM, Will Keaney wrote: > >>> Hmm, you should be seeing association requests in any case. �How are >>> you starting the wireless network? �Can you try setting the -dd option >>> to wpa_supplicant? >>> >>> >> I'm starting it by modprobing ath5k or ath_pci, depending on what needs >> to be tested. �udev calls Gentoo's init script for the interface that's >> created, which starts wpa_supplicant. �I can add debugging flags as well. >> > > Ok, please do and post the log. > Attached. For this log, I started from a fresh boot, set 'dmesg -n7', and ran "# modprobe ath5k && sleep 10 && /etc/init.d/net.wlan0 stop && wpa_supplicant -c /etc/wpa_supplicant/wpa_supplicant.conf -Dwext -dd -iwlan0 | tee /home/uberpinguin/wpa_supplicant.log". dmesg stops showing any output from ath5k and wpa_supplicant fairly quickly, even though I ran wpa_supplicant for a couple of minutes and ran a number of scans and reconnects. I also have to manually set the reg domain to US every time I load the ath5k module. I tried configuring wpa_supplicant.conf to do this itself, but that doesn't seem to work. It would be nice to have a module parameter for setting this at load time. >> When testing with the guest wireless at work today, I got the attached >> error in dmesg. �I only got it once, and haven't been able to reproduce >> it, but thought it might be of interest. >> > > Very much so, thanks for the report (probably has no bearing on your case, > but this is the first example since we added more debugging). > > >> [ 6260.056213] Hardware name: 6459CTO >> [ 6260.056218] invalid hw_rix: 1a >> > > 0x1a is ATH5K_RATE_CODE_2M, certainly a valid rate for 2 GHz.. something's > broken. This is pretty rare though so I think it is some sort of race > condition when switching over to 5 GHz. > Hmm ok. Thanks for the info. Will