i bought the new hardkernel odroid-m2.
tryed to boot up with the older odroid-m1 image. but it will not boot.
tryed to se if any response on HDMI , but nothing. so i think the m1 image is not the right one.
What makes you think HAOS supports odroid M2?
It’s not mentioned here:
You can try a supervised install if the odroid meets the requirements, or a container install (docker).
ok that is bad.
the board is new so i think in future it will be possible
Bold assumption.
HAOS will not support every single SBC on the market…
I was too trusting and thought it would work out.
I will put the odroid in the closet
Really hope this new board will be supported too…
STT can be 3 x time faster… impressive… Up to 16Gb of Ram… Great.
What happens if you follow the m1s instructions and install it on the m2?
Support comes by testing first 
Any logs of errors?
yes i tryed but the M2 will not boot
i found two thinks to build an debian image, to install HOASS later supervised.
but M2 Board is not yet in the List.
here is an Debian image for the M2 board.
https://ppa.linuxfactory.or.kr/images/raw/arm64/bookworm/debian-bookworm-server-odroidm2-20240902.img.xz
i personally installed it, and its booting.
Home Assistant supervised install procedere i also did and its booting.
at the moment the APPARMOR for network connetion in HOASS is not starting
we are working on it to implement it in the Kernel
apparmor is solved -
now networkmanager must be configured, HOASS has no connection
who know how to?
nmcli device
DEVICE TYPE STATE CONNECTION
lo loopback connected (externally) lo
docker0 bridge nicht verwaltet --
hassio bridge nicht verwaltet --
eth0 ethernet nicht verwaltet --
veth2144cc5 ethernet nicht verwaltet --
veth3132851 ethernet nicht verwaltet --
veth74dfc07 ethernet nicht verwaltet --
vetha39aadb ethernet nicht verwaltet --
vethd33fef0 ethernet nicht verwaltet --
vethd4ab458 ethernet nicht verwaltet --
