[Ubuntu] Bluetooth stopped working on recent Ubuntu kernels #50
Comments
|
@esil That tutorial helped me- http://www.tldp.org/LDP/lkmpg/2.6/html/x380.html |
|
Am I really the only one with that issue? Tutorial helps, but doing it every install is very, very annoying. |
|
A bug report can be opened at https://bugzilla.kernel.org so that the kernel includes the BT patch |
|
well, the problem is not in the kernel itself I think.
|
|
@Pilleo : but you still need to patch the btusb.c right? if the patch could be included in the mainline kernel, all other new releases would be fixed automatically... i.e there would be no need for separate patch anymore. |
|
@neurobin , that would be awesome! I will try to describe that issue as soon as possible for mainline, but here at first, so that you could check that it is acceptable issue for mainline. But first a confirmation that it is not only my issue! Guys, anyone, does bluetooth installation works ok for you? |
|
The only bluetooth device I have is a jbl flip4 and of course it doesn't work on ubuntu 17.04. Very annoying that in 2017, ubuntu still can't just be plug and play ! |
I am also having this problem, I just wanted to let you know. I did what you suggested and figured it out, so bluetooth is working. But I do suspect I will have to do it every time a new kernel comes out. |
|
@rachentp |
|
It's not corrupted, but that error could be due to a multitude of things. From what you've said it sounds like the btusb.ko is not created which you need to copy over to the drivers/bluetooth directory. I can further assist, but would need logs.
…On May 13 2019, at 10:35 pm, Sudeepam ***@***.***> wrote:
Hi, I am on linux mint 19, and I tried running the bpatch script. I was getting an error on line 164 of the script, saying that drivers/bluetooth directory is not found. I modified the script to create this directory before execution, but now on the next line, I am getting the following error...
cp: cannot stat 'btusb.c': No such file or directory
I checked the directory and this file indeed is missing, can anyone explain how this can be fixed? The kernal I got was linux-signed-4.15.0 and I think this is corrupted somehow.
—
You are receiving this because you were mentioned.
Reply to this email directly, view it on GitHub ***@***.***/0?redirect=https%3A%2F%2Fgithub.com%2Fneurobin%2FMT7630E%2Fissues%2F50%3Femail_source%3Dnotifications%26email_token%3DAF5PUFFW5TJ7P3BISSV7M23PVJFRFA5CNFSM4C2D5FLKYY3PNVWWK3TUL52HS4DFVREXG43VMVBW63LNMVXHJKTDN5WW2ZLOORPWSZGODVKKAFQ%23issuecomment-492085270&recipient=cmVwbHkrQUY1UFVGSEZUS0xaUU1GRkgyU0xQUzUyNDZEQkZFVkJOSEhBWE5QTzRBQHJlcGx5LmdpdGh1Yi5jb20%3D), or mute the thread ***@***.***/1?redirect=https%3A%2F%2Fgithub.com%2Fnotifications%2Funsubscribe-auth%2FAF5PUFDX3ZY43YKOI7LYGULPVJFRFANCNFSM4C2D5FLA&recipient=cmVwbHkrQUY1UFVGSEZUS0xaUU1GRkgyU0xQUzUyNDZEQkZFVkJOSEhBWE5QTzRBQHJlcGx5LmdpdGh1Yi5jb20%3D).
|
|
Hi @rachentp, I am being told that kernal 4.15 is unsupported due to changes in directory structure but if there is still a workaround that you can think of, can you explain the right way to share logs? |
|
Save your terminal output when you type in ./bpatch. Send me a link to it or reply to this thread with a link to it. Any kernel 4.15+ bpatch will not work without some tweaks. It has to do with the vermagic
…On May 15 2019, at 12:36 am, Sudeepam ***@***.***> wrote:
Hi @rachentp ***@***.***/0?redirect=https%3A%2F%2Fgithub.com%2Frachentp&recipient=cmVwbHkrQUY1UFVGQ0FFVzdRNVlFNjNXM1hSSjUyNUQyQlJFVkJOSEhBWE5QTzRBQHJlcGx5LmdpdGh1Yi5jb20%3D), I am being told that kernal 4.15 is unsupported due to changes in directory structure but if there is still a workaround that you can think of, can you explain the right way to share logs?
—
You are receiving this because you were mentioned.
Reply to this email directly, view it on GitHub ***@***.***/1?redirect=https%3A%2F%2Fgithub.com%2Fneurobin%2FMT7630E%2Fissues%2F50%3Femail_source%3Dnotifications%26email_token%3DAF5PUFDNBSPWADMCUS3IR5DPVO4RRA5CNFSM4C2D5FLKYY3PNVWWK3TUL52HS4DFVREXG43VMVBW63LNMVXHJKTDN5WW2ZLOORPWSZGODVNZEMI%23issuecomment-492540465&recipient=cmVwbHkrQUY1UFVGQ0FFVzdRNVlFNjNXM1hSSjUyNUQyQlJFVkJOSEhBWE5QTzRBQHJlcGx5LmdpdGh1Yi5jb20%3D), or mute the thread ***@***.***/2?redirect=https%3A%2F%2Fgithub.com%2Fnotifications%2Funsubscribe-auth%2FAF5PUFEEQMC7NFMQPEDQVCTPVO4RRANCNFSM4C2D5FLA&recipient=cmVwbHkrQUY1UFVGQ0FFVzdRNVlFNjNXM1hSSjUyNUQyQlJFVkJOSEhBWE5QTzRBQHJlcGx5LmdpdGh1Yi5jb20%3D).
|
Hello!
I had Ubuntu 16.10, and bluetooth worked fine on every default kernel until kernel 4.8.26(including it). After it bluetooth stopped working. It still works fine on xanmod kernel.
Today I updated to Ubuntu 17.04, and bluetooth also does not work on default 4.9.11 kernel.
WiFi works fine everywhere with any kernel.
No sure what should i add here, so I am attaching dmesg output, feel free to ask for any details.
Thank you.
The text was updated successfully, but these errors were encountered: