Microsoft Bluetooth mouse 2.0 does not work

Bug #23967 reported by Daniel
12
Affects Status Importance Assigned to Milestone
bluez-hcidump (Ubuntu)
Fix Released
High
Charles Majola
Dapper
Invalid
High
Unassigned

Bug Description

Bleutooth card : Dell truemobile 350 internal bluetooth
Mouse Microsoft Intellimouse for Bluetooth 2.0 - no dongle
Bluez protocol stack
Ubuntu Breezy Badger
Dell inspiron 6000 laptop.

Scroll wheel not working. When i use Xev, Imwheel and Hcidump my scroll wheel
and my Forward/Back buttons are not recognized and i cannot use them.
I have tried everything, even crashed my X server 7 times :)

If you have any knowledge on how to make these work please respond to
<email address hidden>

Revision history for this message
Charles Majola (chmj) wrote :

Can you please tell me how are you using the mouse, with hidd or the built in bt
device is a hid proxy?

if using hidd please stop bluetooth services by typeing "sudo
/etc/init/d/bluez-utils stop" and then attach the output of "sudo hidd -n"

You might want to read this about bug reports :
http://www.chiark.greenend.org.uk/~sgtatham/bugs.html

Revision history for this message
Daniel Vollmer (maven) wrote :

Hi!

I've had the same problem and gotten a bit further along with this:
The Breezy Ubuntu kernel (2.6.12) only includes rudimentary bluetooth support
for this mouse (or maybe other mice in general) because it only includes the
bootp-protocoll (for BT mouse support in the first place you have to edit
/etc/defaults/bluez-utils and set HIDD_ENABLED to 1).
I backported the bluetooth patches (http://www.bluez.org/patches.html), except
for PCMCIA support, to the Ubuntu kernel and suddenly the mouse worked in HID
mode including the wheel.
I think it is rather unlikely that the official Ubuntu kernel will be updated,
but maybe these patches could be included in next update (2.6.12-9.24)?

The assigned package should be changed to "linux" or "kernel" as bluez-utils
works just fine with the correct kernel implementation.

Revision history for this message
Charles Majola (chmj) wrote :

Thanks, I will get the patch included in the default kernel, just need to test
is some more during this release cycle.

Revision history for this message
meba (jakub-rtfm) wrote :

I am willing to test it too, using 2.6.15-14-386 from Dapper Drake, which is suffering the same problem. MH patch is a must :)

As you requested, hidd -n show nothing. I am attaching some debugging output i found, just let me know if you want more (I would really like to get my mouse working, i buyed it a week ago :)
root@arkeia:/usr/src# hcitool inq
Inquiring ...
        00:0D:3A:A3:FB:11 clock offset: 0x7b91 class: 0x002580
root@arkeia:/usr/src# hcitool info 00:0D:3A:A3:FB:11
Requesting information ...
        BD Address: 00:0D:3A:A3:FB:11
        Device Name: Microsoft Mouse
        LMP Version: 1.2 (0x2) LMP Subversion: 0x100
        Manufacturer: Broadcom Corporation (15)
        Features: 0xbc 0x02 0x04 0x28 0x08 0x08 0x00 0x00
                <encryption> <slot offset> <timing accuracy> <role switch>
                <sniff mode> <RSSI> <power control> <enhanced iscan>
                <interlaced pscan> <AFH cap. slave> <AFH cap. master>

I am using IBM R52 with integrated bluetooth.

Revision history for this message
meba (jakub-rtfm) wrote :

Well, i am changing priority of this bug, because i think, that Dapper Drake should not be released without MH patch, which is crucial for most of new bluetooth equipment

Revision history for this message
meba (jakub-rtfm) wrote :

Please, is there any progress in this bug?

Revision history for this message
meba (jakub-rtfm) wrote :

I can confirm that this bug exists in Dapper Drake. Still in need of MH patches

Changed in bluez-hcidump:
status: Unconfirmed → Confirmed
Revision history for this message
Charles Majola (chmj) wrote :

can you test the kernel from http://www.rootcore.co.za/ubuntu to see if it fixes the problem. It has been build with the MH patches.

Revision history for this message
meba (jakub-rtfm) wrote :

Well, finally, the mouse wheel works! But it seems, that this kernel broken my fglrx drivers (using linux-restricted-modules-2.6.15-15-386), but i assume it's only version incompatibility and will be ok when this patch makes it to default ubuntu tree?

Revision history for this message
meba (jakub-rtfm) wrote : dmesg of fglrx module

Some log from broken fglrx module

Revision history for this message
Charles Majola (chmj) wrote :

Thanks for testing, yes the fglrx will be fixed once we include this patch by default in the kernel tree.

Changed in bluez-hcidump:
status: Confirmed → In Progress
status: Confirmed → In Progress
Changed in bluez-hcidump:
status: In Progress → Rejected
Revision history for this message
Daniel Vollmer (maven) wrote :

Being rejected for dapper means we'll have to build custom kernels for the coming half year as well, if we want proper blueooth-support, correct?

Revision history for this message
Dennis Kaarsemaker (dennis) wrote :

No, it just means that one task is enough.

Revision history for this message
Charles Majola (chmj) wrote :

This is the correct reason....

<dholbach> i just rejected the Ubuntu Dapper part of it
<dholbach> that was a malone bug, it's fixed now
<dholbach> we shouldn't distinguish between "Ubuntu Dapper" and "Ubuntu", as Dapper is not released yet

So the bug is still open for "Ubuntu"

Revision history for this message
Daniel Vollmer (maven) wrote :

Scroll wheel works for me in the new 2.6.15-17.24 kernel :)

Revision history for this message
Daniel Robitaille (robitaille) wrote :

Reported fixed in March with the latest kernel back then

Changed in bluez-hcidump:
status: In Progress → Fix Released
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.