Hi, My instruction may be out of date with the latest version of the kernel/filesystem, but a couple of notes on your questions:
With regards to both the 'opkg upgrade' and the 'disagrees about version of symbol', this looks like you are trying to run a module compiled under a different version (older/newer) of the kernel, i.e. one incompatible with the modules you are trying to load. To get around this I'd recommend trying to run the opkg upgrade again, or downloading and copying over the latest image. I'd recommend trying with the Ubuntu build from RobertCNelson (http://elinux.org/BeagleBoardUbuntu#Method_1:_Download_a_Complete_Pre-Configured_Image - Follow the instructions here, try with the Raring image) - this should work 'out of the box' with the TL-WN722N. The latest Angstrom also includes the ath9k_htc by default, so should also work 'out of the box'. TL/DR: Forget about all my earlier instructions. Use a new image that supports your wifi device out of the box. Regards, Andrew. On Friday, 11 October 2013 14:56:32 UTC+13, Ben Mitch wrote: > > On Thursday, 2 May 2013 23:14:24 UTC+1, AndrewTaneGlen wrote: > >> For what it's worth, here are steps I documented for reliably using an >> 'ath9k_htc' usb wifi dongle with Angstrom (systemd-image): > > > Thanks everyone for posting their experiences. I've tried following > several guides, using two dongles (first an Edimax EW-7811UN, which I > understand needs driver RTL8192CU, then a TP-Link > TL-WN722N<http://www.amazon.co.uk/gp/r.html?R=OGAVEVZ53F3&C=3AOWPWPM94BIV&H=KKKMDGPAKMBADZADAU283TCE1OGA&T=C&U=http%3A%2F%2Fwww.amazon.co.uk%2Fdp%2FB002SZEOLG%2Fref%3Dpe_385721_37038051_pe_217191_31005151_M3T1_dp_2> > which > I think uses ath9k_htc). I have an Asus N10 on order, out of desperation, > but perhaps someone can explain a couple o' things to me that I haven't > been able to make sense of yet. > > At the moment, I'm finding a lot of different approaches suggested, and > I'm not familiar enough with the kernel module/driver architecture of Linux > to see the commonality there must be between them. Perhaps an answer to one > of my questions will help clue me in. > > * Tried the RTL8192CU following > http://circuitco.com/support/index.php?title=WiFi - "opkg upgrade" took > 4-5 hours instead of the 12-20 mins suggested, and the result was a > wireless card that seemed to keep turning itself on and off, or sometimes > just off and off. After further googling, thought I'd bail and try the > other dongle. > > * Tried following http://goo.gl/Zdfo0M for the TL-WN722N. Had to build > ath9k_htc, and the compile failed (pid vs. portid, etc.). I went through > trying to patch up the source, but my notes from that evening peter out > uninformatively (three or four days in, now, exhausted... :/). In any case, > no dice. > > * Tried opkg install kernel-module-ath9k-htc to use the pre-compiled > package. Present on machine, installed ok, but every attempt to load > generated "Invalid argument", with dmesg filled with notes about "disagrees > about version of symbol ...". Gave up, figured I'd have to build for myself. > > * Tried running opkg upgrade with the TL-WN722N plugged in. Came back five > hours later to find the board had frozen. Have not tried upgrading again > since, but still have this in my arsenal, also filed under "desperation". > > In my latest attempt to go wireless, I installed the image 2013.06.20 from > BBB latest images page, logged in as root, and then followed the steps > provided back in May by AndrewTaneGlen, with the change that I used the > latest "backports" release (backports-3.11-rc3-1.tar.bz2) rather than the > circa-May compat-wireless release. As mentioned above, I already tried the > same procedure but using the compat-wireless release, and the compile > failed. > > The log of my SSH is attached, as is my current boot-time dmesg (i.e. > during a reboot after I get to the end of SSH.log). If anyone can clue me > in on any of the following, I'd be very grateful: > > (in SSH.log...) > > * need I worry about "kernel-dev: unsatisfied recommendation for > kernel-base-dev"? > > * is backports the right place to get the driver? I noticed there's an > opkg "kernel-module-ath9k_htc", but whilst I could install it, I couldn't > get modprobe to load it. I'm not good with modprobe, perhaps. Is this > package a valid pre-compiled driver I could use against 2013.06.20? If so, > I only need to figure out how to load it, but the messages I got when I > tried it made me very suspicious I'd have to build my own. > > * I have been getting this a lot: > > WARNING: could not open /lib/modules/3.8.13/modules.order: No such file or > directory > WARNING: could not open /lib/modules/3.8.13/modules.builtin: No such file > or directory > > does that mean my modules have been built, but have not been "installed"? > why do these files not exist, and who is trying to access them? > > * Finally, when I try "modprobe ath9k_htc", I get: > > root@beaglebone:~# modprobe ath9k_htc > ERROR: could not insert 'ath9k_htc': Invalid argument > > and dmesg | tail gives: > > [ 1418.895608] compat: disagrees about version of symbol mem_map > [ 1418.895666] compat: Unknown symbol mem_map (err -22) > > I got very similar messages when trying to modprobe (load?) the > pre-compiled ko module for ath9k_htc that I found through opkg (only many > more of them, for all different symbols). > > * Why, oh, why, oh, why. Did I mention I was exhausted? > > So I'm going to have three dongles, based on three different chipsets. Is > a consensus forming as to which one works (and how) with BBB? Oh well, I > hope the Asus N10 will just magically work... :(. > > Regards, Ben > -- For more options, visit http://beagleboard.org/discuss --- You received this message because you are subscribed to the Google Groups "BeagleBoard" group. To unsubscribe from this group and stop receiving emails from it, send an email to [email protected]. For more options, visit https://groups.google.com/groups/opt_out.
