*** This bug is a duplicate of bug 1394368 ***
https://bugs.launchpad.net/bugs/1394368
Sry for my comment. You sent it. Just got it tu spam folder and
mailing list did not show CCs.
2015-07-20 13:26 GMT+03:00 Dmitry Tunin hanipouspi...@gmail.com:
Rafael,
I saw your mail upstream. You made
*** This bug is a duplicate of bug 1394368 ***
https://bugs.launchpad.net/bugs/1394368
Rafael,
I saw your mail upstream. You made some mistakes.
You did not CC maintainers. They do not always read mailing lists. So
your mail won't be noticed.
Please forward this mail to maintainers emails.
*** This bug is a duplicate of bug 1394368 ***
https://bugs.launchpad.net/bugs/1394368
In fact I unfortunately used the To field instead of Cc. I hope it
won't cause to much trouble.
As for the workaround, I followed the format suggested at
*** This bug is a duplicate of bug 1394368 ***
https://bugs.launchpad.net/bugs/1394368
And CC me too please, if you do.
2015-07-19 23:08 GMT+03:00 Dmitry Tunin hanipouspi...@gmail.com:
But please be careful and follow
https://www.kernel.org/pub/linux/docs/lkml/reporting-bugs.html
And
*** This bug is a duplicate of bug 1394368 ***
https://bugs.launchpad.net/bugs/1394368
But please be careful and follow
https://www.kernel.org/pub/linux/docs/lkml/reporting-bugs.html
And use plain text mailer, or it will be removed as spam
2015-07-19 23:00 GMT+03:00 Raphaël Jakse
*** This bug is a duplicate of bug 1394368 ***
https://bugs.launchpad.net/bugs/1394368
Thanks.
Le 19/07/2015 21:48, Pilot6 a écrit :
*** This bug is a duplicate of bug 1394368 ***
https://bugs.launchpad.net/bugs/1394368
No, report it to linux-bluetooth and personally to bluetooth
*** This bug is a duplicate of bug 1394368 ***
https://bugs.launchpad.net/bugs/1394368
Ok, thanks for your advices. Before sending a report, I'm investigating
the bug a little bit.
I just discovered that commenting out the call to ath3k_load_patch in
ath3k_probe in the patched kernel seems
*** This bug is a duplicate of bug 1394368 ***
https://bugs.launchpad.net/bugs/1394368
Rafael,
Did you report it to upstream maintainers?
2015-07-19 18:46 GMT+03:00 Raphaël Jakse raphael.ja...@gmail.com:
*** This bug is a duplicate of bug 1394368 ***
I would wait what Marcel Holtman says abut that. It is possible to
turn on debug, but it will by easier for him.
2015-05-04 10:50 GMT+03:00 Raphaël Jakse raphael.ja...@gmail.com:
I built linux-4.0.1 with your patch, I get the exact same result.
As a temporary workaround, it might be possible
I can make a 3.19.0-15 for you. But you better report a bug of that
kernel, so it does not get into main.
But I do not see what could cause that. There is only one commit
between 15 and 16.
2015-05-02 21:52 GMT+03:00 Raphaël Jakse raphael.ja...@gmail.com:
I indeed have troubles with 3.19.0-16
My patch only loads the firmware, nothing else. If the adapter works
after firmware has been loaded wel on another kernel, it is strange.
2015-05-02 21:08 GMT+03:00 Raphaël Jakse raphael.ja...@gmail.com:
I'm going to try 3.19.0-16 to see. I have an Intel video card, I don't
think this is the
I'm running your kernel with your extra. It took very long to boot
(somewhere it waits for 3 minutes (saying so), I don't know why).
journalctl -xe gives continuous USB disconnect / new USB device and
bluetooth is not working, acting the way I described in comment #13.
Rebooting to the -15
Maybe you did not install extra of my image either? Try to download
the files again and install one more time.
2015-05-02 22:22 GMT+03:00 Raphaël Jakse raphael.ja...@gmail.com:
My bad, I didn't install linux-image-extra from ubuntu updates. In fact
3.19.0-16 unpatched is running fine with this
I agree. I wrote to the bluetooth linux driver maintainer and I will
tell him that too.
2015-05-02 22:47 GMT+03:00 Raphaël Jakse raphael.ja...@gmail.com:
I'm running your kernel with your extra. It took very long to boot
(somewhere it waits for 3 minutes (saying so), I don't know why).
14 matches
Mail list logo
