this post was submitted on 07 Jul 2026
9 points (100.0% liked)

Linux Mint

3537 readers
1 users here now

Linux Mint is a free Linux-based operating system designed for use on desktop and laptop computers.

Want to see the latest news from the blog? Set the Firefox homepage to:

linuxmint.com/start/

where is a current or past release. Here's an example using release 21.1 'Vera':

https://linuxmint.com/start/vera/

founded 5 years ago
MODERATORS
 

Edit: Thanks everyone thar tried to help. I will install the OS, sinse the problemm looks a bit more complex then I initially thought 🥲

you are viewing a single comment's thread
view the rest of the comments
[–] Adverse_Reaction@anarchist.nexus 2 points 5 days ago (2 children)

What is the output of this command:

sudo dmesg -l err

[–] Homo_Erectus@lemmy.zip 0 points 4 days ago* (last edited 4 days ago) (1 children)

ACPI ERROR

ACPI BIOS ERROR

Also; sry for the late

[–] Adverse_Reaction@anarchist.nexus 2 points 3 days ago* (last edited 3 days ago)

ACPI errors are typically not important. Are you sure there are no other errors above or below your screenshot?

FWIW, you can use the following command to see what BIOS version you currently have, then check with the manufacturer to see what version is most up-to-date and install that. It may quiet down your dmesg/log output if nothing else.

Be warned, there is a certain risk to updating the BIOS. Things can go wrong or even create new problems, but in general it is advisable to keep the BIOS up-to-date. The command to determine what BIOS version you have installed is:

sudo dmidecode -s bios-version  

Also, you should try to boot with nothing unnecessary connected to the PC, to see if it behaves differently. A poorly initialized hardware device can cause any number of strange behavior. USB/Bluetooth devices are easily overlooked/forgotten/ignored as inconsequential, but can hang a system up. Also check the cable connections if it's a desktop PC.

On top of all that I would run fsck on your drive to make sure you aren't dealing with file corruption of some kind. This can be done during boot via the recovery console.

Reboot and hold the Shift key during boot. This will get you to the GRUB menu, even if it is not normally shown.

Select “Advanced options”

Select “Recovery mode” for the kernel version you are normally using.

In the recovery menu, select “fsck“

When prompted to remount the root filesystem, select “Yes“

When fsck completes, “Resume” will continue the boot process normally.

I hope this helps. If not, you may want to consider restoring from backup, assuming you have made a working backup via Timeshift or similar.

Barring that, you either need to dig much deeper into the logs and boot process, or simply reinstall the OS. Testing the hardware by booting a live USB session is also advisable - that can be done via the same USB image you probably used to install the OS to begin with. If the problem persists, then you know something has gone wrong with a hardware component.

Good luck, and keep us posted on your outcome.