Can't turn off/on bluetooth via acpi in eeepc 901/1000

Bug #267768 reported by Giovanni Masucci
4
Affects Status Importance Assigned to Milestone
Linux
Fix Released
Medium
eeepc-acpi (Ubuntu)
Incomplete
Undecided
Unassigned
Nominated for Intrepid by Giovanni Masucci

Bug Description

In ubuntu hardy on eeepc 901/1000 it's impossible to turn off/on the integrated bluetooth.
This patch from daltona solves the issue. It has already been tested in the costum eeepc kernel by Adam Mc Daniel:

http://forum.eeeuser.com/viewtopic.php?pid=304343#p304343

<code>
diff -urN eeepc-acpi/eeepc_acpi.c eeepc-acpi-bt/eeepc_acpi.c
--- eeepc-acpi/eeepc_acpi.c 2008-02-08 18:39:56.000000000 +0100
+++ eeepc-acpi-bt/eeepc_acpi.c 2008-06-27 15:38:03.000000000 +0200
@@ -38,6 +38,7 @@
  * Definitions for Asus EeePC
  */
 #define PROC_ASUS "asus" //the directory
+#define PROC_BT "bt"
 #define PROC_LCD "lcd"
 #define PROC_BRN "brn"
 #define PROC_DISP "disp"
@@ -90,7 +91,7 @@
 } cm_asl_t;

 const char *cm_getv[] = {
- "WLDG", NULL, NULL, NULL,
+ "WLDG", "BTHG", NULL, NULL,
     "CAMG", NULL, NULL, NULL,
     NULL, "PBLG", NULL, NULL,
     "CFVG", NULL, NULL, NULL,
@@ -99,7 +100,7 @@
 };

 const char *cm_setv[] = {
- "WLDS", NULL, NULL, NULL,
+ "WLDS", "BTHS", NULL, NULL,
     "CAMS", NULL, NULL, NULL,
     "SDSP", "PBLS", "HDPS", NULL,
     "CFVS", NULL, NULL, NULL,
@@ -283,6 +284,8 @@
         return -ENODEV;
     if (ehotk->cm_supported & (0x1 << CM_ASL_WLAN))
         eeepc_hotk_new_proc(PROC_WLAN, CM_ASL_WLAN, mode, device);
+ if (ehotk->cm_supported & (0x1 << CM_ASL_BLUETOOTH))
+ eeepc_hotk_new_proc(PROC_BT, CM_ASL_BLUETOOTH, mode, device);
     if (ehotk->cm_supported & (0x1 << CM_ASL_CAMERA))
         eeepc_hotk_new_proc(PROC_CAMERA, CM_ASL_CAMERA, mode, device);
     if (ehotk->cm_supported & (0x1 << CM_ASL_DISPLAYSWITCH))
@@ -306,6 +309,8 @@
     if (acpi_device_dir(device)) {
         if (ehotk->cm_supported & (0x1 << CM_ASL_WLAN))
             remove_proc_entry(PROC_WLAN, acpi_device_dir(device));
+ if (ehotk->cm_supported & (0x1 << CM_ASL_BLUETOOTH))
+ remove_proc_entry(PROC_BT, acpi_device_dir(device));
         if (ehotk->cm_supported & (0x1 << CM_ASL_CAMERA))
             remove_proc_entry(PROC_CAMERA, acpi_device_dir(device));
         if (ehotk->cm_supported & (0x1 << CM_ASL_DISPLAYSWITCH)
</code>

Revision history for this message
Giovanni Masucci (gio-grifis) wrote :

I forgot to say that this bug is also present in intrepid kernel 2.6.27, that from what I've understood, doesn't use eeepc-acpi.ko, but eeepc-laptop.ko
OT:
I don't know if there's much difference between the two, I only know that eeepc-acpi seems to work much better than eepc-laptop on my eeepc 901.
With eeepc-laptop osd are very laggy and I also can't control webcam via acpi.
So it would seem that the best solution is to patch eeepc-osd for bluetooth and include it in the kernel instead of eeepc-laptop, but I'm no expert to take such decision.

Revision history for this message
Sitsofe Wheeler (sitsofe) wrote :

The issues with eeepc-laptop are related to the EC GPE storm bug changes. There are patches that restore the speed of hotkeys. See http://bugzilla.kernel.org/show_bug.cgi?id=11549 . It looks like eepc-acpi is deprecated and Debian appear to be dropping it - http://<email address hidden>/msg38682.html .

Revision history for this message
Giovanni Masucci (gio-grifis) wrote :

with latest 2.6.27 kernel I can now control the webcam via eeepc-laptop ...bluetooth support is still missing or not working

Revision history for this message
Sitsofe Wheeler (sitsofe) wrote :

This is known by the eeepc-laptop devs and in fact the patch for solving this is small (it's just a matter of adding another verb in the kernel driver). It's unlikely the fix will land before 2.6.27 is released though...

Changed in linux:
status: Unknown → Fix Released
Revision history for this message
Sitsofe Wheeler (sitsofe) wrote :

Can this issue be reproduced in Ubuntu 10.04?

Changed in eeepc-acpi (Ubuntu):
status: New → Incomplete
Changed in linux:
importance: Unknown → Medium
To post a comment you must log in.
This report contains Public information  
Everyone can see this information.

Other bug subscribers

Remote bug watches

Bug watches keep track of this bug in other bug trackers.