MX Linux Forum

... re-ran

echo RESUME=UUID=fe797927-c0e9-400d-905e-be7fb41ae116 | sudo tee /etc/initramfs-tools/conf.d/resume ; sudo update-initramfs -uk all
I think this is the alternative to MX Boot Options...

Nope, that's the alternative (and the corrected) to resume_offset=5997854720 which you should ...

Here's one of the reasons why we insist on QSI:

Did you use this consciously? (Do you have a swap file?)

resume_offset=5997854720

(... If no (I guess so) remove it in "MX Boot Options", Apply. You can re-apply the one in post #25 )


When booted with systemd:

sudo systemctl edit apt-daily ...

I'd add that with that hardware, you should be using the AHS version of MX. I suspect that the problem, all along, has been that the driver being used for your NVMe is inadequate for the hardware it is now tasked with. Two days ago I suggested that you try to install MX 21 on your NVMe and you ...

If still not: start the pc with systemd (select an entry with systemd on Grub Menu, if you can't see: look under "Advanced Options") and :

systemd-analyze critical-chain ; systemd-analyze blame


I tried again and the systemd technique did yield an output:


$ systemd-analyze critical-chain ...

With this one it's 40 posts and it'll be page 5 with the next post, still we don't have the QSI .


If there's an option in Bios like "Intel SpeedStep® Technology" , enable it, save, exit.


If no (or if still the same):

echo RESUME=none | sudo tee /etc/initramfs-tools/conf.d/resume ; sudo ...

tone2 wrote:


Btw when I disabled SATA it wouldn't boot at all.

That's not what I said to do. What you want to do is prevent the bios from trying to boot from a non-existent or non-operational device. It can be as simple as adjusting the boot order so that the NVMe is given first priority and ...

Does anyone have any experience with efibootmgr?
I was wondering if this could help

tone2 wrote:

but the nvme is brand new

With NVMEs that is no guarantee of health. It could have a manufacturing or handling defect before you purchased or been damaged during shipping. As mass storage devices go, they are the least robust of the lot.


Especially now that they've stopped ...

Two thoughts come to mind:
1) thoroughly check your bios if either the SSD or the NVME can be toggled off. Your long boot time could be accounted for if the bios was looking for, but not locating the SSD (which you had removed).

2) you NVME is faulty.


Thanks anyway, but the nvme is brand new ...

All this time you have been trying to install an image of your old system, right? I think that you need to eliminate it as the point of failure by trying to install the default XFCE version of MX 21. If this default version of MX 21 installs without a hitch, then you will know that the problem ...