No HDMI video home assistant blue (odroid n2) on 9.0rc2

[irakhlin]

Describe the issue you are experiencing

After upgrading to 9.0rc2 the odroid n2 (ha blue) will display the initial uefi boot screen, but the display will turn off after that point on. Home assistant continues to boot and function normally and has been up without issue for over 24 hours. I have tried starting it with the display connected and without to connect it after boot but this does not seem to make a difference. Based on the logs it seems like this is similar to #1994

What operating system image do you use?

odroid-n2 (Hardkernel ODROID-N2/N2+)

What version of Home Assistant Operating System is installed?

9.0rc2

Did you upgrade the Operating System.

Yes

Steps to reproduce the issue

Boot the system normally or restart

Anything in the Supervisor logs that might be useful for us?

Nothing jumps out

Anything in the Host logs that might be useful for us?

[    0.000000] Booting Linux on physical CPU 0x0000000000 [0x410fd034]
[    0.000000] Linux version 5.15.65 (builder@bb40ed55f6ed) (aarch64-buildroot-linux-gnu-gcc.br_real (Buildroot -g5468d36a2) 9.4.0, GNU ld (GNU Binutils) 2.36.1) #1 SMP PREEMPT Thu Sep 8 11:59:34 UTC 2022
[    0.000000] Machine model: Hardkernel ODROID-N2Plus
[    0.000000] efi: UEFI not found.
[    0.000000] OF: fdt: Reserved memory: failed to reserve memory for node 'secmon@5000000': base 0x0000000005000000, size 3 MiB
[    0.000000] Reserved memory: created CMA memory pool at 0x00000000e4c00000, size 256 MiB
[    0.000000] OF: reserved mem: initialized node linux,cma, compatible id shared-dma-pool
[    0.000000] NUMA: No NUMA configuration found
[    0.000000] NUMA: Faking a node at [mem 0x0000000000000000-0x00000000f4e5afff]
[    0.000000] NUMA: NODE_DATA [mem 0xe4652100-0xe4653fff]
[    0.000000] Zone ranges:
[    0.000000]   DMA      [mem 0x0000000000000000-0x00000000f4e5afff]
[    0.000000]   DMA32    empty
[    0.000000]   Normal   empty
[    0.000000] Movable zone start for each node
[    0.000000] Early memory node ranges
[    0.000000]   node   0: [mem 0x0000000000000000-0x00000000052fffff]
[    0.000000]   node   0: [mem 0x0000000005300000-0x00000000072fffff]
[    0.000000]   node   0: [mem 0x0000000007300000-0x00000000f4e5afff]
[    0.000000] Initmem setup node 0 [mem 0x0000000000000000-0x00000000f4e5afff]
[    0.000000] On node 0, zone DMA: 12709 pages in unavailable ranges
[    0.000000] psci: probing for conduit method from DT.
[    0.000000] psci: PSCIv1.0 detected in firmware.
[    0.000000] psci: Using standard PSCI v0.2 function IDs
[    0.000000] psci: MIGRATE_INFO_TYPE not supported.
[    0.000000] psci: SMC Calling Convention v1.1
[    0.000000] percpu: Embedded 20 pages/cpu s43160 r8192 d30568 u81920
[    0.000000] pcpu-alloc: s43160 r8192 d30568 u81920 alloc=20*4096
[    0.000000] pcpu-alloc: [0] 0 [0] 1 [0] 2 [0] 3 [0] 4 [0] 5 
[    0.000000] Detected VIPT I-cache on CPU0
[    0.000000] CPU features: detected: ARM erratum 845719
[    0.000000] Built 1 zonelists, mobility grouping on.  Total pages: 987425
[    0.000000] Policy zone: DMA
[    0.000000] Kernel command line: zram.enabled=1 zram.num_devices=3 apparmor=1 security=apparmor systemd.machine_id=e101b31c4c604ac5abb84b93a7e71899 cgroup_enable=memory fsck.repair=yes root=PARTUUID=48617373-06 rootfstype=squashfs ro rootwait rauc.slot=A console=tty0 console=ttyAML0,115200n8
[    0.000000] Unknown kernel command line parameters "cgroup_enable=memory", will be passed to user space.

System Health information

No response

Additional information

No response

[agners]

This is fixed with #2128 and will be part of 9.0.