pi5 CEA 1920x1080P impossibile to set

[giandeejay]

@Ashpool I have tried all methods in cmdline.txt
It works only on with Monitor DMT, but there's no solution to set a TV CEA.
TV CEA via HDMI 1 or 2 is completely ignored by Pi5... Black screen out of range.
Instead with pi4 all configuration is possible.
I have tried also to ignore edid...but nothing.
I have tried also to change with another TV, nothing...the pi5 won't let go...

[mitu]

@giandeejay said in pi5 CEA 1920x1080P impossibile to set:

Eg: if I have Television 1920x1080p 60hz what the correct parameters ?
I have tried all possible configuration

The one you posted earlier ( video=HDMI-A-1:1920x1080@60, this is for the 1st HDMI port ), it should work. Please post both the cmdline.txt content and the output of

cat /proc/cmdline

after the system has booted (to a black screen). You may need SSH in order to run the command and post the output of the command.

[Ashpool]

@giandeejay AFAIK modedb merges the formerly known CEA and DMT display modes in just one category. Taken from my raspberry pi4 connected to a Medion TV i get from Bullseye using fkms, modes queried via tvservice -m this list/available modes for CEA/DMT and under Bookworm using kms, queried via modetest this list/modes.

As I am running my TV on 1280x720p I haven't checked yesterday how it acts on video=1920x1080. I tried it now and had to learn, that the i(nterlace) flag following the frequency is ignored on my tv and 1920x1080@60 results in its native 1080i mode - and with just a quick RTFM (thanks @mitu for the modedb docs) I had assumed that i has explicitly to be set for interlaced modes, falling back to the (undocumented?) parameter p (see source for modedb) also doesn't work. Though I can set 1920x1080@59.94 (index #2 from my modetest list above).

[giandeejay]

@mitu

I have tested 2 possible configuration in /boot/cmdline.txt on PI5:

video=HDMI-A-1:1920x1080M@60m
video=HDMI-A-1:1920x1080@60

first:

pi@raspberrypi:/proc $ cat /proc/cmdline
coherent_pool=1M 8250.nr_uarts=1 pci=pcie_bus_safe snd_bcm2835.enable_compat_alsa=0 snd_bcm2835.enable_hdmi=1 smsc95xx.macaddr=D8:3A:DD:A8:28:CE vc_mem.mem_base=0x3fc00000
vc_mem.mem_size=0x40000000 console=ttyAMA10,115200 console=tty1 root=PARTUUID=8fc0304d-02 rootfstype=ext4 fsck.repair=yes rootwait
cfg80211.ieee80211_regdom=IT quiet splash plymouth.ignore-serial-consoles video=HDMI-A-1:1920x1080M@60m

results:
for monitor this work, but not for TV (black screen)

second:

pi@raspberrypi:~ $ cat /proc/cmdline
coherent_pool=1M 8250.nr_uarts=1 pci=pcie_bus_safe snd_bcm2835.enable_compat_alsa=0 snd_bcm2835.enable_hdmi=1 smsc95xx.macaddr=D8:3A:DD:A8:28:CE vc_mem.mem_base=0x3fc00000
vc_mem.mem_size=0x40000000 console=ttyAMA10,115200 console=tty1 root=PARTUUID=8fc0304d-02 rootfstype=ext4 fsck.repair=yes rootwait
cfg80211.ieee80211_regdom=IT quiet splash plymouth.ignore-serial-consoles video=HDMI-A-1:1920x1080@60

results:
for CEA TV I obtain no video (black screen), instead on DMT Monitor works (there is no difference between M and m parameters with or without M and m (the DMT Monitor works),
instead the CEA TV is always black screen (no signal)

Test 1
I have also tried in /boot/config.txt

hdmi_force_hotplug=1
hdmi_ignore_edid=0xa5000080
hdmi_group=1
hdmi_mode=16

(on pi5 for CEA TV black screen, instead monitor works), but if I set this parameters on pi4 TV works at 1920x1080p 60hz(it's normal), and Monitor is black (it's normal)

---

Test 2
I have also tried in /boot/config.txt

hdmi_force_hotplug=1
hdmi_ignore_edid=0xa5000080
hdmi_group=2
hdmi_mode=82

(on pi5 for CEA TV black screen, instead monitor works), but if I set this on pi4: TV is black (it's normal), and Monitor works at 1920x1080p 60hz (it's normal)

---

Test 3
I have also tried in /boot/config.txt

hdmi_force_hotplug=1
hdmi_ignore_edid=0xa5000080
hdmi_group=2
hdmi_mode=87
hdmi_cvt=1920 1080 60 3 0 0 0

(on pi5 for tv nothing, instead monitor works), but if I set this on pi4 TV is black (it's normal), and Monitor is black (it's normal), instead LCD Display on HDMI works at 1920x1080p 60hz (it's normal)

so all the test on Raspberry PI5 to connect a CEA TV at 1920x1080p 60hz has failed ...
instead on PI4 everything works very well: with CEA, DMT, and LCD at 1920x1080p 60hz...

[mitu]

@giandeejay said in pi5 CEA 1920x1080P impossibile to set:

I have tested 2 possible configuration in /boot/cmdline.txt on PI5:

video=HDMI-A-1:1920x1080M@60m
video=HDMI-A-1:1920x1080@60

It's actually /boot/firmware/cmdline.txt - the location in Bookworm has changed. But there's a symlink in /boot so I guess editing still applied to the correct file.

Try ading:

video=HDMI-A-1:1920x1080@60D

and see if that changes anything. Also post the result of executing kmsprint -m from SSH.

I have also tried in /boot/config.txt.....

All options regarding the resolution for HDMI/other display connectors are no longer read from /boot/firmware/config.txt in Bookworm, there's no point in adding any of them.

[giandeejay]

@mitu I FOUND THE PROBLEM !!!! AND NOW TV CEA GOES !!!

Not Working:
/boot/config.txt
config_hdmi_boost=4

Solution:
I have ONLY commented #config_hdmi_boost=4,
and now works on TV CEA at 1920x1080p 60hz !

Working config.txt and cmdline.txt for CEA TV 1920x1080p 60hz:
/boot/config.txt
#config_hdmi_boost=4 #you don't need this active or boost anymore, because modern HDMI cables has much more capabilities
hdmi_force_hotplug=1
hdmi_ignore_edid=0xa5000080
hdmi_group=1
hdmi_mode=16

/boot/cmdline.txt
video=HDMI-A-1:1920x1080@60D

[Ashpool]

@giandeejay said in pi5 CEA 1920x1080P impossibile to set:

hdmi_boost=4

(puzzles me, 'cause:) that shouldn't be parsed on bookworm(/kms enabled Raspberries)
a) because it would be (see b) a legacy_parameter (none of them belongs into the config.txt, as mitu has said multiple times) ... and ...
b) even in a legacy_config.txt situation it is not a valid parameter (the correct one would be config_hdmi_boost)

[giandeejay]

@Ashpool

Sorry,
Look now the precedent post, where I applied the fix to the code...
Sometimes "copy & paste" the correct code, from my smartphone is not so simple...
I mean disable:
#config_hdmi_boost=4

This is the solution...

[mitu]

@giandeejay said in pi5 CEA 1920x1080P impossibile to set:

I mean disable:
#config_hdmi_boost=4

This option is not in the default config.txt distributed by RaspiOS - how did it get there ?

[giandeejay]

@mitu from other Retropie user (since Retropie 4.3)...
also this option is not standard

hdmi_ignore_edid=0xa5000080

but very useful for thousand users

And:
video=HDMI-A-1:1920x1080@60D

where D, is equal to:
hdmi_force_hotplug=1
hdmi_drive=2

[mitu]

@giandeejay said in pi5 CEA 1920x1080P impossibile to set:

@mitu from other Retropie user (since Retropie 4.3)...

Which RetroPie user ? This is not even enabled on older RaspiOS and you're not supposed to copy/paste old configs - they're not forward compatible.

also this option is not standard

hdmi_ignore_edid=0xa5000080

but very useful for thousand users

It should only be used in certain cases (display EDID is not correct) and not plastered indescriminately in configuration files. Same for other configuration options.
I'm starting to believe that your issue is because you copied over the older config.txt , when you shouldn't have changed anything from the default RaspiOS configurations.

[giandeejay]

@mitu No, the problem is that Wayland, changes things without an explanation...

If a user, is informed about config.txt file to configure everything "until yesterday",
and now cmdline.txt replace or introduce new parameters, similar to parameters in config.txt, but different in syntax, some people like me, ​can fall into the trap...

for example: video=HDMI-A-1:1920x1080@60D

where D, is equal to:
hdmi_force_hotplug=1
hdmi_drive=2
and the rest of the command is similar to:
hdmi_group:0=1
hdmi_mode:0=16

This Guide is not updated
https://www.raspberrypi.com/documentation/computers/config_txt.html

Another exapmple is:
dtoverlay=vc4-kms-v3d

But PI5 can use:
dtoverlay=vc4-kms-v3d-pi5

What the difference ?

[mitu]

@giandeejay said in pi5 CEA 1920x1080P impossibile to set:

@mitu No, the problem is that Wayland, changes things without an explanation...

I don't see how that's relevant for RetroPie, but these changes have been detailed in the Bookworm announcement(s) and the documentation published by the RPI folks.

.. and now cmdline.txt replace or introduce new parameters, similar to parameters in config.txt, but different in syntax, some people like me, ​can fall into the trap...

Yes, things change sometimes, but these changes are documented in the Raspberry PI documentation and in the announcements. In fact, these 'new' parameters have existed for quite some time and have been the standard way in Linux to configure the video display - the RPI folks are just aligning with the Linux standard way.

[giandeejay]

@mitu For Example:
This Guide is not updated
https://www.raspberrypi.com/documentation/computers/config_txt.html

Another example is:
dtoverlay=vc4-kms-v3d

But PI5 can use:
dtoverlay=vc4-kms-v3d-pi5

What the difference ?
Things changes , but where is the advice ?

[mitu]

@giandeejay said in pi5 CEA 1920x1080P impossibile to set:

@mitu For Example:
This Guide is not updated
https://www.raspberrypi.com/documentation/computers/config_txt.html

Yes, it is. See: https://www.raspberrypi.com/documentation/computers/config_txt.html#video-options (emph. mine):

The HDMI settings used to be configured by firmware via settings in config.txt; this configuration is now instead done by KMS via settings in cmdline.txt.

Another example is:
dtoverlay=vc4-kms-v3d

But PI5 can use:
dtoverlay=vc4-kms-v3d-pi5

What the difference ?

I don't know - but you can probably find out by reading the overlay help file from the kernel sources. I don't think this is something that end users need to configure though.

[giandeejay]

@mitu no... I know the response ...
there is no difference... for now...

but many people ask...
https://forums.raspberrypi.com/viewtopic.php?t=361001

[mitu]

Sorry, but I don't see the point you want to make here. If you think the documentation on the RPI side needs to be improved - then you can suggest things to the RPI folks. I found about most of these changes from their documentation and their posts and I don't think the documentation deliberately obscures the information.

but many people ask...
https://forums.raspberrypi.com/viewtopic.php?t=361001

I see 1 user, which happens to be the maintainer of the Arch Linux kernel packages - so not quite a regular user - and their question was addressed by the RPI folks. Hardly 'many people' and not something that users are interested anyway.

[giandeejay]

@mitu another discovery for me of last few hours

Now that I know i must modify cmdline.txt (and instructions gaved are all clear) on PI5:

My Pink TV 24" (buyed for 20 euros in earlier 2016) and always declared (by tvservice command) and used with Retropie on pi3 on pi3b+ and pi4 at 1920x1080p 60hz 16:9, now on pi5 runs in 1920x1200 60hz 16:10 (preferred mode)
This is very strange, but true...

[giandeejay]

@mitu in these days I tried to change my Pink TV resolution and aspect ratio (in the origins perfectly working at 1920x1080p 16:9 60hz on pi4), but now, on pi5, seeems impossible to do, to set this 1920x1080p , the only working resolution possible on pi5 is 1920x1200M@60D (16:10)
Any other resolution on pi5 , always in /boot/firmware/cmdline.txt is rejected by TV (No signal)...
And when I start emulationstation in 1920x1080p, in blind mode (blue TV screen), if I press after 1 minute , F4 (to quit blind emulationstation) and I type : wayfire (wayland launch command) correctly start but in 1920x1200p)...
..so I think that wayland ignore 1920x1080p, and re-set my TV at 1920x1200p ...even if in cmdline.txt is setted on 1920x1080p...
Any Idea?

[mitu]

Run kmsprint -m and post the output. What resolution is chosen if you don't force one in cmdline.txt ?