To be frank, I use it a lot here on the forums because it's the universally surest and fastest way to find out something. Mucking about to find what GUI someone is using is a waste of time considering how many different tools are available (with different degrees of efficacy) to do a similar job.
After installing those dkms drivers and rebooting, run "dmesg |grep -i bluetooth" again and see if there's mention of your device....on top do "lsmod |grep blue" to see if there's any module loaded at all.
Those "UART" lines in "dmesg" are for tethering over bluetooth but obviously w.o a recognized adapter there wont be any luck there either.
BTW,
I have encountered some dkms issues on the latest Debian kernels so you might try activating bluetooth manually.
First see if the service is running:
"systemctl status bluetooth.service"
If it says "running" do a restart with "systemctl restart bluetooth.service"
Start "bluetoothctl" with that same command, which will put you a special shell with a blue prompt.
It should say "Agent registered" ..... if not use "power on" and then "list" to see if there's a controler.
use "quit" or "exit" to leave the BT shell.
Then use one of the following options to load (or unload) the modules(from the github page) :
# Init
sudo modprobe rtbth
sudo rfkill unblock bluetooth
hcitool dev # check
# Switch off
sudo rfkill block bluetooth
# Switch on
sudo rfkill unblock bluetooth
# Shutdown
sudo pkill -2 rtbt
sudo rmmod rtbth
And do 1. and 2. again and see if anything has changed.
Well "modprobe rtbth" shows as outcome that the module didn't get loaded from where it's expected to be....making all further tests moot.
Let's first find out if anything at all got installed with: "sudo find / |grep rtbth"
I just installed on a machine using "sudo gdebi rtbth-dkms_3.9.8~git20230219-1~lunar2_amd64.deb" which do show the expected 'line 2497' errors for loading at boot
❯❯❯ sudo gdebi rtbth-dkms_3.9.8\~git20230219-1\~lunar2_amd64.deb
[sudo] password for triantares:
Reading package lists... Done
Building dependency tree... Done
Reading state information... Done
Reading state information... Done
Bluetooth driver for RT3290 Wireless
DKMS package of Bluetooth driver for RT3290 Wireless cards
Do you want to install the software package? [y/N]:y
/usr/bin/gdebi:113: FutureWarning: Possible nested set at position 1
c = findall("[[(](\S+)/\S+[])]", msg)[0].lower()
Selecting previously unselected package rtbth-dkms.
(Reading database ... 468123 files and directories currently installed.)
Preparing to unpack rtbth-dkms_3.9.8~git20230219-1~lunar2_amd64.deb ...
Unpacking rtbth-dkms (3.9.8~git20230219-1~lunar2) ...
Setting up rtbth-dkms (3.9.8~git20230219-1~lunar2) ...
Loading new rtbth-3.9.8 DKMS files...
/usr/sbin/dkms: line 2497: echo: write error: Broken pipe
Building for 6.4.0-0.deb12.2-amd64
/usr/sbin/dkms: line 2497: echo: write error: Broken pipe
Building initial module for 6.4.0-0.deb12.2-amd64
/usr/sbin/dkms: line 2497: echo: write error: Broken pipe
Done.
/usr/sbin/dkms: line 2497: echo: write error: Broken pipe
/usr/sbin/dkms: line 2497: echo: write error: Broken pipe
rtbth.ko:
Running module version sanity check.
- Original module
- No original module exists within this kernel
- Installation
- Installing to /lib/modules/6.4.0-0.deb12.2-amd64/updates/dkms/
depmod....
but a subsequent "sudo find / |grep rtbth"
now does show the modules are in /var/lib/dkms" and ..."sudo modprobe rtbth" doesn't provide any errors
on top "lsmod |grep rtbth" shows it gets loaded for bluetooth.
After which I cannot do any parallel testing as I don't have that realtek hardware... running the next commands will be up to you.
sudo rfkill unblock bluetooth
hcitool dev
On a side note:
If you select lines in a terminal with your mouse, you can then 'middle-click' in i.e your message and the selected text will get copied over. If you enclose that as "preformatted text" (or Ctrl + e) it will show up nicely in the messages.
Which, is a lot easier than uploading pictures all the time (and avoid clogging the servers eventually)
