Hm. Still no bulk moves. What is blocking it?
Announcement
Collapse
No announcement yet.
AMDGPU Has Another Round Of Updates Ahead Of Linux 5.2
Collapse
X
-
Originally posted by jrdoane View Post
I had a 390 and the displays would flicker due to clock changes. In particular, the lowest power state would cause it because I think that would also cause the memory clock to drop as well and for multiple monitors, you really need the clocks to stay a little higher than the lowest level. On my 390, the solution was to add the kernel flag amdgpu.dpm=1 which uses the newer powerplay code instead of the older code which would not only flicker, but would crash my machine. Before that, I would force clocks to high performance which hurts heat and power consumption, but worked.
With that said, I got a Vega 64 and it's a completely different story. I've had zero issues with the Vega card while driving a 4k and two 1080p displays. I haven't seen so much as a flicker with the newer GPU. I also don't tend to use Wayland either, but I don't get flickering with it, just some 3d applications don't like to run. All in all, Vega support is far better than support for Hawaii.
Comment
-
Originally posted by clapbr View Post<rant>
Every bug I´ve had reported by me and others requires constant begging to get any fix, meanwhile we constantly see a lot of work on the driver which means those issues that should be blockers have no priority at all for the dev team. It´s not an edge case by any means, just search the words "AMD flickering" on linux subreddits and there are literally dozens of reports about it every month. I see people with APU's complaining a lot also, and Vega.
- Likes 5
Comment
-
Originally posted by Space Heater View PostThey almost certainly have it in fairly decent shape, but they can't post it publicly until they get the green light from higher up.
Also on the Vulkan side I guess RadV will lag behind amdvlk initially since the RadV developers at RedHat/Valve don't have access to early silicon.
Comment
-
I had great response from AMD on all my previous Carrizo issues so I just assumed it would be even better on my Vega 56 in the Acer predator Helios 500. I guess we will see....
Bug #1813820 “Waking from Suspend causes screen to appear with g...” : Bugs : linux package : UbuntuI am running Kubuntu 18.10. This is the PH517-61 Acer Predator Helios 500 with the Ryzen processor. My first issue I need to deal with is Suspend. I have temporarily disabled suspend in the kcmshell5 configuration. If I do let the laptop suspend and then hit the keyboard I get what appears to be a 1950s TV with no signal. At this point I manually power down and then power up again and am able to view things on screen. Running these commands I get this information: $ journalctl -b -g suspend ...
Comment
Comment