| View previous topic :: View next topic |
| Author |
Message |
RaraRasputin
Tux's lil' helper
Joined: 04 Jun 2004
Posts: 142
Location: Germany
|
 Posted: Fri Jul 09, 2010 10:00 am Post subject: |
 |
|
| dE_logics wrote: | A very stupid advice --
Very unlikely to work. |
Sometimes the most easiest things work. I had installed a new kernel, and afterwards the "switch off wlan" button on my laptop worked for the first time to switch wlan off, but not to switch it back on again, and I received the "unknown error 132" as stated in the first post. Simply pulling wlan up with ifconfig worked.
So easy that I didn't even think about it. Thanks 
_________________
RaraRasputin, lover of the Russian Queen |
|
| Back to top |
|
 |
lkraav
Tux's lil' helper
Joined: 13 Oct 2004
Posts: 96
Location: Estonia
|
| Posted: Sat Jan 28, 2012 4:21 pm Post subject: |
|
|
During my last two laptops I have experienced wlan not coming up for these reasons:
* error -132 has meant that rfkill is blocking the device
* i was indeed missing iwl-6000-ucode
* i had wpa_supplicant compiled +gnutls -ssl, this is now the second time where using gnutls "just does not work (tm)", first experience with that was trying to use curl against microsoft IIS
thanks all for working on it here though, the microcode pointer helped. |
|
| Back to top |
|
|
|
|
You cannot post new topics in this forum
You cannot reply to topics in this forum
You cannot edit your posts in this forum
You cannot delete your posts in this forum
You cannot vote in polls in this forum
|
|
Networking & Security
