HELP!!! J6412 Elkhart Lake miniPC install freeze

[lxrootard]

Hello

I'm experiencing issues to install Proxmox 7.2 on a new J6412 Celeron miniPC with integrated graphics.
The install freezes just after starting X11 and pressing CTL-ALT-F1 or F2 does not work, see screenshot and dmesg attached.
I see a call trace line 690:
[ 2.490101] BUG: kernel NULL pointer dereference, address: 0000000000000000 [ 2.490904] #PF: supervisor read access in kernel mode [ 2.491672] #PF: error_code(0x0000) - not-present page [ 2.492431] PGD 0 P4D 0 [ 2.493205] Oops: 0000 [#1] SMP NOPTI [ 2.493971] CPU: 2 PID: 688 Comm: modprobe Not tainted 5.15.30-2-pve #1 [ 2.494736] Hardware name: Default string Default string/Default string, BIOS 5.19 05/10/2022 [ 2.495521] RIP: 0010:strcmp+0xc/0x20 [ 2.496313] Code: 06 49 89 f8 48 83 c6 01 48 83 c7 01 88 47 ff 84 c0 75 eb 4c 89 c0 c3 0f 1f 80 00 00 00 00 31 c0 eb 08 48 83 c0 01 84 d2 74 0f <0f> b6 14 07 3a 14 06 74 ef 19 c0 83 c8 01 c3 31 c0 c3 66 90 48 89 [ 2.498843] RSP: 0018:ffffb366404dba20 EFLAGS: 00010246 [ 2.499697] RAX: 0000000000000000 RBX: 0000000000000000 RCX: ffffb366404db9d0 [ 2.500553] RDX: 0000000000000000 RSI: ffffffffc0257c93 RDI: 0000000000000000 [ 2.501400] RBP: ffffb366404dba48 R08: 0000000000000000 R09: ffffb366404db7c8 [ 2.502247] R10: ffff906c4e8ff4c0 R11: ffff906fafeb1080 R12: ffffffffc0259c40 [ 2.503084] R13: ffffffffc025b0e0 R14: 0000000000000000 R15: ffffffffc025b140 [ 2.503918] FS: 00007f7088994540(0000) GS:ffff906faff00000(0000) knlGS:0000000000000000 [ 2.504736] CS: 0010 DS: 0000 ES: 0000 CR0: 0000000080050033 [ 2.505544] CR2: 0000000000000000 CR3: 000000010ed8e000 CR4: 0000000000350ee0 [ 2.506338] Call Trace: [ 2.507099] <TASK> [ 2.507836] ? intel_pinctrl_get_soc_data+0x67/0xc0 [ 2.508583] intel_pinctrl_probe_by_uid+0x13/0x30 [ 2.509315] platform_probe+0x46/0xc0 [ 2.510062] really_probe+0x21b/0x420 [ 2.510791] __driver_probe_device+0x115/0x190 [ 2.511530] driver_probe_device+0x23/0xc0 [ 2.512264] __driver_attach+0xbd/0x1d0 [ 2.512998] ? __device_attach_driver+0x110/0x110 [ 2.513728] bus_for_each_dev+0x7c/0xc0 [ 2.514453] driver_attach+0x1e/0x20 [ 2.515181] bus_add_driver+0x135/0x200 [ 2.515893] driver_register+0x91/0xf0 [ 2.516614] ? 0xffffffffc020c000 [ 2.517308] __platform_driver_register+0x1e/0x20 [ 2.517990] ehl_pinctrl_driver_init+0x1c/0x1000 [pinctrl_elkhartlake] [ 2.518669] do_one_initcall+0x46/0x1d0 [ 2.519336] ? kmem_cache_alloc_trace+0x19e/0x2e0 [ 2.520004] do_init_module+0x52/0x280 [ 2.520669] load_module+0x2613/0x2a00 [ 2.521334] __do_sys_finit_module+0xbf/0x120 [ 2.522002] __x64_sys_finit_module+0x1a/0x20 [ 2.522642] do_syscall_64+0x59/0xc0 [ 2.523279] ? exit_to_user_mode_prepare+0x37/0x1b0 [ 2.523896] ? syscall_exit_to_user_mode+0x27/0x50 [ 2.524488] ? __x64_sys_lseek+0x1a/0x20 [ 2.525063] ? do_syscall_64+0x69/0xc0 [ 2.525627] ? exc_page_fault+0x89/0x160 [ 2.526181] ? asm_exc_page_fault+0x8/0x30 [ 2.526730] entry_SYSCALL_64_after_hwframe+0x44/0xae [ 2.527284] RIP: 0033:0x7f7088ab59b9 [ 2.527824] Code: 00 c3 66 2e 0f 1f 84 00 00 00 00 00 0f 1f 44 00 00 48 89 f8 48 89 f7 48 89 d6 48 89 ca 4d 89 c2 4d 89 c8 4c 8b 4c 24 08 0f 05 <48> 3d 01 f0 ff ff 73 01 c3 48 8b 0d a7 54 0c 00 f7 d8 64 89 01 48 [ 2.529520] RSP: 002b:00007ffde4e142b8 EFLAGS: 00000246 ORIG_RAX: 0000000000000139 [ 2.530105] RAX: ffffffffffffffda RBX: 000055a2428a4cf0 RCX: 00007f7088ab59b9 [ 2.530689] RDX: 0000000000000000 RSI: 000055a241af2260 RDI: 0000000000000003 [ 2.531290] RBP: 0000000000040000 R08: 0000000000000000 R09: 000055a2428a66e0 [ 2.531881] R10: 0000000000000003 R11: 0000000000000246 R12: 000055a241af2260 [ 2.532471] R13: 0000000000000000 R14: 000055a2428a4e10 R15: 000055a2428a4cf0 [ 2.533061] </TASK>

Could you please help?

Thanks

 

[lxrootard]

Hi there
Any hints??

 

[lxrootard]

Up! Help anyone?

 

[lxrootard]

I’m surprised no expert on this forum commented my issue?
Elkhart Lake is pretty new but I see similar problems with Alder Lake that is not supported.

I won’t need graphics as this machine will be used as a domotics server.
Is there any workaround such as a headless install mode or do I forget ProxMox??

 

[Lixe]

Funktioniert eine Debian-Installation? Du kannst Proxmox dann auf der Debian-Installation durchführen.

https://pve.proxmox.com/wiki/Install_Proxmox_VE_on_Debian_11_Bullseye

 

[lxrootard]

Still investigating... looks like I'm not the only one
Not sure the problem is exactly the same but I can't change the network adapter as it's built-in and the NUC has no extension capabilities...

 

[LnxBil]

I’m surprised no expert on this forum commented my issue?

The only suggestion you will get from an experienced new hardware user is: wait. New hardware implies always new problems, which will (most probably) be solved in the future. You may have to wait until the patches are incorporated into the Ubuntu kernel though.

I would also love to get my hand on a shiny new elkhart lake piece, but I wait. Also, this is the lowest end of hardware for general virtualization platforms, so it will not be the focus of any development (neither PVE nor Linux).