Raspberry Pi HDMI output looks dull, low contrast

Bug #1896186 reported by Daniel van Vugt
6
This bug affects 1 person
Affects Status Importance Assigned to Milestone
linux-firmware-raspi2 (Ubuntu)
Fix Released
Low
Unassigned

Bug Description

HDMI colour looks dull, low contrast on Raspberry Pi.

Workaround/fix: Edit /boot/firmware/usercfg.txt and add a new line:

  hdmi_pixel_encoding=2

summary: - HDMI colour looks dull, low contrast on Raspberry Pi
+ Raspberry Pi HDMI output looks dull, low contrast
tags: added: hirsute
Changed in linux-firmware-raspi2 (Ubuntu):
importance: Undecided → Low
status: New → Triaged
tags: added: rls-hh-incoming
tags: removed: hirsute
Revision history for this message
Daniel van Vugt (vanvugt) wrote :

Still affects hirsute.

tags: added: hirsute
tags: added: rls-hh-notfixing
removed: rls-hh-incoming
Revision history for this message
Dave Jones (waveform) wrote :

From the Pi's config.txt docs at https://www.raspberrypi.org/documentation/configuration/config-txt/video.md :

  "The hdmi_pixel_encoding command forces the pixel encoding mode. By default, it will use the mode requested from the EDID, so you shouldn't need to change it."

Which would suggest that if the wrong encoding is being selected for your monitor, then it's because your monitor is transmitting the wrong information in its EDID. However, the table below that states that the default is "RGB limited for CEA, RGB full for DMT" which suggests (to me at least) that the heuristic is rather simpler and that any CEA (TV) mode gets the limited 16-235 range (which is typical for TVs), while any DMT (monitor) mode gets the full 0-255 range.

It might be useful to query what EDID the Pi is getting from your monitor. I don't *think* this works when the KMS overlay is loaded, but if you boot the server image, install "libraspberrypi-bin" on it, then run "tvservice -d edid.dat" that should dump the EDID the pi's firmware received from your monitor. If you could attach that we could take a look at what might be going on?

Revision history for this message
Daniel van Vugt (vanvugt) wrote :

This doesn't seem to be a problem anymore but I suspect I was using a different model monitor when I logged this.

Changed in linux-firmware-raspi2 (Ubuntu):
status: Triaged → Fix Released
To post a comment you must log in.
This report contains Public information  
Everyone can see this information.

Other bug subscribers

Remote bug watches

Bug watches keep track of this bug in other bug trackers.