I hadn't shut the computer down for a few days. It had run a few updates and restarted afterward just fine. This morning I started getting this message after boot:
Trying an earlier kernel gave me the following:
Followed by the ACPI stuff again, but there is also an issue of mint-vg not found:
The "mint-vg not found" part bugs me as I had this before. Did a clean install from new media, and now it's happened again. I can't get into the system so I don't know how to run fsck, or what that is. Not sure what busybox is.
_____ _____ _____ _____ _____ _____
I couldn't find much on Mint forums, except this (viewtopic.php?f=46&t=313738&p=1772615&h ... S#p1772615) but I don't think it is the same problem, it's just similar.
Looking further afield I found this:
https://www.linuxquestions.org/question ... 175605357/ where the most revealing comment said:
This device is formerly Windows 10 and I had problems with drive formatting when I swapped over to EXT4 so I thought it may be that. I went back to my Mint installation and made sure I was using UEFI with secure boot disabled and fast boot disabled. Still no go.Just to give you some background, as you probably know, ACPI is the power regulation code in your motherboard's BIOS/UEFI:
It's suppose to be a standard that any operating system can properly implement. However, in typical Microsoft fashion, MS operating systems do not follow or properly implement the ACPI standard. Instead, MS gives motherboard manufacturers their own improperly implemented ACPI code for inclusion in the motherboard BIOS/UEFI. The code runs fine with MS windows but all for other operating systems like linux there can be problems. Because of MS's market dominance, the faulty ACPI implementation from MS has become the de facto industry standard. As a result, linux and other non-MS operating systems have to reverse engineer the faulty ACPI implementation from MS. That's why you can see problems in linux with ACPI related functionality like suspend to ram, hibernate, etc.
Apparently, the ACPI related code in certain newer linux kernels has a problem with the typical BIOS/UEFI ACPI implementation on certain motherboards which is why we're getting those error messages. Even though I get those error messages at the beginning of the boot process, I've had no problems with suspend/resume or any other ACPI related issues. Here's another guy with the same problem so you are not alone:
The advice there was to not run in BIOS legacy mode by disabling UEFI but to run in UEFI mode instead with secure boot disabled.
Any suggestions on how to fix this issue?
PS. Apologies in advance if the images are too small to be readable, it hit the site limit of 640x480.