Need guidance on where to start with wireless usb not working
Linux - NetworkingThis forum is for any issue related to networks or networking.
Routing, network cards, OSI, etc. Anything is fair game.
Notices
Welcome to LinuxQuestions.org, a friendly and active Linux Community.
You are currently viewing LQ as a guest. By joining our community you will have the ability to post topics, receive our newsletter, use the advanced search, subscribe to threads and access many other special features. Registration is quick, simple and absolutely free. Join our community today!
Note that registered members see fewer ads, and ContentLink is completely disabled once you log in.
If you have any problems with the registration process or your account login, please contact us. If you need to reset your password, click here.
Having a problem logging in? Please visit this page to clear all LQ-related cookies.
Get a virtual cloud desktop with the Linux distro that you want in less than five minutes with Shells! With over 10 pre-installed distros to choose from, the worry-free installation life is here! Whether you are a digital nomad or just looking for flexibility, Shells can put your Linux machine on the device that you want to use.
Exclusive for LQ members, get up to 45% off per month. Click here for more info.
Need guidance on where to start with wireless usb not working
Quick disclaimer:
Before anyone gets offended that I'm using Backtrack, it actually does serve a legitimate purpose. That's why I'm using it. That's what is required for many security classes. I'm at IT guy learning about security while going back to school for my master's in Information Assurance, and both my applied cypto class and network security class require the use of Backtrack. I'm not a script kiddie living in my mom's basement trying to break things.
Here's my problem, should you choose to help me:
Vmware seems to handle bridging kinda funky, so Backtrack5r3 running under vmware workstation on a windows 7 box cannot directly access the wireless card - it sees it as a regular wired connection. The workaround is to get a usb wireless, and in reading about these the alfa awus036 came up repeatedly, so I bought one. It works fine in windows, but in backtrack it cannot use it properly. I can power it on or off from bt (ifconfig wlan0 up) and I see the blue light go on and off, but it doesn't show any wireless networks.
Any suggestions on what driver to use and how to go about installing it? I did a little Unix system administration back in my dba days, but the last time I fiddled with Linux was when Slackware was becoming a popular distribution. A few things have changed since then.
I first went to the backtrack forum to see which cards were the most popular, and saw the Alfa awus036 come up.
I had no luck getting an answer to my question on that forum.
The card works fine in windows 7, but I've encountered mixed results in Backtrack. I followed a bunch of suggestions I found online,and over the course of a few hours still had no luck but managed to bugger up my vm enough to the point that deleting the vm and reinstalling backtrack seemed to make sense.
When my vm boots up, the light on the card comes on.
If I run an lsusb, I can see the device.
If I run iwconfig I can see the device.
If I run ifconfig wlan0 up/down I can see the light turn on and off.
If I open wicd, it finds no wireless networks. This is its current state.
At some point during my fiddling with drivers I was able to get it to show all wireless networks ONCE, but it failed to connect to my home network (citing bad password) even though my password was correct. At that point it tried to refresh the list of networks, and showed none. The only way to get the list back was to reboot, followed by the same problem: only willing to show me available networks once. I tried another driver and wasn't able to even get wicd app to work at all, at which point I decided a nuke & pave was the best option.
So at this point I'm back to BT5r3, installed to a vm (not live cd). I can see the card in lsusb, and can turn it on and off with ifconfig, but that's it.
Any hints on where to go next would be appreciated.
Clearly my google skills are weak. I tried "wireless usb awus036nhr: and "backtrack awus036nhr" and a few others, and STILL managed to miss the site you mentioned.
One mentioned it worked out of the box with BT5R2, so I started from scratch and downloaded and install BT5R2 only to encounter the same issues.
Next I tried getting the driver from alfa's site to compile, but it couldn't find eeprom_93xx46.c, so I tried taking that line out of the makefile. It got a little further and died on digsy_mtc_eeprom.c, so I edited that one out as well. The next comile error was with util.c, but I saw that subdirectory had a util.c.orig. I did a diff and the only change was a single line which happened to be teh line it was bombing on, so I switched teh two files. After that the compile bombed on nl80211.c, and I was unable to find a way around that one.
So here I am, all excited, thinking that I'm on the verge of greatness with this thing. I download the driver referenced on the page you mentioned, but much to my chagrin, I noticed Chrome put a (1) after the filename - this was a driver I had already tried (unsuccessfully) a few iterations and 48 hours ago. At this point I was near tears, but I'm blaming it on the onions I just chopped up for a breakfast burrito.
On a good note, although the driver was the same, the page you referenced was different, and in the comments section it mentions two *.c files that you can edit to get past one of the many errors I've seen since I started this. I'm going to edit the files now and see if I can install the driver.
ETA:
I edited teh two files, removed the .gz file (otherwise it overwrites my hard work) and the script now completes!
So I got the script to complete,and even rebooted for good measure since old windows habits are difficult to break.
The card powers on. I can see it when I type lsusb, ifconfig, or iwconfig. If I type "iwlist wlan0 scanning | grep ESSID", I can see my home network that I'm trying to connect to.
Here's the rub - starting the wicd network manager still won't show any wireless networks.
Am I better off scrapping everything and figuring out how to shrink down my windows partition and try dual booting?
So here's the next step in my saga. I figured I'd give it a try as a dual boot and see in vmware is what was causing all of my problems. I shrink my windows partition down by 40gb, burn backtrack5r3 iso to a dvd, and try to install backtrack natively. First problem I run into is that when booting off the dvd, my pc hangs every time I try to type startx. This is solved by hitting tab just as the boot menu for BT comes up, and then you can edit the startup line. I replaced what was there with "quiet splash i915.modeset=1 vga=791". That seemed to work. This wasn't my first edit to that line, but after a few dozen various permutations, that is the one that worked.
Now that I can type startx without hanging, I tried installing backtrack. It did install, but only after making a mess out of my partitions - it ignored teh 40gb partition I was trying to use, and shrunk my windows partition down by another 150gb, so now I have a windows partition 190 gb smaller than when I got up this morning, and I have a 40gb partition doing absolutely nothing.
Once installed, the startup kept bombing until I was able to edit /etc/default/grub to the same keywords I used for the livecd.
So at this point, Backtrack is running from a dual boot, and windows still works.
However, I still have a couple of problems. First, backtrack is wwaayyy slower when typing in a terminal window. When installing a package and hitting 'Y' to continue, the y key I hit took about 4-5 seconds before it shows up on the terminal window. Not sure what this is all about.
Second, I can finally see wireless networks in wicd "yay" but connecting to one (my own) still doesn't work.
On a good note, I'm slowly learning about things, and at this point I can try to get my virtual BT working with wireless, or the physical install.
Now I need to see if I can get back some partition space for windows.
Slowness on hard drive install may be graphics or something else related. Was a md5sum performed on downloaded backtrack iso before a install? You can also run
Code:
top
or
Code:
htop
to see what is gobbling up cpu or ram when you think things are running slow.
Lastly. Being a SLACKWARE forum. Leave the words Slackware and popularity out of your threads. It is probably why I
hear the crickets chirping in this thread.
Happy Trails and Good Luck with your Masters from a GED educated Tattoed Linux Biker. Rok
2nd Edit: Did you put wlan0 or whatever wireless interface shows in wicd>preferences>wireless interface box then and hit the refresh button. P.S. I am past my bedtime and beat. So play with wicd prefernces a bit like advanced setting, make sure wext and play with dbm (you can always switch it back) and make sure Backend is set on external.
Last edited by rokytnji; 02-24-2013 at 10:51 PM.
Reason: Forgot sumthing
Lots to try there. I'm back at work so I'll try this stuff tonight and report back.
Slowness seems to be related to gui. When installed on a VM on my laptop, speed is fine, but when installed natively, echoes to the screen or moving a window have a very noticeable lag. Sometimes echoing characters would take 1-3 seconds to appear on the screen.
I switched to Gnome which is marginally better speedwise, but not by much. Something is taking up cpu related to x windows. Laptop is quad core with 8gb of memory, so it shouldn't be this slow with nothing running.
To compare, when I'm running windows 7, I can have a windows 7vm plus a backtrack vm both running at the same time, and the backtrack vm is far faster than just BT running natively.
ot@bt:~#
root@bt:~#
root@bt:~# ip addr show
1: lo: <LOOPBACK,UP,LOWER_UP> mtu 16436 qdisc noqueue state UNKNOWN
link/loopback 00:00:00:00:00:00 brd 00:00:00:00:00:00
inet 127.0.0.1/8 scope host lo
inet6 ::1/128 scope host
valid_lft forever preferred_lft forever
2: eth0: <BROADCAST,MULTICAST,UP,LOWER_UP> mtu 1500 qdisc pfifo_fast state UP qlen 1000
link/ether b4:99:ba:e1:2a:56 brd ff:ff:ff:ff:ff:ff
inet 192.168.2.2/24 brd 192.168.2.255 scope global eth0
inet6 fe80::b699:baff:fee1:2a56/64 scope link
valid_lft forever preferred_lft forever
3: wlan1: <BROADCAST,MULTICAST> mtu 1500 qdisc noop state DOWN qlen 1000
link/ether 00:24:d7:a3:7b:ac brd ff:ff:ff:ff:ff:ff
4: wlan0: <NO-CARRIER,BROADCAST,MULTICAST,UP> mtu 1500 qdisc mq state DOWN qlen 1000
link/ether 00:c0:ca:66:17:f3 brd ff:ff:ff:ff:ff:ff
root@bt:~# ip link show
1: lo: <LOOPBACK,UP,LOWER_UP> mtu 16436 qdisc noqueue state UNKNOWN
link/loopback 00:00:00:00:00:00 brd 00:00:00:00:00:00
2: eth0: <BROADCAST,MULTICAST,UP,LOWER_UP> mtu 1500 qdisc pfifo_fast state UP qlen 1000
link/ether b4:99:ba:e1:2a:56 brd ff:ff:ff:ff:ff:ff
3: wlan1: <BROADCAST,MULTICAST> mtu 1500 qdisc noop state DOWN qlen 1000
link/ether 00:24:d7:a3:7b:ac brd ff:ff:ff:ff:ff:ff
4: wlan0: <NO-CARRIER,BROADCAST,MULTICAST,UP> mtu 1500 qdisc mq state DOWN qlen 1000
link/ether 00:c0:ca:66:17:f3 brd ff:ff:ff:ff:ff:ff
ot@bt:~#
root@bt:~#
root@bt:~# ip addr show
1: lo: <LOOPBACK,UP,LOWER_UP> mtu 16436 qdisc noqueue state UNKNOWN
link/loopback 00:00:00:00:00:00 brd 00:00:00:00:00:00
inet 127.0.0.1/8 scope host lo
inet6 ::1/128 scope host
valid_lft forever preferred_lft forever
2: eth0: <BROADCAST,MULTICAST,UP,LOWER_UP> mtu 1500 qdisc pfifo_fast state UP qlen 1000
link/ether b4:99:ba:e1:2a:56 brd ff:ff:ff:ff:ff:ff
inet 192.168.2.2/24 brd 192.168.2.255 scope global eth0
inet6 fe80::b699:baff:fee1:2a56/64 scope link
valid_lft forever preferred_lft forever
3: wlan1: <BROADCAST,MULTICAST> mtu 1500 qdisc noop state DOWN qlen 1000
link/ether 00:24:d7:a3:7b:ac brd ff:ff:ff:ff:ff:ff
4: wlan0: <NO-CARRIER,BROADCAST,MULTICAST,UP> mtu 1500 qdisc mq state DOWN qlen 1000
link/ether 00:c0:ca:66:17:f3 brd ff:ff:ff:ff:ff:ff
Plus I am confused by 2 wireless interface reports. wlan1 and wlan0.
Seems like you have duplicate wireless hardware on your gear which between backtrack and mutiple hardware interfaces is beyond my skillset.
Either that or it is just friggin late and I am only up because of Windows SP1 fubar updates. Which is screwing up my attitude.
Oddly I have to bring my wlan0 up with ifconfig by assigning it an ip and such before I can use dhclient on wlan0 to connect to a network. Probably power management related.
Oddly I cannot bridge ethernet to wireless in 3+ kernels, but I can in 2.6 kernels. Or it could be some other difference between debian squeeze and debian sid.
As far as drivers for a given device, googling on the vendor id and product id normally narrows the list down pretty fast. lsusb shows that by default, and lspci -n for pci devices shows that.
You don't need to do anything with your windows drive to dual boot linux. You can put linux on a usb stick and boot it from there. $20 gets you a 32GB stick these days. Although a more expensive class 6 or better sdhc card + reader might feel less laborious. You could probably do most of that install in the vm to avoid excessive writes to the usb stick and clone it to the stick.
Although that guide lacks a few admin steps that most of the other install methods tend to help out with. Like setting a root password so you can log into that new install when you do boot it. I'm tending to do all my installs this way these days as you can apt-get install all the network drivers before you ever boot your install.
LinuxQuestions.org is looking for people interested in writing
Editorials, Articles, Reviews, and more. If you'd like to contribute
content, let us know.