Arch Linux User Repository

cgroup v1 is deprecated as of now and my pc is not booting anymore with the required parameter. I am downgrading systemd for the moment, but we need a solution for this problem rather soon. From the systemd changelog (version 256):

Support for cgroup v1 ('legacy' and 'hybrid' hierarchies) is now considered obsolete and systemd by default will refuse to boot under it. To forcibly reenable cgroup v1 support, SYSTEMD_CGROUP_ENABLE_LEGACY_FORCE=1 must be set on kernel command line. The meson option 'default-hierarchy=' is also deprecated, i.e. only cgroup v2 ('unified' hierarchy) can be selected as build-time default.

You need to add systemd.unified_cgroup_hierarchy=false in your kernel parameters.

Read more at: https://wiki.archlinux.org/title/Kernel_parameters

https://terms.archlinux.org/docs/code-of-conduct/#arch-linux-distribution-support-only

ARM arch. is also supported (for exam. I using ARCH on ARM CPU)
https://archlinuxarm.org/

@adrian.chmiel, archlinux only support x86_64. When running on a x86_64 arch, the correct machine is selected. The machine is something different than uname -m.

Thanks @rokam, regarding MACHINE, "uname -m" always will return architecture of system.
If we use env. variable then maybe better to use something like that?
echo $MACHINE

@adrian.chmiel fixed the systemd-journal-gatewayd.socket, it was my mistake to create hassio-journal-gatewayd.socket. Now the script edits the systemd-journal-gatewayd.socket to add the listenstream file used by docker. There was no need to install a package because systemd-journal-gatewayd is part of systemd.

About the machine, in your case you need to set the MACHINE env var before installing.

eg.:

$ export MACHINE=raspberrypi3-64

I moved the check arch and machine to pre_install step. (The original deb installer does it in the post_install fase)

@rokam, if I'm not mistake, this version requires worked systemd-journal-remote (probably for remore control).
hassio-journal-gatewayd.socket requires systemd-journal-gatewayd which one require and libmicrohttpd package(it is not included now in the installation reuire list)
But we cannot start hassio-journal-gatewayd.socket bcause:
hassio-journal-gatewayd.socket: Socket service hassio-journal-gatewayd.service not loaded, refusing.

Moreover, if I have different machine that on the list, files is copped but the installation procedure stopped, even though RP3 is listed.

In my opinion, if they shoundn't install the package on a platform other than one on the list, it should check it first and return the error of platform not supported and stop the procedure.
Now they copies the files and leaves them unconfigured.

In line 140 should be "*)"?

Regarding MACHINE, if we have RP3, they "uname -m" return aarm64, then the script will not put information about MACHINE and check_machine() function will done with "exit 1".
Currently in my opinion the install script only supports x86 architecture, any other ends with "exit 1".

@adrian.chmiel, thanks for the suggestions. The first one will be fixed, although both will work the same way. The second is incorect. MACHINE should be one of the following:

• generic-x86-64
• odroid-c2
• odroid-n2
• odroid-xu
• qemuarm
• qemuarm-64
• qemux86
• qemux86-64
• raspberrypi
• raspberrypi2
• raspberrypi3
• raspberrypi4
• raspberrypi3-64
• raspberrypi4-64
• tinker
• khadas-vim3

That's why we have a check_machine function in the install script.

@rokam, there is a bug in .INSTALL: (line 47)
sed -i "s,%%HASSIO_CONFIG%%,${CONFIG},g" "${PREFIX}"/bin/hassio-supervisor

Should be:
sed -i "s,%%HASSIO_CONFIG%%,${CONFIG},g" "${PREFIX}/bin/hassio-supervisor"

"is in the wrong place
This is the reason why Martynvandijke60 had problems

Supervisor cannot download docker package, when MACHINE is not specified: (from line 119)
"arm" |"armv6l")
MACHINE=${MACHINE:=armhf}
HASSIO_DOCKER="${DOCKER_REPO}/armhf-hassio-supervisor"
;;
"armv7l")
MACHINE=${MACHINE:=armv7}
HASSIO_DOCKER="${DOCKER_REPO}/armv7-hassio-supervisor"
;;
"aarch64")
MACHINE=${MACHINE:=aarch64}
HASSIO_DOCKER="${DOCKER_REPO}/aarch64-hassio-supervisor"
;;
*)


Next thing, in my opinion is better to check
systemd.unified_cgroup_hierarchy=false
in /proc/cmdline, rarely on ARM platforms there is something in /boot

What problem is if I update ha e supervisor but not package homeassistant-supervised?

@simona, you can create a full backup and then restore it after package installation. The "migration" process will need a lot of tweeks.