Dev1 Galaxy Forum / [SOLVED] Updating kexec-tools from chimaera to daedalus

Re: [SOLVED] Updating kexec-tools from chimaera to daedalus

dummy@example.com (mirrortokyo) — Wed, 01 Jan 2025 06:55:57 +0000

From what I could find on lore.kernel.org and past discussion on irc with AMD developers, the in-built GPU in APU's and newer amdgpu-using discrete GPU's have issues getting into the correct state from a kexec restart.

Re: [SOLVED] Updating kexec-tools from chimaera to daedalus

dummy@example.com (mirrortokyo) — Wed, 01 Jan 2025 02:20:34 +0000

PS, on my old machine (Pentium 4 with Radeon CEDAR discrete GPU), I was able to successfully kexec via:

kexec-load-kernel

then edited /etc/init.d/reboot to add the -k option to the reboot command line:

reboot -d -f -k ${netdown}

and just selected reboot from the lxdm desktop login screen.

Re: [SOLVED] Updating kexec-tools from chimaera to daedalus

dummy@example.com (mirrortokyo) — Wed, 01 Jan 2025 00:56:13 +0000

Tried to get kexec to work again, maybe not possible on this hardware "AMD A10-6800K APU with Radeon(tm) HD Graphics".

In single user mode, I used the kexec-load-kernel script from kexec-tools 1:2.0.29-2. That appears to work.

In the /etc/init.d/reboot script I've tried both kexec -e just before the reboot -d -f ${netdown} line and also:

reboot -d -f -k ${netdown}

which is supposed to attempt a kexec load.

Still getting a hardware reboot.

Is anyone successfully using kexec on x86_64 architecture?

Re: [SOLVED] Updating kexec-tools from chimaera to daedalus

dummy@example.com (mirrortokyo) — Wed, 14 Sep 2022 15:59:16 +0000

I'm still stuck with kexec-tools 1:2.0.20-2.1 - Debian upstream doesn't appear to have addressed this problem.

Re: [SOLVED] Updating kexec-tools from chimaera to daedalus

dummy@example.com (hagbard_) — Thu, 21 Oct 2021 20:51:17 +0000

The postinst script indeed tries to invoke the restart action, which does not exist for kexec.

Removing the following section from the postinst script seems to fix the problem.

# Automatically added by dh_installinit/13.4.1
if [ "$1" = "configure" ] || [ "$1" = "abort-upgrade" ] || [ "$1" = "abort-deconfigure" ] || [ "$1" = "abort-remove" ] ; then
if [ -z "${DPKG_ROOT:-}" ] && [ -x "/etc/init.d/kexec" ]; then
update-rc.d kexec defaults >/dev/null
invoke-rc.d kexec restart || exit 1
fi
fi
# End automatically added section
# Automatically added by dh_installinit/13.4.1
if [ "$1" = "configure" ] || [ "$1" = "abort-upgrade" ] || [ "$1" = "abort-deconfigure" ] || [ "$1" = "abort-remove" ] ; then
if [ -z "${DPKG_ROOT:-}" ] && [ -x "/etc/init.d/kexec-load" ]; then
update-rc.d kexec-load defaults >/dev/null
invoke-rc.d kexec-load restart || exit 1
fi
fi
# End automatically added section

[SOLVED] Updating kexec-tools from chimaera to daedalus

dummy@example.com (hagbard_) — Fri, 24 Sep 2021 19:31:18 +0000

That's what I get when updating kexec-tools (output after dpkg --configure kexec-tools):

Setting up kexec-tools (1:2.0.22-2+b1) ...
Error: argument 'restart' not supported
invoke-rc.d: initscript kexec, action "restart" failed.
dpkg: error processing package kexec-tools (--configure):
installed kexec-tools package post-installation script subprocess returned error exit status 1
Errors were encountered while processing:
kexec-tools

I this devuan specific, since it relates to init? Or should a bug be posted to debian (didn't find any relating to this so far)? Or is a devuan fork necessary?

"restart" seems to be weird for something that isn't a daemon.