Cant boot MX23 on P520, reboot loop

Message
Author
User avatar
Lobstercat
Posts: 15
Joined: Fri Mar 03, 2017 3:06 am

Cant boot MX23 on P520, reboot loop

#1 Post by Lobstercat »

Strange... So I have MX installed on all my computers & it works great! But just got a new Lenovo Thinkstation P520 and it just keeps rebooting. Okay, new as in new for me, yeah I'm not rich so all my computers are old, hahaha! Anyway, so it's a P520 with a M.2 installed. I installed Windows and Fedora. Disk is using MBR since all other PCs are MBR and several VHDs are MBR and it seems it even knows if DVDs were made with MBR and won't let me install GPT plus my VHDs won't work (or so I hear) with a UEFI install, I know I'll get questions on that. Anyway, a bunch of random info that may be useful:
Win works fine. Fedora also works great but anything with GRUB takes forever. Updating Grub and bootloader requires leaving it on overnight. I tried burning MX23 to a DVD but same result as booting from ISO file. MX boots to selection screen and after booting will flash Probing EDD or something, tried booting with EDD=off or something, forgot at the moment, but anyway then it doesn't flash anything on the screen, it just causes the system to reboot. Tried in failsafe, same thing. Tried changing video, same thing. PC has no onboard video, has a RTX3060 video card installed. BIOS is set for Legacy MBR. Same result booting from ISO file on M.2, internal HD, external USB, or physical DVD.
So any ideas? MX has always been my go-to for "it always boots no matter what" solutions, so strange that it doesn't work here, it seems it should. There was one other command which I tried as well (I mean boot argument) which I also forgot now, but it also didn't work or do anything. Hmmmm, I'm puzzled. If you need any more info of course, let me know. Thank you very much in advance for your help!

User avatar
j2mcgreg
Global Moderator
Posts: 6669
Joined: Tue Oct 23, 2007 12:04 pm

Re: Cant boot MX23 on P520, reboot loop

#2 Post by j2mcgreg »

Could you run

Code: Select all

inxi -Fxxxrza

in Fedora and post the results here (in code tags) so we can get a good overview of that machine?
HP 15; ryzen 3 5300U APU; 500 Gb SSD; 8GB ram
HP 17; ryzen 3 3200; 500 GB SSD; 12 GB ram
Idea Center 3; 12 gen i5; 256 GB ssd;

In Linux, newer isn't always better. The best solution is the one that works.

User avatar
Lobstercat
Posts: 15
Joined: Fri Mar 03, 2017 3:06 am

Re: Cant boot MX23 on P520, reboot loop

#3 Post by Lobstercat »

Okay, so here are a few updates: Last time I ran Fedora it updated the Grub/bootloader but didn't recognize itself. Used my trusty SuperGrub2 disk, it worked but with lots of errors, a lot of "insmod isn't allowed to execute in an extractor", and some save_env/export/loadfont/terminal_output/load_env/etc isn't allowed to execute in an extractor, a few "can't find command"'s, etc. Eventually got to Fedora but it quite after a very long load. It probably would have loaded on second try, but didn't want to take a chance so used my live install disk instead. I ran the command, Here is the output I hope. Hopefully it get code tags right..

Code: Select all

Complete!
[liveuser@localhost-live ~]$ inxi -Fxxxrza
System:
  Kernel: 6.2.9-300.fc38.x86_64 arch: x86_64 bits: 64 compiler: gcc
    v: 2.39-9.fc38 clocksource: tsc available: hpet,acpi_pm
    parameters: BOOT_IMAGE=/images/pxeboot/vmlinuz
    root=live:CDLABEL=Fedora-WS-Live-38-1-6 rd.live.image quiet rhgb
  Desktop: GNOME v: 44.0 tk: GTK v: 3.24.37 wm: gnome-shell dm: GDM v: 43.0
    Distro: Fedora release 38 (Thirty Eight)
Machine:
  Type: Desktop System: LENOVO product: 30BFS0NH0S v: ThinkStation P520
    serial: <superuser required> Chassis: type: 3 serial: <superuser required>
  Mobo: LENOVO model: 1036 v: NO DPK serial: <superuser required>
    BIOS: LENOVO v: S03KT40A date: 08/12/2020
CPU:
  Info: model: Intel Xeon W-2145 bits: 64 type: MT MCP arch: Skylake level: v4
    note: check process: Intel 14nm family: 6 model-id: 0x55 (85) stepping: 4
    microcode: 0x2006906
  Topology: cpus: 1x cores: 8 tpc: 2 threads: 16 smt: enabled cache:
    L1: 512 KiB desc: d-8x32 KiB; i-8x32 KiB L2: 8 MiB desc: 8x1024 KiB
    L3: 11 MiB desc: 1x11 MiB
  Speed (MHz): avg: 2918 high: 3700 min/max: 1200/4500 scaling:
    driver: intel_pstate governor: powersave cores: 1: 3700 2: 3700 3: 3700
    4: 3700 5: 1200 6: 1200 7: 3700 8: 3700 9: 3700 10: 1200 11: 3700 12: 3700
    13: 3700 14: 3700 15: 1200 16: 1200 bogomips: 118395
  Flags: avx avx2 ht lm nx pae sse sse2 sse3 sse4_1 sse4_2 ssse3 vmx
  Vulnerabilities:
  Type: itlb_multihit status: KVM: VMX disabled
  Type: l1tf mitigation: PTE Inversion; VMX: conditional cache flushes, SMT
    vulnerable
  Type: mds mitigation: Clear CPU buffers; SMT vulnerable
  Type: meltdown mitigation: PTI
  Type: mmio_stale_data mitigation: Clear CPU buffers; SMT vulnerable
  Type: retbleed mitigation: IBRS
  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: IBRS, IBPB: conditional, STIBP: conditional,
    RSB filling, PBRSB-eIBRS: Not affected
  Type: srbds status: Not affected
  Type: tsx_async_abort mitigation: Clear CPU buffers; SMT vulnerable
Graphics:
  Device-1: NVIDIA GA106 [GeForce RTX 3060 Lite Hash Rate] vendor: Gigabyte
    driver: nouveau v: kernel non-free: 535.xx+ status: current (as of 2023-09)
    arch: Ampere code: GAxxx process: TSMC n7 (7nm) built: 2020-23 pcie:
    gen: 3 speed: 8 GT/s lanes: 16 link-max: gen: 4 speed: 16 GT/s ports:
    active: DP-2 empty: DP-1,HDMI-A-1,HDMI-A-2 bus-ID: 65:00.0
    chip-ID: 10de:2504 class-ID: 0300
  Display: wayland server: X.org v: 1.20.14 with: Xwayland v: 22.1.9
    compositor: gnome-shell driver: gpu: nouveau display-ID: 0
  Monitor-1: DP-2 model: HP V24i G5 serial: <filter> built: 2022
    res: 1920x1080 dpi: 93 gamma: 1.2 size: 527x296mm (20.75x11.65")
    diag: 604mm (23.8") ratio: 16:9 modes: max: 1920x1080 min: 720x400
  API: OpenGL v: 4.3 vendor: mesa v: 23.0.1 glx-v: 1.4 es-v: 3.2
    direct-render: yes renderer: NV176 device-ID: 10de:2504 memory: 11.71 GiB
    unified: no display-ID: :0.0
  API: EGL Message: EGL data requires eglinfo. Check --recommends.
Audio:
  Device-1: Intel 200 Series PCH HD Audio vendor: Lenovo driver: snd_hda_intel
    v: kernel alternate: snd_soc_avs bus-ID: 00:1f.3 chip-ID: 8086:a2f0
    class-ID: 0403
  Device-2: NVIDIA GA106 High Definition Audio vendor: Gigabyte
    driver: snd_hda_intel v: kernel pcie: gen: 3 speed: 8 GT/s lanes: 16
    link-max: gen: 4 speed: 16 GT/s bus-ID: 65:00.1 chip-ID: 10de:228e
    class-ID: 0403
  API: ALSA v: k6.2.9-300.fc38.x86_64 status: kernel-api
    tools: alsactl,alsamixer,amixer
  Server-1: PipeWire v: 0.3.67 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 Ethernet I219-LM vendor: Lenovo driver: e1000e v: kernel
    port: N/A bus-ID: 00:1f.6 chip-ID: 8086:15b7 class-ID: 0200
  IF: eno1 state: up speed: 1000 Mbps duplex: full mac: <filter>
Drives:
  Local Storage: total: 3.64 TiB used: 857.81 GiB (23.0%)
  SMART Message: Required tool smartctl not installed. Check --recommends
  ID-1: /dev/nvme0n1 maj-min: 259:0 vendor: Kingston model: SNV2S1000G
    size: 931.51 GiB block-size: physical: 512 B logical: 512 B speed: 63.2 Gb/s
    lanes: 4 tech: SSD serial: <filter> fw-rev: SBM02103 temp: 19.9 C
    scheme: MBR
  ID-2: /dev/sda maj-min: 8:0 vendor: Western Digital
    model: WD10EZEX-08M2NA0 size: 931.51 GiB block-size: physical: 4096 B
    logical: 512 B speed: 6.0 Gb/s tech: HDD rpm: 7200 serial: <filter>
    fw-rev: 1A01 temp: 27 C scheme: MBR
  ID-3: /dev/sdb maj-min: 8:16 vendor: Western Digital
    model: WD10EZEX-75WN4A0 size: 931.51 GiB block-size: physical: 4096 B
    logical: 512 B speed: 6.0 Gb/s tech: HDD rpm: 7200 serial: <filter>
    fw-rev: 1A01 temp: 27 C scheme: MBR
  ID-4: /dev/sdc maj-min: 8:32 vendor: Western Digital
    model: WD10JMVW-11AJGS4 size: 931.48 GiB block-size: physical: 512 B
    logical: 512 B type: USB rev: 2.1 spd: 480 Mb/s lanes: 1 mode: 2.0
    tech: HDD rpm: 5400 serial: <filter> fw-rev: 1015 scheme: MBR
Partition:
  ID-1: / raw-size: 7.57 GiB size: 7.36 GiB (97.16%) used: 6.1 GiB (82.9%)
    fs: ext4 dev: /dev/dm-0 maj-min: 253:0 mapped: live-rw
Swap:
  Kernel: swappiness: 60 (default) cache-pressure: 100 (default) zswap: no
  ID-1: swap-1 type: zram size: 8 GiB used: 0 KiB (0.0%) priority: 100
    comp: lzo-rle avail: lzo,lz4,lz4hc,842,zstd max-streams: 16 dev: /dev/zram0
Sensors:
  System Temperatures: cpu: 29.0 C mobo: N/A
  Fan Speeds (rpm): N/A
Repos:
  Packages: pm: rpm pkgs: N/A note: see --rpm tools: dnf,gnome-software,yum
    pm: flatpak pkgs: 0
  No active dnf repos in: /etc/dnf/dnf.conf
  No active yum repos in: /etc/yum.repos.d/_copr:copr.fedorainfracloud.org:phracek:PyCharm.repo
  Active yum repos in: /etc/yum.repos.d/fedora-cisco-openh264.repo
    1: fedora-cisco-openh264 ~ https://mirrors.fedoraproject.org/metalink?repo=fedora-cisco-openh264-$releasever&arch=$basearch
  Active yum repos in: /etc/yum.repos.d/fedora-modular.repo
    1: fedora-modular ~ https://mirrors.fedoraproject.org/metalink?repo=fedora-modular-$releasever&arch=$basearch
  Active yum repos in: /etc/yum.repos.d/fedora-updates-modular.repo
    1: updates-modular ~ https://mirrors.fedoraproject.org/metalink?repo=updates-released-modular-f$releasever&arch=$basearch
  No active yum repos in: /etc/yum.repos.d/fedora-updates-testing-modular.repo
  No active yum repos in: /etc/yum.repos.d/fedora-updates-testing.repo
  Active yum repos in: /etc/yum.repos.d/fedora-updates.repo
    1: updates ~ https://mirrors.fedoraproject.org/metalink?repo=updates-released-f$releasever&arch=$basearch
  Active yum repos in: /etc/yum.repos.d/fedora.repo
    1: fedora ~ https://mirrors.fedoraproject.org/metalink?repo=fedora-$releasever&arch=$basearch
  No active yum repos in: /etc/yum.repos.d/google-chrome.repo
  No active yum repos in: /etc/yum.repos.d/rpmfusion-nonfree-nvidia-driver.repo
  No active yum repos in: /etc/yum.repos.d/rpmfusion-nonfree-steam.repo
Info:
  Processes: 365 Uptime: 6m wakeups: 0 Memory: total: 64 GiB
  available: 62.38 GiB used: 3 GiB (4.8%) Init: systemd v: 253
  target: graphical (5) default: graphical tool: systemctl Compilers: N/A
  Shell: Bash v: 5.2.15 running-in: gnome-terminal inxi: 3.3.30
[liveuser@localhost-live ~]$ 

Thank you again, and good luck trying to figure all that out!

ghunter
Posts: 175
Joined: Mon May 29, 2023 12:40 am

Re: Cant boot MX23 on P520, reboot loop

#4 Post by ghunter »

Hi does MX dvd boot OK for any of your other computers?

2) As you have not mentioned which command or software you have used to burn the dvd....what was your command or software?

3) Have you tried flashing an usb stick instead?

4) I assume you have a match for the downloaded dvd image? which 64 MX image did you download please?

5) Leaping ahead if your download was good....maybe your MX dvd does not like your graphics? Try safe mode maybe?

User avatar
Lobstercat
Posts: 15
Joined: Fri Mar 03, 2017 3:06 am

Re: Cant boot MX23 on P520, reboot loop

#5 Post by Lobstercat »

Thanks for your reply! Okay:
1. Yes, MX boots fine from all other computers in the house. Only 2 others have DVD drives, but it boots fine from them, and from USB on the rest.
2. DVD was burned in Windows using ImgBurn
3. Yes, same results.
4. Yes the MD5 & SHA both checked out fine. Using the ahs DVD version.
5. Tried booting in safe mode and in both low and high graphics modes, same result sadly.
Thank you again for helping!

User avatar
j2mcgreg
Global Moderator
Posts: 6669
Joined: Tue Oct 23, 2007 12:04 pm

Re: Cant boot MX23 on P520, reboot loop

#6 Post by j2mcgreg »

Did you remember to disable Secure Boot in your bios and Fast Start Up in Windows?
HP 15; ryzen 3 5300U APU; 500 Gb SSD; 8GB ram
HP 17; ryzen 3 3200; 500 GB SSD; 12 GB ram
Idea Center 3; 12 gen i5; 256 GB ssd;

In Linux, newer isn't always better. The best solution is the one that works.

Charlie Brown

Re: Cant boot MX23 on P520, reboot loop

#7 Post by Charlie Brown »

Also try with

Code: Select all

edd=on nolapic
(Though it's already on by default)

If still not: include also

Code: Select all

noapic
edd=on nolapic noapic

Charlie Brown

Re: Cant boot MX23 on P520, reboot loop

#8 Post by Charlie Brown »

If nothing works and if you'd like to try:

Boot with the usb on another pc, then open "MX Package Installer" from menu, install the "Liquorix 6.5.5.." kernel,

Then : "MX RemasterCC" , finally "Live Usb Kernel Updater" (all from menu)

(... to make it permanent)


Now boot with that usb on this pc.

User avatar
Lobstercat
Posts: 15
Joined: Fri Mar 03, 2017 3:06 am

Re: Cant boot MX23 on P520, reboot loop

#9 Post by Lobstercat »

Thank you for the replies! Okay first, Secure Boot is off, plus it's disabled anyway due to booting in MBR. Fast Boot is not shown in Control Panel, powercfg lists it as unavailable, gpedit lists it as unconfigured, and regedit does show it as enabled (1), so I did change it to 0, and for kicks changed it in gpedit from unconfigured to disabled.
Second, EDD is already enabled by default, enabling or disabling makes no difference. Sadly adding nolapic and noapic also didn't help, still crashed and rebooted. Booting my other PC downstairs to try adding the Liquorix kernel.
I could be wrong but just guessing it may have something to do with the way even Fedora takes all night to do a GRUB/bootloader update - that seems weird when it otherwise seems okay.

User avatar
j2mcgreg
Global Moderator
Posts: 6669
Joined: Tue Oct 23, 2007 12:04 pm

Re: Cant boot MX23 on P520, reboot loop

#10 Post by j2mcgreg »

from here:
https://www.digitalengineering247.com/a ... %20devices.
One of the front panel USB ports is of the Always On type (for charging devices). If it's populated with a regular device, say a mouse receiver or printer etc, a user can get dropped into a reboot loop on shut down.
HP 15; ryzen 3 5300U APU; 500 Gb SSD; 8GB ram
HP 17; ryzen 3 3200; 500 GB SSD; 12 GB ram
Idea Center 3; 12 gen i5; 256 GB ssd;

In Linux, newer isn't always better. The best solution is the one that works.

Post Reply

Return to “General”