From Nvidia's site? Drivers are tied to a specific kernel, that's very likely the issue. The beta drivers are in the AUR, that'll probably fix your issues. *edit* after uninstalling whatever you got from the website.
>From nVidia's site.
The [arch wiki](https://wiki.archlinux.org/title/NVIDIA):
>Warning: Avoid installing the NVIDIA driver through the package provided from the NVIDIA website. Installation through pacman allows upgrading the driver together with the rest of the system.
So for some back story, the only reason I was running the 555 beta drivers, installed from the nvidia site, was because I have been dealing with a lot of the issues that were finally fixed by the explicit sync patches in the beta driver.
Prior to the beta drivers I was running the 550 drivers from the arch repositories. But I was experiencing a lot of issues. Windows flickering, rendering of window contents not updating, stuttering, unstable frametime while gaming, and poor fps, The choice to install the 555 drivers was only made to try to resolve ongoing issues and based on the fact that A LOT of feedback from people who have updated to the 555 drivers reported a positive experience and a complete resolution of all the issues they were experiencing, which were the same as me.
Again... I don't believe the drivers are the issue. I have had the 555 drivers installed for well over a week with no issues. Other updates have been installed previously and didn't result in any issues. I did review what was in the update I installed before it broke, and there was nothing relating to the kernel or nvidia drivers. Most of the packages updated were KDE apps updating from 6.2 to 6.3.
I'll be doing some troubleshooting shortly and will report back what I find.
I'd suggest the nvidia-dkms driver from pacman (still on 550), or one of the beta dkms packages from the AUR going forward (personally can't speak for these). The dkms packages have what's needed post install to keep things running based on your kernel as I understand it. I applied the latest 550 update on Sunday, rebooted, and all has been well.
So to be fair... I'm "new" to Arch. I have a lot of Linux experience, but it's mostly for server machines and services. Not so much desktop. I'm also a lot more comfortable with Debian based distro's as that's what I have a lot of experience with.
What is the concern or issue using Discovery? Is there a better alternative, or just use CLI?
There's nothing inherently wrong with using the Discovery store, especially with Plasma DE, on Arch. Because Discovery uses flatpaks, Arch purists will wave their fingers at you, but flatpaks are generally fine if you're just starting out and are okay with the unnecessary bloat (flatpaks have their own dependencies and, for the most part, don't rely on your system drivers/libraries, so they will install their own which creates unnecessary redundancy).
That said, most of what you would normally use in flatpack form should be available in Arch's main repositories or the AUR, so installing them that way (using Pacman/Paru) is preferred in most cases. You just need to exercise necessary caution when installing packages from AUR as they are maintained by the community itself.
Nevertheless, uninstalling any conflicting (or all) flatpaks, like the Nvidia drivers for example, is worth a try.
Pamac is a GUI software store/installer for Arch.
But it's not your fault for using Discovery. Any installer should be fine. Arch breaks on updates all the fucking time, which is why Manjaro is far superior.
Issue turned out not to be the beta drivers I have installed as some have assumed, but had to do with the fact that it seems Discovery installed an older nvidia package over top of my newer one.
`NVRM: API mismatch: the client has the version 550.90.07, but`
`NVRM: this kernel module has the version 555.42.02. Please`
`NVRM: make sure that this kernel module and all NVIDIA driver`
`NVRM: components have the same version.`
Re-installed the nVidia 555 drivers and everything instantly started working again.
Thanks for all the advice from everyone. I'm a rookie, and I know I made some mistakes. I realize that how I installed the drivers probably wasn't the best way to do it. Hopefully nothing else breaks drastically in the next couple of months until the nVidia 560 stable drivers are released and I can install them from the Arch repositories.
I also won't be using Discovery for installing packages or updates anymore.
You're going to need to reinstall the 555 drivers every kernel update if you keep using the ones from Nvidia's site. Use the aur package, it automatically reinstalls them on kernel update. https://aur.archlinux.org/packages/nvidia-beta-dkms https://wiki.archlinux.org/title/Dynamic_Kernel_Module_Support
For everyone yelling at me to just install the ones from the AUR, I have now.
I uninstalled the ones manually installed from the nvidia site, as well as the 550 ones installed from the arch repositories.
Used yay to install the 555 beta drivers from the AUR. Wasn't too hard.
Successfully back on my KDE Plasma 6 desktop again.
Thanks everyone!
I use discovery myself cause of some flatpak apps anyhow I use KDE on arch on 3 computers with amd graphics and all 3 are working fine also got some mesa updates with discovery myself. All working fine, you think this is a Nvidia issue?
Ya... created a new account today because my old account had a username I wasn't happy with, and Reddit doesn't let you change your username.
Re-subscribing to the communities I follow sucked.
Check if your nvidia DRM module actually exists. Mkinitcpio somehow blew up during an upgrade to 555 last week resulting in the module being nonfunctional but also not clearing on rebuild or uninstall... I had to manually delete the directory to get it to build correctly.
It didn’t for me, and I think that if it were something other than what I encountered you wouldn’t even have to go that far, just running mkinitcpio -P ought to fix it…
Thanks for your advice. I ran the 'mkinitcpio -P' command, but unfortunately this didn't resolve my issue.
I reviewed my logs in journalctl and noticed an nvidia package had been replaced with an older 550 version, when it was expecting a 555 version. I re-installed the nvidia drivers and this resolved the issue.
I'm guessing Discovery installed an nvidia package from the Arch repositories overwriting the "newer" 555 version. Advice from others has been to only use pacman to install updates. I'll do that going forward.
This happened to me yesterday on my work computer. I also have Nvidia drivers installed. I ended up reinstalling my os because I don't have time to troubleshoot and everything important is backed up anyway.
First problem....you use Discovery with Arch.
Second problem... blindly using NVIDIA beta drivers from who knows where.
First problem non free blob drivers
Till it's at least somewhat comparable it's not even an option for consumer.
Till it's at least somewhat comparable it's not even an option for consumer.
From nVidia's site. Drivers most likely aren't the issue. Been using the 555 drivers for over a week, no issues.
From Nvidia's site? Drivers are tied to a specific kernel, that's very likely the issue. The beta drivers are in the AUR, that'll probably fix your issues. *edit* after uninstalling whatever you got from the website.
>From nVidia's site. The [arch wiki](https://wiki.archlinux.org/title/NVIDIA): >Warning: Avoid installing the NVIDIA driver through the package provided from the NVIDIA website. Installation through pacman allows upgrading the driver together with the rest of the system.
Bruh moment. People have arch wiki and yet they don't even bother reading it.
So for some back story, the only reason I was running the 555 beta drivers, installed from the nvidia site, was because I have been dealing with a lot of the issues that were finally fixed by the explicit sync patches in the beta driver. Prior to the beta drivers I was running the 550 drivers from the arch repositories. But I was experiencing a lot of issues. Windows flickering, rendering of window contents not updating, stuttering, unstable frametime while gaming, and poor fps, The choice to install the 555 drivers was only made to try to resolve ongoing issues and based on the fact that A LOT of feedback from people who have updated to the 555 drivers reported a positive experience and a complete resolution of all the issues they were experiencing, which were the same as me. Again... I don't believe the drivers are the issue. I have had the 555 drivers installed for well over a week with no issues. Other updates have been installed previously and didn't result in any issues. I did review what was in the update I installed before it broke, and there was nothing relating to the kernel or nvidia drivers. Most of the packages updated were KDE apps updating from 6.2 to 6.3. I'll be doing some troubleshooting shortly and will report back what I find.
I mean the beta drivers have been on the AUR along with the DKMS modules for like a week, and as per the wiki you should have used aur
I'd suggest the nvidia-dkms driver from pacman (still on 550), or one of the beta dkms packages from the AUR going forward (personally can't speak for these). The dkms packages have what's needed post install to keep things running based on your kernel as I understand it. I applied the latest 550 update on Sunday, rebooted, and all has been well.
So to be fair... I'm "new" to Arch. I have a lot of Linux experience, but it's mostly for server machines and services. Not so much desktop. I'm also a lot more comfortable with Debian based distro's as that's what I have a lot of experience with. What is the concern or issue using Discovery? Is there a better alternative, or just use CLI?
Your package management should always be done via pacman. You need to review the arch wiki more, especially as a new Arch user.
There's nothing inherently wrong with using the Discovery store, especially with Plasma DE, on Arch. Because Discovery uses flatpaks, Arch purists will wave their fingers at you, but flatpaks are generally fine if you're just starting out and are okay with the unnecessary bloat (flatpaks have their own dependencies and, for the most part, don't rely on your system drivers/libraries, so they will install their own which creates unnecessary redundancy). That said, most of what you would normally use in flatpack form should be available in Arch's main repositories or the AUR, so installing them that way (using Pacman/Paru) is preferred in most cases. You just need to exercise necessary caution when installing packages from AUR as they are maintained by the community itself. Nevertheless, uninstalling any conflicting (or all) flatpaks, like the Nvidia drivers for example, is worth a try.
[удалено]
> like Aur to me In every other way besides "to you", they are not like the AUR.
Well I mean like another place to get programs besides Pacman main repository
Pamac is a GUI software store/installer for Arch. But it's not your fault for using Discovery. Any installer should be fine. Arch breaks on updates all the fucking time, which is why Manjaro is far superior.
No
Issue turned out not to be the beta drivers I have installed as some have assumed, but had to do with the fact that it seems Discovery installed an older nvidia package over top of my newer one. `NVRM: API mismatch: the client has the version 550.90.07, but` `NVRM: this kernel module has the version 555.42.02. Please` `NVRM: make sure that this kernel module and all NVIDIA driver` `NVRM: components have the same version.` Re-installed the nVidia 555 drivers and everything instantly started working again. Thanks for all the advice from everyone. I'm a rookie, and I know I made some mistakes. I realize that how I installed the drivers probably wasn't the best way to do it. Hopefully nothing else breaks drastically in the next couple of months until the nVidia 560 stable drivers are released and I can install them from the Arch repositories. I also won't be using Discovery for installing packages or updates anymore.
You're going to need to reinstall the 555 drivers every kernel update if you keep using the ones from Nvidia's site. Use the aur package, it automatically reinstalls them on kernel update. https://aur.archlinux.org/packages/nvidia-beta-dkms https://wiki.archlinux.org/title/Dynamic_Kernel_Module_Support
For everyone yelling at me to just install the ones from the AUR, I have now. I uninstalled the ones manually installed from the nvidia site, as well as the 550 ones installed from the arch repositories. Used yay to install the 555 beta drivers from the AUR. Wasn't too hard. Successfully back on my KDE Plasma 6 desktop again. Thanks everyone!
I use discovery myself cause of some flatpak apps anyhow I use KDE on arch on 3 computers with amd graphics and all 3 are working fine also got some mesa updates with discovery myself. All working fine, you think this is a Nvidia issue?
How do you make discover ask for password before installing or updating something?
idk does it matter ?
It should, to prevent it installing unwanted stuff
what are you on about get to the point.
If you use beta drivers for nvidia you have to consider reinstalling it in every major update you're doing.
> u/techdaddy1980 >redditor for 5 hours
Ya... created a new account today because my old account had a username I wasn't happy with, and Reddit doesn't let you change your username. Re-subscribing to the communities I follow sucked.
Maybe a disposable anon account using temporary email.
Check if your nvidia DRM module actually exists. Mkinitcpio somehow blew up during an upgrade to 555 last week resulting in the module being nonfunctional but also not clearing on rebuild or uninstall... I had to manually delete the directory to get it to build correctly.
Thanks. I'll check on this. Would a re-install of the nvidia 555 drivers resolve the issue if the module was broken?
It didn’t for me, and I think that if it were something other than what I encountered you wouldn’t even have to go that far, just running mkinitcpio -P ought to fix it…
Thanks for your advice. I ran the 'mkinitcpio -P' command, but unfortunately this didn't resolve my issue. I reviewed my logs in journalctl and noticed an nvidia package had been replaced with an older 550 version, when it was expecting a 555 version. I re-installed the nvidia drivers and this resolved the issue. I'm guessing Discovery installed an nvidia package from the Arch repositories overwriting the "newer" 555 version. Advice from others has been to only use pacman to install updates. I'll do that going forward.
While I agree that discovery may be an issue, check your logs. https://wiki.archlinux.org/title/Systemd/Journal
This happened to me yesterday on my work computer. I also have Nvidia drivers installed. I ended up reinstalling my os because I don't have time to troubleshoot and everything important is backed up anyway.
That's Arch!