Solus media machine dropping Bluetooth connections

WetGeek

Recently my Solus Plasma desktop media machine has begun to drop the keyboard, mouse, and soundbar that are connected to it using Bluetooth. I have to use a different wireless mouse to reboot the machine, and upon startup it has no problem reconnecting with those devices automatically. When the proble occurs, I cannot reconnect the peripherals using the wireless mouse. Clicking on Connect in the Bluetooth settings does nothing.

These occurrences seem to be quite at random. Every computer here, including my daily-use laptop, uses Solus KDE Plasma, and no other computer has exhibited this problem. The media machine and my laptop use the same keyboard and mouse, using two different Bluetooth channels.

Any ideas?

brent

WetGeek Every computer here, including my daily-use laptop, uses Solus KDE Plasma, and no other computer has exhibited this problem.

based on that statement I'd say hardware. I've had dongles at end of life and usb ports give out too. I've had this Budgie once upon a time and reverted to a wired mouse and keys and never looked back. back then I was convinced it was software though, based on a single machine...ps. merry xmas eve

WetGeek

brent based on that statement I'd say hardware

You may be right. The machine is a DELL Optiplex desktop, though, and Bluetooth is internal -- not a dongle.

WetGeek

Got my weather-delayed laptop today, and used Etcher to create a Bunsen Labs Beryllium installer. First attempt failed to boot. I had told the installer to use the whole 512 GB SSD. So I used a "live" Budgie session to remove all the existing partitions and tried to install again. Another failure. I thought I might have removed the installer USB drive too soon, so I tried again, only to get the "No bootable devices found" error again.

I've been trying a UEFI installation. Maybe tomorrow I'll modify the UEFI/BIOS to allow legacy boots, and see if it will boot that way. I've had no problem at all with installing onto a VM. If it works as a legacy boot, I'll settle for that.

brent

WetGeek Try UEFI first, Legacy second. Doesn't matter if its the only distro.
Don't give Bunsen the whole disk, it does not want the whole disk. It just wants the largest of unallocated spaces. So make it one.
Format the whole SSD as GPT, in gparted.
I made the USB per their preference: Rufus (in WIN).
Then make two partitions in a live iso, in gparted.. One bigger than the other. Like 200GB and another at 190. It will grab the 200GB and make its own swap/boot/and ext4. Try that. That's how it worked for me.

WetGeek

WetGeek If it works as a legacy boot, I'll settle for that.

I decided to stay up past my bedtime, and try a legacy installation. It worked. I've done just a bit of configuration for now, the rest will be tomorrow. At least I can boot Beryllium now, and it's blazing fast, so legacy boot is fine with me.

WetGeek

brent That's how it worked for me.

Sorry, by the time I read your reply, I'd already let Beryllium have the whole 512 GB. That was actually my intention from the beginning. It worked quite well. More configs to do tomorrow.