UEFI Install boots to black screen [Solved]

[Charlie Brown]

... you may be able to use MX Tweak to change the driver back to Modesetting...

But it's already modesetting :) He just tried the NDI on live session and it refused him as he had no such device :)

Display: x11 server: X.Org v: 1.21.1.7 compositor: xfwm v: 4.18.0 driver: X: loaded: modesetting ...

[j2mcgreg]

I found this solution:

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.

here in the Manjaro Reddt:

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.

[fehlix]

I found this solution:

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.

here in the Manjaro Reddt:

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.

Fallback is kind of without micro-code, hence the suggestions made to disable micro-code loading.

In addtion OP has not mentioned whether the GRUB Menu is shown.
In the case Grub Menu is not shown, either hold a key like spacebar,
or increase grub's menu timeout,
b/c some systems seems to have different interpretation
of the timeout, e.g instead of second they use milliseconds.

[siamhie]

...

Code: Select all

BootCurrent: 0001

Your boot order is still pointing to the PNY USB device (Boot0001) as the default and not MX Linux (Boot0000)...

Because the command was issued when on live session.

You're right. BootCurrent shows what you booted into.

My live ISO boot.

boot-order.jpg

His BootOrder still has PNY USB as the default though.

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

[Charlie Brown]

He could try just for next boot (at least no harm to try)

Code: Select all

sudo efibootmgr -n 0000

Reboot (preferably without the usb attached)

[evenkeel]

@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.

[fehlix]

@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.

Maybe network issue - or a timeout of the forum itself. Just mark the post wich made it [Solved] as such.
And also try install another kernel as mentioned already and check whether the other kernel would work with µcode-loading or not. And if you cannot boot without the addtion boot parameter,
open MX Boot Options and add the additional boot parameter to the boot options line.
Also one question I had whether you originally always got the GRUB menu or in case the small timeout made it to not show the GRUB menu long enough. I think, settings timeout to -1 in boot options may disable grub-menu timeout, just in case.
Any other questions please, post again.

[evenkeel]

@fehlix, I just answered your question but it disappeared. Probably operator (me) error. I think I closed the browser too quickly. 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.

[fehlix]

@fehlix, I just answered your question but it disappeared. Probably operator (me) error. I think I closed the browser too quickly.

Sometimes it helps to copy/paste your formulated text temporary into featherpad or geany text editor,
so you won't loose the text written, when the message did not made onto the server, so you would be able to send again.

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.

OK, what I would now do,
* First add the "dis_ucode_ldr" boot parameter to disable µcode-loading to the GRUB menu,
by opening MX Boot Options and add to the boot parameter line space separated: dis_ucode_ldr.

* Maybe before you add the new kernel, remove some packages
which are not used like those RAID related and luks encryption related:

Code: Select all

sudo apt purge cryptsetup-initramfs mdadm

and also any of the wireless Realtek driver not used by your system:

Code: Select all

sudo apt purge "rtl*-dkms"

This would make installing / upgrading kernels "faster":
* Next install latest liquorix kernel.: Open MX Package Installer (MXPI)
and select within the first tab Pop. Apps.. -> Kernels -> latest Liquorix kernel
to install.

Now reboot and check whether the new kernel would boot,
you can test/check µcode loading by removing the µcode boot parameter dis_ucode_ldr
which is now with the grub menu:
On GRUB menu entry: Press [E] -> arrow keys down to the linux line
and remove from end of line the µcode boot parameter. F10 or [Ctrl]+x to boot.
If this will bring you a black screen again, keep the µcode parameter,
otherwise if that works you can remove parameter with help of MX Boot Options.

[evenkeel]

@fehlix featherpad. Check. I did all you suggested. It's booting. You make this stuff look easy. I installed the "Liquorix 64 bit (ahs updates package)". Is that the correct kernel? Laptop now booting both with and without "dis_ucode_ld" boot parameter. Wiser to keep or delete? While doing one of the two purges and again during the liquorix install I saw "Possible missing firmware /lib/firmware/i915/mtl_huc_gsc.bin for module i915." Also "Possible missing firmware /lib/firmware/i915/mtl_guc_70.bin for module i915." Is that make or break? Many thanks.