ralphy wrote: > To help you resolve the build issue, you'll need to post the full log, > not just where bitbake failed. > > I've uploaded the 'wpa_supplicant v2.9 binaries for the radio to > sourceforge' > (https://sourceforge.net/projects/lmsclients/files/squeezeos/). To > install see the bottom of 'this post' > (https://forums.slimdevices.com/showthread.php?111663-Community-Build-Radio-Firmware&p=971241&viewfull=1#post971241). > > The atheros-ar6ksdk.build_sw.63 source that I'm investigating is from > the 'google chromium project' > (https://chromium.googlesource.com/chromiumos/third_party/atheros/+/0b056069300072c35f9c6795a9a48e27bcafe82d/files). > I've had to pull the sources for a couple of the tools from the sdk 3.1 > source as google has removed it from theirs. > > The supported ar600x device list matches the driver from logitech, > however the .63 driver tries to load the firmware for the ar6003 when > inserted. I'm guessing that google modified the driver to look for the > ar6003 as that appears to be the atheros hardware they use(d). That's as > far as I've had time to look at it.
Great, some real progress. I will download the sources and have a look. It might be that we have to compare and substitute decompiled code for the 6003 related code. Perhaps 6002 vs 6003 device specific code might not be so critical if the issue is how the chip and driver is monitoring, reporting, and reacting to packet loss issues. Also, the problem might lie partially in the CPU code, which is another matter. Some critical questions are: how is the system getting disrupted, how does that cause a failure, why are the chip and driver not taking effective countermeasures, and why is the driver not reporting failure to the supplicant or other layer? I spent quite a while searching for "the full log, not just where bitbake failed." I have not found it. Where might it be? Here is the latest console session plus the indicated failure log appended 31700. If this is insufficient, I need some help to find the full log. BTW, the TL-WN722N v1 usb adapter uses the Atheros AR9271 ath9k [phy1] chip, which can operate in monitor mode, but not as a spectrum analyzer. This would require the discontinued and rare $500 Wi-Spy DBx device. Its looking like 80's HP spectrum analyzer and camera for me, although perhaps I could down convert into an RTL-SDR... This might even work if a disruptive non-WiFi signal is strong enough. BTW also, I am new to WiFi hacking. Does anyone have any experience with WiFi sniffing? What is the best way to use aircrack-ng and / or other packages to identify packets that might be causing trouble? Also, any pointers to WiFi tech tutorials? Both packets and software. Thank you. ------------------------------------------------------------------------ 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
