Wireless will connect with NetworkManager, but nothing else

synack_sa · #1 29th September 2009, 06:21 AM

Hi All

I'm having a problem. Starting off with Gnome, I was easily able to connect to the wireless network and browse/ping/etc no problem. It's been a while since I working in Linux and I've always preferred lightweight IDE's like fluxbox and Enlightenment. I've installed both, but have been struggling to get wireless networking working in either of them. This isn't a problem with the IDE's so much as it is a problem with the fact that NetworkManager doesn't work with either of them.

I've installed WICD on my laptop and in the configuration of system-config-network, I've made sure that the option "Controlled by NetworkManager" is unticked. As soon as I do this and try to use a program like WCID to work with wlan0, it just breaks.

If I try do a ifup wlan0, I get the error message "Error for wireless request set mode 8b06".

Any ideas?

SynAck

scottro · #2 29th September 2009, 10:25 AM

NetworkManager can be a bit of a nuisance if you don't use it.

I have a page that deals with making sure it's not running.

http://home.roadrunner.com/~computer.../wireless.html

synack_sa · #3 29th September 2009, 06:31 PM

Okay, I followed your guide and I ran into the same problem I did when I was doing it myself.

Here's a run down:
ifconfig after reboot

Code:

wlan0     Link encap:Ethernet  HWaddr 00:24:D2:CE:FA:33  
          BROADCAST MULTICAST  MTU:1500  Metric:1
          RX packets:0 errors:0 dropped:0 overruns:0 frame:0
          TX packets:0 errors:0 dropped:0 overruns:0 carrier:0
          collisions:0 txqueuelen:1000 
          RX bytes:0 (0.0 b)  TX bytes:0 (0.0 b)

ifup wlan0 after reboot

Code:

ifup wlan0
Error for wireless request "Set Mode" (8B06) :
    SET failed on device wlan0 ; Invalid argument.

Determining IP information for wlan0... failed.

If it make any difference, I'm posting this right now, from my laptop which is now connected again with NetworkManager. I really would like to get around this if possible.

Thanks

SynAck

scottro · #4 29th September 2009, 07:16 PM

It seems it has to do with the mode setting. Not sure why or what. Googling the error (just the first line,) brings up several possible solutions. I guess I would try one of them. (Not the ones from this forum though, that rather old thread doesn't seem to have solved it. There's a few on linuxquestions, however, where they did solve it.)