- This topic has 3 replies, 2 voices, and was last updated 2 days, 8 hours ago by
.
-
Posts
-
On two Fedora 44 machines with NVENC-capable NVIDIA GPUs, NoMachine 9.8.2 never uses the hardware encoder for physical-desktop connections. nvidia-smi reports the encoder engine at 0% and 0 encoder sessions at all times, while nxcodec.bin consistently burns 15-32% of a CPU core doing software encoding. NVENC on the same machine is verifiably functional — ffmpeg drives the encoder engine to 88% on demand. This appears to contradict KB article AR01T01151, which states GPU-accelerated video encoding is “always used, where available, when connecting to the physical display… This is the typical case of connections to the Enterprise Desktop or to the free edition of NoMachine.” I’m running latest Fedora kde x11 on both and NoMachine (server) 9.8.2-2 x86_64, built Wed Jul 8 2026. Pls see attached md file for all the details. It looks like whether I use 1 monitor (1920×1080) or dual (3840×1080) the HW Encoder doesn’t work and thus consumes excessive CPU.
Can you send us the full set of logs taken from the host you are connecting to? Go to Settings > Server Settings > Security, scroll down and Take logs. Send us the whole file. You can send it to forum[at]nomachine[dot]com or attach here. If you are sending it via email, please use the topic of this title as the subject of your email. Thanks!
Thank you, here is the file attached with below instructions given the file was 3.2MB. NoMachine Server Logs – File Reconstruction
Instructions ========================================================
OVERVIEW
The original Server logs zip file (3.2 MB) has been split into 4 smaller parts to accommodate the 1 MB upload file size limit. All parts must be downloaded before attempting reconstruction. PARTS INCLUDED ————– • nomachine_logs_part_aa (800 KB) • nomachine_logs_part_ab (800 KB) • nomachine_logs_part_ac (800 KB) • nomachine_logs_part_ad_combined (826 KB)
RECONSTRUCTION INSTRUCTIONS
On Linux/macOS: 1. Place all 4 part files in the same directory 2. Open a terminal in that directory 3. Run this command: cat nomachine_logs_part_aa nomachine_logs_part_ab nomachine_logs_part_ac nomachine_logs_part_ad_combined > “Server logs 2026-07-27 11.58.04.zip” 4. The original zip file will be recreated On Windows (Command Prompt): 1. Place all 4 part files in the same directory 2. Open Command Prompt and navigate to that directory 3. Run this command: copy /b nomachine_logs_part_aa + nomachine_logs_part_ab + nomachine_logs_part_ac + nomachine_logs_part_ad_combined “Server logs 2026-07-27 11.58.04.zip” 4. The original zip file will be recreated On Windows (PowerShell): 1. Place all 4 part files in the same directory 2. Open PowerShell and navigate to that directory 3. Run this command: Get-Content nomachine_logs_part_aa, nomachine_logs_part_ab, nomachine_logs_part_ac, nomachine_logs_part_ad_combined -ReadCount 0 -Encoding Byte | Set-Content -Encoding Byte “Server logs 2026-07-27 11.58.04.zip” 4. The original zip file will be recreated
VERIFICATION
After reconstruction, verify the file size is approximately 3.2 MB. The zip file can then be extracted normally using your preferred archive tool.
IMPORTANT NOTES
All 4 parts must be present and in order (aa, ab, ac, ad_combined) • Do not modify or rename the part files before reconstruction • Download the parts in order if using a browser interface
Hi, thanks for those. Logs confirm an already known issue: https://kb.nomachine.com/TR02X11706 which also includes a temporary workaround. The fix is going to be included in NoMachine 10, coming soon.