Support for MX and antiX Linux distros
https://www.forum.mxlinux.org/
But it's already modesetting :) He just tried the NDI on live session and it refused him as he had no such device :)m_pav wrote: Mon Jan 08, 2024 6:02 pm... you may be able to use MX Tweak to change the driver back to Modesetting...
here in the Manjaro Reddt:Update: SOLVED! Thank you to everyone who provided any sort of help/advice. I’m still not exactly sure what caused the problem, but all I have to do when booting is press shift to be taken to the GRUB, going to advanced options, then selecting the thing that says “fallback initramsfs” and from there it boots perfectly every time.
Fallback is kind of without micro-code, hence the suggestions made to disable micro-code loading.j2mcgreg wrote: Tue Jan 09, 2024 9:36 am I found this solution:here in the Manjaro Reddt:Update: SOLVED! Thank you to everyone who provided any sort of help/advice. I’m still not exactly sure what caused the problem, but all I have to do when booting is press shift to be taken to the GRUB, going to advanced options, then selecting the thing that says “fallback initramsfs” and from there it boots perfectly every time.
https://www.reddit.com/r/ManjaroLinux/c ... op_but_it/
for the same problem on the same laptop.
It should give some clues as to what is borking your MX install.
Charlie Brown wrote: Tue Jan 09, 2024 9:06 amBecause the command was issued when on live session.siamhie wrote: Mon Jan 08, 2024 11:40 pm...
Your boot order is still pointing to the PNY USB device (Boot0001) as the default and not MX Linux (Boot0000)...Code: Select all
BootCurrent: 0001
Code: Select all
$ efibootmgr -v
BootCurrent: 0001
Timeout: 2 seconds
BootOrder: 0001,0000
Boot0000* MX Linux HD(1,GPT,4ceacac5-4e7e-49c9-8b4d-2f087149e243,0x800,0x80000)/File(\EFI\MX\grubx64.efi)
Boot0001* UEFI: PNY USB 2.0 FD PMAP, Partition 2 PciRoot(0x0)/Pci(0x14,0x0)/USB(3,0)/HD(2,MBR,0x1a4cc5ae,0x39b8800,0x18800)..BO
Code: Select all
sudo efibootmgr -n 0000Maybe network issue - or a timeout of the forum itself. Just mark the post wich made it [Solved] as such.evenkeel wrote: Tue Jan 09, 2024 6:42 pm @fehlix, I don't understand what happened to this thread. I'm the original poster but wasn't notified that my problem was solved. I wrote to your attn 3 or 4 hours ago saying that the dis_ucode_ldr edit you suggested I try brought me (without the Live stick) to the desktop. Smiley emoticon and all. I asked for next steps. I don't see that posting here. Please advise. Thank you.
Sometimes it helps to copy/paste your formulated text temporary into featherpad or geany text editor,evenkeel wrote: Tue Jan 09, 2024 9:26 pm @fehlix, I just answered your question but it disappeared. Probably operator (me) error. I think I closed the browser too quickly.
OK, what I would now do,evenkeel wrote: Tue Jan 09, 2024 9:26 pm I will try to be brief: the error message that seemed to go very quickly was the: ‘Failed to open EFI/BOOT: Invalid parameter. Failed to load image (??): Invalid parameter. Start image returned invalid parameter. Falling back to default loader.’ I was mistaken in my initial posting, it did NOT appear after Welcome. It appeared after Dell logo,--F12 to boot sequence and exit,--but BEFORE Welcome. The first menu I see on live-session is the same as page 27 of the manual. With the cursor landed on Language - Keyboard, there was a 59 second countdown (but I had played with settings); when I moved the cursor up to MX-23.1_ahs and pressed enter, there was a five second countdown. But the 'Failed to open EFI/BOOT: Invalid parameter, etc' message was the very brief one. Now that I know what it says of course it looks like a billboard. Anyway, I did not see this error msg after booting with the dis_ucode_ldr edit. Quiz me further if I misunderstood you or failed to answer your question. I will continue to work on this. But now must sleep.
Code: Select all
sudo apt purge cryptsetup-initramfs mdadm
Code: Select all
sudo apt purge "rtl*-dkms"