MX-21 installation freezes after initial set-up

[Huckleberry Finn]

You may need these steps to really disable secure boot:

Step-By-Step: Make A Backup Of Existing Keys And Disable Secure Boot

• Plug-in a USB drive.

• Restart your computer and enter into the BIOS utility by pressing the Asus BIOS key applicable to your system. In my case, it was DEL. Keep an eye out for instructions on the first screen. This should load up the Asus UEFI BIOS utility interface.

• Go into the Advanced Mode (F7 or any other key as specified).

• Go into the ‘Secure Boot‘ option under the Boot section.

• Ensure the proper OS Type is selected, and go into Key Management.

• Select ‘Save Secure Boot Keys‘ and press enter.

• Select the USB drive when asked to ‘Select a File System‘.

• Four key files named PK, KEK, DB, and DBX are saved to the USB.

• Delete Platform Key (PK) to disable secure boot. (Note: Do not delete other keys)

• Save and restart to apply settings (usually F10) and boot with ‘secure boot’ disabled.

Shortly, most steps , usb etc. are just to backup first. Main idea is "Delete 'Platform Key' " , Save and restart .

[asinoro]

Off course, there is always the possibility to install MX21 on one computer and to migrate to another, as long the partition size is the same with the gparted. You can do this with an Ethernet crossover cable, or external USB drive and the help of the forum if you don't know how to do this.

[Yoshio]

Sorry, had been a bit busy over the weekend.

By now I up-dated the bios and set a admin PW. Unfortunately that didn't help to change anything.

@Huckleberry Finn - thanks for your post again. That is exactly how I did, do it and for deleting the Platform Key it works and this actually what makes it at all possible to boot, at least, in the live environments of some of the distros I tried. Unfortunately CSM always gets set back to "enabled" with the remark that this is necessary due to my graphics card.

The only bit of new information I could gain is the following:

Augenblickliche Bootparameter it says: "BOOT_IMAGE=/antiX/vmlinuz quiet nosplash nomodeset lang=de_AT kbd=at tz=Europe/Vienna

This is the point where the whole system freezes and keyboard and mouse are deactivated.

With the start parameters: "quiet" and "nosplash" I do get a reboot of the system, no freeze.

With MXPI, I guess, MX-Linux's Package Installer is meant? If so, unfortunately, I cannot get to it as I cannot boot into the live environment.

@asinoro - What You wrote in your post, that had been something I had been thinking about as well. I was wondering if this could be an option. I would have the option to install MX on an external hard drive using my old notebook and then copy this external installation over to the internal SSD of my new PC. Do You think that this is going to work?

[asinoro]

@asinoro - What You wrote in your post, that had been something I had been thinking about as well. I was wondering if this could be an option. I would have the option to install MX on an external hard drive using my old notebook and then copy this external installation over to the internal SSD of my new PC. Do You think that this is going to work?

By migrating the MX21 you have the option that you can boot first with systemd and then migrate it, it is an option that do not exist in the live medium of MX. Secondly, from schroot method of any other Linux live medium you can access the MX system and perform command to install or remove applications.
And maybe will boot ok without any problem, as long you have installed another Linux preferably Ubuntu based, that has the boot repair, and gives you also the possibility to access the MX21 through it.

[razor2021]

If you ran the MX21 live-only off a USB stick and leave this session up, does it also freeze over time? In theory, running a live session of the USB stick is loading it all into RAM and also runs the same PC components mostly. If that does not freeze, it's puzzling to know why it continues to freeze on your main PC.

[Huckleberry Finn]

...
The only bit of new information I could gain is the following:

Augenblickliche Bootparameter it says: "BOOT_IMAGE=/antiX/vmlinuz quiet nosplash nomodeset lang=de_AT kbd=at tz=Europe/Vienna

This is the point where the whole system freezes and keyboard and mouse are deactivated.

With the start parameters: "quiet" and "nosplash" I do get a reboot of the system, no freeze.

Yes, but if you applied it like that, it's nomodeset that did the trick. And (if you say yes) it means Nouveau was unable to be loaded with MX though it was possible with same kernel on Debian ... Whatever.. If that's true, just boot to live session with nomodeset (or as you did with nosplash), and install, then you may/may not install Nvidia Driver or 5.16 kernel etc.. (The rest is easy)

With MXPI, I guess, MX-Linux's Package Installer is meant?...

Yep.