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
___
ath9k-devel mailing list
ath9k-devel@lists.ath9k.org
https://lists.ath9k.org/mailman/listinfo/ath9k-devel
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
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
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
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
Noo, 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 suj...@msujith.org:
Joshua Richenhagen wrote:
Goddammit sorry, I found the reason for all this
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
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
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
On 4 January 2014 10:01, Joshua Richenhagen richenha...@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
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
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
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:
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 suj...@msujith.org:
Joshua Richenhagen wrote:
P.S.: Everytime I issue rmmod
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'
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 suj...@msujith.org:
Joshua Richenhagen wrote:
can I download a newer firmware file from somewhere else in the
meantime?
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]
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 suj...@msujith.org:
Joshua Richenhagen wrote:
Dear Sujith,
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
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 =
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
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
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
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,
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
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
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
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
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_0x3101.dfu
1526ca3e2138cbacd896cb7df5ba63dd ramps_0x3101_40.dfu
2013/10/28 Sujith Manoharan suj...@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_0x3101.dfu
1526ca3e2138cbacd896cb7df5ba63dd ramps_0x3101_40.dfu
It looks like the
30 matches
Mail list logo