On Mon, 22 Nov 2010, Larry Finger wrote: > On 11/22/2010 02:59 AM, Klaas De Craemer wrote: > > > > Sorry, I meant I get a few errors in the form of "SIOCSIFFLAGS: > > Unknown error 132" on the stdout when trying to bring up the blocked > > interface. > > Do those errors also occur when it works, or just when it is blocked? Just a small side note: I receive the same error message for "ifconfig wlan0 up" whenever rfkill is active for a wlan device - using iwl3945 and iwlagn here. So I would not look too deep into this message in case rfkill is on. (Not that we could not use a better error message in this case, or perhaps just also a printk - took me quite a while to figure it out at first) c'ya sven-haegar -- Three may keep a secret, if two of them are dead. - Ben F. -- To unsubscribe from this list: send the line "unsubscribe linux-wireless" in the body of a message to majordomo@xxxxxxxxxxxxxxx More majordomo info at http://vger.kernel.org/majordomo-info.html
