Mx-23.2 boot failure

[james]

Charlie Brown: I am not sure what you mean by check Mx Boot Options. Is that an app? Is that something that I get into during boot? I think I saw something like that while booting with the Live USB Snapshot, but I do not recall being able to set any parameters when booting without it. Anyway, I definitely do not want to have to get into Mx by typing "startx" and dealing with unlocking Keyrings, so I definitely want to do the nomodeset and remove the failsafe. Yeah, that's what happens when you give me an inch. Anyway, as requested, here is the latest QSI:

Code: Select all

Snapshot created on: 20240310_1128
System:
  Kernel: 6.7.8-1-liquorix-amd64 [6.7-12~mx23ahs] arch: x86_64 bits: 64 compiler: gcc v: 12.2.0 parameters: audit=0
    intel_pstate=disable rcupdate.rcu_expedited=1 BOOT_IMAGE=/boot/vmlinuz-6.7.8-1-liquorix-amd64
    root=UUID=<filter> ro quiet
  Desktop: Xfce v: 4.18.1 tk: Gtk v: 3.24.36 info: xfce4-panel wm: xfwm v: 4.18.0 vt: 1
    dm: LightDM v: 1.26.0 Distro: MX-23.2_ahs_x64 Libretto January 21  2024 base: Debian GNU/Linux
    12 (bookworm)
Machine:
  Type: Desktop System: Gigabyte product: Z690 AERO G DDR4 v: -CF serial: <superuser required>
  Mobo: Gigabyte model: Z690 AERO G DDR4 v: x.x serial: <superuser required> UEFI: American
    Megatrends LLC. v: F8a date: 03/28/2022
Battery:
  Device-1: hidpp_battery_0 model: Logitech Wireless Keyboard K330 serial: <filter> charge: 100%
    (should be ignored) rechargeable: yes status: discharging
  Device-2: hidpp_battery_1 model: Logitech Wireless Mouse M215 2nd Gen serial: <filter>
    charge: 100% (should be ignored) rechargeable: yes status: discharging
CPU:
  Info: model: 12th Gen Intel Core i9-12900K bits: 64 type: MST AMCP arch: Alder Lake gen: core 12
    level: v3 note: check built: 2021+ process: Intel 7 (10nm ESF) family: 6 model-id: 0x97 (151)
    stepping: 2 microcode: 0x32
  Topology: cpus: 1x cores: 16 mt: 8 tpc: 2 st: 8 threads: 24 smt: enabled cache: L1: 1.4 MiB
    desc: d-8x32 KiB, 8x48 KiB; i-8x32 KiB, 8x64 KiB L2: 14 MiB desc: 8x1.2 MiB, 2x2 MiB L3: 30 MiB
    desc: 1x30 MiB
  Speed (MHz): avg: 836 high: 1000 min/max: 800/3201 boost: enabled scaling: driver: acpi-cpufreq
    governor: ondemand cores: 1: 800 2: 800 3: 1000 4: 800 5: 983 6: 800 7: 1000 8: 800 9: 800
    10: 800 11: 800 12: 800 13: 902 14: 800 15: 800 16: 1000 17: 800 18: 800 19: 800 20: 800
    21: 800 22: 800 23: 800 24: 800 bogomips: 152985
  Flags: avx avx2 ht lm nx pae sse sse2 sse3 sse4_1 sse4_2 ssse3 vmx
  Vulnerabilities:
  Type: gather_data_sampling status: Not affected
  Type: itlb_multihit status: Not affected
  Type: l1tf status: Not affected
  Type: mds status: Not affected
  Type: meltdown status: Not affected
  Type: mmio_stale_data status: Not affected
  Type: retbleed status: Not affected
  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: Not affected
  Type: tsx_async_abort status: Not affected
Graphics:
  Device-1: Intel AlderLake-S GT1 vendor: Gigabyte driver: N/A alternate: i915 bus-ID: 00:02.0
    chip-ID: 8086:4680 class-ID: 0300
  Device-2: NVIDIA GA104 [GeForce RTX 3070 Ti] vendor: eVga.com. driver: nvidia v: 525.147.05
    non-free: 530.xx+ status: current (as of 2023-03) arch: Ampere code: GAxxx process: TSMC n7 (7nm)
    built: 2020-22 pcie: gen: 1 speed: 2.5 GT/s lanes: 16 link-max: gen: 4 speed: 16 GT/s
    bus-ID: 01:00.0 chip-ID: 10de:2482 class-ID: 0300
  Display: server: X.Org v: 1.21.1.7 compositor: xfwm v: 4.18.0 driver: X: loaded: nvidia
    unloaded: fbdev,modesetting,nouveau,vesa alternate: nv gpu: nvidia display-ID: :0 screens: 1
  Screen-1: 0 s-res: 1920x1080 s-dpi: 96 s-size: 508x286mm (20.00x11.26") s-diag: 583mm (22.95")
  Monitor-1: HDMI-0 res: 1920x1080 hz: 60 dpi: 82 size: 598x336mm (23.54x13.23")
    diag: 686mm (27.01") modes: N/A
  API: OpenGL v: 4.6.0 NVIDIA 525.147.05 renderer: NVIDIA GeForce RTX 3070 Ti/PCIe/SSE2
    direct-render: Yes
Audio:
  Device-1: Intel Alder Lake-S HD Audio vendor: Gigabyte driver: N/A
    alternate: snd_hda_intel, snd_sof_pci_intel_tgl bus-ID: 1-11:4 chip-ID: 0414:a012 bus-ID: 00:1f.3
    class-ID: 0300 chip-ID: 8086:7ad0 class-ID: 0403
  Device-2: NVIDIA GA104 High Definition Audio vendor: eVga.com. driver: snd_hda_intel v: kernel
    pcie: gen: 4 speed: 16 GT/s lanes: 16 bus-ID: 01:00.1 chip-ID: 10de:228b class-ID: 0403
  Device-3: Giga-Byte USB Audio type: USB driver: hid-generic,snd-usb-audio,usbhid
  API: ALSA v: k6.7.8-1-liquorix-amd64 status: kernel-api tools: alsamixer,amixer
  Server-1: PipeWire v: 1.0.0 status: off with: 1: pipewire-pulse status: off 2: wireplumber
    status: off 3: pw-jack type: plugin tools: pw-cat,pw-cli,wpctl
  Server-2: PulseAudio v: 16.1 status: active tools: pacat,pactl,pavucontrol
Network:
  Device-1: Intel Alder Lake-S PCH CNVi WiFi driver: iwlwifi v: kernel modules: wl bus-ID: 00:14.3
    chip-ID: 8086:7af0 class-ID: 0280
  IF: wlan0 state: down mac: <filter>
  Device-2: Intel Ethernet I225-V vendor: Gigabyte driver: igc v: kernel pcie: gen: 2
    speed: 5 GT/s lanes: 1 port: N/A bus-ID: 05:00.0 chip-ID: 8086:15f3 class-ID: 0200
  IF: eth1 state: down mac: <filter>
  Device-3: Realtek RTL8111/8168/8411 PCI Express Gigabit Ethernet driver: r8169 v: kernel pcie:
    gen: 1 speed: 2.5 GT/s lanes: 1 port: 3000 bus-ID: 06:00.0 chip-ID: 10ec:8161 class-ID: 0200
  IF: eth0 state: up speed: 100 Mbps duplex: full mac: <filter>
Bluetooth:
  Device-1: Intel AX201 Bluetooth type: USB driver: btusb v: 0.8 bus-ID: 1-14:8 chip-ID: 8087:0026
    class-ID: e001
  Report: hciconfig ID: hci0 rfk-id: 1 state: up address: <filter> bt-v: 3.0 lmp-v: 5.2
    sub-v: 3462 hci-v: 5.2 rev: 3462
  Info: acl-mtu: 1021:4 sco-mtu: 96:6 link-policy: rswitch sniff link-mode: peripheral accept
Drives:
  Local Storage: total: 2.61 TiB used: 705.45 GiB (26.4%)
  SMART Message: Unable to run smartctl. Root privileges required.
  ID-1: /dev/nvme0n1 maj-min: 259:2 vendor: Western Digital model: WDS500G1X0E-00AFY0
    size: 465.76 GiB block-size: physical: 512 B logical: 512 B speed: 63.2 Gb/s lanes: 4 type: SSD
    serial: <filter> rev: 614600WD temp: 38.9 C scheme: GPT
  ID-2: /dev/nvme1n1 maj-min: 259:0 vendor: Western Digital model: WDS100T1X0E-00AFY0
    size: 931.51 GiB block-size: physical: 512 B logical: 512 B speed: 63.2 Gb/s lanes: 4 type: SSD
    serial: <filter> rev: 614600WD temp: 38.9 C scheme: GPT
  ID-3: /dev/nvme2n1 maj-min: 259:1 vendor: Western Digital model: WDS100T1X0E-00AFY0
    size: 931.51 GiB block-size: physical: 512 B logical: 512 B speed: 63.2 Gb/s lanes: 4 type: SSD
    serial: <filter> rev: 614600WD temp: 38.9 C scheme: GPT
  ID-4: /dev/sda maj-min: 8:0 type: USB vendor: SanDisk model: USB 3.2Gen1 size: 114.6 GiB
    block-size: physical: 512 B logical: 512 B type: N/A serial: <filter> rev: 1.00 scheme: MBR
  SMART Message: Unknown USB bridge. Flash drive/Unsupported enclosure?
  ID-5: /dev/sdb maj-min: 8:16 type: USB model: General USB Flash Disk size: 231.85 GiB
    block-size: physical: 512 B logical: 512 B type: SSD serial: <filter> rev: 1100 scheme: MBR
  SMART Message: Unknown USB bridge. Flash drive/Unsupported enclosure?
Partition:
  ID-1: / raw-size: 931.26 GiB size: 915.57 GiB (98.31%) used: 98.11 GiB (10.7%) fs: ext4
    dev: /dev/nvme2n1p2 maj-min: 259:5
  ID-2: /boot/efi raw-size: 256 MiB size: 252 MiB (98.46%) used: 547 KiB (0.2%) fs: vfat
    dev: /dev/nvme2n1p1 maj-min: 259:4
Swap:
  Kernel: swappiness: 15 (default 60) cache-pressure: 100 (default)
  ID-1: swap-1 type: file size: 8 GiB used: 0 KiB (0.0%) priority: -2 file: /swap/swap
Sensors:
  System Temperatures: cpu: 24.0 C mobo: N/A gpu: nvidia temp: 32 C
  Fan Speeds (RPM): N/A gpu: nvidia fan: 0%
Repos:
  Packages: pm: dpkg pkgs: 2700 libs: 1449 tools: apt,apt-get,aptitude,nala,synaptic pm: rpm
    pkgs: 0
  No active apt repos in: /etc/apt/sources.list
  Active apt repos in: /etc/apt/sources.list.d/brave-browser-release.list
    1: deb [arch=amd64] https://brave-browser-apt-release.s3.brave.com/ stable main
  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 https://mxrepo.com/mx/repo/ bookworm main non-free
    2: deb https://mxrepo.com/mx/repo/ bookworm ahs
  Active apt repos in: /etc/apt/sources.list.d/protonvpn-stable.list
    1: deb [arch="all", signed-by=/usr/share/keyrings/protonvpn-stable-archive-keyring.gpg] https://repo.protonvpn.com/debian stable main
  Active apt repos in: /etc/apt/sources.list.d/vivaldi.list
    1: deb [arch=amd64] https://repo.vivaldi.com/stable/deb/ stable main
Info:
  Processes: 493 Uptime: 1h 50m wakeups: 11 Memory: 62.57 GiB used: 1.99 GiB (3.2%) Init: SysVinit
  v: 3.06 runlevel: 5 default: graphical tool: systemctl Compilers: gcc: 12.2.0 alt: 12
  Client: shell wrapper v: 5.2.15-release inxi: 3.3.26
Boot Mode: UEFI

[xaol]

xaol: Something tells me you may have asked an important question. This is from a Terminal open in the Mx Linux desktop environment, since I am back in it now. This doesn't look good:

Code: Select all

[~]
$ service lightdm status
lightdm is not running ... failed!
[~]
$ 

i think that's probably to be expected since you opened the gui with startx. hopefully if it is enabled at boot as suggested, it will start properly the next time you reboot.

[Charlie Brown]

... Is that an app?..

Yep, in Whisker menu (one of the MX Tools). However no need to that as it seems to be ok, you just have the quiet parameter (if you like you can add nosplash there to see the flowing text.. you may/may not, not a must)

Whatever, all look fine (not bad) now, just it seems you're using Nvidia as the default, maybe set so in Bios settings. Therefore it didn't load the i915 driver for Intel):

Graphics:
Device-1: Intel AlderLake-S GT1 vendor: Gigabyte driver: N/A alternate: i915 bus-ID: 00:02.0
...
Device-2: NVIDIA GA104 [GeForce RTX 3070 Ti] vendor: eVga.com. driver: nvidia v: 525.147.05
...
Display: server: X.Org v: 1.21.1.7 compositor: xfwm v: 4.18.0 driver: X: loaded: nvidia
unloaded: fbdev,modesetting,nouveau,vesa alternate: nv gpu: nvidia display-ID: :0 screens: 1

Screen-1: 0 s-res: 1920x1080 s-dpi: 96 s-size: 508x286mm (20.00x11.26") s-diag: 583mm (22.95")
Monitor-1: HDMI-0 res: 1920x1080 hz: 60 dpi: 82 size: 598x336mm (23.54x13.23")
diag: 686mm (27.01") modes: N/A
API: OpenGL v: 4.6.0 NVIDIA 525.147.05 renderer: NVIDIA GeForce RTX 3070 Ti/PCIe/SSE2
direct-render: Yes

[james]

Charlie Brown: I assume you mean lightdm in the Service Manager? OK, when selected, there is a Start button in the lower right and also a "Disable at Boot" button. I figure I don't want to disable it at boot, so I don't press that one. When I press START I am suddenly back at a black screen with a blinking cursor in the upper left. But xaol taught me the Control-Alt-F1 trick, and so I'm back in the GUI again, and there's a box that says "Success: lightdm was started". I am currently connected to an HD monitor, because the resolution was crap on this until I got this problem fixed, so I guess I should switch it to my 4K UHD monitor to make sure the resolution goes back to normal for 4K, but let me finish trouble-shooting this. Is there a suggestion on what else needs to be done to get this machine to reboot and then come back up into Mx like it should?

[Charlie Brown]

No, don't disable that, it's (and should be) already enabled.

Just, do you remember disabling the Intel card in Bios settings (or so) ?

[james]

Charlie Brown: "Just, do you remember disabling the Intel card in Bios settings (or so) ?"
I do not recall doing anything regarding video in BIOS. I do not want to use the Intel card, though, because I think that is on the motherboard. I have a GTForce RTX 3070 Ti which I bought to be able to handle a 4K UHD monitor, so that's the one I want to use. I had that all configured and working after installing the nVidia driver, until I ran into this no-boot problem. Is there anything else you suggest I do or am I ready to reboot the machine and see if it behaves itself?

[Charlie Brown]

Ok, then all are fine. Just reboot.

(You already know what to do in case of the same issue :D )

[james]

Charlie Brown: Nope, this is not fixed. It boots to the same black screen with the blinking cursor in the upper left. I can now do the CNTRL-ALT-F1, do the log-in and password, type "startx" at the prompt, and then put in the password to unlock the Keyring, but I REALLY don't want to have to do that every time I reboot. I took your advice and typed "e" and was able to write down all the stuff in Grub:

Code: Select all

 Grub Version 2.06-13+deb12u1
load video
insmod gzio
if [x$grub-platform=xxen]; then insmod xzio; insmod izopio; fi
insmod part-gpt
insmod ext2
search --no-floppy --fs -UUID --set=root  c32...(serial # of root)...9756
echo 'Loading Linux 6.7.8-1-liquorix-amd64...'
linus /boot/vmlinuz-6.7.8  Linux 6.7.8-1-liquorix-amd64  root=UUID
echo c32...(serial # of root)...9756 ro quiet
'Loading initial ramdisk...'
initrd /boot/initrd.img-6.7.8-1-liquorix-amd64

Is there a way to get this thing just to boot like it used to, into the desktop GUI?
Thank you for all your help.

[james]

I have rebooted and it boots to the same black screen with the blinking cursor in the upper left. I can now do the CNTRL-ALT-F1, do the log-in and password, type "startx" at the prompt, and then put in the password to unlock the Keyring. REALLY don't want to go through that every time. I just ran "service lightdm status" and the result is

Code: Select all

lightdm is not running ... failed!

As before, when I bring up Mx Service Manager and select "lightdm" it has a "Disable at boot" button, which I think means it is set to start up at boot as it should, and next to that is a start button, meaning it did NOT start at boot, thus the "failed" above.
Any idea how to fix this so that startx does not fail? And is this the cause of this whole thing (what at least appeared to be a failure to boot because it stopped at the black screen) or is it something else?

[Charlie Brown]

Code: Select all

sudo update-rc.d lightdm defaults

Reboot.

Btw. When booting live usb replace failsafe with xorg=nvidia