MX Linux Forum

Posted: **Wed Jan 29, 2025 9:54 pm**

Think I may have messed up my main drive with a hard reset. This is a fairly new reinstall

Getting this at boot:
0.134147] ACPI Error: Needed type [Reference], found [Integer] (____ptrval__) (20228331/exresop-66) '
C @.134153] ACPI Error: AE_AML_OPERAND_TYPE, While resolving operands for [Op
codeName unavailable] (28220331 /dswexec-431)
C @.134157] ACPI Error: Aborting method \_PR.CPU@._PDC due to previous error
(RE_AML_OPERAND_TYPE) (28228331/psparse-529)
[ 1.482684] DMAR: DRHD: handling fault status reg 2
{ 1.482688] DMAR: [DMA Read NO_PASID] Request device [01:00.01] fault addr 0x0
[fault reason 0x06] PTE Read access is not set
[ 1.555689] nouveau 6888:01:08.8: DRM: Pointer to LVDS manufacturer table invalid
Give root password for maintenance
(or press Control-D to continue):

I can press Control D, and everything loads, but think I'd better fix the problem before it manifests itself in worse ways.

I'm running on an old iMac:

Kernel: 6.1.0-30-amd64 [6.1.124-1] arch: x86_64 bits: 64 compiler: gcc v: 12.2.0
parameters: BOOT_IMAGE=/boot/vmlinuz-6.1.0-30-amd64 root=UUID=<filter> ro quiet splash
Desktop: Xfce v: 4.20.0 tk: Gtk v: 3.24.38 info: xfce4-panel wm: xfwm v: 4.20.0 vt: 7
dm: LightDM v: 1.32.0 Distro: MX-23.5_x64 Libretto September 15 2024 base: Debian GNU/Linux 12
(bookworm)

iMac14,2 v: 1.0 date: 04/09/2018

Graphics:
Device-1: NVIDIA GK104M [GeForce GTX 775M Mac Edition] vendor: Apple driver: nouveau v: kernel
non-free: series: 470.xx+ status: legacy-active (EOL~2023/24) arch: Kepler code: GKxxx
process: TSMC 28nm built: 2012-18 pcie: gen: 1 speed: 2.5 GT/s lanes: 16 link-max: gen: 3
speed: 8 GT/s ports: active: DP-1 empty: DP-2,DP-3 bus-ID: 01:00.0 chip-ID: 10de:119d
class-ID: 0300 temp: 48.0 C
Device-2: Apple FaceTime HD Camera (Built-in) type: USB driver: uvcvideo bus-ID: 1-7:5
chip-ID: 05ac:8511 class-ID: 0e02 serial: <filter>
Display: x11 server: X.Org v: 1.21.1.7 compositor: xfwm v: 4.20.0 driver: X:
loaded: modesetting unloaded: fbdev,vesa dri: nouveau gpu: nouveau display-ID: :0.0 screens: 1

Any ideas how to fix this? My skills are basic, not my day job.

ANY help appreciated.

Barry

Posted: **Thu Jan 30, 2025 12:44 am**

Please post code like so:
[code]code output here[/code]

Also, FULL QSI please.

Thanks.

Posted: **Thu Jan 30, 2025 1:32 am**

Reposting with Code:

Code: Select all

0.134147] ACPI Error: Needed type [Reference], found [Integer] (____ptrval__) (20228331/exresop-66) '
C @.134153] ACPI Error: AE_AML_OPERAND_TYPE, While resolving operands for [Op
codeName unavailable] (28220331 /dswexec-431)
C @.134157] ACPI Error: Aborting method \_PR.CPU@._PDC due to previous error
(RE_AML_OPERAND_TYPE) (28228331/psparse-529)
[ 1.482684] DMAR: DRHD: handling fault status reg 2
{ 1.482688] DMAR: [DMA Read NO_PASID] Request device [01:00.01] fault addr 0x0
[fault reason 0x06] PTE Read access is not set
[ 1.555689] nouveau 6888:01:08.8: DRM: Pointer to LVDS manufacturer table invalid
Give root password for maintenance
(or press Control-D to continue):

Full QSI:

Code: Select all

Snapshot created on: 20250126_2309
System:
  Kernel: 6.1.0-30-amd64 [6.1.124-1] arch: x86_64 bits: 64 compiler: gcc v: 12.2.0
    parameters: BOOT_IMAGE=/boot/vmlinuz-6.1.0-30-amd64 root=UUID=<filter> ro quiet splash
  Desktop: Xfce v: 4.20.0 tk: Gtk v: 3.24.38 info: xfce4-panel wm: xfwm v: 4.20.0 vt: 7
    dm: LightDM v: 1.32.0 Distro: MX-23.5_x64 Libretto September 15  2024 base: Debian GNU/Linux 12
    (bookworm)
Machine:
  Type: Desktop System: Apple product: iMac14,2 v: 1.0 serial: <superuser required> Chassis:
    type: 13 v: Mac-27ADBB7B4CEE8E61 serial: <superuser required>
  Mobo: Apple model: Mac-27ADBB7B4CEE8E61 v: iMac14,2 serial: <superuser required> UEFI: Apple
    v: IM142.88Z.0130.B00.1804091831 date: 04/09/2018
Battery:
  Device-1: hidpp_battery_5 model: Logitech ERGO M575 Trackball serial: <filter> charge: 55%
    rechargeable: yes status: discharging
CPU:
  Info: model: Intel Core i7-4771 bits: 64 type: MT MCP arch: Haswell gen: core 4 level: v3
    note: check built: 2013-15 process: Intel 22nm family: 6 model-id: 0x3C (60) stepping: 3
    microcode: 0x28
  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: 8 MiB desc: 1x8 MiB
  Speed (MHz): avg: 3215 high: 3866 min/max: 800/3900 scaling: driver: intel_cpufreq
    governor: ondemand cores: 1: 3492 2: 900 3: 3866 4: 3493 5: 3492 6: 3492 7: 3493 8: 3493
    bogomips: 55867
  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: 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 status: Unknown: No mitigations
  Type: reg_file_data_sampling 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: Retpolines; IBPB: conditional; IBRS_FW; STIBP: conditional; RSB
    filling; PBRSB-eIBRS: Not affected; BHI: Not affected
  Type: srbds mitigation: Microcode
  Type: tsx_async_abort status: Not affected
Graphics:
  Device-1: NVIDIA GK104M [GeForce GTX 775M Mac Edition] vendor: Apple driver: nouveau v: kernel
    non-free: series: 470.xx+ status: legacy-active (EOL~2023/24) arch: Kepler code: GKxxx
    process: TSMC 28nm built: 2012-18 pcie: gen: 1 speed: 2.5 GT/s lanes: 16 link-max: gen: 3
    speed: 8 GT/s ports: active: DP-1 empty: DP-2,DP-3 bus-ID: 01:00.0 chip-ID: 10de:119d
    class-ID: 0300 temp: 46.0 C
  Device-2: Apple FaceTime HD Camera (Built-in) type: USB driver: uvcvideo bus-ID: 1-7:5
    chip-ID: 05ac:8511 class-ID: 0e02 serial: <filter>
  Display: x11 server: X.Org v: 1.21.1.7 compositor: xfwm v: 4.20.0 driver: X:
    loaded: modesetting unloaded: fbdev,vesa dri: nouveau gpu: nouveau display-ID: :0.0 screens: 1
  Screen-1: 0 s-res: 2560x1440 s-dpi: 96 s-size: 678x382mm (26.69x15.04") s-diag: 778mm (30.64")
  Monitor-1: DP-1 model: Apple iMac built: 2012 res: 2560x1440 hz: 60 dpi: 109 gamma: 1.2
    size: 597x336mm (23.5x13.23") diag: 685mm (27") ratio: 16:9 modes: max: 2560x1440 min: 1280x720
  API: OpenGL v: 4.3 Mesa 22.3.6 renderer: NVE4 direct-render: Yes
Audio:
  Device-1: Intel 8 Series/C220 Series High Definition Audio driver: snd_hda_intel v: kernel
    bus-ID: 00:1b.0 chip-ID: 8086:8c20 class-ID: 0403
  Device-2: NVIDIA GK104 HDMI Audio driver: snd_hda_intel v: kernel pcie: gen: 1 speed: 2.5 GT/s
    lanes: 16 link-max: gen: 3 speed: 8 GT/s bus-ID: 01:00.1 chip-ID: 10de:0e0a class-ID: 0403
  API: ALSA v: k6.1.0-30-amd64 status: kernel-api tools: alsamixer,amixer
  Server-1: PipeWire v: 1.0.0 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: Broadcom BCM4360 802.11ac Wireless Network Adapter vendor: Apple driver: wl v: kernel
    modules: bcma pcie: gen: 1 speed: 2.5 GT/s lanes: 1 bus-ID: 03:00.0 chip-ID: 14e4:43a0
    class-ID: 0280
  IF: wlan0 state: down mac: <filter>
  Device-2: Broadcom NetXtreme BCM57766 Gigabit Ethernet PCIe driver: tg3 v: kernel pcie: gen: 1
    speed: 2.5 GT/s lanes: 1 port: N/A bus-ID: 04:00.0 chip-ID: 14e4:1686 class-ID: 0200
  IF: eth0 state: up speed: 100 Mbps duplex: full mac: <filter>
Bluetooth:
  Device-1: Apple Bluetooth Host Controller type: USB driver: btusb v: 0.8 bus-ID: 1-8.3:11
    chip-ID: 05ac:828d class-ID: fe01
  Report: hciconfig ID: hci0 rfk-id: 1 state: up address: <filter> bt-v: 2.1 lmp-v: 4.0
    sub-v: 4176 hci-v: 4.0 rev: 23a3
  Info: acl-mtu: 1021:8 sco-mtu: 64:1 link-policy: rswitch sniff link-mode: peripheral accept
    service-classes: rendering, capturing, object transfer, audio, telephony
Drives:
  Local Storage: total: 946.42 GiB used: 701.12 GiB (74.1%)
  SMART Message: Unable to run smartctl. Root privileges required.
  ID-1: /dev/sda maj-min: 8:0 vendor: Apple model: HDD ST1000DM003 size: 931.51 GiB block-size:
    physical: 4096 B logical: 512 B speed: 3.0 Gb/s type: HDD rpm: 7200 serial: <filter> rev: AP19
    scheme: GPT
  ID-2: /dev/sdc maj-min: 8:32 type: USB vendor: SanDisk model: Cruzer Fit size: 14.91 GiB
    block-size: physical: 512 B logical: 512 B type: N/A serial: <filter> rev: 1.26 scheme: GPT
  SMART Message: Unknown USB bridge. Flash drive/Unsupported enclosure?
Partition:
  ID-1: / raw-size: 27.94 GiB size: 27.33 GiB (97.83%) used: 15.98 GiB (58.5%) fs: ext4
    dev: /dev/sda2 maj-min: 8:2
  ID-2: /boot/efi raw-size: 256 MiB size: 252 MiB (98.46%) used: 274 KiB (0.1%) fs: vfat
    dev: /dev/sda1 maj-min: 8:1
  ID-3: /home raw-size: 903.32 GiB size: 888.07 GiB (98.31%) used: 678.81 GiB (76.4%) fs: ext4
    dev: /dev/sda3 maj-min: 8:3
Swap:
  Kernel: swappiness: 15 (default 60) cache-pressure: 100 (default)
  ID-1: swap-1 type: file size: 4 GiB used: 3.3 MiB (0.1%) priority: -2 file: /swap/swap
Sensors:
  System Temperatures: cpu: 48.0 C mobo: N/A gpu: nouveau temp: 46.0 C
  Fan Speeds (RPM): N/A
Repos:
  Packages: pm: dpkg pkgs: 2918 libs: 1621 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/brave-browser-release.list
    1: deb [arch=amd64 signed-by=/usr/share/keyrings/brave-browser-archive-keyring.gpg] 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 http://mirror.math.princeton.edu/pub/mxlinux/mx/repo/ bookworm main non-free
  Active apt repos in: /etc/apt/sources.list.d/extrepo_librewolf.sources
    1: deb [arch=amd64 arm64] https://repo.librewolf.net librewolf main
Info:
  Processes: 308 Uptime: 3h 53m wakeups: 17 Memory: 15.56 GiB used: 5.88 GiB (37.8%) 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

Posted: **Thu Jan 30, 2025 9:27 am**

I think I would do a fsck on the root partition.

you can try adding this to your boot parameters

Code: Select all

fsck.mode=force

but you can also do the fsck from a live usb.

Posted: **Thu Jan 30, 2025 12:38 pm**

I'll try fsck from a usb and report back when I get the chance.

Thanks!

Posted: **Thu Jan 30, 2025 4:40 pm**

Tried fsck from a usb on sda's. No dice. Same error. Any other ideas?

Posted: **Thu Jan 30, 2025 5:44 pm**

bcreighton wrote: Thu Jan 30, 2025 4:40 pm Tried fsck from a usb on sda's. No dice. Same error. Any other ideas?

Based on the age of your CPU, your HDD is eleven years old and likely needs to be replaced.

Posted: **Thu Jan 30, 2025 7:23 pm**

did you run the fsck on all your partitions?

Posted: **Thu Jan 30, 2025 10:39 pm**

CPU is fine. Hard drive... maybe getting a little up there, but it isn't throwing any errors. Other than that, the display is still gorgeous and it is a solid computer. No reason to throw it away, what a waste. It was working fine UNTIL installed the latest upgrade.

Yes, I ran fsck on sda1, sda2, and sda3. SDA2 and 3 were clean.

Anything else I can try?

Posted: **Thu Jan 30, 2025 10:44 pm**

Maybe to check to see if all fstab entries are still valid.

Posted: **Sat Feb 01, 2025 11:46 pm**

How do I do that? Not really familiar with fstab.

Thanks.

Posted: **Sun Feb 02, 2025 12:36 am**

bcreighton wrote: Sat Feb 01, 2025 11:46 pm How do I do that? Not really familiar with fstab.

"man fstab" will be useful here. And since you've already posted your QSI, you know that you have a few partitions to be aware of:

Code: Select all

Partition:
  ID-1: / raw-size: 27.94 GiB size: 27.33 GiB (97.83%) used: 15.98 GiB (58.5%) fs: ext4
    dev: /dev/sda2 maj-min: 8:2
  ID-2: /boot/efi raw-size: 256 MiB size: 252 MiB (98.46%) used: 274 KiB (0.1%) fs: vfat
    dev: /dev/sda1 maj-min: 8:1
  ID-3: /home raw-size: 903.32 GiB size: 888.07 GiB (98.31%) used: 678.81 GiB (76.4%) fs: ext4
    dev: /dev/sda3 maj-min: 8:3

Each of these partitions needs its own entry in /etc/fstab. "/" needs to point to /dev/sda2. "/boot/efi" needs to point to /dev/sda1. And so forth.

In short, every mountpoint (/, /home, /boot/efi) needs a line that pairs it to its own unique /dev/something partition.

Posted: **Sun Feb 02, 2025 8:33 am**

post output of

Code: Select all

cat /etc/fstab
sudo blkid

Posted: **Sun Feb 02, 2025 11:31 am**

You can try to avoid hard reboots when you lock-up by using {Fn+F1-F4} for a terminal, and then, logout, exit, or shutdown -r or -h now. There are a few other tricks for that, too. REISUB is one of them. (I learned that recently here, on this great forum.)

Posted: **Wed Feb 05, 2025 11:03 am**

Sorry for the delay, life interruptions.

ok, this is what i have in my etc/fstab. As nearly as I can determine, there is an entry for each partition?

#Entry for /dev/sda1 :
UUID=5E04-1863 /boot/efi vfat noatime,dmask=0002,fmask=0113 0 0

#Entry for /dev/sda2 :
UUID=611a97a7-33e9-4c26-93da-bdce9c0b1e39 / ext4 noatime 1 1

#Entry for /dev/sda3 :
UUID=72372e9f-feec-4830-9c96-f3c0ebe06a45 /home ext4 noatime 1 0
/swap/swap swap swap defaults 0 0

Thanks.

Posted: **Sat Feb 08, 2025 12:31 pm**

Oh, oops, Hi @bcreighton,

If you haven't figured out my mistake yet, my above "help" should have read {Ctl+Alt+F1-F4}. Sorry 'bout that.

Posted: **Sat Feb 08, 2025 1:35 pm**

bcreighton wrote: Wed Feb 05, 2025 11:03 am Sorry for the delay, life interruptions.

ok, this is what i have in my etc/fstab. As nearly as I can determine, there is an entry for each partition?

#Entry for /dev/sda1 :
UUID=5E04-1863 /boot/efi vfat noatime,dmask=0002,fmask=0113 0 0

#Entry for /dev/sda2 :
UUID=611a97a7-33e9-4c26-93da-bdce9c0b1e39 / ext4 noatime 1 1

#Entry for /dev/sda3 :
UUID=72372e9f-feec-4830-9c96-f3c0ebe06a45 /home ext4 noatime 1 0
/swap/swap swap swap defaults 0 0

Thanks.

The fstab looks good. So is your boot error now fixed?
If not, may be good to let us know what those UUID relates to, eithe one of those (or both)

Code: Select all

sudo blkid

or

Code: Select all

sudo lsblk -f

Posted: **Mon Feb 10, 2025 1:14 pm**

No, I wish.

Here are the results of running lsblk

Code: Select all

 /dev/sda1: LABEL_FATBOOT="EFI-SYSTEM" LABEL="EFI-SYSTEM" UUID="5E04-1863" BLOCK_SIZE="512" TYPE="vfat" PARTLABEL="primary" PARTUUID="7edbeb11-86ab-4f08-a7a4-76e3f1dc7387"
/dev/sda2: LABEL="rootMX23" UUID="611a97a7-33e9-4c26-93da-bdce9c0b1e39" BLOCK_SIZE="4096" TYPE="ext4" PARTLABEL="primary" PARTUUID="5b75caf0-ef20-45fc-9fd4-c6750139e012"
/dev/sda3: LABEL="homeMX" UUID="72372e9f-feec-4830-9c96-f3c0ebe06a45" BLOCK_SIZE="4096" TYPE="ext4" PARTLABEL="primary" PARTUUID="0eca8624-1efd-4135-af70-353c7f5458e1"

so SDA1 EFI
SDA2 Operating System?
SDA3 File system?

Posted: **Tue Feb 11, 2025 1:04 pm**

No more ideas? : )

Posted: **Tue Feb 11, 2025 1:32 pm**

Does the MX liveUSB/liveSystem boot normally?
Have you tried al from LiveSystem runnin Gparted -> right click on the partions -> check, which does fscheck and a bit more.
Would it boot from LiveUSB Booet menu -> Boot Rescue Menu"-> search for GRUB loader/menus?

Posted: **Wed Feb 19, 2025 12:40 am**

Can I use snapshot, then MX Linux USB Maker, and just do a fresh install to solve this problem?

Posted: **Wed Feb 19, 2025 3:45 am**

If your system itself is faulty you will be taking that along in the snapshot, and the consequent install.

Posted: **Wed Feb 19, 2025 11:11 am**

But, it seems to boot and work fine when I use a MX Linux made USB copy?

Posted: **Wed Feb 19, 2025 11:21 am**

bcreighton wrote: Wed Feb 19, 2025 11:11 am But, it seems to boot and work fine when I use a MX Linux made USB copy?

But you will only really know through use.

Posted: **Wed Feb 19, 2025 11:22 am**

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

Guess there is only 1 way to find out.

Posted: **Wed Feb 19, 2025 1:04 pm**

OK, tried new install from MX Linux USB. Exact same error. Rebooted into usb live, ran gparted, checked partitions. Main partition was fine. The fat 32 partition succeeded, no errors, but when it tried to grow file system to fill the partition using libparted, it threw an error with no additional information.

Am I at an end? Should I just do a fresh install?

Posted: **Fri Feb 21, 2025 10:42 am**

Yea, fresh install, same result. Installed graphic card's codecs, no dice. Think thats it. Odd, the same OS runs off my USB stick without a hitch. Can't figure that one out, but I give up

Posted: **Fri Feb 21, 2025 11:12 am**

bcreighton wrote: Fri Feb 21, 2025 10:42 am Yea, fresh install, same result. Installed graphic card's codecs, no dice. Think thats it. Odd, the same OS runs off my USB stick without a hitch. Can't figure that one out, but I give up

The MX Live system runs in ram only which is why it seems to work. But when you try to access the HDD, it crashes so it seems obvious that the HDD is the problem.

Posted: **Fri Feb 21, 2025 12:18 pm**

@bcreighton

Nope, they're not related to any hdd / ssd issues, nothing to worry, even ignorable.

A Bios update might solve such issues when available. Or:

Kermit the Frog wrote: Thu Nov 28, 2024 8:14 am
oliverjames wrote: Thu Nov 28, 2024 5:25 am... a number of ACPI error messages ...
... you can add
Code: Select all
loglevel=3
in kernel parameters box in "MX Boot Options".
https://www.kernel.org/doc/Documentation/admin-guide/kernel-parameters.txt wrote:
Code: Select all
	loglevel=	[KNL,EARLY]
			All Kernel Messages with a loglevel smaller than the
			console loglevel will be printed to the console. It can
			also be changed with klogd or other programs. The
			loglevels are defined as follows:

			0 (KERN_EMERG)		system is unusable
			1 (KERN_ALERT)		action must be taken immediately
			2 (KERN_CRIT)		critical conditions
			3 (KERN_ERR)		error conditions
			4 (KERN_WARNING)	warning conditions
			5 (KERN_NOTICE)		normal but significant condition
			6 (KERN_INFO)		informational
			7 (KERN_DEBUG)		debug-level messages
i.e. loglevel=0 will print emergency messages only (when system is about to crash or is unstable).

In fact quiet is the equivalent of loglevel=4 that's why the system lets the "warning" messages be printed. By the way, no matter you use loglevel 3 or less they're still recorded in log files (in case one needs to search/inquire something). You can also change the splash to nosplash if you prefer the flowing text (like me) but you don't have to.

You can also try (add) the:

Code: Select all

intremap=off

parameter.

Posted: **Fri Feb 21, 2025 1:22 pm**

In my opinion your hard-disk will be dead soon. I had the same troubles under Fedora 40: freeze, boot error etc. : the reason was my hard-disk had reached its end of life. Replace your hard-disk with an SSD and your troubles will fly away.

Posted: **Sat Feb 22, 2025 1:48 pm**

interesting in QSI 'Kernel version is 6.1.0-30" and shows MX-23.5 to which does not its default Kernel booted is 6.12.8-1 (think a progression upgrade and not fresh install.)
another thought seeing "DMA Read NO_PASID" 1st entry start top of pg.
Looks like a corrupt boot strap is a thought. or something gone corrupt.

Tip to Question: Can you load or boot your original "MX-Live"Flash stick from here perform an "FSCK" on the internal hard drive to check its integrity. it will not be mounted

DMA read Direct Memory Address - something is caught in a "bit-lock or loss of data" crc error ? (bad memory stick? / lower voltages?)

eg: of a command line fsck check knowing your drive sudo blkid -o list ; or simply sudo blkid change /dev/sda1 for your own drive this is simply an example to cmdline use
sudo fsck -t ext4 -y -f -c /dev/sda1

this may shed some light. So back up a few step -do not click on drive in thunar- fsck must be performed on an unmounted drive. where by MX-Live-Flash boot is essential to cover 2 tests. does it work, then open an xfce4 terminal shell and issue the above sudo fskc -t ext4 -y -f -c /dev/sdxyz-1 fill in your appropriate info shown in blkid. keeping in line with dolphins 1st suggestion.
last of last . Perform a RTC reset on your bios and reset the mother board defaults.

Posted: **Sat Feb 22, 2025 2:02 pm**

Maybe try (especially the /home partition, or each partitions ext4) ... I already had this problem before (due to a nvidia card and the firefox .cache)

Code: Select all

lsblk -f
e2fsck -Dyf /dev/sda##

Posted: **Fri Mar 07, 2025 11:14 am**

Sorry for the long delay in replying. But, I bought a new hard drive to try out and had to wait for its arrival and then time to do the install. Unfortunately, during the process of removing the monitor I nicked an edge, enough to pretty much ruin the monitor. sigh. So, I bought a newer toughbook, since they are supposed to be Linux friendly. Fortunately, I had snapshot and MX Live USB Maker (BIG thank you to MX for developing this!), so I installed my system onto the laptop. No more problems. Perhaps it was the hard drive.

Thank you to everyone who tried to assist me.

Well, no more original problems. The only issue I have now is that the external monitor, connected through hdmi, only worked when installed Nvidia drivers, and then as DP-1 instead of HDMI, and then, whenever the screen goes to sleep I typically cannot reactivate it. Sometimes, seemingly randomly, it turns itself back on. In all honesty, I'm using an older TV. xrandr --output DP-1 --auto doesn't seem to work. In fact, DP-1 shows as not even connected. If I reboot or log back in, it turns back on. Very odd, but this is a separate thread I recognize. I guess I don't care enough to post it on a new thread.

Anyway, thanks to all.

Posted: **Fri Mar 07, 2025 5:16 pm**

abra -cadabra new hardware is always a fun prospect to consider , Out with the older hardware.

you could always keep this older hardware replace the drive and use as a backup. food for thought.. Nice to see you are a happy camper again.

Posted: **Fri Mar 07, 2025 5:28 pm**

@bcreighton Please mark this topic as solved and if you need / want to open a new topic on the new machine and screen issues please do.

MX Linux Forum

boot error

boot error

Re: boot error

Re: boot error

Re: boot error

Re: boot error

Re: boot error

Re: boot error

Re: boot error

Re: boot error

Re: boot error

Re: boot error

Re: boot error

Re: boot error

Re: boot error

Re: boot error

Re: boot error

Re: boot error

Re: boot error

Re: boot error

Re: boot error

Re: boot error

Re: boot error

Re: boot error

Re: boot error

Re: boot error

Re: boot error

Re: boot error

Re: boot error

Re: boot error

Re: boot error

Re: boot error

Re: boot error

Re: boot error

Re: boot error

Re: boot error