On Sun, May 25, 2008 at 02:59:03PM +0200, Bart Samwel wrote: > Hi Graziano, > > Bart Samwel wrote: > > graziano wrote: > >> I"m sorry to be a spammer today, but I found out that commenting out the > >> asus-wireless even brought back my wireless. Now Fn+F2 works for > >> bluetooth, but not wlan (which suits me better than the previous > >> behaviour). So I think it is a problem with a double toggling the status > >> of the wireless, which makes it impossible to turn it on again. > > If I am correct, the problem is caused by the code in > /etc/acpi/start.d/60-asus-wireless-led.sh. There are two possible scenarios: > > * isAnyWirelessPoweredOn incorrectly returns false for your hardware > * setLEDAsusWireless also toggles the hardware, not only the LED
setLEDAsusWireless also seems to toggle the hardware. If I start with wlan set to 1, and rf_kill to 0, writing 0 to wlan (what setLEDAsusWireless does) also changes rf_kill to 2. So it seems that wlan controls the hardware kill. When I rmmod and modprobe the ipw2200 module, I also see: ipw2200: Radio Frequency Kill Switch is On: Kill switch must be turned off for wireless networking to work. I don't get this message on boot, because than the kill switch hasn't been activated yet. I don't bring my wireless up automaticly at boot, so the operstate says "down" when booting, and the wireless gets completly disabled (wlan 0). This part seems to be good for me, since it's just a waste of power when I don't use it. However, pressing Fn+F2 to enable the wireless doesn't seem to work properly, since the wlan never gets written anymore. Kurt -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
