Quoting Bart Samwel <b...@samwel.tk>: > > Thanks for reporting and contributing. Apparently we cannot tell the > driver to use a certain power level when the hardware is disabled... > This is a shame, because the power level will be incorrect when the > device is re-enabled -- laptop mode tools doesn't re-apply settings when > interfaces are enabled or disabled. > > I wonder, does this problem happen only when the hardware kill switch is > used? Or does this already go wrong if you just do an ifdown on your > device (as indicated by /sys/class/net/$DEVICE/operstate)? I wonder if > there are other things that can't be used if the device's radio is > killed. Might be worth a submitting a bug report to the iwl guys... > > Cheers, > Bart >
Hello again Bart, When I submitted the bug, the wireless was killed by the hardware rf switch on boot. If it is killed by the switch, cat /sys/class/net/wlan0/device/enable gives "0" cat /sys/class/net/wlan0/operstate gives "down" Now, if i turn the rf switch to "on" and keep the interface down: cat /sys/class/net/wlan0/device/enable gives "0" cat /sys/class/net/wlan0/operstate gives "down" During ifconfig ups/ifconfig downs /sys/../operstate remains "down", /sys/../enable changes according to up/down. As it seems, for operstate to work i have to be connected to an ap. ifconfig wlan0 up just doesn't change it. In my /etc/network/interfaces i have no section for wlan0. The /sys/class/net/wlan0/device/enable maybe better for laptop-mode, because many people don't have an rf switch or are not connected to ap at boot. -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org
