|Date Added:||12 December 2012|
|File Size:||67.83 Mb|
|Operating Systems:||Windows NT/2000/XP/2003/2003/7/8/10 MacOS 10/X|
|Price:||Free* [*Free Regsitration Required]|
Device supports scan flush.
I hope this will give you enough info to narrow down your problem. It should be rtlcu for v1, but if you have v2 the above-referenced WikiDevi page says that there is a special, pre-compiled binary driver for the Raspberry which is located here.
Arch Linux ARM • View topic – [SOLVED] Issues with WIFI on cubox-i
This package is based on the source of this GitHub repository owned by Jens Segers who actually wrote an article with the instructions to install it so if you’re not on Archlinux, these may be useful. Amazon read it would work out of the box but it didn’t.
Have you tried a sanity test n8l0211 connecting your BBB to a known, working wireless access point? So I followed several tutorials to have the driver working.
If furthermore you wish to find out which USB adaptor can be put into AP mode, I am afraid there is no really authoritative list, mostly because of the manufacturers: As a common cost-cutting measure, wireless adapter manufacturers will revise an existing product’s specifications, substituting a different chipset or other components without changing the formerly Linux-compatible product’s model number.
To view someone’s posting history, sign in, click on their user name, then on “Search User’s Posts. These codes, though not accessible through lspcican be seen from the output of lsusb. I try to found a solution on internet, but found nothing that works. Note I only use wired, but thought I would pipe zrch some basic debugging comments.
Arch Linux ARM • View topic – WLAN: nl not found
Please correct me if I am arrch. Sign up or log in Sign up using Google. I think wifi-menu is part of netctl which is different.
For v1, I found this online lnuxfor v2 instead I found this. Perhaps the driver of your card only supports the old WEXT interface, not nl?
Manufacturers don’t help matters much, often using strange naming conventions that produce numerous confusingly similar model names and numbers. I know this question is kind of old, but for the next ones who will have this problem, this could save them some time: Now it is important to learn which driver you are using.
But not in that way: