http://bugzilla.novell.com/show_bug.cgi?id=548266 http://bugzilla.novell.com/show_bug.cgi?id=548266#c2 --- Comment #2 from Gruber Wolfgang 2010-01-04 16:54:04 UTC --- @Tamás Németh: Have you found a workaround for this until this bug is solved? It is very complicated to always go into BIOS if i need Bluetooth. Thanks Wolfgang -- Configure bugmail: http://bugzilla.novell.com/userprefs.cgi?tab=email ------- You are receiving this mail because: ------- You are on the CC list for the bug.

http://bugzilla.novell.com/show_bug.cgi?id=548266 http://bugzilla.novell.com/show_bug.cgi?id=548266#c4 --- Comment #4 from Tamás Németh 2010-02-15 17:45:11 UTC --- (In reply to comment #2)

@Tamás Németh: Have you found a workaround for this until this bug is solved? It is very complicated to always go into BIOS if i need Bluetooth.

Thanks Wolfgang

Yes, if you are interested in it, I've found a workaround here: https://bugs.launchpad.net/linux/+bug/404626 Start the machine with both wlan and bluetooth turned on from BIOS, and the you will be able to swich wlan by either fn+F2 or toggling (between 0 and 1) the value of /sys/devices/platform/eeepc/rfkill/rfkill1/state. And, in addition you will be able to turn on/off bluetooth by doing the same to /sys/devices/platform/eeepc/rfkill/rfkill2/state, like: echo 0 > /sys/devices/platform/eeepc/rfkill/rfkill2/state or echo 1 > /sys/devices/platform/eeepc/rfkill/rfkill2/state I've also tried it by staring the machine with bluetooth off (and optionally loading these kernel modules: rfcomm, sco, bnep, l2cap, btusb and bluetooth), but it didn't work for me. Dear developers, can you turn this workarounf info into a final solution? -- Configure bugmail: http://bugzilla.novell.com/userprefs.cgi?tab=email ------- You are receiving this mail because: ------- You are on the CC list for the bug.

https://bugzilla.novell.com/show_bug.cgi?id=548266 https://bugzilla.novell.com/show_bug.cgi?id=548266#c6 --- Comment #6 from Tamás Németh 2010-11-19 13:00:40 UTC --- (In reply to comment #5)

Isn't this anyhow better with the latest kernel which I see you have installed? The rfkill eeepc handling was rewritten in 2.6.34 or alike.

It's not better, but seems to be a bit different. The killswitch still doesn't affect bluetooth, so I still have echo numbers into the sysfs files, however now it's possible to start the machine with disabled bluetooth and activate it later (until now I had to start it with bluetooth turned on), but despite switching it off afterwards, KDE still sees it as switched on. Weird. The other problem is that pressing the killswitch a few times consecutively caused a kernel panic. -- Configure bugmail: https://bugzilla.novell.com/userprefs.cgi?tab=email ------- You are receiving this mail because: ------- You are on the CC list for the bug.

https://bugzilla.novell.com/show_bug.cgi?id=548266 https://bugzilla.novell.com/show_bug.cgi?id=548266#c8 Uwe Drechsel changed: What |Removed |Added ---------------------------------------------------------------------------- Status|NEW |CLOSED Resolution| |WONTFIX --- Comment #8 from Uwe Drechsel 2011-08-26 12:53:29 CEST --- The lifecycle of openSUSE 11.2 ended on May 12th 2011. I'm closing this bug to make it easier to focus on upcoming releases. Thank you for reporting this issue and we are sorry that we have not be able to fix it before this version reached its end of life. If you would still like to see this bug fixed and are able to reproduce it against a maintained version, please reopen this bug and change the 'version' of this bug to the applicable version. -- Configure bugmail: https://bugzilla.novell.com/userprefs.cgi?tab=email ------- You are receiving this mail because: ------- You are on the CC list for the bug.