You are not logged in.
Hi all,
I upgraded the kernel from 3.10 to 3.11 and noticed that after resuming from standby my buetooth mouse won't reconnect no matter what.
(I tried both 3.11 minor revisions that went stable since the latest stable 3.10 but to no avail; I do not use anything from the testing repo or any custom core packages)
In gnome bluetooth settings the mouse still shows connected after resume but it won't work no more, not even after restarting the bluetooth service.
I also tried powering the mouse off and back on but it won't help either, only a full system restart would.
My system is a Dell Inspiron 5323 and its integrated (Intel) bluetooth used to work properly before the kernel upgrade.
Downgrading linux back to 3.10 solves the issue.
I'm kinda lost.
Anyone else seen this problem?
Edit: please see the hardware info in my post below
Last edited by aky (2013-10-16 16:02:26)
Offline
Hello again,
I'm back with more info. I unpinned the kernel (unblocked the upgrade in /etc/pacman.conf) and upgraded again to 3.11:
[aky@3axis ~]$ uname -a
Linux 3axis 3.11.4-1-ARCH #1 SMP PREEMPT Sat Oct 5 21:22:51 CEST 2013 x86_64 GNU/Linux
[aky@3axis ~]$
[edit]
This is everything bluetooth related that I have installed:
[root@3axis ~]# pacman -Qs bluetooth
local/bluez 5.9-1
Daemons for the bluetooth protocol stack
local/bluez-libs 5.9-1
Deprecated libraries for the bluetooth protocol stack
local/bluez-utils 5.9-1
Development and debugging utilities for the bluetooth protocol stack
local/gnome-bluetooth 3.10.0-1
The GNOME Bluetooth Subsystem
local/sbc 1.1-1
Bluetooth Subband Codec (SBC) library
[root@3axis ~]#
Hardware info:
Bus 004 Device 008: ID 8087:07da Intel Corp.
Device Descriptor:
bLength 18
bDescriptorType 1
bcdUSB 2.00
bDeviceClass 224 Wireless
bDeviceSubClass 1 Radio Frequency
bDeviceProtocol 1 Bluetooth
bMaxPacketSize0 64
idVendor 0x8087 Intel Corp.
idProduct 0x07da
bcdDevice 78.69
iManufacturer 0
iProduct 0
iSerial 0
bNumConfigurations 1
Configuration Descriptor:
bLength 9
bDescriptorType 2
wTotalLength 177
bNumInterfaces 2
bConfigurationValue 1
iConfiguration 0
bmAttributes 0xe0
Self Powered
Remote Wakeup
MaxPower 0mA
Interface Descriptor:
bLength 9
bDescriptorType 4
bInterfaceNumber 0
bAlternateSetting 0
bNumEndpoints 3
bInterfaceClass 224 Wireless
bInterfaceSubClass 1 Radio Frequency
bInterfaceProtocol 1 Bluetooth
iInterface 0
Endpoint Descriptor:
bLength 7
bDescriptorType 5
bEndpointAddress 0x81 EP 1 IN
bmAttributes 3
Transfer Type Interrupt
Synch Type None
Usage Type Data
wMaxPacketSize 0x0010 1x 16 bytes
bInterval 1
Endpoint Descriptor:
bLength 7
bDescriptorType 5
bEndpointAddress 0x02 EP 2 OUT
bmAttributes 2
Transfer Type Bulk
Synch Type None
Usage Type Data
wMaxPacketSize 0x0040 1x 64 bytes
bInterval 1
Endpoint Descriptor:
bLength 7
bDescriptorType 5
bEndpointAddress 0x82 EP 2 IN
bmAttributes 2
Transfer Type Bulk
Synch Type None
Usage Type Data
wMaxPacketSize 0x0040 1x 64 bytes
bInterval 1
Interface Descriptor:
bLength 9
bDescriptorType 4
bInterfaceNumber 1
bAlternateSetting 0
bNumEndpoints 2
bInterfaceClass 224 Wireless
bInterfaceSubClass 1 Radio Frequency
bInterfaceProtocol 1 Bluetooth
iInterface 0
Endpoint Descriptor:
bLength 7
bDescriptorType 5
bEndpointAddress 0x03 EP 3 OUT
bmAttributes 1
Transfer Type Isochronous
Synch Type None
Usage Type Data
wMaxPacketSize 0x0000 1x 0 bytes
bInterval 1
Endpoint Descriptor:
bLength 7
bDescriptorType 5
bEndpointAddress 0x83 EP 3 IN
bmAttributes 1
Transfer Type Isochronous
Synch Type None
Usage Type Data
wMaxPacketSize 0x0000 1x 0 bytes
bInterval 1
Interface Descriptor:
bLength 9
bDescriptorType 4
bInterfaceNumber 1
bAlternateSetting 1
bNumEndpoints 2
bInterfaceClass 224 Wireless
bInterfaceSubClass 1 Radio Frequency
bInterfaceProtocol 1 Bluetooth
iInterface 0
Endpoint Descriptor:
bLength 7
bDescriptorType 5
bEndpointAddress 0x03 EP 3 OUT
bmAttributes 1
Transfer Type Isochronous
Synch Type None
Usage Type Data
wMaxPacketSize 0x0009 1x 9 bytes
bInterval 1
Endpoint Descriptor:
bLength 7
bDescriptorType 5
bEndpointAddress 0x83 EP 3 IN
bmAttributes 1
Transfer Type Isochronous
Synch Type None
Usage Type Data
wMaxPacketSize 0x0009 1x 9 bytes
bInterval 1
Interface Descriptor:
bLength 9
bDescriptorType 4
bInterfaceNumber 1
bAlternateSetting 2
bNumEndpoints 2
bInterfaceClass 224 Wireless
bInterfaceSubClass 1 Radio Frequency
bInterfaceProtocol 1 Bluetooth
iInterface 0
Endpoint Descriptor:
bLength 7
bDescriptorType 5
bEndpointAddress 0x03 EP 3 OUT
bmAttributes 1
Transfer Type Isochronous
Synch Type None
Usage Type Data
wMaxPacketSize 0x0011 1x 17 bytes
bInterval 1
Endpoint Descriptor:
bLength 7
bDescriptorType 5
bEndpointAddress 0x83 EP 3 IN
bmAttributes 1
Transfer Type Isochronous
Synch Type None
Usage Type Data
wMaxPacketSize 0x0011 1x 17 bytes
bInterval 1
Interface Descriptor:
bLength 9
bDescriptorType 4
bInterfaceNumber 1
bAlternateSetting 3
bNumEndpoints 2
bInterfaceClass 224 Wireless
bInterfaceSubClass 1 Radio Frequency
bInterfaceProtocol 1 Bluetooth
iInterface 0
Endpoint Descriptor:
bLength 7
bDescriptorType 5
bEndpointAddress 0x03 EP 3 OUT
bmAttributes 1
Transfer Type Isochronous
Synch Type None
Usage Type Data
wMaxPacketSize 0x0019 1x 25 bytes
bInterval 1
Endpoint Descriptor:
bLength 7
bDescriptorType 5
bEndpointAddress 0x83 EP 3 IN
bmAttributes 1
Transfer Type Isochronous
Synch Type None
Usage Type Data
wMaxPacketSize 0x0019 1x 25 bytes
bInterval 1
Interface Descriptor:
bLength 9
bDescriptorType 4
bInterfaceNumber 1
bAlternateSetting 4
bNumEndpoints 2
bInterfaceClass 224 Wireless
bInterfaceSubClass 1 Radio Frequency
bInterfaceProtocol 1 Bluetooth
iInterface 0
Endpoint Descriptor:
bLength 7
bDescriptorType 5
bEndpointAddress 0x03 EP 3 OUT
bmAttributes 1
Transfer Type Isochronous
Synch Type None
Usage Type Data
wMaxPacketSize 0x0021 1x 33 bytes
bInterval 1
Endpoint Descriptor:
bLength 7
bDescriptorType 5
bEndpointAddress 0x83 EP 3 IN
bmAttributes 1
Transfer Type Isochronous
Synch Type None
Usage Type Data
wMaxPacketSize 0x0021 1x 33 bytes
bInterval 1
Interface Descriptor:
bLength 9
bDescriptorType 4
bInterfaceNumber 1
bAlternateSetting 5
bNumEndpoints 2
bInterfaceClass 224 Wireless
bInterfaceSubClass 1 Radio Frequency
bInterfaceProtocol 1 Bluetooth
iInterface 0
Endpoint Descriptor:
bLength 7
bDescriptorType 5
bEndpointAddress 0x03 EP 3 OUT
bmAttributes 1
Transfer Type Isochronous
Synch Type None
Usage Type Data
wMaxPacketSize 0x0031 1x 49 bytes
bInterval 1
Endpoint Descriptor:
bLength 7
bDescriptorType 5
bEndpointAddress 0x83 EP 3 IN
bmAttributes 1
Transfer Type Isochronous
Synch Type None
Usage Type Data
wMaxPacketSize 0x0031 1x 49 bytes
bInterval 1
[/edit]
Before going to standby/suspend (laptop's lid closed):
[aky@3axis ~]$ bluetoothctl -a
[NEW] Controller 68:XX:XX:XX:XX:53 3axis [default]
[NEW] Device 00:XX:XX:XX:XX:FB Razer Orochi
[NEW] Device 00:XX:XX:XX:XX:53 E2530
[NEW] Device 68:XX:XX:XX:XX:94 Radu’s Mac mini
[NEW] Device F0:XX:XX:XX:XX:81 PLT_BB903+
[NEW] Device 00:XX:XX:XX:XX:05 Bluetooth Laser Travel Mouse
Agent registered
[bluetooth]# quit
[DEL] Controller 68:XX:XX:XX:XX:53 3axis [default]
[aky@3axis ~]$
After opening the lid and system's up there's no mouse activity.
[edit]
[root@3axis ~]# rfkill list
0: phy0: Wireless LAN
Soft blocked: no
Hard blocked: no
4: hci0: Bluetooth
Soft blocked: no
Hard blocked: no
[root@3axis ~]#
[/edit]
My Logitech "Bluetooth Laser Travel Mouse" doesn't work anymore and there's this:
[aky@3axis ~]$ bluetoothctl -a
[NEW] Controller 68:XX:XX:XX:XX:53 3axis [default]
[NEW] Device 00:XX:XX:XX:XX:FB Razer Orochi
[NEW] Device 00:XX:XX:XX:XX:53 E2530
[NEW] Device 68:XX:XX:XX:XX:94 Radu’s Mac mini
[NEW] Device F0:XX:XX:XX:XX:81 PLT_BB903+
[NEW] Device 00:XX:XX:XX:XX:05 Bluetooth Laser Travel Mouse
Agent registered
[bluetooth]# pairable on
Changing pairable on succeeded
[bluetooth]# default-agent
Default agent request successful
[bluetooth]# scan on
Discovery started
[CHG] Controller 68:XX:XX:XX:XX:53 Discovering: yes
[bluetooth]# info 00:XX:XX:XX:XX:05
Device 00:XX:XX:XX:XX:05
Name: Bluetooth Laser Travel Mouse
Alias: Bluetooth Laser Travel Mouse
Class: 0x002580
Icon: input-mouse
Paired: no
Trusted: yes
Blocked: no
Connected: yes
LegacyPairing: no
UUID: Human Interface Device... (00001124-0000-1000-8000-00805f9b34fb)
UUID: PnP Information (00001200-0000-1000-8000-00805f9b34fb)
Modalias: usb:v046DpB008d0313
[bluetooth]# pair 00:XX:XX:XX:XX:05
Attempting to pair with 00:XX:XX:XX:XX:05
[bluetooth]# connect 00:XX:XX:XX:XX:05
Attempting to connect to 00:XX:XX:XX:XX:05
Failed to connect: org.bluez.Error.Failed
Failed to pair: org.bluez.Error.AuthenticationCanceled
[CHG] Device 00:XX:XX:XX:XX:05 Connected: no
[DEL] Device 00:XX:XX:XX:XX:05 Bluetooth Laser Travel Mouse
[DEL] Device F0:XX:XX:XX:XX:81 PLT_BB903+
[DEL] Device 68:XX:XX:XX:XX:94 Radu’s Mac mini
[DEL] Device 00:XX:XX:XX:XX:53 E2530
[DEL] Device 00:XX:XX:XX:XX:FB Razer Orochi
[CHG] Controller 68:XX:XX:XX:XX:53 Class: 0x000000
[CHG] Controller 68:XX:XX:XX:XX:53 Powered: no
[CHG] Controller 68:XX:XX:XX:XX:53 Discovering: no
[DEL] Controller 68:XX:XX:XX:XX:53 3axis [default]
[NEW] Controller 68:XX:XX:XX:XX:53 3axis [default]
[NEW] Device 00:XX:XX:XX:XX:05 Bluetooth Laser Travel Mouse
[NEW] Device F0:XX:XX:XX:XX:81 PLT_BB903+
[NEW] Device 68:XX:XX:XX:XX:94 Radu’s Mac mini
[NEW] Device 00:XX:XX:XX:XX:53 E2530
[NEW] Device 00:XX:XX:XX:XX:FB Razer Orochi
[CHG] Controller 68:XX:XX:XX:XX:53 Class: 0x00010c
[CHG] Controller 68:XX:XX:XX:XX:53 Powered: yes
[CHG] Device 00:XX:XX:XX:XX:05 Connected: yes
[bluetooth]#
I followed these steps as described in another bluetooth thread and it's only the final step - "connect 00:XX:XX:XX:XX:05" - when I get the mouse back working.
This doesn't happen if I downgrade the kernel to linux-3.10.10-1-x86_64 and it did not happen with any kernel version before.
My Logitech mouse used to work right after opening the laptop lid with no intervention.
Even stranger, I can see that it's reported as "Paired: no", which is not true.
Any ideea what the problem could be / how can this be fixed?
Last edited by aky (2013-10-13 14:04:42)
Offline
Hello,
I have the exact same problem and I'm very bored ! I have a Dell Inspiron 1545 and a Dell BT Travel Mouse. After some research, I've found some topics speaking that Broadcom cards could be in conflict. Personally, rfkill list and hciconfig doesn't find my hci0 when using bluez 5.9 but it does when using bluez 5.7. Anyone to help us please ? :-)
Thanks, have a nice day !
Offline
Hello robin850,
And welcome on arch forums! (I see this is your first post here)
I have the exact same problem [..] I've found some topics speaking that Broadcom cards could be in conflict
I'm not sure that you have the same problem.
It could be, tho.. there's no Broadcom in my system. I know how funny it sounds but it's also true:
[root@3axis ~]# lsusb -v|grep -i road
[root@3axis ~]# lspci -v|grep -i road
[root@3axis ~]#
So either is something related to bluetooth in general in the latest kernels (3.11) or maybe your problem has a different cause.
Regards
Offline
I think this could be related: https://bugzilla.redhat.com/show_bug.cgi?id=1010410
Offline
I don't know if this is relevant to you or not but there have been developments to the bluez package (which is bluez 5) - I know that most people have been using bluez4 until now. I use KDE not Gnome, but I now use bluez instead of bluez4 since the latter is I believe no longer maintained. If you are still using bluez4 is it possible for you to move to bluez (i.e. bluez5) instead?
Mike C
Offline
I don't know if this is relevant to you or not but there have been developments to the bluez package (which is bluez 5) - I know that most people have been using bluez4 until now. I use KDE not Gnome, but I now use bluez instead of bluez4 since the latter is I believe no longer maintained. If you are still using bluez4 is it possible for you to move to bluez (i.e. bluez5) instead?
Please look above, I already mentioned this:
This is everything bluetooth related that I have installed:
[root@3axis ~]# pacman -Qs bluetooth local/bluez 5.9-1 Daemons for the bluetooth protocol stack local/bluez-libs 5.9-1 Deprecated libraries for the bluetooth protocol stack local/bluez-utils 5.9-1 Development and debugging utilities for the bluetooth protocol stack local/gnome-bluetooth 3.10.0-1 The GNOME Bluetooth Subsystem local/sbc 1.1-1 Bluetooth Subband Codec (SBC) library [root@3axis ~]#
Offline
@aky : Ugh, thanks for the link though!
@mcloaker : I'm still on Bluez 5, I'm just locked to the 5.7-1 version since with 5.9-1, rfkill list or hciconfig don't detect hci0 :-(
Thanks for your kindness guys!
Offline
@mcloaker : I'm still on Bluez 5, I'm just locked to the 5.7-1 version since with 5.9-1, rfkill list or hciconfig don't detect hci0 :-(
So you mentioned Broadcom + bluetooth doesn't show up in rfkill list for you..
My bluetooth adapter is Intel + bluetooth shows up in rfkill list even after opening the laptop lid for me.. and that with Bluez 5.9-1
Like I said, probably you have a different bluetooth issue.
I don't know, maybe I should open a bug report for this and link it to the bug on Fedora bug tracker.
The issue reported on Fedora seems the closest to mine.
Offline
OK - I don't know what technique you used to get your BT mouse going but here are my notes in case they might help -
Bluetooth related packages installed are:
sudo pacman -Qs blue
local/bluez 5.7-1
Daemons for the bluetooth protocol stack
local/bluez-libs 5.7-1
Deprecated libraries for the bluetooth protocol stack
local/bluez-utils 5.7-1
Development and debugging utilities for the bluetooth protocol stack
local/sbc 1.1-1
Bluetooth Subband Codec (SBC) library
Then I got the bluetooth service working via systemctl and then configured in the command line and did not attempt to use the KDE bluetooth at all - mouse is much smoother and works a lot better! The key facility is bluetoothctl which is available once bluez5 is running.
Here is the set of commands:
1) Start the daemon
[root@lapmike3 ~]# systemctl start bluetooth
[root@lapmike3 ~]# systemctl status bluetooth
bluetooth.service - Bluetooth service
Loaded: loaded (/usr/lib/systemd/system/bluetooth.service; disabled)
Active: active (running) since Mon 2013-08-12 20:20:38 BST; 4s ago
Docs: man:bluetoothd(8)
Main PID: 1824 (bluetoothd)
Status: "Running"
CGroup: name=systemd:/system/bluetooth.service
└─1824 /usr/lib/bluetooth/bluetoothd
Aug 12 20:20:38 lapmike3 systemd[1]: Starting Bluetooth service...
Aug 12 20:20:38 lapmike3 bluetoothd[1824]: Bluetooth daemon 5.7
Aug 12 20:20:38 lapmike3 systemd[1]: Started Bluetooth service.
Aug 12 20:20:38 lapmike3 bluetoothd[1824]: Starting SDP server
Aug 12 20:20:38 lapmike3 bluetoothd[1824]: Bluetooth management interface 1.3 initialized
2) Now use the available tools to set up the BT mouse pairing:
[root@lapmike3 ~]# hciconfig
hci0: Type: BR/EDR Bus: USB
BD Address: 00:xx:xx:xx:xx:A7 ACL MTU: 310:10 SCO MTU: 64:8
UP RUNNING PSCAN
RX bytes:34665 acl:1505 sco:0 events:707 errors:0
TX bytes:7896 acl:318 sco:0 commands:142 errors:0
[root@lapmike3 ~]# hcitool scan
Scanning ...
00:xx:xx:xx:xx:ED Bluetooth Travel Mouse
[root@lapmike3 ~]# bluetoothctl
[NEW] Controller 00:xx:xx:xx:xx:A7 lapmike3-0 [default]
[NEW] Device 00:xx:xx:xx:xx:ED Bluetooth Travel Mouse
[NEW] Device 10:xx:xx:xx:xx:7A Nokia 6303i classic
[bluetooth]# list
Controller 00:xx:xx:xx:xx:A7 lapmike3-0 [default]
[bluetooth]# select 00:xx:xx:xx:xx:A7
[bluetooth]# power on
Changing power on succeeded
[bluetooth]# scan on
Discovery started
[CHG] Controller 00:xx:xx:xx:xx:A7 Discovering: yes
[CHG] Device 00:xx:xx:xx:xx:ED LegacyPairing: yes
[CHG] Device 00:xx:xx:xx:xx:ED RSSI: -56
[bluetooth]# devices
Device 00:xx:xx:xx:xx:ED Bluetooth Travel Mouse
Device 10:xx:xx:xx:xx:7A Nokia 6303i classic
[bluetooth]# trust 00:xx:xx:xx:xx:ED
Changing 00:xx:xx:xx:xx:ED trust succeeded
[CHG] Device 00:xx:xx:xx:xx:ED Trusted: yes
[bluetooth]# pairable on
Changing pairable on succeeded
[bluetooth]# pair 00:xx:xx:xx:xx:ED
Attempting to pair with 00:xx:xx:xx:xx:ED
[CHG] Device 00:xx:xx:xx:xx:ED Connected: yes
[CHG] Device 00:xx:xx:xx:xx:ED Modalias: usb:v046DpB002d4809
Pairing successful
[CHG] Device 00:xx:xx:xx:xx:ED Modalias: usb:v046DpB002d4809
[CHG] Device 00:xx:xx:xx:xx:ED UUIDs has unsupported type
[CHG] Device 00:xx:xx:xx:xx:ED Paired: yes
[CHG] Device 00:xx:xx:xx:xx:ED Paired: no
[CHG] Device 00:xx:xx:xx:xx:ED Connected: no
[bluetooth]# connect 00:xx:xx:xx:xx:ED
Attempting to connect to 00:xx:xx:xx:xx:ED
[CHG] Device 00:xx:xx:xx:xx:ED Connected: yes
Connection successful
[bluetooth]#
[bluetooth]# quit
[DEL] Controller 00:xx:xx:xx:xx:A7 lapmike3-0 [default]
[root@lapmike3 ~]# systemctl enable bluetooth
ln -s '/usr/lib/systemd/system/bluetooth.service' '/etc/systemd/system/dbus-org.bluez.service'
ln -s '/usr/lib/systemd/system/bluetooth.service' '/etc/systemd/system/bluetooth.target.wants/bluetooth.service'
BT mouse now fine .
To make it work after reboot just make the following file:
[mike@lapmike3 ~]$ cat /etc/udev/rules.d/10-local.rules
# Set bluetooth power up
ACTION=="add", KERNEL=="hci0", RUN+="/usr/bin/hciconfig hci0 up"
Another user I was in communication with used this method as well and also then had no problems after this. How did your own method differ from this way of setting it up?
Last edited by mcloaked (2013-10-13 19:32:23)
Mike C
Offline
Hi mcloaked,
There is no "technique" involved and while I don't remember for sure I think I paired my mouse via gnome-bluetooth.
But this was more than half an year ago.
It worked flawlessly up until I upgraded to the first revision of the linux 3.11 kernel that went stable on arch.
At first I waited to see if the next kernel revision (or version) fixes the problem but it didn't (or else I wouldn't have opened this thread in the first place)
Downgrading only the kernel from 3.11 to 3.10 solves the problem, with blues 5.9 installed.
I even had tested the newer 3.11 kernels before upgrading from bluez4 to the new blues (5) and it was the same: on linux 3.10 everything is just fine, on linux 3.11 my mouse stops reconnecting after the laptop resumes from suspend.
But I already said that too..
Thank you for at least trying to help.
But this is tail chasing because Bluez is not responsible for this problem. It's kinda obvious.
[edit] Bug reported: https://bugs.archlinux.org/task/37320
Last edited by aky (2013-10-13 19:01:33)
Offline
Just a shot in the dark but is there a possibility that something is not right in the configs (but hard to find what) as a result of the original pairing in terms of being incompatible with bluez5? If so maybe it is worth unpairing the mouse - and pairing it again using the technique I gave above which does not depend on the DE bluetooth code, and seeing if it makes any difference - of course there may be a reply from one of the experts in your bug report that you quote which may resolve the issue before too long - and maybe there are some diagnostics that can be run to give a clue as to what underlies the failure on recovery from suspend. However it does seem that there are still a lot of bugs generally associated with the suspend/resume process.
Mike C
Offline
Well.. I just tried unpairing and pairing the mouse again.
It didn't help and it comes as no surprise.
What would the kernel have to do with the bluetooth pairing anyway?
Because, as I stated a few times already, downgrading only the kernel to 3.10 (and no other changes whatsoever) solves the problem
(everything else stays, including Bluez which is at version 5.9-1)
This issue is annoying as hell already
Offline
Probably because there are bluetooth drivers in the kernel - eg see http://padovan.org/blog/tag/linux-bluetooth/ or http://www.bluez.org/about/
Also this Ubuntu bug may be related - specific to Gnome Bluetooth - https://bugs.launchpad.net/ubuntu/+sour … ug/1094744
Last edited by mcloaked (2013-10-13 20:18:25)
Mike C
Offline
[offtopic alert]
Probably because there are bluetooth drivers in the kernel - eg see http://padovan.org/blog/tag/linux-bluetooth/
Sure, only the kernel doesn't do the pairing part
[/offtopic alert]
The part with "drivers in the kernel" stands, and maybe that's where the problem comes from: the new (3.11) kernel and something maybe broken with those drivers.
That could explain why upgrading only the kernel (hence the drivers) makes things from working to broken (while nobody messed neither with the pairing which remained the same nor with the apps like Bluez which also stayed as they were before)
[edit]
Like I said: chasing tails around Bluez - which is innocent IMO
[/edit]
Last edited by aky (2013-10-13 20:11:49)
Offline
Could be - but also see the quote I added about the Ubuntu bug report in my previous post.
Mike C
Offline
Could be - but also see the quote I added about the Ubuntu bug report in my previous post.
Thanks, I've read the comments on that bug report and..
When you don't use the mouse for a long enough time, the mouse disconnects and won't reconnect. I have to go into bluetooth settings, remove it, and re-pair it.
I pretty much doubt it's related because my mouse never disconnects and repairing is not needed.
I have to either issue that bluetoothctl command = connect [BT mac] after resuming from suspend, or reboot the system to make my mouse work again.
No suspend = my mouse works indefinitely
+
Repairing doesn't help in my case, after the system resumed.
Also, I think that the bug reported on Ubuntu is closely related to that specific mouse model/manufacturer rather than related to the bluetooth adapter like in my case (as I suspect).
Also there's no mention of the kernel versions on the Ubuntu bug report and the problem described there seems to be present on more Ubuntu releases and flavors: 12.04, 13.04, 13.10 [K]ubuntu.
The BT mouse reconnect-after-resume problem that I have manifests with the linux 3.11.x kernels only - which is not the case with all those (some old, even long time support like 12.04) - Ubuntu versions. I don't think that Ubuntu backported 3.11 to the old releases, including 12.04 .
So.. I'm afraid that's a different problem than mine
Edit: minor cosmetic changes
Last edited by aky (2013-10-13 21:01:24)
Offline
I think this could be related: https://bugzilla.redhat.com/show_bug.cgi?id=1010410
Apparently there's a similar bug report on Ubuntu also: https://bugs.launchpad.net/ubuntu/+sour … ug/1213239
(and it also includes a patch which I have not tested yet)
The bug I filed with Arch was closed and I've been told to report it upstream.
It'd have been nice to have more specifics.
I don't want to post bug reports in a hundred places and get the same result as on the Arch bug tracker (ping pong style), so pointing in the exact/right direction would be nice.
Can anyone help with this?
Offline
The only "upstream" that I am aware of is http://www.bluez.org/development/lists/
This is mostly patches, rather than discussion of issues/problems.
The only recent bug report regarding bluez seems to be in the kernel bugzilla - so maybe that it is where reports need to be filed?
Last edited by mcloaked (2013-10-14 15:18:59)
Mike C
Offline
Hi mcloaked,
and thanks for bearing with me so far.
I tested Hans de Goede's (of Redhat) patch which solves this kernel regression.
The full discussion, rationale and the patch can be found at: http://thread.gmane.org/gmane.linux.ker … ocus=66112
Offline
Good to hear that the patch referred to works to solve this - if that is the case then it would be a good idea to mark this solved?
Mike C
Offline
Dunno, even if the rationale behind the fix seems sensible and the person who produced this regression admitted his guilt .. I'd still like to see this patch merged "upstream" first.
The fix doesn't seem to be included in the upcoming linux kernel (3.12) ATM.
.. and because I never enjoyed patching things "by hand" (and that's also the main reason I'm not using LFS) I'll leave it as it is for now; maybe to post here if/when new developments on this issue present themselves.
Offline
Fixed (upstream) in 3.13 and also backported to the recent 3.12 kernel series.
Please close this thread.
Thanks!
Offline