MX Linux Forum

I dual booted Windows 7 and ...I destroyed it about 3 times so far and reinstalled it instead of distro hopping....


Going forward might I suggest a strategy to avoid reinstalling? Personally, whenever I've had a crash (rare really but it always is a possibility), I've relied on the following:
1 ...

noursle,
This may be of value (or not). At times I've had to reinstall and the Windows menu has disappeared. What I have found success in is boot into MX. Grab from mxpi if you haven't already got it installed, Grub Customizer. Run GC and you very well may find (as I've done) the errant Windows menu ...

I should add in here the QSI for this second platform. Now, through a process of elimination, it appears to me that whenever a new init is built the problem occurs. On this occasion the file that caused the collapse was intel-microcode.
Snapshot created on: 20231112_1649
System:
Kernel: 6.5.0-1mx ...

Well ER, the contagion if I may call it that has now spread to a second platform where I run MX. Using the mxpi and just selecting upgradable packages (four were there) yielded that plethora of warnings about amdgpu files and an upgrade of the initramfs. Upon reboot I'm left at the command line and ...

Well I'm afraid I'm left in the awkward position of not being able to do a conventional/routine apt update/upgrade. This is because each time something that appears to be connected with the aforementioned missing firmware and/or the mediatek or realtek drivers, the system once rebooted loses its ...

Hello again all,
Well, I've tried siamie's suggestion of sudo apt ... etc ... I believe I'd tried that before siamhie but what you were suggesting was probably in response to a typo I'd made earlier.
Anyway, on this occasion (and this has happened before) all the 287 not upgrade were upgraded ...

That looks OK for the wi-fi, but those "287 not upgraded yet" is not good.

I'd sure like to see the terminal output of the attempted upgrade. Those firmware messages are not errors, just harmless warnings. Note that there's a "W" for warning for each, not "E".

You appear to have a combined root ...

Also, which kernel are you trying to add? Another user reported that the latest 6.1.0-35 from Debian required "nowatchdog" be added to the boot options in order to boot.


Stevo,
I have tried various kernels all resulting in issues that manifest with a non-graphical boot necessitating as I've ...

siamhie wrote: Wed May 21, 2025 7:27 am

linexer2016 wrote: Tue May 20, 2025 2:50 am if I sometimes do a sudo apt && update and sudo apt-dist upgrade, the whole thing fails again.

Try this instead

Code: Select all

sudo apt update && sudo apt upgrade 

Will do and report accordingly thanks S.

Ok here's what I tried (and have tried many times over last few months) and what has failed.
1. I've tried (various including liqorix kernels) and each time all appears to go more or less as expected EXCEPT for error message(s) pertaining to either the amdgpu or mediatek drivers.
2. Upon reboot I ...