Ubuntu 14.04 Black screen nvidia driver 347. taints Kernel?
up vote
2
down vote
favorite
My pc, gtx 750 with nvidia 347 driver ubuntu gnome 14.04, boots only to black screen.
When I look into the /var/log/syslog I get this error with the nvidia driver.
nvidia: module license 'NVIDIA' taints kernel.
nvidia: module verification failed: signature and/or required key missing - tainting kernel
init: plymouth-upstart-bridge main process (223) terminated with status 1
gdm-simple-slave[1176]: Failed to give slave programs access to the display. Trying to proceed.
I installed the drive by hand stopping gdm and the install process did not create any error.
The plymouth error is very strange since I define "noplymouth" in grub.
I am not very familiar with error messages.
What do those messages mean and more importantly how do I fix it?
Is there a way to get rid of plymouth all together since it only displays the ubuntu logo at the beginning.
thanks for reading
Update:
Just read that the kernel taint message is normal and nothing to worry about.
The plymouth message is still strange and it is multiple times in the syslog file.
drivers nvidia kernel
asked Mar 21 '15 at 15:10
oldmansaur
9629
add a comment |
up vote
2
down vote
favorite
My pc, gtx 750 with nvidia 347 driver ubuntu gnome 14.04, boots only to black screen.
When I look into the /var/log/syslog I get this error with the nvidia driver.
nvidia: module license 'NVIDIA' taints kernel.
nvidia: module verification failed: signature and/or required key missing - tainting kernel
init: plymouth-upstart-bridge main process (223) terminated with status 1
gdm-simple-slave[1176]: Failed to give slave programs access to the display. Trying to proceed.
I installed the drive by hand stopping gdm and the install process did not create any error.
The plymouth error is very strange since I define "noplymouth" in grub.
I am not very familiar with error messages.
What do those messages mean and more importantly how do I fix it?
Is there a way to get rid of plymouth all together since it only displays the ubuntu logo at the beginning.
thanks for reading
Update:
Just read that the kernel taint message is normal and nothing to worry about.
The plymouth message is still strange and it is multiple times in the syslog file.
drivers nvidia kernel
asked Mar 21 '15 at 15:10
oldmansaur
9629
how did you install the driver by hand? Because lots of different issues might happen if you did or didn't do something to complete the process. e.g. this tutorial askubuntu.com/questions/66328/…
– JoKeR
Mar 21 '15 at 16:04
I dropped to command line (Alt-ctrl-F1) I switched of gdm (sudo service gdm stop) then I ran the driver file from nvidia(346.47).
– oldmansaur
Mar 21 '15 at 16:07
please read the tutorial that I posted in upper comment I used it on 12.04 and 14.04 and it works when you do everything right.
– JoKeR
Mar 21 '15 at 16:17
Thanks for the quick reply I just did this. When I run nvidia-settings I get(nvidia-setttings:1775)Gdk-ERROR **: error:XDG_RUNTIME_DIR not set in the environment.What does that mean?
– oldmansaur
Mar 21 '15 at 16:43
don't pay much attention to that it's ok rungksudo nvidia-settingsinstead if so.
– JoKeR
Mar 21 '15 at 20:57
add a comment |
up vote
2
down vote
favorite
up vote
2
down vote
favorite
My pc, gtx 750 with nvidia 347 driver ubuntu gnome 14.04, boots only to black screen.
When I look into the /var/log/syslog I get this error with the nvidia driver.
nvidia: module license 'NVIDIA' taints kernel.
nvidia: module verification failed: signature and/or required key missing - tainting kernel
init: plymouth-upstart-bridge main process (223) terminated with status 1
gdm-simple-slave[1176]: Failed to give slave programs access to the display. Trying to proceed.
I installed the drive by hand stopping gdm and the install process did not create any error.
The plymouth error is very strange since I define "noplymouth" in grub.
I am not very familiar with error messages.
What do those messages mean and more importantly how do I fix it?
Is there a way to get rid of plymouth all together since it only displays the ubuntu logo at the beginning.
thanks for reading
Update:
Just read that the kernel taint message is normal and nothing to worry about.
The plymouth message is still strange and it is multiple times in the syslog file.
drivers nvidia kernel
asked Mar 21 '15 at 15:10
oldmansaur
9629
My pc, gtx 750 with nvidia 347 driver ubuntu gnome 14.04, boots only to black screen.
When I look into the /var/log/syslog I get this error with the nvidia driver.
nvidia: module license 'NVIDIA' taints kernel.
nvidia: module verification failed: signature and/or required key missing - tainting kernel
init: plymouth-upstart-bridge main process (223) terminated with status 1
gdm-simple-slave[1176]: Failed to give slave programs access to the display. Trying to proceed.
I installed the drive by hand stopping gdm and the install process did not create any error.
The plymouth error is very strange since I define "noplymouth" in grub.
I am not very familiar with error messages.
What do those messages mean and more importantly how do I fix it?
Is there a way to get rid of plymouth all together since it only displays the ubuntu logo at the beginning.
thanks for reading
Update:
Just read that the kernel taint message is normal and nothing to worry about.
The plymouth message is still strange and it is multiple times in the syslog file.
drivers nvidia kernel
drivers nvidia kernel
asked Mar 21 '15 at 15:10
oldmansaur
9629
asked Mar 21 '15 at 15:10
oldmansaur
9629
edited Mar 21 '15 at 16:15
asked Mar 21 '15 at 15:10
oldmansaur
9629
asked Mar 21 '15 at 15:10
oldmansaur
9629
asked Mar 21 '15 at 15:10
oldmansaur
9629
9629
how did you install the driver by hand? Because lots of different issues might happen if you did or didn't do something to complete the process. e.g. this tutorial askubuntu.com/questions/66328/…
– JoKeR
Mar 21 '15 at 16:04
I dropped to command line (Alt-ctrl-F1) I switched of gdm (sudo service gdm stop) then I ran the driver file from nvidia(346.47).
– oldmansaur
Mar 21 '15 at 16:07
please read the tutorial that I posted in upper comment I used it on 12.04 and 14.04 and it works when you do everything right.
– JoKeR
Mar 21 '15 at 16:17
Thanks for the quick reply I just did this. When I run nvidia-settings I get(nvidia-setttings:1775)Gdk-ERROR **: error:XDG_RUNTIME_DIR not set in the environment.What does that mean?
– oldmansaur
Mar 21 '15 at 16:43
don't pay much attention to that it's ok rungksudo nvidia-settingsinstead if so.
– JoKeR
Mar 21 '15 at 20:57
add a comment |
how did you install the driver by hand? Because lots of different issues might happen if you did or didn't do something to complete the process. e.g. this tutorial askubuntu.com/questions/66328/…
– JoKeR
Mar 21 '15 at 16:04
I dropped to command line (Alt-ctrl-F1) I switched of gdm (sudo service gdm stop) then I ran the driver file from nvidia(346.47).
– oldmansaur
Mar 21 '15 at 16:07
please read the tutorial that I posted in upper comment I used it on 12.04 and 14.04 and it works when you do everything right.
– JoKeR
Mar 21 '15 at 16:17
Thanks for the quick reply I just did this. When I run nvidia-settings I get(nvidia-setttings:1775)Gdk-ERROR **: error:XDG_RUNTIME_DIR not set in the environment.What does that mean?
– oldmansaur
Mar 21 '15 at 16:43
don't pay much attention to that it's ok rungksudo nvidia-settingsinstead if so.
– JoKeR
Mar 21 '15 at 20:57
how did you install the driver by hand? Because lots of different issues might happen if you did or didn't do something to complete the process. e.g. this tutorial askubuntu.com/questions/66328/…
– JoKeR
Mar 21 '15 at 16:04
how did you install the driver by hand? Because lots of different issues might happen if you did or didn't do something to complete the process. e.g. this tutorial askubuntu.com/questions/66328/…
– JoKeR
Mar 21 '15 at 16:04
I dropped to command line (Alt-ctrl-F1) I switched of gdm (sudo service gdm stop) then I ran the driver file from nvidia(346.47).
– oldmansaur
Mar 21 '15 at 16:07
I dropped to command line (Alt-ctrl-F1) I switched of gdm (sudo service gdm stop) then I ran the driver file from nvidia(346.47).
– oldmansaur
Mar 21 '15 at 16:07
please read the tutorial that I posted in upper comment I used it on 12.04 and 14.04 and it works when you do everything right.
– JoKeR
Mar 21 '15 at 16:17
please read the tutorial that I posted in upper comment I used it on 12.04 and 14.04 and it works when you do everything right.
– JoKeR
Mar 21 '15 at 16:17
Thanks for the quick reply I just did this. When I run nvidia-settings I get
(nvidia-setttings:1775)Gdk-ERROR **: error:XDG_RUNTIME_DIR not set in the environment. What does that mean?– oldmansaur
Mar 21 '15 at 16:43
Thanks for the quick reply I just did this. When I run nvidia-settings I get
(nvidia-setttings:1775)Gdk-ERROR **: error:XDG_RUNTIME_DIR not set in the environment. What does that mean?– oldmansaur
Mar 21 '15 at 16:43
don't pay much attention to that it's ok run
gksudo nvidia-settings instead if so.– JoKeR
Mar 21 '15 at 20:57
don't pay much attention to that it's ok run
gksudo nvidia-settings instead if so.– JoKeR
Mar 21 '15 at 20:57
add a comment |
1 Answer
1
active
oldest
votes
up vote
0
down vote
While the question is old, I believe that an explanation of what tainted means is in place.
nvidia: module license 'NVIDIA' taints kernel.
A tainted kernel is a kernel that is touched by some action which makes it difficult to debug. This can for instance be a closed source kernel module - as in this case. There's different kinds of taints. This link is somewhat specific to Novell/SUSE, but the main content is applicable to Ubuntu as well.
The Nvidia module taints the kernel because it is not open source.
answered Jan 12 at 22:57
vidarlo
8,07542341
add a comment |
1 Answer
1
active
oldest
votes
1 Answer
1
active
oldest
votes
active
oldest
votes
active
oldest
votes
up vote
0
down vote
While the question is old, I believe that an explanation of what tainted means is in place.
nvidia: module license 'NVIDIA' taints kernel.
A tainted kernel is a kernel that is touched by some action which makes it difficult to debug. This can for instance be a closed source kernel module - as in this case. There's different kinds of taints. This link is somewhat specific to Novell/SUSE, but the main content is applicable to Ubuntu as well.
The Nvidia module taints the kernel because it is not open source.
answered Jan 12 at 22:57
vidarlo
8,07542341
add a comment |
up vote
0
down vote
While the question is old, I believe that an explanation of what tainted means is in place.
nvidia: module license 'NVIDIA' taints kernel.
A tainted kernel is a kernel that is touched by some action which makes it difficult to debug. This can for instance be a closed source kernel module - as in this case. There's different kinds of taints. This link is somewhat specific to Novell/SUSE, but the main content is applicable to Ubuntu as well.
The Nvidia module taints the kernel because it is not open source.
answered Jan 12 at 22:57
vidarlo
8,07542341
add a comment |
up vote
0
down vote
up vote
0
down vote
While the question is old, I believe that an explanation of what tainted means is in place.
nvidia: module license 'NVIDIA' taints kernel.
A tainted kernel is a kernel that is touched by some action which makes it difficult to debug. This can for instance be a closed source kernel module - as in this case. There's different kinds of taints. This link is somewhat specific to Novell/SUSE, but the main content is applicable to Ubuntu as well.
The Nvidia module taints the kernel because it is not open source.
answered Jan 12 at 22:57
vidarlo
8,07542341
While the question is old, I believe that an explanation of what tainted means is in place.
nvidia: module license 'NVIDIA' taints kernel.
A tainted kernel is a kernel that is touched by some action which makes it difficult to debug. This can for instance be a closed source kernel module - as in this case. There's different kinds of taints. This link is somewhat specific to Novell/SUSE, but the main content is applicable to Ubuntu as well.
The Nvidia module taints the kernel because it is not open source.
answered Jan 12 at 22:57
vidarlo
8,07542341
answered Jan 12 at 22:57
vidarlo
8,07542341
answered Jan 12 at 22:57
vidarlo
8,07542341
answered Jan 12 at 22:57
vidarlo
8,07542341
8,07542341
add a comment |
add a comment |
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%2f599556%2fubuntu-14-04-black-screen-nvidia-driver-347-taints-kernel%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
how did you install the driver by hand? Because lots of different issues might happen if you did or didn't do something to complete the process. e.g. this tutorial askubuntu.com/questions/66328/…
– JoKeR
Mar 21 '15 at 16:04
I dropped to command line (Alt-ctrl-F1) I switched of gdm (sudo service gdm stop) then I ran the driver file from nvidia(346.47).
– oldmansaur
Mar 21 '15 at 16:07
please read the tutorial that I posted in upper comment I used it on 12.04 and 14.04 and it works when you do everything right.
– JoKeR
Mar 21 '15 at 16:17
Thanks for the quick reply I just did this. When I run nvidia-settings I get
(nvidia-setttings:1775)Gdk-ERROR **: error:XDG_RUNTIME_DIR not set in the environment.What does that mean?– oldmansaur
Mar 21 '15 at 16:43
don't pay much attention to that it's ok run
gksudo nvidia-settingsinstead if so.– JoKeR
Mar 21 '15 at 20:57