ASUS NUC 14 Pro will not boot

[tane64]

Describe the issue you are experiencing

Home Assistant OS 12.4 Will not boot on a new ASUS NUC 14
Booting ‘Slot A (OK=0 TRY+0)

System will freeze after that

What operating system image do you use?

generic-x86-64 (Generic UEFI capable x86-64 systems)

What version of Home Assistant Operating System is installed?

12.4

Did the problem occur after upgrading the Operating System?

No

Hardware details

Asus NUC 14 Pro Intel 125, 16 GB Memory 4 TB SSD NVME

Steps to reproduce the issue

Fresh install

Ubuntu and Proxmox will install and boot fine.

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

no

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

Botsing ‘Slot A (OK=0 TRY+0)

System  Will freeze

System information

No response

Additional information

No response

[sairon]

Can you please test if the latest dev build (as of today) boots correctly? Could be fixed by 63a05a5.

[tane64]

Same result. Will not boot
After Booting Slot A system will freeze

[sairon]

If there nothing else shown after selecting the boot slot, GRUB is likely failing to load kernel. It can be a bug in the UEFI firmware or GRUB itself. HAOS 12.2 brought GRUB 2.12 that hasn't made it way into most of the current mainstream distros, and for example in case of Ubuntu, it's heavily patched. Can you please also check if HAOS 12.1 doesn't behave differently by any chance?

[tane64]

Same result with HAOS 12.1
Also downgraded the Bios firmware to
38
39
41
42
43

All same result after after GRUB menu it will freeze

[riemers]

Playing with these settings made it boot on my side. In particular the intel VT for directed I/O (VT-d) needs to be unticked. I have verified this with opmised bios settings, then disabling secure boot and unticking above named item.

[sairon]

Nice find, @riemers! Although toggling VT-d shouldn't make any difference if HAOS boots or not, disabling it doesn't do any harm, because HAOS doesn't make any use of it. Disabling secure boot is mandatory though.

[riemers]

True, although other operating systems boot up just fine.. so i am still pretty sure its something to do with the boot in the current HAOS but will be eventually be updated by mainstream one would say. At least there is a work around.

p.s. you can close the ticket (i instructed tane64 and it works on his side)

[sairon]

Unfortunately, without the device on hand, it's shooting in the dark. It could also be the other way, because HAOS already uses GRUB 2.12 bootloader, which is not yet in most of the others (or not heavily unpatched).

The only other idea I have right now is to check if it really fails to boot or just the graphics driver doesn't correctly initialize. To test that, re-enable the BIOS option and check if HA become reachable after some time.

[riemers]

Thought about that too, but never noticed an ip after longer waiting. Also the keyboard locks up too. So for example caps lock lights don’t work anymore either.

…

________________________________ Van: Jan Čermák ***@***.***> Verzonden: Thursday, August 8, 2024 1:27:07 PM Aan: home-assistant/operating-system ***@***.***> CC: Erik-jan Riemers ***@***.***>; Mention ***@***.***> Onderwerp: Re: [home-assistant/operating-system] ASUS NUC 14 Pro will not boot (Issue #3474) Unfortunately, without the device on hand, it's shooting in the dark. It could also be the other way, because HAOS already uses GRUB 2.12 bootloader, which is not yet in most of the others (or not heavily unpatched). The only other idea I have right now is to check if it really fails to boot or just the graphics driver doesn't correctly initialize. To test that, re-enable the BIOS option and check if HA become reachable after some time. — Reply to this email directly, view it on GitHub<#3474 (comment)>, or unsubscribe<https://github.com/notifications/unsubscribe-auth/AAFGQOL7B77JCYYUG7CZTB3ZQNIYXAVCNFSM6AAAAABK3HOVE6VHI2DSMVQWIX3LMV43OSLTON2WKQ3PNVWWK3TUHMZDENZVGU4DOMJVHE>. You are receiving this because you were mentioned.Message ID: ***@***.***>

[themajesticking]

Playing with these settings made it boot on my side. In particular the intel VT for directed I/O (VT-d) needs to be unticked. I have verified this with opmised bios settings, then disabling secure boot and unticking above named item.

OMGG I've been fighting with this for 4 hours on my NUC 14 Pro and this was the fix. I ticked/unticked the boxes in this photo and the "Booting ‘Slot A (OK=0 TRY+0)" flashed for a second and HA finally completed its first boot. Thanks!

[xeor]

Confirming this solved the exact same issue I had on NUC 14 as well. There should be a "known fixes" section in some docs somewhere :)

[Deckoz2302]

I'd argue that disabling VT-D is not a fix, as it disables the iGPU on Ultra 5 125H, making it unable to pass through the iGPU for hardware accelerated decoding of streams within Frigate Add-On.

Sure it makes home assistant OS boot, but disabling hardware for I/O pass through in the process.

[alvinchen1]

Confirming that this resolved issue getting Home Assistant installed on Bee-Link GTi14

BIOS - Press F7
Advanced - CPU Configuration - Intel (VMX) Virtualization Technology - from Enabled to Disabled
Security - Secure Boot - Secure Boot - from Enabled to Disabled
Save and Exit

[waypts]

RIEMERS POST SOLVED THIS ISSUE!!!! I had this exact problem trying to run Home Assistant on the Asus NUC 14 Pro+. I followed the Home Assistant Setup x86 Secondary Instructions. Under the BIOS Security Tab, be sure to UNCHECK the Intel VT for Directed I/O (VT-d) option. I spent hours trying to figure out why Home Assistant wouldn't run and would freeze. I appreciate Reimer's post. Home Assistant either needs to add this to their install instructions or troubleshooting notes or fix this issue. This was a pain!

Playing with these settings made it boot on my side. In particular the intel VT for directed I/O (VT-d) needs to be unticked. I have verified this with opmised bios settings, then disabling secure boot and unticking above named item.