Arch Linux

freaxtux

Member

Registered: 2012-07-17

Posts: 37

[SOLVED]How do I make the HDMI output to be full RGB mode on Wayland

Hello, I just found out the default display manager for GNOME is now Wayland
For two major reasons I can't just move to it, one being IME and another being finding no proper replacement for xrandr
I guess I have to face these now, but the former one is likely to be long way round till they properly work, and what I can't do on my own

So I'm trying to figure out what is easier to solve first.
Since the intel kernel driver treats HDMI output to be "limited color range", black to seem to be gray. kernel.org bugzilla(they marked this WONTFIX)
It could be easily fixed with xrandr but I couldn't find a trick to achieve this on Wayland. google search

Do anyone have solution for this?
Thanks in advance.

Last edited by freaxtux (2016-10-19 03:09:23)

freaxtux

Member

Registered: 2012-07-17

Posts: 37

Re: [SOLVED]How do I make the HDMI output to be full RGB mode on Wayland

Bump

R00KIE

Forum Fellow

From: Between a computer and a chair

Registered: 2008-09-14

Posts: 4,734

Re: [SOLVED]How do I make the HDMI output to be full RGB mode on Wayland

Don't bump your thread https://wiki.archlinux.org/index.php/Co … ct#Bumping

People coming here live in many different time zones so be patient until people have the chance to come here and give you a reply.

Meanwhile you should do research and try to solve the problem yourself. That said, I'm not familiar with gnome but I suppose you should be able to configure it to use X instead of wayland.

---

R00KIE
Tm90aGluZyB0byBzZWUgaGVyZSwgbW92ZSBhbG9uZy4K

freaxtux

Member

Registered: 2012-07-17

Posts: 37

Re: [SOLVED]How do I make the HDMI output to be full RGB mode on Wayland

Oops, it just works now. It seems that I didn't test enough. I remembered having some frustration with xrandr + Wayland earlier and assumed that this was it. it must have been different thing

I plugged the monitor while on Wayland, and it wasn't displaying properly as described above.

It might have been bad connection while initializing (the cable is a bit faulty) or sudden transition to Wayland

Simply logging into Xorg session and then back to Wayland solved it.

Sorry for worthless question.

P. S. Sorry for bumping too. I didn't know there were such a rule

(edit : scraped my stupid rambling   )

Last edited by freaxtux (2016-10-19 03:09:06)