Hi there! I suffer from the very same bug as described in this thread.
looks like something is getting jacked up with the ath3k bluetooth driver using both the ARCH kernel and custom configured/compiled kernel.
The obvious sign is that bluez no longer works (hcitool dev) and there is now error mesgs in dmesg:
ath3k_load_firmware: Can't change to loading configuration err
ath3k: probe of 3-2:1.0 failed with error -5
can anyone else confirm this issue ?
Sorry for necrobumping the old thread. Here's a new one.
The problem is exactly the same on my Sony Vaio VPCF22.
Does anyone have this BT-Chip and got it working?
Last edited by Thorsten Reinbold (2013-04-18 10:42:05)
I suggest reading all comments at the bug report you've linked, finding the latest firmware and - if it still doesn't work - finding out which version of device it is, how it reacts to this latest firmware and reporting your findings there.
Latest Firmware is already in use.
dmesg | grep ath3 [ 9.647865] ath3k: probe of 1-1.5:1.0 failed with error -110 [ 9.647950] usbcore: registered new interface driver ath3k
lsusb Bus 001 Device 004: ID 0489:e027 Foxconn / Hon Hai
The 0489:e027 is an Atheros AR3011.
This is a similar Gentoo-Bugreport. The Patch that solves the problem there is obviously already applied on my System (adding Device ID to ath3k.c and btusb.c).
Last edited by Thorsten Reinbold (2013-04-18 10:51:04)
Well, this is weird. With the latest daily-image from Ubuntu, BT works out of the box without problems. Firmware is exactly the same. In which way can I use this knowledge to solve the problem?
Ok, I have to correct myself: on Ubuntu it isn't working, too. I've found some patches for the modules ath3k.c and btusb.c, but those patches are already applied to the Arch-Kernel. I gues I really need some advice here.