MX Linux freezes at startup.

[chamane2025]

Ctrl+Alt+F4 gives you a terminal and prompt or does nothing?

If you get a terminal prompt, then try renaming this file:

~/.config/xfce4/xfconf/xfce-perchannel-xml/displays.xml to displays_old.xml

and then reboot.

Unfortunately, it does nothing. I tried all possible ctrl+alt+F's. I get no reaction but a completely black screen.

[chamane2025]

Any other suggestion is beyond my knowledge.

do you see a graphical menu when you boot the installed system? if so, that may have an Advanced Options submenu (as previously mentioned). if you use the arrow key to move down to that entry then hit enter there may be more options. sometimes trying some options from there can be helpful in situations like this.

I tried systemd from the advanced options on the graphical menu. You are right, kermit the frog made the same suggestion previously. It is now working, I am back in the system. But I have to select that option on the graphical menu everytime I reboot now. Is there a way to make it work again by default?

[xaol]

it has been a while since i've booted mx with kde (in case there are any differences to what i am describing next), but in MX Boot Options do you see a checkbox in front of an item labeled "Enable saving last boot choice"? if so, that may be something to try. i don't recall how it works exactly. it may present that as the first boot option to make it easier for you to select (hopefully).

editing to add: i did test that real quick in an mx 23 kde virtual machine. i found it slightly easier to do if adding a check mark to both the "last choice" as well as "Use flat menus (no submenus)" boxes. that saved me one press of the Enter key at least :)

[chamane2025]

No checkbox on my side. I don't mind using a submenu now, it's just that I don't understand why I have to.

Thanks all for the help.

[Kermit the Frog]

Just click the "Boot to" dropdown in "MX Boot Options" and select any of them with "systemd" ... "Apply".

[chamane2025]

Just click the "Boot to" dropdown in "MX Boot Options" and select any of them with "systemd" ... "Apply".

Done. Working great again.

Thanks a lot !

[Kermit the Frog]

You're welcome.

So, maybe sddm-modified-init was somehow broken ...

[Kermit the Frog]

On this opportunity @Adrian :

MX Boot Options shows the current menu entries in "Boot to", that one is ok (even perfect, cause it shows them "as is" even when grub.cfg was manually edited by you).

However :

• It doesn't show the current boot parameters. (I don't mean it's a must but it would be better imho).

• But the one that seems to need a fix is that it shows "no" rather than "nosplash" no matter what option was selected: Very Detailed, Detailed or Limited. (Like: no , no quiet, no quiet hush)

Maybe you consider for next versions.

[fehlix]

• But the one that seems to need a fix is that it shows "no" rather than "nosplash" no matter what option was selected: Very Detailed, Detailed or Limited. (Like: no , no quiet, no quiet hush)

Seems to me something within your settings maybe different:
Check default:

Code: Select all

grep LINUX_DEFAULT /etc/default/grub
GRUB_CMDLINE_LINUX_DEFAULT="quiet nosplash"

Check MX Boot Options:

mxbo-parameters.jpg

So it seems to be it shows as it should be (or as designed).

[Kermit the Frog]

Code: Select all

$ grep LINUX_DEFAULT /etc/default/grub
GRUB_CMDLINE_LINUX_DEFAULT="quiet nosplash"

Code: Select all

$ inxi -Sxxxza
System:
  Kernel: 6.11.2-1-liquorix-amd64 arch: x86_64 bits: 64 compiler: gcc v: 12.2.0 parameters: audit=0 intel_pstate=disable
    BOOT_IMAGE=/boot/vmlinuz-6.11.2-1-liquorix-amd64 root=UUID=8a501b97-def8-9a35-ac87-139f05d4d977 ro quiet nosplash
...