Boot hangs after upgrade from 16.04 to 18.04.1
1
I upgraded from 16.04 to 18.04.1 and all seemed to go OK. But when I rebooted, the system hangs.
Early in the boot process, I get the error message:
Error no video mode activated
The last lines shown are:
[ 5.901767] pps_core: LinuxPPS API ver. 1 registered
[ 5.906814] pps_core: Software ver. 5.3.6 - Copyright 2005-2007 Rodolfo Giometti <giometti@linux.it>
[ 5.916187] clocksource: Switched to clocksource tsc
[ 5.921562] piix4_smbus 0000:00:14.0: SMBus Host Controller at 0xb00, revision 0
[ 5.929183] piix4_smbus 0000:00:14.0: Auxiliary SMBus Host Controller at 0xb20
[ 5.937026] impi message handler version 3.92
[ 5.942086] PTP clock support registered
[ 5.942222] hidraw: raw HID events driver (C) Jiri Kosina
I can ping the system when it's hung, but I can't ssh into it.
I can boot into recovery mode, bring up a root shell, and see all my files.
When I resume normal boot from recovery mode, I get a flickering error message:
[ 256.522705] do_IRQ: 1.36 No irq handler for vector
This continues indefinitely.
The specs on my video card are:
EVGA GeForce GTX 660Ti PCI-E 3.0 2048MB 2 DVI, 1 HDMI 1.4, 1 DisplayPort;
2048MB GDDR5 Memory (192 bit);
Base Clock: 915 MHz;
Memory Bandwidth: 144.192 GB/sec Supports NVIDIA CUDA: 1344 CUDA Cores
Is this problem related to the 18.04.1 video driver?
How do I fix it?
boot
edited Jan 12 at 16:13
Android Dev
10.8k63360
asked Jan 12 at 2:57
Tom SpeerTom Speer
62
|
show 12 more comments
1
I upgraded from 16.04 to 18.04.1 and all seemed to go OK. But when I rebooted, the system hangs.
Early in the boot process, I get the error message:
Error no video mode activated
The last lines shown are:
[ 5.901767] pps_core: LinuxPPS API ver. 1 registered
[ 5.906814] pps_core: Software ver. 5.3.6 - Copyright 2005-2007 Rodolfo Giometti <giometti@linux.it>
[ 5.916187] clocksource: Switched to clocksource tsc
[ 5.921562] piix4_smbus 0000:00:14.0: SMBus Host Controller at 0xb00, revision 0
[ 5.929183] piix4_smbus 0000:00:14.0: Auxiliary SMBus Host Controller at 0xb20
[ 5.937026] impi message handler version 3.92
[ 5.942086] PTP clock support registered
[ 5.942222] hidraw: raw HID events driver (C) Jiri Kosina
I can ping the system when it's hung, but I can't ssh into it.
I can boot into recovery mode, bring up a root shell, and see all my files.
When I resume normal boot from recovery mode, I get a flickering error message:
[ 256.522705] do_IRQ: 1.36 No irq handler for vector
This continues indefinitely.
The specs on my video card are:
EVGA GeForce GTX 660Ti PCI-E 3.0 2048MB 2 DVI, 1 HDMI 1.4, 1 DisplayPort;
2048MB GDDR5 Memory (192 bit);
Base Clock: 915 MHz;
Memory Bandwidth: 144.192 GB/sec Supports NVIDIA CUDA: 1344 CUDA Cores
Is this problem related to the 18.04.1 video driver?
How do I fix it?
boot
edited Jan 12 at 16:13
Android Dev
10.8k63360
asked Jan 12 at 2:57
Tom SpeerTom Speer
62
Did you uninstall video driver before upgrading, and then boot with nomodeset (like a new install) and install new nVidia driver? See section on adding nomodeset to linux line in grub menu when booting. askubuntu.com/questions/162075/… I have a slightly newer nVidia card and open source drive works well. You may also need to first purge old driver? ubuntuforums.org/…
– oldfred
Jan 12 at 17:27
I did not knowingly uninstall the video driver. I booted with nomodeset in the Linux boot command. This time the boot process got further. One step failed with the error Failed to start VirtualBox Linux Kernel module
– Tom Speer
Jan 13 at 1:14
The last line completed in the boot was Started Update UTMP about System Runlevel Changes
– Tom Speer
Jan 13 at 1:24
So is this an install in VirtualBox? I do not know VirtualBox and its unique issues. Often last posted line is not issue, but one several lines above it. Have you tried recovery mode, that includes nomodeset automatically and boots to a menu of repair options or command line.
– oldfred
Jan 13 at 4:29
No, it's not an install in VirtualBox. It's an upgrade from 16.04 to 18.04.1. I'm just reporting the symptoms I see, since I don't know enough to make sense of them. I'm hoping that someone knows what the next steps in the boot process are so they can identify where it's going wrong. I've tried tried recovery mode. I can get to a root shell, but can't proceed much past that.
– Tom Speer
Jan 13 at 5:59
|
show 12 more comments
1
1
1
I upgraded from 16.04 to 18.04.1 and all seemed to go OK. But when I rebooted, the system hangs.
Early in the boot process, I get the error message:
Error no video mode activated
The last lines shown are:
[ 5.901767] pps_core: LinuxPPS API ver. 1 registered
[ 5.906814] pps_core: Software ver. 5.3.6 - Copyright 2005-2007 Rodolfo Giometti <giometti@linux.it>
[ 5.916187] clocksource: Switched to clocksource tsc
[ 5.921562] piix4_smbus 0000:00:14.0: SMBus Host Controller at 0xb00, revision 0
[ 5.929183] piix4_smbus 0000:00:14.0: Auxiliary SMBus Host Controller at 0xb20
[ 5.937026] impi message handler version 3.92
[ 5.942086] PTP clock support registered
[ 5.942222] hidraw: raw HID events driver (C) Jiri Kosina
I can ping the system when it's hung, but I can't ssh into it.
I can boot into recovery mode, bring up a root shell, and see all my files.
When I resume normal boot from recovery mode, I get a flickering error message:
[ 256.522705] do_IRQ: 1.36 No irq handler for vector
This continues indefinitely.
The specs on my video card are:
EVGA GeForce GTX 660Ti PCI-E 3.0 2048MB 2 DVI, 1 HDMI 1.4, 1 DisplayPort;
2048MB GDDR5 Memory (192 bit);
Base Clock: 915 MHz;
Memory Bandwidth: 144.192 GB/sec Supports NVIDIA CUDA: 1344 CUDA Cores
Is this problem related to the 18.04.1 video driver?
How do I fix it?
boot
edited Jan 12 at 16:13
Android Dev
10.8k63360
asked Jan 12 at 2:57
Tom SpeerTom Speer
62
I upgraded from 16.04 to 18.04.1 and all seemed to go OK. But when I rebooted, the system hangs.
Early in the boot process, I get the error message:
Error no video mode activated
The last lines shown are:
[ 5.901767] pps_core: LinuxPPS API ver. 1 registered
[ 5.906814] pps_core: Software ver. 5.3.6 - Copyright 2005-2007 Rodolfo Giometti <giometti@linux.it>
[ 5.916187] clocksource: Switched to clocksource tsc
[ 5.921562] piix4_smbus 0000:00:14.0: SMBus Host Controller at 0xb00, revision 0
[ 5.929183] piix4_smbus 0000:00:14.0: Auxiliary SMBus Host Controller at 0xb20
[ 5.937026] impi message handler version 3.92
[ 5.942086] PTP clock support registered
[ 5.942222] hidraw: raw HID events driver (C) Jiri Kosina
I can ping the system when it's hung, but I can't ssh into it.
I can boot into recovery mode, bring up a root shell, and see all my files.
When I resume normal boot from recovery mode, I get a flickering error message:
[ 256.522705] do_IRQ: 1.36 No irq handler for vector
This continues indefinitely.
The specs on my video card are:
EVGA GeForce GTX 660Ti PCI-E 3.0 2048MB 2 DVI, 1 HDMI 1.4, 1 DisplayPort;
2048MB GDDR5 Memory (192 bit);
Base Clock: 915 MHz;
Memory Bandwidth: 144.192 GB/sec Supports NVIDIA CUDA: 1344 CUDA Cores
Is this problem related to the 18.04.1 video driver?
How do I fix it?
boot
boot
edited Jan 12 at 16:13
Android Dev
10.8k63360
asked Jan 12 at 2:57
Tom SpeerTom Speer
62
edited Jan 12 at 16:13
Android Dev
10.8k63360
asked Jan 12 at 2:57
Tom SpeerTom Speer
62
edited Jan 12 at 16:13
Android Dev
10.8k63360
edited Jan 12 at 16:13
Android Dev
10.8k63360
edited Jan 12 at 16:13
Android Dev
10.8k63360
10.8k63360
asked Jan 12 at 2:57
Tom SpeerTom Speer
62
asked Jan 12 at 2:57
Tom SpeerTom Speer
62
asked Jan 12 at 2:57
Tom SpeerTom Speer
62
62
Did you uninstall video driver before upgrading, and then boot with nomodeset (like a new install) and install new nVidia driver? See section on adding nomodeset to linux line in grub menu when booting. askubuntu.com/questions/162075/… I have a slightly newer nVidia card and open source drive works well. You may also need to first purge old driver? ubuntuforums.org/…
– oldfred
Jan 12 at 17:27
I did not knowingly uninstall the video driver. I booted with nomodeset in the Linux boot command. This time the boot process got further. One step failed with the error Failed to start VirtualBox Linux Kernel module
– Tom Speer
Jan 13 at 1:14
The last line completed in the boot was Started Update UTMP about System Runlevel Changes
– Tom Speer
Jan 13 at 1:24
So is this an install in VirtualBox? I do not know VirtualBox and its unique issues. Often last posted line is not issue, but one several lines above it. Have you tried recovery mode, that includes nomodeset automatically and boots to a menu of repair options or command line.
– oldfred
Jan 13 at 4:29
No, it's not an install in VirtualBox. It's an upgrade from 16.04 to 18.04.1. I'm just reporting the symptoms I see, since I don't know enough to make sense of them. I'm hoping that someone knows what the next steps in the boot process are so they can identify where it's going wrong. I've tried tried recovery mode. I can get to a root shell, but can't proceed much past that.
– Tom Speer
Jan 13 at 5:59
|
show 12 more comments
Did you uninstall video driver before upgrading, and then boot with nomodeset (like a new install) and install new nVidia driver? See section on adding nomodeset to linux line in grub menu when booting. askubuntu.com/questions/162075/… I have a slightly newer nVidia card and open source drive works well. You may also need to first purge old driver? ubuntuforums.org/…
– oldfred
Jan 12 at 17:27
I did not knowingly uninstall the video driver. I booted with nomodeset in the Linux boot command. This time the boot process got further. One step failed with the error Failed to start VirtualBox Linux Kernel module
– Tom Speer
Jan 13 at 1:14
The last line completed in the boot was Started Update UTMP about System Runlevel Changes
– Tom Speer
Jan 13 at 1:24
So is this an install in VirtualBox? I do not know VirtualBox and its unique issues. Often last posted line is not issue, but one several lines above it. Have you tried recovery mode, that includes nomodeset automatically and boots to a menu of repair options or command line.
– oldfred
Jan 13 at 4:29
No, it's not an install in VirtualBox. It's an upgrade from 16.04 to 18.04.1. I'm just reporting the symptoms I see, since I don't know enough to make sense of them. I'm hoping that someone knows what the next steps in the boot process are so they can identify where it's going wrong. I've tried tried recovery mode. I can get to a root shell, but can't proceed much past that.
– Tom Speer
Jan 13 at 5:59
Did you uninstall video driver before upgrading, and then boot with nomodeset (like a new install) and install new nVidia driver? See section on adding nomodeset to linux line in grub menu when booting. askubuntu.com/questions/162075/… I have a slightly newer nVidia card and open source drive works well. You may also need to first purge old driver? ubuntuforums.org/…
– oldfred
Jan 12 at 17:27
Did you uninstall video driver before upgrading, and then boot with nomodeset (like a new install) and install new nVidia driver? See section on adding nomodeset to linux line in grub menu when booting. askubuntu.com/questions/162075/… I have a slightly newer nVidia card and open source drive works well. You may also need to first purge old driver? ubuntuforums.org/…
– oldfred
Jan 12 at 17:27
I did not knowingly uninstall the video driver. I booted with nomodeset in the Linux boot command. This time the boot process got further. One step failed with the error Failed to start VirtualBox Linux Kernel module
– Tom Speer
Jan 13 at 1:14
I did not knowingly uninstall the video driver. I booted with nomodeset in the Linux boot command. This time the boot process got further. One step failed with the error Failed to start VirtualBox Linux Kernel module
– Tom Speer
Jan 13 at 1:14
The last line completed in the boot was Started Update UTMP about System Runlevel Changes
– Tom Speer
Jan 13 at 1:24
The last line completed in the boot was Started Update UTMP about System Runlevel Changes
– Tom Speer
Jan 13 at 1:24
So is this an install in VirtualBox? I do not know VirtualBox and its unique issues. Often last posted line is not issue, but one several lines above it. Have you tried recovery mode, that includes nomodeset automatically and boots to a menu of repair options or command line.
– oldfred
Jan 13 at 4:29
So is this an install in VirtualBox? I do not know VirtualBox and its unique issues. Often last posted line is not issue, but one several lines above it. Have you tried recovery mode, that includes nomodeset automatically and boots to a menu of repair options or command line.
– oldfred
Jan 13 at 4:29
No, it's not an install in VirtualBox. It's an upgrade from 16.04 to 18.04.1. I'm just reporting the symptoms I see, since I don't know enough to make sense of them. I'm hoping that someone knows what the next steps in the boot process are so they can identify where it's going wrong. I've tried tried recovery mode. I can get to a root shell, but can't proceed much past that.
– Tom Speer
Jan 13 at 5:59
No, it's not an install in VirtualBox. It's an upgrade from 16.04 to 18.04.1. I'm just reporting the symptoms I see, since I don't know enough to make sense of them. I'm hoping that someone knows what the next steps in the boot process are so they can identify where it's going wrong. I've tried tried recovery mode. I can get to a root shell, but can't proceed much past that.
– Tom Speer
Jan 13 at 5:59
|
show 12 more comments
0
active
oldest
votes
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
});
}
});
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%2f1109043%2fboot-hangs-after-upgrade-from-16-04-to-18-04-1%23new-answer', 'question_page');
}
);
Post as a guest
Required, but never shown
0
active
oldest
votes
0
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.
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%2f1109043%2fboot-hangs-after-upgrade-from-16-04-to-18-04-1%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
Did you uninstall video driver before upgrading, and then boot with nomodeset (like a new install) and install new nVidia driver? See section on adding nomodeset to linux line in grub menu when booting. askubuntu.com/questions/162075/… I have a slightly newer nVidia card and open source drive works well. You may also need to first purge old driver? ubuntuforums.org/…
– oldfred
Jan 12 at 17:27
I did not knowingly uninstall the video driver. I booted with nomodeset in the Linux boot command. This time the boot process got further. One step failed with the error Failed to start VirtualBox Linux Kernel module
– Tom Speer
Jan 13 at 1:14
The last line completed in the boot was Started Update UTMP about System Runlevel Changes
– Tom Speer
Jan 13 at 1:24
So is this an install in VirtualBox? I do not know VirtualBox and its unique issues. Often last posted line is not issue, but one several lines above it. Have you tried recovery mode, that includes nomodeset automatically and boots to a menu of repair options or command line.
– oldfred
Jan 13 at 4:29
No, it's not an install in VirtualBox. It's an upgrade from 16.04 to 18.04.1. I'm just reporting the symptoms I see, since I don't know enough to make sense of them. I'm hoping that someone knows what the next steps in the boot process are so they can identify where it's going wrong. I've tried tried recovery mode. I can get to a root shell, but can't proceed much past that.
– Tom Speer
Jan 13 at 5:59