12gen N-series Nas motherboard (topton, cwwk, ... )
- Thread starter Steffe
- Start date
Notice: Page may contain affiliate links for which we may earn a small commission through services like Amazon Affiliates or Skimlinks.
Apologies, I couldn't find the Part# of the memory chips you use in your post history. You mention Crucial and SK Hynix but no PN. Thanks.
P.S: Someone mentioned CT32G56C46S5 as a viable option for the Green N305. So I ordered it to give a try with the purple N305 I'll get in a few days. It's even not worth accepting the parcel if this is what you tried at first.
Upon further investigation, I have found:
1. In BIOS, enable USB per-port override, and set all ports to "Enabled".
2. If a USB 3 device is plugged at boot (or kernel start?), there is no error message in dmesg, and the USB SuperSpeed device is detected.
The device is attached to "Thunderbolt 4 USB Controller"
3. If no USB 3 device is plugged at boot, those error messages appear in dmesg, and SuperSpeed is not detected when plugging in a USB 3 device.
4. Upon kexec, if "avoid_reset_quirk" attribute is not set, the xhci controller will not be detected again until a full reboot.
5. If a system shutdown is requested (go to S5), the system will bounce back to S0 and reboot.
In conclusion, the workaround is: (Linux)
1. Enable USB per-port override in BIOS, setting all ports to "Enabled".
2. Keep a USB 3 device plugged into a USB 3 port before power on (or kernel boot up?).
Can be a USB 3 hub or something
3. Set "avoid_reset_quirk" in sysfs to "1".
Probably firmware bug. BIOS version 2024-06-24.
Anyone else have this problem? Or is there a better workaround?
When looking at what you all know today would you buy the N305 board again? Looks sweet and ticks (really) all the boxes but when I read about picky memory, C-state settings, and USB problems I wonder if I should really try one of these or stick with a board from a more reputable brand, e.g. Asrock N100.
Combed through BIOS setup again and I found the setting:
In Chipset -> System Agent (SA) Configuration -> TCSS setup menu, set "D3 Cold Enable/Disable" to "Disabled"
That's it. This prevents the Thunderbolt 4 USB Controller from going into D3cold and becoming unresponsive.
No, didn't report.
Well... it really ticked all the boxes and at the right price. Even more boxes than the Asrock N100. Tempted.
Would prefer less head banging and cursing, though.
I would always go with more well-known and respectable brands. However, the pricing is good and at the time of my purchase, even today, a similar featured motherboard cannot be found. It's not meant for high end, but for home usage it's perfect. It has it quirks and the bios is outright bad, but I have just grown to live with it.
Mine have been running since February (first availability of the first nas boards) with no technical downtime. I am very happy with the setup today. Should a board come from well-known and respectable brand, I would consider changing if there are significant power savings and if the return of investments is reasonable. That is not very likely though.
Mine have been running since February (first availability of the first nas boards) with no technical downtime. I am very happy with the setup today. Should a board come from well-known and respectable brand, I would consider changing if there are significant power savings and if the return of investments is reasonable. That is not very likely though.
I've been running my purple N305 for two months now – no issue whatsoever.
Had a bit of misconfiguration in BIOS for USB, making them all USB2, but that was my fault and easily fixable.
Really grear value for the money.
My setup in JonsboN3, 4X HDD - Baracuda Pro Ent, 2x NVME and HDD Fans - consume about 26W in idle (i was hoping for a bit less to be honest) and go up to 70-80W at peak load.
Had a bit of misconfiguration in BIOS for USB, making them all USB2, but that was my fault and easily fixable.
Really grear value for the money.
My setup in JonsboN3, 4X HDD - Baracuda Pro Ent, 2x NVME and HDD Fans - consume about 26W in idle (i was hoping for a bit less to be honest) and go up to 70-80W at peak load.
I'm really curious here.
What was the setting in question? From your previous post, it's something "Legacy", not the TCSS D3cold one.
Is TCSS D3cold enabled in your system? If it's enabled, can you use USB 3 if booted without any USB 3 devices already plugged in?
Does your board also have problem with D3cold?
Those two boards seem to have JMB585 for SATA and might not be able to reach deeper C-states.
That may or may not impact your power consumption.
Yes, it was "Legacy". When I had it enabled – it dropped all the ports to the USB 2 mode.
I'll check about plunging USB3 after boot.
What is TCSS D3cold?
Is it Advanced -> USB Configuration -> Legacy USB Support?
I'm talking about Chipset -> System Agent (SA) Configuration -> TCSS setup menu -> D3 Cold Enable/Disable
TCSS probably means (Intel) (USB) Type C SubSystem.
D3cold is a device (deep) power saving state.
See Device Low-Power States - Windows drivers
For context, see my previous posts on page 35-36 in this thread.
Sorry for the delay. Just got back home.
It is interesting, but I think you are right. I just plugged USB3 stick to the port of running NAS, and it only shows as USB2.
Can't check the BIOS right now, as I need to move it to the location with the monitor.
Yes, this one.
It is interesting, but I think you are right. I just plugged USB3 stick to the port of running NAS, and it only shows as USB2.
Can't check the BIOS right now, as I need to move it to the location with the monitor.
That confirms I'm not the only one with this problem. Good to know.
I think I have enough information now.
TL;DR
Everyone with a purple CWWK board, verify that your USB 3 interfaces are actually working.
The issue manifests if no USB 3 device is plugged before power on. Or at kexec.
The BIOS setting to disable is
Chipset -> System Agent (SA) Configuration -> TCSS setup menu -> D3 Cold Enable/Disable.Advanced -> USB Configuration -> Legacy USB Support is probably a red herring.Now for the details.
1. Power off the system. AKA power state S5.
2. Unplug all USB devices from USB 3 ports.
3. Power on the system. AKA power state S0.
4. Wait until the OS boots. Here, Linux will spit out errors about not being able to bring the Thunderbolt USB controller from D3cold to D0.
5. Plug in a USB 3 device to one of USB 3 ports.
6. Observe that it only works as USB 2 or, if it's a "tricky" device like a Western Digital external hard disk, not detected at all.
7. Perform a reboot of Linux kernel via kexec.
8. At shutdown, Linux kernel tries to reset all devices, and fail when it comes around to the USB controller with a "host halt" error in dmesg.
9. Observe that the newly booted Linux kernel cannot detect the Thunderbolt USB controller at all.
10. Shutdown from Linux (poweroff)
11. Observe that the computer bounces right back to power on.
My hypothesis:
- BIOS (UEFI) sees nothing connected to the Thunderbolt USB Controller.
- BIOS puts the USB Controller into D3cold, but somehow leave the PCI device visible. (?)
- Kernel tries to bring up the controller, fail.
- Kernel tries to halt everything at shutdown, but the kexeced kernel tries to reinitialize everything.
- TCSS firmware triggers PCI PME# after poweroff, waking the system from S5.
Conclusion:
This is most likely a bug in the TCSS firmware.
Can be worked around by disabling D3cold.
See this Linux Kernel Bugzilla
1. Power off the system. AKA power state S5.
2. Unplug all USB devices from USB 3 ports.
3. Power on the system. AKA power state S0.
4. Wait until the OS boots. Here, Linux will spit out errors about not being able to bring the Thunderbolt USB controller from D3cold to D0.
5. Plug in a USB 3 device to one of USB 3 ports.
6. Observe that it only works as USB 2 or, if it's a "tricky" device like a Western Digital external hard disk, not detected at all.
7. Perform a reboot of Linux kernel via kexec.
8. At shutdown, Linux kernel tries to reset all devices, and fail when it comes around to the USB controller with a "host halt" error in dmesg.
9. Observe that the newly booted Linux kernel cannot detect the Thunderbolt USB controller at all.
10. Shutdown from Linux (poweroff)
11. Observe that the computer bounces right back to power on.
My hypothesis:
- BIOS (UEFI) sees nothing connected to the Thunderbolt USB Controller.
- BIOS puts the USB Controller into D3cold, but somehow leave the PCI device visible. (?)
- Kernel tries to bring up the controller, fail.
- Kernel tries to halt everything at shutdown, but the kexeced kernel tries to reinitialize everything.
- TCSS firmware triggers PCI PME# after poweroff, waking the system from S5.
Conclusion:
This is most likely a bug in the TCSS firmware.
Can be worked around by disabling D3cold.
See this Linux Kernel Bugzilla
Another issue I'm seeing...
I can't seem to enable
Chipset -> System Agent (SA) Configuration -> GNA Device (B0:D8:F0).Tried setting it to Enabled then Save and Exit, but no GNA device showed up on lspci.
Bizarrely, when I reenter the BIOS setup again, the setting is Disabled.
Does anyone else have this problem?
P.S. ASPM settings in PCH-IO Configuration get reset to Disabled every time you enter BIOS Setup.
Hi everyone!
I've purchased the purple CW-NAS-ADLN-K board from an aliexpress seller (Topton computer store) and I have some trouble: I can boot from an USB drive and install OS to M.2 SSD, but I can't boot from the SSD with OS, there is no such boot option
BIOS from the box:
BIOS vendor: CWWK
Core version: UEFI 2.8; PI 1.7
Compliancy: CW-NAS-ADLN-K V10
What can be wrong?
I've purchased the purple CW-NAS-ADLN-K board from an aliexpress seller (Topton computer store) and I have some trouble: I can boot from an USB drive and install OS to M.2 SSD, but I can't boot from the SSD with OS, there is no such boot option
BIOS from the box:
BIOS vendor: CWWK
Core version: UEFI 2.8; PI 1.7
Compliancy: CW-NAS-ADLN-K V10
What can be wrong?
There are two BIOSes for this board: one for sata and one for nvme boot. Go to board official page and check bios and drivers. There you would find details and ISOs for both bios types.
I have SATA SSD and M.2 NVMe SSD and I have installed OS on both, but boot is unavailable neither from SATA nor from NVMe
I can see NVMe in the corresponding section, but not in boot menu