Public bug reported:

Hello. I use jaunty with latest software updates (Alpha5).
And there is some little issue in eeepc-laptop kernel module.

Bug: bluetooth rfkill interface doesn't work properly.
Note. I've checked it at asus eeepc 901; probably it works fine at other models.

Steps to reproduce:
boot latest available generic linux kernel and check bluetooth status (bt 
should be turned on after boot):
> cat /sys/class/rfkill/rfkill1/state
0
Try to change state:
> echo 1 | sudo tee /sys/class/rfkill/rfkill1/state
1
tee: /sys/class/rfkill/rfkill1/state: No such device
But file exists:
> file /sys/class/rfkill/rfkill1/state
/sys/class/rfkill/rfkill1/state: ASCII text

What happens:
1. even if bluetooth is on, "cat /sys/class/rfkill/rfkill1/state" returns 0.
2. there is no way to change bluetooth state via 
/sys/class/rfkill/rfkill1/state file.

What should happens:
1. if bluetooth is on, /sys/class/rfkill/rfkill1/state should contains 1, and 0 
in otherwise.
2. there is should be way to change /sys/class/rfkill/rfkill1/state value.

P.S. However, all other interfaces works well:
/sys/devices/platform/eeepc/camera for web camera
/sys/devices/platform/eeepc/cardr for cardreader
/sys/class/rfkill/rfkill0/state for wireless

P.P.S. In attachment - patch, which fixes it - after patching and rebuilding 
kernel, value is sets in 1 if bt turned on, and in 0 if it is turned off, and 
user have ability to change value on the fly, but there is two things:
1. I didn't write it; I've just found it in Internet.
2. There is no any copyrights or author's info, so I don't sure, is it possible 
for Kernel Team include this patch into Ubuntu's version of Linux kernel.

** Affects: linux (Ubuntu)
     Importance: Undecided
         Status: New

-- 
[eeepc-laptop] bluetooth rfkill interface doesn't work properly at 901 model
https://bugs.launchpad.net/bugs/341970
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.

-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs

Reply via email to