msfjarvis
/
msfjarvis.dev
mirror of https://github.com/msfjarvis/msfjarvis.dev.git
1
0
Fork 0
Code Issues Packages Projects Releases Wiki Activity

Revise wording 

Signed-off-by: Harsh Shandilya <me@msfjarvis.dev>
This commit is contained in:
Harsh Shandilya 2020-07-17 15:45:33 +05:30
parent 3ba900578e
commit 6f282048ad
1 changed files with 3 additions and 5 deletions
Show Stats Download Patch File Download Diff File Expand all files Collapse all files

8
content/posts/making-a-bluetooth-adapter-work-on-linux.md
View File

@ -20,11 +20,11 @@ Thanks to this combination of factors, things got weird. I tried a bunch of thin
You're gonna need 1) a GUI to handle BT devices, b) the PulseAudio module for Bluetooth. For the GUI I used [blueberry](http://packages.linuxmint.com/search.php?release=ulyana&section=main&keyword=blueberry), and [pulseaudio-module-bluetooth](https://packages.ubuntu.com/focal/pulseaudio-module-bluetooth) for PulseAudio support.
I did `apt install -y blueberry pulseaudio-module-bluetooth` to get these on Linux Mint, you can do whatever your distro's preferred package handling method is.
I did `apt install -y blueberry pulseaudio-module-bluetooth` to get these on Linux Mint, you should use whatever your distro's preferred package management interface is.
### Fixing up the kernel (optional)
I mentioned earlier that I run a very slimmed down config, which means nothing that I didn't already use was enabled. This included Bluetooth, so I went ahead and enabled all the configs for it [here](https://msfjarvis.dev/g/linux/992c2d8bce8b). If everything works out, your dmesg should contain these lines
I mentioned earlier that I run a very slimmed down config, which means nothing that I didn't already use was enabled. This included Bluetooth, so I went ahead and enabled all the configs for it [here](https://msfjarvis.dev/g/linux/992c2d8bce8b), then installed the new kernel and rebooted into it. You shouldn't need to do this if you do not run a custom kernel. To be completely sure, check your dmesg for Bluetooth initialization logs:
```shell
$ dmesg | rg Bluetooth
@ -42,8 +42,6 @@ $ dmesg | rg Bluetooth
[ 0.327120] Bluetooth: HIDP socket layer initialized
```
If you run your distro's kernel, you shouldn't need to make any changes.
### Wrapping up
If you're not a relatively up-to-date distro, you might need to make some more manual adjustments before everything works. Open up `/etc/pulse/default.pa` in any editor with root access (so you can write your changes back), then look for `module-bluetooth-discover`. In my version of the file, I have this:
@ -73,6 +71,6 @@ Below it, add `/usr/bin/pactl load-module module-bluetooth-discover` so the fina
/usr/bin/pactl load-module module-bluetooth-discover
```
This will manually load the module when X11 triggers PulseAudio init. This is more a hail mary, and if you want, you can test without it but it won't hurt to add it anyway.
This will manually load the module when X11 triggers PulseAudio init. This should ideally not be required so you can try without this change, but it won't break anything if you add it anyway.
Once done, reboot your computer and you should be able to pair and connect to devices and play audio through them.