[ath9k-devel] Atheros QCWB335 / AR9565 / QCA9565 Bluetooth

[ath9k-devel] Atheros QCWB335 / AR9565 / QCA9565 Bluetooth

[Joshua Richenhagen]

Hello,

I'm using a Acer Aspire E1-572 laptop with the wifi + bt combi card
named in the subject. Wireless works fine, but I can't get Bluetooth
working, even with the newest kernel 3.12-rc7. It seems to be properly
recognized but I can't see any other bt devices and other devices
can't see me too.

Is the driver for this bluetooth chipset ready at all and do I suffer
from a bug in my kernel or distro. Or is the driver not finished yet
and I simply have to wait?

Thanks in advance
Joshua

[ath9k-devel] Atheros QCWB335 / AR9565 / QCA9565 Bluetooth

[Sujith Manoharan]

Joshua Richenhagen wrote:
> Hello,
> 
> I'm using a Acer Aspire E1-572 laptop with the wifi + bt combi card
> named in the subject. Wireless works fine, but I can't get Bluetooth
> working, even with the newest kernel 3.12-rc7. It seems to be properly
> recognized but I can't see any other bt devices and other devices
> can't see me too.
> 
> Is the driver for this bluetooth chipset ready at all and do I suffer
> from a bug in my kernel or distro. Or is the driver not finished yet
> and I simply have to wait?

Support for WLAN/BT Coexistence for AR9565 is present in ath9k:
http://wireless.kernel.org/en/users/Drivers/ath9k/btcoex

The right BT firmware needs to be used. The firmware for AR9565
appears to have been last updated in 2012:
http://git.kernel.org/cgit/linux/kernel/git/firmware/linux-firmware.git/commit/ar3k?id=5c7fc9e29438119aaa4dcb8d47b79902209b75d6

What is the output of lsusb -v ? Maybe the BT device's
IDs have to be added to the ath3k driver.

Sujith

[ath9k-devel] Atheros QCWB335 / AR9565 / QCA9565 Bluetooth

[Joshua Richenhagen]

This is the output of lsusb -v: http://paste.ubuntu.com/6319121/

And these firmware files are in my /lib/firmware/ar3k directory:

0ddd087fb9b87ea4a6e2f79b2db4d6
63  AthrBT_0x31010000.dfu
1526ca3e2138cbacd896cb7df5ba63dd  ramps_0x31010000_40.dfu

2013/10/28 Sujith Manoharan <sujith@msujith.org>:
> Joshua Richenhagen wrote:
>> Hello,
>>
>> I'm using a Acer Aspire E1-572 laptop with the wifi + bt combi card
>> named in the subject. Wireless works fine, but I can't get Bluetooth
>> working, even with the newest kernel 3.12-rc7. It seems to be properly
>> recognized but I can't see any other bt devices and other devices
>> can't see me too.
>>
>> Is the driver for this bluetooth chipset ready at all and do I suffer
>> from a bug in my kernel or distro. Or is the driver not finished yet
>> and I simply have to wait?
>
> Support for WLAN/BT Coexistence for AR9565 is present in ath9k:
> http://wireless.kernel.org/en/users/Drivers/ath9k/btcoex
>
> The right BT firmware needs to be used. The firmware for AR9565
> appears to have been last updated in 2012:
> http://git.kernel.org/cgit/linux/kernel/git/firmware/linux-firmware.git/commit/ar3k?id=5c7fc9e29438119aaa4dcb8d47b79902209b75d6
>
> What is the output of lsusb -v ? Maybe the BT device's
> IDs have to be added to the ath3k driver.
>
> Sujith
>

[ath9k-devel] Atheros QCWB335 / AR9565 / QCA9565 Bluetooth

[Sujith Manoharan]

Joshua Richenhagen wrote:
> This is the output of lsusb -v: http://paste.ubuntu.com/6319121/
> 
> And these firmware files are in my /lib/firmware/ar3k directory:
> 
> 0ddd087fb9b87ea4a6e2f79b2db4d6
> 63  AthrBT_0x31010000.dfu
> 1526ca3e2138cbacd896cb7df5ba63dd  ramps_0x31010000_40.dfu

It looks like the BT IDs of your card are not present in ath3k right now.

Can you try this patch ?
http://msujith.org/patches/wl/Oct-29-2013/0001-Bluetooth-Add-support-for-Foxconn-Hon-Hai-0x0489-0xe.patch

Sujith

[ath9k-devel] Atheros QCWB335 / AR9565 / QCA9565 Bluetooth

[Joshua Richenhagen]

I'm trying to, but I can't find a proper tutorial howto rebuild ath3k
and btusb kernel module. And I'm to stupid to figure it out myself.

Refering to https://backports.wiki.kernel.org/index.php/Documentation
there is no "make defconfig-ath3k", can you give me some instruction?

2013/10/29 Sujith Manoharan <sujith@msujith.org>:
> Joshua Richenhagen wrote:
>> This is the output of lsusb -v: http://paste.ubuntu.com/6319121/
>>
>> And these firmware files are in my /lib/firmware/ar3k directory:
>>
>> 0ddd087fb9b87ea4a6e2f79b2db4d6
>> 63  AthrBT_0x31010000.dfu
>> 1526ca3e2138cbacd896cb7df5ba63dd  ramps_0x31010000_40.dfu
>
> It looks like the BT IDs of your card are not present in ath3k right now.
>
> Can you try this patch ?
> http://msujith.org/patches/wl/Oct-29-2013/0001-Bluetooth-Add-support-for-Foxconn-Hon-Hai-0x0489-0xe.patch
>
> Sujith

[ath9k-devel] Atheros QCWB335 / AR9565 / QCA9565 Bluetooth

[Joshua Richenhagen]

Forget about my last mail, got it compiled. Bluetooth is working now,
thank you very mutch. But after compiling, installing the new modules
and a reboot, I had to manually modprobe ath3k to get it working. Is
there still something missing in the driver or is this a Ubuntu fault?

Another question, is there a possibility to see the progress of the
patch going upstream? I want to know when its in standard kernel so
that I don't have to compile the module myself anymore.

2013/10/29 Sujith Manoharan <sujith@msujith.org>:
> Joshua Richenhagen wrote:
>> This is the output of lsusb -v: http://paste.ubuntu.com/6319121/
>>
>> And these firmware files are in my /lib/firmware/ar3k directory:
>>
>> 0ddd087fb9b87ea4a6e2f79b2db4d6
>> 63  AthrBT_0x31010000.dfu
>> 1526ca3e2138cbacd896cb7df5ba63dd  ramps_0x31010000_40.dfu
>
> It looks like the BT IDs of your card are not present in ath3k right now.
>
> Can you try this patch ?
> http://msujith.org/patches/wl/Oct-29-2013/0001-Bluetooth-Add-support-for-Foxconn-Hon-Hai-0x0489-0xe.patch
>
> Sujith

[ath9k-devel] Atheros QCWB335 / AR9565 / QCA9565 Bluetooth

[Sujith Manoharan]

Joshua Richenhagen wrote:
> Forget about my last mail, got it compiled. Bluetooth is working now,
> thank you very mutch. But after compiling, installing the new modules
> and a reboot, I had to manually modprobe ath3k to get it working. Is
> there still something missing in the driver or is this a Ubuntu fault?

The driver should be loaded automatically. Are you using backports ?

> Another question, is there a possibility to see the progress of the
> patch going upstream? I want to know when its in standard kernel so
> that I don't have to compile the module myself anymore.

Can you post the contents of /sys/kernel/debug/usb/devices ? It is needed
to submit the patch upstream.

Sujith

[ath9k-devel] Atheros QCWB335 / AR9565 / QCA9565 Bluetooth

[Joshua Richenhagen]

The btusb module is loaded automatically, the ath3k module doesn't. I
have to modprobe ath3k after every reboot. I'm using the Ubuntu 13.10
default kernel. First I installed the Ubuntu linux-source package,
copied the .conf of my current kernel, copied the Module.symvers of my
current kernel headers. The I did "make prepare", "make scripts" and
"make M=drivers/bluetooth". Finally I copied the ath3k.ko and btusb.ko
into the "/lib/modules/3.11.0-12-generic/kernel/drivers/bluetooth/"
directory.

This is the output of my devices file: http://paste.ubuntu.com/6324339/

2013/10/29 Sujith Manoharan <sujith@msujith.org>:
> Joshua Richenhagen wrote:
>> Forget about my last mail, got it compiled. Bluetooth is working now,
>> thank you very mutch. But after compiling, installing the new modules
>> and a reboot, I had to manually modprobe ath3k to get it working. Is
>> there still something missing in the driver or is this a Ubuntu fault?
>
> The driver should be loaded automatically. Are you using backports ?
>
>> Another question, is there a possibility to see the progress of the
>> patch going upstream? I want to know when its in standard kernel so
>> that I don't have to compile the module myself anymore.
>
> Can you post the contents of /sys/kernel/debug/usb/devices ? It is needed
> to submit the patch upstream.
>
> Sujith

[ath9k-devel] Atheros QCWB335 / AR9565 / QCA9565 Bluetooth

[Sujith Manoharan]

Joshua Richenhagen wrote:
> The btusb module is loaded automatically, the ath3k module doesn't. I
> have to modprobe ath3k after every reboot. I'm using the Ubuntu 13.10
> default kernel. First I installed the Ubuntu linux-source package,
> copied the .conf of my current kernel, copied the Module.symvers of my
> current kernel headers. The I did "make prepare", "make scripts" and
> "make M=drivers/bluetooth". Finally I copied the ath3k.ko and btusb.ko
> into the "/lib/modules/3.11.0-12-generic/kernel/drivers/bluetooth/"
> directory.

I am not familiar with the recommended way to compile kernels on Ubuntu.
But, try "sudo make modules_install".

> This is the output of my devices file: http://paste.ubuntu.com/6324339/

Thanks. I'll send the patch to the bluetooth list.

Sujith

[ath9k-devel] Atheros QCWB335 / AR9565 / QCA9565 Bluetooth

[Joshua Richenhagen]

Dear Sujith,

some more testing has shown that my bluetooth still doesn't work
reliably. Some times after startup "dmesg" shows the following message
and bluetooth is broken. After some reboots it works again, without
having made any changes.

[ 7.791682] Bluetooth: Error in firmware loading err = -110,len = 448,
size = 4096
[ 7.791693] Bluetooth: Loading patch file failed
[ 7.791704] ath3k: probe of 2-5:1.0 failed with error -110
[ 7.791747] usbcore: registered new interface driver ath3k

Any idea?

Thanks in advance
Joshua

2013/10/29 Sujith Manoharan <sujith@msujith.org>:
> Joshua Richenhagen wrote:
>> The btusb module is loaded automatically, the ath3k module doesn't. I
>> have to modprobe ath3k after every reboot. I'm using the Ubuntu 13.10
>> default kernel. First I installed the Ubuntu linux-source package,
>> copied the .conf of my current kernel, copied the Module.symvers of my
>> current kernel headers. The I did "make prepare", "make scripts" and
>> "make M=drivers/bluetooth". Finally I copied the ath3k.ko and btusb.ko
>> into the "/lib/modules/3.11.0-12-generic/kernel/drivers/bluetooth/"
>> directory.
>
> I am not familiar with the recommended way to compile kernels on Ubuntu.
> But, try "sudo make modules_install".
>
>> This is the output of my devices file: http://paste.ubuntu.com/6324339/
>
> Thanks. I'll send the patch to the bluetooth list.
>
> Sujith

[ath9k-devel] Atheros QCWB335 / AR9565 / QCA9565 Bluetooth

[Joshua Richenhagen]

Dear Sujith,

you did added the device id to AR3012 driver, do you? But lsusb -v of
0489:e05f shows iProduct 0. So according to
http://wireless.kernel.org/en/users/Drivers/ath3k it's a AR3011
device. Could this be why it's not working properly? Or am I missing
something?

Thanks in advance
Joshua

2013/11/18 Joshua Richenhagen <richenhagen@gmail.com>:
> Dear Sujith,
>
> some more testing has shown that my bluetooth still doesn't work
> reliably. Some times after startup "dmesg" shows the following message
> and bluetooth is broken. After some reboots it works again, without
> having made any changes.
>
> [ 7.791682] Bluetooth: Error in firmware loading err = -110,len = 448,
> size = 4096
> [ 7.791693] Bluetooth: Loading patch file failed
> [ 7.791704] ath3k: probe of 2-5:1.0 failed with error -110
> [ 7.791747] usbcore: registered new interface driver ath3k
>
> Any idea?
>
> Thanks in advance
> Joshua
>
> 2013/10/29 Sujith Manoharan <sujith@msujith.org>:
>> Joshua Richenhagen wrote:
>>> The btusb module is loaded automatically, the ath3k module doesn't. I
>>> have to modprobe ath3k after every reboot. I'm using the Ubuntu 13.10
>>> default kernel. First I installed the Ubuntu linux-source package,
>>> copied the .conf of my current kernel, copied the Module.symvers of my
>>> current kernel headers. The I did "make prepare", "make scripts" and
>>> "make M=drivers/bluetooth". Finally I copied the ath3k.ko and btusb.ko
>>> into the "/lib/modules/3.11.0-12-generic/kernel/drivers/bluetooth/"
>>> directory.
>>
>> I am not familiar with the recommended way to compile kernels on Ubuntu.
>> But, try "sudo make modules_install".
>>
>>> This is the output of my devices file: http://paste.ubuntu.com/6324339/
>>
>> Thanks. I'll send the patch to the bluetooth list.
>>
>> Sujith

[ath9k-devel] Atheros QCWB335 / AR9565 / QCA9565 Bluetooth

[Sujith Manoharan]

Joshua Richenhagen wrote:
> Dear Sujith,
> 
> you did added the device id to AR3012 driver, do you? But lsusb -v of
> 0489:e05f shows iProduct 0. So according to
> http://wireless.kernel.org/en/users/Drivers/ath3k it's a AR3011
> device. Could this be why it's not working properly? Or am I missing
> something?

I think AR3012 is used in WB335, but I have asked internally, so I'll
confirm what part is present in AR9565 once I get some information.

The firmware in linux-firmware.git is really old and maybe an update
is needed - not sure when that will happen, though.

Sujith

[ath9k-devel] Atheros QCWB335 / AR9565 / QCA9565 Bluetooth

[Joshua Richenhagen]

DearSujith,

can I download a newer firmware file from somewhere else in the
meantime? How can I verify that the firmware is definitly causing the
problem and not something else.

Thanks in advance
Joshua

2013/11/18 Sujith Manoharan <sujith@msujith.org>:
> Joshua Richenhagen wrote:
>> Dear Sujith,
>>
>> you did added the device id to AR3012 driver, do you? But lsusb -v of
>> 0489:e05f shows iProduct 0. So according to
>> http://wireless.kernel.org/en/users/Drivers/ath3k it's a AR3011
>> device. Could this be why it's not working properly? Or am I missing
>> something?
>
> I think AR3012 is used in WB335, but I have asked internally, so I'll
> confirm what part is present in AR9565 once I get some information.
>
> The firmware in linux-firmware.git is really old and maybe an update
> is needed - not sure when that will happen, though.
>
> Sujith

[ath9k-devel] Atheros QCWB335 / AR9565 / QCA9565 Bluetooth

[Sujith Manoharan]

Joshua Richenhagen wrote:
> can I download a newer firmware file from somewhere else in the
> meantime? How can I verify that the firmware is definitly causing the
> problem and not something else.

I got confirmation that the Bluetooth part in WB335 is AR3012, so
the patch is correct.

I am not sure when the firmware will be updated, though.

Sujith

[ath9k-devel] Atheros QCWB335 / AR9565 / QCA9565 Bluetooth

[Sujith Manoharan]

Joshua Richenhagen wrote:
> can I download a newer firmware file from somewhere else in the
> meantime? How can I verify that the firmware is definitly causing the
> problem and not something else.

Here is a new firmware: http://msujith.org/dir/ath3k/AthrBT_0x31010000.dfu
Drop it into /lib/firmware/ar3k/ (the location depends on your distribution),
and reboot.

Sujith

[ath9k-devel] Atheros QCWB335 / AR9565 / QCA9565 Bluetooth

[Joshua Richenhagen]

The new firmware file doesn't solve the problem either. Here is the
full dmesg output (error at row 1158-1161):
http://paste.ubuntu.com/6452471/

2013/11/21 Sujith Manoharan <sujith@msujith.org>:
> Joshua Richenhagen wrote:
>> can I download a newer firmware file from somewhere else in the
>> meantime? How can I verify that the firmware is definitly causing the
>> problem and not something else.
>
> Here is a new firmware: http://msujith.org/dir/ath3k/AthrBT_0x31010000.dfu
> Drop it into /lib/firmware/ar3k/ (the location depends on your distribution),
> and reboot.
>
> Sujith

[ath9k-devel] Atheros QCWB335 / AR9565 / QCA9565 Bluetooth

[Joshua Richenhagen]

P.S.: Everytime I issue rmmod ath3k; modprobe ath3k; I get the
following messages:

[ 1429.503550] usbcore: deregistering interface driver ath3k
[ 1433.996712] Request for unknown module key 'Magrathea: Glacier
signing key: d23f2f0afe5db0d436c757eb762ff7610a8f5d19' err -11
[ 1438.992653] Bluetooth: Can't get state to change to load ram patch err
[ 1438.992663] Bluetooth: Loading patch file failed
[ 1438.992681] ath3k: probe of 2-5:1.0 failed with error -110
[ 1438.992769] usbcore: registered new interface driver ath3k


2013/11/21 Sujith Manoharan <sujith@msujith.org>:
> Joshua Richenhagen wrote:
>> can I download a newer firmware file from somewhere else in the
>> meantime? How can I verify that the firmware is definitly causing the
>> problem and not something else.
>
> Here is a new firmware: http://msujith.org/dir/ath3k/AthrBT_0x31010000.dfu
> Drop it into /lib/firmware/ar3k/ (the location depends on your distribution),
> and reboot.
>
> Sujith

[ath9k-devel] Atheros QCWB335 / AR9565 / QCA9565 Bluetooth

[Sujith Manoharan]

Joshua Richenhagen wrote:
> P.S.: Everytime I issue rmmod ath3k; modprobe ath3k; I get the
> following messages:
> 
> [ 1429.503550] usbcore: deregistering interface driver ath3k
> [ 1433.996712] Request for unknown module key 'Magrathea: Glacier
> signing key: d23f2f0afe5db0d436c757eb762ff7610a8f5d19' err -11
> [ 1438.992653] Bluetooth: Can't get state to change to load ram patch err
> [ 1438.992663] Bluetooth: Loading patch file failed
> [ 1438.992681] ath3k: probe of 2-5:1.0 failed with error -110
> [ 1438.992769] usbcore: registered new interface driver ath3k

I am not a bluetooth developer, but the bluetooth team is looking at this issue,
so if any solution comes up, I'll post it here.

Sujith

[ath9k-devel] Atheros QCWB335 / AR9565 / QCA9565 Bluetooth

[Joshua Richenhagen]

Dear Sujith,

I was just wondering that the patch still didn't landed upstream until
3.13-rc3. Are you holding the patch back until the firmware bug is
solved?

Thanks in advance
Joshua

2013/11/25 Sujith Manoharan <sujith@msujith.org>:
> Joshua Richenhagen wrote:
>> P.S.: Everytime I issue rmmod ath3k; modprobe ath3k; I get the
>> following messages:
>>
>> [ 1429.503550] usbcore: deregistering interface driver ath3k
>> [ 1433.996712] Request for unknown module key 'Magrathea: Glacier
>> signing key: d23f2f0afe5db0d436c757eb762ff7610a8f5d19' err -11
>> [ 1438.992653] Bluetooth: Can't get state to change to load ram patch err
>> [ 1438.992663] Bluetooth: Loading patch file failed
>> [ 1438.992681] ath3k: probe of 2-5:1.0 failed with error -110
>> [ 1438.992769] usbcore: registered new interface driver ath3k
>
> I am not a bluetooth developer, but the bluetooth team is looking at this issue,
> so if any solution comes up, I'll post it here.
>
> Sujith

[ath9k-devel] Atheros QCWB335 / AR9565 / QCA9565 Bluetooth

[Sujith Manoharan]

Joshua Richenhagen wrote:
> Dear Sujith,
> 
> I was just wondering that the patch still didn't landed upstream until
> 3.13-rc3. Are you holding the patch back until the firmware bug is
> solved?

The patch has been merged in bluetooth-next:
https://git.kernel.org/cgit/linux/kernel/git/bluetooth/bluetooth-next.git/commit/?id=35580d223b6b04d9a570e4fe377c46a102413fe8

Sujith

[ath9k-devel] Atheros QCWB335 / AR9565 / QCA9565 Bluetooth

[Joshua Richenhagen]

Today the Canonical Kernel Team has build a test kernel from the
upstream linux-next tree for me (based on 3.13-rc5). This kernel
includes the latest bluetooth stack, including your patch. But sadly
it still doesn't work and dmesg shows the same error message I already
reported.

Full dmesg output: http://paste.ubuntu.com/6685680/

Is there anything further I could do to help the bluetooth devs
finding the cause?



2013/12/13 Sujith Manoharan <sujith@msujith.org>:
> Joshua Richenhagen wrote:
>> Dear Sujith,
>>
>> I was just wondering that the patch still didn't landed upstream until
>> 3.13-rc3. Are you holding the patch back until the firmware bug is
>> solved?
>
> The patch has been merged in bluetooth-next:
> https://git.kernel.org/cgit/linux/kernel/git/bluetooth/bluetooth-next.git/commit/?id=35580d223b6b04d9a570e4fe377c46a102413fe8
>
> Sujith

[ath9k-devel] Atheros QCWB335 / AR9565 / QCA9565 Bluetooth

[Adrian Chadd]

Hi,

I suggest at some point grabbing your company management and having
them book a meeting or two with QCA. That's how resources get assigned
to this. Otherwise Sujith is doing it when he can and he's already
burnt out at the best of times.. :-)


-a


On 3 January 2014 09:12, Joshua Richenhagen <richenhagen@gmail.com> wrote:
> Today the Canonical Kernel Team has build a test kernel from the
> upstream linux-next tree for me (based on 3.13-rc5). This kernel
> includes the latest bluetooth stack, including your patch. But sadly
> it still doesn't work and dmesg shows the same error message I already
> reported.
>
> Full dmesg output: http://paste.ubuntu.com/6685680/
>
> Is there anything further I could do to help the bluetooth devs
> finding the cause?
>
>
>
> 2013/12/13 Sujith Manoharan <sujith@msujith.org>:
>> Joshua Richenhagen wrote:
>>> Dear Sujith,
>>>
>>> I was just wondering that the patch still didn't landed upstream until
>>> 3.13-rc3. Are you holding the patch back until the firmware bug is
>>> solved?
>>
>> The patch has been merged in bluetooth-next:
>> https://git.kernel.org/cgit/linux/kernel/git/bluetooth/bluetooth-next.git/commit/?id=35580d223b6b04d9a570e4fe377c46a102413fe8
>>
>> Sujith
> _______________________________________________
> ath9k-devel mailing list
> ath9k-devel at lists.ath9k.org
> https://lists.ath9k.org/mailman/listinfo/ath9k-devel

[ath9k-devel] Atheros QCWB335 / AR9565 / QCA9565 Bluetooth

[Joshua Richenhagen]

Hi Adrian,

no, Acer and all the other companys that are selling hardware with
this chipset and linux preinstalled should book these meetings. But
yes, I get your point... Really didn't wanted to push Sujith, sorry
for that. Just wanted to make clear that if there is anything a non
developer like me could do, testing/debuging etc., that I'm willing
to.

Cheers
Joshua

2014/1/3 Adrian Chadd <adrian@freebsd.org>:
> Hi,
>
> I suggest at some point grabbing your company management and having
> them book a meeting or two with QCA. That's how resources get assigned
> to this. Otherwise Sujith is doing it when he can and he's already
> burnt out at the best of times.. :-)
>
>
> -a
>
>
> On 3 January 2014 09:12, Joshua Richenhagen <richenhagen@gmail.com> wrote:
>> Today the Canonical Kernel Team has build a test kernel from the
>> upstream linux-next tree for me (based on 3.13-rc5). This kernel
>> includes the latest bluetooth stack, including your patch. But sadly
>> it still doesn't work and dmesg shows the same error message I already
>> reported.
>>
>> Full dmesg output: http://paste.ubuntu.com/6685680/
>>
>> Is there anything further I could do to help the bluetooth devs
>> finding the cause?
>>
>>
>>
>> 2013/12/13 Sujith Manoharan <sujith@msujith.org>:
>>> Joshua Richenhagen wrote:
>>>> Dear Sujith,
>>>>
>>>> I was just wondering that the patch still didn't landed upstream until
>>>> 3.13-rc3. Are you holding the patch back until the firmware bug is
>>>> solved?
>>>
>>> The patch has been merged in bluetooth-next:
>>> https://git.kernel.org/cgit/linux/kernel/git/bluetooth/bluetooth-next.git/commit/?id=35580d223b6b04d9a570e4fe377c46a102413fe8
>>>
>>> Sujith
>> _______________________________________________
>> ath9k-devel mailing list
>> ath9k-devel at lists.ath9k.org
>> https://lists.ath9k.org/mailman/listinfo/ath9k-devel

[ath9k-devel] Atheros QCWB335 / AR9565 / QCA9565 Bluetooth

[Adrian Chadd]

On 4 January 2014 10:01, Joshua Richenhagen <richenhagen@gmail.com> wrote:
> Hi Adrian,
>
> no, Acer and all the other companys that are selling hardware with
> this chipset and linux preinstalled should book these meetings. But
> yes, I get your point... Really didn't wanted to push Sujith, sorry
> for that. Just wanted to make clear that if there is anything a non
> developer like me could do, testing/debuging etc., that I'm willing
> to.

Right. Well, if it's not working on their linux pre-install then that
needs to be reported as a bug or two to acer so they can file the
relevant bug report with QCA and get it looked at. :-P



-a

[ath9k-devel] Atheros QCWB335 / AR9565 / QCA9565 Bluetooth

[Sujith Manoharan]

Joshua Richenhagen wrote:
> Today the Canonical Kernel Team has build a test kernel from the
> upstream linux-next tree for me (based on 3.13-rc5). This kernel
> includes the latest bluetooth stack, including your patch. But sadly
> it still doesn't work and dmesg shows the same error message I already
> reported.
> 
> Full dmesg output: http://paste.ubuntu.com/6685680/
> 
> Is there anything further I could do to help the bluetooth devs
> finding the cause?

Sorry, I am not a bluetooth developer. :-)

But, I think this issue was also seen on a Dell platform. Chris, this
issue was also seen with Dell 1707, IIRC. Do you have a workaround
for this issue ? Did QCA give a solution ?

The Ubuntu bug is this one, I believe:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1237296

Sujith

[ath9k-devel] Atheros QCWB335 / AR9565 / QCA9565 Bluetooth

[Joshua Richenhagen]

Goddammit sorry, I found the reason for all this trouble. It is an
dual boot windows 8.1 issue. Because windows 8.1 doesn't shutdown
properly, instead it goes into some kind of hybrid shutdown state. The
firmware file is already loaded into the bluetooth module and that
condition can't be handled by the linux ath3k driver, so it shows the
error I reported. When disabling this hybrid shutdown everything works
just fine.

2014/1/5 Sujith Manoharan <sujith@msujith.org>:
> Joshua Richenhagen wrote:
>> Today the Canonical Kernel Team has build a test kernel from the
>> upstream linux-next tree for me (based on 3.13-rc5). This kernel
>> includes the latest bluetooth stack, including your patch. But sadly
>> it still doesn't work and dmesg shows the same error message I already
>> reported.
>>
>> Full dmesg output: http://paste.ubuntu.com/6685680/
>>
>> Is there anything further I could do to help the bluetooth devs
>> finding the cause?
>
> Sorry, I am not a bluetooth developer. :-)
>
> But, I think this issue was also seen on a Dell platform. Chris, this
> issue was also seen with Dell 1707, IIRC. Do you have a workaround
> for this issue ? Did QCA give a solution ?
>
> The Ubuntu bug is this one, I believe:
> https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1237296
>
> Sujith

[ath9k-devel] Atheros QCWB335 / AR9565 / QCA9565 Bluetooth

[Sujith Manoharan]

Joshua Richenhagen wrote:
> Goddammit sorry, I found the reason for all this trouble. It is an
> dual boot windows 8.1 issue. Because windows 8.1 doesn't shutdown
> properly, instead it goes into some kind of hybrid shutdown state. The
> firmware file is already loaded into the bluetooth module and that
> condition can't be handled by the linux ath3k driver, so it shows the
> error I reported. When disabling this hybrid shutdown everything works
> just fine.

Thanks for the update. :)

Sujith

[ath9k-devel] Atheros QCWB335 / AR9565 / QCA9565 Bluetooth

[Joshua Richenhagen]

Noooooooooooooooooo, I'm getting crazy! Two reboots later it wasn't
working again, now I had to reboot seven times to get it working
again. So the Problem is still the same.

2014/1/15 Sujith Manoharan <sujith@msujith.org>:
> Joshua Richenhagen wrote:
>> Goddammit sorry, I found the reason for all this trouble. It is an
>> dual boot windows 8.1 issue. Because windows 8.1 doesn't shutdown
>> properly, instead it goes into some kind of hybrid shutdown state. The
>> firmware file is already loaded into the bluetooth module and that
>> condition can't be handled by the linux ath3k driver, so it shows the
>> error I reported. When disabling this hybrid shutdown everything works
>> just fine.
>
> Thanks for the update. :)
>
> Sujith

[ath9k-devel] Atheros QCWB335 / AR9565 / QCA9565 Bluetooth

[Joshua Richenhagen]

I did a booting marathon now to see how often it works or not. I did
20 boots, working y or n, here is the result:

y y n y n y n n n y n n y n n n n n n y

So it worked 7/20 times, its like playing roulette, completely random.
In my understanding it can only be a timing or priority issue at
startup.

2014/1/15 Joshua Richenhagen <richenhagen@gmail.com>:
> Noooooooooooooooooo, I'm getting crazy! Two reboots later it wasn't
> working again, now I had to reboot seven times to get it working
> again. So the Problem is still the same.
>
> 2014/1/15 Sujith Manoharan <sujith@msujith.org>:
>> Joshua Richenhagen wrote:
>>> Goddammit sorry, I found the reason for all this trouble. It is an
>>> dual boot windows 8.1 issue. Because windows 8.1 doesn't shutdown
>>> properly, instead it goes into some kind of hybrid shutdown state. The
>>> firmware file is already loaded into the bluetooth module and that
>>> condition can't be handled by the linux ath3k driver, so it shows the
>>> error I reported. When disabling this hybrid shutdown everything works
>>> just fine.
>>
>> Thanks for the update. :)
>>
>> Sujith

[ath9k-devel] Atheros QCWB335 / AR9565 / QCA9565 Bluetooth

[Joshua Richenhagen]

Dear Sujith,

finally I found the real reason, ath3k fails to work approximately 2/3
of the time if btusb is connected to a pin which uses the xhci driver.
I compiled a dkms kernel package, with the help of a very nice
canonical employee, which switches the usb pin of the bt device to
ehci on startup. Now ath3k and my bluetooth works like a charm 100% of
the time. However, this is just a workaround for a very nasty bug. Can
you forward this information to the bluetooth devs?

Thanks in advance
Joshua

2014-01-15 16:26 GMT+01:00 Joshua Richenhagen <richenhagen@gmail.com>:
> I did a booting marathon now to see how often it works or not. I did
> 20 boots, working y or n, here is the result:
>
> y y n y n y n n n y n n y n n n n n n y
>
> So it worked 7/20 times, its like playing roulette, completely random.
> In my understanding it can only be a timing or priority issue at
> startup.
>
> 2014/1/15 Joshua Richenhagen <richenhagen@gmail.com>:
>> Noooooooooooooooooo, I'm getting crazy! Two reboots later it wasn't
>> working again, now I had to reboot seven times to get it working
>> again. So the Problem is still the same.
>>
>> 2014/1/15 Sujith Manoharan <sujith@msujith.org>:
>>> Joshua Richenhagen wrote:
>>>> Goddammit sorry, I found the reason for all this trouble. It is an
>>>> dual boot windows 8.1 issue. Because windows 8.1 doesn't shutdown
>>>> properly, instead it goes into some kind of hybrid shutdown state. The
>>>> firmware file is already loaded into the bluetooth module and that
>>>> condition can't be handled by the linux ath3k driver, so it shows the
>>>> error I reported. When disabling this hybrid shutdown everything works
>>>> just fine.
>>>
>>> Thanks for the update. :)
>>>
>>> Sujith

[ath9k-devel] Atheros QCWB335 / AR9565 / QCA9565 Bluetooth

[Sujith Manoharan]

Joshua Richenhagen wrote:
> Dear Sujith,
> 
> finally I found the real reason, ath3k fails to work approximately 2/3
> of the time if btusb is connected to a pin which uses the xhci driver.
> I compiled a dkms kernel package, with the help of a very nice
> canonical employee, which switches the usb pin of the bt device to
> ehci on startup. Now ath3k and my bluetooth works like a charm 100% of
> the time. However, this is just a workaround for a very nasty bug. Can
> you forward this information to the bluetooth devs?

Sure, I will.

Thanks for tracking down this bug !

Sujith

[ath9k-devel] Atheros QCWB335 / AR9565 / QCA9565 Bluetooth

[Ewan Le Bideau]

Hello, facing to the same issue, I would be glad to execute this workaround,
can you explain how to make it work ? 

Thank you

Ewan