FS#23825 - [kernel26] Bluetooth stopped working after upgrade to kernel 2.6.38
Attached to Project:
Arch Linux
Opened by Radu Potop (wooptoo) - Monday, 18 April 2011, 10:59 GMT
Last edited by Andrea Scarpino (BaSh) - Sunday, 19 June 2011, 06:50 GMT
Opened by Radu Potop (wooptoo) - Monday, 18 April 2011, 10:59 GMT
Last edited by Andrea Scarpino (BaSh) - Sunday, 19 June 2011, 06:50 GMT
|
Details
Description:
Bluetooth stopped working after upgrade to kernel 2.6.38. It doesn't work at all. It worked with kernel 2.6.37 and it works with kernel 2.5.32 lts. Additional info: * package version(s) kernel26 2.6.38.2-1 bluez 4.91-1 |
This task depends upon
Closed by Andrea Scarpino (BaSh)
Sunday, 19 June 2011, 06:50 GMT
Reason for closing: Fixed
Additional comments about closing: kernel26 2.6.39-1
bluez 4.93-2
Sunday, 19 June 2011, 06:50 GMT
Reason for closing: Fixed
Additional comments about closing: kernel26 2.6.39-1
bluez 4.93-2
Comment by
Jelle van der Waa (jelly) - Monday,
18 April 2011, 11:07 GMT
check upstream if it's a regression in the kernel.
Comment by Radu Potop (wooptoo) -
Monday, 18 April 2011, 11:16 GMT
I don't know how exactly I am supposed to do this. Should I read
the changelog (
http://www.kernel.org/pub/linux/kernel/v2.6/ChangeLog-2.6.38
) or should I search for bug reports?
Comment by Thomas Bächler (brain0) -
Monday, 18 April 2011, 11:38 GMT
Same problem. When I launch bluetoothd, my adapter is not
recognized. When I log in as root and run "hciconfig hci0 down;
hciconfig hci0 up", it starts working. Somehow, bluetoothd fails
to initialize the adapter on its own the first time. Does this
help in your case, too?
Comment by Radu Potop (wooptoo) -
Monday, 18 April 2011, 11:51 GMT
Thomas: thanks, it works with your instructions. I added them to
rc.local as a temporary fix.
Comment by roko (roko) - Saturday,
18 June 2011, 18:19 GMT
Does the problem persists with the latest (.39) kernel and bluez
(4.93-2)?
Comment by Radu Potop (wooptoo) -
Saturday, 18 June 2011, 22:58 GMT
I guess it got fixed at some point. I unplugged the adapter and
plugged it in again and it initializes/works fine.