-
Notifications
You must be signed in to change notification settings - Fork 22
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Disappearing Nvidia Drivers #17
Comments
This should be fixed by https://bugs.launchpad.net/ubuntu/+source/ubuntu-drivers-common/+bug/1904583 |
Thanks for the response Alberto .. posted it on the Linux Mint forum.
On Monday, February 1, 2021, 4:50:42 AM CST, tseliot <[email protected]> wrote:
This should be fixed by https://bugs.launchpad.net/ubuntu/+source/ubuntu-drivers-common/+bug/1904583
—
You are receiving this because you authored the thread.
Reply to this email directly, view it on GitHub, or unsubscribe.
|
Still does not fix the problem of the mint Prime applet not showing in the notification area because when it uses /usr/bin/prime-supported to check whether to run or not it gets a false response because when in Intel mode the file /var/lib/ubuntu-drivers-common/requires_offloading does not exist. I am not sure if this is the applet problem or /usr/bin/prime-supported problem but from a semantics standpoint it would seem to be /usr/bin/prime-supported. For further details check my post at the above referenced forum. |
OK I didn't realize there are 2 prime-supported files in Mint. One is in /usr/bin and the other is in /var/lib/ubuntu-drivers-common/. |
I don't think anything should use the prime-supported script (which is only
meant to attach outputs in nvidia mode). The "prime-select query" command
is the way to go to check which profile is in use.
…On Wed, 3 Feb 2021 at 16:30, burntex ***@***.***> wrote:
OK I didn't realize there are 2 prime-supported files in Mint. One is in
/usr/bin and the other is in /var/lib/ubuntu-drivers-common/.
I think that you use the 'official' one in /var/lib/ubuntu-drivers-common/
but the one in /usr/bin is used by the Mint nvidia-prime-applet (
https://github.com/linuxmint/nvidia-prime-applet). So I don't think this
is your issue but belongs to the applet. I will try and work with them.
Thx. will let you know how that goes.
—
You are receiving this because you commented.
Reply to this email directly, view it on GitHub
<#17 (comment)>,
or unsubscribe
<https://github.com/notifications/unsubscribe-auth/AACMLMLWDXDZMGXO2Q7GMMDS5FTXXANCNFSM4W2QOXGQ>
.
--
Alberto Milone
|
@tseliot: a bit offtopic - but it looks like It might be the cause of empty nvidia-settings window, for example, like on the screenshot in linuxmint/nvidia-prime-applet#7 (comment). |
I worked on this for weeks, and then decided to start over. I bought a bigger ssd drive and set up a dual boot system. For Nvidia, on the linux mint side, I chose the older 390 driver. Even after the mint update, everything is fine. I still have the applet visible, and all of the nvidia settings, as well. My only guess is that using the older driver works for me. |
Well, this is kind of weird because nvidia-settings should be still the latest version. I don't see any "legacy" nvidia-settings packages in the repo... |
nvidia-settings looks empty if the driver wasn't loaded correctly, or if it
crashed.
But, yes, 08_add_prime_support.patch needs updating.
…On Thu, 3 Jun 2021 at 13:11, monsta ***@***.***> wrote:
@tseliot <https://github.com/tseliot>: a bit offtopic - but it looks like
08_add_prime_support.patch in nvidia-settings still uses prime-supported?
It might be the cause of empty nvidia-settings window, for example, like
on the screenshot in linuxmint/nvidia-prime-applet#7 (comment)
<linuxmint/nvidia-prime-applet#7 (comment)>
.
—
You are receiving this because you were mentioned.
Reply to this email directly, view it on GitHub
<#17 (comment)>,
or unsubscribe
<https://github.com/notifications/unsubscribe-auth/AACMLMOA5SEMMP5OYOZO2Z3TQ5PMTANCNFSM4W2QOXGQ>
.
--
Alberto Milone
|
It seems like a possible cause of empty nvidia-settings window in Mint is the unexpected placement of dkms modules. They're placed in It should be changed to It looks like /* NVIDIA Optimus */
else if ((intel_loaded || amdgpu_loaded) && !nouveau_loaded &&
(nvidia_loaded || nvidia_kmod_available)) {
fprintf(log_handle, "NVIDIA hybrid system\n"); |
I didn't know Mint packaged their own drivers. Wouldn't it be easier for them if they simply switched to updates/dkms ? |
No, the drivers are the same - from Ubuntu repos. It's just that dkms doesn't recognize it's running in Ubuntu-based distro, so it doesn't override the path for modules to Examples from my system (Mint 20.3, based on Ubuntu 20.04): $ grep DEST_MODULE_LOCATION /usr/src/nvidia-390.144/dkms.conf
DEST_MODULE_LOCATION[0]="/kernel/drivers/char/drm"
DEST_MODULE_LOCATION[1]="/kernel/drivers/char/drm"
DEST_MODULE_LOCATION[2]="/kernel/drivers/char/drm"
DEST_MODULE_LOCATION[3]="/kernel/drivers/char/drm"
|
see: https://forums.linuxmint.com/viewtopic.php?f=59&t=341289
The text was updated successfully, but these errors were encountered: