PjV
Posts: 13
Joined: Tue Dec 13, 2016 5:39 pm

Re: Setting up HDMI output when video output isn't what you

Fri Jan 20, 2017 9:53 am

dom wrote:You want:

Code: Select all

max_framebuffer_width=2560
max_framebuffer_height=1080
Thanks, I have been overlooking that typo for hours and hours :oops:

It seems that there is a limit of 2400 pixels somewhere.
These are the current contents of config.txt:

Code: Select all

hdmi_cvt=2560 1080 50 7 0 0 0 
hdmi_group=2
hdmi_mode=87
hdmi_pixel_freq_limit=300000000
hdmi_drive=2

max_framebuffer_width=2560
framebuffer_width=2400

dtparam=audio=on
If I set a value for framebuffer_width of over 2400, not everything gets shown.
Right hand side, everything to the right of the 2400th pixel isn't visible.

Playing with the overscan_left and overscan_right has only effect on the position of the image, it is always the same area that gets cut off.
If a value for framebuffer_width and values for both overscan_left and overscan_right are provided, the overscan values have to cancel eachother out (i.e. their sum equals 0). Otherwise they are (seem to be?) ignored.
Perhaps there is an error in the processing of these framebuffer and overscan values, or it is just unclear to me how to configure them.

Anyway, thanks again; 2400x1080 is a lot better then 1920x1080 :)

bitnix
Posts: 8
Joined: Thu Jan 26, 2017 4:07 pm

Re: Setting up HDMI output when video output isn't what you

Thu Jan 26, 2017 4:36 pm

I have an Insignia NS-19D220NA16-A HDTV (720p@1360x768 60HZ) hooked up to my Pi over HDMI. I wanted to get audio over HDMI so I set hdmi_drive to 2 and rebooted. Upon reboot, the resolution seems to become less defined and the colors become faded.

Here is the parser output

Code: Select all

Enabling fuzzy format match...
Parsing edid...
HDMI:EDID version 1.3, 1 extensions, screen size 41x23 cm
HDMI:EDID features - videodef 0x80 !standby !suspend !active off; colour encoding:RGB444|YCbCr422; sRGB is not default colourspace; preferred format is native; does not support GTF
HDMI:EDID found monitor name descriptor tag 0xfc
HDMI:EDID monitor name is NS19D220NA16A�
HDMI:EDID found monitor range descriptor tag 0xfd
HDMI:EDID monitor range offsets: V min=0, V max=0, H min=0, H max=0
HDMI:EDID monitor range: vertical is 55-76 Hz, horizontal is 30-80 kHz, max pixel clock is 170 MHz
HDMI:EDID monitor range does not support GTF
HDMI:EDID found preferred DMT detail timing format: 1360x768p @ 60 Hz (39)
HDMI:EDID failed to find a matching detail format for 1280x768p hfp:80 hs:128 hbp:212 vfp:3 vs:7 vbp:32 pixel clock:82 MHz
HDMI:EDID calculated refresh rate is 60 Hz
HDMI:EDID guessing the format to be 1280x768p @60 Hz
HDMI:EDID found DMT detail timing format: 1280x768p @ 60 Hz (22)
HDMI:EDID established timing I/II bytes are A3 08 00
HDMI:EDID found DMT format: code 4, 640x480p @ 60 Hz in established timing I/II
HDMI:EDID found DMT format: code 8, 800x600p @ 56 Hz in established timing I/II
HDMI:EDID found DMT format: code 9, 800x600p @ 60 Hz in established timing I/II
HDMI:EDID found DMT format: code 16, 1024x768p @ 60 Hz in established timing I/II
HDMI:EDID standard timings block x 8: 0x81C0 8100 810F 8140 8180 9500 B300 0101 
HDMI:EDID found DMT format: code 85, 1280x720p @ 60 Hz (16:9) in standard timing 0
HDMI:EDID found DMT format: code 28, 1280x800p @ 60 Hz (16:10) in standard timing 1
HDMI:EDID found DMT format: code 29, 1280x800p @ 75 Hz (16:10) in standard timing 2
HDMI:EDID found DMT format: code 32, 1280x960p @ 60 Hz (4:3) in standard timing 3
HDMI:EDID found DMT format: code 35, 1280x1024p @ 60 Hz (5:4) in standard timing 4
HDMI:EDID found DMT format: code 47, 1440x900p @ 60 Hz (16:10) in standard timing 5
HDMI:EDID found DMT format: code 58, 1680x1050p @ 60 Hz (16:10) in standard timing 6
HDMI:EDID parsing v3 CEA extension 0
HDMI:EDID monitor support - underscan IT formats:no, basic audio:yes, yuv444:yes, yuv422:yes, #native DTD:3
HDMI:EDID found CEA detail timing format: 1280x720p @ 60 Hz (4)
HDMI:EDID found CEA detail timing format: 720x480p @ 60 Hz (2)
HDMI:EDID found CEA detail timing format: 1920x1080i @ 60 Hz (5)
HDMI:EDID found CEA format: code 1, 640x480p @ 60Hz 
HDMI:EDID found CEA format: code 2, 720x480p @ 60Hz 
HDMI:EDID found CEA format: code 3, 720x480p @ 60Hz 
HDMI:EDID found CEA format: code 4, 1280x720p @ 60Hz (native)
HDMI:EDID found CEA format: code 5, 1920x1080i @ 60Hz 
HDMI:EDID found CEA format: code 6, 1440x480i @ 60Hz 
HDMI:EDID found CEA format: code 7, 1440x480i @ 60Hz 
HDMI:EDID found CEA format: code 16, 1920x1080p @ 60Hz 
HDMI:EDID found CEA format: code 32, 1920x1080p @ 24Hz 
HDMI:EDID found audio format 2 channels PCM, sample rate: 32|44|48 kHz, sample size: 16|20|24 bits
HDMI:EDID found audio format 6 channels AC3, sample rate: 32|44|48 kHz, bitrate: 640 kbps
HDMI:EDID found HDMI VSDB length 5
HDMI:EDID HDMI VSDB has physical address 1.0.0.0
HDMI:EDID HDMI VSDB has no extension fields
HDMI:EDID filtering formats with pixel clock > 162 MHz or h. blanking > 1023
HDMI:EDID best score mode initialised to DMT (4) 640x480p @ 60 Hz with pixel clock 25 MHz (score 0)
HDMI:EDID best score mode is now CEA (1) 640x480p @ 60 Hz with pixel clock 25 MHz (score 43432)
HDMI:EDID best score mode is now CEA (2) 720x480p @ 60 Hz with pixel clock 27 MHz (score 3545736)
HDMI:EDID CEA mode (3) 720x480p @ 60 Hz with pixel clock 27 MHz has a score of 45736
HDMI:EDID best score mode is now CEA (4) 1280x720p @ 60 Hz with pixel clock 74 MHz (score 4107944)
HDMI:EDID DMT mode (4) 640x480p @ 60 Hz with pixel clock 25 MHz has a score of 36864
HDMI:EDID CEA mode (5) 1920x1080i @ 60 Hz with pixel clock 74 MHz has a score of 3149416
HDMI:EDID CEA mode (6) 1440x480i @ 60 Hz with pixel clock 27 MHz has a score of 35368
HDMI:EDID CEA mode (7) 1440x480i @ 60 Hz with pixel clock 27 MHz has a score of 35368
HDMI:EDID DMT mode (8) 800x600p @ 56 Hz with pixel clock 36 MHz has a score of 53760
HDMI:EDID DMT mode (9) 800x600p @ 60 Hz with pixel clock 40 MHz has a score of 57600
HDMI:EDID CEA mode (16) 1920x1080p @ 60 Hz with pixel clock 148 MHz has a score of 149416
HDMI:EDID DMT mode (16) 1024x768p @ 60 Hz with pixel clock 65 MHz has a score of 94370
HDMI:EDID best score mode is now DMT (22) 1280x768p @ 60 Hz with pixel clock 68 MHz (score 4617964)
HDMI:EDID DMT mode (28) 1280x800p @ 60 Hz with pixel clock 83 MHz has a score of 147880
HDMI:EDID DMT mode (29) 1280x800p @ 75 Hz with pixel clock 106 MHz has a score of 178600
HDMI:EDID CEA mode (32) 1920x1080p @ 24 Hz with pixel clock 74 MHz has a score of 74766
HDMI:EDID DMT mode (32) 1280x960p @ 60 Hz with pixel clock 108 MHz has a score of 172456
HDMI:EDID DMT mode (35) 1280x1024p @ 60 Hz with pixel clock 108 MHz has a score of 182286
HDMI:EDID best score mode is now DMT (39) 1360x768p @ 60 Hz with pixel clock 85 MHz (score 5188004)
HDMI:EDID DMT mode (47) 1440x900p @ 60 Hz with pixel clock 106 MHz has a score of 180520
HDMI:EDID DMT mode (58) 1680x1050p @ 60 Hz with pixel clock 146 MHz has a score of 236680
HDMI:EDID DMT mode (85) 1280x720p @ 60 Hz with pixel clock 74 MHz has a score of 135592
HDMI:EDID preferred mode remained as DMT (39) 1360x768p @ 60 Hz with pixel clock 85 MHz
HDMI:EDID has HDMI support and audio support
edid_parser exited with code 0
I've also attached my EDID file.

Any help is greatly appreciated. Thank you.
Attachments
edidfile.bz2
(288 Bytes) Downloaded 105 times

PjV
Posts: 13
Joined: Tue Dec 13, 2016 5:39 pm

Re: Setting up HDMI output when video output isn't what you

Fri Jan 27, 2017 5:51 am

bitnix wrote:I have an Insignia NS-19D220NA16-A HDTV (720p@1360x768 60HZ) hooked up to my Pi over HDMI. I wanted to get audio over HDMI so I set hdmi_drive to 2 and rebooted. Upon reboot, the resolution seems to become less defined and the colors become faded.

Here is the parser output

Code: Select all

HDMI:EDID best score mode is now DMT (39) 1360x768p @ 60 Hz with pixel clock 85 MHz (score 5188004)
HDMI:EDID preferred mode remained as DMT (39) 1360x768p @ 60 Hz with pixel clock 85 MHz
HDMI:EDID has HDMI support and audio support
edid_parser exited with code 0
I've also attached my EDID file.

Any help is greatly appreciated. Thank you.
Hi, which mode was selected before you set the hdmi_drive value to 2?
Is the screen completely filled or does your tv do overscan / underscan?

bitnix
Posts: 8
Joined: Thu Jan 26, 2017 4:07 pm

Re: Setting up HDMI output when video output isn't what you

Fri Jan 27, 2017 3:16 pm

PjV wrote:
bitnix wrote:I have an Insignia NS-19D220NA16-A HDTV (720p@1360x768 60HZ) hooked up to my Pi over HDMI. I wanted to get audio over HDMI so I set hdmi_drive to 2 and rebooted. Upon reboot, the resolution seems to become less defined and the colors become faded.

Here is the parser output

Code: Select all

HDMI:EDID best score mode is now DMT (39) 1360x768p @ 60 Hz with pixel clock 85 MHz (score 5188004)
HDMI:EDID preferred mode remained as DMT (39) 1360x768p @ 60 Hz with pixel clock 85 MHz
HDMI:EDID has HDMI support and audio support
edid_parser exited with code 0
I've also attached my EDID file.

Any help is greatly appreciated. Thank you.
Hi, which mode was selected before you set the hdmi_drive value to 2?
Is the screen completely filled or does your tv do overscan / underscan?
The mode selected was DVI DMT (39) 1360x768. The screen is completely filled and I have overscan off on the Pi and TV.

dom
Raspberry Pi Engineer & Forum Moderator
Raspberry Pi Engineer & Forum Moderator
Posts: 5106
Joined: Wed Aug 17, 2011 7:41 pm
Location: Cambridge

Re: Setting up HDMI output when video output isn't what you

Fri Jan 27, 2017 4:05 pm

bitnix wrote:I have an Insignia NS-19D220NA16-A HDTV (720p@1360x768 60HZ) hooked up to my Pi over HDMI. I wanted to get audio over HDMI so I set hdmi_drive to 2 and rebooted. Upon reboot, the resolution seems to become less defined and the colors become faded.
We default to full range RGB with DMT modes. Here is status with hdmi_drive=1

Code: Select all

$ tvservice  -s
state 0x120006 [DVI DMT (39) RGB full 16:9], 1360x768 @ 60.00Hz, progressive
And with hdmi_drive=2

Code: Select all

state 0x12000a [HDMI DMT (39) RGB full 16:9], 1360x768 @ 60.00Hz, progressive
Both are using full range RGB. Now it may be the monitor is not decoding the signalling that shows if signal is limited or full range and assumes limited for HDMI drive.
Can you try forcing limited range (add "hdmi_pixel_encoding=1" to config.txt) which should give:

Code: Select all

state 0x12000a [HDMI DMT (39) RGB lim 16:9], 1360x768 @ 60.00Hz, progressive

bitnix
Posts: 8
Joined: Thu Jan 26, 2017 4:07 pm

Re: Setting up HDMI output when video output isn't what you

Fri Jan 27, 2017 4:43 pm

dom wrote:
bitnix wrote:I have an Insignia NS-19D220NA16-A HDTV (720p@1360x768 60HZ) hooked up to my Pi over HDMI. I wanted to get audio over HDMI so I set hdmi_drive to 2 and rebooted. Upon reboot, the resolution seems to become less defined and the colors become faded.
We default to full range RGB with DMT modes. Here is status with hdmi_drive=1

Code: Select all

$ tvservice  -s
state 0x120006 [DVI DMT (39) RGB full 16:9], 1360x768 @ 60.00Hz, progressive
And with hdmi_drive=2

Code: Select all

state 0x12000a [HDMI DMT (39) RGB full 16:9], 1360x768 @ 60.00Hz, progressive
Both are using full range RGB. Now it may be the monitor is not decoding the signalling that shows if signal is limited or full range and assumes limited for HDMI drive.
Can you try forcing limited range (add "hdmi_pixel_encoding=1" to config.txt) which should give:

Code: Select all

state 0x12000a [HDMI DMT (39) RGB lim 16:9], 1360x768 @ 60.00Hz, progressive
I set pixel encoding to 1 and the problem persists. I took pictures of the problem I'm having.

http://imgur.com/a/We49t

The first picture is hdmi_drive set to 1. Notice the color of the text and the definition of the wallpaper; the text is not faded and the wallpaper is normal. Now, the second picture is hdmi_drive set to 2. The text is faded in color and the wallpaper is sharper but less defined.

*Here's a better example to show off the wallpaper sharpening: http://imgur.com/a/U9JRJ

dom
Raspberry Pi Engineer & Forum Moderator
Raspberry Pi Engineer & Forum Moderator
Posts: 5106
Joined: Wed Aug 17, 2011 7:41 pm
Location: Cambridge

Re: Setting up HDMI output when video output isn't what you

Fri Jan 27, 2017 5:05 pm

PjV wrote:Anyway, thanks again; 2400x1080 is a lot better then 1920x1080 :)
I've had a look as I wasn't aware of where the 2400 came from.
Turns out default max_framebuffer is 1920x1200 (if you don't override in config.txt).
There is a limit of virtual framebuffer size of double the physical size. But for some reason the width/heights were swapped - possibly a typo when adding rotated framebuffer support.
The virtual framebuffer is a linux feature allowing scrolling or page flipping by swapping halves of the virtual framebuffer.

Removing the swap of width/height in the virtual framebuffer size check does remove the 2400 limit and I can display the whole of 2560x1080.
This fix will be in next rpi-update firmware (and later in apt-get firmware).

dom
Raspberry Pi Engineer & Forum Moderator
Raspberry Pi Engineer & Forum Moderator
Posts: 5106
Joined: Wed Aug 17, 2011 7:41 pm
Location: Cambridge

Re: Setting up HDMI output when video output isn't what you

Sat Jan 28, 2017 12:47 pm

dom wrote:This fix will be in next rpi-update firmware (and later in apt-get firmware).
Latest rpi-update firmware should fix this.

PjV
Posts: 13
Joined: Tue Dec 13, 2016 5:39 pm

Re: Setting up HDMI output when video output isn't what you

Sat Jan 28, 2017 12:55 pm

bitnix wrote:The first picture is hdmi_drive set to 1. Notice the color of the text and the definition of the wallpaper; the text is not faded and the wallpaper is normal. Now, the second picture is hdmi_drive set to 2. The text is faded in color and the wallpaper is sharper but less defined.
Seeing the images, it looks like a cable issue to me, what clock speed is reported by tvservice -m DMT in both situations?

PjV
Posts: 13
Joined: Tue Dec 13, 2016 5:39 pm

Re: Setting up HDMI output when video output isn't what you

Sat Jan 28, 2017 12:57 pm

dom wrote:
dom wrote:This fix will be in next rpi-update firmware (and later in apt-get firmware).
Latest rpi-update firmware should fix this.
That is great news, thanks!

bitnix
Posts: 8
Joined: Thu Jan 26, 2017 4:07 pm

Re: Setting up HDMI output when video output isn't what you

Sat Jan 28, 2017 6:24 pm

PjV wrote:
bitnix wrote:The first picture is hdmi_drive set to 1. Notice the color of the text and the definition of the wallpaper; the text is not faded and the wallpaper is normal. Now, the second picture is hdmi_drive set to 2. The text is faded in color and the wallpaper is sharper but less defined.
Seeing the images, it looks like a cable issue to me, what clock speed is reported by tvservice -m DMT in both situations?
The clock speed is 85Mhz for both drive 1 and 2. I also tried out a spare HDMI cable and that did not fix the problem. I am feeling that the Pi does not like the TV.

PjV
Posts: 13
Joined: Tue Dec 13, 2016 5:39 pm

Re: Setting up HDMI output when video output isn't what you

Wed Feb 01, 2017 3:18 pm

dom wrote: I've had a look as I wasn't aware of where the 2400 came from.
Turns out default max_framebuffer is 1920x1200 (if you don't override in config.txt).
There is a limit of virtual framebuffer size of double the physical size. But for some reason the width/heights were swapped - possibly a typo when adding rotated framebuffer support.
The virtual framebuffer is a linux feature allowing scrolling or page flipping by swapping halves of the virtual framebuffer.

Removing the swap of width/height in the virtual framebuffer size check does remove the 2400 limit and I can display the whole of 2560x1080.
This fix will be in next rpi-update firmware (and later in apt-get firmware).
Thanks for the clarification.
I used it to test with max_framebuffer_height=2560 and now the complete area is used.
For other with this (or a similar) monitor...
My complete /boot/config.txt

Code: Select all

max_framebuffer_width=2560
max_framebuffer_height=2560 #workaround for swapped values
framebuffer_width=2560
framebuffer_height=1080

disable_overscan=1
hdmi_group=2
hdmi_mode=87
hdmi_cvt=2560 1080 50 7 0 0 0
hdmi_pixel_freq_limit=200000000
hdmi_drive=2

dtparam=audio=on

r.home2061
Posts: 2
Joined: Mon Feb 13, 2017 2:33 am

Re: Setting up HDMI output when video output isn't what you

Mon Feb 13, 2017 2:47 am

I'm an owner of a DELL U2913WM and after the update to KODI 17 the custom hdmi mode for 21:9 doesn't work anymore.
After some trouble, now it works again for me and i'm happy to share this to anybody whos need.

These are my config.txt excerpt:

hdmi_drive=2
hdmi_ignore_edid=0xa5000080
hdmi_group=2
hdmi_mode=87
hdmi_aspect_21_9=7
hdmi_pixel_freq_limit=400000000
hdmi_cvt=2560 1080 50 7 0 0 1
config_hdmi_boost=4
max_framebuffer_width=2560
max_framebuffer_height=1080
framebuffer_width=2560
framebuffer_height=1080

I hope this will work for you, too.
If you had some improvement, please share it.

THX
greetings

bohrabohrafamily
Posts: 3
Joined: Wed Feb 15, 2017 6:21 am

Starting a getting a blank screen

Wed Feb 15, 2017 6:58 am

Hello all,
Sorry for the LONG post but I am at wits end and wanted to document everything to help someone find a solution to my problem :ugeek:
First time PI user and I got a PI 3. I was able to use it with my monitor (a new LG_IPS_FULLHD) and all was great. Eventually my wife wanted her monitor back and so I set up xrdp and was able to connect to the PI 3 using Windows Remote Desktop (following instruction found http://raspberrypi.stackexchange.com/qu ... -with-xrdp)

But recently I had went to a hacker space and need to get my PI 3 on the new network, before I could remote in to it, and so I plugged in a HDMI monitor and started up the PI 3. I got a little of the startup progress, a "press SHIFT" to enter recovery screen and then screen went black...but the 'blacklight' was still working. I tried another HDMI cable and another monitor but nothing worked so I gave up

When I came I tried connecting to my LG monitor which was working before but NOW IT TOO IS FAILING to display any picture (after an initial startup screen). However because I am back on my home network the xrdp connection works and I am able to use Windows Remote Desktop and get the Raspbian desktop.

With my LG HDMI monitor attached here the output from the commands

Code: Select all

/opt/vc/bin/tvservice -m CEA
Group CEA has 0 modes:

Code: Select all

/opt/vc/bin/tvservice -m DMT 
Group DMT has 0 modes:

Code: Select all

/opt/vc/bin/tvservice -s 
state 0x120009 [HDMI DMT (4) RGB full 4:3], 640x480 @ 60.00Hz, progressive

Code: Select all

parsed edid.dat file 
Enabling fuzzy format match...
Parsing edid.dat...
HDMI:EDID version 1.3, 1 extensions, screen size 48x27 cm
HDMI:EDID features - videodef 0x80 standby suspend active off; colour encoding:RGB444|YCbCr422; sRGB is not default colourspace; preferred format is native; does not support GTF
HDMI:EDID found monitor range descriptor tag 0xfd
HDMI:EDID monitor range offsets: V min=0, V max=0, H min=0, H max=0
HDMI:EDID monitor range: vertical is 56-75 Hz, horizontal is 30-83 kHz, max pixel clock is 150 MHz
HDMI:EDID monitor range does not support GTF
HDMI:EDID found monitor name descriptor tag 0xfc
HDMI:EDID monitor name is LG_IPS_FULLHD
HDMI:EDID found monitor S/N descriptor tag 0xff
HDMI:EDID found preferred CEA detail timing format: 1920x1080p @ 60 Hz (16)
HDMI:EDID established timing I/II bytes are A5 4B 00
HDMI:EDID found DMT format: code 4, 640x480p @ 60 Hz in established timing I/II
HDMI:EDID found DMT format: code 6, 640x480p @ 75 Hz in established timing I/II
HDMI:EDID found DMT format: code 9, 800x600p @ 60 Hz in established timing I/II
HDMI:EDID found DMT format: code 11, 800x600p @ 75 Hz in established timing I/II
HDMI:EDID found DMT format: code 16, 1024x768p @ 60 Hz in established timing I/II
HDMI:EDID found DMT format: code 18, 1024x768p @ 75 Hz in established timing I/II
HDMI:EDID found DMT format: code 36, 1280x1024p @ 75 Hz in established timing I/II
HDMI:EDID standard timings block x 8: 0x714F 8180 9500 B300 A9C0 8100 81C0 9040 
HDMI:EDID found DMT format: code 21, 1152x864p @ 75 Hz (4:3) in standard timing 0
HDMI:EDID found DMT format: code 35, 1280x1024p @ 60 Hz (5:4) in standard timing 1
HDMI:EDID found DMT format: code 47, 1440x900p @ 60 Hz (16:10) in standard timing 2
HDMI:EDID found DMT format: code 58, 1680x1050p @ 60 Hz (16:10) in standard timing 3
HDMI:EDID found DMT format: code 83, 1600x900p @ 60 Hz (16:9) in standard timing 4
HDMI:EDID found DMT format: code 28, 1280x800p @ 60 Hz (16:10) in standard timing 5
HDMI:EDID found DMT format: code 85, 1280x720p @ 60 Hz (16:9) in standard timing 6
HDMI:EDID found DMT format: code 42, 1400x1050p @ 60 Hz (4:3) in standard timing 7
HDMI:EDID parsing v3 CEA extension 0
HDMI:EDID monitor support - underscan IT formats:yes, basic audio:no, yuv444:yes, yuv422:yes, #native DTD:1
HDMI:EDID found CEA detail timing format: 1920x1080p @ 60 Hz (16)
HDMI:EDID found CEA detail timing format: 1920x1080i @ 60 Hz (5)
HDMI:EDID found CEA detail timing format: 1280x720p @ 60 Hz (4)
HDMI:EDID found CEA detail timing format: 720x480p @ 60 Hz (2)
HDMI:EDID found CEA format: code 16, 1920x1080p @ 60Hz (native)
HDMI:EDID found CEA format: code 4, 1280x720p @ 60Hz 
HDMI:EDID found CEA format: code 3, 720x480p @ 60Hz 
HDMI:EDID found CEA format: code 1, 640x480p @ 60Hz 
HDMI:EDID found CEA format: code 20, 1920x1080i @ 50Hz 
HDMI:EDID found CEA format: code 18, 720x576p @ 50Hz 
HDMI:EDID found CEA format: code 5, 1920x1080i @ 60Hz 
HDMI:EDID found CEA format: code 31, 1920x1080p @ 50Hz 
HDMI:EDID found CEA format: code 16, 1920x1080p @ 60Hz 
HDMI:EDID found CEA format: code 19, 1280x720p @ 50Hz 
HDMI:EDID found HDMI VSDB length 5
HDMI:EDID HDMI VSDB has physical address 1.0.0.0
HDMI:EDID HDMI VSDB has no extension fields
HDMI:EDID adding mandatory support for CEA (17) 720x576p @ 50Hz
HDMI:EDID filtering formats with pixel clock > 162 MHz or h. blanking > 1023
HDMI:EDID best score mode initialised to CEA (1) 640x480p @ 60 Hz with pixel clock 25 MHz (score 0)
HDMI:EDID best score mode is now CEA (1) 640x480p @ 60 Hz with pixel clock 25 MHz (score 61864)
HDMI:EDID best score mode is now CEA (2) 720x480p @ 60 Hz with pixel clock 27 MHz (score 3066472)
HDMI:EDID CEA mode (3) 720x480p @ 60 Hz with pixel clock 27 MHz has a score of 66472
HDMI:EDID best score mode is now CEA (4) 1280x720p @ 60 Hz with pixel clock 74 MHz (score 3635592)
HDMI:EDID DMT mode (4) 640x480p @ 60 Hz with pixel clock 25 MHz has a score of 18432
HDMI:EDID best score mode is now CEA (5) 1920x1080i @ 60 Hz with pixel clock 74 MHz (score 4273832)
HDMI:EDID DMT mode (6) 640x480p @ 75 Hz with pixel clock 31 MHz has a score of 23040
HDMI:EDID DMT mode (9) 800x600p @ 60 Hz with pixel clock 40 MHz has a score of 28800
HDMI:EDID DMT mode (11) 800x600p @ 75 Hz with pixel clock 49 MHz has a score of 36000
HDMI:EDID best score mode is now CEA (16) 1920x1080p @ 60 Hz with pixel clock 148 MHz (score 5398248)
HDMI:EDID DMT mode (16) 1024x768p @ 60 Hz with pixel clock 65 MHz has a score of 47185
HDMI:EDID CEA mode (17) 720x576p @ 50 Hz with pixel clock 27 MHz has a score of 66472
HDMI:EDID CEA mode (18) 720x576p @ 50 Hz with pixel clock 27 MHz has a score of 66472
HDMI:EDID DMT mode (18) 1024x768p @ 75 Hz with pixel clock 78 MHz has a score of 58982
HDMI:EDID CEA mode (19) 1280x720p @ 50 Hz with pixel clock 74 MHz has a score of 117160
HDMI:EDID CEA mode (20) 1920x1080i @ 50 Hz with pixel clock 74 MHz has a score of 128680
HDMI:EDID DMT mode (21) 1152x864p @ 75 Hz with pixel clock 108 MHz has a score of 99649
HDMI:EDID DMT mode (28) 1280x800p @ 60 Hz with pixel clock 83 MHz has a score of 86440
HDMI:EDID CEA mode (31) 1920x1080p @ 50 Hz with pixel clock 148 MHz has a score of 232360
HDMI:EDID DMT mode (35) 1280x1024p @ 60 Hz with pixel clock 108 MHz has a score of 103643
HDMI:EDID DMT mode (36) 1280x1024p @ 75 Hz with pixel clock 135 MHz has a score of 98304
HDMI:EDID DMT mode (42) 1400x1050p @ 60 Hz with pixel clock 121 MHz has a score of 113200
HDMI:EDID DMT mode (47) 1440x900p @ 60 Hz with pixel clock 106 MHz has a score of 102760
HDMI:EDID DMT mode (58) 1680x1050p @ 60 Hz with pixel clock 146 MHz has a score of 130840
HDMI:EDID DMT mode (83) 1600x900p @ 60 Hz with pixel clock 108 MHz has a score of 111400
HDMI:EDID DMT mode (85) 1280x720p @ 60 Hz with pixel clock 74 MHz has a score of 80296
HDMI:EDID preferred mode remained as CEA (16) 1920x1080p @ 60 Hz with pixel clock 148 MHz
HDMI:EDID has HDMI support and no audio support
edid_parser exited with code 0
Here is what I have in my /boot/config.txt

Code: Select all

# For more options and information see
# http://www.raspberrypi.org/documentation/configuration/config-txt.md
# Some settings may impact device functionality. See link above for details

# uncomment if you get no picture on HDMI for a default "safe" mode
hdmi_safe=1

# uncomment this if your display has a black border of unused pixels visible
# and your display can output without overscan
#disable_overscan=1

# uncomment the following to adjust overscan. Use positive numbers if console
# goes off screen, and negative if there is too much border
#overscan_left=16
#overscan_right=16
#overscan_top=16
#overscan_bottom=16

# uncomment to force a console size. By default it will be display's size minus
# overscan.
#framebuffer_width=1280
#framebuffer_height=720

# uncomment if hdmi display is not detected and composite is being output
hdmi_force_hotplug=1

# uncomment to force a specific HDMI mode (this will force VGA)
hdmi_group=2
hdmi_mode=85

# uncomment to force a HDMI mode rather than DVI. This can make audio work in
# DMT (computer monitor) modes
hdmi_drive=2

# uncomment to increase signal to HDMI, if you have interference, blanking, or
# no display
config_hdmi_boost=4
hdmi_edid_file=1
# uncomment for composite PAL
#sdtv_mode=2

#uncomment to overclock the arm. 700 MHz is the default.
#arm_freq=800

# Uncomment some or all of these to enable the optional hardware interfaces
dtparam=i2c_arm=off
#dtparam=i2s=on
dtparam=spi=off

# Uncomment this to enable the lirc-rpi module
#dtoverlay=lirc-rpi

# Additional overlays and parameters are documented /boot/overlays/README

# Enable audio (loads snd_bcm2835)
dtparam=audio=on

# NOOBS Auto-generated Settings:
hdmi_force_hotplug=1
dtoverlay=vc4-kms-v3d
start_x=0
gpu_mem=256
enable_uart=0
#dtoverlay=w1-gpio
I have tried many things and tempted to WIPE the PI (reinstall Raspian) and start over...please help

dom
Raspberry Pi Engineer & Forum Moderator
Raspberry Pi Engineer & Forum Moderator
Posts: 5106
Joined: Wed Aug 17, 2011 7:41 pm
Location: Cambridge

Re: Starting a getting a blank screen

Wed Feb 15, 2017 12:40 pm

bohrabohrafamily wrote:

Code: Select all

hdmi_safe=1
hdmi_force_hotplug=1
hdmi_group=2
hdmi_mode=85
hdmi_drive=2
config_hdmi_boost=4
hdmi_edid_file=1
hdmi_force_hotplug=1
dtoverlay=vc4-kms-v3d
You seem to have a lot of conflicting options specified so it is perhaps not surprising you have trouble.

First, the config.txt hdmi options affect the firmware display driver only.
You have enabled vc4-kms-v3d which is the experimental arm side 3d/display driver. Do you really want to be using that? It is still considered experimental and not enabled by default.

Personally I'd remove every setting I've quoted above and see how you get on.

bohrabohrafamily
Posts: 3
Joined: Wed Feb 15, 2017 6:21 am

Re: Setting up HDMI output when video output isn't what you

Wed Feb 15, 2017 5:14 pm

Hello,

I will try...I've been trying many things to get the display working but to no avail.

I will remove (i.e. comment out) those entries and report back

Thanks!

bohrabohrafamily
Posts: 3
Joined: Wed Feb 15, 2017 6:21 am

Re: Setting up HDMI output when video output isn't what you

Thu Feb 16, 2017 12:01 am

THANKS!!!
THANKS!!!
THANKS!!!

Commenting out the items allowed to work. The desktop is not fully using the entire monitor space but it renders!

Now should I try uncommenting the lines back to see what restores the full size and what caused the break :geek:

dom
Raspberry Pi Engineer & Forum Moderator
Raspberry Pi Engineer & Forum Moderator
Posts: 5106
Joined: Wed Aug 17, 2011 7:41 pm
Location: Cambridge

Re: Setting up HDMI output when video output isn't what you

Thu Feb 16, 2017 10:52 am

bohrabohrafamily wrote:Now should I try uncommenting the lines back to see what restores the full size and what caused the break :geek:
Try adding disable_overscan=1

matinzk
Posts: 35
Joined: Fri Sep 28, 2012 4:26 pm
Location: UK

Re: Setting up HDMI output when video output isn't what you

Sat May 13, 2017 5:39 pm

I have a 12.3" bar type (ultra wide) LCD with 1920x720 pixels resolution.

When I set the config.txt to this resolution I get some distorted pixels at the bottom of the LCD. Any ideas how I can get rid of them?

This is the contents of the confg.txt file:-

Code: Select all

arm_freq=700
gpu_freq=250
gpu_mem=128

hdmi_force_hotplug=1

hdmi_drive=2
hdmi_ignore_edid=0xa5000080

hdmi_group=2
hdmi_mode=87

hdmi_cvt 1920 720 60 6 0 0 1
framebuffer_depth=16
					  
config_hdmi_boost=4

disable_overscan=1
Also here is an image
Image


Any help is much appreciated.

Thank you.

RoddyJoff
Posts: 35
Joined: Wed Jan 15, 2014 3:31 pm
Location: Manchester, UK

Re: Setting up HDMI output when video output isn't what you

Sat May 20, 2017 3:52 pm

I wonder if anyone is able to help.

I am attempting to connect an Apple 20" DVI monitor to my Raspberry Pi using anHDMI to DVI adapter - I have tried three different ones so far without success sadly.

I know the monitor works OK.

When I boot the Pi the white LED on the monitor flashes 3 times, waits a few seconds and then flashes again, repeated ad infinitum.

By researching the problem I have discovered the TVSERVICE utility and using it have recorded the following information. None of the settings I have tried have worked.

Does anyone know if an Apple DVI monitor will work with a Pi and if so what the correct settings are?

Thanking you all in advance.....

Code: Select all

 
pi@WeatherC ~ $ tvservice -n
device_name=APP-y

pi@WeatherC ~ $ tvservice --mode=CEA
Group CEA has 0 modes:

pi@WeatherC ~ $ tvservice --mode=DMT
Group DMT has 3 modes:
  (prefer) mode 4: 640x480 @ 60Hz 4:3, clock:25MHz progressive 
           mode 57: 1680x1050 @ 60Hz 16:10, clock:119MHz progressive 
           mode 58: 1680x1050 @ 60Hz 16:10, clock:146MHz progressive 

===========================

pi@WeatherC ~ $ tvservice -e="DMT 4 HDMI"
Powering on HDMI with explicit settings (DMT mode 4)

pi@WeatherC ~ $ /opt/vc/bin/tvservice -d edid.dat
Written 256 bytes to edid.dat

pi@WeatherC ~ $ /opt/vc/bin/edidparser edid.dat

Enabling fuzzy format match...
Parsing edid.dat...
HDMI:EDID version 1.3, 1 extensions, screen size 43x27 cm
HDMI:EDID features - videodef 0x80 !standby !suspend active off; colour encoding:RGB444|YCbCr444|YCbCr422; sRGB is default colourspace; preferred format is native; does not support GTF
HDMI:EDID found monitor name descriptor tag 0xfc
HDMI:EDID monitor name is Cinema_Displa�
HDMI:EDID found monitor name descriptor tag 0xfc
HDMI:EDID monitor name is y
HDMI:EDID ignored unknown descriptor tag 0x0
HDMI:EDID does not yet know monitor vertical range, setting to default 24 to 120Hz
HDMI:EDID found preferred DMT detail timing format: 1680x1050p @ 60 Hz (57)
HDMI:EDID established timing I/II bytes are 00 00 00
HDMI:EDID standard timings block x 8: 0xB300 0101 0101 0101 0101 0101 0101 0101 
HDMI:EDID found DMT format: code 58, 1680x1050p @ 60 Hz (16:10) in standard timing 0
HDMI:EDID skipping over display information extension tag 0x40
HDMI:EDID adding mandatory support for DMT (4) 640x480p @ 60Hz
HDMI:EDID filtering formats with pixel clock > 162 MHz or h. blanking > 1023
HDMI:EDID best score mode initialised to DMT (4) 640x480p @ 60 Hz with pixel clock 25 MHz (score 0)
HDMI:EDID best score mode is now DMT (4) 640x480p @ 60 Hz with pixel clock 25 MHz (score 36864)
HDMI:EDID best score mode is now DMT (57) 1680x1050p @ 60 Hz with pixel clock 119 MHz (score 5317520)
HDMI:EDID DMT mode (58) 1680x1050p @ 60 Hz with pixel clock 146 MHz has a score of 236680
HDMI:EDID preferred mode remained as DMT (57) 1680x1050p @ 60 Hz with pixel clock 119 MHz
HDMI:EDID has only DVI support and no audio support
edid_parser exited with code 0
pi@WeatherC ~ $ 

===========================

pi@WeatherC ~ $ tvservice -e="DMT 57 HDMI"
Powering on HDMI with explicit settings (DMT mode 57)

pi@WeatherC ~ $ /opt/vc/bin/tvservice -d edid.dat
Written 256 bytes to edid.dat

pi@WeatherC ~ $ /opt/vc/bin/edidparser edid.dat

Enabling fuzzy format match...
Parsing edid.dat...
HDMI:EDID version 1.3, 1 extensions, screen size 43x27 cm
HDMI:EDID features - videodef 0x80 !standby !suspend active off; colour encoding:RGB444|YCbCr444|YCbCr422; sRGB is default colourspace; preferred format is native; does not support GTF
HDMI:EDID found monitor name descriptor tag 0xfc
HDMI:EDID monitor name is Cinema_Displa����D�v�4�v
HDMI:EDID found monitor name descriptor tag 0xfc
HDMI:EDID monitor name is y
HDMI:EDID ignored unknown descriptor tag 0x0
HDMI:EDID does not yet know monitor vertical range, setting to default 24 to 120Hz
HDMI:EDID found preferred DMT detail timing format: 1680x1050p @ 60 Hz (57)
HDMI:EDID established timing I/II bytes are 00 00 00
HDMI:EDID standard timings block x 8: 0xB300 0101 0101 0101 0101 0101 0101 0101 
HDMI:EDID found DMT format: code 58, 1680x1050p @ 60 Hz (16:10) in standard timing 0
HDMI:EDID skipping over display information extension tag 0x40
HDMI:EDID adding mandatory support for DMT (4) 640x480p @ 60Hz
HDMI:EDID filtering formats with pixel clock > 162 MHz or h. blanking > 1023
HDMI:EDID best score mode initialised to DMT (4) 640x480p @ 60 Hz with pixel clock 25 MHz (score 0)
HDMI:EDID best score mode is now DMT (4) 640x480p @ 60 Hz with pixel clock 25 MHz (score 36864)
HDMI:EDID best score mode is now DMT (57) 1680x1050p @ 60 Hz with pixel clock 119 MHz (score 5317520)
HDMI:EDID DMT mode (58) 1680x1050p @ 60 Hz with pixel clock 146 MHz has a score of 236680
HDMI:EDID preferred mode remained as DMT (57) 1680x1050p @ 60 Hz with pixel clock 119 MHz
HDMI:EDID has only DVI support and no audio support
edid_parser exited with code 0

===========================

pi@WeatherC ~ $ tvservice -e="DMT 58 HDMI"
Powering on HDMI with explicit settings (DMT mode 58)

pi@WeatherC ~ $ /opt/vc/bin/tvservice -d edid.dat
Written 256 bytes to edid.dat

pi@WeatherC ~ $ /opt/vc/bin/edidparser edid.dat

Enabling fuzzy format match...
Parsing edid.dat...
HDMI:EDID version 1.3, 1 extensions, screen size 43x27 cm
HDMI:EDID features - videodef 0x80 !standby !suspend active off; colour encoding:RGB444|YCbCr444|YCbCr422; sRGB is default colourspace; preferred format is native; does not support GTF
HDMI:EDID found monitor name descriptor tag 0xfc
HDMI:EDID monitor name is Cinema_Displa0W0Wd�v�T�v
HDMI:EDID found monitor name descriptor tag 0xfc
HDMI:EDID monitor name is y
HDMI:EDID ignored unknown descriptor tag 0x0
HDMI:EDID does not yet know monitor vertical range, setting to default 24 to 120Hz
HDMI:EDID found preferred DMT detail timing format: 1680x1050p @ 60 Hz (57)
HDMI:EDID established timing I/II bytes are 00 00 00
HDMI:EDID standard timings block x 8: 0xB300 0101 0101 0101 0101 0101 0101 0101 
HDMI:EDID found DMT format: code 58, 1680x1050p @ 60 Hz (16:10) in standard timing 0
HDMI:EDID skipping over display information extension tag 0x40
HDMI:EDID adding mandatory support for DMT (4) 640x480p @ 60Hz
HDMI:EDID filtering formats with pixel clock > 162 MHz or h. blanking > 1023
HDMI:EDID best score mode initialised to DMT (4) 640x480p @ 60 Hz with pixel clock 25 MHz (score 0)
HDMI:EDID best score mode is now DMT (4) 640x480p @ 60 Hz with pixel clock 25 MHz (score 36864)
HDMI:EDID best score mode is now DMT (57) 1680x1050p @ 60 Hz with pixel clock 119 MHz (score 5317520)
HDMI:EDID DMT mode (58) 1680x1050p @ 60 Hz with pixel clock 146 MHz has a score of 236680
HDMI:EDID preferred mode remained as DMT (57) 1680x1050p @ 60 Hz with pixel clock 119 MHz
HDMI:EDID has only DVI support and no audio support
edid_parser exited with code 0
pi@WeatherC ~ $ 

===========================

------------------------------------
The best things in life are free.

RoddyJoff
Posts: 35
Joined: Wed Jan 15, 2014 3:31 pm
Location: Manchester, UK

Re: Setting up HDMI output when video output isn't what you

Sat May 20, 2017 3:57 pm

PS

Here's a copy of the CONFIG.TXT file..

[codepi@WeatherC ~ $ cat /boot/config.txt
# For more options and information see
# http://www.raspberrypi.org/documentatio ... fig-txt.md
# Some settings may impact device functionality. See link above for details

# uncomment if you get no picture on HDMI for a default "safe" mode
hdmi_safe=1

# uncomment this if your display has a black border of unused pixels visible
# and your display can output without overscan
#disable_overscan=1

# uncomment the following to adjust overscan. Use positive numbers if console
# goes off screen, and negative if there is too much border
#overscan_left=16
#overscan_right=16
#overscan_top=16
#overscan_bottom=16

# uncomment to force a console size. By default it will be display's size minus
# overscan.
#framebuffer_width=1280
#framebuffer_height=720

# uncomment if hdmi display is not detected and composite is being output
hdmi_force_hotplug=1

#hdmi_ignore_edid=0xa5000080

# uncomment to force a specific HDMI mode (this will force VGA)
hdmi_group=2
hdmi_mode=4

# uncomment to force a HDMI mode rather than DVI. This can make audio work in
# DMT (computer monitor) modes
hdmi_drive=1

# uncomment to increase signal to HDMI, if you have interference, blanking, or
# no display
config_hdmi_boost=4

# uncomment for composite PAL
#sdtv_mode=2

#uncomment to overclock the arm. 700 MHz is the default.
#arm_freq=800
][/code]
------------------------------------
The best things in life are free.

User avatar
FTrevorGowen
Forum Moderator
Forum Moderator
Posts: 4115
Joined: Mon Mar 04, 2013 6:12 pm
Location: Bristol, U.K.
Contact: Website

Re: Setting up HDMI output when video output isn't what you

Sat May 20, 2017 5:33 pm

@RoddyJoff, AFAICT from your two posts these settings

Code: Select all

hdmi_group=2
hdmi_mode=4
in config.txt are inconsistent with those reported as being "usuable" via the tvservice command:

Code: Select all

pi@WeatherC ~ $ tvservice --mode=DMT
Group DMT has 3 modes:
  (prefer) mode 4: 640x480 @ 60Hz 4:3, clock:25MHz progressive
           mode 57: 1680x1050 @ 60Hz 16:10, clock:119MHz progressive
           mode 58: 1680x1050 @ 60Hz 16:10, clock:146MHz progressive 
I also have noted that there are no "native" or "preferred" modes shown**. This makes me wonder whether you're really using a HDMI-to-VGA converter (active) rather than a HDMI-to-DVI adapter/cable (I've never seen/used any Apple monitors since the time of the Apple II which was composite**** and whether they are DVI or VGA IJDK)?
Trev.
** See my notes here for examples: http://www.cpmspectrepi.uk/raspberry_pi ... tings.html
**** Which I used as a green monochrome display for a Spectrum+3 running CP/M .
Usually running Raspbian Jessie on up to 12 of 13 Pi's (an A, B1, 2xB2, 2xB+, A+, P2B, 3xP0, P0W) and Stretch on my P3B. See: https://www.cpmspectrepi.uk/raspberry_pi/raspiidx.htm

epgibbons
Posts: 3
Joined: Tue May 09, 2017 4:35 pm

Re: Setting up HDMI output when video output isn't what you

Thu May 25, 2017 8:06 pm

In my case I want to run the pi without a connected hdmi device (e.g. smart tv) and use vncviewer on my laptop with resolution that matches the resolution of the laptop screen.
To do that I uncommented and edited the following lines in /boot/config.txt

disable_overscan=1 ( so that resolution is defined by hdmi_group and hdmi_mode as below)

hdmi_force_hotplug=1

hdmi_group=1
hdmi_mode=16 (1920*1080)

hdmi_drive=2

RoddyJoff
Posts: 35
Joined: Wed Jan 15, 2014 3:31 pm
Location: Manchester, UK

Re: Setting up HDMI output when video output isn't what you

Mon Jun 05, 2017 11:01 am

Thanks for your reply Trev, it pointed me in the right direction and after further research I have finally fixed it.

Here’s the solution for anyone else who is having trouble.

Modify the config.txt file so that it only contains the following lines:

Code: Select all

hdmi_drive=2 
config_hdmi_boost=4 
hdmi_group=1 
hdmi_mode=16 
hdmi_force_hotplug=1 
disable_overscan=0
Cheers.
------------------------------------
The best things in life are free.

RoddyJoff
Posts: 35
Joined: Wed Jan 15, 2014 3:31 pm
Location: Manchester, UK

Re: Setting up HDMI output when video output isn't what you

Mon Jun 05, 2017 11:19 am

PS here is where I found the solution...

https://raspberrypi.stackexchange.com/q ... put-to-vga
------------------------------------
The best things in life are free.

Return to “Troubleshooting”

Who is online

Users browsing this forum: David_J_Haley and 41 guests