Yes, that's right.

You don't need to enter any commands at all, just select rescue mode from the "Advanced Options" sub-menu and follow the prompts to open a shell in the installed system.

See also https://www.debian.org/releases/stable/ … 06.en.html

Once you're chrooted into the installed system you can install the pastebinint package and use that to upload the command output to Debian's pastebin service so you can just share the URL here rather than transcribe it. See the manpage for details.

So hd2 is the Mac drive then?

What does set say about the root & prefix?

If you have a live ISO image handy can you post the output of

efibootmgr -v
parted --list

There are several kernel modules that provide the firewall functionality but the init script (or systemd unit file) is needed to load the user space process that actually runs the firewall.

Bloat!

$ ls -l /bin/ed
-rwxr-xr-x 1 root root 55368 Jan 19 07:39 /bin/ed
$ ls -l /bin/tee
-rwxr-xr-x 1 root root 39080 Mar  6  2020 /bin/tee
$

You need to set the partition as the root rather than the entire device.

Use

ls (hd2,gpt1)
ls (hd2,gpt2)
ls (hd2,gpt3)

Are the kernel & initramfs image (symlinks) listed in the output of any of those commands?

Use the ls command to view all of the attached disks and their partitions and use (for example)

ls (hd0,1)

^ That will show the content of the first partition on the first hard drive.

Once you find vmlinuz & initrd.img set that partition as the root, for example

set root=(hd0,1)

Then declare the location of the kernel, root partition (presumed to be /dev/sda1 for this example, edit that bit if it's elsewhere) & initramfs image and boot the system:

linux /vmlinuz root=/dev/sda1
initrd /initrd.img
boot

Once the system is booted then run this command for a non-UEFI system (be sure to choose the block device rather than a partition when asked):

# dpkg-reconfigure grub-pc

Or this command for a UEFI system:

# dpkg-reconfigure grub-efi-amd64

The grub> prompt indicates that /boot/grub/grub.cfg cannot be found, reconfiguring the relevant GRUB package should fix that.

If you're curious then you can use the set command (with no options) to find out where GRUB is looking for the configuration file.

I can't load pcc_cpufreq unless acpi_cpufreq is also loaded so I don't think they can be used independently but this is just a guess. I can't really understand the official documentation.

How did you determine that Slackware system uses pcc instead of acpi?

And btw:

Useless use of cat:

grep _cpufreq /proc/modules

Amazing performance from SRV — better than Hendrix?

For me: Carter USM, Post Historic Monsters.

You could try blocking the acpi_cpufreq module from the GRUB menu by pressing "e" with the Devuan entry highlighted then add this to the end of the line that starts with "linux":

module_blacklist=acpi_cpufreq

Then press <ctrl>+x (at the same time) to boot the modified entry and use this to check if pcc_cpufreq is being used:

cpupower frequency-info # supplied by the linux-cpupower package

If that works then either add the kernel parameter to GRUB_CMDLINE_LINUX in /etc/default/grub and run update-grub or use https://wiki.archlinux.org/index.php/Ke … probe.d/_2 to block it permanently.

http://deb.devuan.org/devuan/zzz-dists/ shows the last repository update as this morning so you should probably both share your sources — which mirrors are you using?

Have you installed the amd64-microcode package?

https://pkginfo.devuan.org/cgi-bin/poli … e&q=stress