You are not logged in.
I was asking if you could upgrade the driver on the proxmox host.
Offline
I have tried multiple other drivers in the 16 range and all of them give me the same error.
17.3 550.90.07 https://storage.googleapis.com/nvidia-d … 7-grid.run
17.2 550.90.07 https://storage.googleapis.com/nvidia-d … 7-grid.run
17.1 550.54.15 https://storage.googleapis.com/nvidia-d … 5-grid.run
17.0 550.54.14 https://storage.googleapis.com/nvidia-d … 4-grid.run
16.7 535.183.06 https://storage.googleapis.com/nvidia-d … 6-grid.run
16.6 535.183.01 https://storage.googleapis.com/nvidia-d … 1-grid.run
16.5 535.161.08 https://storage.googleapis.com/nvidia-d … 8-grid.run
16.4 535.161.07 https://storage.googleapis.com/nvidia-d … 7-grid.run
Offline
and no the quadro p400 only supports 16.4 and i tried to install all of these drivers listed and none of them work on my arch vm. The fail to build kernel. How do i go about patching driver?
Offline
Adapt the 535 drivers to use 535.161.07-grid:
git clone https://aur.archlinux.org/nvidia-535xx-utils.git
cd nvidia-535xx-utils/
curl -o PKGBUILD.diff http://0x0.st/XJ0g.diff
git apply -v PKGBUILD.diff
makepkg -rsi
Last edited by loqs (2024-08-21 03:11:00)
Offline
can you explain how this works. Crazy you can do things like this. Also if i have a kernel update will dkms keep the driver alive? or do i need to do this everytime? Also it works as far as i can tell i enabled kernel parameters and i even have wayland working.
Offline
also will that link stay active? Im restoring my other machine now to install on both might take a while though.
Offline
Also if i have a kernel update will dkms keep the driver alive?
Until you need a patch for that newer kernel, eventually the dkms rebuild will fail.
Using the LTS kernel will likely be a smoother sail (though it has happened that they inverted and the LTS kernel was newer than the main one in the repos)
also will that link stay active?
https://0x0.st/ - see the retention calculation, but you can just locally keep it.
Offline
how do i keep it locally?
Offline
Offline
Nice im guessing you just mean to copy the build folder and keep it somewhere safe.
Offline
So quick update. When i first boot the vms everything is snappy my remote desktop works perfect. After the vm sits unused for a few minutes remoting back in is not usable it is so laggy. Any suggestions? As soon as i reboot it is good and if i ssh into it that seems fine its just the gui.
Offline
You don't need to copy the build folder, only the patch that one day >> 1y will disappear from 0x0.st (and that will actually easily fit on a floppy, if you have such drive )
When the VM turns slow, does the GPU still respond to nvidia-smi?
Offline
Yes. Nvidia still shows in SSH session. But it is unbarable how slow it is.
Offline
Check whether it still powers up when taxing it.
Please open a new thread for this and also elaborate the context and symptoms ("slow" at what? Doom? xterm? some compositor? Do you use vsync?)
Offline
One last thing before i start a new thread. Before i switched to arch. On debian the original driver worked perfect. With that being said with the original driver i had a lot of systemctl services related to gridd. with the patched driver there is no service on my system related to gridd. is there any way to patch the original grid driver so i have all of the stuff it included?
Offline
also after further testing. I install glmark2 and as soon as i run it performance on vm craps out and lags bad.
Offline
Is there away to apply the patch to the nvidia gridd driver. Once i extract the folder is there a way i can put patch inside and rebuild it?
Offline
loqs patch does exactly that.
- "https://us.download.nvidia.com/XFree86/Linux-x86_64/${pkgver}/${_pkg}.run")
+ '0003-Fix-conftest-to-use-nv_drm_gem_vmap-which-has-the-se.patch'
+ "https://storage.googleapis.com/nvidia-drivers-us-public/GRID/vGPU16.4/${_pkg}.run")
i had a lot of systemctl services related to gridd. with the patched driver there is no service on my system related to gridd
Please don't paraphrase, https://bbs.archlinux.org/viewtopic.php?id=57855 - what "services related to gridd."? What makes you believe they're part of that driver?
The nvidia install scripts have a feature to repacakge themselves with applying a patch, check "--help"
That being said: Simply use the LTS kernel?
Offline
Before i ran arch i installed the same driver on debian. It worked without a hitch and it had a service called gridd. I dont remember everything but there is forsure stuff missing. I deleted all of my debian vms because i expected it to work the same on arch.
Offline
And a kernel from yesteryear…
Use. The. LTS. Kernel.
It's gonna allow you to build the modules from the runtime installer and provide a reference point.
Edit: https://docs.nvidia.com/vgpu/13.0/grid- … index.html
Last edited by seth (2024-08-25 06:39:33)
Offline
I will try that tonight... Sorry this has been a hasell. I like arch more for desktop based distro. My Debian is used for servers only now. With no desktop environment.
Also if all else fails i uses a docker contain that hosts remmina publicly and i can give one of you guys access remotely to this thing...
Last edited by awptechnologies (2024-08-25 14:05:11)
Offline
Even with the lts kernel it still fails to build. Sorry this is so late just now have time to mess with it...
Offline
im just confused on why this driver worked perfect on debian but not arch.
Offline
And a kernel from yesteryear…
Fails to build "how"?
Build log?
Please don't paraphrase, https://bbs.archlinux.org/viewtopic.php?id=57855
Blogging about your general confusion won't get you ahead with this…
Offline
how do i post it as a link since the log is so big. Its annoying to go through and delete certain parts.
Offline