Is your feature request related to a problem? Please describe
Somewhat -- KIAUH installs klipper as a systemd service, but the klipper docs for installing the rpi-mcu virtual linux MCU have it started as an init.d service and also note that the rpi-mcu process must be started before the klipper service. Given this, it seems it would make sense to have the rpi-mcu process also started as a systemd unit. One possible way to accomplish this would be to have KIAUH have an helper to install the rpi-mcu process, bypassing the klipper doc install process.
Describe the solution you'd like
Have KIAUH handle the klipper rpi-mcu install process, substituting a systemd unit for the klipper-bundled init.d script.
Alternatively (possibly better?) I may be able to write a systemd unit option and contribute it directly to klipper. This still might benefit from some support for installation in KIAUH.
Describe alternatives you've considered
Install init.d starter for rpi-mcu process; figure out how init.d / systemd startup sequencing works
Write and test systemd unit for rpi-mcu process starting & submit it as a PR to Klipper, along with relevant documentation changes to call it out as an option.
Is your feature request related to a problem? Please describe
Somewhat -- KIAUH installs klipper as a systemd service, but the klipper docs for installing the rpi-mcu virtual linux MCU have it started as an init.d service and also note that the rpi-mcu process must be started before the klipper service. Given this, it seems it would make sense to have the rpi-mcu process also started as a systemd unit. One possible way to accomplish this would be to have KIAUH have an helper to install the rpi-mcu process, bypassing the klipper doc install process.
Describe the solution you'd like
Describe alternatives you've considered
Additional information
No response