Mx-23.2 boot failure

[CharlesV]

please post a new qsi. and did you attempt to use the mx nvidia installer ? (it already be installed. )

[james]

CharlesV,
Yes, I used the Nvidia driver installer seen on the Mx Tools menu.
Here is 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 splash
  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.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 serial: <filter>
    charge: 55% (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: 838 high: 1000 min/max: 800/3201 boost: enabled scaling: driver: acpi-cpufreq
    governor: ondemand cores: 1: 1000 2: 800 3: 931 4: 800 5: 1000 6: 800 7: 989 8: 800 9: 993
    10: 800 11: 800 12: 800 13: 800 14: 800 15: 800 16: 800 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: 4 speed: 16 GT/s lanes: 16 bus-ID: 01:00.0 chip-ID: 10de:2482
    class-ID: 0300
  Display: x11 server: X.Org v: 1.21.1.7 compositor: xfwm v: 4.18.0 driver: X: loaded: N/A
    unloaded: fbdev dri: swrast gpu: nvidia note: X driver n/a display-ID: :0 screens: 1
  Screen-1: 0 s-res: 1024x768 s-dpi: 96 s-size: 271x203mm (10.67x7.99") s-diag: 339mm (13.33")
  Monitor-1: default res: 1024x768 hz: 76 size: N/A modes: N/A
  API: OpenGL v: 4.5 Mesa 23.1.2-1~mx23ahs renderer: llvmpipe (LLVM 15.0.6 256 bits)
    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:3 bus-ID: 00:1f.3 chip-ID: 0414:a012
    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:7 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.27 TiB used: 97.3 GiB (4.2%)
  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: 41.9 C scheme: GPT
  ID-2: /dev/nvme1n1 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: 40.9 C scheme: GPT
  ID-3: /dev/nvme2n1 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: 41.9 C scheme: GPT
Partition:
  ID-1: / raw-size: 931.26 GiB size: 915.57 GiB (98.31%) used: 97.3 GiB (10.6%) fs: ext4
    dev: /dev/nvme1n1p2 maj-min: 259:4
  ID-2: /boot/efi raw-size: 256 MiB size: 252 MiB (98.46%) used: 274 KiB (0.1%) fs: vfat
    dev: /dev/nvme1n1p1 maj-min: 259:3
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: 27.0 C mobo: N/A
  Fan Speeds (RPM): N/A
Repos:
  Packages: pm: dpkg pkgs: 2697 libs: 1447 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: 484 Uptime: 9h 18m wakeups: 13 Memory: 62.57 GiB used: 1.97 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

[Charlie Brown]

The res. etc. are not ok cause (though your boot parameters are ok, somehow) :

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: 4 speed: 16 GT/s lanes: 16 bus-ID: 01:00.0 chip-ID: 10de:2482
class-ID: 0300
Display: x11 server: X.Org v: 1.21.1.7 compositor: xfwm v: 4.18.0 driver: X: loaded: N/A
unloaded: fbdev dri: swrast gpu: nvidia note: X driver n/a display-ID: :0 screens: 1
Screen-1: 0 s-res: 1024x768 s-dpi: 96 s-size: 271x203mm (10.67x7.99") s-diag: 339mm (13.33")
Monitor-1: default res: 1024x768 hz: 76 size: N/A modes: N/A
API: OpenGL v: 4.5 Mesa 23.1.2-1~mx23ahs renderer: llvmpipe (LLVM 15.0.6 256 bits)
direct-render: Yes


As in previous posts, delete the /etc/X11/xorg.conf file "if existing", reboot,

... if still the same: apply post #53.

[james]

OK, here's this situation now...
I tried the first suggestion, got rid of the /etc/X11/xorg.conf, rebooted.
The machine came up with the Mx splash screen and the resolution was UHD. Wonderful.
Launched a VirtualBox. It complained it could not see the M drive, which was the OTHER nmve drive I had been using for data. Brought up Disks, and I could see a boot partition and a root partition on both nvme1 and nvme2. So I brought up gParted and deleted one. I figured, I'll delete both partitions off the one that isn't mounted and make a new ext4 partition called M and take ownership. And rebooted. Worked again.
VirtualBox still not happy, had to delete and remount the new M drive, and will have to create all the file structure that used to be there.
But from here on, any problems I encounter should be related to the fact I wiped the data and folders from the M drive, which I can restore. MX is back and working, and I have rebooted it a couple of times to see if it was going to surprise me. Loaded all the updates and rebooted again. OK.
Looks like I'm back to where I was four days ago. Just a couple of final questions...
1) Pan newsreader search bar keeps acting like both the Numlock and Insert key functions are in the wrong state. I try to type something in and its highlighting a character instead of inserting one, or deleting what was highlighted instead of adding one. I know that there is, at least for Numlock, a way to turn it either off or on. Can you tell me where that is, and is that permanent?
2) Why do there have to be so many keys on the keyboard? Couldn't there be just one??? :-)
Anyway, thanks for all the assistance in getting this resolved. I'll mark it solved in a couple of days... I just don't want to jinx myself quite yet...
But for now, it LOOKS like this dog is fit to hunt.
And Snapshot works and has saved me from having to re-install and re-configure all the apps!
Thank you all again for your patience and help during a very frustrating three days.
James

[DukeComposed]

2) Why do there have to be so many keys on the keyboard? Couldn't there be just one???

Way ahead of you.

[Charlie Brown]

... I know that there is, at least for Numlock, a way to turn it either off or on...

[james]

DukeComposed: yep, the only person who could have benefited from that keyboard was Stephen Hawking - if he could have moved a finger....

Charlie Brown: Thanks again. There certainly were a lot of people helping me out these past few days, and while xoal, for instance, suggested the CNTRL-ALT-F1, you were the one who took the last step in getting me back into the desktop from the no-boot state, and the one who got the screen resolution back, so a special thanks to you. Besides great software, this is a great forum, without which I would certainly NOT be using MX at this point.

[Charlie Brown]

You're welcome.

In case you create a new snapshot later: just remember (as I previously told) you need to use the parameter (when booting that live usb):

Code: Select all

xorg=nvidia

(Otherwise it may boot to a black screen. But this is not related to these issues or not specific to you. Just for Nvidia driver is installed, it needs to be done this way. Yes, there are ways to make it permanent (not to type each time) but this time the live usb won't boot on other (non-Nvidia) machines ... )

[james]

Charlie Brown: Good to know. Actually, I have another machine that I usually use, and the one we've been messing with is a secondary that I am using to test MX before I put it on my main machine. I want to run into whatever I'm going to run into (sure glad I made THAT decision!) before I put convert my main machine to MX. Now, the main machine also has an NVIDIA GEFORCE graphics card, but not the same one - actually its an older one, but it also supports UHD graphics. Unlike the secondary we have been debugging which is Intel board and CPU, the main machine is AMD board and CPU. Would you advise using the Live USB snapshot I just made that was a snapshot of the secondary secondary machine when I convert the main machine, or do you think it would be wise to make a new LIVE Snapshot ISO of the secondary before doing that? Also, where do I enter that parameter you pasted above? Do I go to MX Boot Options and paste that in the Kernel parameters, and if so is it in addition to or replacing the "quiet splash" that is there now?

[Charlie Brown]

... where do I enter that parameter you pasted above?..

On (the blue) welcome screen, when the top entry "MX-23 ..." is highlighted just press E and you'll see the current ones, like

linux ... ... quiet splasht splash ...

just type among / after them with a space before (&after) then press F10


As for the other pc: the simplest is to boot with this live usb (or the next iso you prepare for/on this pc).

Cause, say, the installed driver is 525.xxx (according to this pc), the other pc might require another one (say, it may be able to work with one of the "legacy" drivers only)... Shortly when you try to boot it'll give the answer, also no harm.