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 <richenha...@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 <richenha...@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 <suj...@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 mailing list ath9k-devel@lists.ath9k.org https://lists.ath9k.org/mailman/listinfo/ath9k-devel
