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?
