pi5 CEA 1920x1080P impossibile to set
-
@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) -
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=4This is the solution...
-
@giandeejay said in pi5 CEA 1920x1080P impossibile to set:
I mean disable:
#config_hdmi_boost=4This option is not in the default
config.txtdistributed by RaspiOS - how did it get there ? -
@mitu from other Retropie user (since Retropie 4.3)...
also this option is not standardhdmi_ignore_edid=0xa5000080
but very useful for thousand users
And:
video=HDMI-A-1:1920x1080@60Dwhere D, is equal to:
hdmi_force_hotplug=1
hdmi_drive=2 -
@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 olderconfig.txt, when you shouldn't have changed anything from the default RaspiOS configurations. -
@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=16This Guide is not updated
https://www.raspberrypi.com/documentation/computers/config_txt.htmlAnother exapmple is:
dtoverlay=vc4-kms-v3dBut PI5 can use:
dtoverlay=vc4-kms-v3d-pi5What the difference ?
-
@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.
-
@mitu For Example:
This Guide is not updated
https://www.raspberrypi.com/documentation/computers/config_txt.htmlAnother example is:
dtoverlay=vc4-kms-v3dBut PI5 can use:
dtoverlay=vc4-kms-v3d-pi5What the difference ?
Things changes , but where is the advice ? -
@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.htmlYes, 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-v3dBut PI5 can use:
dtoverlay=vc4-kms-v3d-pi5What 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.
-
@mitu no... I know the response ...
there is no difference... for now...but many people ask...
https://forums.raspberrypi.com/viewtopic.php?t=361001 -
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=361001I 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.
-
@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... -
@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? -
Run
kmsprint -mand post the output. What resolution is chosen if you don't force one incmdline.txt? -
@mitu said in pi5 CEA 1920x1080P impossibile to set:
Run
kmsprint -mand post the output. What resolution is chosen if you don't force one incmdline.txt?Hi MITU,
Maybe i have found a solution for my TV CEAMy GOAL is to set 1920x1080p 60hz on pi5 cmdline.txt (but nothing of written before can do it working, always blue screen on TV and out of range)
But maybe i found a real solution:
Is very hard to find an online updated guide for cmdline.txt for PI5 attached to a TV CEA (like mine) , because most users use DMT Monitor, not a TV...
The real problem is because my TV can support various Hdmi mode (maximum value is 1920x1200p, but my tv can support also 1920x1080i and 1920x1080p)And my GOAL is to force 1920x1080p 60hz (not 1920x1200p)
When I start raspberry pi5 with raspberry pi os (without wayland desktop support)
useful for me to install (next) Retropie, for a manual setup...Kms kernel video detect my TV CEA and set the best possible supported resolution at 1920x1200@60hz.
And if I force in cmdline.txt
1920x1080@60D
My TV responds: Signal out of range.So only 1920x1200p works on TV, But this resolution is not the best resolution for me (and for Retropie)
Solution:
So in these days, I found randomly online , beacause there is no a definitive and exhaustive guide on how to set a custom resolution, for pi5 with a TV CEA, instead of DMT Monitors.
So i'm very confused reading general raspberry pi's online guide ..
Because are generic too, not specific for a single model of raspberry pi..
I have to force 1920x1080p 60hz on a PI5 (not 4, not 3b+, not cm4, not zero, pico and so on...
So maybe in
cmdline.txt i have to add 2 parameters instead of 1 (valid for all CEA TV)video=HDMI-I-1:1920x1080@60De video=TV-1:D
I hope that second parameters can set cortectly the CEA mode.
Instead of use (valid only for DMT, but not for a CEA TV)
video=HDMI-I-1:1920x1080@60DCan you confirm that also:
video=TV-1:D ...in addition (like previous example) is a good set for TV CEA on PI5 hdmi port 0 ? -
@giandeejay said in pi5 CEA 1920x1080P impossibile to set:
video=TV-1:D ...in addition (like previous example) is a good set for TV CEA on PI5 hdmi port 0 ?
No, I haven't heard of such connector type.
-
@mitu said in pi5 CEA 1920x1080P impossibile to set:
@giandeejay said in pi5 CEA 1920x1080P impossibile to set:
video=TV-1:D ...in addition (like previous example) is a good set for TV CEA on PI5 hdmi port 0 ?
No, I haven't heard of such connector type.
Ok infact was a test
Nothing happens...
My problem with 1920x1080p 60hz on CEA TV still unsolved...I have also tried to modify under .config/wayfire.ini the resolution but there is something of strange, 1920x1080P is accepted by wayland desktop but if I use lxrandr.desktop program I cannot modify the resolution , when I apply any change before saving the resolution still remain 1920x1200 instead of 1920x1080..
And if i start from terminal emulationstation -- resolution 1920 1080
I obtain always a bluescreen TV out of range.So I think there are too much resolution manager program that cause my problem during pi5 boot.
-
@mitu Hi Mitu , on some forum and documentation online, I saw something of unexplained (not clear) on how the new Pi OS Bookworm works:
if I change resolution in /boot/firmware/cmdline.txt I expect that this resolution work as well in terminal and in desktop... but it's not so simple as I think:
Bookworm Graphic Desktop (Wayland / Wayfire) has much more than one file to change the Graphic Resolution, another file is for example the /home/<user>/.config/wayfire.ini
Instead I think that Retropie 4.8.6 works on "terminal resolution" instead of Desktop resolution like Wayland, so the "user mistmatch" is behind the corner...
So probably if I try to get Retropie working at 1920x1080p 60hz on my Raspberry Pi5 (like I correctly work on my pi4, but where on my pi4 only by changing 2 parameters Retropie 4.8.6 change correctly the two resolutions in Terminal + in Desktop) using in /boot/config.txt:
hdmi_group=1
hdmi_mode=16with the same TV , Retropie 4.8.6 on pi4 works correctly in 1920x1080 60hz (16:9)
Instead on PI5, with: video=HDMI-A-1:1920x1080@60D , in cmdline.txt ,
Retropie 4.8.6 after few seconds, of listing boot text lines, immediatly make my TV OUT OF RANGE, in Blue Screen, but if I wait some seconds (the loading of emulationstation) and if I press (blind) F4 and if I type wayfire command, wayland desktop immediatly starts correctly but in 1920x1200...If I use LXRANDR or XRANDR program it says that my HDMI (0) Device is called Xwayland0:
Instead If i set:
on PI5, with: video=HDMI-A-1:1920x1200@60D , in cmdline.txt ,
Retropie 4.8.6 after few seconds, of listing boot text lines, next appear correctly the Emulationstation Loading, but at 1920x1200 at 60hz, so in this resolution i can see also the 2 delimiters lines up and down the Emulationstation Screen (Systems Select) "--------------------------------"
like a zoom out... or too much overscan borders (but overscan is set to off).Instead:
If I delete the "video=HDMI-A-1:1920x1200@60D" , in cmdline.txt , I obtain Blue Screen on TV, so i think that the "kms-v3d" driver cannot recognise correctly the resolution of my TV... during boot...So if I take a look of Retropie on Pi4 connected to the same TV it says 1920x1080 @59.88 hz
Tomorrow if i have time i will post the: kmsprint -m results:
for now every time I watch this command, the result is:
1920x1200*,
and many other resolution like 1280x960, 1024x768 are listed like 1920x1080,
but I don't know how to set...I hope this can help you, to help me...
-
@giandeejay said in pi5 CEA 1920x1080P impossibile to set:
@mitu Hi Mitu , on some forum and documentation online, I saw something of unexplained (not clear) on how the new Pi OS Bookworm works:
if I change resolution in /boot/firmware/cmdline.txt I expect that this resolution work as well in terminal and in desktop... but it's not so simple as I think:
Bookworm Graphic Desktop (Wayland / Wayfire) has much more than one file to change the Graphic Resolution, another file is for example the /home/<user>/.config/wayfire.ini
Instead I think that Retropie 4.8.6 works on "terminal resolution" instead of Desktop resolution like Wayland, so the "user mistmatch" is behind the corner...
So probably if I try to get Retropie working at 1920x1080p 60hz on my Raspberry Pi5 (like I correctly work on my pi4, but where on my pi4 only by changing 2 parameters Retropie 4.8.6 change correctly the two resolutions in Terminal + in Desktop) using in /boot/config.txt:
hdmi_group=1
hdmi_mode=16with the same TV , Retropie 4.8.6 on pi4 works correctly in 1920x1080 60hz (16:9)
Instead on PI5, with: video=HDMI-A-1:1920x1080@60D , in cmdline.txt ,
Retropie 4.8.6 after few seconds, of listing boot text lines, immediatly make my TV OUT OF RANGE, in Blue Screen, but if I wait some seconds (the loading of emulationstation) and if I press (blind) F4 and if I type wayfire command, wayland desktop immediatly starts correctly but in 1920x1200...If I use LXRANDR or XRANDR program it says that my HDMI (0) Device is called Xwayland0:
Instead If i set:
on PI5, with: video=HDMI-A-1:1920x1200@60D , in cmdline.txt ,
Retropie 4.8.6 after few seconds, of listing boot text lines, next appear correctly the Emulationstation Loading, but at 1920x1200 at 60hz, so in this resolution i can see also the 2 delimiters lines up and down the Emulationstation Screen (Systems Select) "--------------------------------"
like a zoom out... or too much overscan borders (but overscan is set to off).Instead:
If I delete the "video=HDMI-A-1:1920x1200@60D" , in cmdline.txt , I obtain Blue Screen on TV, so i think that the "kms-v3d" driver cannot recognise correctly the resolution of my TV... during boot...So if I take a look of Retropie on Pi4 connected to the same TV it says 1920x1080 @59.88 hz
Tomorrow if i have time i will post the: kmsprint -m results:
for now every time I watch this command, the result is:
1920x1200*,
and many other resolution like 1280x960, 1024x768 are listed like 1920x1080,
but I don't know how to set...I hope this can help you, to help me...
HI MITU ,
there something going strange .......On my pi5 and my TV 1920x1080p, with retropie 4.8.6:
If I set in /boot/firmware/cmdline.txt
this line:
video=HDMI-A-1:1920x1200@60DTV starts in 1920x1200, and boot correctly in CLI, so Emulationstation starts,
so If I next press F4 to go in CLI, and If I also modify
/home/pi/.config/wayfire.iniand set something like this in the file:
[HDMI-A-1]
video=1920x1080and next I type:
wayfireWayland Desktop starts correctly in 1920x1080p !!!!
So I dont' know why, if i boot directly in CLI (to start Emulationstation) with this parameters in /boot/firmware/cmdline.txt
video=HDMI-A-1:1920x1080@60Dimmediatly for 2 seconds I can see (correctly) some text booting line, but
when Emulationstation is booting after 1 second, the signal of TV goes "OUT OF RANGE".So My TV supports 1920x1080p 60hz and 1920x1200p 60hz,
but when Emulationstation starts only this 1920x1200p 60hz works........Instead Wayland (and TV) can support every resolution 1080p and 1200p, and so on.
-
Can you please post the output of the command I asked in my last reply ?
Contributions to the project are always appreciated, so if you would like to support us with a donation you can do so here.
Hosting provided by Mythic-Beasts. See the Hosting Information page for more information.