@chripo, I would be interested to compare BIOS settings with you, and am curious which Linux distro you are using. I just got this board (CWWK-ADLK-NAS-V10) w/ the N305 CPU, and I've been struggling to get it booting for several days. The only components connected are a Samsung 970 EVO Plus, and a 32GB stick of RAM (
https://www.amazon.com/dp/B09XB3ZNHC). It boots Windows 11, but not Linux. All of the recent installers that I tried (Debian 12, Ubuntu 23.10, Proxmox 8.1, Fedora 39) cause the system to hard-reboot about a second after grub starts booting the kernel. This hard-reboot is a brief power-off and then back on. After much troubleshooting with different operating systems, different Linux distributions, and even bisecting the kernel via git (a process that took the better part of a day), I have the problem somewhat isolated, but I'm not sure how best to resolve it.
Basically, all kernels since 6.1 fail to boot (causing this reboot loop). After discovering that I could boot an old Debian 11 installer, I bisected the problem down to this commit:
Merge branches 'pm-cpuidle', 'pm-core', 'pm-sleep' and 'powercap' · torvalds/linux@ac73ce3. Finding that this is a power management problem, I further reduced the problem to having C-states greater than 2 enabled in the intel_idle driver. Any of these kernel parameters will work around the problem:
- idle=nomwait (which disables the intel_idle driver)
- intel_idle.max_cstate=2
- intel_idle.states_off=28 (which disables state 2,3,4, and leaves states 0 and 1 enabled).
I have spent a fair bit of time poking around in the BIOS. Using the factory default settings, the parameter that sounds like it controls C-states (Advanced -> Power and Performance -> CPU - Power Management Control -> C States) was 'Disabled' by default. I enabled it, but the system fails to boot regardless of how it is set, and surprisingly with the default of 'Disabled', it still looks like the C1E state is being used according to 'powertop'.
I would like to find a BIOS setting that allows the kernel to boot unaltered. Overall, this seems like a BIOS bug to me, or maybe I've got a bad board. The BIOS defaults should be "safe". I'm surprised a BIOS would be shipped that can't boot a stock Debian, Ubuntu, Proxmox, or Fedora (with the exception of turning off secure boot maybe). I have no idea if the manufacturer would respond if I try to contact them about it. I would not have high hopes considering this was an aliexpress purchase.
On the off chance it is related to the RAM (which is unlikely, as I ran a full Memtest86+ without issues), I have an alternate stick coming in the mail tomorrow. I doubt it is related, but it is the only component attached to the motherboard that I haven't tried removing or replacing.