Kernel panic on booting ISO on Intel 125H

[GiorgioAresu]

Hello, I just got a new node for my cluster, a Minisforum UH125 Pro (based on Intel Core Ultra 125H), but can't get talos to boot on the thing.
I tried both the secureboot ISO and the normal one, with and without the intel extensions (i915, intel-ucode, mei, thunderbolt), the result I get is a panic right after the sidero logo is shown, with the only lines shown being:

EFI stub: Loaded initrd from LINUX_EFI_INITRD_MEDIA_GUID device path
EFI stub: Measured initrd data into PCR 9

Then it reboots.

Same thing with v1.9.6.

I have tpm enabled (I assume this doesn't make a difference, but still tried it without it, earlier), SR-IOV on (was off by default, doesn't seem to make a difference either). Can't find any option to force legacy non-UEFI boot in the bios.
I tried kernel arguments from onedr0p's repo (https://github.com/onedr0p/home-ops/blob/main/talos/controlplane.yaml.j2) as he has the same CPU though on a different system. Removing console=tty0 as per #9168 (reply in thread) didn't work

Any ideas? Is there a way to get more logs or hints out of it, despite it not making it to the actual booting part?
Thanks

[frezbo]

Could you try with the normal iso, secureboot off and upload some info about the panic message?

[GiorgioAresu]

It reboots if I don't put panic=0, which should just get it to stop rebooting automatically on kernel panics.
Both with the default console=tty0 and without it, it doesn't make a difference. No difference with earlycon either. Yes I'm adding them from the boot menu, I tried with custom ISOs earlier to add the intel extensions, but those didn't work either.

[frezbo]

you'd need to figure what's the console arguments for the hardware, nothing we can help without a panic message

[GiorgioAresu]

Proxmox and Ubuntu boot fine with the default kernel parameters, which are very basic: Proxmox 8.4 uses BOOT_IMAGE=/boot/linux26 ro ramdisk_size=16777216 rw quiet splash=silent but it has like 30 drivers. I'm not familiar with this so bear with me, is it possible it's missing drivers? Is it reasonable to try with a custom image with all extensions and if that works finding out which ones are needed?

[GiorgioAresu]

Nevermind, I went through the extensions list again, there's nothing else related to this hw

[GiorgioAresu]

Just an update, for now I ended up installing proxmox and virtualizing talos on it just for this single node, as I think the only way forward would be to troubleshoot initrd and kernel images, on which I don't have any knowledge (and can't invest the time as of now). I'm available to try any suggestion on it though, as doing so just requires a reboot and I'd rather run it bare-metal if I can