-
Notifications
You must be signed in to change notification settings - Fork 16
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Invert Breaking with 4.17+ Kernel & AMDGPU #20
Comments
Can you try xcalib for comparison?
…On Wed, Oct 31, 2018, 04:00 df0ecc ***@***.*** wrote:
Hi! xrandr-invert-colors is behaving unusually with a Radeon GPU & kernel
versions 4.17 and beyond. I have double checked that I am still using X11
and do not have redshift installed. When I run the command the screen
becomes very bright, mostly white. I have tested it with Intel integrated
graphics with the latest kernel available to me (4.19.0-3-MANJARO x86_64)
on my laptop and it still worked perfectly fine. Thank you.
—
You are receiving this because you are subscribed to this thread.
Reply to this email directly, view it on GitHub
<#20>, or mute the
thread
<https://github.com/notifications/unsubscribe-auth/AAG-ZARRVvK7VNb873fN22eqItwew4Czks5uqRJmgaJpZM4YDQY2>
.
|
Yes. 'xcalib -i -a' is producing the same kind of oversaturated desktop.
|
Then it sounds like an upstream issue for me. I guess a bug should be filed
somewhere.
koo5: thanks for the quick reply :-)
note to self:Ubutunu 18.10 has linux kernel 4.18, to try to reproduce this
issue on it on Radeon GPU
|
Perhaps this could shed more light on it... Blank screen since Kernel 4.17 (AMDGPU.DC) on Amd Radeon RX460 and RX380 on Ultrawidescreen Monitor I tried the suggested workaround (adding "amdgpu.dc=0" to the grub kernel command line) and invert functionality was restored. Also, for sake of troubleshooting, here is my GPU info: Specifically I am using the RX 550. |
I am having the exact same issue with an a RX 580 as well, while it still works on my laptop using the Intel chipset. |
From everything I've gathered, this particular series of cards has been fairly problematic, but as kernel 5 progresses things are improving. If you use Firefox I recommend the 'Invert Colors' add-on. Good resource: https://www.phoronix.com/forums/forum/linux-graphics-x-org-drivers/open-source-amd-linux |
Thank you for the follow-up. Unfortunately I am not using Firefox, but anyway I would like to have
the color inversion feature beyond just the web browser.
Something like the [Invert-window-colors](https://extensions.gnome.org/extension/1041/invert-window-color/) gnome extension is great because it allows inverting just individual windows (which is great when windows do not all have the same brightness/color), but I am not using gnome. `xrandr-invert-colors` was therefore by far the best solution for me. We'll see if kernel updates improve the situation.
|
I'm experiencing the same issues. Adding the boot parameter didn't help on my machine. Edit: In the meantime, i somewhat isolated the issue. xcalib's contrast values after "-i -a" are messed up, c.f. OpenICC/xcalib#9 (comment) |
Same here on an RX 550 on Ubuntu 18.04 LTS. Both "xcalib -i -a" and "xrandr-invert-colors" give the same behaviour: the screen goes all white washed out, can't see diddly. I have not yet tried the potential grub kernel workaround. giant dump of logs
|
sorry to hear that guys, your best bet is probably to file a bug against your xorg package. At least, someone there should know where to take it further. |
Indeed, some upstream bug reports should help. Eventually cross-link this issue with the other bug reports. |
Hi! xrandr-invert-colors is behaving unusually with a Radeon GPU & kernel versions 4.17 and beyond. I have double checked that I am still using X11 and do not have redshift installed. When I run the command the screen becomes very bright, mostly white. I have tested it with Intel integrated graphics with the latest kernel available to me (4.19.0-3-MANJARO x86_64) on my laptop and it still worked perfectly fine. Thank you.
The text was updated successfully, but these errors were encountered: