Hello, we have bought the same model from the same seller, use the same ram and nvme. I use the bios with the default config and it works perfectly with proxmox+pfsense. Why don't you restore the bios to default values?
CWWK/Topton/... Nxxx quad NIC router
- Thread starter Becks0815
- Start date
Notice: Page may contain affiliate links for which we may earn a small commission through services like Amazon Affiliates or Skimlinks.
That is what I am thinking of doing. I was following that blog for more power saving/ cooler temp settings.
1- Do you have BIOS with advance settings unlocked? or stock BIOS that comes default with the device?
2- what is the power usage at idel on stock settings?
3 - what is your CPU tems on stock settings??
Please let me know. thanks.
After resetting everything, following is the output i see in proxmox shell...what do you see when issuing the following command. I only posted 2 CPU output, but output is exact same for all 4 CPUs.
cpufreq-info
cpufrequtils 008: cpufreq-info (C) Dominik Brodowski 2004-2009
Report errors and bugs to cpufreq@vger.kernel.org, please.
analyzing CPU 0:
driver: acpi-cpufreq
CPUs which run at the same hardware frequency: 0
CPUs which need to have their frequency coordinated by software: 0
maximum transition latency: 10.0 us.
hardware limits: 700 MHz - 801 MHz
available frequency steps: 801 MHz, 800 MHz, 700 MHz
available cpufreq governors: conservative, ondemand, userspace, powersave, performance, schedutil
current policy: frequency should be within 700 MHz and 801 MHz.
The governor "ondemand" may decide which speed to use
within this range.
current CPU frequency is 700 MHz (asserted by call to hardware).
cpufreq stats: 801 MHz:7.49%, 800 MHz:1.85%, 700 MHz:90.65% (163)
analyzing CPU 1:
current CPU frequency is 700 MHz (asserted by call to hardware).
cpufreq stats: 801 MHz:8.76%, 800 MHz:1.33%, 700 MHz:89.91% (128)
analyzing CPU 2:
The stock BIOS that comes default with the device with the default config.
cpufrequtils 008: cpufreq-info (C) Dominik Brodowski 2004-2009
Report errors and bugs to cpufreq@vger.kernel.org, please.
analyzing CPU 0:
driver: intel_pstate
CPUs which run at the same hardware frequency: 0
CPUs which need to have their frequency coordinated by software: 0
maximum transition latency: 4294.55 ms.
hardware limits: 700 MHz - 3.40 GHz
available cpufreq governors: performance, powersave
current policy: frequency should be within 700 MHz and 3.40 GHz.
The governor "performance" may decide which speed to use
within this range.
current CPU frequency is 1.86 GHz.
analyzing CPU 1:
driver: intel_pstate
CPUs which run at the same hardware frequency: 1
CPUs which need to have their frequency coordinated by software: 1
maximum transition latency: 4294.55 ms.
hardware limits: 700 MHz - 3.40 GHz
available cpufreq governors: performance, powersave
current policy: frequency should be within 700 MHz and 3.40 GHz.
The governor "performance" may decide which speed to use
within this range.
current CPU frequency is 3.10 GHz.
Modify the hardware limits
Last edited:
both stock latest bios, without any particural setup..
- c-states enabled
- PL1 8000 PL2 15000 for the n100
- PL1 15000 PL2 35000 for the n305
both boost correctly to max speed (respectively 3400 and 3800).
on a CWWK n100 v3, baremetal pfsense:
on CWWK n305 v3, proxmox host:
- c-states enabled
- PL1 8000 PL2 15000 for the n100
- PL1 15000 PL2 35000 for the n305
both boost correctly to max speed (respectively 3400 and 3800).
on a CWWK n100 v3, baremetal pfsense:
Code:
[2.7.2-RELEASE][root@pfSense]/root: dmidecode -t 4
# dmidecode 3.5
# SMBIOS entry point at 0x75c7d000
Found SMBIOS entry point in EFI, reading table from /dev/mem.
SMBIOS 3.6 present.
# SMBIOS implementations newer than version 3.5.0 are not
# fully supported by this version of dmidecode.
Handle 0x0034, DMI type 4, 48 bytes
Processor Information
Socket Designation: U3E1
Type: Central Processor
Family: Other
Manufacturer: Intel(R) Corporation
ID: E0 06 0B 00 FF FB EB BF
Version: Intel(R) N100
Voltage: 1.0 V
External Clock: 100 MHz
Max Speed: 3400 MHz
Current Speed: 2871 MHz
Status: Populated, Enabled
Upgrade: Other
L1 Cache Handle: 0x0031
L2 Cache Handle: 0x0032
L3 Cache Handle: 0x0033
Serial Number: To Be Filled By O.E.M.
Asset Tag: To Be Filled By O.E.M.
Part Number: To Be Filled By O.E.M.
Core Count: 4
Core Enabled: 4
Thread Count: 4
Characteristics:
64-bit capable
Multi-Core
Execute Protection
Enhanced Virtualization
Power/Performance Controlon CWWK n305 v3, proxmox host:
Code:
root@proxmox:~# dmidecode -t 4
# dmidecode 3.4
Getting SMBIOS data from sysfs.
SMBIOS 3.6.0 present.
# SMBIOS implementations newer than version 3.5.0 are not
# fully supported by this version of dmidecode.
Handle 0x0034, DMI type 4, 48 bytes
Processor Information
Socket Designation: U3E1
Type: Central Processor
Family: Core i3
Manufacturer: Intel(R) Corporation
ID: E0 06 0B 00 FF FB EB BF
Signature: Type 0, Family 6, Model 190, Stepping 0
Flags:
FPU (Floating-point unit on-chip)
VME (Virtual mode extension)
DE (Debugging extension)
PSE (Page size extension)
TSC (Time stamp counter)
MSR (Model specific registers)
PAE (Physical address extension)
MCE (Machine check exception)
CX8 (CMPXCHG8 instruction supported)
APIC (On-chip APIC hardware supported)
SEP (Fast system call)
MTRR (Memory type range registers)
PGE (Page global enable)
MCA (Machine check architecture)
CMOV (Conditional move instruction supported)
PAT (Page attribute table)
PSE-36 (36-bit page size extension)
CLFSH (CLFLUSH instruction supported)
DS (Debug store)
ACPI (ACPI supported)
MMX (MMX technology supported)
FXSR (FXSAVE and FXSTOR instructions supported)
SSE (Streaming SIMD extensions)
SSE2 (Streaming SIMD extensions 2)
SS (Self-snoop)
HTT (Multi-threading)
TM (Thermal monitor supported)
PBE (Pending break enabled)
Version: Intel(R) Core(TM) i3-N305
Voltage: 0.8 V
External Clock: 100 MHz
Max Speed: 3800 MHz
Current Speed: 2079 MHz
Status: Populated, Enabled
Upgrade: Other
L1 Cache Handle: 0x0031
L2 Cache Handle: 0x0032
L3 Cache Handle: 0x0033
Serial Number: To Be Filled By O.E.M.
Asset Tag: To Be Filled By O.E.M.
Part Number: To Be Filled By O.E.M.
Core Count: 8
Core Enabled: 8
Thread Count: 8
Characteristics:
64-bit capable
Multi-Core
Execute Protection
Enhanced Virtualization
Power/Performance Controldunno what is wrong with your box, you definetly have something messed up in the bios settings or os settings.
Code:
root@proxmox:~# cpufreq-info
cpufrequtils 008: cpufreq-info (C) Dominik Brodowski 2004-2009
Report errors and bugs to cpufreq@vger.kernel.org, please.
analyzing CPU 0:
driver: intel_pstate
CPUs which run at the same hardware frequency: 0
CPUs which need to have their frequency coordinated by software: 0
maximum transition latency: 4294.55 ms.
hardware limits: 800 MHz - 3.80 GHz
available cpufreq governors: performance, powersave
current policy: frequency should be within 800 MHz and 3.80 GHz.
The governor "performance" may decide which speed to use
within this range.
current CPU frequency is 1.75 GHz.thank you very much @skynet137 and @pigr8
I changed everything to default in the BIOS and in proxmox changed governor in crontab to “ondemand” mode (default mode)
then I also enabled PL1 and PL2 as mentioned above and everything started to work as normal.
CPU temps & NVME temps have definitely gone up 5C
idle last 7 days still shows 5W avg.
when I did a full CPU stress test for 60 secs it went up to 12W and cores are hitting 3GHz, as seen in the attachment.
Attached pics for reference
I changed everything to default in the BIOS and in proxmox changed governor in crontab to “ondemand” mode (default mode)
then I also enabled PL1 and PL2 as mentioned above and everything started to work as normal.
CPU temps & NVME temps have definitely gone up 5C
idle last 7 days still shows 5W avg.
when I did a full CPU stress test for 60 secs it went up to 12W and cores are hitting 3GHz, as seen in the attachment.
Attached pics for reference
Code:
cpufreq-info
cpufrequtils 008: cpufreq-info (C) Dominik Brodowski 2004-2009
Report errors and bugs to cpufreq@vger.kernel.org, please.
analyzing CPU 0:
driver: intel_pstate
CPUs which run at the same hardware frequency: 0
CPUs which need to have their frequency coordinated by software: 0
maximum transition latency: 4294.55 ms.
hardware limits: 700 MHz - 3.40 GHz
available cpufreq governors: performance, powersave
current policy: frequency should be within 700 MHz and 3.40 GHz.
The governor "performance" may decide which speed to use
within this range.
current CPU frequency is 3.23 GHz.
Code:
# dmidecode 3.4
Getting SMBIOS data from sysfs.
SMBIOS 3.5.0 present.
Handle 0x004A, DMI type 4, 48 bytes
Processor Information
Socket Designation: U3E1
Type: Central Processor
Family: Other
Manufacturer: Intel(R) Corporation
ID: E0 06 0B 00 FF FB EB BF
Version: Intel(R) N100
Voltage: 1.0 V
External Clock: 100 MHz
Max Speed: 3400 MHz
Current Speed: 2871 MHz
Status: Populated, Enabled
Upgrade: Other
L1 Cache Handle: 0x0047
L2 Cache Handle: 0x0048
L3 Cache Handle: 0x0049
Serial Number: To Be Filled By O.E.M.
Asset Tag: To Be Filled By O.E.M.
Part Number: To Be Filled By O.E.M.
Core Count: 4
Core Enabled: 4
Thread Count: 4
Characteristics:
64-bit capable
Multi-Core
Execute Protection
Enhanced Virtualization
Power/Performance ControlAttachments
Last edited:
Wow - box arrived from China today - ali living up to its 'express' title.
I simply swapped the RAM and nvme out of my current N100 box into the new one, plugged the ethernet cables into the same jacks, booted to BIOS, set the time, rebooted....straight into my working OPNsense install. Great!
Temps do indeed seem 5-6C lower than the old box - better paste? Better case design?
And I now have a working HDMI output again, as well as a spare N100 box as a failover.
Now - how do I check that COM/Console port as requested - bearing in mind I don't want to take down our router for any length of time
Last edited:
You would need to connect a computer to the COM port using something like a Cisco USB-to-RJ45 Console cable that has a built in serial port, fire up a terminal emulator and see if BIOS shows up during boot.
Failing that, you could check if the BIOS on a monitor shows a setting to enable serial console redirection or something similar.
Failing that, you could check if the BIOS on a monitor shows a setting to enable serial console redirection or something similar.
I don't have the COM port connector hardware, but checking in the BIOS, it does indeed have serial console redirection, and a hole bunch of options associated with it. Looks like a pretty unlocked BIOS from what I can tell!
Thank you very much. It seems that this might support console as soon as it gets powered up. Now I am just torn apart between this one and the CWWK ones wich the higher cooling fins. Your temps do look really good, though! Reading through the Ali Express comments it seems to be hit or miss regarding the temps... but following this thread, it is the same, no matter if Topton, CWWK or any others, so it is always a little bit of a risk. Only the customer support seems to be not good at Topton from what I have read here and on Ali Express, so I might forgo the serial port, although I really like to have one ;-)
Thanks for reporting back and doing the tests!
I cut some more holes in the end plate of my X86-P5 and added a serial port and two USB ports.
Attachments
Oh wait! I see it is the P5, but now I wonder if the CWWK N100 boxes the thread is about have the necessary Serial port connector on the Board as well!
Alright, I'm at a bit of a loss... I have a Topton N100 with 16Gb ram and 256Gb nvme.
Until 2 days ago I was running proxmox with opnsense on it and it would crash and need to be restarted every 4-5 days or so. No indication to the cause of the crashes in the opnsense logs, so seems hardware/driver related.
Thinking removing the proxmox intermediary might help, since I'm not running anything else on the box anyway, I tried a bare metal install of opnsense a couple days ago. It now crashes every 15 to 20 minutes.. sometimes under load, sometimes without me doing anything at all. I've checked the temps, I applied new thermal paste, temps stay within the 40-50 range. I've ran multiple memtest they all pass with 0 errors. I've cleared the CMOS battery. I don't know what else to try... any ideas?
Edit: so this has been interesting.. I figured out that if my desktop isn't connected to the Wifi (in either 2.4 or 5Ghz) then the router doesn't crash. I use a set of access points with Omada for the wifi. When I connect the desktop PC by cable, no crashes. When I use my laptop as wifi hotspot to share the existing wifi with the desktop PC, no crashes. Still no clue as to why this is happening, especially since it wasn't as frequent with proxmox install..
Until 2 days ago I was running proxmox with opnsense on it and it would crash and need to be restarted every 4-5 days or so. No indication to the cause of the crashes in the opnsense logs, so seems hardware/driver related.
Thinking removing the proxmox intermediary might help, since I'm not running anything else on the box anyway, I tried a bare metal install of opnsense a couple days ago. It now crashes every 15 to 20 minutes.. sometimes under load, sometimes without me doing anything at all. I've checked the temps, I applied new thermal paste, temps stay within the 40-50 range. I've ran multiple memtest they all pass with 0 errors. I've cleared the CMOS battery. I don't know what else to try... any ideas?
Edit: so this has been interesting.. I figured out that if my desktop isn't connected to the Wifi (in either 2.4 or 5Ghz) then the router doesn't crash. I use a set of access points with Omada for the wifi. When I connect the desktop PC by cable, no crashes. When I use my laptop as wifi hotspot to share the existing wifi with the desktop PC, no crashes. Still no clue as to why this is happening, especially since it wasn't as frequent with proxmox install..
Last edited:
Are APs POE? are they connected to n100 directly or via a switch - if directly try using a switch in between maybe they are trying to pull power..
I've just had an N100 delivered from TopTon (I know...) to replace my N5105 at home.
I pulled it completely apart, removed the copper block on the case and cleaned out all of the thermal paste.
I've used Thermal Grizzly - Kryonaut to re-paste the copper block to the chassis.
Same Kryonaut used on the CPU to a copper shim (20x20x0.3mm, Was a gap from factory)
Same Kryonaut used between the shim and the copper block.
I've used:
DTK 12V 5A 60W Power Supply (I wont use the one sent from TopTon)
Crucial P3 500Gb M.2 NVMe (CT500P3SSD8)
Kingston Fury Impact 16Gb DDR5 (KF556S40IB-16)
All sourced from Amazon UK.
This will be running bare metal OPNSense, to replace my N5105.
My N5105 idles at 52 Celsius.
The N100 is idling at 39 Celsius.
I have installed the microcode updates, and made a few small changes to the BIOS, mainly PL1 - 8000, PL2 - 8500.
I'm letting in bed in for a few days before swapping over.
So far though, it's running great. The case is luke-warm to the touch.
Hope that helps someone who is on the edge of ordering one.
Just for info its : CW-AL-4L-V2.0 mobo with BIOS ALN4L102 - 11/08/2023
I pulled it completely apart, removed the copper block on the case and cleaned out all of the thermal paste.
I've used Thermal Grizzly - Kryonaut to re-paste the copper block to the chassis.
Same Kryonaut used on the CPU to a copper shim (20x20x0.3mm, Was a gap from factory)
Same Kryonaut used between the shim and the copper block.
I've used:
DTK 12V 5A 60W Power Supply (I wont use the one sent from TopTon)
Crucial P3 500Gb M.2 NVMe (CT500P3SSD8)
Kingston Fury Impact 16Gb DDR5 (KF556S40IB-16)
All sourced from Amazon UK.
This will be running bare metal OPNSense, to replace my N5105.
My N5105 idles at 52 Celsius.
The N100 is idling at 39 Celsius.
I have installed the microcode updates, and made a few small changes to the BIOS, mainly PL1 - 8000, PL2 - 8500.
I'm letting in bed in for a few days before swapping over.
So far though, it's running great. The case is luke-warm to the touch.
Hope that helps someone who is on the edge of ordering one.
Just for info its : CW-AL-4L-V2.0 mobo with BIOS ALN4L102 - 11/08/2023
Last edited:
not POE and they're already on a separate switch, the N100 only use 2 ports: 2.5G WAN provider and 2.5Gb to switch
Only the desktop pc running on wifi seems to crash the router. I have 47 other devices on the wifi without issues.
were things get interesting is that i think, in some cases, the router crashes when I see specific events in my windows event log on the desktop pc, such as:
Which is wild to me, this error is a notorious one some intel wifi pcie cards, but the fact that it could potentially be the cause of the router crashing is a bit mind boggling... If anyone has any ideas as to what the underlying cause might be (some opnsense configuration to prevent malfomed packets maybe?) I'm all ears..
Regarding the COM Port on the CWWK N100 boards, they sent me this picture for the Pinout. I see that others were trying to work it out in earlier posts...
I've also been working on that but then ran out of time..
There are two standards for COM cables, DTK/Intel and AT/Everex. So when buying a cable, make sure to get the right one.
If you look at DTK/Intel, it's connected crossing over.
IDC - DB9
1 - 1
2 - 6
3 - 2
4 - 7
5 - 3
6 - 8
7 - 4
8 - 9
9 - 5
Everex:
