AMD RX480 Screen flicker after update to 18.04
As mentioned in the title. Was upgrading from 17.10. Having this screen flickering.
My GPU is AMD RX480
What I did:
- Search for similar issues for 18.04, can't find any
- Perform fresh install. Still the same.
Please help. It is very annoying. I can't work.
18.04 flicker
add a comment |
As mentioned in the title. Was upgrading from 17.10. Having this screen flickering.
My GPU is AMD RX480
What I did:
- Search for similar issues for 18.04, can't find any
- Perform fresh install. Still the same.
Please help. It is very annoying. I can't work.
18.04 flicker
Join the ticket, the more people declare the problem, the faster the problem is solved bugs.launchpad.net/ubuntu/+source/xserver-xorg-video-amdgpu/…
– IvvanVG
Feb 1 at 14:15
add a comment |
As mentioned in the title. Was upgrading from 17.10. Having this screen flickering.
My GPU is AMD RX480
What I did:
- Search for similar issues for 18.04, can't find any
- Perform fresh install. Still the same.
Please help. It is very annoying. I can't work.
18.04 flicker
As mentioned in the title. Was upgrading from 17.10. Having this screen flickering.
My GPU is AMD RX480
What I did:
- Search for similar issues for 18.04, can't find any
- Perform fresh install. Still the same.
Please help. It is very annoying. I can't work.
18.04 flicker
18.04 flicker
edited May 5 '18 at 3:00
WinEunuuchs2Unix
46.7k1190182
46.7k1190182
asked Apr 29 '18 at 3:52
LaoPiSaiLaoPiSai
118211
118211
Join the ticket, the more people declare the problem, the faster the problem is solved bugs.launchpad.net/ubuntu/+source/xserver-xorg-video-amdgpu/…
– IvvanVG
Feb 1 at 14:15
add a comment |
Join the ticket, the more people declare the problem, the faster the problem is solved bugs.launchpad.net/ubuntu/+source/xserver-xorg-video-amdgpu/…
– IvvanVG
Feb 1 at 14:15
Join the ticket, the more people declare the problem, the faster the problem is solved bugs.launchpad.net/ubuntu/+source/xserver-xorg-video-amdgpu/…
– IvvanVG
Feb 1 at 14:15
Join the ticket, the more people declare the problem, the faster the problem is solved bugs.launchpad.net/ubuntu/+source/xserver-xorg-video-amdgpu/…
– IvvanVG
Feb 1 at 14:15
add a comment |
7 Answers
7
active
oldest
votes
I solved it myself by using amdgpu.dc=0 as a boot parameter.
To do this, edit the file /etc/default/grub, for example using
sudoedit /etc/default/grub
Find the line beginning GRUB_CMDLINE_LINUX_DEFAULT and add the text amdgpu.dc=0 between the double quotes (""). Leave any other parameters as they are. For example, you may end up with a line like this:
GRUB_CMDLINE_LINUX_DEFAULT="quiet splash amdgpu.dc=0"
Save the file and exit, and then run
sudo update-grub
to write the configuration, and reboot.
Getting a black screen, answer doesn't work any more?
– Gabor
May 9 '18 at 2:17
I had this problem and your solution worked! +1
– Ian Rehwinkel
May 17 '18 at 19:20
Hi all, if you update to 18.10, you need to reverse the changes or otherwise the flicker will return.
– LaoPiSai
Oct 30 '18 at 10:54
add a comment |
I have screen flickering problem when I'm connecting my laptop to my TV. I found that when I change the refresh rate from 60Hz to 59Hz this problem disappear.
Within Xorg (as I know 18.04 uses it by default) you can change the refresh rate by the help of xrandr:
0. First you must find the video output name to which you should assing the new mode. Just type xrandr and investigate which one is it. In my case this is HDMI-1.
1. Generate new modeline using cvt:
$ cvt 1920 1080 59
# 1920x1080 58.94 Hz (CVT) hsync: 66.02 kHz; pclk: 169.00 MHz
Modeline "1920x1080_59.00" 169.00 1920 2040 2240 2560 1080 1083 1088 1120 -hsync +vsync
1920and1080are the horizontal and vertical resolution's values.
59is the value of the refresh rate.
2. Create the new mode:
xrandr --newmode 1920x1080_59.00 169.00 1920 2040 2240 2560 1080 1083 1088 1120 -hsync +vsync
3. Assign the new mode to the video output:
xrandr --addmode HDMI-1 1920x1080_59.00
4. Activate the new mode:
xrandr --output HDMI-1 --mode 1920x1080_59.00
If the above works and the problem disappear, you should find a proper way to add and set this mode at the system startup. Here are few references about that:
- How can I make
xrandrcustomization permanent? - Adding newmode with Xrandr - "800x480_60.00"
- start up command
- Differences how to run scripts at startup
add a comment |
I've no answer here, but some observation and confirmation of problem. If someone finds this text: please stick to ubuntu 17.10 if you have radeon rx 580 (may be 480 and vegas)
Got myself to very same situation with 18.04 (upgrade, then fresh install). Amd rx 580 here, kernel 4.15.0-20.
What did not help:
- fresh install after upgrade
oibaf drivers
M-Bab custom kernel
4.17-rc3 kernel from main line ppa.- amdgpu.dc=1 as boot parameter (/etc/default/grub)
Update:
Apparently older kernel works. I've been tinkering with other distibutions and found that kernel 4.15.14 works for rx 580, you may want to try it from mainline ppa.
Hi, try amdgpu.dc=0. It solves the problem.
– LaoPiSai
May 5 '18 at 1:57
Kernel4.15is no longer maintained by Linux Kernel developers. You can also try the4.14chain from the same mainline PPA. It is maintained for 5 or 6 years. I'm using4.14.34myself as4.14.36and4.14.37had symbolic link bugs which prevented installing.
– WinEunuuchs2Unix
May 12 '18 at 22:31
add a comment |
Turn off the automatic brightness control to fix this.
add a comment |
I faced a similar problem,I wasn't able to log in with the graphical mode at all, I solved it by :
1- enter to tty mode (ctrl+alt+f5, en my case)
2- adding open grafic Drivers (https://launchpad.net/~oibaf/+archive/ubuntu/graphics-drivers):
sudo add-apt-repository ppa:oibaf/graphics-drivers
sudo apt-get update
3- reboot
4- enter into tty mode again
5-
sudo apt update && sudo apt full-upgrade
6- reboot and it works fine!!
hope it helps.
Thank you very much @Hassan for sharing the instructions. In my case I cannot get into the tty. Just to make sure, where do you ctrl+alt+f5? Does your computer have a fn key?
– Delosari
Jul 14 '18 at 23:01
add a comment |
Just got 4.19-rc1 kernel installed and flickering is completly gone, no need to restart PC no other magic - it works out of the box.
I'm using Arch now, but believe ubuntu's mainline kernel going to provide same experience. http://kernel.ubuntu.com/~kernel-ppa/mainline/v4.19-rc1/
add a comment |
I had the same issue with my RX580 (Kubuntu 18.04, Plasma 5). The flickering only started when the GPU got higher load (playing the Witcher 3 in my case).
First I installed the 4.19 kernel (which has amdgpu.dc=1 by default).
That alone didn't seem to help but maybe contributes to the fix.
Than, I set the screen refresh rate to 59.xx hz with the KDE monitor settings GUI.
After this, the problem seems to be fixed.
In my case the flickering started when I manually switched screen resolution with xrandr (without an explicit refresh rate setting), so maybe the refresh rate was misconfigured by those commands and only the refresh rate needed to be fixed.
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%2f1029517%2famd-rx480-screen-flicker-after-update-to-18-04%23new-answer', 'question_page');
}
);
Post as a guest
Required, but never shown
7 Answers
7
active
oldest
votes
7 Answers
7
active
oldest
votes
active
oldest
votes
active
oldest
votes
I solved it myself by using amdgpu.dc=0 as a boot parameter.
To do this, edit the file /etc/default/grub, for example using
sudoedit /etc/default/grub
Find the line beginning GRUB_CMDLINE_LINUX_DEFAULT and add the text amdgpu.dc=0 between the double quotes (""). Leave any other parameters as they are. For example, you may end up with a line like this:
GRUB_CMDLINE_LINUX_DEFAULT="quiet splash amdgpu.dc=0"
Save the file and exit, and then run
sudo update-grub
to write the configuration, and reboot.
Getting a black screen, answer doesn't work any more?
– Gabor
May 9 '18 at 2:17
I had this problem and your solution worked! +1
– Ian Rehwinkel
May 17 '18 at 19:20
Hi all, if you update to 18.10, you need to reverse the changes or otherwise the flicker will return.
– LaoPiSai
Oct 30 '18 at 10:54
add a comment |
I solved it myself by using amdgpu.dc=0 as a boot parameter.
To do this, edit the file /etc/default/grub, for example using
sudoedit /etc/default/grub
Find the line beginning GRUB_CMDLINE_LINUX_DEFAULT and add the text amdgpu.dc=0 between the double quotes (""). Leave any other parameters as they are. For example, you may end up with a line like this:
GRUB_CMDLINE_LINUX_DEFAULT="quiet splash amdgpu.dc=0"
Save the file and exit, and then run
sudo update-grub
to write the configuration, and reboot.
Getting a black screen, answer doesn't work any more?
– Gabor
May 9 '18 at 2:17
I had this problem and your solution worked! +1
– Ian Rehwinkel
May 17 '18 at 19:20
Hi all, if you update to 18.10, you need to reverse the changes or otherwise the flicker will return.
– LaoPiSai
Oct 30 '18 at 10:54
add a comment |
I solved it myself by using amdgpu.dc=0 as a boot parameter.
To do this, edit the file /etc/default/grub, for example using
sudoedit /etc/default/grub
Find the line beginning GRUB_CMDLINE_LINUX_DEFAULT and add the text amdgpu.dc=0 between the double quotes (""). Leave any other parameters as they are. For example, you may end up with a line like this:
GRUB_CMDLINE_LINUX_DEFAULT="quiet splash amdgpu.dc=0"
Save the file and exit, and then run
sudo update-grub
to write the configuration, and reboot.
I solved it myself by using amdgpu.dc=0 as a boot parameter.
To do this, edit the file /etc/default/grub, for example using
sudoedit /etc/default/grub
Find the line beginning GRUB_CMDLINE_LINUX_DEFAULT and add the text amdgpu.dc=0 between the double quotes (""). Leave any other parameters as they are. For example, you may end up with a line like this:
GRUB_CMDLINE_LINUX_DEFAULT="quiet splash amdgpu.dc=0"
Save the file and exit, and then run
sudo update-grub
to write the configuration, and reboot.
edited May 5 '18 at 16:41
Zanna
51k13138242
51k13138242
answered May 5 '18 at 1:55
LaoPiSaiLaoPiSai
118211
118211
Getting a black screen, answer doesn't work any more?
– Gabor
May 9 '18 at 2:17
I had this problem and your solution worked! +1
– Ian Rehwinkel
May 17 '18 at 19:20
Hi all, if you update to 18.10, you need to reverse the changes or otherwise the flicker will return.
– LaoPiSai
Oct 30 '18 at 10:54
add a comment |
Getting a black screen, answer doesn't work any more?
– Gabor
May 9 '18 at 2:17
I had this problem and your solution worked! +1
– Ian Rehwinkel
May 17 '18 at 19:20
Hi all, if you update to 18.10, you need to reverse the changes or otherwise the flicker will return.
– LaoPiSai
Oct 30 '18 at 10:54
Getting a black screen, answer doesn't work any more?
– Gabor
May 9 '18 at 2:17
Getting a black screen, answer doesn't work any more?
– Gabor
May 9 '18 at 2:17
I had this problem and your solution worked! +1
– Ian Rehwinkel
May 17 '18 at 19:20
I had this problem and your solution worked! +1
– Ian Rehwinkel
May 17 '18 at 19:20
Hi all, if you update to 18.10, you need to reverse the changes or otherwise the flicker will return.
– LaoPiSai
Oct 30 '18 at 10:54
Hi all, if you update to 18.10, you need to reverse the changes or otherwise the flicker will return.
– LaoPiSai
Oct 30 '18 at 10:54
add a comment |
I have screen flickering problem when I'm connecting my laptop to my TV. I found that when I change the refresh rate from 60Hz to 59Hz this problem disappear.
Within Xorg (as I know 18.04 uses it by default) you can change the refresh rate by the help of xrandr:
0. First you must find the video output name to which you should assing the new mode. Just type xrandr and investigate which one is it. In my case this is HDMI-1.
1. Generate new modeline using cvt:
$ cvt 1920 1080 59
# 1920x1080 58.94 Hz (CVT) hsync: 66.02 kHz; pclk: 169.00 MHz
Modeline "1920x1080_59.00" 169.00 1920 2040 2240 2560 1080 1083 1088 1120 -hsync +vsync
1920and1080are the horizontal and vertical resolution's values.
59is the value of the refresh rate.
2. Create the new mode:
xrandr --newmode 1920x1080_59.00 169.00 1920 2040 2240 2560 1080 1083 1088 1120 -hsync +vsync
3. Assign the new mode to the video output:
xrandr --addmode HDMI-1 1920x1080_59.00
4. Activate the new mode:
xrandr --output HDMI-1 --mode 1920x1080_59.00
If the above works and the problem disappear, you should find a proper way to add and set this mode at the system startup. Here are few references about that:
- How can I make
xrandrcustomization permanent? - Adding newmode with Xrandr - "800x480_60.00"
- start up command
- Differences how to run scripts at startup
add a comment |
I have screen flickering problem when I'm connecting my laptop to my TV. I found that when I change the refresh rate from 60Hz to 59Hz this problem disappear.
Within Xorg (as I know 18.04 uses it by default) you can change the refresh rate by the help of xrandr:
0. First you must find the video output name to which you should assing the new mode. Just type xrandr and investigate which one is it. In my case this is HDMI-1.
1. Generate new modeline using cvt:
$ cvt 1920 1080 59
# 1920x1080 58.94 Hz (CVT) hsync: 66.02 kHz; pclk: 169.00 MHz
Modeline "1920x1080_59.00" 169.00 1920 2040 2240 2560 1080 1083 1088 1120 -hsync +vsync
1920and1080are the horizontal and vertical resolution's values.
59is the value of the refresh rate.
2. Create the new mode:
xrandr --newmode 1920x1080_59.00 169.00 1920 2040 2240 2560 1080 1083 1088 1120 -hsync +vsync
3. Assign the new mode to the video output:
xrandr --addmode HDMI-1 1920x1080_59.00
4. Activate the new mode:
xrandr --output HDMI-1 --mode 1920x1080_59.00
If the above works and the problem disappear, you should find a proper way to add and set this mode at the system startup. Here are few references about that:
- How can I make
xrandrcustomization permanent? - Adding newmode with Xrandr - "800x480_60.00"
- start up command
- Differences how to run scripts at startup
add a comment |
I have screen flickering problem when I'm connecting my laptop to my TV. I found that when I change the refresh rate from 60Hz to 59Hz this problem disappear.
Within Xorg (as I know 18.04 uses it by default) you can change the refresh rate by the help of xrandr:
0. First you must find the video output name to which you should assing the new mode. Just type xrandr and investigate which one is it. In my case this is HDMI-1.
1. Generate new modeline using cvt:
$ cvt 1920 1080 59
# 1920x1080 58.94 Hz (CVT) hsync: 66.02 kHz; pclk: 169.00 MHz
Modeline "1920x1080_59.00" 169.00 1920 2040 2240 2560 1080 1083 1088 1120 -hsync +vsync
1920and1080are the horizontal and vertical resolution's values.
59is the value of the refresh rate.
2. Create the new mode:
xrandr --newmode 1920x1080_59.00 169.00 1920 2040 2240 2560 1080 1083 1088 1120 -hsync +vsync
3. Assign the new mode to the video output:
xrandr --addmode HDMI-1 1920x1080_59.00
4. Activate the new mode:
xrandr --output HDMI-1 --mode 1920x1080_59.00
If the above works and the problem disappear, you should find a proper way to add and set this mode at the system startup. Here are few references about that:
- How can I make
xrandrcustomization permanent? - Adding newmode with Xrandr - "800x480_60.00"
- start up command
- Differences how to run scripts at startup
I have screen flickering problem when I'm connecting my laptop to my TV. I found that when I change the refresh rate from 60Hz to 59Hz this problem disappear.
Within Xorg (as I know 18.04 uses it by default) you can change the refresh rate by the help of xrandr:
0. First you must find the video output name to which you should assing the new mode. Just type xrandr and investigate which one is it. In my case this is HDMI-1.
1. Generate new modeline using cvt:
$ cvt 1920 1080 59
# 1920x1080 58.94 Hz (CVT) hsync: 66.02 kHz; pclk: 169.00 MHz
Modeline "1920x1080_59.00" 169.00 1920 2040 2240 2560 1080 1083 1088 1120 -hsync +vsync
1920and1080are the horizontal and vertical resolution's values.
59is the value of the refresh rate.
2. Create the new mode:
xrandr --newmode 1920x1080_59.00 169.00 1920 2040 2240 2560 1080 1083 1088 1120 -hsync +vsync
3. Assign the new mode to the video output:
xrandr --addmode HDMI-1 1920x1080_59.00
4. Activate the new mode:
xrandr --output HDMI-1 --mode 1920x1080_59.00
If the above works and the problem disappear, you should find a proper way to add and set this mode at the system startup. Here are few references about that:
- How can I make
xrandrcustomization permanent? - Adding newmode with Xrandr - "800x480_60.00"
- start up command
- Differences how to run scripts at startup
edited Jun 3 '18 at 5:16
user3563396
31
31
answered May 3 '18 at 4:50
pa4080pa4080
14.5k52772
14.5k52772
add a comment |
add a comment |
I've no answer here, but some observation and confirmation of problem. If someone finds this text: please stick to ubuntu 17.10 if you have radeon rx 580 (may be 480 and vegas)
Got myself to very same situation with 18.04 (upgrade, then fresh install). Amd rx 580 here, kernel 4.15.0-20.
What did not help:
- fresh install after upgrade
oibaf drivers
M-Bab custom kernel
4.17-rc3 kernel from main line ppa.- amdgpu.dc=1 as boot parameter (/etc/default/grub)
Update:
Apparently older kernel works. I've been tinkering with other distibutions and found that kernel 4.15.14 works for rx 580, you may want to try it from mainline ppa.
Hi, try amdgpu.dc=0. It solves the problem.
– LaoPiSai
May 5 '18 at 1:57
Kernel4.15is no longer maintained by Linux Kernel developers. You can also try the4.14chain from the same mainline PPA. It is maintained for 5 or 6 years. I'm using4.14.34myself as4.14.36and4.14.37had symbolic link bugs which prevented installing.
– WinEunuuchs2Unix
May 12 '18 at 22:31
add a comment |
I've no answer here, but some observation and confirmation of problem. If someone finds this text: please stick to ubuntu 17.10 if you have radeon rx 580 (may be 480 and vegas)
Got myself to very same situation with 18.04 (upgrade, then fresh install). Amd rx 580 here, kernel 4.15.0-20.
What did not help:
- fresh install after upgrade
oibaf drivers
M-Bab custom kernel
4.17-rc3 kernel from main line ppa.- amdgpu.dc=1 as boot parameter (/etc/default/grub)
Update:
Apparently older kernel works. I've been tinkering with other distibutions and found that kernel 4.15.14 works for rx 580, you may want to try it from mainline ppa.
Hi, try amdgpu.dc=0. It solves the problem.
– LaoPiSai
May 5 '18 at 1:57
Kernel4.15is no longer maintained by Linux Kernel developers. You can also try the4.14chain from the same mainline PPA. It is maintained for 5 or 6 years. I'm using4.14.34myself as4.14.36and4.14.37had symbolic link bugs which prevented installing.
– WinEunuuchs2Unix
May 12 '18 at 22:31
add a comment |
I've no answer here, but some observation and confirmation of problem. If someone finds this text: please stick to ubuntu 17.10 if you have radeon rx 580 (may be 480 and vegas)
Got myself to very same situation with 18.04 (upgrade, then fresh install). Amd rx 580 here, kernel 4.15.0-20.
What did not help:
- fresh install after upgrade
oibaf drivers
M-Bab custom kernel
4.17-rc3 kernel from main line ppa.- amdgpu.dc=1 as boot parameter (/etc/default/grub)
Update:
Apparently older kernel works. I've been tinkering with other distibutions and found that kernel 4.15.14 works for rx 580, you may want to try it from mainline ppa.
I've no answer here, but some observation and confirmation of problem. If someone finds this text: please stick to ubuntu 17.10 if you have radeon rx 580 (may be 480 and vegas)
Got myself to very same situation with 18.04 (upgrade, then fresh install). Amd rx 580 here, kernel 4.15.0-20.
What did not help:
- fresh install after upgrade
oibaf drivers
M-Bab custom kernel
4.17-rc3 kernel from main line ppa.- amdgpu.dc=1 as boot parameter (/etc/default/grub)
Update:
Apparently older kernel works. I've been tinkering with other distibutions and found that kernel 4.15.14 works for rx 580, you may want to try it from mainline ppa.
edited May 1 '18 at 14:57
answered May 1 '18 at 7:29
LauriLauri
464
464
Hi, try amdgpu.dc=0. It solves the problem.
– LaoPiSai
May 5 '18 at 1:57
Kernel4.15is no longer maintained by Linux Kernel developers. You can also try the4.14chain from the same mainline PPA. It is maintained for 5 or 6 years. I'm using4.14.34myself as4.14.36and4.14.37had symbolic link bugs which prevented installing.
– WinEunuuchs2Unix
May 12 '18 at 22:31
add a comment |
Hi, try amdgpu.dc=0. It solves the problem.
– LaoPiSai
May 5 '18 at 1:57
Kernel4.15is no longer maintained by Linux Kernel developers. You can also try the4.14chain from the same mainline PPA. It is maintained for 5 or 6 years. I'm using4.14.34myself as4.14.36and4.14.37had symbolic link bugs which prevented installing.
– WinEunuuchs2Unix
May 12 '18 at 22:31
Hi, try amdgpu.dc=0. It solves the problem.
– LaoPiSai
May 5 '18 at 1:57
Hi, try amdgpu.dc=0. It solves the problem.
– LaoPiSai
May 5 '18 at 1:57
Kernel
4.15 is no longer maintained by Linux Kernel developers. You can also try the 4.14 chain from the same mainline PPA. It is maintained for 5 or 6 years. I'm using 4.14.34 myself as 4.14.36 and 4.14.37had symbolic link bugs which prevented installing.– WinEunuuchs2Unix
May 12 '18 at 22:31
Kernel
4.15 is no longer maintained by Linux Kernel developers. You can also try the 4.14 chain from the same mainline PPA. It is maintained for 5 or 6 years. I'm using 4.14.34 myself as 4.14.36 and 4.14.37had symbolic link bugs which prevented installing.– WinEunuuchs2Unix
May 12 '18 at 22:31
add a comment |
Turn off the automatic brightness control to fix this.
add a comment |
Turn off the automatic brightness control to fix this.
add a comment |
Turn off the automatic brightness control to fix this.
Turn off the automatic brightness control to fix this.
edited May 3 '18 at 3:46
fosslinux
2,39521837
2,39521837
answered May 3 '18 at 3:27
forwindieforwindie
1
1
add a comment |
add a comment |
I faced a similar problem,I wasn't able to log in with the graphical mode at all, I solved it by :
1- enter to tty mode (ctrl+alt+f5, en my case)
2- adding open grafic Drivers (https://launchpad.net/~oibaf/+archive/ubuntu/graphics-drivers):
sudo add-apt-repository ppa:oibaf/graphics-drivers
sudo apt-get update
3- reboot
4- enter into tty mode again
5-
sudo apt update && sudo apt full-upgrade
6- reboot and it works fine!!
hope it helps.
Thank you very much @Hassan for sharing the instructions. In my case I cannot get into the tty. Just to make sure, where do you ctrl+alt+f5? Does your computer have a fn key?
– Delosari
Jul 14 '18 at 23:01
add a comment |
I faced a similar problem,I wasn't able to log in with the graphical mode at all, I solved it by :
1- enter to tty mode (ctrl+alt+f5, en my case)
2- adding open grafic Drivers (https://launchpad.net/~oibaf/+archive/ubuntu/graphics-drivers):
sudo add-apt-repository ppa:oibaf/graphics-drivers
sudo apt-get update
3- reboot
4- enter into tty mode again
5-
sudo apt update && sudo apt full-upgrade
6- reboot and it works fine!!
hope it helps.
Thank you very much @Hassan for sharing the instructions. In my case I cannot get into the tty. Just to make sure, where do you ctrl+alt+f5? Does your computer have a fn key?
– Delosari
Jul 14 '18 at 23:01
add a comment |
I faced a similar problem,I wasn't able to log in with the graphical mode at all, I solved it by :
1- enter to tty mode (ctrl+alt+f5, en my case)
2- adding open grafic Drivers (https://launchpad.net/~oibaf/+archive/ubuntu/graphics-drivers):
sudo add-apt-repository ppa:oibaf/graphics-drivers
sudo apt-get update
3- reboot
4- enter into tty mode again
5-
sudo apt update && sudo apt full-upgrade
6- reboot and it works fine!!
hope it helps.
I faced a similar problem,I wasn't able to log in with the graphical mode at all, I solved it by :
1- enter to tty mode (ctrl+alt+f5, en my case)
2- adding open grafic Drivers (https://launchpad.net/~oibaf/+archive/ubuntu/graphics-drivers):
sudo add-apt-repository ppa:oibaf/graphics-drivers
sudo apt-get update
3- reboot
4- enter into tty mode again
5-
sudo apt update && sudo apt full-upgrade
6- reboot and it works fine!!
hope it helps.
edited May 12 '18 at 22:19
answered May 12 '18 at 22:11
HassanHassan
12
12
Thank you very much @Hassan for sharing the instructions. In my case I cannot get into the tty. Just to make sure, where do you ctrl+alt+f5? Does your computer have a fn key?
– Delosari
Jul 14 '18 at 23:01
add a comment |
Thank you very much @Hassan for sharing the instructions. In my case I cannot get into the tty. Just to make sure, where do you ctrl+alt+f5? Does your computer have a fn key?
– Delosari
Jul 14 '18 at 23:01
Thank you very much @Hassan for sharing the instructions. In my case I cannot get into the tty. Just to make sure, where do you ctrl+alt+f5? Does your computer have a fn key?
– Delosari
Jul 14 '18 at 23:01
Thank you very much @Hassan for sharing the instructions. In my case I cannot get into the tty. Just to make sure, where do you ctrl+alt+f5? Does your computer have a fn key?
– Delosari
Jul 14 '18 at 23:01
add a comment |
Just got 4.19-rc1 kernel installed and flickering is completly gone, no need to restart PC no other magic - it works out of the box.
I'm using Arch now, but believe ubuntu's mainline kernel going to provide same experience. http://kernel.ubuntu.com/~kernel-ppa/mainline/v4.19-rc1/
add a comment |
Just got 4.19-rc1 kernel installed and flickering is completly gone, no need to restart PC no other magic - it works out of the box.
I'm using Arch now, but believe ubuntu's mainline kernel going to provide same experience. http://kernel.ubuntu.com/~kernel-ppa/mainline/v4.19-rc1/
add a comment |
Just got 4.19-rc1 kernel installed and flickering is completly gone, no need to restart PC no other magic - it works out of the box.
I'm using Arch now, but believe ubuntu's mainline kernel going to provide same experience. http://kernel.ubuntu.com/~kernel-ppa/mainline/v4.19-rc1/
Just got 4.19-rc1 kernel installed and flickering is completly gone, no need to restart PC no other magic - it works out of the box.
I'm using Arch now, but believe ubuntu's mainline kernel going to provide same experience. http://kernel.ubuntu.com/~kernel-ppa/mainline/v4.19-rc1/
answered Aug 29 '18 at 7:10
LauriLauri
464
464
add a comment |
add a comment |
I had the same issue with my RX580 (Kubuntu 18.04, Plasma 5). The flickering only started when the GPU got higher load (playing the Witcher 3 in my case).
First I installed the 4.19 kernel (which has amdgpu.dc=1 by default).
That alone didn't seem to help but maybe contributes to the fix.
Than, I set the screen refresh rate to 59.xx hz with the KDE monitor settings GUI.
After this, the problem seems to be fixed.
In my case the flickering started when I manually switched screen resolution with xrandr (without an explicit refresh rate setting), so maybe the refresh rate was misconfigured by those commands and only the refresh rate needed to be fixed.
add a comment |
I had the same issue with my RX580 (Kubuntu 18.04, Plasma 5). The flickering only started when the GPU got higher load (playing the Witcher 3 in my case).
First I installed the 4.19 kernel (which has amdgpu.dc=1 by default).
That alone didn't seem to help but maybe contributes to the fix.
Than, I set the screen refresh rate to 59.xx hz with the KDE monitor settings GUI.
After this, the problem seems to be fixed.
In my case the flickering started when I manually switched screen resolution with xrandr (without an explicit refresh rate setting), so maybe the refresh rate was misconfigured by those commands and only the refresh rate needed to be fixed.
add a comment |
I had the same issue with my RX580 (Kubuntu 18.04, Plasma 5). The flickering only started when the GPU got higher load (playing the Witcher 3 in my case).
First I installed the 4.19 kernel (which has amdgpu.dc=1 by default).
That alone didn't seem to help but maybe contributes to the fix.
Than, I set the screen refresh rate to 59.xx hz with the KDE monitor settings GUI.
After this, the problem seems to be fixed.
In my case the flickering started when I manually switched screen resolution with xrandr (without an explicit refresh rate setting), so maybe the refresh rate was misconfigured by those commands and only the refresh rate needed to be fixed.
I had the same issue with my RX580 (Kubuntu 18.04, Plasma 5). The flickering only started when the GPU got higher load (playing the Witcher 3 in my case).
First I installed the 4.19 kernel (which has amdgpu.dc=1 by default).
That alone didn't seem to help but maybe contributes to the fix.
Than, I set the screen refresh rate to 59.xx hz with the KDE monitor settings GUI.
After this, the problem seems to be fixed.
In my case the flickering started when I manually switched screen resolution with xrandr (without an explicit refresh rate setting), so maybe the refresh rate was misconfigured by those commands and only the refresh rate needed to be fixed.
answered Oct 28 '18 at 19:44
solasola
363411
363411
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%2f1029517%2famd-rx480-screen-flicker-after-update-to-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
Join the ticket, the more people declare the problem, the faster the problem is solved bugs.launchpad.net/ubuntu/+source/xserver-xorg-video-amdgpu/…
– IvvanVG
Feb 1 at 14:15