FS#40902 - [linux] bluetooth unusable
Attached to Project:
Arch Linux
Opened by mark (qinohe) - Thursday, 19 June 2014, 22:53 GMT
Last edited by Laurent Carlier (lordheavy) - Thursday, 31 July 2014, 23:09 GMT
Opened by mark (qinohe) - Thursday, 19 June 2014, 22:53 GMT
Last edited by Laurent Carlier (lordheavy) - Thursday, 31 July 2014, 23:09 GMT
|
Details
Description:Upgrading linux (3.14.6-1 -> 3.15.1-1) leaves
bluetooth ath3k unusable.
[code]dmesg|grep Bluetooth [ 3.438010] Bluetooth: Core ver 2.19 [ 3.438033] Bluetooth: HCI device and connection manager initialized [ 3.438041] Bluetooth: HCI socket layer initialized [ 3.438043] Bluetooth: L2CAP socket layer initialized [ 3.438053] Bluetooth: SCO socket layer initialized [ 8.425489] Bluetooth: Can't get version to change to load ram patch err [ 8.425501] Bluetooth: Loading patch file failed[/code] Steps to reproduce:Ugrade Patch:Patch was found https://bugzilla.kernel.org/attachment.cgi?id=140051&action=diff Attached patch for Arch |
This task depends upon
Closed by Laurent Carlier (lordheavy)
Thursday, 31 July 2014, 23:09 GMT
Reason for closing: Fixed
Additional comments about closing: linux 3.15.7-1
Thursday, 31 July 2014, 23:09 GMT
Reason for closing: Fixed
Additional comments about closing: linux 3.15.7-1
I would like to know, is this enough for the devs, to temporarily fix the problem, or would you need something more?
It's not about 'if' you go use the patch, but if it is okay, if you would use it. Thanks, qinohe.
[ 8.890376] Bluetooth: Core ver 2.19
[ 8.890391] Bluetooth: HCI device and connection manager initialized
[ 8.890399] Bluetooth: HCI socket layer initialized
[ 8.890402] Bluetooth: L2CAP socket layer initialized
[ 8.890417] Bluetooth: SCO socket layer initialized
[ 10.154866] Bluetooth: BNEP (Ethernet Emulation) ver 1.3
[ 10.154870] Bluetooth: BNEP filters: protocol multicast
[ 10.154877] Bluetooth: BNEP socket layer initialized
[ 13.890830] Bluetooth: Can't get version to change to load ram patch err
[ 13.890835] Bluetooth: Loading patch file failed
Just updated to 3.15.2-1-custom with patch, I have bluetooth, patch works.
Though, I guess this is an upstream bug...
After finding what went wrong to this commit, see link in commit task.
Created a new patch, with support for 'USB_DEVICE(0x0cf3, 0xe005)' and not the 'USB_DEVICE(0x0cf3, 0x3005)'
sha256sum='e0c100fe0949a86088537c37e2e0e585730ab625e923efa5993467b80264e68c'
I would remove the old one, if I knew how.
edit:Situation unchanged, just patched my ABS package to run 3.15.3-1.
running an a3thk card, and getting
ath3k: probe of 4-2:1.0 failed with error -110
waiting for the patch...
edit: attached is PKGBUILD for linux with above patch added.
plz mainline
Bluetooth works with it.
The PKGBUILD with all neccessary patchfiles is attached in this post. (Only one of this patchfiles is needed for the Bluetooth-issue, though.)
I uploaded the Kernel to Wuala, if you don't want to compile yourself. You can download it via the following URL:
https://www.wuala.com/MiB1982/Archlinux/?key=KernelBTPatch
Edit: Upstream hasn't included the patch either, yet. I guess the Arch-Maintainers wait for that to happen.
I try to install linux-lts (3.14.12) and also not working.
How long we have to wait to apply this patch in the kernel repository?
edit: I leave it open till it hit's stable.
Arch keeps packages close to upstream, it does not add patches not accepted by the project. Now when the patch is accepted it's OK to use it in arch package. But IMHO it is better to wait until it landed in linux-stable repo. Talk to Greg Hartman and ask to push the patch to linux-stable.
Next time I walk adifferent path when having a kernel bug, I put it on the mailinglist, not bugzilla!
yes, but Arch makes exceptions for bugfixes, stability fixes, and coherency. Arch is not an "absolute vanilla" distro, but is very much OK with added patches for bugfixes.
to mib1982 and qinohe good job guys. My beef is that the community did the work, all that was needed was a review of the code, and simply re-using what was uploaded.
In the end I'm happy it happened. I learned how to make a patch, how to patch, install a kernel and make my own. I'm running abs/mainline tailored to my machine, without a glitch.
I say a big thank you all who contributed.