the auto line is actually also there on my post, right above the allow-hotplug. i thought maybe they didn’t play well together so i’ve also tried just one and just the other.
it’s currently working again but i’m not sure why this time it started up and for now i think i’ll just abuse the fact that linux normally doesn’t reboot to avoid this issue for as long as possible.
i’ve ordered the UWN100 adapter that seems more widely recommended (altho mostly for angstrom from what i read). i’m hoping maybe that works better.
i may be accidentally identifying correlation where there’s only randomness but this last time i got it recognized by booting to the edimax (which it always recognizes upon boot but never actually gets many packets through), and then pulling it out and using the allow-hotplug option to pop the KEEBOX in, and then it got recognized and actually works consistently. that’s a silly solution, but since this is just a device for my own uses, i’ll stick with it if it works.
So use duct tape and tape it to the side of the case ? Yeah,I am not being serious.
From memory the ones mentioned by Robert many moons AGO( heh ) were a bit longer than those tiny ones you’ve been playing with, But if you get that one working then this conversation is probably moot.
I too am in the same situation. I have spent countless hours trying to configure WiFi on, not one, but two BBB - a rev B and a rev C. I have also tried 3 different Linux distros - Ubuntu, Angstrom, and Debian; 3 different WiFi adapters (same chipset, but different manufactureres - all to no avail.
As a reference point, I was able to get WiFi running on 2 Raspberry Pis in less than 10 minutes from boot up.
i’m still having success with the KEEBOX which is the most minimal on the list of known supported wifi adapters. i’m curious about the physics of the problem that apparently the dongle needs to be away from the plane of the board, or something? is there any way to shield the board to prevent this? is there a way to wrap something on the board in shrink wrap, perhaps?
i’m sure there’s a ton of differences between the BBB and Raspberry Pi, but is it known what the key distinction is that causes this ground plane interference with the BBB but not the Raspberry Pi?
The issue makes the susceptibility of some dongles to interference worse. Some dongles work just fine. It is due to the closeness to the HDMI connector. The HDMI connector is grounded.
Just to add to the discussion. I’ve used Tiny and cheap ( $.50 ea ) bluetooth dongles in the past, and they seemed to install / operate fine. Problem was they all had the same MAC address, and I could not find a proper work around. So communicating between two of these was not possible.
I would think that bluetooth would be more of a problem since it is similar frequency, just lower power. But I am not exactly a hardware / radio person.
