Hey man!Does anyone know the size of the barrel plug for the power supply?
Barrel: 5.5 x 2.5mm
Hey man!Does anyone know the size of the barrel plug for the power supply?
5.5x2.5. I bought this to go from a Meanwell to a V1 N6005 Topton unit when I had it.Does anyone know the size of the barrel plug for the power supply?
Perhaps venting on more than one side and the HDD not resting on the top, give the bottom plate some slots and raise it off the resting surface with some silicone or rubber feet too for both air and vibration?I do admit that my first attempt at 3D is not going to win any design awards, but messy? In my book it can't be messy if it's square (see attached photos)
Can You please let us know if PFSENSE runs stable with the i226 NICs ??????????????????????
Yeah it would be nice to know if pfsense, opnsense, promox, esxi and etc, work nice with the new i226.Can You please let us know if PFSENSE runs stable with the i226 NICs ??????????????????????
Part of the mystery solved...I hope it helps others: I tried your suggestion with thermal pad - no dice, worse temps. Then I took a light and peeked under the mobo to see if I can spot what prevents the CPU to make proper contact with the copper block: the the bloody additional aluminum block used as radiator (north of CPU).It might get shouted down, but if you are unsure use a thermal pad!
---------------
True, circulating hot air around a case is not ideal but oddly enough forcing air on onto a surface is more effective at heat transfer than relying on convection currents or potential difference, even if it's warm air. The real answer is that you need to do both.
Even if you need to make some ducting out of cardboard or a cut-down small plastic juice bottle to ensure the hot component gets a singular flow of air, as in server cases.
root@OPNsense:~ # pciconf -lv | grep -A1 -B2 network
igc0@pci0:0:16:0: class=0x020000 rev=0x04 hdr=0x00 vendor=0x8086 device=0x125c subvendor=0x8086 subdevice=0x0000
vendor = 'Intel Corporation'
class = network
subclass = ethernet
[2.6.0-RELEASE][admin@pfSense.home.arpa]/root: pciconf -lv | grep -A1 -B2 network
none1@pci0:0:16:0: class=0x020000 card=0x00008086 chip=0x125c8086 rev=0x04 hdr=0x00
vendor = 'Intel Corporation'
class = network
subclass = ethernet
igc0: <Intel(R) Ethernet Controller I226-V> mem 0x81400000-0x814fffff,0x81560000-0x81563fff irq 11 at device 16.0 on pci0
igc0: Setup of Shared code failed, error -2
igc0: IFDI_ATTACH_PRE failed 6
device_attach: igc0 attach returned 6
You've got the same model I have, I think, though with all the changes it's difficult to keep track. The spaces *between* the cutouts are for the Intel NICs on mine. The cut outs are just for the screws so they don't foul the chips. That's part of the reason I went for the K2-Pro gunk.Part of the mystery solved...I hope it helps others: I tried your suggestion with thermal pad - no dice, worse temps. Then I took a light and peeked under the mobo to see if I can spot what prevents the CPU to make proper contact with the copper block: the the bloody additional aluminum block used as radiator (north of CPU).
Since it has cutouts in it (i assume those fitting in are voltage regulators?) of course it's not machined properly and it prevents the CPU from being seated like it should.
i have the same unit, the alu block you are referring to is the one on the inside shell that has come pads? that should be for the vrm, it that preventing you having good temps? did you apply the bios optimization? how hot did it run before?Part of the mystery solved...I hope it helps others: I tried your suggestion with thermal pad - no dice, worse temps. Then I took a light and peeked under the mobo to see if I can spot what prevents the CPU to make proper contact with the copper block: the the bloody additional aluminum block used as radiator (north of CPU).
Since it has cutouts in it (i assume those fitting in are voltage regulators?) of course it's not machined properly and it prevents the CPU from being seated like it should.
Removed the Al block for now and I can stay below 70C during stress test...will see what solution I can find for this besides the fan on the way already. Should be enough, other mobos don't have the second radiator.
BTW: mine is the 1338MP-12 blue board (no prefix letters) with N5105 and RJ45 console port
THIS model...of course it had to drop in price
Did you buy the adapter for the 2nd M2?Well, mine has secretly turned up after a complaint was made to Australia Post.
I'm just running through it now and it looks about 300% better than the earlier one I returned from a different seller.
The NICs are i226 and need manual driver installation in Windows 11, they are not detected by Windows Update. I was a bit nostalgic about having to manually install each interface one by one.
I'll post a bit more later on.
Edit_1: things are bad when you start numbering your edits, but here we go. Please note that clicking on the thumbnails will link to an unsized image and the file could be large.
This is the link to what I bought.
I had previously bought an earlier model from a different seller and it had issues and is currently <*still*> in dispute with the AliExpress seller. But the story isn't about that, it's about the replacement and OMG what a difference they are. The packaging was better, the BIOS - Wow the options I have now a too many to go through but it's needless to say that if I want to change anything I probably have a BIOS setting for it with this new one.191.45US $ 5% OFF|Upgrade The N5105 Softroute Mini-host /openwrt/pve/esxi Fansless Energy Saving Pc - Barebone & Mini Pc - AliExpress
Smarter Shopping, Better Living! Aliexpress.comwww.aliexpress.com
It came well packed and even though the box corners had a bit of damage the unit was well protected.
The heatsinks are a combination of a copper block to the lid for the CPU and an aluminium block across the NICs. Contact and paste look really good and I haven't had a reason to open it up yet.
As noted above, I started with Windows 11 Pro, I didn't mean to as I thought the WD Blue SSD I used was clean and it wasn't so I went with that. Drivers for the new i226 NICs are an issue during installation as the drivers have to be manually installed, the link is below for you.
Intel® Network Adapter Driver for Microsoft* Windows* 11
This download record installs drivers for Intel® Network Adapters using Microsoft Windows 11*www.intel.com
The i226 complete driver pack for every supported OS is below.
Intel® Ethernet Adapter Complete Driver Pack
This download installs version 27.6 of the Intel® Ethernet Adapter Complete Driver Pack for supported OS versions.www.intel.com
Once installed, I used iperf3 in both directions and the scores were spot on.
Doing a 'drag & drop' test of an 8Gb file showed a very consistent transfer rate and around the 40% CPU utilization.
Here are some photos of the CPU details, and benchmark results from CPU-Z. (they aren't screenshots - sorry)
CPU-Z score card for the N5105 mini-router .
Single;
... and Multi;
Power and Temps.
Power consumption was no higher than 26 watts, it was almost like it was being throttled. You can expect a range of 22 - 25watts when working generally and a system idle draw of around 11 watts; please note that the power supply draws 2 watts when the unit is shut down.
CPU temperature sat at a constant 67 degrees while running CPU-Z benchmark; With load at 100%, CPU temperature variation between the cores at full load was within 1*c.
Ubuntu was a walk in the park, here are some results from lscpu & lspci, lspci -vv
Thanks.
No I didn't, it just came installed. I took it out for the tests and added an AX200 WiFi card in its place.Did you buy the adapter for the 2nd M2?
If not, it's a nice addition compared to other sellers.
Topton for example, sells this adapter for 15$
I went that way at first with Hyper-V, but I couldn't get IOMMU to work, the Windows NIC drivers doesn't see it as IOMMU enabled. However it does work in Proxmox VE... and allows me to address the NIC's directly via PCI from the VM without a middle layer of going through the Hypervisor for translation of the NIC...listed below as PCI Devices...Guys, has anyone used Hyper-V on these minipc's?
It would be interesting to see how it performs for Ubuntu Server + pfSense virtualization
Yeah, on mine the aluminum block cutouts don't line properly with the VRs so it kept the gap between CPU and the copper block large. I just removed the aluminum block, haven't gone past 70C since, and that's without the fan.i have the same unit, the alu block you are referring to is the one on the inside shell that has come pads? that should be for the vrm, it that preventing you having good temps? did you apply the bios optimization? how hot did it run before?
i switched my production firewall to this topton unit to see how it handles but i had no time to finish the setup, the 2.5g are still not configured but for now it does work without issues.
View attachment 24138
IOMMU is detected in Proxmox VE after I declare "intel_iommu=on iommu=pt" in grub options.I went that way at first with Hyper-V, but I couldn't get IOMMU to work, the Windows NIC drivers doesn't see it as IOMMU enabled. However it does work in Proxmox VE... and allows me to address the NIC's directly via PCI from the VM without a middle layer of going through the Hypervisor for translation of the NIC...listed below as PCI Devices...
View attachment 24149
now i have to open it up again and check my block too, i wonder if that is the case.Yeah, on mine the aluminum block cutouts don't line properly with the VRs so it kept the gap between CPU and the copper block large. I just removed the aluminum block, haven't gone past 70C since, and that's without the fan.
Yes, I did apply all the BIOS and pfSense optimisations recommended here.
Oh: I was asking about the inability to see Turbo frequency in action...it looks like *BSD has a problem determining anything except the base clock.
Last "words of wisdom" : don't be stupid like me and when/if you run a test with the case open (on mine the sides come off) grab it by the side pressing the RESET button.... unless you have time at 1am re-configuring BIOS settings. Lesson learned.