Intel Celeron J6412 some experience?

[rodnheli]

Hello,
has anyone of you experience with an Intel Celeron J6412 processor and Proxmox? Not really something to find here in the forum
I would like to assemble something energy-saving again for home use.

VENOEN Mini PC 12th Gen In-tel J6412

My previous attempt to operate Proxmox with an N5105 unfortunately failed - you can read a long post here in the forum about the constant VM freezes.
I am currently using Proxmox with an Core i3 Gen 10 which works perfect.

Main purpose - home assistant (VM) and several containers for Wireguard, Pihole and especially Plex with transcoding (1 stream) - the J6412 should theoretically be well
positioned.I would definitely like to know if anyone is using the J6412...

Thank you very much,
Helmut

 

[Moayad]

Hi,

has anyone of you experience with an Intel Celeron J6412 processor and Proxmox? Not really something to find here in the forum

It should work with Proxmox VE, since I have similar but (Celeron J6413) and works well.

 

[rodnheli]

Great - thank you very much for your answer.
I have now ordered the minipc from the first post. Should be there tomorrow.

Elkhart Lake is perhaps a hope for the disappointed Jasper Lake buyers who wanted a low power system...

 

[bsven]

Hi,

Would be great if you can share your experience.

I tried it with an Asrock NUC Box with an J6412 and didn't got it to work.
I showed the same problem like the AMD Kernel Bug 5.13.19-2 with an Minis-Forum HX90.
3 minutes boot time and an no IP-address.
But it only to my network with a reboot of the dhclient. All workarounds with older or newer kernel versions didn't helped.

Guess the driver of the i965 graphics make some issues.

 

[rodnheli]

Unfortunately bad news!
Proxmox runs on the box - had small starting difficulties but was able to solve almost all of them.

BUT: Xubuntu VM - again frozen after about 13 hours. Home Assistant VM and LXC contaier run without problems.

In summary: apparently the same problems with Elkhart Lake as with Jasper Lake.
I'll give up for now - I've wasted too much time with the bug I also don't know where this problem could be officially attached?

 

[rodnheli]

UPDATE:

I've read on Amazon reviews that there was a BIOS update for the device - and installed it - parallel i updated the newest intel-microcode on the host...

The guest is up now for days - without problems


This week i got Odroid H3+ - let's see ...

 

[lxrootard]

Hello @rodnheli
Just curious, what's your miniPC's uptime?

I've bought this Venoen J6412 to serve as a domotics server but despite my efforts it never ran more than a week without freeze.
I've struggled for months on the same issues, see this post.
The BIOS is GEHL1104 v2.22.2 / v5.19 (already upgraded). I've also upgraded the intel firmware to 0x17 (intel-microcode/stable,now 3.20230214) and PVE to the latest release but I still get PCI errors at startup, see below.

Is your BIOS version the same than mine or newer?
If yes could you please share the download link? There's no download link on Venoen's website.
Thanks

[    0.342680] ACPI BIOS Error (bug): AE_AML_BUFFER_LIMIT, Field [IOF2] at bit offset/length 712/16 exceeds size of target Buffer (664 bits) (20220331/dsopcode-198)
[    0.342714] ACPI Error: Aborting method \_SB.PC00.UA00.BTH0._CRS due to previous error (AE_AML_BUFFER_LIMIT) (20220331/psparse-529)
[    0.342729] ACPI Error: Method execution failed \_SB.PC00.UA00.BTH0._CRS due to previous error (AE_AML_BUFFER_LIMIT) (20220331/uteval-68)
[    1.603639] pcieport 0000:00:1c.0: DPC: error containment capabilities: Int Msg #0, RPExt+ PoisonedTLP+ SwTrigger+ RP PIO Log 4, DL_ActiveErr+
[    1.604146] pcieport 0000:00:1c.1: DPC: error containment capabilities: Int Msg #0, RPExt+ PoisonedTLP+ SwTrigger+ RP PIO Log 4, DL_ActiveErr+
[    1.604625] pcieport 0000:00:1c.2: DPC: error containment capabilities: Int Msg #0, RPExt+ PoisonedTLP+ SwTrigger+ RP PIO Log 4, DL_ActiveErr+
[    1.605101] pcieport 0000:00:1c.3: DPC: error containment capabilities: Int Msg #0, RPExt+ PoisonedTLP+ SwTrigger+ RP PIO Log 4, DL_ActiveErr+
[    1.605565] pcieport 0000:00:1c.4: DPC: error containment capabilities: Int Msg #0, RPExt+ PoisonedTLP+ SwTrigger+ RP PIO Log 4, DL_ActiveErr+
[    1.606047] pcieport 0000:00:1c.6: DPC: error containment capabilities: Int Msg #0, RPExt+ PoisonedTLP+ SwTrigger+ RP PIO Log 4, DL_ActiveErr+
[    1.712864] RAS: Correctable Errors collector initialized.
[    4.944029] pcieport 0000:00:1c.2: AER: Corrected error received: 0000:00:1c.2
[    4.944041] pcieport 0000:00:1c.2: PCIe Bus Error: severity=Corrected, type=Physical Layer, (Receiver ID)
[    4.944043] pcieport 0000:00:1c.2:   device [8086:4b3a] error status/mask=00000001/00002000

$ lspci
00:00.0 Host bridge: Intel Corporation Device 4538 (rev 01)
00:02.0 VGA compatible controller: Intel Corporation Device 4555 (rev 01)
00:08.0 System peripheral: Intel Corporation Device 4511 (rev 01)
00:14.0 USB controller: Intel Corporation Device 4b7d (rev 11)
00:14.2 RAM memory: Intel Corporation Device 4b7f (rev 11)
00:16.0 Communication controller: Intel Corporation Device 4b70 (rev 11)
00:17.0 SATA controller: Intel Corporation Device 4b63 (rev 11)
00:1c.0 PCI bridge: Intel Corporation Device 4b38 (rev 11)
00:1c.1 PCI bridge: Intel Corporation Device 4b39 (rev 11)
00:1c.2 PCI bridge: Intel Corporation Device 4b3a (rev 11)
00:1c.3 PCI bridge: Intel Corporation Device 4b3b (rev 11)
00:1c.4 PCI bridge: Intel Corporation Device 4b3c (rev 11)
00:1c.6 PCI bridge: Intel Corporation Device 4b3e (rev 11)
00:1f.0 ISA bridge: Intel Corporation Device 4b00 (rev 11)
00:1f.3 Audio device: Intel Corporation Device 4b58 (rev 11)
00:1f.4 SMBus: Intel Corporation Device 4b23 (rev 11)
00:1f.5 Serial bus controller [0c80]: Intel Corporation Device 4b24 (rev 11)
01:00.0 Ethernet controller: Realtek Semiconductor Co., Ltd. RTL8111/8168/8411 PCI Express Gigabit Ethernet Controller (rev 0c)
02:00.0 Ethernet controller: Realtek Semiconductor Co., Ltd. RTL8111/8168/8411 PCI Express Gigabit Ethernet Controller (rev 0c)
03:00.0 Network controller: Intel Corporation Wireless 3165 (rev 81)
06:00.0 Non-Volatile memory controller: Samsung Electronics Co Ltd Device a809

$ pveversion
pve-manager/7.4-3/9002ab8a (running kernel: 5.19.17-2-pve)

 

[rodnheli]

Hi,
i've the same version as you GHEL 11.04 - same microcode, kernel and PVE version.
Uptime was today 12 days...

 

[Norrah]

Did you guys figure out the Issue? (or at least a way to circumvent it)
I've set my HAos to reboot every day, but it's not enough.

I'm so annoyed that my Haos keeps going into an unresponsive mode and I have to physically reboot my Proxmox each time (it's the only of my VM's that does).

I'm running my Proxmox on an Intel Celeron J6412 (Protectli VP2420, Just for others googling similar issues)