Error with Nvidia 410.78 drivers
up vote
0
down vote
favorite
1
Just updated from Nvidia 410.73 to 410.78 drivers. 410.73 ran fine. Now 410.78 throws an error when trying to use nvidia-settings.
root@Serenity:/home/keith/Desktop# /usr/bin/nvidia-settings
libEGL warning: DRI2: failed to authenticate
(nvidia-settings:3214): GLib-GObject-CRITICAL **: 16:49:45.561: g_object_unref: assertion 'G_IS_OBJECT (object)' failed
libEGL warning: DRI2: failed to authenticate
** Message: 16:49:46.239: PRIME: No offloading required. Abort
** Message: 16:49:46.239: PRIME: is it supported? no
^C
root@Serenity:/home/keith/Desktop#
So what has gone wrong here?
nvidia
edited Nov 27 at 1:05
Terrance
18.4k34091
asked Nov 27 at 0:56
Keith
11
|
show 3 more comments
up vote
0
down vote
favorite
1
Just updated from Nvidia 410.73 to 410.78 drivers. 410.73 ran fine. Now 410.78 throws an error when trying to use nvidia-settings.
root@Serenity:/home/keith/Desktop# /usr/bin/nvidia-settings
libEGL warning: DRI2: failed to authenticate
(nvidia-settings:3214): GLib-GObject-CRITICAL **: 16:49:45.561: g_object_unref: assertion 'G_IS_OBJECT (object)' failed
libEGL warning: DRI2: failed to authenticate
** Message: 16:49:46.239: PRIME: No offloading required. Abort
** Message: 16:49:46.239: PRIME: is it supported? no
^C
root@Serenity:/home/keith/Desktop#
So what has gone wrong here?
nvidia
edited Nov 27 at 1:05
Terrance
18.4k34091
asked Nov 27 at 0:56
Keith
11
Yes several times. Each time I tried to use nvidia-settings for setting my clocks and fan speeds, the command were not accepted.
– Keith
Nov 27 at 2:26
I then tried to revert to 396 drivers and hit the same problem. So I backed out of the Nvidia drivers entirely and reverted to base Nouveau drivers. Then went back to 410.78 drivers as the ppa doesn't offer the 410.73 release anymore. I can now actually invoke the nvidia-settings parameters and they are at least accepted. Just have a benign libEGL failed to authenticate error still.
– Keith
Nov 27 at 2:30
I can't find any mention of this new error with this driver on the Ubuntu forums. I shot an email off to one of the ppa maintainers and hope to hear something from him eventually.
– Keith
Nov 27 at 2:33
I just use the normal Additional Drivers tab installation in the Software Updater to install the drivers. Been doing it since 390 with no issues. I tried the 415.13 drivers when they were released but they were MUCH slower than the 410.73 drivers so I reverted. I use the Nvidia drivers for distributed processing. No graphics or gaming. Been running with no issues on Nvidia ppa drivers for a year. It was just this last minor update that things went wrong.
– Keith
Nov 27 at 5:04
No I don't normally just invoke nvidia-settings without parameters. I just did that for a quick test to see if the bug was still there after all the downgrades/upgrades. The very first attempt to run my nvidia-settings script after installing the 410.78 drivers failed on every parameter call with the libEGL failed to authenticate error. Why I had to start looking for the reason for the change in the new driver that I had never had any problem with before on earlier drivers. So I had to jump through hoops to get a working system again.
– Keith
Nov 27 at 7:14
|
show 3 more comments
up vote
0
down vote
favorite
1
up vote
0
down vote
favorite
1
1
Just updated from Nvidia 410.73 to 410.78 drivers. 410.73 ran fine. Now 410.78 throws an error when trying to use nvidia-settings.
root@Serenity:/home/keith/Desktop# /usr/bin/nvidia-settings
libEGL warning: DRI2: failed to authenticate
(nvidia-settings:3214): GLib-GObject-CRITICAL **: 16:49:45.561: g_object_unref: assertion 'G_IS_OBJECT (object)' failed
libEGL warning: DRI2: failed to authenticate
** Message: 16:49:46.239: PRIME: No offloading required. Abort
** Message: 16:49:46.239: PRIME: is it supported? no
^C
root@Serenity:/home/keith/Desktop#
So what has gone wrong here?
nvidia
edited Nov 27 at 1:05
Terrance
18.4k34091
asked Nov 27 at 0:56
Keith
11
Just updated from Nvidia 410.73 to 410.78 drivers. 410.73 ran fine. Now 410.78 throws an error when trying to use nvidia-settings.
root@Serenity:/home/keith/Desktop# /usr/bin/nvidia-settings
libEGL warning: DRI2: failed to authenticate
(nvidia-settings:3214): GLib-GObject-CRITICAL **: 16:49:45.561: g_object_unref: assertion 'G_IS_OBJECT (object)' failed
libEGL warning: DRI2: failed to authenticate
** Message: 16:49:46.239: PRIME: No offloading required. Abort
** Message: 16:49:46.239: PRIME: is it supported? no
^C
root@Serenity:/home/keith/Desktop#
So what has gone wrong here?
nvidia
nvidia
edited Nov 27 at 1:05
Terrance
18.4k34091
asked Nov 27 at 0:56
Keith
11
edited Nov 27 at 1:05
Terrance
18.4k34091
asked Nov 27 at 0:56
Keith
11
edited Nov 27 at 1:05
Terrance
18.4k34091
edited Nov 27 at 1:05
Terrance
18.4k34091
edited Nov 27 at 1:05
Terrance
18.4k34091
18.4k34091
asked Nov 27 at 0:56
Keith
11
asked Nov 27 at 0:56
Keith
11
asked Nov 27 at 0:56
Keith
11
11
Yes several times. Each time I tried to use nvidia-settings for setting my clocks and fan speeds, the command were not accepted.
– Keith
Nov 27 at 2:26
I then tried to revert to 396 drivers and hit the same problem. So I backed out of the Nvidia drivers entirely and reverted to base Nouveau drivers. Then went back to 410.78 drivers as the ppa doesn't offer the 410.73 release anymore. I can now actually invoke the nvidia-settings parameters and they are at least accepted. Just have a benign libEGL failed to authenticate error still.
– Keith
Nov 27 at 2:30
I can't find any mention of this new error with this driver on the Ubuntu forums. I shot an email off to one of the ppa maintainers and hope to hear something from him eventually.
– Keith
Nov 27 at 2:33
I just use the normal Additional Drivers tab installation in the Software Updater to install the drivers. Been doing it since 390 with no issues. I tried the 415.13 drivers when they were released but they were MUCH slower than the 410.73 drivers so I reverted. I use the Nvidia drivers for distributed processing. No graphics or gaming. Been running with no issues on Nvidia ppa drivers for a year. It was just this last minor update that things went wrong.
– Keith
Nov 27 at 5:04
No I don't normally just invoke nvidia-settings without parameters. I just did that for a quick test to see if the bug was still there after all the downgrades/upgrades. The very first attempt to run my nvidia-settings script after installing the 410.78 drivers failed on every parameter call with the libEGL failed to authenticate error. Why I had to start looking for the reason for the change in the new driver that I had never had any problem with before on earlier drivers. So I had to jump through hoops to get a working system again.
– Keith
Nov 27 at 7:14
|
show 3 more comments
Yes several times. Each time I tried to use nvidia-settings for setting my clocks and fan speeds, the command were not accepted.
– Keith
Nov 27 at 2:26
I then tried to revert to 396 drivers and hit the same problem. So I backed out of the Nvidia drivers entirely and reverted to base Nouveau drivers. Then went back to 410.78 drivers as the ppa doesn't offer the 410.73 release anymore. I can now actually invoke the nvidia-settings parameters and they are at least accepted. Just have a benign libEGL failed to authenticate error still.
– Keith
Nov 27 at 2:30
I can't find any mention of this new error with this driver on the Ubuntu forums. I shot an email off to one of the ppa maintainers and hope to hear something from him eventually.
– Keith
Nov 27 at 2:33
I just use the normal Additional Drivers tab installation in the Software Updater to install the drivers. Been doing it since 390 with no issues. I tried the 415.13 drivers when they were released but they were MUCH slower than the 410.73 drivers so I reverted. I use the Nvidia drivers for distributed processing. No graphics or gaming. Been running with no issues on Nvidia ppa drivers for a year. It was just this last minor update that things went wrong.
– Keith
Nov 27 at 5:04
No I don't normally just invoke nvidia-settings without parameters. I just did that for a quick test to see if the bug was still there after all the downgrades/upgrades. The very first attempt to run my nvidia-settings script after installing the 410.78 drivers failed on every parameter call with the libEGL failed to authenticate error. Why I had to start looking for the reason for the change in the new driver that I had never had any problem with before on earlier drivers. So I had to jump through hoops to get a working system again.
– Keith
Nov 27 at 7:14
Yes several times. Each time I tried to use nvidia-settings for setting my clocks and fan speeds, the command were not accepted.
– Keith
Nov 27 at 2:26
Yes several times. Each time I tried to use nvidia-settings for setting my clocks and fan speeds, the command were not accepted.
– Keith
Nov 27 at 2:26
I then tried to revert to 396 drivers and hit the same problem. So I backed out of the Nvidia drivers entirely and reverted to base Nouveau drivers. Then went back to 410.78 drivers as the ppa doesn't offer the 410.73 release anymore. I can now actually invoke the nvidia-settings parameters and they are at least accepted. Just have a benign libEGL failed to authenticate error still.
– Keith
Nov 27 at 2:30
I then tried to revert to 396 drivers and hit the same problem. So I backed out of the Nvidia drivers entirely and reverted to base Nouveau drivers. Then went back to 410.78 drivers as the ppa doesn't offer the 410.73 release anymore. I can now actually invoke the nvidia-settings parameters and they are at least accepted. Just have a benign libEGL failed to authenticate error still.
– Keith
Nov 27 at 2:30
I can't find any mention of this new error with this driver on the Ubuntu forums. I shot an email off to one of the ppa maintainers and hope to hear something from him eventually.
– Keith
Nov 27 at 2:33
I can't find any mention of this new error with this driver on the Ubuntu forums. I shot an email off to one of the ppa maintainers and hope to hear something from him eventually.
– Keith
Nov 27 at 2:33
I just use the normal Additional Drivers tab installation in the Software Updater to install the drivers. Been doing it since 390 with no issues. I tried the 415.13 drivers when they were released but they were MUCH slower than the 410.73 drivers so I reverted. I use the Nvidia drivers for distributed processing. No graphics or gaming. Been running with no issues on Nvidia ppa drivers for a year. It was just this last minor update that things went wrong.
– Keith
Nov 27 at 5:04
I just use the normal Additional Drivers tab installation in the Software Updater to install the drivers. Been doing it since 390 with no issues. I tried the 415.13 drivers when they were released but they were MUCH slower than the 410.73 drivers so I reverted. I use the Nvidia drivers for distributed processing. No graphics or gaming. Been running with no issues on Nvidia ppa drivers for a year. It was just this last minor update that things went wrong.
– Keith
Nov 27 at 5:04
No I don't normally just invoke nvidia-settings without parameters. I just did that for a quick test to see if the bug was still there after all the downgrades/upgrades. The very first attempt to run my nvidia-settings script after installing the 410.78 drivers failed on every parameter call with the libEGL failed to authenticate error. Why I had to start looking for the reason for the change in the new driver that I had never had any problem with before on earlier drivers. So I had to jump through hoops to get a working system again.
– Keith
Nov 27 at 7:14
No I don't normally just invoke nvidia-settings without parameters. I just did that for a quick test to see if the bug was still there after all the downgrades/upgrades. The very first attempt to run my nvidia-settings script after installing the 410.78 drivers failed on every parameter call with the libEGL failed to authenticate error. Why I had to start looking for the reason for the change in the new driver that I had never had any problem with before on earlier drivers. So I had to jump through hoops to get a working system again.
– Keith
Nov 27 at 7:14
|
show 3 more comments
active
oldest
votes
active
oldest
votes
active
oldest
votes
active
oldest
votes
active
oldest
votes
draft saved
draft discarded
Thanks for contributing an answer to Ask Ubuntu!
- Please be sure to answer the question. Provide details and share your research!
But avoid …
- Asking for help, clarification, or responding to other answers.
- Making statements based on opinion; back them up with references or personal experience.
To learn more, see our tips on writing great answers.
Some of your past answers have not been well-received, and you're in danger of being blocked from answering.
Please pay close attention to the following guidance:
- Please be sure to answer the question. Provide details and share your research!
But avoid …
- Asking for help, clarification, or responding to other answers.
- Making statements based on opinion; back them up with references or personal experience.
To learn more, see our tips on writing great answers.
draft saved
draft discarded
Sign up or log in
StackExchange.ready(function () {
StackExchange.helpers.onClickDraftSave('#login-link');
});
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Post as a guest
Required, but never shown
StackExchange.ready(
function () {
StackExchange.openid.initPostLogin('.new-post-login', 'https%3a%2f%2faskubuntu.com%2fquestions%2f1096338%2ferror-with-nvidia-410-78-drivers%23new-answer', 'question_page');
}
);
Post as a guest
Required, but never shown
Sign up or log in
StackExchange.ready(function () {
StackExchange.helpers.onClickDraftSave('#login-link');
});
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Post as a guest
Required, but never shown
Sign up or log in
StackExchange.ready(function () {
StackExchange.helpers.onClickDraftSave('#login-link');
});
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Post as a guest
Required, but never shown
Sign up or log in
StackExchange.ready(function () {
StackExchange.helpers.onClickDraftSave('#login-link');
});
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Post as a guest
Required, but never shown
Required, but never shown
Required, but never shown
Required, but never shown
Required, but never shown
Required, but never shown
Required, but never shown
Required, but never shown
Required, but never shown
Yes several times. Each time I tried to use nvidia-settings for setting my clocks and fan speeds, the command were not accepted.
– Keith
Nov 27 at 2:26
I then tried to revert to 396 drivers and hit the same problem. So I backed out of the Nvidia drivers entirely and reverted to base Nouveau drivers. Then went back to 410.78 drivers as the ppa doesn't offer the 410.73 release anymore. I can now actually invoke the nvidia-settings parameters and they are at least accepted. Just have a benign libEGL failed to authenticate error still.
– Keith
Nov 27 at 2:30
I can't find any mention of this new error with this driver on the Ubuntu forums. I shot an email off to one of the ppa maintainers and hope to hear something from him eventually.
– Keith
Nov 27 at 2:33
I just use the normal Additional Drivers tab installation in the Software Updater to install the drivers. Been doing it since 390 with no issues. I tried the 415.13 drivers when they were released but they were MUCH slower than the 410.73 drivers so I reverted. I use the Nvidia drivers for distributed processing. No graphics or gaming. Been running with no issues on Nvidia ppa drivers for a year. It was just this last minor update that things went wrong.
– Keith
Nov 27 at 5:04
No I don't normally just invoke nvidia-settings without parameters. I just did that for a quick test to see if the bug was still there after all the downgrades/upgrades. The very first attempt to run my nvidia-settings script after installing the 410.78 drivers failed on every parameter call with the libEGL failed to authenticate error. Why I had to start looking for the reason for the change in the new driver that I had never had any problem with before on earlier drivers. So I had to jump through hoops to get a working system again.
– Keith
Nov 27 at 7:14