HDMI Default Resolution changed in kernel update, commit ef24397487cfe33ad76070ec55686b4ed2606bfd

[benosteen]

"Default to DVI for DMT modes. Override with hdmi_drive=2. Add perforce version numbering. Avoid unwanted HDMI clock range check" --> commit ef24397

Using HDMI to an Optima HD600X projector, a mode of "1080i" was chosen by the Pi for display for kernels before this commit.

After the commit, it is using a 720p mode (mode 19 in the list below)

$  /opt/vc/bin/tvservice -m DMT
Group DMT has 17 modes:
           mode 4: 640x480 @ 60Hz, progressive
           mode 5: 640x480 @ 72Hz, progressive
           mode 6: 640x480 @ 75Hz, progressive
           mode 8: 800x600 @ 56Hz, progressive
           mode 9: 800x600 @ 60Hz, progressive
           mode 10: 800x600 @ 72Hz, progressive
           mode 11: 800x600 @ 75Hz, progressive
           mode 13: 800x600 @ 120Hz, progressive
           mode 16: 1024x768 @ 60Hz, progressive
           mode 17: 1024x768 @ 70Hz, progressive
           mode 18: 1024x768 @ 75Hz, progressive
           mode 20: 1024x768 @ 120Hz, progressive
           mode 28: 1280x800 @ 60Hz, progressive
           mode 35: 1280x1024 @ 60Hz, progressive
           mode 36: 1280x1024 @ 75Hz, progressive
           mode 58: 1680x1050 @ 60Hz, progressive
           mode 85: 1280x720 @ 60Hz, progressive
pi@raspberrypi:/opt/vc/src/hello_pi/hello_audio$  /opt/vc/bin/tvservice -m CEA
Group CEA has 16 modes:
           mode 1: 640x480 @ 60Hz, progressive
           mode 2: 720x480 @ 60Hz, progressive
           mode 3: 720x480 @ 60Hz, progressive
           mode 4: 1280x720 @ 60Hz, progressive
           mode 5: 1920x1080 @ 60Hz, interlaced
           mode 7: 720x480 @ 60Hz, interlaced
           mode 16: 1920x1080 @ 60Hz, progressive
           mode 17: 720x576 @ 50Hz, progressive
           mode 18: 720x576 @ 50Hz, progressive
  (native) mode 19: 1280x720 @ 50Hz, progressive
           mode 20: 1920x1080 @ 50Hz, interlaced
           mode 22: 720x576 @ 50Hz, interlaced
           mode 31: 1920x1080 @ 50Hz, progressive
           mode 32: 1920x1080 @ 24Hz, progressive
           mode 33: 1920x1080 @ 25Hz, progressive
           mode 34: 1920x1080 @ 30Hz, progressive
pi@raspberrypi:/opt/vc/src/hello_pi/hello_audio$ /opt/vc/bin/tvservice -s
state 0x12001a, 1280x720 @ 50Hz, progressive

This is probably intended behaviour, if the [native] tag is coming from the projector's EDID (can't check, as tvservice on img doesn't understand '-d')

[popcornmix]

My guess is that 720p50 is the preferred resolution of display, so the new behaviour is correct.
Can you use this:
https://github.com/raspberrypi/firmware/raw/master/opt/vc/bin/tvservice
and dump the edid so we can confirm.

[benosteen]

http://dl.dropbox.com/u/49868798/OPTIMAHD600X_Projector.edid EDID file

(For anyone following along, tvservice requires sudo to use the -d option)

[popcornmix]

Your TV does indicate 1080i is preferred, so we should probably do that (although it is debatable).
I expect this will change back to 1080i in next firmware update.

[github-newb]

Actually the preferred mode is some sort of 1280x720 which does not correspond to a known 720p format. The second detailed timing block is 720p50.

[raspberrypi]

Just for reference, the problem was that we'd accidentally introduced
a 160MHz dot clock limit. 1600x1200x60 needs 161MHz.

Eben

On Wed, Apr 18, 2012 at 1:27 AM, Ben O'Steen
[email protected]
wrote:

"Default to DVI for DMT modes. Override with hdmi_drive=2. Add perforce version numbering. Avoid unwanted HDMI clock range check" --> commit ef24397

Using HDMI to an Optima HD600X projector, a mode of "1080i" was chosen by the Pi for display for kernels before this commit.

After the commit, it is using a 720p mode (mode 19 in the list below)

$  /opt/vc/bin/tvservice -m DMT
Group DMT has 17 modes:
          mode 4: 640x480 @ 60Hz, progressive
          mode 5: 640x480 @ 72Hz, progressive
          mode 6: 640x480 @ 75Hz, progressive
          mode 8: 800x600 @ 56Hz, progressive
          mode 9: 800x600 @ 60Hz, progressive
          mode 10: 800x600 @ 72Hz, progressive
          mode 11: 800x600 @ 75Hz, progressive
          mode 13: 800x600 @ 120Hz, progressive
          mode 16: 1024x768 @ 60Hz, progressive
          mode 17: 1024x768 @ 70Hz, progressive
          mode 18: 1024x768 @ 75Hz, progressive
          mode 20: 1024x768 @ 120Hz, progressive
          mode 28: 1280x800 @ 60Hz, progressive
          mode 35: 1280x1024 @ 60Hz, progressive
          mode 36: 1280x1024 @ 75Hz, progressive
          mode 58: 1680x1050 @ 60Hz, progressive
          mode 85: 1280x720 @ 60Hz, progressive
pi@raspberrypi:/opt/vc/src/hello_pi/hello_audio$  /opt/vc/bin/tvservice -m CEA
Group CEA has 16 modes:
          mode 1: 640x480 @ 60Hz, progressive
          mode 2: 720x480 @ 60Hz, progressive
          mode 3: 720x480 @ 60Hz, progressive
          mode 4: 1280x720 @ 60Hz, progressive
          mode 5: 1920x1080 @ 60Hz, interlaced
          mode 7: 720x480 @ 60Hz, interlaced
          mode 16: 1920x1080 @ 60Hz, progressive
          mode 17: 720x576 @ 50Hz, progressive
          mode 18: 720x576 @ 50Hz, progressive
 (native) mode 19: 1280x720 @ 50Hz, progressive
          mode 20: 1920x1080 @ 50Hz, interlaced
          mode 22: 720x576 @ 50Hz, interlaced
          mode 31: 1920x1080 @ 50Hz, progressive
          mode 32: 1920x1080 @ 24Hz, progressive
          mode 33: 1920x1080 @ 25Hz, progressive
          mode 34: 1920x1080 @ 30Hz, progressive
pi@raspberrypi:/opt/vc/src/hello_pi/hello_audio$ /opt/vc/bin/tvservice -s
state 0x12001a, 1280x720 @ 50Hz, progressive

---

Reply to this email directly or view it on GitHub:
#4

[rick2k]

I can no longer output at 1680x1050(native res) to my monitor. It used to be fine with the previous Debian image I used.

I have black borders around the image.
xranr reports my max resolution as 1584x954 and that's all that I can output on the Pi. Strangely my monitor reports it as a 1680x1050 input though (I guess this is where the borders come from)

What's going on here?

I tried a variety of difference config.txt settings and have the latest start.elf and kernel (as of 5pm today), I can only seem to run at 640x480 or this odd 1584 setting.

[popcornmix]

disable_overscan=1

[rick2k]

Solved!

Thanks.

[popcornmix]

Closing as I believe the resolution being chosen is correct based on the information supplied in EDID.