Please read this before reporting a bug:
https://wiki.archlinux.org/title/Bug_reporting_guidelines
Do NOT report bugs when a package is just outdated, or it is in the AUR. Use the 'flag out of date' link on the package page, or the Mailing List.
REPEAT: Do NOT report bugs for outdated packages!
https://wiki.archlinux.org/title/Bug_reporting_guidelines
Do NOT report bugs when a package is just outdated, or it is in the AUR. Use the 'flag out of date' link on the package page, or the Mailing List.
REPEAT: Do NOT report bugs for outdated packages!
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
|
DetailsDescription:
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

check upstream if it's a regression in the kernel.

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?

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?

Thomas: thanks, it works with your instructions. I added them to rc.local as a temporary fix.

Does the problem persists with the latest (.39) kernel and bluez (4.93-2)?

I guess it got fixed at some point. I unplugged the adapter and plugged it in again and it initializes/works fine.