Screen blank after upgrading to 18.10
0
So I just upgrade my HTPC from 18.04 to 18.10. It has a built in AMD video card and it is plugged in to my tv with a HDMI cable and it is set to autmatically log in. After the upgrade, the computer will boot and have the ubuntu hue like the log in prompt is coming then the screen will go black. I plugged it into a much smaller TV and it did fine but for some reason it doesn't like my wide screen. Any ideas?
video 18.10
asked Mar 16 at 0:20
Phillip HallPhillip Hall
11
|
show 9 more comments
0
So I just upgrade my HTPC from 18.04 to 18.10. It has a built in AMD video card and it is plugged in to my tv with a HDMI cable and it is set to autmatically log in. After the upgrade, the computer will boot and have the ubuntu hue like the log in prompt is coming then the screen will go black. I plugged it into a much smaller TV and it did fine but for some reason it doesn't like my wide screen. Any ideas?
video 18.10
asked Mar 16 at 0:20
Phillip HallPhillip Hall
11
Computer specs needed. Specifically CPU, GPU, and if possible, hardware specs of your TVs. Did you uninstall all graphics drivers as recommended prior to upgrade?
– avisitoritseems
Mar 16 at 0:48
CPU AMD A8-9600 GPU Integrated AMD Radeon R series. The tv is 10 yrs old Samsung LCD. I didn't uninstall all graphic drivers prior to upgrade. Didn't know I was supposed to. I guess that could be the problem.
– Phillip Hall
Mar 16 at 11:38
Try addingradeon.modeset=0and/oracpi=offto your GRUB. Add it after the wordsquiet splashwithin the quotes of that line. There's some more to make that a permanent fix if it works, but for now let's see if that works. Have you tried to see if the issue is replicated when using a live USB that has 18.04 or 18.10 installed on it?
– avisitoritseems
Mar 16 at 15:54
Actually since you do have access to your screen on the smaller one, what you can try is opening terminal,sudo nano /etc/default/grub, and addingradeon.modeset=0to the line beginning inGRUB_CMDLINE_LINUX_DEFAULT. That or just purge and reinstall your video drivers. This is interesting to me, I didn't think AMD drivers had issues like Nvidia does.
– avisitoritseems
Mar 16 at 17:38
None of that works. I haven't tried purging and reinstalling the drivers yet.
– Phillip Hall
Mar 16 at 17:54
|
show 9 more comments
0
0
0
So I just upgrade my HTPC from 18.04 to 18.10. It has a built in AMD video card and it is plugged in to my tv with a HDMI cable and it is set to autmatically log in. After the upgrade, the computer will boot and have the ubuntu hue like the log in prompt is coming then the screen will go black. I plugged it into a much smaller TV and it did fine but for some reason it doesn't like my wide screen. Any ideas?
video 18.10
asked Mar 16 at 0:20
Phillip HallPhillip Hall
11
So I just upgrade my HTPC from 18.04 to 18.10. It has a built in AMD video card and it is plugged in to my tv with a HDMI cable and it is set to autmatically log in. After the upgrade, the computer will boot and have the ubuntu hue like the log in prompt is coming then the screen will go black. I plugged it into a much smaller TV and it did fine but for some reason it doesn't like my wide screen. Any ideas?
video 18.10
video 18.10
asked Mar 16 at 0:20
Phillip HallPhillip Hall
11
asked Mar 16 at 0:20
Phillip HallPhillip Hall
11
asked Mar 16 at 0:20
Phillip HallPhillip Hall
11
asked Mar 16 at 0:20
Phillip HallPhillip Hall
11
asked Mar 16 at 0:20
Phillip HallPhillip Hall
11
11
Computer specs needed. Specifically CPU, GPU, and if possible, hardware specs of your TVs. Did you uninstall all graphics drivers as recommended prior to upgrade?
– avisitoritseems
Mar 16 at 0:48
CPU AMD A8-9600 GPU Integrated AMD Radeon R series. The tv is 10 yrs old Samsung LCD. I didn't uninstall all graphic drivers prior to upgrade. Didn't know I was supposed to. I guess that could be the problem.
– Phillip Hall
Mar 16 at 11:38
Try addingradeon.modeset=0and/oracpi=offto your GRUB. Add it after the wordsquiet splashwithin the quotes of that line. There's some more to make that a permanent fix if it works, but for now let's see if that works. Have you tried to see if the issue is replicated when using a live USB that has 18.04 or 18.10 installed on it?
– avisitoritseems
Mar 16 at 15:54
Actually since you do have access to your screen on the smaller one, what you can try is opening terminal,sudo nano /etc/default/grub, and addingradeon.modeset=0to the line beginning inGRUB_CMDLINE_LINUX_DEFAULT. That or just purge and reinstall your video drivers. This is interesting to me, I didn't think AMD drivers had issues like Nvidia does.
– avisitoritseems
Mar 16 at 17:38
None of that works. I haven't tried purging and reinstalling the drivers yet.
– Phillip Hall
Mar 16 at 17:54
|
show 9 more comments
Computer specs needed. Specifically CPU, GPU, and if possible, hardware specs of your TVs. Did you uninstall all graphics drivers as recommended prior to upgrade?
– avisitoritseems
Mar 16 at 0:48
CPU AMD A8-9600 GPU Integrated AMD Radeon R series. The tv is 10 yrs old Samsung LCD. I didn't uninstall all graphic drivers prior to upgrade. Didn't know I was supposed to. I guess that could be the problem.
– Phillip Hall
Mar 16 at 11:38
Try addingradeon.modeset=0and/oracpi=offto your GRUB. Add it after the wordsquiet splashwithin the quotes of that line. There's some more to make that a permanent fix if it works, but for now let's see if that works. Have you tried to see if the issue is replicated when using a live USB that has 18.04 or 18.10 installed on it?
– avisitoritseems
Mar 16 at 15:54
Actually since you do have access to your screen on the smaller one, what you can try is opening terminal,sudo nano /etc/default/grub, and addingradeon.modeset=0to the line beginning inGRUB_CMDLINE_LINUX_DEFAULT. That or just purge and reinstall your video drivers. This is interesting to me, I didn't think AMD drivers had issues like Nvidia does.
– avisitoritseems
Mar 16 at 17:38
None of that works. I haven't tried purging and reinstalling the drivers yet.
– Phillip Hall
Mar 16 at 17:54
Computer specs needed. Specifically CPU, GPU, and if possible, hardware specs of your TVs. Did you uninstall all graphics drivers as recommended prior to upgrade?
– avisitoritseems
Mar 16 at 0:48
Computer specs needed. Specifically CPU, GPU, and if possible, hardware specs of your TVs. Did you uninstall all graphics drivers as recommended prior to upgrade?
– avisitoritseems
Mar 16 at 0:48
CPU AMD A8-9600 GPU Integrated AMD Radeon R series. The tv is 10 yrs old Samsung LCD. I didn't uninstall all graphic drivers prior to upgrade. Didn't know I was supposed to. I guess that could be the problem.
– Phillip Hall
Mar 16 at 11:38
CPU AMD A8-9600 GPU Integrated AMD Radeon R series. The tv is 10 yrs old Samsung LCD. I didn't uninstall all graphic drivers prior to upgrade. Didn't know I was supposed to. I guess that could be the problem.
– Phillip Hall
Mar 16 at 11:38
Try adding
radeon.modeset=0 and/or acpi=off to your GRUB. Add it after the words quiet splash within the quotes of that line. There's some more to make that a permanent fix if it works, but for now let's see if that works. Have you tried to see if the issue is replicated when using a live USB that has 18.04 or 18.10 installed on it?– avisitoritseems
Mar 16 at 15:54
Try adding
radeon.modeset=0 and/or acpi=off to your GRUB. Add it after the words quiet splash within the quotes of that line. There's some more to make that a permanent fix if it works, but for now let's see if that works. Have you tried to see if the issue is replicated when using a live USB that has 18.04 or 18.10 installed on it?– avisitoritseems
Mar 16 at 15:54
Actually since you do have access to your screen on the smaller one, what you can try is opening terminal,
sudo nano /etc/default/grub, and adding radeon.modeset=0 to the line beginning in GRUB_CMDLINE_LINUX_DEFAULT. That or just purge and reinstall your video drivers. This is interesting to me, I didn't think AMD drivers had issues like Nvidia does.– avisitoritseems
Mar 16 at 17:38
Actually since you do have access to your screen on the smaller one, what you can try is opening terminal,
sudo nano /etc/default/grub, and adding radeon.modeset=0 to the line beginning in GRUB_CMDLINE_LINUX_DEFAULT. That or just purge and reinstall your video drivers. This is interesting to me, I didn't think AMD drivers had issues like Nvidia does.– avisitoritseems
Mar 16 at 17:38
None of that works. I haven't tried purging and reinstalling the drivers yet.
– Phillip Hall
Mar 16 at 17:54
None of that works. I haven't tried purging and reinstalling the drivers yet.
– Phillip Hall
Mar 16 at 17:54
|
show 9 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%2f1126053%2fscreen-blank-after-upgrading-to-18-10%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%2f1126053%2fscreen-blank-after-upgrading-to-18-10%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
Computer specs needed. Specifically CPU, GPU, and if possible, hardware specs of your TVs. Did you uninstall all graphics drivers as recommended prior to upgrade?
– avisitoritseems
Mar 16 at 0:48
CPU AMD A8-9600 GPU Integrated AMD Radeon R series. The tv is 10 yrs old Samsung LCD. I didn't uninstall all graphic drivers prior to upgrade. Didn't know I was supposed to. I guess that could be the problem.
– Phillip Hall
Mar 16 at 11:38
Try adding
radeon.modeset=0and/oracpi=offto your GRUB. Add it after the wordsquiet splashwithin the quotes of that line. There's some more to make that a permanent fix if it works, but for now let's see if that works. Have you tried to see if the issue is replicated when using a live USB that has 18.04 or 18.10 installed on it?– avisitoritseems
Mar 16 at 15:54
Actually since you do have access to your screen on the smaller one, what you can try is opening terminal,
sudo nano /etc/default/grub, and addingradeon.modeset=0to the line beginning inGRUB_CMDLINE_LINUX_DEFAULT. That or just purge and reinstall your video drivers. This is interesting to me, I didn't think AMD drivers had issues like Nvidia does.– avisitoritseems
Mar 16 at 17:38
None of that works. I haven't tried purging and reinstalling the drivers yet.
– Phillip Hall
Mar 16 at 17:54