Newish Linux user noticing kernel and bluetooth errors on boot and shutdown, want to try and fix them

I tried to see if I could fix the bios error by following this guide and it seems to have failed. Also doing the test I realized that it appears that restart isn’t working on my computer at the moment. Which meant that I used the restart button on the physical PC to do it instead.

For future reference, the > and >> operators can be used to write stdout to a file, the first one overwrites data while the second one appends it. E.g.

echo hello > tmp.txt
echo world > tmp.txt
cat tmp.txt

Should give the output world while

echo hello >> tmp.txt
echo world >> tmp.txt
cat tmp.txt

Gives the output hello\nworld.

I will need to look into this further, but sounds like a bad bios update. Does your motherboard have a reflash button?

@ultraforce, you mentioned you are double booting. Do both operating software have there ownseparatee disks, meaning twoseparate physicall disk?. When I was dual booting, I had an issue simlar to yours, which is one of the reasons I switched to runing Windows in a virtual machine.

Yes both systems have their own seperate disks, nvme ssd for Linux and media on Linux, SATA ssd for Windows. I was worried about the whole issues of Windows sometimes messing with Linux installations so I got a third SSD and unplugged the nvme ssds during the installation of Windows.

There is a BIOS Flashback button yes. I actually don’t know if the USB stick I used for the most recent BIOS update was of the officially supported format types so since I have found the normal BIOS USB I can try reinstalling the BIOS update if you think that might be helpful.

I think it is worth a shot. Otherwise back to researching :slightly_smiling_face:

Sadly it didn’t work got the same errors as before. Here is the whole dmesg. I probably should focus on work for a bit and also just got access to a dell optiplex running ubuntu 18.04 lts that I’ll try out doing some stuff with so might take a bit longer to respond.
dmesg.txt (130.3 KB)

Sorry I messed up and didn’t send it as a reply turned out it didn’t work with the errors being identical to the ones before.

Looking for examples with the same errors I found someone using arch who got the same errors with a motherboard that is very similar to mine outside of the nouveau errors(makes sense as I’m not using Nvidia).

Should I maybe try the solution that seemed to work for them?

Also given this bios - ACPI error on every boot - Ask Ubuntu article is it probably best to ignore/contact ASUS about ACPI?

@ultraforce As long as everything else works, meaning you are able to do everything you want with the computer, I would ignore the errors and contact Asus. I always have had boot errors on my Linux machine. I ignore them.

only thing I’ve run into an issue on my computer seems to be attempts at restart through the button on KDE but don’t know how to look at logs for what’s going on after it says the PC will restart.

I do not understand your statement of attempts a restart through the button on KDE. Could you go into more detail.? Maybe upload a picture of the button you are talking about. Go to the command line (the app where you type commands) and type the following command.

cd /var/log
That is the location where KDE stores all the log files. At least that my location. I would start googling every error or failler untill there isn’y errors or failers.
I think you are complicating your Linux journey by Dual botting two different operating systems. Sinse you have two different compuyers I sujest runing Windows on one and KDE on the other.
It is your life. Do what you want.

If you don’t mind me asking, what task do you need done that requies Windows?

well I was going to try and explain, basically the restart button on the application launcher when pressed would not actually restart the computer it would shutdown the Kwin session and any app I had and just hang on the terminal but I just tried and it doesn’t any more.

1 Like

the restart button started working again.

Windows is mostly there because of a piece of hardware I have that only officially supports windows and Mac OS. It also is a back up if I screw something up since I’m not using BTRFS and haven’t yet bothered setting up any sort of back up for my main desktop. So Windows on a separate drive should be safe from breaking.

Additionally, it’s in case there is a game I want to play that really wants Windows to be used, I’ve gotten into itch.io type games at times which tend to not be designed for Linux compatibility. So just running the .exe on windows is faster.

Official support is irrelevant, either it works on Linux, or it works with hacks, or it does not. Often unofficial Linux support is even better out of box though.

For instance I have some third party gamepads for Switch that require USB cables in Windows but can run Bluetooth on Linux. Because screw official support, that is why. :face_with_tongue:

So do try to get that hardware working under Linux, if you cannot, just wait for a good time to replace that hardware (usually breaks or is obsolete).

Your point of having Windows just because is valid, though I recommend you to re-evaluate in summer of 2025 if you really need it.

There is nothing wrong with a Windows installation, use whatever works for you. Linux is all about expanding on that concept, and if Windows is still a part of your puzzle then let it be part of your puzzle for now.

In this case the reason I asked for a cheapo SATA SSD was that a peripheral worked except for the ethernet port and only case where support would go forward with returns and what not was if it also didn’t work on officially supported hardware. And it didn’t so I can get a replacement as soon as I get off my but and find a proper box to do the return.

@ultraforce From what I have read, a Windows update will corrupt Grub, and one day, you try to load KDE, and it won’t. I never got a corrupt Grub; I only Double Booted two OS for about six months before the inconvenience of double booting drove me insane. I either found Linux alternatives for the Windows takes, ran my Windows takes in a virtual machine or figured out how to get them to run with Wine.