Hi Bjørn,
On Thursday 27 Aug 2009 17:39:21 Bjørn Mork wrote: > > Setting level 3: > > nemi:/etc# echo 3 > /sys/class/net/wlan0/device/power_level > nemi:/etc# cat /sys/class/net/wlan0/device/power_level > SYSTEM:auto MODE:fixed INDEX:3 > > Setting level 0: > > nemi:/etc# echo 0 > /sys/class/net/wlan0/device/power_level > nemi:/etc# cat /sys/class/net/wlan0/device/power_level > SYSTEM:auto MODE:fixed INDEX:0 > > Notice how this is different from the default "MODE:auto". > > > Setting level 6 restores the default: > > nemi:/etc# echo 6 > /sys/class/net/wlan0/device/power_level > nemi:/etc# cat /sys/class/net/wlan0/device/power_level > SYSTEM:auto MODE:auto INDEX:0 > > > However level 7 seem to be gone, as reported by Clemens: > > nemi:/etc# echo 7 > /sys/class/net/wlan0/device/power_level > bash: echo: write error: Invalid argument > > > So there still is a difference between 0 and 6. I have absolutely no > idea which one should be used on AC, but I do note that 6 seems to be > the default. > > I'm not sure about this as I don't have that device. I'm copying Clemens since he was the one of first pointed the changes. > A side note: The "wireless" node seems to be gone in 2.6.30: > > nemi:/etc# ls -la /sys/class/net/wlan0/wireless > ls: cannot access /sys/class/net/wlan0/wireless: No such file or directory > > Again, on my box with ipw2200 device, 2.6.30 still presents the wireless folder. r...@champaran:/usr/share/man $ ls /sys/class/net/eth1/wireless/ beacon crypt fragment level link misc noise nwid retries status You must be using the newer iwlwifi drivers. Oops!!. There's LP Bug #369113 where I fixed similar bug for ipw2200. I'm not sure how the wireless folder has reappeared in 2.6.30. It was reported to not be present in 2.6.29. Sigh!! Perhaps wireless-tools is what should be used here too.... > > You may want to apply this or something similar to get 2.6.30 support. > I must admit that I didn't really understand the need for the > "-d $DEVICE/wireless" test. Testing the driver name should be safe > enough. > I'm not sure how you plan testing the driver name ? As wlan* ? Take my case, the wireless device is listed as eth1. Checking for the "wireless" folder's existence was one way to identify it a wireless device. The sysfs breakage is one reason why I want to rely on tools instead. Or if we were using a high level language, libraries. Ritesh -- Ritesh Raj Sarraf RESEARCHUT - http://www.researchut.com "Necessity is the mother of invention."
signature.asc
Description: This is a digitally signed message part.
