transmitterdan
Posts: 5
Joined: Sun Sep 10, 2017 11:57 pm

Re: STICKY: Setting up HDMI output when video output is wrong.

Sat Feb 08, 2020 10:33 pm

transmitterdan wrote:
Sun Jan 19, 2020 4:01 am
I use HDMI video into a 55 inch LG OLED TV. I have 3 Pi units (1 model 3B and 2 model 4). The one older 3B unit works fine. But the 2 brand new model 4 units both cause the TV to blank (switches to black) then a couple seconds later the screen comes back on. It happens at random but really annoying times. Is there any solution to the screen blinking off/on?

Here are some tvservice outputs:

Code: Select all

[email protected]:~ $ tvservice -s
state 0xa [HDMI CEA (16) RGB lim 16:9], 1920x1080 @ 60.00Hz, progressive
[email protected]:~ $ tvservice -s
state 0xa [HDMI CEA (16) RGB lim 16:9], 1920x1080 @ 60.00Hz, progressive
[email protected]:~ $ tvservice -l
1 attached device(s), display ID's are : 
Display Number 2, type HDMI 0
[email protected]:~ $ edid-decode 10in-edid 
EDID version: 1.3
Manufacturer: GSM Model 1 Serial Number 16843009
Made in week 1 of 2017
Digital display
Maximum image size: 160 cm x 90 cm
Gamma: 2.20
RGB color display
First detailed timing is preferred timing
Display x,y Chromaticity:
  Red:   0.6396, 0.3300
  Green: 0.2998, 0.5996
  Blue:  0.1503, 0.0595
  White: 0.3125, 0.3291
Established timings supported:
  [email protected] 9:5 HorFreq: 31469 Hz Clock: 28.320 MHz
  [email protected] 4:3 HorFreq: 31469 Hz Clock: 25.175 MHz
  [email protected] 4:3 HorFreq: 37900 Hz Clock: 40.000 MHz
  [email protected] 4:3 HorFreq: 48400 Hz Clock: 65.000 MHz
Standard timings supported:
  [email protected] 4:3 HorFreq: 31469 Hz Clock: 25.175 MHz
  [email protected] 4:3 HorFreq: 37900 Hz Clock: 40.000 MHz
  [email protected] 4:3 HorFreq: 48400 Hz Clock: 65.000 MHz
  [email protected] 4:3
  [email protected] 5:4 HorFreq: 64000 Hz Clock: 108.000 MHz
Detailed mode: Clock 594.000 MHz, 1600 mm x 900 mm
               3840 4016 4104 4400 hborder 0
               2160 2168 2178 2250 vborder 0
               +hsync +vsync 
I guess since no one knows the answer then the Pi 4 units are just junk hardware. This is a pretty modern display and it works with every device I connect except the Pi 4 units i have. Both cause the display to glitch on and off with some random lines appearing from time to time.

aBUGSworstnightmare
Posts: 1673
Joined: Tue Jun 30, 2015 1:35 pm

Re: STICKY: Setting up HDMI output when video output is wrong.

Sun Feb 09, 2020 8:27 am

Tried adding 'disable_fw_kms_setup=1' to your config.txt?

transmitterdan
Posts: 5
Joined: Sun Sep 10, 2017 11:57 pm

Re: STICKY: Setting up HDMI output when video output is wrong.

Sun Feb 09, 2020 4:04 pm

aBUGSworstnightmare wrote:
Sun Feb 09, 2020 8:27 am
Tried adding 'disable_fw_kms_setup=1' to your config.txt?
I have not tried that. I am trying right now to run self-built Linux kernel from github latest 4.19 kernel.

Code: Select all

[email protected]:~ $ uname --all
Linux raspberrypi4g 4.19.102-v7l+ #1 SMP Sat Feb 8 17:46:41 CST 2020 armv7l GNU/Linux
So far this morning no blackouts or glitches. So it would seem this issue is related to software/firmware which might be fixed in github.

aBUGSworstnightmare
Posts: 1673
Joined: Tue Jun 30, 2015 1:35 pm

Re: STICKY: Setting up HDMI output when video output is wrong.

Sun Feb 09, 2020 4:56 pm

There is an new offical Raspbian release as well 05/02/2020

lalumiere368
Posts: 1
Joined: Sun Feb 16, 2020 9:08 pm

Re: Setting up HDMI output

Sun Feb 16, 2020 9:28 pm

abishur wrote:
Mon May 14, 2012 12:39 pm
Actually I'd say at the present this is absolutely vital to absolute beginners. :-) There's been a lot of issues with newbies getting the device to work just the way they want to on their screens. The directions are concise and easy to follow so even an absolute beginner should be able to type in the single line on the bash prompt to get the modes supported by their TV/monitor.

Side note, I'm using a 5 port HDMI switcher. I've noticed that if I change the active HDMI port off of the pi for a bit, when I swap it back I don't have HDMI output from the pi. It's not that the screen is just black, there is simply no output. I can still SSH into it, so it's not frozen either. Is there a setting in config.txt to add to constantly force HDMI output that might resolve this? I've already set hdmi_mode=16
Speaking as an absolute beginner, yeah, I'm finding this really helpful. Here are some stupid questions:

I'm not even getting a bash prompt from my TV/monitor. It just switches back and forth from digital to analog mode looking for a signal. I have some theories on why this could be happening.

1) I need to configure the pi on my PC first by opening the config.txt file in bash (I will probably try this ASAP after finishing this post). Or do I need to try the keyboard shortcuts? But it doesn't even look like NOOBS is loading.
2) The DVI-microHDMI adapter I got for my screen (an older samsung monitor) does not fit well in the HDMI 0 port, and it's not establishing a connection. I've read that this has been an issue for others. When I put the microHDMI cable into the HDMI 1 port, the screen lights up in a bunch of vertical rgb lines. So something is happening there. I have read that if I'm only connecting one screen I have to use the HDMI 0 port. Which would suck, because the fit is too tight on my pi, for this adapter anyway, and it just doesn't seem to be making the connection. I can't verify whether this is true though and don't want to order new hardware if I can fix it with software.
3) Do I maybe need a DVI to HDMI converter cable instead of an adapter cable?
3) Monitor is incompatible and won't translate to HDMI. It is a Samsung B2230 widescreen monitor. I am still researching if there are any internal glitches with DVI to HDMI output.

The only other screen I have available right now is a gechic onlap 1302, which is even more of a pain in the ass, so I'd really appreciate some feedback and moral support. Thanks!

aBUGSworstnightmare
Posts: 1673
Joined: Tue Jun 30, 2015 1:35 pm

Re: Setting up HDMI output

Mon Feb 17, 2020 5:33 am

lalumiere368 wrote:
Sun Feb 16, 2020 9:28 pm
abishur wrote:
Mon May 14, 2012 12:39 pm
Actually I'd say at the present this is absolutely vital to absolute beginners. :-) There's been a lot of issues with newbies getting the device to work just the way they want to on their screens. The directions are concise and easy to follow so even an absolute beginner should be able to type in the single line on the bash prompt to get the modes supported by their TV/monitor.

Side note, I'm using a 5 port HDMI switcher. I've noticed that if I change the active HDMI port off of the pi for a bit, when I swap it back I don't have HDMI output from the pi. It's not that the screen is just black, there is simply no output. I can still SSH into it, so it's not frozen either. Is there a setting in config.txt to add to constantly force HDMI output that might resolve this? I've already set hdmi_mode=16
Speaking as an absolute beginner, yeah, I'm finding this really helpful. Here are some stupid questions:

I'm not even getting a bash prompt from my TV/monitor. It just switches back and forth from digital to analog mode looking for a signal. I have some theories on why this could be happening.

1) I need to configure the pi on my PC first by opening the config.txt file in bash (I will probably try this ASAP after finishing this post). Or do I need to try the keyboard shortcuts? But it doesn't even look like NOOBS is loading.
2) The DVI-microHDMI adapter I got for my screen (an older samsung monitor) does not fit well in the HDMI 0 port, and it's not establishing a connection. I've read that this has been an issue for others. When I put the microHDMI cable into the HDMI 1 port, the screen lights up in a bunch of vertical rgb lines. So something is happening there. I have read that if I'm only connecting one screen I have to use the HDMI 0 port. Which would suck, because the fit is too tight on my pi, for this adapter anyway, and it just doesn't seem to be making the connection. I can't verify whether this is true though and don't want to order new hardware if I can fix it with software.
3) Do I maybe need a DVI to HDMI converter cable instead of an adapter cable?
3) Monitor is incompatible and won't translate to HDMI. It is a Samsung B2230 widescreen monitor. I am still researching if there are any internal glitches with DVI to HDMI output.

The only other screen I have available right now is a gechic onlap 1302, which is even more of a pain in the ass, so I'd really appreciate some feedback and moral support. Thanks!
isn't your Samsung monitor FHD resolution (1920x1080pixels)? So why not simply force that mode (see https://www.raspberrypi.org/documentati ... t/video.md )?
Do you really neede noobs? Why don't you start with a plain Raspbian Buster https://www.raspberrypi.org/downloads/raspbian/ ?

transmitterdan
Posts: 5
Joined: Sun Sep 10, 2017 11:57 pm

Re: STICKY: Setting up HDMI output when video output is wrong.

Fri Feb 28, 2020 1:00 pm

transmitterdan wrote:
Sun Feb 09, 2020 4:04 pm
So far this morning no blackouts or glitches. So it would seem this issue is related to software/firmware which might be fixed in github.
Well the blackouts are back. And now I think I have another clue. As long as a VNC viewer is viewing the RPi 4 screen then the TV monitor blinks on and off rapidly and often. As soon as I kill the VNC viewer on my Windows laptop the RPi monitor screen is much more stable but still blanks off and on occasionally. More often when running a graphics intensive application.

I am convinced this is some kind of software bug related to really high resolution displays. It's as if the software/firmware can't keep up with the pixel rate needed by hi-res HDMI displays.

DCIMike125
Posts: 2
Joined: Tue Mar 03, 2020 8:19 pm

Re: STICKY: Setting up HDMI output when video output is wrong.

Tue Mar 03, 2020 8:29 pm

Hi all, I just got a PI4. When I power it up, I see a "splash screen" followed by recovery options...the no video output at all. I can access it thru remote desktop. my power supply is 2500mA which should be plenty

Help!!!

Image
Image
Image

aBUGSworstnightmare
Posts: 1673
Joined: Tue Jun 30, 2015 1:35 pm

Re: STICKY: Setting up HDMI output when video output is wrong.

Wed Mar 04, 2020 1:52 pm

DCIMike125 wrote:
Tue Mar 03, 2020 8:29 pm
Hi all, I just got a PI4. When I power it up, I see a "splash screen" followed by recovery options...the no video output at all. I can access it thru remote desktop. my power supply is 2500mA which should be plenty

Help!!!
...
Flash a new uSD card (or re-flash the one you're using) with the OS image https://www.raspberrypi.org/downloads/raspbian/ ) and then start from scratch.

Are you using NOOBS by chance (as I've never seen a recovery message ...)
Make sure to use HDMI0 - that's the HDMI port next to USB-C

DCIMike125
Posts: 2
Joined: Tue Mar 03, 2020 8:19 pm

Re: STICKY: Setting up HDMI output when video output is wrong.

Wed Mar 04, 2020 3:06 pm

Flash a new uSD card (or re-flash the one you're using) with the OS image https://www.raspberrypi.org/downloads/raspbian/ ) and then start from scratch.

Are you using NOOBS by chance (as I've never seen a recovery message ...)
Make sure to use HDMI0 - that's the HDMI port next to USB-C
Thanks, that worked

meanmeech
Posts: 10
Joined: Sun Jan 06, 2013 7:24 pm

Re: STICKY: Setting up HDMI output when video output is wrong.

Wed Mar 25, 2020 6:44 am

Maybe not the right place to post?

I have a dual screen issue with the Pi4 using hdmi, in particular, the resolution settings are in stuck in "Fixed Mode", so I have not options to change.

tvservice -s
state 0xa [HDMI DMT (87) RGB full 16:9], 1080x1920 @ 60.00Hz, progressive

Hware - Pi4 4Gb, Screens are both waveshare 5.5" amoled
OS - Buster

As of today, both screens are working in 1920x1080. I had to ignore waveshares comment stating to delete overlay, as without it, I simple couldn't get both screens to work. However, if I remove the specific hdmi_mode and timing, again, both screens show snow.
****************************************************************************
* All I want is to reduce to resolution as everything is just a little to small. *
****************************************************************************

Here is what I did to get everything up and running -


Using just one screen works fine on Buster (latest updates etc) when following the instruction provided by waveshare, IE amend the config.txt file -

max_framebuffer_height=1920
max_usb_current=1
config_hdmi_boost=10
hdmi_group=2
hdmi_force_hotplug=1
hdmi_mode=87
hdmi_timings=1080 1 26 4 50 1920 1 8 2 6 0 0 0 60 0 135580000 3
Plus they advise to removed line dtoverlay=vc4-fkms-V3D.

Adding the second screen is where the fun begins.


One screen works when using this -
*************************************

# Enable DRM VC4 V3D driver on top of the dispmanx display stack
#dtoverlay=vc4-fkms-v3d
#max_framebuffers=2

[all]
#dtoverlay=vc4-fkms-v3d

max_framebuffer_height=1920
max_usb_current=1
config_hdmi_boost=10
hdmi_group=2
hdmi_force_hotplug=1
hdmi_mode=87
hdmi_timings=1080 1 26 4 50 1920 1 8 2 6 0 0 0 60 0 135580000 3
display_rotate=1


Second screen added - not working
************************************
added lines in Config.txt -

max_framebuffer_height=1920
max_usb_current=1
config_hdmi_boost=10
hdmi_group=2
hdmi_force_hotplug=1
hdmi_mode=87
hdmi_timings=1080 1 26 4 50 1920 1 8 2 6 0 0 0 60 0 135580000 3
display_rotate=1

max_framebuffer_height:1=1920
#max_usb_current:1=1
config_hdmi_boost:1=10
hdmi_group:1=2
hdmi_force_hotplug:1=1
hdmi_mode:1=87
hdmi_timings:1=1080 1 26 4 50 1920 1 8 2 6 0 0 0 60 0 135580000 3
display_rotate:1=1

Second screen now working but only showing the rainbow Splash screen
***************************************************************************

tvservice -s
state 0xa [HDMI DMT (87) RGB full 16:9], 1080x1920 @ 60.00Hz, progressive

Is this showing hdmi0 only?

Thought I would give "core_freq_min:1=500" a try... no bananas! -

Removing the following lines -
****************************

#max_usb_current:1=1
#config_hdmi_boost:1=10
hdmi_group:1=2
#hdmi_force_hotplug:1=1


Back to hdmi1 with the splash screen...


Enabled the following as I noticed that xrandx is missing, IE Screen configuration was missing.
*************************************************************************************************

dtoverlay=vc4-fkms-v3d
max_framebuffers=2

This became interesting. Second screen working in portait and first now stuck on the welcome screen. BUT the cursor works.


Removed the following -

# Enable DRM VC4 V3D driver on top of the dispmanx display stack
dtoverlay=vc4-fkms-v3d
max_framebuffers=2

[all]
#dtoverlay=vc4-fkms-v3d

#core_freq_min=500
#core_freq_min:1=500

#max_framebuffer_height=1920
#max_usb_current=1
#config_hdmi_boost=10
hdmi_group=2
hdmi_force_hotplug=1
hdmi_mode=87
hdmi_timings=1080 1 26 4 50 1920 1 8 2 6 0 0 0 60 0 135580000 3
#display_rotate=1

#max_framebuffer_height:1=1920
#max_usb_current:1=1
#config_hdmi_boost:1=10
#hdmi_group:1=2
#hdmi_force_hotplug:1=1
#hdmi_mode:1=87
#hdmi_timings:1=1080 1 26 4 50 1920 1 8 2 6 0 0 0 60 0 135580000 3
#display_rotate:1=1

Now have 2 screens in portait.

In "screen configuration" (Xrandr)/Screen layout editor, I moved the screens to the desired rotation and position. Save (click the tick)
***************************************************************************************************************************************

Now everything is not small.

miskor
Posts: 1
Joined: Wed Mar 25, 2020 7:48 am

Re: STICKY: Setting up HDMI output when video output is wrong.

Wed Mar 25, 2020 3:20 pm

Hi community,

Please, please help, I am going mad with this issue - whatever I set in raspi-config I can not get a picture on my (a little older) LG TV M2280D from rpi4! It only shows blank screen sometime with message "No signal", sometime just blank... Like it is unable to synchronize properly with rpi4 but why?

I tried with "hdmi-safe=1", no luck...

If I connect that same rpi4 to another monitor - it displays immediately picture from rpi4. If I connect some other hdmi device to TV HDMI input (e.g. retro console like Nintendo SNES ) - it will display the picture from that source!

Here is the output from few recommended commands in the first post:

[email protected]:~ $ tvservice -m CEA
Group CEA has 15 modes:
mode 1: 640x480 @ 60Hz 4:3, clock:25MHz progressive
mode 2: 720x480 @ 60Hz 4:3, clock:27MHz progressive
mode 3: 720x480 @ 60Hz 16:9, clock:27MHz progressive
(native) mode 4: 1280x720 @ 60Hz 16:9, clock:74MHz progressive
mode 5: 1920x1080 @ 60Hz 16:9, clock:74MHz interlaced
mode 7: 720x480 @ 60Hz 16:9, clock:27MHz x2 interlaced
(prefer) mode 16: 1920x1080 @ 60Hz 16:9, clock:148MHz progressive
mode 17: 720x576 @ 50Hz 4:3, clock:27MHz progressive
mode 18: 720x576 @ 50Hz 16:9, clock:27MHz progressive
mode 19: 1280x720 @ 50Hz 16:9, clock:74MHz progressive
mode 20: 1920x1080 @ 50Hz 16:9, clock:74MHz interlaced
mode 22: 720x576 @ 50Hz 16:9, clock:27MHz x2 interlaced
mode 31: 1920x1080 @ 50Hz 16:9, clock:148MHz progressive
mode 32: 1920x1080 @ 24Hz 16:9, clock:74MHz progressive
mode 34: 1920x1080 @ 30Hz 16:9, clock:74MHz progressive

[email protected]:~ $ tvservice -m DMT
Group DMT has 11 modes:
mode 4: 640x480 @ 60Hz 4:3, clock:25MHz progressive
mode 6: 640x480 @ 75Hz 4:3, clock:31MHz progressive
mode 9: 800x600 @ 60Hz 4:3, clock:40MHz progressive
mode 11: 800x600 @ 75Hz 4:3, clock:49MHz progressive
mode 16: 1024x768 @ 60Hz 4:3, clock:65MHz progressive
mode 17: 1024x768 @ 70Hz 4:3, clock:75MHz progressive
mode 18: 1024x768 @ 75Hz 4:3, clock:78MHz progressive
mode 21: 1152x864 @ 75Hz 4:3, clock:108MHz progressive
mode 35: 1280x1024 @ 60Hz 5:4, clock:108MHz progressive
mode 36: 1280x1024 @ 75Hz 5:4, clock:135MHz progressive
mode 58: 1680x1050 @ 60Hz 16:10, clock:146MHz progressive

[email protected]:~ $ tvservice -s
state 0xa [HDMI CUSTOM RGB full 16:9], 1280x720 @ 60.00Hz, progressive

[email protected]:~ $ tvservice -d edid.dat
Written 256 bytes to edid.dat

[email protected]:~ $ edidparser edid.dat
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 170 MHz
HDMI:EDID monitor range does not support GTF
HDMI:EDID found monitor name descriptor tag 0xfc
HDMI:EDID monitor name is M2280D
HDMI:EDID found preferred CEA detail timing format: 1920x1080p @ 60 Hz (16)
HDMI:EDID found DMT detail timing format: 1680x1050p @ 60 Hz (58)
HDMI:EDID established timing I/II bytes are A5 6F 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 17, 1024x768p @ 70 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: 0x8180 818F 7140 B300 814F 714F 0101 0101
HDMI:EDID found DMT format: code 35, 1280x1024p @ 60 Hz (5:4) in standard timing 0
HDMI:EDID found DMT format: code 36, 1280x1024p @ 75 Hz (5:4) in standard timing 1
HDMI:EDID unknown standard timing 1152x864 @ 60 Hz aspect ratio (4:3)
HDMI:EDID found DMT format: code 58, 1680x1050p @ 60 Hz (16:10) in standard timing 3
HDMI:EDID unknown standard timing 1280x960 @ 75 Hz aspect ratio (4:3)
HDMI:EDID found DMT format: code 21, 1152x864p @ 75 Hz (4:3) in standard timing 5
HDMI:EDID parsing v3 CEA extension 0
HDMI:EDID monitor support - underscan IT formats:yes, basic audio:yes, yuv444:yes, yuv422:yes, #native DTD:1
HDMI:EDID found CEA detail timing format: 1280x720p @ 60 Hz (4)
HDMI:EDID found CEA detail timing format: 1920x1080i @ 60 Hz (5)
HDMI:EDID found CEA detail timing format: 1920x1080i @ 50 Hz (20)
HDMI:EDID found CEA detail timing format: 1920x1080p @ 50 Hz (31)
HDMI:EDID found CEA detail timing format: 1920x1080p @ 60 Hz (16)
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 3, 720x480p @ 60Hz
HDMI:EDID found CEA format: code 2, 720x480p @ 60Hz
HDMI:EDID found CEA format: code 32, 1920x1080p @ 24Hz
HDMI:EDID found CEA format: code 34, 1920x1080p @ 30Hz
HDMI:EDID found CEA format: code 16, 1920x1080p @ 60Hz
HDMI:EDID found CEA format: code 17, 720x576p @ 50Hz
HDMI:EDID found CEA format: code 19, 1280x720p @ 50Hz
HDMI:EDID found CEA format: code 18, 720x576p @ 50Hz
HDMI:EDID found CEA format: code 20, 1920x1080i @ 50Hz
HDMI:EDID found CEA format: code 31, 1920x1080p @ 50Hz
HDMI:EDID found CEA format: code 7, 1440x480i @ 60Hz
HDMI:EDID found CEA format: code 22, 1440x576i @ 50Hz
HDMI:EDID found audio format 6 channels AC3, sample rate: 32|44|48 kHz, bitrate: 640 kbps
HDMI:EDID found audio format 2 channels PCM, sample rate: 32|44|48 kHz, sample size: 16|20|24 bits
HDMI:EDID found HDMI VSDB length 6
HDMI:EDID HDMI VSDB has physical address 1.0.0.0
HDMI:EDID HDMI VSDB supports AI:yes, dual link DVI:no
HDMI:EDID HDMI VSDB deep colour support - 48-bit:no 36-bit:no 30-bit:no DC_yuv444:no
HDMI:EDID HDMI VSDB has no latency information
HDMI:EDID adding mandatory support for CEA (1) 640x480p @ 60Hz
HDMI:EDID filtering formats with pixel clock unlimited MHz or h. blanking unlimited
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 66472)
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 4190888)
HDMI:EDID DMT mode (4) 640x480p @ 60 Hz with pixel clock 25 MHz has a score of 18432
HDMI:EDID CEA mode (5) 1920x1080i @ 60 Hz with pixel clock 74 MHz has a score of 3773832
HDMI:EDID DMT mode (6) 640x480p @ 75 Hz with pixel clock 31 MHz has a score of 5760
HDMI:EDID CEA mode (7) 1440x480i @ 60 Hz with pixel clock 27 MHz has a score of 45736
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 9000
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 DMT mode (17) 1024x768p @ 70 Hz with pixel clock 75 MHz has a score of 13762
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 14745
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 3232360
HDMI:EDID DMT mode (21) 1152x864p @ 75 Hz with pixel clock 108 MHz has a score of 43662
HDMI:EDID CEA mode (22) 1440x576i @ 50 Hz with pixel clock 27 MHz has a score of 45736
HDMI:EDID CEA mode (31) 1920x1080p @ 50 Hz with pixel clock 148 MHz has a score of 2732360
HDMI:EDID CEA mode (32) 1920x1080p @ 24 Hz with pixel clock 74 MHz has a score of 124532
HDMI:EDID CEA mode (34) 1920x1080p @ 30 Hz with pixel clock 74 MHz has a score of 149416
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 49576
HDMI:EDID DMT mode (58) 1680x1050p @ 60 Hz with pixel clock 146 MHz has a score of 4630840
HDMI0:EDID preferred mode remained as CEA (16) 1920x1080p @ 60 Hz with pixel clock 148 MHz
HDMI:EDID has HDMI support and audio support
edidparser exited with code 0
[email protected]:~ $

Please help, I am not a basic user but this is really difficult for me...

Regards,
Misko

aBUGSworstnightmare
Posts: 1673
Joined: Tue Jun 30, 2015 1:35 pm

Re: STICKY: Setting up HDMI output when video output is wrong.

Wed Mar 25, 2020 4:05 pm

If it's too small then you should buy bigger displays *lol*

Right click the desktop and change setting for large scree , should become bigger now

meanmeech
Posts: 10
Joined: Sun Jan 06, 2013 7:24 pm

Re: STICKY: Setting up HDMI output when video output is wrong.

Wed Mar 25, 2020 5:53 pm

Funny aBUGSworstnightmare…

Pointing out the obvious doesn't deal with problem. :mrgreen:
Screen size.jpg
Screen size.jpg (187 KiB) Viewed 102 times
As you can see, I've done this. Also then running tvservice, the modes available are only applicable to HDMI1 (secondary screen)

[email protected]:/opt/vc/bin $ /opt/vc/bin/tvservice -m DMT
Group DMT has 3 modes:
mode 4: 640x480 @ 60Hz 4:3, clock:25MHz progressive
(prefer) mode 87: 1080x1920 @ 60Hz 16:9, clock:135MHz progressive
mode 88: 1080x1920 @ 60Hz 16:9, clock:135MHz progressive

aBUGSworstnightmare
Posts: 1673
Joined: Tue Jun 30, 2015 1:35 pm

Re: STICKY: Setting up HDMI output when video output is wrong.

Thu Mar 26, 2020 6:03 pm

On the Pi 4, to specify the HDMI port, add an index identifier to the hdmi_group or hdmi_mode entry in config.txt, e.g. hdmi_mode:0 or hdmi_group:1.
Same is valid for hdmi_timings:0 or hdmi_timings:1=...

Make sure to have this set correcly in your config.txt.

What I told you was called pixel doubling in previous releases; have you tested it?

david_wijaya77
Posts: 1
Joined: Wed Apr 01, 2020 10:38 am

Re: STICKY: Setting up HDMI output when video output is wrong.

Wed Apr 01, 2020 10:42 am

Thank you for your detailed instruction about how to setting up HDMI output. Can I add the tutorial in my website https://nitrotekno.com? I will create a link to you for sure

Warm regards,
David

Return to “Troubleshooting”