Topton Jasper Lake Quad i225V Mini PC Report

[Adrjl64]

I tried the FMI01 N5105 4L-V01 (the v3 version) BIOS from 2022-6-7 and the temps and power consumption are higher. Was hoping to get the dual nvme drive setup to work, but no result on that.

Does anyone have the BIOS version for the v3 mainboard from before 2022-6-7?

 

[cat2devnull]

Was hoping to get the dual nvme drive setup to work, but no result on that.

I couldn't get 2 x Samsung 970 Evo Plus drives to work but one Samsung and one Seagate together worked fine.
What combo won't work for you?

 

[Adrjl64]

I tried combinations with two Patriot P300’s, a Samsung 960 EVO and a Samsung 970 EVO. All combinations led to only one visible nvme drive.

Which specific Seagate drive do you use?

 

[pigr8]

anyone tried to port coreboot on those things? no eh?

 

[cat2devnull]

It's strange that it's so picky. From my server logs;

[144d:a808] 01:00.0 Non-Volatile memory controller: Samsung Electronics Co Ltd NVMe SSD Controller SM981/PM981/PM983
[N:0:4:1] disk Samsung SSD 970 EVO Plus 1TB__1 /dev/nvme0n1 1.00TB
[1bb1:5012] 02:00.0 Non-Volatile memory controller: Seagate Technology PLC FireCuda 510 SSD (rev 01)
[N:1:1:1] disk Seagate BarraCuda 510 SSD ZP1000CM3000__1 /dev/nvme1n1 1.00TB

 

[burtal]

I tried the FMI01 N5105 4L-V01 (the v3 version) BIOS from 2022-6-7 and the temps and power consumption are higher. Was hoping to get the dual nvme drive setup to work, but no result on that.

Does anyone have the BIOS version for the v3 mainboard from before 2022-6-7?

yep....temps and power re a bit higher while the CPU clocks are a bit lower....also not reaching the lower Cstates ...like C8

here are both bioses original and updated , use google traslate

http://pan.changwang.com:8888/1/main/BIOS%E7%A8%8B%E5%BA%8F/FMI01%20N5105%20JK%204L-V01%20CBOX%EF%BC%88%E7%AC%AC%E4%B8%89%E7%89%88%E9%BB%91%E8%89%B2PCB%E7%89%88%E6%9C%AC%E4%B8%93%E7%94%A8BIOS-V3%EF%BC%89

 

[Adrjl64]

It's strange that it's so picky. From my server logs;

[144d:a808] 01:00.0 Non-Volatile memory controller: Samsung Electronics Co Ltd NVMe SSD Controller SM981/PM981/PM983
[N:0:4:1] disk Samsung SSD 970 EVO Plus 1TB__1 /dev/nvme0n1 1.00TB
[1bb1:5012] 02:00.0 Non-Volatile memory controller: Seagate Technology PLC FireCuda 510 SSD (rev 01)
[N:1:1:1] disk Seagate BarraCuda 510 SSD ZP1000CM3000__1 /dev/nvme1n1 1.00TB

Thanks for the information. This mainboard seems very picky indeed. I bought my unit from HUNSN on the dutch Amazon store. The HUNSN supportdesk provided me with some information on this issue. The result was a few screenshots about a combination of a nvme drives and corresponding controllers that seemed to be compatibel, but I haven't figured out yet what the actual reason is why some drives are compatibel and some are not.

here are both bioses original and updated , use google traslate

Very much appreciated!

 

[thimplicity]

For those people experiencing pfsense guest hangs on Proxmox on the N5105/N6000 units, are you using the stock 7.2 ISO with no updates?

I had issues with pfsense on Proxmox hanging every few days. This was eventually resolved by disabling C-states in the BIOS, ensuring powerd was not enabled in pfsense, and making sure I had the latest qemu updates from Proxmox (requires a license). Since doing the combination of those three things, I have not had a hang.

Alright, moment of truth:

• I reset the BIOS settings to default
• I disabled C-States in the BIOS (this is the default setting and was also disabled before today)
• I disabled Intel ME in the BIOS (was enabled by default)
• I disabled Powerd in pfSense
• I updated proxmox incl dist-upgrade
• Temperatures have not been a problem, as I have a 120mm fan on the chassis, so everything is below 50 degrees Celcius.

Spoiler: pveversion -v

proxmox-ve: 7.2-1 (running kernel: 5.15.39-3-pve)
pve-manager: 7.2-7 (running version: 7.2-7/d0dd0e85)
pve-kernel-5.15: 7.2-8
pve-kernel-helper: 7.2-8
pve-kernel-5.15.39-3-pve: 5.15.39-3
pve-kernel-5.15.39-1-pve: 5.15.39-1
pve-kernel-5.15.30-2-pve: 5.15.30-3
ceph-fuse: 15.2.16-pve1
corosync: 3.1.5-pve2
criu: 3.15-1+pve-1
glusterfs-client: 9.2-1
ifupdown2: 3.1.0-1+pmx3
ksm-control-daemon: 1.4-1
libjs-extjs: 7.0.0-1
libknet1: 1.24-pve1
libproxmox-acme-perl: 1.4.2
libproxmox-backup-qemu0: 1.3.1-1
libpve-access-control: 7.2-4
libpve-apiclient-perl: 3.2-1
libpve-common-perl: 7.2-2
libpve-guest-common-perl: 4.1-2
libpve-http-server-perl: 4.1-3
libpve-storage-perl: 7.2-7
libspice-server1: 0.14.3-2.1
lvm2: 2.03.11-2.1
lxc-pve: 5.0.0-3
lxcfs: 4.0.12-pve1
novnc-pve: 1.3.0-3
proxmox-backup-client: 2.2.5-1
proxmox-backup-file-restore: 2.2.5-1
proxmox-mini-journalreader: 1.3-1
proxmox-widget-toolkit: 3.5.1
pve-cluster: 7.2-2
pve-container: 4.2-2
pve-docs: 7.2-2
pve-edk2-firmware: 3.20210831-2
pve-firewall: 4.2-5
pve-firmware: 3.5-1
pve-ha-manager: 3.4.0
pve-i18n: 2.7-2
pve-qemu-kvm: 6.2.0-11
pve-xtermjs: 4.16.0-1
qemu-server: 7.2-3
smartmontools: 7.2-pve3
spiceterm: 3.2-2
swtpm: 0.7.1~bpo11+1
vncterm: 1.7-1
zfsutils-linux: 2.1.5-pve1

@skimikes: Would you share your Hardware and Options tab of the pfSense VM in proxmox? The only other thing it might be for me is that you run it on different settings, e.g. BIOD vs. UEFI.

I will monitor and report back. In case skimikes settings are the same the next step is to move pfSense to bare metal. All issues here seem to be connected to the virtualization.

 

[oneplane]

anyone tried to port coreboot on those things? no eh?

Plenty of work getting done for Jasper Lake in general coreboot: src/soc/intel/jasperlake Directory Reference but no full ports besides what Protectli might have done so far.

 

[dazagrt]

Well, AliExpress has come through agreeing it's faulty and that the seller has to pay the return postage as well in this instance. The postage is going to cost them $42usd I only have to assume it's worth it for them.

Now more waiting, grrrr.

 

[thimplicity]

Well, AliExpress has come through agreeing it's faulty and that the seller has to pay the return postage as well in this instance. The postage is going to cost them $42usd I only have to assume it's worth it for them.

Now more waiting, grrrr.

Topton offered today that I ship my box back, but they did not talk about the costs. I will not ship anything back before I have the shipping costs

 

[dazagrt]

Topton offered today that I ship my box back, but they did not talk about the costs. I will not ship anything back before I have the shipping costs

My first offer was a Refund amount AU $113.53 on a cost of $227.07aud. I said no, as you would, then they came back with return & full refund, but postage at my cost, and I said no. That dragged on quite a bit until I got screenshots of it saying that it was "return at seller's cost". Finally, they approved that they would force the seller to pay the shipping costs.

I posted it express and AusPost still reckons it is going to take 25+ days to get to China.

 

[thimplicity]

My problem is, I do not see a better alternative that does not cost double and has relatively old tech in it.

 

[dazagrt]

My problem is, I do not see a better alternative that does not cost double and has relatively old tech in it.

For what use case though? as a router?

 

[pigr8]

so i finished my design and printed it, fits a 80x80x10 mm fan (i got myself a 5v one), the air vents are the same as stock, fits the stock screws plus 4 heatsunk insert to fix the fan and 2 extra m3 nuts to eventually mount the unit on the wall or something.

obviously no vesa mount possibile, can be printed in whatever material (i printed in abs) without any support just as it is.. on the other externa facing side there are 4 slots to place the original rubber feets.





a 10mm fan clears every internal component, probably a 15mm also but not sure, temps are "fine" and the enclosure is nice and fresh.
inside the zip is the stl to slice it, as said no supports needed, 10-20% infill is more than enough.

 

[PigLover]

Very nice @pigr8 !

 

[thimplicity]

For what use case though? as a router?

Yes, the idea was to use it as a router mainly, but with four VMs/containers: pfSense, pihole, homebridge, scrypted

If I need to move it to baremetal with pfSense for stability, I will survive it, but there does not seem to be a lot on the market with that form factor.

 

[thimplicity]

so i finished my design and printed it, fits a 80x80x10 mm fan (i got myself a 5v one), the air vents are the same as stock, fits the stock screws plus 4 heatsunk insert to fix the fan and 2 extra m3 nuts to eventually mount the unit on the wall or something.

obviously no vesa mount possibile, can be printed in whatever material (i printed in abs) without any support just as it is.. on the other externa facing side there are 4 slots to place the original rubber feets.

View attachment 23818

View attachment 23819

a 10mm fan clears every internal component, probably a 15mm also but not sure, temps are "fine" and the enclosure is nice and fresh.
inside the zip is the stl to slice it, as said no supports needed, 10-20% infill is more than enough.

Very Nice! How much would it be for you to print and ship it? I do not own a 3D printer or know someone who does.

 

[gregg098]

I'm currently sitting at 5+ days of uptime on my OPNsense VM. I never had any system crashes in Proxmox, but had a lot of issues keeping OPNsense running on this machine (but not others). I'm not exactly sure what the trigger was, but things are staying running for now.

For reference, running Proxmox on a V1 N6005 unit. OPNsense as a VM with Linux bridges assigned for WAN and LAN. The LAN bridge is a Linux Bond setup as LACP to my switch. Also have a few LXCs running my Unifi and Omada controllers, and now a seperate one with OpenVPN Access Server. Idea was to always make this my network machine, hence the controllers and VPNs.

The last three things I changed, and am unsure of their impact, were:
1) Disable QEMU agent in OPNsense - really doubt this made a difference, but who knows. Heard others say it was an issue. ACPI seems to work just fine.

2) Disable OpenVPN server in OPNsense and move it back to a a linux container. Unsure of the impact here. I only really use OpenVPN as a backup anyways. It always worked before moving to the Topton box. I always saw a lot of OpenVPN errors around WAN DHCP renewals.

3) Moved other LXCs on the Topton machine to a seperate Linux bridge assigned to an unused NIC, and plugged that into my switch. Previously I just assigned the same OPNsense LAN bridge to those containers. This seems like a waste of another port on the Topton unit and my switch, but hey, if it works it works.

Ill add that I used the exact same VMs/LXCs on another machine for a few months. Even tested on a cheapo Beelink machine. Ran rock solid on both. Then OPNsense would die in the middle of the night almost every night on the Topton machine. Tried a fresh install of everything and tons of tweaks including getting rid of the LACP bond at one point. All of sudden I have 5 days uptime and no issue

I have the 120mm USB fan sitting underneath the unit blowing up. Keeps temps in the low 30's most of the time.

Dont know if any of this is useful information, but just some observations.

 

[fazambuja]

Ok, but you are using it sideways which does not seem to be optimal at all. So i don't think you can compare what happens when you use a 120mm fan with the chassis sideways to what happens when you have a 40mm attached at the middle of the bottom cover.

The thing is that with the slim chassis which has vents on the sides + the 40mm fan in the middle of the bottom cover, in my vision the air will cool the whole motherboard and exhaust by the side vents easily due to the positioning the fan in the middle of the bottom cover.

My case is the square one that allows being placed on the side. It gives more access to air than placing it down. But it is not necessary, to be honest.
What I was trying to say is that the 120mm is too "big" to be used in the bottom of my case. There are no side vents for the air to leave, and it seems to get trapped inside. The slim case might be different.
But overall, the Noctua 40x10 is capable of keeping my device cool; I don't want to sound that the 120mm is needed, but it is a quiet option.
And again, a home fan is a great way to test if cooling from above works on your case.