MX Linux Forum

Support for MX and antiX Linux distros
https://www.forum.mxlinux.org/

UEFI Install boots to black screen

https://www.forum.mxlinux.org/viewtopic.php?t=78776

Page 1 of 1

UEFI Install boots to black screen

Posted: Sun Jan 07, 2024 5:18 pm
by evenkeel
Nothing written here is intended to fault MX software. I’ve been using MX Linux exclusively since MX-15 and it’s worked great. I’m typing this on a 2016 Dell Optiplex desktop, sporting MX-21 that did not need a custom install. The “regular” installation created an efi system partition automatically. My problem began when I tried to install MX on a 2019 laptop. I am not a fan of this new UEFI architecture.

Please advise if you can. Many thanks in advance.

GOAL: Whole disk single boot Linux install of MX-23.1 AHS OS 64bit w/Xfce, assuming AHS is best. It’s going on a UEFI Dell Latitude 5500 laptop (2019). I want: (1) an EFI partition [as I understand it is necessary]; (2) combined /home partition; and, (3) SWAP.


PROBLEM: I have tried to install MX21, then MX23.1 and now MX-23.1 AHS on this laptop over a four week period involving maybe 12 installations, but couldn’t / can’t get any of them to boot to desktop. Correction: It booted a few times but only directly from the install. Once powered down and turned back on without the live USB one sees Welcome to MX-23.1_ahs (Libretto!), after which the screen goes black and stays black. Must be turned off from power button.

Powering up with the MX-Live USB as boot device shows the Welcome screen and then a brief flash of light (actually an error message): ‘Failed to open EFI/BOOT: Invalid parameter. Failed to load image (??): Invalid parameter. Start image returned invalid parameter. Falling back to default loader’ This error message flashed so quickly I couldn't read it and didn't realize until I was writing this that it was a potential show-stopper. The screen then goes to desktop and a Live session and BTW looks great. So to the extent I thought about that little flash of light at all, I assumed the system had resolved some internal conflict that I didn't need to worry about.

Anyway, Dell diagnostics feature shows all hardware working. Dell states they have no objection to people installing non-MicroSoft operating systems on their hardware; I assume the motherboard is able to accept the install.

Command line update of installer returned “mx-installer is already the newest version (23.10.02mx23).”

At some point I noticed Boot Sequence shows the USB stick; MX Linux; and MX23. I don’t understand this bifurcation.

/var/log/minstall.log:

demo@mx1:/var/log
$ cat minstall.log
2024-01-06 14:21:24.820 DBG default: Installer version: 23.10.02mx23
2024-01-06 14:21:24.905 DBG default: << void MInstall::startup() >>
2024-01-06 14:21:24.905 DBG default: Detect EFI: 64
2024-01-06 14:21:24.905 DBG default: Exec #1: uname -m
2024-01-06 14:21:24.905 DBG default: uname -m
2024-01-06 14:21:24.979 DBG default: Exit #1: 0
2024-01-06 14:21:24.979 DBG default: Detect arch: "x86_64"
2024-01-06 14:21:24.979 DBG default: Live boot: BOOT_IMAGE=/antiX/vmlinuz quiet splasht nosplash
2024-01-06 14:21:25.001 DBG default: Check MD5: /live/boot-dev/antiX/initrd.gz
2024-01-06 14:21:25.493 DBG default: Check MD5: /live/boot-dev/antiX/linuxfs
2024-01-06 14:21:35.491 DBG default: << void MProcess::halt(bool) >>
2024-01-06 14:21:35.492 DBG default: -- Check halted –


results of command line lsblk:

demo@mx1:~
$ lsblk
NAME MAJ:MIN RM SIZE RO TYPE MOUNTPOINTS
loop0 7:0 0 2G 1 loop /live/linux
sda 8:0 0 465.8G 0 disk
├─sda1 8:1 0 512M 0 part
├─sda2 8:2 0 447.5G 0 part
└─sda3 8:3 0 8.1G 0 part [SWAP]
sdb 8:16 1 28.9G 0 disk
├─sdb1 8:17 1 28.9G 0 part /home/demo/Live-usb-storage
│ /root/Live-usb-storage
│ /live/boot-dev
└─sdb2 8:18 1 49M 0 part


results of command line efibootmgr -v:

demo@mx1:~
$ efibootmgr -v
BootCurrent: 0002
Timeout: 2 seconds
BootOrder: 0002,0000,0001
Boot0000* MX Linux HD(1,GPT,70e14769-d59d-4775-a0c2-88b416b7673a,0x800,0x100000)/File(\EFI\MX\grubx64.efi)
Boot0001* MX23 HD(1,GPT,70e14769-d59d-4775-a0c2-88b416b7673a,0x800,0x100000)/File(\EFI\MX23\grubx64.efi)
Boot0002* UEFI: PNY USB 2.0 FD PMAP, Partition 2 PciRoot(0x0)/Pci(0x14,0x0)/USB(3,0)/HD(2,MBR,0x1a4cc5ae,0x39b8800,0x18800)..BO
demo@mx1:~


Quick System Info here:

Code: Select all

 
 System:
  Kernel: 6.5.0-1mx-ahs-amd64 [6.5.3-1~mx23ahs] arch: x86_64 bits: 64 compiler: gcc v: 12.2.0
    parameters: BOOT_IMAGE=/antiX/vmlinuz quiet splasht nosplash
  Desktop: Xfce v: 4.18.1 tk: Gtk v: 3.24.36 info: xfce4-panel wm: xfwm v: 4.18.0 vt: 7
    dm: LightDM v: 1.26.0 Distro: MX-23.1_ahs_x64 Libretto October 15  2023 base: Debian GNU/Linux
    12 (bookworm)
Machine:
  Type: Laptop System: Dell product: Latitude 5500 v: N/A serial: <superuser required> Chassis:
    type: 10 serial: <superuser required>
  Mobo: Dell model: 0M14W7 v: A00 serial: <superuser required> UEFI: Dell v: 1.6.5
    date: 12/26/2019
Battery:
  ID-1: BAT0 charge: 45.7 Wh (97.4%) condition: 46.9/68.0 Wh (68.9%) volts: 8.4 min: 7.6
    model: BYD DELL 9JRYT9A type: Li-poly serial: <filter> status: charging
CPU:
  Info: model: Intel Core i5-8265U bits: 64 type: MT MCP arch: Comet/Whiskey Lake note: check
    gen: core 8 level: v3 note: check built: 2018 process: Intel 14nm family: 6 model-id: 0x8E (142)
    stepping: 0xC (12) microcode: 0xC6
  Topology: cpus: 1x cores: 4 tpc: 2 threads: 8 smt: enabled cache: L1: 256 KiB
    desc: d-4x32 KiB; i-4x32 KiB L2: 1024 KiB desc: 4x256 KiB L3: 6 MiB desc: 1x6 MiB
  Speed (MHz): avg: 509 high: 845 min/max: 400/3900 scaling: driver: intel_pstate
    governor: powersave cores: 1: 400 2: 845 3: 400 4: 400 5: 400 6: 400 7: 400 8: 830
    bogomips: 28800
  Flags: avx avx2 ht lm nx pae sse sse2 sse3 sse4_1 sse4_2 ssse3 vmx
  Vulnerabilities:
  Type: gather_data_sampling status: Vulnerable: No microcode
  Type: itlb_multihit status: KVM: VMX disabled
  Type: l1tf status: Not affected
  Type: mds status: Not affected
  Type: meltdown status: Not affected
  Type: mmio_stale_data status: Vulnerable: Clear CPU buffers attempted, no microcode; SMT
    vulnerable
  Type: retbleed mitigation: Enhanced IBRS
  Type: spec_rstack_overflow status: Not affected
  Type: spec_store_bypass mitigation: Speculative Store Bypass disabled via prctl
  Type: spectre_v1 mitigation: usercopy/swapgs barriers and __user pointer sanitization
  Type: spectre_v2 mitigation: Enhanced / Automatic IBRS, IBPB: conditional, RSB filling,
    PBRSB-eIBRS: SW sequence
  Type: srbds status: Vulnerable: No microcode
  Type: tsx_async_abort status: Not affected
Graphics:
  Device-1: Intel WhiskeyLake-U GT2 [UHD Graphics 620] vendor: Dell driver: i915 v: kernel
    arch: Gen-9.5 process: Intel 14nm built: 2016-20 ports: active: eDP-1
    empty: DP-1,HDMI-A-1,HDMI-A-2 bus-ID: 00:02.0 chip-ID: 8086:3ea0 class-ID: 0300
  Device-2: Realtek Integrated_Webcam_HD type: USB driver: uvcvideo bus-ID: 1-6:3
    chip-ID: 0bda:5539 class-ID: 0e02 serial: <filter>
  Display: x11 server: X.Org v: 1.21.1.7 compositor: xfwm v: 4.18.0 driver: X:
    loaded: modesetting unloaded: fbdev,vesa dri: iris gpu: i915 display-ID: :0.0 screens: 1
  Screen-1: 0 s-res: 1366x768 s-dpi: 96 s-size: 361x203mm (14.21x7.99") s-diag: 414mm (16.31")
  Monitor-1: eDP-1 model: BOE Display 0x086b built: 2019 res: 1366x768 hz: 60 dpi: 101 gamma: 1.2
    size: 344x194mm (13.54x7.64") diag: 395mm (15.5") ratio: 16:9 modes: 1366x768
  API: OpenGL v: 4.6 Mesa 23.1.2-1~mx23ahs renderer: Mesa Intel UHD Graphics 620 (WHL GT2)
    direct-render: Yes
Audio:
  Device-1: Intel Cannon Point-LP High Definition Audio vendor: Dell driver: snd_hda_intel
    v: kernel alternate: snd_soc_skl,snd_sof_pci_intel_cnl bus-ID: 00:1f.3 chip-ID: 8086:9dc8
    class-ID: 0403
  API: ALSA v: k6.5.0-1mx-ahs-amd64 status: kernel-api tools: alsamixer,amixer
  Server-1: PipeWire v: 0.3.65 status: active with: 1: pipewire-pulse status: active
    2: wireplumber status: active 3: pipewire-alsa type: plugin 4: pw-jack type: plugin
    tools: pactl,pw-cat,pw-cli,wpctl
Network:
  Device-1: Intel Cannon Point-LP CNVi [Wireless-AC] driver: iwlwifi v: kernel modules: wl
    bus-ID: 00:14.3 chip-ID: 8086:9df0 class-ID: 0280
  IF: wlan0 state: down mac: <filter>
  Device-2: Intel Ethernet I219-V vendor: Dell driver: e1000e v: kernel port: N/A bus-ID: 00:1f.6
    chip-ID: 8086:15be class-ID: 0200
  IF: eth0 state: down mac: <filter>
Bluetooth:
  Device-1: Intel Bluetooth 9460/9560 Jefferson Peak (JfP) type: USB driver: btusb v: 0.8
    bus-ID: 1-10:4 chip-ID: 8087:0aaa class-ID: e001
  Report: hciconfig ID: hci0 rfk-id: 3 state: up address: <filter> bt-v: 3.0 lmp-v: 5.1
    sub-v: 100 hci-v: 5.1 rev: 100
  Info: acl-mtu: 1021:4 sco-mtu: 96:6 link-policy: rswitch sniff link-mode: peripheral accept
    service-classes: rendering, capturing, object transfer, audio, telephony
Drives:
  Local Storage: total: 494.67 GiB used: 2.11 GiB (0.4%)
  SMART Message: Unable to run smartctl. Root privileges required.
  ID-1: /dev/sda maj-min: 8:0 vendor: Samsung model: SSD 870 EVO 500GB size: 465.76 GiB
    block-size: physical: 512 B logical: 512 B speed: 6.0 Gb/s type: SSD serial: <filter> rev: 2B6Q
    scheme: GPT
  ID-2: /dev/sdb maj-min: 8:16 type: USB vendor: PNY model: USB 2.0 FD size: 28.91 GiB
    block-size: physical: 512 B logical: 512 B type: N/A serial: <filter> rev: PMAP scheme: MBR
  SMART Message: Unknown USB bridge. Flash drive/Unsupported enclosure?
Partition:
  Message: No partition data found.
Swap:
  Kernel: swappiness: 15 (default 60) cache-pressure: 100 (default)
  ID-1: swap-1 type: partition size: 8.11 GiB used: 0 KiB (0.0%) priority: -2 dev: /dev/sda3
    maj-min: 8:3
Sensors:
  System Temperatures: cpu: 44.0 C pch: 41.0 C mobo: 37.0 C
  Fan Speeds (RPM): cpu: 0
Repos:
  Packages: pm: dpkg pkgs: 2054 libs: 1041 tools: apt,apt-get,aptitude,nala,synaptic pm: rpm
    pkgs: 0 pm: flatpak pkgs: 0
  No active apt repos in: /etc/apt/sources.list
  Active apt repos in: /etc/apt/sources.list.d/debian-stable-updates.list
    1: deb http://deb.debian.org/debian bookworm-updates main contrib non-free non-free-firmware
  Active apt repos in: /etc/apt/sources.list.d/debian.list
    1: deb http://deb.debian.org/debian bookworm main contrib non-free non-free-firmware
    2: deb http://security.debian.org/debian-security bookworm-security main contrib non-free non-free-firmware
  Active apt repos in: /etc/apt/sources.list.d/mx.list
    1: deb http://mxrepo.com/mx/repo/ bookworm main non-free
    2: deb http://mxrepo.com/mx/repo/ bookworm ahs
Info:
  Processes: 271 Uptime: 1m wakeups: 8092 Memory: 7.6 GiB used: 1.14 GiB (15.0%) Init: SysVinit
  v: 3.06 runlevel: 5 default: graphical tool: systemctl Compilers: gcc: 12 Client: shell wrapper
  v: 5.2.15-release inxi: 3.3.26
Boot Mode: UEFI

Steps listed below are an amalgam of past attempts with emphasis on latest install:

Downloaded new Gparted 1.5.0-6-amd64.iso, checksum and signature good. Created live USB.

Pursuant to MX’s 64-bit UEFI instructions for overwriting MS Windows in order to create an all-Linux environment, I booted Gparted-live USB into target laptop, and created new system table formatted as GPT. Then created:
- new primary EFI system partition formatted as fat32
- new primary /home partition formatted as ext4;
- new primary swap partition formatted as SWAP
Clicked apply. When process completed successfully, set flags “boot” and “esp” on the EFI partition.


Formatted different USB stick as fat32 for Live MX iso.
- Downloaded MX-23.1_ahs_x64.iso onto the older Dell (not the target computer). Hashes good. Signature good.
- Used MX Live USB Maker to create the live USB. When complete, command line querry md5sum -c *.md5 in directory /media/MyUserName/MX-Live-usb/antiX returned ok, ok, ok.

Used that Live MX USB to boot into target laptop and went to System Set-up (they call it BIOS but it is too complex to be “basic” anything)
- Secure Boot: Turned it off
- Secure Boot Mode: was on “Deployed Mode,” changed it to “Audit Mode.”
- System configuration > Integrated NIC: “Enable UEFI Network Stack” is checked. “enabled w/PXE” was also checked, changed that one to plain “enabled”
- System configuration > Smart Reporting was disabled by default. Left disabled.
- System configuration > USB Configuration. Both “Enable USB Boot Support” and “Enable External USB Port” are checked.
- Fastboot cannot be turned off; set to “thorough”
- SATA Operation: Defaulted to RAID, changed to AHCI.
- Boot sequence: set it to boot from the Live MX-23.1 AHS USB.


All features worked in Live session so I installed. In fact, everything worked so well that I totally forgot the second-long blip of light on initialization warning of a boot error. I had no idea what it said (para. 4 above). After the most recent install failed I attempted to lengthen this warning’s time on screen using System Setup and/or timeout in gui Boot Options. It did not lengthen, prntscrn doesn’t work on boot and my phone’s camera is not good. So I did a number of restarts in order to write the error message down. [Would MX developers be able to make this error message stay on the screen longer? Thnx.] Returning to installation, I tried both “regular” and “custom.”

Current installation is custom install. I did not know which partition to make “active” on the “Choose Partitions” screen of the custom install. Which partition should be active on a UEFI system? The EFI (boot) partition or root? I tried it both ways. No go. EFI partition marked as active on this install.

On LIVE session I:

(1) ran NVIDIA Driver Installer, but it found no NVIDIA card and exited.

(2) used Synaptic to download and install 199 updates onto the Live-usb that I understand has persistence. My understanding is the updates would have incorporated. I am sure but not positive I did this prior to performing the current install.

(3) looked at Gparted and the flags on EFI partition had changed to include “legacy boot.” I changed it back to original selection, “boot” and “esp.”

(4) tried MX Boot Repair. Still not booting.

(5) tried rEFInd. Used Synaptic to download and install rEFInd, still no boot and the added software seemed a further complication. I deleted it from the boot sequence menu. Now rEFInd doesn’t come up in Synaptic when I search for it again. Sigh.

I give up. I fully expect to face-palm while grunting, “Doh!” What did I miss?

Re: UEFI Install boots to black screen

Posted: Sun Jan 07, 2024 6:05 pm
by fehlix
Suggest, to re-boot LiveUSB and install latest mx-installer on the live booted system.
And do select "auto install entire disk" instead of custom.
This may help avoiding any mistakes related to partitions etc.
+++EDIT+++
Or, maybe do a full-upgrade of the LiveBooted USB before auto-install entire disk.

Re: UEFI Install boots to black screen

Posted: Mon Jan 08, 2024 5:34 pm
by evenkeel
@fehlix, thank you for your answer. I really appreciate it. I downloaded and installed updates and then did a regular install as you suggested. Yet laptop still not booting from disk. Going back to Live session gparted shows a simplified file system, the bifurcation is gone. That's an improvement. When I watched the update details I saw "possible missing firmware module i915," or something. It goes extremely fast. This may represent another research project for me. But if you could take a look, here is the new and improved inxi, etc.

Thank you.

I looked but this time did not find a /var/log/minstall.log.

demo@mx1:~
$ 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
demo@mx1:~

demo@mx1:~
$ lsblk
NAME MAJ:MIN RM SIZE RO TYPE MOUNTPOINTS
loop0 7:0 0 2G 1 loop /live/linux
sda 8:0 0 465.8G 0 disk
├─sda1 8:1 0 256M 0 part
└─sda2 8:2 0 465.5G 0 part
sdb 8:16 1 28.9G 0 disk
├─sdb1 8:17 1 28.9G 0 part /home/demo/Live-usb-storage
│ /root/Live-usb-storage
│ /live/boot-dev
└─sdb2 8:18 1 49M 0 part

Code: Select all

System:
  Kernel: 6.5.0-1mx-ahs-amd64 [6.5.3-1~mx23ahs] arch: x86_64 bits: 64 compiler: gcc v: 12.2.0
    parameters: BOOT_IMAGE=/antiX/vmlinuz quiet splasht nosplash
  Desktop: Xfce v: 4.18.1 tk: Gtk v: 3.24.36 info: xfce4-panel wm: xfwm v: 4.18.0 vt: 7
    dm: LightDM v: 1.26.0 Distro: MX-23.1_ahs_x64 Libretto October 15  2023 base: Debian GNU/Linux
    12 (bookworm)
Machine:
  Type: Laptop System: Dell product: Latitude 5500 v: N/A serial: <superuser required> Chassis:
    type: 10 serial: <superuser required>
  Mobo: Dell model: 0M14W7 v: A00 serial: <superuser required> UEFI: Dell v: 1.6.5
    date: 12/26/2019
Battery:
  ID-1: BAT0 charge: 46.9 Wh (100.0%) condition: 46.9/68.0 Wh (68.9%) volts: 8.3 min: 7.6
    model: BYD DELL 9JRYT9A type: Li-poly serial: <filter> status: full
CPU:
  Info: model: Intel Core i5-8265U bits: 64 type: MT MCP arch: Comet/Whiskey Lake note: check
    gen: core 8 level: v3 note: check built: 2018 process: Intel 14nm family: 6 model-id: 0x8E (142)
    stepping: 0xC (12) microcode: 0xC6
  Topology: cpus: 1x cores: 4 tpc: 2 threads: 8 smt: enabled cache: L1: 256 KiB
    desc: d-4x32 KiB; i-4x32 KiB L2: 1024 KiB desc: 4x256 KiB L3: 6 MiB desc: 1x6 MiB
  Speed (MHz): avg: 525 high: 900 min/max: 400/3900 scaling: driver: intel_pstate
    governor: powersave cores: 1: 400 2: 400 3: 900 4: 400 5: 400 6: 400 7: 400 8: 900
    bogomips: 28800
  Flags: avx avx2 ht lm nx pae sse sse2 sse3 sse4_1 sse4_2 ssse3 vmx
  Vulnerabilities:
  Type: gather_data_sampling status: Vulnerable: No microcode
  Type: itlb_multihit status: KVM: VMX disabled
  Type: l1tf status: Not affected
  Type: mds status: Not affected
  Type: meltdown status: Not affected
  Type: mmio_stale_data status: Vulnerable: Clear CPU buffers attempted, no microcode; SMT
    vulnerable
  Type: retbleed mitigation: Enhanced IBRS
  Type: spec_rstack_overflow status: Not affected
  Type: spec_store_bypass mitigation: Speculative Store Bypass disabled via prctl
  Type: spectre_v1 mitigation: usercopy/swapgs barriers and __user pointer sanitization
  Type: spectre_v2 mitigation: Enhanced / Automatic IBRS, IBPB: conditional, RSB filling,
    PBRSB-eIBRS: SW sequence
  Type: srbds status: Vulnerable: No microcode
  Type: tsx_async_abort status: Not affected
Graphics:
  Device-1: Intel WhiskeyLake-U GT2 [UHD Graphics 620] vendor: Dell driver: i915 v: kernel
    arch: Gen-9.5 process: Intel 14nm built: 2016-20 ports: active: eDP-1
    empty: DP-1,HDMI-A-1,HDMI-A-2 bus-ID: 00:02.0 chip-ID: 8086:3ea0 class-ID: 0300
  Device-2: Realtek Integrated_Webcam_HD type: USB driver: uvcvideo bus-ID: 1-6:3
    chip-ID: 0bda:5539 class-ID: 0e02 serial: <filter>
  Display: x11 server: X.Org v: 1.21.1.7 compositor: xfwm v: 4.18.0 driver: X:
    loaded: modesetting unloaded: fbdev,vesa dri: iris gpu: i915 display-ID: :0.0 screens: 1
  Screen-1: 0 s-res: 1366x768 s-dpi: 96 s-size: 361x203mm (14.21x7.99") s-diag: 414mm (16.31")
  Monitor-1: eDP-1 model: BOE Display 0x086b built: 2019 res: 1366x768 hz: 60 dpi: 101 gamma: 1.2
    size: 344x194mm (13.54x7.64") diag: 395mm (15.5") ratio: 16:9 modes: 1366x768
  API: OpenGL v: 4.6 Mesa 23.1.2-1~mx23ahs renderer: Mesa Intel UHD Graphics 620 (WHL GT2)
    direct-render: Yes
Audio:
  Device-1: Intel Cannon Point-LP High Definition Audio vendor: Dell driver: snd_hda_intel
    v: kernel alternate: snd_soc_skl,snd_sof_pci_intel_cnl bus-ID: 00:1f.3 chip-ID: 8086:9dc8
    class-ID: 0403
  API: ALSA v: k6.5.0-1mx-ahs-amd64 status: kernel-api tools: alsamixer,amixer
  Server-1: PipeWire v: 0.3.65 status: active with: 1: pipewire-pulse status: active
    2: wireplumber status: active 3: pipewire-alsa type: plugin 4: pw-jack type: plugin
    tools: pactl,pw-cat,pw-cli,wpctl
Network:
  Device-1: Intel Cannon Point-LP CNVi [Wireless-AC] driver: iwlwifi v: kernel modules: wl
    bus-ID: 00:14.3 chip-ID: 8086:9df0 class-ID: 0280
  IF: wlan0 state: down mac: <filter>
  Device-2: Intel Ethernet I219-V vendor: Dell driver: e1000e v: kernel port: N/A bus-ID: 00:1f.6
    chip-ID: 8086:15be class-ID: 0200
  IF: eth0 state: down mac: <filter>
Bluetooth:
  Device-1: Intel Bluetooth 9460/9560 Jefferson Peak (JfP) type: USB driver: btusb v: 0.8
    bus-ID: 1-10:4 chip-ID: 8087:0aaa class-ID: e001
  Report: hciconfig ID: hci0 rfk-id: 3 state: up address: <filter> bt-v: 3.0 lmp-v: 5.1
    sub-v: 100 hci-v: 5.1 rev: 100
  Info: acl-mtu: 1021:4 sco-mtu: 96:6 link-policy: rswitch sniff link-mode: peripheral accept
    service-classes: rendering, capturing, object transfer, audio, telephony
Drives:
  Local Storage: total: 494.67 GiB used: 2.11 GiB (0.4%)
  SMART Message: Unable to run smartctl. Root privileges required.
  ID-1: /dev/sda maj-min: 8:0 vendor: Samsung model: SSD 870 EVO 500GB size: 465.76 GiB
    block-size: physical: 512 B logical: 512 B speed: 6.0 Gb/s type: SSD serial: <filter> rev: 2B6Q
    scheme: GPT
  ID-2: /dev/sdb maj-min: 8:16 type: USB vendor: PNY model: USB 2.0 FD size: 28.91 GiB
    block-size: physical: 512 B logical: 512 B type: N/A serial: <filter> rev: PMAP scheme: MBR
  SMART Message: Unknown USB bridge. Flash drive/Unsupported enclosure?
Partition:
  Message: No partition data found.
Swap:
  Alert: No swap data was found.
Sensors:
  System Temperatures: cpu: 48.0 C pch: 43.0 C mobo: 36.0 C
  Fan Speeds (RPM): cpu: 0
Repos:
  Packages: pm: dpkg pkgs: 2054 libs: 1041 tools: apt,apt-get,aptitude,nala,synaptic pm: rpm
    pkgs: 0 pm: flatpak pkgs: 0
  No active apt repos in: /etc/apt/sources.list
  Active apt repos in: /etc/apt/sources.list.d/debian-stable-updates.list
    1: deb http://deb.debian.org/debian bookworm-updates main contrib non-free non-free-firmware
  Active apt repos in: /etc/apt/sources.list.d/debian.list
    1: deb http://deb.debian.org/debian bookworm main contrib non-free non-free-firmware
    2: deb http://security.debian.org/debian-security bookworm-security main contrib non-free non-free-firmware
  Active apt repos in: /etc/apt/sources.list.d/mx.list
    1: deb http://mxrepo.com/mx/repo/ bookworm main non-free
    2: deb http://mxrepo.com/mx/repo/ bookworm ahs
Info:
  Processes: 260 Uptime: 0m wakeups: 1812 Memory: 7.6 GiB used: 1.09 GiB (14.4%) Init: SysVinit
  v: 3.06 runlevel: 5 default: graphical tool: systemctl Compilers: gcc: 12 Client: shell wrapper
  v: 5.2.15-release inxi: 3.3.26
Boot Mode: UEFI

Re: UEFI Install boots to black screen

Posted: Mon Jan 08, 2024 5:46 pm
by Charlie Brown
evenkeel wrote: Sun Jan 07, 2024 5:18 pm On LIVE session I:

(1) ran NVIDIA Driver Installer, ...
But... why?

Graphics:
Device-1: Intel WhiskeyLake-U GT2 [UHD Graphics 620] vendor: Dell driver: i915 v: kernel
arch: Gen-9.5 process: Intel 14nm built: 2016-20 ports: active: eDP-1
empty: DP-1,HDMI-A-1,HDMI-A-2 bus-ID: 00:02.0 chip-ID: 8086:3ea0 class-ID: 0300
Device-2: Realtek Integrated_Webcam
...

Re: UEFI Install boots to black screen

Posted: Mon Jan 08, 2024 6:02 pm
by m_pav
Yeah, that Device-2 is a totally weird one, but not completely unexpected when working with Dell, who do some real funky things with their machines :rolleyes:

I wonder if the I915 driver is over-driving your HD 1366*768 display?

What happens if you boot with TV or 2nd monitor connected via the DP or HDMI port? If you get a desktop on the 2nd monitor you may be able to use the Display app to get the internal display working, set it as the primary, disconnect the secondary and reboot.

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

One more thing that may help is to install a Liquorix kernel, we have found these can tidy up some random hardware related quirks.

Re: UEFI Install boots to black screen

Posted: Mon Jan 08, 2024 6:02 pm
by fehlix
evenkeel wrote: Mon Jan 08, 2024 5:34 pm @fehlix, thank you for your answer. I really appreciate it. I downloaded and installed updates and then did a regular install as you suggested. Yet laptop still not booting from disk. Going back to Live session gparted shows a simplified file system, the bifurcation is gone. That's an improvement. When I watched the update details I saw "possible missing firmware module i915," or something. It goes extremely fast. This may represent another research project for me. But if you could take a look, here is the new and improved inxi, etc.

Thank you.

I looked but this time did not find a /var/log/minstall.log.
OK, first things first: Please do post text output e.g from commands wrapped between those [code]code-brackets[/code], for better readability, as otherwise I have difficulty to read those ( and may loos interest to read further).
Those code-tags you see when posting QSI.
So, please provide the following command outputs when running from LiveUSB:
again (code-tag wrapped)

Code: Select all

efibootmgr -v

and

Code: Select all

lsblk -f -o +PARTUUID
Next steps to do, might follow after having read the newly provided info.
Thanks.

Re: UEFI Install boots to black screen

Posted: Mon Jan 08, 2024 8:52 pm
by evenkeel
@fehlix Okay, thanks. Here goes:

Code: Select all

demo@mx1:~
$ 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
demo@mx1:~

Code: Select all

demo@mx1:~
$ lsblk -f -o +PARTUUID
NAME FSTYPE FSVER LABEL UUID                                 FSAVAIL FSUSE% MOUNTPOINTS PARTUUID
loop0
     squash 4.0                                                    0   100% /live/linux 
sda                                                                                     
├─sda1
│    vfat   FAT32 EFI-SYSTEM
│                       4B58-B98D                                                       4ceacac5-4e7e-49c9-8b4d-2f087149e243
└─sda2
     ext4   1.0   rootMX23
                        45e34414-3424-4dba-b4bf-99b6aad560c3                            1ae547c5-1f64-4b93-9a71-8d40d85e6ffa
sdb                                                                                     
├─sdb1
│    ext4   1.0   MX-Live-usb
│                       2d1f2caa-4e44-4a21-8c25-3282c90a2f0b   26.2G     7% /home/demo/Live-usb-storage
│                                                                                       1a4cc5ae-01
│                                                                           /root/Live-usb-storage 
│                                                                           /live/boot- 
│                                                                           dev         
└─sdb2
     vfat   FAT32 MX-UEFI
                        1830-E41C                                                       1a4cc5ae-02
demo@mx1:~
$


@Charlie Brown Thank you. Good point. I think I'd read somewhere on MX's forum that Nvidia drivers could be a cause of black screen. But as you point out, that doesn't apply to this laptop. Yet I see "i915" in those graphic specs, which I only notice now because you made it conspicuous. Very cool.

@m_pav And thanks to you too. Your observations help me get still clearer that this is likely a graphics issue. I will try to plug a monitor into this tomorrow and see what happens.

Re: UEFI Install boots to black screen

Posted: Mon Jan 08, 2024 9:15 pm
by fehlix
OK, thanks.
As it booted to the LiveUSB, without issue we may try something unususal.
First figure out whether it's firmware related:
On the "MX Linux Welcom" GRUB screen, could you add a boot parameter
to disable loading microcode:

Press "E"-key on the keyboard "the e for edit".

Navigate with arrow key to the line starting with "linux"

Now press arrow down folowed by arrow left,
to go the end of the linux-line.

Press spacebar and type

Code: Select all

dis_ucode_ldr

Now boot with F10 or Ctrl+x
We would now boot without micro-code, the way the live-system boots.

If not we may try another methode, to install a newer kernel,
e.g this way:
Try to add instaetd of disabling micro code, to add nomodeset boot parameter.

Code: Select all

nomodeset
You would get a a not so good graphics, but may good enough
to install e.g. liquorix kernels to try.

Another trial would be to disable grub's tpm module,
may be if both method above won't work ... later

Re: UEFI Install boots to black screen

Posted: Mon Jan 08, 2024 11:40 pm
by siamhie
evenkeel wrote: Mon Jan 08, 2024 8:52 pm @fehlix Okay, thanks. Here goes:

Code: Select all

demo@mx1:~
$ 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
demo@mx1:~

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


Here's what mine looks like.

Code: Select all

efibootmgr -v
BootCurrent: 0005
Timeout: 1 seconds
BootOrder: 0005,0006
Boot0005* MX Linux	HD(1,GPT,917d581a-0070-477e-8aea-3c3a30ddf25f,0x800,0x40000)/File(\EFI\MX\GRUBX64.EFI)
Boot0006* UEFI OS	HD(1,GPT,917d581a-0070-477e-8aea-3c3a30ddf25f,0x800,0x40000)/File(\EFI\BOOT\BOOTX64.EFI)..BO

Re: UEFI Install boots to black screen

Posted: Tue Jan 09, 2024 9:06 am
by Charlie Brown
siamhie wrote: Mon Jan 08, 2024 11:40 pm...

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.

Re: UEFI Install boots to black screen

Posted: Tue Jan 09, 2024 9:09 am
by Charlie Brown
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...
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 ...

Re: UEFI Install boots to black screen

Posted: Tue Jan 09, 2024 9:36 am
by 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.

Re: UEFI Install boots to black screen

Posted: Tue Jan 09, 2024 9:51 am
by fehlix
j2mcgreg wrote: Tue Jan 09, 2024 9:36 am 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.

Re: UEFI Install boots to black screen

Posted: Tue Jan 09, 2024 11:01 am
by siamhie
Charlie Brown wrote: Tue Jan 09, 2024 9:06 am
siamhie wrote: Mon Jan 08, 2024 11:40 pm...

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

Re: UEFI Install boots to black screen

Posted: Tue Jan 09, 2024 11:20 am
by 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)

Re: UEFI Install boots to black screen

Posted: Tue Jan 09, 2024 6:42 pm
by 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.

Re: UEFI Install boots to black screen

Posted: Tue Jan 09, 2024 6:51 pm
by fehlix
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.
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.

Re: UEFI Install boots to black screen

Posted: Tue Jan 09, 2024 9:26 pm
by 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.

Re: UEFI Install boots to black screen  [Solved]

Posted: Wed Jan 10, 2024 8:35 am
by fehlix
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.
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.
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.
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.

Re: UEFI Install boots to black screen

Posted: Wed Jan 10, 2024 8:57 pm
by 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.

Re: UEFI Install boots to black screen

Posted: Wed Jan 10, 2024 9:09 pm
by fehlix
evenkeel wrote: Wed Jan 10, 2024 8:57 pm @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.
* I'd remove dis_ucode_ld from boot options, and keep it in mind to use manually if needed.
* Generally "Warnings" can be read as for "Info" not relevant for "normal" user.
* Liquorix get regularly upgrades by this meta-package you have mentioned, the one you may have installed,
and would automatically trigger newer package for the liquorix kernel to get installed, and older one would be removed, so you would always have latest and one older. the newer kernel will be at the top of the GRUB menu.

Re: UEFI Install boots to black screen

Posted: Thu Jan 11, 2024 7:45 pm
by evenkeel
@fehlix I can't believe I just blew out a third posting. (Where is the Arghhhh symbol?) Oh well, I'll learn. But I now have a functional 100% MX Linux operating system, just as I hoped. Thank you for your time, skill and help. I have marked this Solved. Thank you also to all who joined in. You sparked ideas for me. Best!

Re: UEFI Install boots to black screen

Posted: Thu Jan 11, 2024 9:32 pm
by siamhie
evenkeel wrote: Thu Jan 11, 2024 7:45 pm Where is the Arghhhh symbol?
:frustrated:

When quoting someone's post you should see the smilies on the right side. :singing:

Re: UEFI Install boots to black screen

Posted: Fri Jan 12, 2024 7:47 pm
by evenkeel
That's the symbol all right. Hope not to overuse it, but now I know. Thanks @siamhie.

Re: UEFI Install boots to black screen

Posted: Wed Jan 17, 2024 4:38 pm
by evenkeel
CORRECTION FYI--no response requested: Folks, @fehlix, @Charlie Brown, @m_pav, @siamhie, @j2mcgreg, I was incorrect to write that my Latitude 5500 now works both with and without the dis_ucode_ldr parameter. I'd failed to delete the parameter from MX Boot Options. Once I saw that, I took the dis_ucode_ldr out of MX Boot Options, hit Apply, let the app update Grub, then shut down normally. Booted up again and at the Welcome screen pressed "e" to make sure that parameter was gone. It was gone. Ctrl + X. Black screen. Hard shutdown. Repeated several times--black screen each time. Hard shutdowns. 'k. So this laptop currently needs the dis_ucode_ldr boot parameter. I typed it in again at both places. I'm back to the desktop and a beautiful OS. I hope this info helps. If I learn anything else I'll start a new thread.
All times are UTC-04:00
Page 1 of 1

Powered by phpBB® Forum Software © phpBB Limited