Upgrade to 18.04 from 16.04: cannot boot into desktop











up vote
0
down vote

favorite












Have an older Dell Inspirion 5720 that I just upgraded to 18.04...



When the machine rebooted, it basically goes into an endless wait state: the GUI never loads and if I flip around on the terminals, I see the error message:



nouveau: .... MMIO write of 00000001f FAULT at 6013d4 [ IBUS ]
A start job is running for hold until boot process finishes up (no limit)



I can ssh into the box, and dmsg shows this:



[    1.755073] nouveau 0000:01:00.0: fb: 1024 MiB GDDR5
[ 1.761716] nouveau 0000:01:00.0: volt: couldn't find speedo value, volting not possible
[ 1.761769] nouveau 0000:01:00.0: bus: MMIO read of 00000000 FAULT at 612004 [ IBUS ]
...
[ 26.653007] nouveau 0000:01:00.0: bus: MMIO write of 0000001f FAULT at 6013d4 [ IBUS ]
[ 37.565957] nouveau 0000:01:00.0: bus: MMIO write of 0000001f FAULT at 6013d4 [ IBUS ]


With the last two messages repeating...



I've tried blacklisting the nouveau drivers from the kernel by adding a blacklist directive into a new .conf file in /etc/modprobe.d and specifying that nouveau never is loaded again by aliasing it to /bin/false in /etc/modprobe.d/blacklist.conf.



I also tried adding "nomodeset" to GRUB bootloader and rebooting, but no love at all.



Here's all the related output from journalctl -b:



root@mongoid:/home/mshallop# journalctl -b | grep nouveau
Nov 12 12:39:46 mongoid kernel: nouveau 0000:01:00.0: NVIDIA GF117 (0d7000a2)
Nov 12 12:39:46 mongoid kernel: nouveau 0000:01:00.0: bios: version 75.17.33.00.01
Nov 12 12:39:46 mongoid kernel: nouveau 0000:01:00.0: fb: 1024 MiB GDDR5
Nov 12 12:39:46 mongoid kernel: nouveau 0000:01:00.0: volt: couldn't find speedo value, volting not possible
Nov 12 12:39:46 mongoid kernel: nouveau 0000:01:00.0: bus: MMIO read of 00000000 FAULT at 612004 [ IBUS ]
Nov 12 12:39:46 mongoid kernel: nouveau 0000:01:00.0: DRM: VRAM: 1024 MiB
Nov 12 12:39:46 mongoid kernel: nouveau 0000:01:00.0: DRM: GART: 1048576 MiB
Nov 12 12:39:46 mongoid kernel: nouveau 0000:01:00.0: DRM: Pointer to TMDS table invalid
Nov 12 12:39:46 mongoid kernel: nouveau 0000:01:00.0: DRM: DCB version 4.0
Nov 12 12:39:46 mongoid kernel: nouveau 0000:01:00.0: DRM: MM: using COPY0 for buffer copies
Nov 12 12:39:46 mongoid kernel: [drm] Initialized nouveau 1.3.1 20120801 for 0000:01:00.0 on minor 1
Nov 12 12:39:48 mongoid sensors[886]: nouveau-pci-0100
Nov 12 12:39:48 mongoid /usr/lib/gdm3/gdm-x-session[999]: (==) Matched nouveau as autoconfigured driver 0
Nov 12 12:39:48 mongoid /usr/lib/gdm3/gdm-x-session[999]: (II) LoadModule: "nouveau"
Nov 12 12:39:48 mongoid /usr/lib/gdm3/gdm-x-session[999]: (II) Loading /usr/lib/xorg/modules/drivers/nouveau_drv.so
Nov 12 12:39:48 mongoid /usr/lib/gdm3/gdm-x-session[999]: (II) Module nouveau: vendor="X.Org Foundation"
Nov 12 12:39:48 mongoid /usr/lib/gdm3/gdm-x-session[999]: (II) [drm] nouveau interface version: 1.3.1
Nov 12 12:39:48 mongoid kernel: nouveau 0000:01:00.0: bus: MMIO write of ffffff1f FAULT at 6013d4 [ IBUS ]
Nov 12 12:39:48 mongoid kernel: nouveau 0000:01:00.0: bus: MMIO write of badf1001 FAULT at 50405c [ IBUS ]
Nov 12 12:39:48 mongoid /usr/lib/gdm3/gdm-x-session[999]: (II) NOUVEAU(G0): [DRI2] DRI driver: nouveau
Nov 12 12:39:48 mongoid /usr/lib/gdm3/gdm-x-session[999]: (II) NOUVEAU(G0): [DRI2] VDPAU driver: nouveau
Nov 12 12:40:02 mongoid kernel: nouveau 0000:01:00.0: bus: MMIO write of 0000001f FAULT at 6013d4 [ IBUS ]
Nov 12 12:40:13 mongoid kernel: nouveau 0000:01:00.0: bus: MMIO write of 0000001f FAULT at 6013d4 [ IBUS ]


How do I disable this (or better, remove) this mod that's dorking my system?



Thanks!










share|improve this question
























  • nomodeset should be enough to load a default desktop with decreased resolution but allowing you to install/reinstall the recommended Nvidia drivers needed for your graphics. But I'm not sure about what you did before as it may have created a different conflict.
    – GabrielaGarcia
    Nov 12 at 20:59















up vote
0
down vote

favorite












Have an older Dell Inspirion 5720 that I just upgraded to 18.04...



When the machine rebooted, it basically goes into an endless wait state: the GUI never loads and if I flip around on the terminals, I see the error message:



nouveau: .... MMIO write of 00000001f FAULT at 6013d4 [ IBUS ]
A start job is running for hold until boot process finishes up (no limit)



I can ssh into the box, and dmsg shows this:



[    1.755073] nouveau 0000:01:00.0: fb: 1024 MiB GDDR5
[ 1.761716] nouveau 0000:01:00.0: volt: couldn't find speedo value, volting not possible
[ 1.761769] nouveau 0000:01:00.0: bus: MMIO read of 00000000 FAULT at 612004 [ IBUS ]
...
[ 26.653007] nouveau 0000:01:00.0: bus: MMIO write of 0000001f FAULT at 6013d4 [ IBUS ]
[ 37.565957] nouveau 0000:01:00.0: bus: MMIO write of 0000001f FAULT at 6013d4 [ IBUS ]


With the last two messages repeating...



I've tried blacklisting the nouveau drivers from the kernel by adding a blacklist directive into a new .conf file in /etc/modprobe.d and specifying that nouveau never is loaded again by aliasing it to /bin/false in /etc/modprobe.d/blacklist.conf.



I also tried adding "nomodeset" to GRUB bootloader and rebooting, but no love at all.



Here's all the related output from journalctl -b:



root@mongoid:/home/mshallop# journalctl -b | grep nouveau
Nov 12 12:39:46 mongoid kernel: nouveau 0000:01:00.0: NVIDIA GF117 (0d7000a2)
Nov 12 12:39:46 mongoid kernel: nouveau 0000:01:00.0: bios: version 75.17.33.00.01
Nov 12 12:39:46 mongoid kernel: nouveau 0000:01:00.0: fb: 1024 MiB GDDR5
Nov 12 12:39:46 mongoid kernel: nouveau 0000:01:00.0: volt: couldn't find speedo value, volting not possible
Nov 12 12:39:46 mongoid kernel: nouveau 0000:01:00.0: bus: MMIO read of 00000000 FAULT at 612004 [ IBUS ]
Nov 12 12:39:46 mongoid kernel: nouveau 0000:01:00.0: DRM: VRAM: 1024 MiB
Nov 12 12:39:46 mongoid kernel: nouveau 0000:01:00.0: DRM: GART: 1048576 MiB
Nov 12 12:39:46 mongoid kernel: nouveau 0000:01:00.0: DRM: Pointer to TMDS table invalid
Nov 12 12:39:46 mongoid kernel: nouveau 0000:01:00.0: DRM: DCB version 4.0
Nov 12 12:39:46 mongoid kernel: nouveau 0000:01:00.0: DRM: MM: using COPY0 for buffer copies
Nov 12 12:39:46 mongoid kernel: [drm] Initialized nouveau 1.3.1 20120801 for 0000:01:00.0 on minor 1
Nov 12 12:39:48 mongoid sensors[886]: nouveau-pci-0100
Nov 12 12:39:48 mongoid /usr/lib/gdm3/gdm-x-session[999]: (==) Matched nouveau as autoconfigured driver 0
Nov 12 12:39:48 mongoid /usr/lib/gdm3/gdm-x-session[999]: (II) LoadModule: "nouveau"
Nov 12 12:39:48 mongoid /usr/lib/gdm3/gdm-x-session[999]: (II) Loading /usr/lib/xorg/modules/drivers/nouveau_drv.so
Nov 12 12:39:48 mongoid /usr/lib/gdm3/gdm-x-session[999]: (II) Module nouveau: vendor="X.Org Foundation"
Nov 12 12:39:48 mongoid /usr/lib/gdm3/gdm-x-session[999]: (II) [drm] nouveau interface version: 1.3.1
Nov 12 12:39:48 mongoid kernel: nouveau 0000:01:00.0: bus: MMIO write of ffffff1f FAULT at 6013d4 [ IBUS ]
Nov 12 12:39:48 mongoid kernel: nouveau 0000:01:00.0: bus: MMIO write of badf1001 FAULT at 50405c [ IBUS ]
Nov 12 12:39:48 mongoid /usr/lib/gdm3/gdm-x-session[999]: (II) NOUVEAU(G0): [DRI2] DRI driver: nouveau
Nov 12 12:39:48 mongoid /usr/lib/gdm3/gdm-x-session[999]: (II) NOUVEAU(G0): [DRI2] VDPAU driver: nouveau
Nov 12 12:40:02 mongoid kernel: nouveau 0000:01:00.0: bus: MMIO write of 0000001f FAULT at 6013d4 [ IBUS ]
Nov 12 12:40:13 mongoid kernel: nouveau 0000:01:00.0: bus: MMIO write of 0000001f FAULT at 6013d4 [ IBUS ]


How do I disable this (or better, remove) this mod that's dorking my system?



Thanks!










share|improve this question
























  • nomodeset should be enough to load a default desktop with decreased resolution but allowing you to install/reinstall the recommended Nvidia drivers needed for your graphics. But I'm not sure about what you did before as it may have created a different conflict.
    – GabrielaGarcia
    Nov 12 at 20:59













up vote
0
down vote

favorite









up vote
0
down vote

favorite











Have an older Dell Inspirion 5720 that I just upgraded to 18.04...



When the machine rebooted, it basically goes into an endless wait state: the GUI never loads and if I flip around on the terminals, I see the error message:



nouveau: .... MMIO write of 00000001f FAULT at 6013d4 [ IBUS ]
A start job is running for hold until boot process finishes up (no limit)



I can ssh into the box, and dmsg shows this:



[    1.755073] nouveau 0000:01:00.0: fb: 1024 MiB GDDR5
[ 1.761716] nouveau 0000:01:00.0: volt: couldn't find speedo value, volting not possible
[ 1.761769] nouveau 0000:01:00.0: bus: MMIO read of 00000000 FAULT at 612004 [ IBUS ]
...
[ 26.653007] nouveau 0000:01:00.0: bus: MMIO write of 0000001f FAULT at 6013d4 [ IBUS ]
[ 37.565957] nouveau 0000:01:00.0: bus: MMIO write of 0000001f FAULT at 6013d4 [ IBUS ]


With the last two messages repeating...



I've tried blacklisting the nouveau drivers from the kernel by adding a blacklist directive into a new .conf file in /etc/modprobe.d and specifying that nouveau never is loaded again by aliasing it to /bin/false in /etc/modprobe.d/blacklist.conf.



I also tried adding "nomodeset" to GRUB bootloader and rebooting, but no love at all.



Here's all the related output from journalctl -b:



root@mongoid:/home/mshallop# journalctl -b | grep nouveau
Nov 12 12:39:46 mongoid kernel: nouveau 0000:01:00.0: NVIDIA GF117 (0d7000a2)
Nov 12 12:39:46 mongoid kernel: nouveau 0000:01:00.0: bios: version 75.17.33.00.01
Nov 12 12:39:46 mongoid kernel: nouveau 0000:01:00.0: fb: 1024 MiB GDDR5
Nov 12 12:39:46 mongoid kernel: nouveau 0000:01:00.0: volt: couldn't find speedo value, volting not possible
Nov 12 12:39:46 mongoid kernel: nouveau 0000:01:00.0: bus: MMIO read of 00000000 FAULT at 612004 [ IBUS ]
Nov 12 12:39:46 mongoid kernel: nouveau 0000:01:00.0: DRM: VRAM: 1024 MiB
Nov 12 12:39:46 mongoid kernel: nouveau 0000:01:00.0: DRM: GART: 1048576 MiB
Nov 12 12:39:46 mongoid kernel: nouveau 0000:01:00.0: DRM: Pointer to TMDS table invalid
Nov 12 12:39:46 mongoid kernel: nouveau 0000:01:00.0: DRM: DCB version 4.0
Nov 12 12:39:46 mongoid kernel: nouveau 0000:01:00.0: DRM: MM: using COPY0 for buffer copies
Nov 12 12:39:46 mongoid kernel: [drm] Initialized nouveau 1.3.1 20120801 for 0000:01:00.0 on minor 1
Nov 12 12:39:48 mongoid sensors[886]: nouveau-pci-0100
Nov 12 12:39:48 mongoid /usr/lib/gdm3/gdm-x-session[999]: (==) Matched nouveau as autoconfigured driver 0
Nov 12 12:39:48 mongoid /usr/lib/gdm3/gdm-x-session[999]: (II) LoadModule: "nouveau"
Nov 12 12:39:48 mongoid /usr/lib/gdm3/gdm-x-session[999]: (II) Loading /usr/lib/xorg/modules/drivers/nouveau_drv.so
Nov 12 12:39:48 mongoid /usr/lib/gdm3/gdm-x-session[999]: (II) Module nouveau: vendor="X.Org Foundation"
Nov 12 12:39:48 mongoid /usr/lib/gdm3/gdm-x-session[999]: (II) [drm] nouveau interface version: 1.3.1
Nov 12 12:39:48 mongoid kernel: nouveau 0000:01:00.0: bus: MMIO write of ffffff1f FAULT at 6013d4 [ IBUS ]
Nov 12 12:39:48 mongoid kernel: nouveau 0000:01:00.0: bus: MMIO write of badf1001 FAULT at 50405c [ IBUS ]
Nov 12 12:39:48 mongoid /usr/lib/gdm3/gdm-x-session[999]: (II) NOUVEAU(G0): [DRI2] DRI driver: nouveau
Nov 12 12:39:48 mongoid /usr/lib/gdm3/gdm-x-session[999]: (II) NOUVEAU(G0): [DRI2] VDPAU driver: nouveau
Nov 12 12:40:02 mongoid kernel: nouveau 0000:01:00.0: bus: MMIO write of 0000001f FAULT at 6013d4 [ IBUS ]
Nov 12 12:40:13 mongoid kernel: nouveau 0000:01:00.0: bus: MMIO write of 0000001f FAULT at 6013d4 [ IBUS ]


How do I disable this (or better, remove) this mod that's dorking my system?



Thanks!










share|improve this question















Have an older Dell Inspirion 5720 that I just upgraded to 18.04...



When the machine rebooted, it basically goes into an endless wait state: the GUI never loads and if I flip around on the terminals, I see the error message:



nouveau: .... MMIO write of 00000001f FAULT at 6013d4 [ IBUS ]
A start job is running for hold until boot process finishes up (no limit)



I can ssh into the box, and dmsg shows this:



[    1.755073] nouveau 0000:01:00.0: fb: 1024 MiB GDDR5
[ 1.761716] nouveau 0000:01:00.0: volt: couldn't find speedo value, volting not possible
[ 1.761769] nouveau 0000:01:00.0: bus: MMIO read of 00000000 FAULT at 612004 [ IBUS ]
...
[ 26.653007] nouveau 0000:01:00.0: bus: MMIO write of 0000001f FAULT at 6013d4 [ IBUS ]
[ 37.565957] nouveau 0000:01:00.0: bus: MMIO write of 0000001f FAULT at 6013d4 [ IBUS ]


With the last two messages repeating...



I've tried blacklisting the nouveau drivers from the kernel by adding a blacklist directive into a new .conf file in /etc/modprobe.d and specifying that nouveau never is loaded again by aliasing it to /bin/false in /etc/modprobe.d/blacklist.conf.



I also tried adding "nomodeset" to GRUB bootloader and rebooting, but no love at all.



Here's all the related output from journalctl -b:



root@mongoid:/home/mshallop# journalctl -b | grep nouveau
Nov 12 12:39:46 mongoid kernel: nouveau 0000:01:00.0: NVIDIA GF117 (0d7000a2)
Nov 12 12:39:46 mongoid kernel: nouveau 0000:01:00.0: bios: version 75.17.33.00.01
Nov 12 12:39:46 mongoid kernel: nouveau 0000:01:00.0: fb: 1024 MiB GDDR5
Nov 12 12:39:46 mongoid kernel: nouveau 0000:01:00.0: volt: couldn't find speedo value, volting not possible
Nov 12 12:39:46 mongoid kernel: nouveau 0000:01:00.0: bus: MMIO read of 00000000 FAULT at 612004 [ IBUS ]
Nov 12 12:39:46 mongoid kernel: nouveau 0000:01:00.0: DRM: VRAM: 1024 MiB
Nov 12 12:39:46 mongoid kernel: nouveau 0000:01:00.0: DRM: GART: 1048576 MiB
Nov 12 12:39:46 mongoid kernel: nouveau 0000:01:00.0: DRM: Pointer to TMDS table invalid
Nov 12 12:39:46 mongoid kernel: nouveau 0000:01:00.0: DRM: DCB version 4.0
Nov 12 12:39:46 mongoid kernel: nouveau 0000:01:00.0: DRM: MM: using COPY0 for buffer copies
Nov 12 12:39:46 mongoid kernel: [drm] Initialized nouveau 1.3.1 20120801 for 0000:01:00.0 on minor 1
Nov 12 12:39:48 mongoid sensors[886]: nouveau-pci-0100
Nov 12 12:39:48 mongoid /usr/lib/gdm3/gdm-x-session[999]: (==) Matched nouveau as autoconfigured driver 0
Nov 12 12:39:48 mongoid /usr/lib/gdm3/gdm-x-session[999]: (II) LoadModule: "nouveau"
Nov 12 12:39:48 mongoid /usr/lib/gdm3/gdm-x-session[999]: (II) Loading /usr/lib/xorg/modules/drivers/nouveau_drv.so
Nov 12 12:39:48 mongoid /usr/lib/gdm3/gdm-x-session[999]: (II) Module nouveau: vendor="X.Org Foundation"
Nov 12 12:39:48 mongoid /usr/lib/gdm3/gdm-x-session[999]: (II) [drm] nouveau interface version: 1.3.1
Nov 12 12:39:48 mongoid kernel: nouveau 0000:01:00.0: bus: MMIO write of ffffff1f FAULT at 6013d4 [ IBUS ]
Nov 12 12:39:48 mongoid kernel: nouveau 0000:01:00.0: bus: MMIO write of badf1001 FAULT at 50405c [ IBUS ]
Nov 12 12:39:48 mongoid /usr/lib/gdm3/gdm-x-session[999]: (II) NOUVEAU(G0): [DRI2] DRI driver: nouveau
Nov 12 12:39:48 mongoid /usr/lib/gdm3/gdm-x-session[999]: (II) NOUVEAU(G0): [DRI2] VDPAU driver: nouveau
Nov 12 12:40:02 mongoid kernel: nouveau 0000:01:00.0: bus: MMIO write of 0000001f FAULT at 6013d4 [ IBUS ]
Nov 12 12:40:13 mongoid kernel: nouveau 0000:01:00.0: bus: MMIO write of 0000001f FAULT at 6013d4 [ IBUS ]


How do I disable this (or better, remove) this mod that's dorking my system?



Thanks!







boot drivers 18.04 nouveau






share|improve this question















share|improve this question













share|improve this question




share|improve this question








edited Nov 12 at 20:55

























asked Nov 12 at 20:49









Micheal Shallop

171118




171118












  • nomodeset should be enough to load a default desktop with decreased resolution but allowing you to install/reinstall the recommended Nvidia drivers needed for your graphics. But I'm not sure about what you did before as it may have created a different conflict.
    – GabrielaGarcia
    Nov 12 at 20:59


















  • nomodeset should be enough to load a default desktop with decreased resolution but allowing you to install/reinstall the recommended Nvidia drivers needed for your graphics. But I'm not sure about what you did before as it may have created a different conflict.
    – GabrielaGarcia
    Nov 12 at 20:59
















nomodeset should be enough to load a default desktop with decreased resolution but allowing you to install/reinstall the recommended Nvidia drivers needed for your graphics. But I'm not sure about what you did before as it may have created a different conflict.
– GabrielaGarcia
Nov 12 at 20:59




nomodeset should be enough to load a default desktop with decreased resolution but allowing you to install/reinstall the recommended Nvidia drivers needed for your graphics. But I'm not sure about what you did before as it may have created a different conflict.
– GabrielaGarcia
Nov 12 at 20:59










1 Answer
1






active

oldest

votes

















up vote
1
down vote



accepted










try blacklisting nouveau completely:



sudo bash -c "echo blacklist nouveau > /etc/modprobe.d/blacklist-nvidia-nouveau.conf"
sudo bash -c "echo options nouveau modeset=0 >> /etc/modprobe.d/blacklist-nvidia-nouveau.conf"
sudo update-initramfs -u


and finally reboot the system.



you might also try running the following command:



sudo ubuntu-drivers autoinstall





share|improve this answer








New contributor




ImStackWIthWorkOverflow is a new contributor to this site. Take care in asking for clarification, commenting, and answering.
Check out our Code of Conduct.


















  • thanks for the answer - I was forgetting the update-initramfs directive... ugh... once I was able to boot, I forced an update and then updated again... I'm cleanly booting into the 4.15 kernel... now I need to unscrew the other box the 18.04 update messed up there, too...
    – Micheal Shallop
    Nov 12 at 22:06











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',
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
});


}
});














 

draft saved


draft discarded


















StackExchange.ready(
function () {
StackExchange.openid.initPostLogin('.new-post-login', 'https%3a%2f%2faskubuntu.com%2fquestions%2f1092341%2fupgrade-to-18-04-from-16-04-cannot-boot-into-desktop%23new-answer', 'question_page');
}
);

Post as a guest















Required, but never shown

























1 Answer
1






active

oldest

votes








1 Answer
1






active

oldest

votes









active

oldest

votes






active

oldest

votes








up vote
1
down vote



accepted










try blacklisting nouveau completely:



sudo bash -c "echo blacklist nouveau > /etc/modprobe.d/blacklist-nvidia-nouveau.conf"
sudo bash -c "echo options nouveau modeset=0 >> /etc/modprobe.d/blacklist-nvidia-nouveau.conf"
sudo update-initramfs -u


and finally reboot the system.



you might also try running the following command:



sudo ubuntu-drivers autoinstall





share|improve this answer








New contributor




ImStackWIthWorkOverflow is a new contributor to this site. Take care in asking for clarification, commenting, and answering.
Check out our Code of Conduct.


















  • thanks for the answer - I was forgetting the update-initramfs directive... ugh... once I was able to boot, I forced an update and then updated again... I'm cleanly booting into the 4.15 kernel... now I need to unscrew the other box the 18.04 update messed up there, too...
    – Micheal Shallop
    Nov 12 at 22:06















up vote
1
down vote



accepted










try blacklisting nouveau completely:



sudo bash -c "echo blacklist nouveau > /etc/modprobe.d/blacklist-nvidia-nouveau.conf"
sudo bash -c "echo options nouveau modeset=0 >> /etc/modprobe.d/blacklist-nvidia-nouveau.conf"
sudo update-initramfs -u


and finally reboot the system.



you might also try running the following command:



sudo ubuntu-drivers autoinstall





share|improve this answer








New contributor




ImStackWIthWorkOverflow is a new contributor to this site. Take care in asking for clarification, commenting, and answering.
Check out our Code of Conduct.


















  • thanks for the answer - I was forgetting the update-initramfs directive... ugh... once I was able to boot, I forced an update and then updated again... I'm cleanly booting into the 4.15 kernel... now I need to unscrew the other box the 18.04 update messed up there, too...
    – Micheal Shallop
    Nov 12 at 22:06













up vote
1
down vote



accepted







up vote
1
down vote



accepted






try blacklisting nouveau completely:



sudo bash -c "echo blacklist nouveau > /etc/modprobe.d/blacklist-nvidia-nouveau.conf"
sudo bash -c "echo options nouveau modeset=0 >> /etc/modprobe.d/blacklist-nvidia-nouveau.conf"
sudo update-initramfs -u


and finally reboot the system.



you might also try running the following command:



sudo ubuntu-drivers autoinstall





share|improve this answer








New contributor




ImStackWIthWorkOverflow is a new contributor to this site. Take care in asking for clarification, commenting, and answering.
Check out our Code of Conduct.









try blacklisting nouveau completely:



sudo bash -c "echo blacklist nouveau > /etc/modprobe.d/blacklist-nvidia-nouveau.conf"
sudo bash -c "echo options nouveau modeset=0 >> /etc/modprobe.d/blacklist-nvidia-nouveau.conf"
sudo update-initramfs -u


and finally reboot the system.



you might also try running the following command:



sudo ubuntu-drivers autoinstall






share|improve this answer








New contributor




ImStackWIthWorkOverflow is a new contributor to this site. Take care in asking for clarification, commenting, and answering.
Check out our Code of Conduct.









share|improve this answer



share|improve this answer






New contributor




ImStackWIthWorkOverflow is a new contributor to this site. Take care in asking for clarification, commenting, and answering.
Check out our Code of Conduct.









answered Nov 12 at 21:04









ImStackWIthWorkOverflow

263




263




New contributor




ImStackWIthWorkOverflow is a new contributor to this site. Take care in asking for clarification, commenting, and answering.
Check out our Code of Conduct.





New contributor





ImStackWIthWorkOverflow is a new contributor to this site. Take care in asking for clarification, commenting, and answering.
Check out our Code of Conduct.






ImStackWIthWorkOverflow is a new contributor to this site. Take care in asking for clarification, commenting, and answering.
Check out our Code of Conduct.












  • thanks for the answer - I was forgetting the update-initramfs directive... ugh... once I was able to boot, I forced an update and then updated again... I'm cleanly booting into the 4.15 kernel... now I need to unscrew the other box the 18.04 update messed up there, too...
    – Micheal Shallop
    Nov 12 at 22:06


















  • thanks for the answer - I was forgetting the update-initramfs directive... ugh... once I was able to boot, I forced an update and then updated again... I'm cleanly booting into the 4.15 kernel... now I need to unscrew the other box the 18.04 update messed up there, too...
    – Micheal Shallop
    Nov 12 at 22:06
















thanks for the answer - I was forgetting the update-initramfs directive... ugh... once I was able to boot, I forced an update and then updated again... I'm cleanly booting into the 4.15 kernel... now I need to unscrew the other box the 18.04 update messed up there, too...
– Micheal Shallop
Nov 12 at 22:06




thanks for the answer - I was forgetting the update-initramfs directive... ugh... once I was able to boot, I forced an update and then updated again... I'm cleanly booting into the 4.15 kernel... now I need to unscrew the other box the 18.04 update messed up there, too...
– Micheal Shallop
Nov 12 at 22:06


















 

draft saved


draft discarded



















































 


draft saved


draft discarded














StackExchange.ready(
function () {
StackExchange.openid.initPostLogin('.new-post-login', 'https%3a%2f%2faskubuntu.com%2fquestions%2f1092341%2fupgrade-to-18-04-from-16-04-cannot-boot-into-desktop%23new-answer', 'question_page');
}
);

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







Popular posts from this blog

How to change which sound is reproduced for terminal bell?

Title Spacing in Bjornstrup Chapter, Removing Chapter Number From Contents

Can I use Tabulator js library in my java Spring + Thymeleaf project?