2 hours ago, Rkpaxam said:

Hi Since upgrading to 7.0 now 7.1.2 i keep getting an error saying its failed to download the updated driver, it then borks the GPU and the whole system needs to be rebooted for the GPU to be recognised

Can you please give me a few screenshots or do you know the exact message?

Diagnostics would also help.

If we are talking about the automatic update because you are on the latest branch then this even won't bork your system because it would simply remove the new driver which failed to download and the old driver will be still be running, you always have to reboot to switch drivers, the plugin on it's own never does a update from the drive when it's running.

2 hours ago, Rkpaxam said:

Any ideas what the issue is?

Diagnostics after the error message would maybe help or the exact error message itself.

On 5/30/2025 at 12:08 PM, ich777 said:

Can you please give me a few screenshots or do you know the exact message?

Diagnostics would also help.

If we are talking about the automatic update because you are on the latest branch then this even won't bork your system because it would simply remove the new driver which failed to download and the old driver will be still be running, you always have to reboot to switch drivers, the plugin on it's own never does a update from the drive when it's running.

Diagnostics after the error message would maybe help or the exact error message itself.

Not the original poster but I am having the error after updating. Weird part is it is trying to download v565.77 but I am choosing v575.57.08 . Diagnotstics attached.

Thanks for the fix below. Sorry I missed it the first time.

theblender-diagnostics-20250602-2335.zip

Edited June 3, 20251 yr by ChuckBuilds
Missed announcement about known error

2 hours ago, ChuckBuilds said:

Not the original poster but I am having the error after updating. Weird part is it is trying to download v565.77 but I am choosing v575.57.08 . Diagnotstics attached.

Please see this post:

On 5/30/2025 at 6:08 PM, ich777 said:

Can you please give me a few screenshots or do you know the exact message?

Diagnostics would also help.

If we are talking about the automatic update because you are on the latest branch then this even won't bork your system because it would simply remove the new driver which failed to download and the old driver will be still be running, you always have to reboot to switch drivers, the plugin on it's own never does a update from the drive when it's running.

Diagnostics after the error message would maybe help or the exact error message itself.

Sorry its took a few days for it to come back up Please find attached. As before due to this happening the GPU is now not recconised and I will have to change to another driver and reboot to get it to work.

tower-diagnostics-20250603-1021.zip

10 hours ago, Rkpaxam said:

Apologies for me-tooing this, but I'm getting the same error, and have now as a result noticed numerous plugin updates are failing for "generic" reasons... I'll follow this thread, and if anyone is feeling generous with their time and knowledge, I've attached my own diagnostics file. Thanks! :)

ungreg-diagnostics-20250603-1208.zip

11 hours ago, flyingqueso said:

Apologies for me-tooing this, but I'm getting the same error, and have now as a result noticed numerous plugin updates are failing for "generic" reasons... I'll follow this thread, and if anyone is feeling generous with their time and knowledge, I've attached my own diagnostics file. Thanks! :)

21 hours ago, Rkpaxam said:

Sorry its took a few days for it to come back up Please find attached. As before due to this happening the GPU is now not recconised and I will have to change to another driver and reboot to get it to work.

Do both of you use Unifi gear by any chance? If yes please check your IDS/IPS rules and logs if there are any hints in there.

The driver is pulled from GitHub making a GitHub API Call and then the download from GitHub is initiated, there is nothing more to it.

However what I noticed lately that GitHub Downloads can be at times, from certain regions in the World, be very unreliable.

I'm not sure what causes this but these are the main reasons what could cause the download to fail:

• No left GitHub API calls for your IP (60 per hour)

• Unreliable Download from GitHub

• Insufficient disk space on your USB Boot Device

3 hours ago, ich777 said:

Do both of you use Unifi gear by any chance? If yes please check your IDS/IPS rules and logs if there are any hints in there.

The driver is pulled from GitHub making a GitHub API Call and then the download from GitHub is initiated, there is nothing more to it.

However what I noticed lately that GitHub Downloads can be at times, from certain regions in the World, be very unreliable.

I'm not sure what causes this but these are the main reasons what could cause the download to fail:

• No left GitHub API calls for your IP (60 per hour)

• Unreliable Download from GitHub

• Insufficient disk space on your USB Boot Device

Im using Opensene router with crowdsec & Geoblock and TP link (TP link does not interact with unraid server on the network) with some AGH instances (however the server is on a bypass from these due to reasons). but never had this issue before the upgrade to 7.0 and have no other issues with Github downloads.
And as I can still download the file manually I cant believe those are related to my issue at least.

No issues with the USB plenty of space and no other failings.

For now I have stuck it on a specific driver so it shouldn't try to update.

As it's only transcoding I can't see being a few drivers being being an issue.

Edited June 4, 20251 yr by Rkpaxam

12 hours ago, ich777 said:

Do both of you use Unifi gear by any chance?

• No left GitHub API calls for your IP (60 per hour)

• Unreliable Download from GitHub

• Insufficient disk space on your USB Boot Device

Yeah, sure do. Opened up the regions I had blocked and that didn't help, one of my plug-in updates specifically fails to download from GitHub, but I think you're on to something with the boot drive. I've suspected a problem with it and have a replacement coming later today. Hopefully that is my solution.

1 hour ago, flyingqueso said:

Yeah, sure do. Opened up the regions I had blocked and that didn't help, one of my plug-in updates specifically fails to download from GitHub, but I think you're on to something with the boot drive. I've suspected a problem with it and have a replacement coming later today. Hopefully that is my solution.

I've just selected a driver and told it not to auto update and I will manually do it as I want to.

I personally can't see it being my USB or isp setup as this issue only started with 7.0.

The fact it is multiple people with the same issue would lead me to think either unraid, plugin or hardware issue with the newer kernel

Hey all.

I'm also affected by the RTX 5070 driver situation.

Any info on when (or if) the open source 575.57.08 driver will be released?

2 hours ago, drkmtr said:

I'm also affected by the RTX 5070 driver situation.

What situation?

On what Unraid version are you on?

4 hours ago, ich777 said:

What situation?

On what Unraid version are you on?

I'm on UNRAID 7.1.2, and restricted to using the open source driver with my RTX 5070. However CUDA does not work on version 570.144. I read somewhere that 575.57.08 has better support for CUDA.

5 hours ago, drkmtr said:

I'm on UNRAID 7.1.2, and restricted to using the open source driver with my RTX 5070. However CUDA does not work on version 570.144. I read somewhere that 575.57.08 has better support for CUDA.

Open source drivers are compiled once when a new Unraid version is released, you can upgrade to 7.1.3 and there you should have the driver.

Seems that the nvtop plugin is also linked to this thread for support. Just came to ask if there's any plans to bump nvtop to the latest version?

7 hours ago, ich777 said:

Open source drivers are compiled once when a new Unraid version is released, you can upgrade to 7.1.3 and there you should have the driver.

i assume users are maystuck here

opensource says latest 570.144

while on available versions there is no choice to choose between regular and opensource

Is it possible to keep a certain version in the driver version option for a long time?

Allow me to describe the benefits of doing this:
The Nvidia Driver plugin currently keeps updating the host driver version in a rolling fashion, and each time I update the system version, the Nvidia Driver plugin forces me to install the new host driver. This creates a number of problems, and I've already seen some feedback about incompatibility with older Kepler cards, as well as problems with some people's Docker apps.

In my development workflow, I've long used a combination of LXC and Nvidia Driver to get both a VM-like experience and GPU compute power, but having to have the same version of the userspace driver installed in the LXC container as the Unraid host also forces me to update the driver one-by-one for each LXC container every time I update the Unraid system and the Nvidia driver. In the most recent update, my LXC development environment was completely destroyed. I'm sure this is a huge nuisance to those who have had similar experiences as me as well.

I understand that compiling a large number of driver versions for each unraid version is a difficult thing to do, which is the main reason why the nvidia driver plugin is in a rolling mode, but I'm sure it's not too difficult to maintain just one additional version, and if you're still not willing to support this request, perhaps you could explain the driver compilation process in a note that would allow me to do this myself?
Much appreciated!

18 hours ago, ich777 said:

Open source drivers are compiled once when a new Unraid version is released, you can upgrade to 7.1.3 and there you should have the driver.

Latest open source driver on your repo is nvos-570.153.02-6.12.30-Unraid-1.txz

Is there a timeframe for 575.57.08? https://github.com/NVIDIA/open-gpu-kernel-modules/releases/tag/575.57.08

41 minutes ago, drkmtr said:

Is there a timeframe for 575.57.08? https://github.com/NVIDIA/open-gpu-kernel-modules/releases/tag/575.57.08

Nope, not yet since this requires almost a complete rewrite from the plugin.

6 hours ago, Un1kk said:

that would allow me to do this myself?

It's all open source:

https://github.com/ich777/unraid_kernel

https://github.com/unraid/unraid-nvidia-driver

Just look into the source folder from the Nvidia-Driver repo.

6 hours ago, Un1kk said:

Is it possible to keep a certain version in the driver version option for a long time?

Sure, don't set it to latest and set a static version in the plugin settings.

14 hours ago, porter83 said:

Seems that the nvtop plugin is also linked to this thread for support. Just came to ask if there's any plans to bump nvtop to the latest version?

Done.

On 6/4/2025 at 10:43 PM, Rkpaxam said:

I personally can't see it being my USB or isp setup as this issue only started with 7.0.

Nothing changed how the plugin works also I can't imagine that a Kernel update or similar is the cause of the issue and it is definitely working for most people since otherwise more people would comment here.

The plugin relies on pure bash script language and nothing changed there.

1 hour ago, ich777 said:

Nothing changed how the plugin works also I can't imagine that a Kernel update or similar is the cause of the issue and it is definitely working for most people since otherwise more people would comment here.

The plugin relies on pure bash script language and nothing changed there.

Ok so i think i found the issue, whilst my unraid is whitlisted in my AGH instance it seems to be having issues randomly so i have gone back to the data harvesters that are google and all is well.

1 hour ago, ich777 said:

don't set it to latest and set a static version in the plugin settings

You may have misunderstood me, so let me illustrate this point with an example.

Suppose I was previously on unraid 7.0 (Kernel 6.6.78), at which point I could select driver version 550.142 in avaliable versions (not the LATEST versions), now when I upgraded to 7.1.3 (Kernel 6.12.24), the system automatically upgraded my driver to the latest 570.144 in the background, and the process is irrevocable because after updating the system, the 550.142 option also disappears. As you can see from your Github Release, you don't have a 550.142 driver for Unraid 7.1.3 at all.

https://github.com/unraid/unraid-nvidia-driver/releases/tag/6.6.78-Unraid

https://github.com/unraid/unraid-nvidia-driver/releases/tag/6.12.24-Unraid

That is, if I understand you correctly, keeping a static version before and after updating the system is not achievable

2 hours ago, ich777 said:

Just look into the source folder from the Nvidia-Driver repo

Thank you for your instructions, that said, I would like to know what you think of my suggestion. I'm sure if you could take this on board, this could make your plugin better and help more people!

26 minutes ago, Un1kk said:

That is, if I understand you correctly, keeping a static version before and after updating the system is not achievable

may i see it wrong, but you already have some "spare" versions always which you can use, and meanwhile update your apps before the next major jump comes ? or do i missunderstand something here ?

from my other post upper (different question, but there are the currently available versions ...)

if i see it corrent, may rather lower the update frequency of your apps ? there are 4 backwards versions now ?