Topton Jasper Lake Quad i225V Mini PC Report
- Thread starter ReturnedSword
- Start date
Notice: Page may contain affiliate links for which we may earn a small commission through services like Amazon Affiliates or Skimlinks.
In the BIOS (assuming you have a CW board with AMI BIOS):
Advanced > PCH-FW Configuration > ME State > [Enabled/Disabled]
I bought one of these N5100 boxes recently. It powered on once and never again 
Not expecting much in terms of refund. They said to ship it back to which I said not a chance.
Would anyone happen to have any kind of idea where to look for the possible cause? I've looked at the PCB pretty closely and don't see anything obvious. Power adapter works just fine. The thing I got has GF-1338NP-12 rev 1.4 printed on the PCB.
Not expecting much in terms of refund. They said to ship it back to which I said not a chance. Would anyone happen to have any kind of idea where to look for the possible cause? I've looked at the PCB pretty closely and don't see anything obvious. Power adapter works just fine. The thing I got has GF-1338NP-12 rev 1.4 printed on the PCB.
Have you tried removing everything except a single stick of RAM? I have a N5105 CW-N11 that refuses to power on when a Teamforce 256GB m.2 NVME drive is installed. Any other drive and it's fine but when the Teamforce drive is installed, you'd think the unit is 100% dead.I bought one of these N5100 boxes recently. It powered on once and never again
Would anyone happen to have any kind of idea where to look for the possible cause? I've looked at the PCB pretty closely and don't see anything obvious. Power adapter works just fine. The thing I got has GF-1338NP-12 rev 1.4 printed on the PCB.
Heads up @pinterI bought one of these N5100 boxes recently. It powered on once and never again
Would anyone happen to have any kind of idea where to look for the possible cause? I've looked at the PCB pretty closely and don't see anything obvious. Power adapter works just fine. The thing I got has GF-1338NP-12 rev 1.4 printed on the PCB.
I got the exact same model of the box as you and I ran into the same issue (i think). I do not remember exactly right now why it happens cause it was a while back, but if I remember corectly it has something to do with restarting after some changes in BIOS settings.
Anyhow, what worked for me twice, was unplugging everything from the unit, including the power adapter, and holding on the power button for I would say at least 10 seconds, then re-connecting the power adapter and powering on. If it does not power on, try holding the power button for 3-4 seconds (with the power connected). If that also fails, there is a reset button in a pinhole on the unit. I am pretty sure that has it's good purpose there.
If the unit powers on, it takes a longer time to boot. As far as I remember it resets all BIOS settings to default and that's why it takes longer.
Hope this also works for you
good luck
Last edited:
skimlikes probably nailed it for you but if it still doesn't post, try a different stick of memory and remove any storage. You didn't provide much info but if you need more help you may want to include the amount and make of the RAM and storage (NVMe, SSD). Did you purchase it separately or order the unit with vendor supplied items?I bought one of these N5100 boxes recently. It powered on once and never again
Would anyone happen to have any kind of idea where to look for the possible cause? I've looked at the PCB pretty closely and don't see anything obvious. Power adapter works just fine. The thing I got has GF-1338NP-12 rev 1.4 printed on the PCB.
Bob S
Having spent the weekend playing with the CW-J6-L6 (J6413 with 6x i226 NICs), I can't say I would recommend it to anyone over the N5105 or N6005. The N6005 (CW-N6000 v1.1, 4x i225) pulls ~7.8w during typical network traffic scenarios for my home. The N5105 (CW-N11, 6x i225) pulls ~9.5w. The best I could get out of the J6413 without hobbling it was 14w. The J6413 idles between 38 and 41C whereas the N6005 and N5105 both idle around 27C. Measured after 24 hours, the case, passively cooled, was 38C which feels warm to the touch but is not uncomfortable. The J6413 performs on par with the N5105 albeit with a 32% increase in wattage.
Code:
[ 0.739724] DMAR: No ATSR found
[ 0.739725] DMAR: No SATC found
[ 0.739726] DMAR: IOMMU feature fl1gp_support inconsistent
[ 0.739727] DMAR: IOMMU feature pgsel_inv inconsistent
[ 0.739727] DMAR: IOMMU feature nwfs inconsistent
[ 0.739728] DMAR: IOMMU feature dit inconsistent
[ 0.739728] DMAR: IOMMU feature sc_support inconsistent
[ 0.739729] DMAR: IOMMU feature dev_iotlb_support inconsistentAnybody managed to find the BIOS setting to avoid those errors? Thank you.
@skimikes @lukasig @BobS thanks for the feedback. I've tried pretty much every combination of everything, no memory/storage, only memory, memory and storage, pull the bios battery etc. If any of these things were an issue is it plausible the thing wouldn't show any signs of life at all? I guess the only thing I haven't done is try different memory but that's cause I don't have any. There's no life at all. I would expect something, even if there's memory plugged in.
I ordered the box without memory or storage. Plugged in an ssd and got 8GB RAM. The stick I got is some Silicon Power brand.
I ordered the box without memory or storage. Plugged in an ssd and got 8GB RAM. The stick I got is some Silicon Power brand.
Okay - back to basics. Remove any storage and make sure the memory is the correct type - double check - then make sure it is in the correct slot for the type memory if it makes a difference for that motherboard. I'm assuming it has two SODIMM slots and that you have tried both if it's a single 8GB stick. If it's two 4GB sticks, use one, swap around rinse and repeat.
Yes - the mini will act like dead meat if it has incompatible memory or bad memory.
Once you have done the above and still have a memory stick installed, take a USB stick that has an indicator on it that flashes when it's being accessed. With power on, insert the USB stick and watch for flashing. If you see flashing, good chance the BIOS/UEFI is seeing it. If you have the pfsense or Windows iso installed on it there's a chance it will try to boot to that. Power off/on with USB stick in.
Not knowing what box you have, please explain how are you connecting video? If it has multiple video out ports, have you tried the other ones?
What I'm getting at is trying to see if it will show a BIOS screen - or even briefly flash something that shows life. But... the box could be perfect but your physical connections could be incorrect. For instance, if you're trying to use this in a headless (no monitor connected) configuration, some systems won't boot without a monitor connected.
So please explain what is connected where and include a model or a link to that box you have so we can see what it has. Need the details in order to help. Flying blind otherwise.
BobS
Last edited:
@pinter Having the exact same box and experiencing pretty much the same symptoms, I would be surprised if it's not the exact same thing. As I said, it was a while back and can't remember the exact details but try leaving only the ram stick connected (the same ram it first started with) and plug a paper clip in the reset hole and holding the reset for a while while connected to power, see if that does anything.
I have bought my box in the same way: N5100, no ram, no ssd. Before it was shipped, I got this message from the seller:
"Suggest DO NOT buy Barebone Mini PC ("No Ram No Storage" bundle)If you are NOT IT hardware technician. PC demands professional skill to assemble and debug.We are afraid to see you suffer a bad shopping experience and DO NOT compensate for buyer's man-made damage and faulty. If you leave negative feedback because of your faulty without discussing, warranty will be lost by default."
So I think shipping it back to the seller does not make much sense at this point.
Last edited:
Code:
root@pve:~# uname -a
Linux pve 5.19.17-1-pve #1 SMP PREEMPT_DYNAMIC PVE 5.19.17-1 (Mon, 14 Nov 2022 20:25:12 x86_64 GNU/Linux
root@pve:~# cat /etc/default/grub | grep GRUB_CMDLINE_LINUX_DEFAULT
GRUB_CMDLINE_LINUX_DEFAULT="quiet intel_iommu=on"
root@pve:~# dmesg | grep -e DMAR -e IOMMU
[ 0.018837] ACPI: DMAR 0x00000000746C2000 000088 (v02 INTEL EDK2 00000002 01000013)
[ 0.018868] ACPI: Reserving DMAR table memory at [mem 0x746c2000-0x746c2087]
[ 0.049974] DMAR: IOMMU enabled
[ 0.122772] DMAR: Host address width 39
[ 0.122773] DMAR: DRHD base: 0x000000fed90000 flags: 0x0
[ 0.122779] DMAR: dmar0: reg_base_addr fed90000 ver 4:0 cap 1c0000c40660462 ecap 49e2ff0505e
[ 0.122782] DMAR: DRHD base: 0x000000fed91000 flags: 0x1
[ 0.122787] DMAR: dmar1: reg_base_addr fed91000 ver 1:0 cap d2008c40660462 ecap f050da
[ 0.122790] DMAR: RMRR base: 0x0000007b800000 end: 0x0000007fbfffff
[ 0.122793] DMAR-IR: IOAPIC id 2 under DRHD base 0xfed91000 IOMMU 1
[ 0.122794] DMAR-IR: HPET id 0 under DRHD base 0xfed91000
[ 0.122796] DMAR-IR: Queued invalidation will be enabled to support x2apic and Intr-remapping.
[ 0.124557] DMAR-IR: Enabled IRQ remapping in x2apic mode
[ 0.301525] pci 0000:00:02.0: DMAR: Skip IOMMU disabling for graphics
[ 0.369124] DMAR: No ATSR found
[ 0.369125] DMAR: No SATC found
[ 0.369127] DMAR: IOMMU feature fl1gp_support inconsistent
[ 0.369128] DMAR: IOMMU feature pgsel_inv inconsistent
[ 0.369129] DMAR: IOMMU feature nwfs inconsistent
[ 0.369130] DMAR: IOMMU feature pds inconsistent
[ 0.369131] DMAR: IOMMU feature eafs inconsistent
[ 0.369131] DMAR: IOMMU feature prs inconsistent
[ 0.369132] DMAR: IOMMU feature nest inconsistent
[ 0.369133] DMAR: IOMMU feature mts inconsistent
[ 0.369133] DMAR: IOMMU feature sc_support inconsistent
[ 0.369134] DMAR: IOMMU feature dev_iotlb_support inconsistent
[ 0.369135] DMAR: dmar0: Using Queued invalidation
[ 0.369138] DMAR: dmar1: Using Queued invalidation
[ 0.370852] DMAR: Intel(R) Virtualization Technology for Directed I/O
root@pve:~# dmesg | grep 'remapping'
[ 0.122796] DMAR-IR: Queued invalidation will be enabled to support x2apic and Intr-remapping.
[ 0.124557] DMAR-IR: Enabled IRQ remapping in x2apic mode
root@pve:~# find /sys/kernel/iommu_groups/ -type l
/sys/kernel/iommu_groups/7/devices/0000:00:1c.4
/sys/kernel/iommu_groups/15/devices/0000:04:00.0
/sys/kernel/iommu_groups/5/devices/0000:00:17.0
/sys/kernel/iommu_groups/13/devices/0000:02:00.0
/sys/kernel/iommu_groups/3/devices/0000:00:15.2
/sys/kernel/iommu_groups/3/devices/0000:00:15.0
/sys/kernel/iommu_groups/11/devices/0000:00:1f.0
/sys/kernel/iommu_groups/11/devices/0000:00:1f.5
/sys/kernel/iommu_groups/11/devices/0000:00:1f.3
/sys/kernel/iommu_groups/11/devices/0000:00:1f.4
/sys/kernel/iommu_groups/1/devices/0000:00:02.0
/sys/kernel/iommu_groups/8/devices/0000:00:1c.5
/sys/kernel/iommu_groups/16/devices/0000:05:00.0
/sys/kernel/iommu_groups/6/devices/0000:00:1c.0
/sys/kernel/iommu_groups/14/devices/0000:03:00.0
/sys/kernel/iommu_groups/4/devices/0000:00:16.0
/sys/kernel/iommu_groups/12/devices/0000:01:00.0
/sys/kernel/iommu_groups/2/devices/0000:00:14.5
/sys/kernel/iommu_groups/2/devices/0000:00:14.2
/sys/kernel/iommu_groups/2/devices/0000:00:14.0
/sys/kernel/iommu_groups/10/devices/0000:00:1c.7
/sys/kernel/iommu_groups/0/devices/0000:00:00.0
/sys/kernel/iommu_groups/9/devices/0000:00:1c.6
Last edited:
What power supply was bundled with your box? Can you confirm it gives out voltage on the barrel plug?
I had a very similar thing happening, the pins on the europlug socket for the psu's cable were so low quality they deformed after a few uses and ceased making contact. See this post here.
OMG it woke up! Not sure what combination of things worked. I moved my RAM to the other slot and left the box plugged in overnight. I plugged in a keyboard, monitor and a USB stick as suggested above. Pushed the reset button for a good 30 seconds and then upon pressing the power button it actually lit up and I got as far as the BIOS!
Just want to thank you guys for spurring me to try different things, I thought for sure this thing was completely toast.
Just want to thank you guys for spurring me to try different things, I thought for sure this thing was completely toast.
So you're saying that once everything was plugged in and turned on it worked...;-)
I think you should find out exactly what the cause of the problem was to make sure this is not a real or intermittent defect - or just fat thumbs. We all have made those mistakes. So take the time to learn from this so you'll better understand how to troubleshoot it next time - and there's a really good chance of there being a next time...
I would suggest you install Win10 initially along with HWInfo and other tools mentioned previously so you can easily check the memory and the storage drive. Even name brand RAM and storage can experience premature failures, so it's a good idea to stress those upfront while everything is still within warranty. Plus it's good training.
After installing the OS, cycle the unit (power off/on) several times (without USB plugged in) to make sure it boots and operates properly - or if it lets out all the magic smoke. By that I mean, do a proper shutdown and power on - not just pull the plug...
You may or may not need to make some BIOS/UEFI changes and with Windows, all the drivers may not show up. Don't panic over any of that but also don't just start making BIOS changes without having a basic understanding of what the setting is doing. Lots of strange acronyms in the BIOS/UEFI and while there are standards there are also vendors that make changes that you'll have a difficult time even finding a reference for the setting(s) they have included.
One other suggestion is to mention the make/model and configuration of the mini. This thread has covered a multitude of different boxes from different vendors so we can only guess at what you have purchased.
Glad you got it working - now try to break it again so you'll be sure it's really working...
BobS
Last edited:
What do you get from:
Code:
for i in `lshw -c network -businfo|grep pci@|awk '{print $1}'|sed -e 's/pci@//'`; do find /sys/kernel/iommu_groups/ -name $i; done
Code:
root@proxmox:~# for i in `lshw -c network -businfo|grep pci@|awk '{print $1}'|sed -e 's/pci@//'`; do find /sys/kernel/iommu_groups/ -name $i; done
/sys/kernel/iommu_groups/13/devices/0000:01:00.0
/sys/kernel/iommu_groups/14/devices/0000:02:00.0
/sys/kernel/iommu_groups/15/devices/0000:03:00.0
/sys/kernel/iommu_groups/16/devices/0000:04:00.0
/sys/kernel/iommu_groups/17/devices/0000:05:00.0
/sys/kernel/iommu_groups/18/devices/0000:06:00.0@rfox you have had any luck getting an update from Loksing on this ribbon cable? Their website is strange and won't let me send them an email without an order number
What found in my Topton Ryzen 7 5800U testing so far is that, it is super stable and packs far more horsepower than the fanless N5105. Certainly happy with the purchase so far.
That said, I found their proprietary SATA cable rather flimsy and on 3 disk RAIDZ1-0 ZFS (other two M.2) somewhat unstable. UDMA_CRC_Error_Count ramp is concerning and had to resilver ZFS twice. SATA cable likely the culprit there.
Anybody know where can I find this SATA cable? Kingvoy and Toptop don't sell individual spare and I'm having hard time locating the right cable