Dazog

Hopefully slackbuilds releases 418.43 soon to patch the CVE: https://nvidia.custhelp.com/app/answers/detail/a_id/4772

I wonder if this can be included some how to control fan speeds: https://github.com/nan0s7/nfancurve

Has anyone figured out how to monitor this in Netdata or through telegraf to Grafana? Instead of having the smi window open? I found this docker: https://github.com/D34DC3N73R/netdata-glibc Cannot get it to display any of the gpu stats

Ok, not complaining I doubt many people are using expensive Turing cards for this yet

Thanks for the info. Slackbuilds shows 418.30 posted. I would wait until next month when Geforce 1660Ti cards come out. Because 418.30 and above supports Turing Streaming for new cards with New Nvidia Video Codec SDK 9 https://developer.nvidia.com/nvidia-video-codec-sdk

CVE's oustanding as of RC4: Curl has a few CVE's again. Latest is at 7.64. Oniguruma is at version 6.9.1 (5.9.6_p1) has multiple CVE's

5.10.19 is out https://community.ubnt.com/t5/UniFi-Beta-Blog/UniFi-Network-Controller-5-10-19-Stable-Candidate-has-been/ba-p/2680361

I love the new design. HATE the old win95 icons and colors. I think what we need to do is create a thread in the requests section asking nicely for support for people to theme the system themselves.

Is the nvidia driver going to stay on the LTS branch and will the driver be updated to follow unraid releases or when you guy see fit. Thanks again for the hard work is the least I can say honestly.

The best answer would be to roll back to stable. They are looking into it and remember we jumped kernel releases. Since unraid is used in different ways then any distro, we see different issue than some of the distro users see. Sometimes being on the cutting edge has disadvantages in edge cases. I would wait to test again once the devs can figure if its an unraid or upstream issue.

Quadro FX 3800 is 10 years old... It doesn't have the hardware encode/decode required. Refer to this: https://developer.nvidia.com/video-encode-decode-gpu-support-matrix if it's not on there. It's not going to work.

https://bugzilla.kernel.org/show_bug.cgi?id=202055#c38

This is getting patched in the kernel. Not something Unraid can fix. If you read the bugzilla someone fixed it for 4.20 and possibly back-ported to 4.19 and I assume ported to 5.0 Have to wait.

Last we were told is 4.20 is aim with possible 5.0 depending on when it is finalized.