After Ubuntu 18.04 reinstall, monitor stops working
I am running Ubuntu 18.04 on an old Acer Aspire e1-470p pc (with Intel HD Graphics 4000 Graphics processor) connected to a Viewsonic VX2703MH-LED monitor by HDMI.
I corrupted my boot options (probably by toggling UEFI and Secure settings in an attempt to boot Ubuntu Live ) leading to an inability to boot into either Win10 or my Ubuntu. I was able to partially resolve the issue by installing a new 18.04 version alongside my old 18.04.1. Previously my Viewsonic monitor was working with an HDMI connection to my Acer Aspire.
The details of my problems leading up to this point are here.
Old noob corrupted his dual boot, (bios legacy boot?). Any suggestions?
After installing Ubuntu alongside my previous installation, my PC boots well into the new install if the Viewsonic monitor is not connected, although still does not boot well into the old install. See above link for Train error.
However, if I boot with the Viewsonic monitor attached by HDMI cable, the GRUB interface appears on the monitor in large black and white screen. If I choose to boot, the screen monitor goes white with vertical stripes and then white with illegible black and white blocks of characters.
If I boot without the monitor attached, and wait until successful completion into Ubuntu, when I connect the Viewsonic monitor by HDMI nothing happens. My monitor does not detect any signal from the PC. (The monitor is working fine with my Raspberry Pi).

18.04 multiple-monitors hdmi monitor
add a comment |
I am running Ubuntu 18.04 on an old Acer Aspire e1-470p pc (with Intel HD Graphics 4000 Graphics processor) connected to a Viewsonic VX2703MH-LED monitor by HDMI.
I corrupted my boot options (probably by toggling UEFI and Secure settings in an attempt to boot Ubuntu Live ) leading to an inability to boot into either Win10 or my Ubuntu. I was able to partially resolve the issue by installing a new 18.04 version alongside my old 18.04.1. Previously my Viewsonic monitor was working with an HDMI connection to my Acer Aspire.
The details of my problems leading up to this point are here.
Old noob corrupted his dual boot, (bios legacy boot?). Any suggestions?
After installing Ubuntu alongside my previous installation, my PC boots well into the new install if the Viewsonic monitor is not connected, although still does not boot well into the old install. See above link for Train error.
However, if I boot with the Viewsonic monitor attached by HDMI cable, the GRUB interface appears on the monitor in large black and white screen. If I choose to boot, the screen monitor goes white with vertical stripes and then white with illegible black and white blocks of characters.
If I boot without the monitor attached, and wait until successful completion into Ubuntu, when I connect the Viewsonic monitor by HDMI nothing happens. My monitor does not detect any signal from the PC. (The monitor is working fine with my Raspberry Pi).

18.04 multiple-monitors hdmi monitor
Thank you. Powered off, unplugged the monitor and disconnected HDMI cables. Waited 30. Reconnected. No change.
– Pallama
Dec 30 '18 at 1:19
I added a link to an image of the monitor after booting.
– Pallama
Dec 30 '18 at 1:32
add a comment |
I am running Ubuntu 18.04 on an old Acer Aspire e1-470p pc (with Intel HD Graphics 4000 Graphics processor) connected to a Viewsonic VX2703MH-LED monitor by HDMI.
I corrupted my boot options (probably by toggling UEFI and Secure settings in an attempt to boot Ubuntu Live ) leading to an inability to boot into either Win10 or my Ubuntu. I was able to partially resolve the issue by installing a new 18.04 version alongside my old 18.04.1. Previously my Viewsonic monitor was working with an HDMI connection to my Acer Aspire.
The details of my problems leading up to this point are here.
Old noob corrupted his dual boot, (bios legacy boot?). Any suggestions?
After installing Ubuntu alongside my previous installation, my PC boots well into the new install if the Viewsonic monitor is not connected, although still does not boot well into the old install. See above link for Train error.
However, if I boot with the Viewsonic monitor attached by HDMI cable, the GRUB interface appears on the monitor in large black and white screen. If I choose to boot, the screen monitor goes white with vertical stripes and then white with illegible black and white blocks of characters.
If I boot without the monitor attached, and wait until successful completion into Ubuntu, when I connect the Viewsonic monitor by HDMI nothing happens. My monitor does not detect any signal from the PC. (The monitor is working fine with my Raspberry Pi).

18.04 multiple-monitors hdmi monitor
I am running Ubuntu 18.04 on an old Acer Aspire e1-470p pc (with Intel HD Graphics 4000 Graphics processor) connected to a Viewsonic VX2703MH-LED monitor by HDMI.
I corrupted my boot options (probably by toggling UEFI and Secure settings in an attempt to boot Ubuntu Live ) leading to an inability to boot into either Win10 or my Ubuntu. I was able to partially resolve the issue by installing a new 18.04 version alongside my old 18.04.1. Previously my Viewsonic monitor was working with an HDMI connection to my Acer Aspire.
The details of my problems leading up to this point are here.
Old noob corrupted his dual boot, (bios legacy boot?). Any suggestions?
After installing Ubuntu alongside my previous installation, my PC boots well into the new install if the Viewsonic monitor is not connected, although still does not boot well into the old install. See above link for Train error.
However, if I boot with the Viewsonic monitor attached by HDMI cable, the GRUB interface appears on the monitor in large black and white screen. If I choose to boot, the screen monitor goes white with vertical stripes and then white with illegible black and white blocks of characters.
If I boot without the monitor attached, and wait until successful completion into Ubuntu, when I connect the Viewsonic monitor by HDMI nothing happens. My monitor does not detect any signal from the PC. (The monitor is working fine with my Raspberry Pi).

18.04 multiple-monitors hdmi monitor
18.04 multiple-monitors hdmi monitor
edited Dec 31 '18 at 6:24
Sourav Ghosh
38329
38329
asked Dec 30 '18 at 0:36
PallamaPallama
86
86
Thank you. Powered off, unplugged the monitor and disconnected HDMI cables. Waited 30. Reconnected. No change.
– Pallama
Dec 30 '18 at 1:19
I added a link to an image of the monitor after booting.
– Pallama
Dec 30 '18 at 1:32
add a comment |
Thank you. Powered off, unplugged the monitor and disconnected HDMI cables. Waited 30. Reconnected. No change.
– Pallama
Dec 30 '18 at 1:19
I added a link to an image of the monitor after booting.
– Pallama
Dec 30 '18 at 1:32
Thank you. Powered off, unplugged the monitor and disconnected HDMI cables. Waited 30. Reconnected. No change.
– Pallama
Dec 30 '18 at 1:19
Thank you. Powered off, unplugged the monitor and disconnected HDMI cables. Waited 30. Reconnected. No change.
– Pallama
Dec 30 '18 at 1:19
I added a link to an image of the monitor after booting.
– Pallama
Dec 30 '18 at 1:32
I added a link to an image of the monitor after booting.
– Pallama
Dec 30 '18 at 1:32
add a comment |
1 Answer
1
active
oldest
votes
It seems to me that 18.04 have problem with some Radeon HD card. So this may not be related to your monitor but Kernel Mode Setting. You can try to add "nomodeset" kernel parameter in Grub before boot to see if this helps.
Thanks. “ro nomodeset quiet splash” was already in the boot file for most recent kernel. I tried removing nomodeset, and monitor loaded the splash screen but then stopped when logo disappeared. Tried quiet splash nouveu.modeset=0, same thing. So I am getting the purple Ubuntu screen instead of the black and white gibberish but doesn’t complete booting
– Pallama
Dec 31 '18 at 3:34
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%2f1105488%2fafter-ubuntu-18-04-reinstall-monitor-stops-working%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
It seems to me that 18.04 have problem with some Radeon HD card. So this may not be related to your monitor but Kernel Mode Setting. You can try to add "nomodeset" kernel parameter in Grub before boot to see if this helps.
Thanks. “ro nomodeset quiet splash” was already in the boot file for most recent kernel. I tried removing nomodeset, and monitor loaded the splash screen but then stopped when logo disappeared. Tried quiet splash nouveu.modeset=0, same thing. So I am getting the purple Ubuntu screen instead of the black and white gibberish but doesn’t complete booting
– Pallama
Dec 31 '18 at 3:34
add a comment |
It seems to me that 18.04 have problem with some Radeon HD card. So this may not be related to your monitor but Kernel Mode Setting. You can try to add "nomodeset" kernel parameter in Grub before boot to see if this helps.
Thanks. “ro nomodeset quiet splash” was already in the boot file for most recent kernel. I tried removing nomodeset, and monitor loaded the splash screen but then stopped when logo disappeared. Tried quiet splash nouveu.modeset=0, same thing. So I am getting the purple Ubuntu screen instead of the black and white gibberish but doesn’t complete booting
– Pallama
Dec 31 '18 at 3:34
add a comment |
It seems to me that 18.04 have problem with some Radeon HD card. So this may not be related to your monitor but Kernel Mode Setting. You can try to add "nomodeset" kernel parameter in Grub before boot to see if this helps.
It seems to me that 18.04 have problem with some Radeon HD card. So this may not be related to your monitor but Kernel Mode Setting. You can try to add "nomodeset" kernel parameter in Grub before boot to see if this helps.
answered Dec 30 '18 at 2:06
Maciej PolańskiMaciej Polański
11
11
Thanks. “ro nomodeset quiet splash” was already in the boot file for most recent kernel. I tried removing nomodeset, and monitor loaded the splash screen but then stopped when logo disappeared. Tried quiet splash nouveu.modeset=0, same thing. So I am getting the purple Ubuntu screen instead of the black and white gibberish but doesn’t complete booting
– Pallama
Dec 31 '18 at 3:34
add a comment |
Thanks. “ro nomodeset quiet splash” was already in the boot file for most recent kernel. I tried removing nomodeset, and monitor loaded the splash screen but then stopped when logo disappeared. Tried quiet splash nouveu.modeset=0, same thing. So I am getting the purple Ubuntu screen instead of the black and white gibberish but doesn’t complete booting
– Pallama
Dec 31 '18 at 3:34
Thanks. “ro nomodeset quiet splash” was already in the boot file for most recent kernel. I tried removing nomodeset, and monitor loaded the splash screen but then stopped when logo disappeared. Tried quiet splash nouveu.modeset=0, same thing. So I am getting the purple Ubuntu screen instead of the black and white gibberish but doesn’t complete booting
– Pallama
Dec 31 '18 at 3:34
Thanks. “ro nomodeset quiet splash” was already in the boot file for most recent kernel. I tried removing nomodeset, and monitor loaded the splash screen but then stopped when logo disappeared. Tried quiet splash nouveu.modeset=0, same thing. So I am getting the purple Ubuntu screen instead of the black and white gibberish but doesn’t complete booting
– Pallama
Dec 31 '18 at 3:34
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%2f1105488%2fafter-ubuntu-18-04-reinstall-monitor-stops-working%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
Thank you. Powered off, unplugged the monitor and disconnected HDMI cables. Waited 30. Reconnected. No change.
– Pallama
Dec 30 '18 at 1:19
I added a link to an image of the monitor after booting.
– Pallama
Dec 30 '18 at 1:32