On Fri, Jul 10, 2009 at 3:35 PM, Thiemo Nagel<[email protected]> wrote: > Corentin Chary wrote: >> On Fri, Jul 10, 2009 at 12:23 PM, Thiemo Nagel<[email protected]> wrote: >>> I just tested the new GSM rfkill in 2.6.31-rc2 and I get the following on my >>> EeePC 1000HGO: >>> >>> eee:/# cat /sys/class/rfkill/rfkill2/name >>> eeepc-wwan3g >>> eee:/# echo 0 > /sys/class/rfkill/rfkill2/state >>> bash: echo: write error: Operation not permitted >>> >>> What could be the reason for that? >> >> Reading the kernel source I can find: >> /* >> * The intention was that userspace can only take control over >> * a given device when/if rfkill-input doesn't control it due >> * to user_claim. Since user_claim is currently unsupported, >> * we never support changing the state from userspace -- this >> * can be implemented again later. >> */ >> >> It seems that rfkill should be controlled by /dev/rfkill (cf >> Documentation/rfkill.txt). >> Maybe network-manager can control that .. But I'm not sure. >> Maybe you should CC the wireless mailing list. > > Thanks for the quick reply. The interesting thing is, that the direct > access works well for eeepc-wlan and eeepc-bluetooth rfkills. I've CC'd > debian-eeepc-devel, maybe they know something. >
Are you sure that it works with newer kernels ? This commit should have broken it for all rfkill. commit 19d337dff95cbf76edd3ad95c0cee2732c3e1ec5 Author: Johannes Berg <[email protected]> Date: Tue Jun 2 13:01:37 2009 +0200 -- Corentin Chary http://xf.iksaif.net - http://uffs.org _______________________________________________ Debian-eeepc-devel mailing list [email protected] http://lists.alioth.debian.org/mailman/listinfo/debian-eeepc-devel
