Search results for query: n5105

I have a HUNSN RJ03 that uses a Changwang v5 board. Has anyone tried to update their BIOS with their ISO? Any issues?

Looks like Changwang (CWWK) is starting to update their BIOS for the JasperLake miniPCs Please note this is for the N5105 v3 v4 v5 (4 LAN Ports). Hopefully, the others will follow. (Google Translate) Updated the microcode issued by Intel on February 14, 2023, Fixed the 11th generation...

There were lots of problems with N5105. It's a very lot thread and I don't know if they are fixed or worked around.

I am running proxmox on a Aliexpress N5105 with 4 x i226 NiCs and 16gb RAM (1x16gb module) and OPNSense in a VM. every 5 days or so it fails and I cannot seem to be able to restart the VM without powering off the box with the physical switch. I have tried restarting VM in proxmox and...

Thanks for all your work guys! Fingers crossed for me that microcode 0x24000024 does the trick, like everyone said 0x24000023 improved things marginally but still have had occasional freezes. Just updated to 0x24000024. (edit: N5105 btw)

It's a n5105 box with 4 NICs running Proxmox and pfSense is a VM on this Proxmox

...und Backup Privat testen um meinen eigenen Horizont zu erweitern. 1.) Jetzt frage ich mich ob es bei der Hardware Sinn macht ein Mainboard mit mehreren Lan Anschlüssen zu nehmen? 2.) Langt eine N5105 CPU? Ich dachte an so ein Board da ich dieses in ein kleines 19 Zoll Gehäuse packen könnte.

Again ALL OK !!!!! :) N5105, 16gb kingston, ssd 980 500gb + hdd 1.75tb samsung root@pve:~# uptime 21:45:24 up 20 days, 7:15, root@pve:~# cat /proc/cmdline BOOT_IMAGE=/boot/vmlinuz-6.1.15-1-pve root=/dev/mapper/pve-root ro quiet intel_iommu=on root@pve:~# pveversion pve-manager/7.4-3/9002ab8a...

Hi So due to the recent reports of success with kernel 6.2 and microcode 0x24000024 I decided to give it a try. System: Intel N5105, MB: CW-N6000 (from Topton, MB is obviously from Changwang), 4x i225 B3, 2x8GB, 1x SSD NVMe from WesternDigital. Before I was running the kernel 6.1 with the...

My uptime is currently "up 2 weeks, 3 days, 2 hours, 55 minutes" on a Beelink U59 (with N5105). Previous uptime prior to the changes below was never more than 6 hours. Changes I made: Upgrade Ubuntu VM kernel to 6.2 wget...

...power management to "max battery" and that's when pfsense started crashing nightly. So this problem with pfsense crashing is not strictly an N5105 problem... it happens with J6413 as well. In my environment, I know the setup required to crash pfsense. So after I updated proxmox to 7.4...

@ckl Sorry to hear about that, it is actually the first time I am hearing that J6413 has the same issues with the N5095/N5105/N6005. What Kernel version are you on? Have you tried upgrading it to 6.1? I do know that the 12th Gen and 13th Gen processors require Kernel 6.1 and above to properly...

Came here to say thanks, and share my success in getting Plesk HW transcoding. Beelink Intel N5105 16GB ram Proxmox 7.3 (updating kernel as instructed in this thread) LXC container running Ubuntu 22.04 CPU usage at 60% while HW transcoding a 4k movie & DVR recording live TV GPU usage between...

which package contains cpupower? When I try to run it I get "Unable to locate package cpupower"[/CODE]

Hi there, Small contribution to this thread. Running Proxmox on a Odroid H3 (Intel N5105). 4 x Intel(R) Celeron(R) N5105 @ 2.00GHz (1 Socket) Linux 6.2.6-1-pve #1 SMP PREEMPT_DYNAMIC PVE 6.2.6-1 (2023-03-14T17:08Z) GRUB_CMDLINE_LINUX_DEFAULT="intel_iommu=on pcie_aspm.policy=performance...

Sounds good, I assume I will need a reboot for the new microcode?

i can only speak from my point of view. i was running 6.1.2 on my n5105 box since it came out and then immediately switched to 6.2.2 (havent rebooted since for even newer kernel) and havent noticed any negative effects, but i am not using features such as gpu passthrough or anything, so others...

...the command did not return anything: root@pve:~# cat /proc/cpuinfo|grep 'microcode\|model name' model name : Intel(R) Celeron(R) N5105 @ 2.00GHz microcode : 0x1d model name : Intel(R) Celeron(R) N5105 @ 2.00GHz microcode : 0x1d model name : Intel(R) Celeron(R)...

...powersave or performance. the longest i could go without any vm dying was about 10 days. but on average every 3-5 days something died on my n5105 box. since installing the version 24 microcode i havent had any vms die on me except opnsense, which didnt die, but has some weird issue with...

the 23 microcode will most likely not solve your issues permanently. at least that seems to be the consens in thsi thread. the 24 microcode on the other seems to be the fix we wanted for these cpu's. at least some of us are already on several weeks uptime on their vm's with it :)