wlan0 working, but... not really working... any help?
I recently had a problem with my home partition under an Ubuntu 10.04 install on my Inspiron 1545. I've been considering switching to Debian for a while and I figured that I would just switch instead of try to fix the problem.
I used the Debian x86_64 net install disk, but part way through, I received a message stating that I had to load wireless drivers from external media. I did this and got through the install with no problems. My problem now is that I cannot get nm-applet to recognize ANY wireless networks. The computer automatically connects to my home network (the one I set up in for the install) but nm-applet won't recognize anything, even the network the computer is connected to. I've been forced to pull up a terminal and use iwconfig everytime I want to connect to a new network, I like working CLI, but you can probably imagine how annoying that can be at times. Does anyone have any ideas as to why this may be, and how I can fix it? If more info is needed to find the problem, let me know and I'll be happy to provide it. Thank you in advance for any help. |
My first question would be, what is the model of your wireless card?
I believe an lspci -v would provide the details we would need. Then possibly an lsmod to determine what modules are loaded. You said you loaded external drivers, what drivers did you load? |
lspci output:
Code:
0c:00.0 Network controller: Intel Corporation WiFi Link 5100 Code:
Module Size Used by |
What does dmesg | grep iwl
output? |
dmesg | grep iwl output:
Code:
[ 5.903844] iwlagn: Intel(R) Wireless WiFi Link AGN driver for Linux, 1.3.27ks |
What does iwlist scan output? If it displays the networks in the area, then it's most likely an issue with NetworkManager or nm-applet.
|
iwlist scan output:
Code:
lo Interface doesn't support scanning. |
That's the interesting thing. It means you can scan all the networks in the area just fine. That's essentially a listing of networks. It means that, most likely, your kernel driver is working and it's an issue with network manager. I'm not 100% sure where to go from here, other than recommending that you check out #nm on freenode if possible...
EDIT: output of sudo grep NetworkManager /var/log/daemon.log |
Here's SOME of the output: (it filled the terminal)
Code:
Feb 7 21:55:36 Hermes NetworkManager[1417]: <warn> bluez error getting default adapter: The name org.bluez was not provided by any .service files |
Ok, turned out the fix was in changing "managed=false" in /etc/NetworkManager/NetworkManager.conf into "managed=true"
Linux. It's so simple it's hard... :P |
Cool find :] I am glad you were able to get going.
|
All times are GMT -5. The time now is 08:49 AM. |