Computer failure troubleshooting on MX Linux after formatting

Other Distributions
41

That means it could not upgrade the kernel. This is very strange.
I have seen similar dpkg errors, but those were with packages I made myself, and I screwed somethin up while creating those packages.
So I think, the packages were corrupted, maybe while downloading.

Try to run

sudo apt clean
sudo apt update
sudo apt upgrade

and see what happens?

1 Like
42

Thanks, @callpaul.eu I thought about that, but figured maybe it was made in California USA (that was the timezone in BIOS after it reset). But once I changed it in BIOS it has stayed. And now that I changed it in Debian, it has also stayed after reboot.

It is a simple to access area to replace CMOS, so I will have to pick one up as I don’t think I have that flat battery at home just now.

Sheila

1 Like
43

Same thing. update has no issues. It is upgrade that returned the same error as before for package linux-image-amd64

Also dpkg: dependency problems prevent configuration of linux-image-amd64:

And that is because of the repeat of error in processing linux-image-6.1.0-31-amd64.

So something is still not right. I am unsure of the latest version of Debian 12, but my flash drive had both 12.5 and 12.7, I installed 12.7. So that is probably why it is trying to upgrade.

12.7 currently is using 6.1.0-25-amd64

One other thing, it was at lunch that I said above that I had 433.8 GB used–I meant “free.” I booted up after work and tried the upgrade and now it reports 434.4 GB free. And after installing barrier and upgrading, stil reports 431.1 GB free. If it continues to work and has no further issues like continuous errors filling up logs/drive space, I think it might be assumed that the Nvidia card itself or the PCIe slot holding it was the issue.

UPDATE: I went in and uncommented the “amend” in grub and then installed Barrier. Watching the output, it said it found the image for 6.1.0-31-amd64. So I rebooted after and now uname -r shows it is using that version.

Sheila

2 Likes
44

You might take a look at the Debian systemd logs

1 Like
45

Try updating dpkg

1 Like
46

Thanks, but it already updated the kernel so am now on the 6.1.0-31 vs the 6.1.0-25 in use at install. Now from GRUB Advanced it has both.

No errors in updating or upgrading now and the log errors are things related to other things I installed. For instance, I installed the budgie desktop and it deleted pulseaudio and installed pipewire. So something else looks for pulseaudio and cannot find it. Not worried about those type of errors as once I see that everything is running fine, I intend to reinstall MX; so probably give it till next week to see that there are no other hardware issues and will do a fresh install.

Sheila

3 Likes