boot error

[atomick]

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.

[oops]

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##

[bcreighton]

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.

[atomick]

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.

[CharlesV]

@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.