While trying to configure network with net-setup, I was getting wlan0 unassociated because of the following error: RTNETLINK answers: Unknown error 132 After searching a bit, I found that it's caused by rfkill softblocking the device. It can be unblocked with the following: # rfkill list -> it will show the kind of blocker causing the problem # rfkill unblock all -> to unblock it and let network to work I think that a note to this should be added to handbook as it's non intuitive to find the solution. Thanks a lot Reproducible: Always
It is not necessary to install the rfkill package for this. The controls can also be reached via /sys/class/rfkill
OK, thanks for the info :)
This is not an acceptable solution. We need something non-intrusive. At no point should users ever touch /sys/.
Does any option to be passed to kernel command line do the same? Maybe it would prevent people from having to change /sys values... :-/
The added information should make it clear that there are machines with physical switches which are mapped to rfkill (like the Thinkpads). I don't assume that their values can still be changed through software.
I'm on the same line as Jan; I'm also not confident if documenting rfkill would suffice. There are two types of locks, hard and soft. The soft ones can be managed by rfkill, but hard ones can't. I have an Intel wireless (one that uses the ipw2200 module) which I have to unlock through a key combination (rfkill is not possible here). If rfkill is available on the installation media (minimal livecd) I wouldn't mind adding a paragraph about it (but that would be more something like """ Some wireless cards are deactivated by default. To activate them, please consult your hardware documentation. Some of these cards can be unblocked using the rfkill application. If that is the case, use "rfkill list" to see the available cards and "rfkill unblock <index>" to activate the wireless functionality. """
I am happy with that paragraph, in my case, I tried several ways to unlock it until rfkill fixed the problem :-/
I've added the paragraph to the wireless part of the handbook/networking instructions.