Can't disable nouveau drivers in Ubuntu 18.04
I tried disabling nouveau drivers in Ubuntu 18.04 by putting these lines in /etc/modprobe.d/blacklist.conf:
#Blacklist nouveau drivers
blacklist nouveau
blacklist lbm-nouveau
alias nouveau off
alias lbm-nouveau off
and updating initramfs.
On reboot the gdm won't start, blocked in the last line:
Trying to enter any tty, I get the same error (I had to undo changes from rescue mode).
The same procedure was working on 17.10 (with xorg).
My pc is an Asus ux430uq with clean install of ubuntu 18.04 (4.15.0-20 kernel).
I am afraid of uninstalling xserver-xorg-video-nouveau drivers since I don't know how to reinstall them if something go wrong (I can't get internet working in rescue mode).
EDIT:
Uninstalling the above package lead to the same error. Trying to boot ubuntu with the kernel flag nouveau.modeset=0 gives the same error too.
drivers nvidia 18.04 nouveau blacklist
edited Nov 23 '18 at 18:47
Zanna
50.7k13136241
asked May 3 '18 at 11:22
velixvelix
2861213
add a comment |
I tried disabling nouveau drivers in Ubuntu 18.04 by putting these lines in /etc/modprobe.d/blacklist.conf:
#Blacklist nouveau drivers
blacklist nouveau
blacklist lbm-nouveau
alias nouveau off
alias lbm-nouveau off
and updating initramfs.
On reboot the gdm won't start, blocked in the last line:
Trying to enter any tty, I get the same error (I had to undo changes from rescue mode).
The same procedure was working on 17.10 (with xorg).
My pc is an Asus ux430uq with clean install of ubuntu 18.04 (4.15.0-20 kernel).
I am afraid of uninstalling xserver-xorg-video-nouveau drivers since I don't know how to reinstall them if something go wrong (I can't get internet working in rescue mode).
EDIT:
Uninstalling the above package lead to the same error. Trying to boot ubuntu with the kernel flag nouveau.modeset=0 gives the same error too.
drivers nvidia 18.04 nouveau blacklist
edited Nov 23 '18 at 18:47
Zanna
50.7k13136241
asked May 3 '18 at 11:22
velixvelix
2861213
add a comment |
I tried disabling nouveau drivers in Ubuntu 18.04 by putting these lines in /etc/modprobe.d/blacklist.conf:
#Blacklist nouveau drivers
blacklist nouveau
blacklist lbm-nouveau
alias nouveau off
alias lbm-nouveau off
and updating initramfs.
On reboot the gdm won't start, blocked in the last line:
Trying to enter any tty, I get the same error (I had to undo changes from rescue mode).
The same procedure was working on 17.10 (with xorg).
My pc is an Asus ux430uq with clean install of ubuntu 18.04 (4.15.0-20 kernel).
I am afraid of uninstalling xserver-xorg-video-nouveau drivers since I don't know how to reinstall them if something go wrong (I can't get internet working in rescue mode).
EDIT:
Uninstalling the above package lead to the same error. Trying to boot ubuntu with the kernel flag nouveau.modeset=0 gives the same error too.
drivers nvidia 18.04 nouveau blacklist
edited Nov 23 '18 at 18:47
Zanna
50.7k13136241
asked May 3 '18 at 11:22
velixvelix
2861213
I tried disabling nouveau drivers in Ubuntu 18.04 by putting these lines in /etc/modprobe.d/blacklist.conf:
#Blacklist nouveau drivers
blacklist nouveau
blacklist lbm-nouveau
alias nouveau off
alias lbm-nouveau off
and updating initramfs.
On reboot the gdm won't start, blocked in the last line:
Trying to enter any tty, I get the same error (I had to undo changes from rescue mode).
The same procedure was working on 17.10 (with xorg).
My pc is an Asus ux430uq with clean install of ubuntu 18.04 (4.15.0-20 kernel).
I am afraid of uninstalling xserver-xorg-video-nouveau drivers since I don't know how to reinstall them if something go wrong (I can't get internet working in rescue mode).
EDIT:
Uninstalling the above package lead to the same error. Trying to boot ubuntu with the kernel flag nouveau.modeset=0 gives the same error too.
drivers nvidia 18.04 nouveau blacklist
drivers nvidia 18.04 nouveau blacklist
edited Nov 23 '18 at 18:47
Zanna
50.7k13136241
asked May 3 '18 at 11:22
velixvelix
2861213
edited Nov 23 '18 at 18:47
Zanna
50.7k13136241
asked May 3 '18 at 11:22
velixvelix
2861213
edited Nov 23 '18 at 18:47
Zanna
50.7k13136241
edited Nov 23 '18 at 18:47
Zanna
50.7k13136241
edited Nov 23 '18 at 18:47
Zanna
50.7k13136241
50.7k13136241
asked May 3 '18 at 11:22
velixvelix
2861213
asked May 3 '18 at 11:22
velixvelix
2861213
asked May 3 '18 at 11:22
velixvelix
2861213
2861213
add a comment |
add a comment |
5 Answers
5
active
oldest
votes
I found the solution. I'll write it here for who may have the same problem.
My gdm3 session was running in wayland. To check it:
$ loginctl
SESSION UID USER SEAT TTY
2 1000 velix seat0 tty2
c2 1000 velix
c1 120 gdm seat0 tty1
The command loginctl show-session <session-n> -p Type show the session type:
$ loginctl show-session c1 -p Type
Type=Wayland
To change it, edit the file /etc/gdm3/custom.conf and uncomment the line WaylandEnable=false.
After rebooting:
$ loginctl show-session c1 -p Type
Type=x11
Now blacklisting nouveau drivers in /etc/modprobe.d/blacklist.conf (as in the question) works and doesn't give the above error.
The key point is to run xorg instead of wayland
(That's why it was working in my 17.10 ubuntu, forced to run xorg)
answered May 4 '18 at 13:34
velixvelix
2861213
+1 Thanks for sharing. Don't forget to accept your answer by clicking check mark next to it in a day or so when it lets you.
– WinEunuuchs2Unix
May 4 '18 at 23:13
1
Gives black screen on a MacBook, answer no longer works?
– Gabor
May 9 '18 at 2:10
My answer is 5 days old. This method is still working on my notebook.
– velix
May 9 '18 at 16:24
On a MacBook, where I have the error same as in your screenshot, I only get a black screen. Loginctl also errors out withFailed to create bus connection
– Gabor
May 9 '18 at 20:24
I think it's a different problem. Open a new question and put more info in that.
– velix
May 10 '18 at 9:58
|
show 2 more comments
https://bugs.launchpad.net/nvidia-drivers-ubuntu/+bug/1784598
try:
sudo systemctl disable nvidia-fallback.service
answered Jul 31 '18 at 10:10
heeenheeen
1212
add a comment |
Got exactly same problem, my configuration is x11 (returned by loginctl command).
The only way working for me at the moment is to rename the nouveau file module.
# pwd
/lib/modules/4.15.0-20-generic/kernel/drivers/gpu/drm/nouveau
# mv nouveau.ko nouveau.ko-old
# reboot
dirty solution but working, hope it will help. Of course, all was fine in 17.10.
answered May 23 '18 at 16:30
lightmanlightman
112
add a comment |
Don't forget to disable Secure Boot in BIOS especially when you want nvidia (and not nouveau) driver working. Otherwise it will quite always fall back back to nouveau no matter what you do.
Also note that "Secure Boot" option can be hidden in BIOS under various options on various places and often that option is not saying anything about "Secure Boot" but sometimes it's called "Other OS" similar. Every BIOS can be quite unique here. It took me several days of trying various approaches until I went back to BIOS as last resort. It cannot be emphasized enough especially when you are upgrading 18.04 from older version.
answered Jul 19 '18 at 19:13
crdevcrdev
1
add a comment |
Add modprobe.blacklist=nouveau to kernel cmdline. This worked on my laptop.
answered 2 hours ago
Zhang BoyangZhang Boyang
11
New contributor
Zhang Boyang is a new contributor to this site. Take care in asking for clarification, commenting, and answering.
Check out our Code of Conduct.
add a comment |
Your Answer
StackExchange.ready(function() {
var channelOptions = {
tags: "".split(" "),
id: "89"
};
initTagRenderer("".split(" "), "".split(" "), channelOptions);
StackExchange.using("externalEditor", function() {
// Have to fire editor after snippets, if snippets enabled
if (StackExchange.settings.snippets.snippetsEnabled) {
StackExchange.using("snippets", function() {
createEditor();
});
}
else {
createEditor();
}
});
function createEditor() {
StackExchange.prepareEditor({
heartbeatType: 'answer',
autoActivateHeartbeat: false,
convertImagesToLinks: true,
noModals: true,
showLowRepImageUploadWarning: true,
reputationToPostImages: 10,
bindNavPrevention: true,
postfix: "",
imageUploader: {
brandingHtml: "Powered by u003ca class="icon-imgur-white" href="https://imgur.com/"u003eu003c/au003e",
contentPolicyHtml: "User contributions licensed under u003ca href="https://creativecommons.org/licenses/by-sa/3.0/"u003ecc by-sa 3.0 with attribution requiredu003c/au003e u003ca href="https://stackoverflow.com/legal/content-policy"u003e(content policy)u003c/au003e",
allowUrls: true
},
onDemand: true,
discardSelector: ".discard-answer"
,immediatelyShowMarkdownHelp:true
});
}
});
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%2f1031511%2fcant-disable-nouveau-drivers-in-ubuntu-18-04%23new-answer', 'question_page');
}
);
Post as a guest
Required, but never shown
5 Answers
5
active
oldest
votes
5 Answers
5
active
oldest
votes
active
oldest
votes
active
oldest
votes
I found the solution. I'll write it here for who may have the same problem.
My gdm3 session was running in wayland. To check it:
$ loginctl
SESSION UID USER SEAT TTY
2 1000 velix seat0 tty2
c2 1000 velix
c1 120 gdm seat0 tty1
The command loginctl show-session <session-n> -p Type show the session type:
$ loginctl show-session c1 -p Type
Type=Wayland
To change it, edit the file /etc/gdm3/custom.conf and uncomment the line WaylandEnable=false.
After rebooting:
$ loginctl show-session c1 -p Type
Type=x11
Now blacklisting nouveau drivers in /etc/modprobe.d/blacklist.conf (as in the question) works and doesn't give the above error.
The key point is to run xorg instead of wayland
(That's why it was working in my 17.10 ubuntu, forced to run xorg)
answered May 4 '18 at 13:34
velixvelix
2861213
+1 Thanks for sharing. Don't forget to accept your answer by clicking check mark next to it in a day or so when it lets you.
– WinEunuuchs2Unix
May 4 '18 at 23:13
1
Gives black screen on a MacBook, answer no longer works?
– Gabor
May 9 '18 at 2:10
My answer is 5 days old. This method is still working on my notebook.
– velix
May 9 '18 at 16:24
On a MacBook, where I have the error same as in your screenshot, I only get a black screen. Loginctl also errors out withFailed to create bus connection
– Gabor
May 9 '18 at 20:24
I think it's a different problem. Open a new question and put more info in that.
– velix
May 10 '18 at 9:58
|
show 2 more comments
I found the solution. I'll write it here for who may have the same problem.
My gdm3 session was running in wayland. To check it:
$ loginctl
SESSION UID USER SEAT TTY
2 1000 velix seat0 tty2
c2 1000 velix
c1 120 gdm seat0 tty1
The command loginctl show-session <session-n> -p Type show the session type:
$ loginctl show-session c1 -p Type
Type=Wayland
To change it, edit the file /etc/gdm3/custom.conf and uncomment the line WaylandEnable=false.
After rebooting:
$ loginctl show-session c1 -p Type
Type=x11
Now blacklisting nouveau drivers in /etc/modprobe.d/blacklist.conf (as in the question) works and doesn't give the above error.
The key point is to run xorg instead of wayland
(That's why it was working in my 17.10 ubuntu, forced to run xorg)
answered May 4 '18 at 13:34
velixvelix
2861213
+1 Thanks for sharing. Don't forget to accept your answer by clicking check mark next to it in a day or so when it lets you.
– WinEunuuchs2Unix
May 4 '18 at 23:13
1
Gives black screen on a MacBook, answer no longer works?
– Gabor
May 9 '18 at 2:10
My answer is 5 days old. This method is still working on my notebook.
– velix
May 9 '18 at 16:24
On a MacBook, where I have the error same as in your screenshot, I only get a black screen. Loginctl also errors out withFailed to create bus connection
– Gabor
May 9 '18 at 20:24
I think it's a different problem. Open a new question and put more info in that.
– velix
May 10 '18 at 9:58
|
show 2 more comments
I found the solution. I'll write it here for who may have the same problem.
My gdm3 session was running in wayland. To check it:
$ loginctl
SESSION UID USER SEAT TTY
2 1000 velix seat0 tty2
c2 1000 velix
c1 120 gdm seat0 tty1
The command loginctl show-session <session-n> -p Type show the session type:
$ loginctl show-session c1 -p Type
Type=Wayland
To change it, edit the file /etc/gdm3/custom.conf and uncomment the line WaylandEnable=false.
After rebooting:
$ loginctl show-session c1 -p Type
Type=x11
Now blacklisting nouveau drivers in /etc/modprobe.d/blacklist.conf (as in the question) works and doesn't give the above error.
The key point is to run xorg instead of wayland
(That's why it was working in my 17.10 ubuntu, forced to run xorg)
answered May 4 '18 at 13:34
velixvelix
2861213
I found the solution. I'll write it here for who may have the same problem.
My gdm3 session was running in wayland. To check it:
$ loginctl
SESSION UID USER SEAT TTY
2 1000 velix seat0 tty2
c2 1000 velix
c1 120 gdm seat0 tty1
The command loginctl show-session <session-n> -p Type show the session type:
$ loginctl show-session c1 -p Type
Type=Wayland
To change it, edit the file /etc/gdm3/custom.conf and uncomment the line WaylandEnable=false.
After rebooting:
$ loginctl show-session c1 -p Type
Type=x11
Now blacklisting nouveau drivers in /etc/modprobe.d/blacklist.conf (as in the question) works and doesn't give the above error.
The key point is to run xorg instead of wayland
(That's why it was working in my 17.10 ubuntu, forced to run xorg)
answered May 4 '18 at 13:34
velixvelix
2861213
edited May 29 '18 at 17:57
answered May 4 '18 at 13:34
velixvelix
2861213
answered May 4 '18 at 13:34
velixvelix
2861213
answered May 4 '18 at 13:34
velixvelix
2861213
2861213
+1 Thanks for sharing. Don't forget to accept your answer by clicking check mark next to it in a day or so when it lets you.
– WinEunuuchs2Unix
May 4 '18 at 23:13
1
Gives black screen on a MacBook, answer no longer works?
– Gabor
May 9 '18 at 2:10
My answer is 5 days old. This method is still working on my notebook.
– velix
May 9 '18 at 16:24
On a MacBook, where I have the error same as in your screenshot, I only get a black screen. Loginctl also errors out withFailed to create bus connection
– Gabor
May 9 '18 at 20:24
I think it's a different problem. Open a new question and put more info in that.
– velix
May 10 '18 at 9:58
|
show 2 more comments
+1 Thanks for sharing. Don't forget to accept your answer by clicking check mark next to it in a day or so when it lets you.
– WinEunuuchs2Unix
May 4 '18 at 23:13
1
Gives black screen on a MacBook, answer no longer works?
– Gabor
May 9 '18 at 2:10
My answer is 5 days old. This method is still working on my notebook.
– velix
May 9 '18 at 16:24
On a MacBook, where I have the error same as in your screenshot, I only get a black screen. Loginctl also errors out withFailed to create bus connection
– Gabor
May 9 '18 at 20:24
I think it's a different problem. Open a new question and put more info in that.
– velix
May 10 '18 at 9:58
+1 Thanks for sharing. Don't forget to accept your answer by clicking check mark next to it in a day or so when it lets you.
– WinEunuuchs2Unix
May 4 '18 at 23:13
+1 Thanks for sharing. Don't forget to accept your answer by clicking check mark next to it in a day or so when it lets you.
– WinEunuuchs2Unix
May 4 '18 at 23:13
1
1
Gives black screen on a MacBook, answer no longer works?
– Gabor
May 9 '18 at 2:10
Gives black screen on a MacBook, answer no longer works?
– Gabor
May 9 '18 at 2:10
My answer is 5 days old. This method is still working on my notebook.
– velix
May 9 '18 at 16:24
My answer is 5 days old. This method is still working on my notebook.
– velix
May 9 '18 at 16:24
On a MacBook, where I have the error same as in your screenshot, I only get a black screen. Loginctl also errors out with
Failed to create bus connection– Gabor
May 9 '18 at 20:24
On a MacBook, where I have the error same as in your screenshot, I only get a black screen. Loginctl also errors out with
Failed to create bus connection– Gabor
May 9 '18 at 20:24
I think it's a different problem. Open a new question and put more info in that.
– velix
May 10 '18 at 9:58
I think it's a different problem. Open a new question and put more info in that.
– velix
May 10 '18 at 9:58
|
show 2 more comments
https://bugs.launchpad.net/nvidia-drivers-ubuntu/+bug/1784598
try:
sudo systemctl disable nvidia-fallback.service
answered Jul 31 '18 at 10:10
heeenheeen
1212
add a comment |
https://bugs.launchpad.net/nvidia-drivers-ubuntu/+bug/1784598
try:
sudo systemctl disable nvidia-fallback.service
answered Jul 31 '18 at 10:10
heeenheeen
1212
add a comment |
https://bugs.launchpad.net/nvidia-drivers-ubuntu/+bug/1784598
try:
sudo systemctl disable nvidia-fallback.service
answered Jul 31 '18 at 10:10
heeenheeen
1212
https://bugs.launchpad.net/nvidia-drivers-ubuntu/+bug/1784598
try:
sudo systemctl disable nvidia-fallback.service
answered Jul 31 '18 at 10:10
heeenheeen
1212
answered Jul 31 '18 at 10:10
heeenheeen
1212
answered Jul 31 '18 at 10:10
heeenheeen
1212
answered Jul 31 '18 at 10:10
heeenheeen
1212
1212
add a comment |
add a comment |
Got exactly same problem, my configuration is x11 (returned by loginctl command).
The only way working for me at the moment is to rename the nouveau file module.
# pwd
/lib/modules/4.15.0-20-generic/kernel/drivers/gpu/drm/nouveau
# mv nouveau.ko nouveau.ko-old
# reboot
dirty solution but working, hope it will help. Of course, all was fine in 17.10.
answered May 23 '18 at 16:30
lightmanlightman
112
add a comment |
Got exactly same problem, my configuration is x11 (returned by loginctl command).
The only way working for me at the moment is to rename the nouveau file module.
# pwd
/lib/modules/4.15.0-20-generic/kernel/drivers/gpu/drm/nouveau
# mv nouveau.ko nouveau.ko-old
# reboot
dirty solution but working, hope it will help. Of course, all was fine in 17.10.
answered May 23 '18 at 16:30
lightmanlightman
112
add a comment |
Got exactly same problem, my configuration is x11 (returned by loginctl command).
The only way working for me at the moment is to rename the nouveau file module.
# pwd
/lib/modules/4.15.0-20-generic/kernel/drivers/gpu/drm/nouveau
# mv nouveau.ko nouveau.ko-old
# reboot
dirty solution but working, hope it will help. Of course, all was fine in 17.10.
answered May 23 '18 at 16:30
lightmanlightman
112
Got exactly same problem, my configuration is x11 (returned by loginctl command).
The only way working for me at the moment is to rename the nouveau file module.
# pwd
/lib/modules/4.15.0-20-generic/kernel/drivers/gpu/drm/nouveau
# mv nouveau.ko nouveau.ko-old
# reboot
dirty solution but working, hope it will help. Of course, all was fine in 17.10.
answered May 23 '18 at 16:30
lightmanlightman
112
answered May 23 '18 at 16:30
lightmanlightman
112
answered May 23 '18 at 16:30
lightmanlightman
112
answered May 23 '18 at 16:30
lightmanlightman
112
112
add a comment |
add a comment |
Don't forget to disable Secure Boot in BIOS especially when you want nvidia (and not nouveau) driver working. Otherwise it will quite always fall back back to nouveau no matter what you do.
Also note that "Secure Boot" option can be hidden in BIOS under various options on various places and often that option is not saying anything about "Secure Boot" but sometimes it's called "Other OS" similar. Every BIOS can be quite unique here. It took me several days of trying various approaches until I went back to BIOS as last resort. It cannot be emphasized enough especially when you are upgrading 18.04 from older version.
answered Jul 19 '18 at 19:13
crdevcrdev
1
add a comment |
Don't forget to disable Secure Boot in BIOS especially when you want nvidia (and not nouveau) driver working. Otherwise it will quite always fall back back to nouveau no matter what you do.
Also note that "Secure Boot" option can be hidden in BIOS under various options on various places and often that option is not saying anything about "Secure Boot" but sometimes it's called "Other OS" similar. Every BIOS can be quite unique here. It took me several days of trying various approaches until I went back to BIOS as last resort. It cannot be emphasized enough especially when you are upgrading 18.04 from older version.
answered Jul 19 '18 at 19:13
crdevcrdev
1
add a comment |
Don't forget to disable Secure Boot in BIOS especially when you want nvidia (and not nouveau) driver working. Otherwise it will quite always fall back back to nouveau no matter what you do.
Also note that "Secure Boot" option can be hidden in BIOS under various options on various places and often that option is not saying anything about "Secure Boot" but sometimes it's called "Other OS" similar. Every BIOS can be quite unique here. It took me several days of trying various approaches until I went back to BIOS as last resort. It cannot be emphasized enough especially when you are upgrading 18.04 from older version.
answered Jul 19 '18 at 19:13
crdevcrdev
1
Don't forget to disable Secure Boot in BIOS especially when you want nvidia (and not nouveau) driver working. Otherwise it will quite always fall back back to nouveau no matter what you do.
Also note that "Secure Boot" option can be hidden in BIOS under various options on various places and often that option is not saying anything about "Secure Boot" but sometimes it's called "Other OS" similar. Every BIOS can be quite unique here. It took me several days of trying various approaches until I went back to BIOS as last resort. It cannot be emphasized enough especially when you are upgrading 18.04 from older version.
answered Jul 19 '18 at 19:13
crdevcrdev
1
answered Jul 19 '18 at 19:13
crdevcrdev
1
answered Jul 19 '18 at 19:13
crdevcrdev
1
answered Jul 19 '18 at 19:13
crdevcrdev
1
1
add a comment |
add a comment |
Add modprobe.blacklist=nouveau to kernel cmdline. This worked on my laptop.
answered 2 hours ago
Zhang BoyangZhang Boyang
11
New contributor
Zhang Boyang is a new contributor to this site. Take care in asking for clarification, commenting, and answering.
Check out our Code of Conduct.
add a comment |
Add modprobe.blacklist=nouveau to kernel cmdline. This worked on my laptop.
answered 2 hours ago
Zhang BoyangZhang Boyang
11
New contributor
Zhang Boyang is a new contributor to this site. Take care in asking for clarification, commenting, and answering.
Check out our Code of Conduct.
add a comment |
Add modprobe.blacklist=nouveau to kernel cmdline. This worked on my laptop.
answered 2 hours ago
Zhang BoyangZhang Boyang
11
New contributor
Zhang Boyang is a new contributor to this site. Take care in asking for clarification, commenting, and answering.
Check out our Code of Conduct.
Add modprobe.blacklist=nouveau to kernel cmdline. This worked on my laptop.
answered 2 hours ago
Zhang BoyangZhang Boyang
11
New contributor
Zhang Boyang is a new contributor to this site. Take care in asking for clarification, commenting, and answering.
Check out our Code of Conduct.
answered 2 hours ago
Zhang BoyangZhang Boyang
11
New contributor
Zhang Boyang is a new contributor to this site. Take care in asking for clarification, commenting, and answering.
Check out our Code of Conduct.
answered 2 hours ago
Zhang BoyangZhang Boyang
11
answered 2 hours ago
Zhang BoyangZhang Boyang
11
11
New contributor
Zhang Boyang is a new contributor to this site. Take care in asking for clarification, commenting, and answering.
Check out our Code of Conduct.
New contributor
Zhang Boyang is a new contributor to this site. Take care in asking for clarification, commenting, and answering.
Check out our Code of Conduct.
Zhang Boyang is a new contributor to this site. Take care in asking for clarification, commenting, and answering.
Check out our Code of Conduct.
add a comment |
add a comment |
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.
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%2f1031511%2fcant-disable-nouveau-drivers-in-ubuntu-18-04%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
