MX Linux Forum

dolphin_oracle wrote: ↑Sat Apr 12, 2025 8:41 pm so building the dkms packages for three kenrels is going to take a while.

run the dpkg --configure -a command and let it finish.

Hi Dolphin -

You are right - guess this computer is pretty slow.

Thank you!

Hi- Today's update was stalled at 82%, while I assume involved kernels - "depmod" or something. Long ago, as I did not want kernels to update and had uninstalled: linux-image-amd64 meta-package linux-headers-amd64 And this is likely why the update issue stalled. Went to reinstall them to get past ...

fehlix -

Yes, I will mark it solved and re-visit if I find other issues.

Thank you again for your help!

fehlix-

Thank you for all the time and effort you put in to this - I appreciate it!

Thank you fehlix- Hope this is correct. (Can't edit grub entries without grub-customizer - tried many times from MX posts, arch and other different sources. Failed miserably...) Wiped everything from the second drive - only swap, MX, antiX, and antiX on the main drive and nothing else on the laptop ...

If my experimenting has not led me astray, I have discovered that removing Windows 10 operating system from the computer stopped it from booting to the "initramfs" TTY in the added operating systems, but did not stop the "begin:running/scripts/local- block" script on boot. It was not just Win 10 ...

fehlix- After removing Windows completely, and updating initramfs, same problem. Loading the now empty internal auxiliary m.2 with three antiX versions (base, sysVinit, runit-full), and MX as fourth selection, boots perfectly to every one with antiX as the boot controller. Wiped the main drive with ...

Snapshot created on: 20231026_0109 System: Kernel: 6.1.0-12-amd64 [6.1.52-1] arch: x86_64 bits: 64 compiler: gcc v: 12.2.0 parameters: quiet splash lang=en_US kbd=us tz=America/New_York 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 ...

Thank you fehlix - I think I had mislead you. The initramfs TTY screen appears when I try to boot from a selection of antiX on the menu, but it boots to MX itself with no issues, just the menu selections of the multi-boot. Should I gather the QSI, lsblk -f and parted --list from MX that is installed ...

Hi fehlix- I had been multi-booting MX with antiX and sometimes Windows (which I might remove from this computer in case it is the problem - it is on another disk presently). Before the block-scripts started showing up, I would just revert-save and make sure none of the other installations were set ...