HiFiBerryOs 64 - Alpha 5 - HDMI Display resolution is not recognized

[diytim]

DO NOT remove the blocks below, but fill these with the requested data. Incomplete bug reports will be ignored! You should remove this comment before posting the bug report.

Describe the bug HDMI 7" Touch Display works but full resolution is not used. HiFiBerry GUI is shown in the right upper corner. Only about 1/2 of screen is used. In config.txt 'disable_overscan=1' or '# disable_overscan=1' does not change anything.

HiFiBerryOS version 20240116 (OS 64 Alpha 4)

HiFiBerry sound card DAC2 HD

To Reproduce Steps to reproduce the behavior:

Go to '...'
Click on '....'
Scroll down to '....'
See error

Expected behavior HiFiBerry GUI should be shown in full resoltion

Screenshots If applicable, add screenshots to help explain your problem.

Browser (if applicable)

OS: [e.g. iOS]
Browser [e.g. chrome, safari]
Version [e.g. 22]

Additional context HiFiBerry system information: Raspberry PI 4 Model B, Rev. 1.5 aplay 1 card 0 sndrpihifiberry [snd_rpi_hifiberry_dacplushd] aplay 2 device 0 HiFiBerry DAC+ HD HiFi pcm179x-hifi-0 [HiFiBerry DAC+ HD HiFi pcm179x-hifi-0 ] Mixer DAC Features pi localui bluetooth pi3orlater arm7 arm8 64bit Power controller not detected Linux version Linux hifiberry 6.1.72-v8 #1 SMP PREEMPT Tue Jan 16 13:34:44 UTC 2024 aarch64 GNU/Linux Date and time Sat Jan 20 12:43:42 UTC 2024 etho 192.168.17.50 /data mounted OK /dev/dri/card0 OK BT devices hci0 - WIFI devices wlan0 audiocontrol2 running beocreate2 running bluetooth not running bluealsa not running bluealsa-aplay not running dlnampris not running mpd running pigpio running raat not running shairport-sync running sigmatcp running snapcastempris not running spotify running squeezelite not running sshd running ympd running weston running cog running

[diytim]

Maybe this journalctl -f output helps:

Feb 01 16:37:55 hifiberry dockerd[1187]: time="2024-02-01T16:37:55.131613448+01:00" level=info msg="Loading containers: done." Feb 01 16:37:55 hifiberry node[766]: Requesting 'albums' (in context '[object Object]') from 'mpd'... Feb 01 16:37:55 hifiberry dockerd[1187]: time="2024-02-01T16:37:55.383184647+01:00" level=warning msg="failed to find docker-init: exec: \"docker-init\": executable file not found in $PATH" Feb 01 16:37:55 hifiberry systemd[1]: var-lib-docker-overlay2-opaque\x2dbug\x2dcheck2319196210-merged.mount: Deactivated successfully. Feb 01 16:37:55 hifiberry dockerd[1187]: time="2024-02-01T16:37:55.427017208+01:00" level=warning msg="WARNING: No memory limit support" Feb 01 16:37:55 hifiberry dockerd[1187]: time="2024-02-01T16:37:55.427282240+01:00" level=warning msg="WARNING: No swap limit support" Feb 01 16:37:55 hifiberry dockerd[1187]: time="2024-02-01T16:37:55.427415126+01:00" level=info msg="Docker daemon" commit=buildroot graphdriver=overlay2 version=24.0.7 Feb 01 16:37:55 hifiberry dockerd[1187]: time="2024-02-01T16:37:55.431306273+01:00" level=info msg="Daemon has completed initialization" Feb 01 16:37:55 hifiberry systemd[1]: Started Docker Application Container Engine. Feb 01 16:37:55 hifiberry systemd[1]: Startup finished in 1.956s (kernel) + 2min 5.488s (userspace) = 2min 7.445s. Feb 01 16:37:55 hifiberry dockerd[1187]: time="2024-02-01T16:37:55.621965907+01:00" level=info msg="API listen on /run/docker.sock" Feb 01 16:37:57 hifiberry vollibrespot[743]: [Vollibrespot] : couldn't parse packet from 192.168.17.50:5353: type 47 is invalid Feb 01 16:37:59 hifiberry raat_app[698]: [0000070] [t548345727872] 109.919 TRACE Network Status Changed. Refreshing Discovery Feb 01 16:37:59 hifiberry raat_app[698]: [0000071] [t548345727872] 109.919 TRACE [discovery] stopping Feb 01 16:37:59 hifiberry raat_app[698]: [0000072] [t548345727872] 109.919 TRACE closing multicast Feb 01 16:37:59 hifiberry raat_app[698]: [0000073] [t548345727872] 109.919 TRACE [discovery] closing unicast send socket Feb 01 16:37:59 hifiberry raat_app[698]: [0000074] [t548345727872] 109.919 TRACE [discovery] closing unicast recv socket Feb 01 16:37:59 hifiberry raat_app[698]: [0000075] [t548345727872] 109.919 TRACE [discovery] starting Feb 01 16:37:59 hifiberry raat_app[698]: [0000076] [t548345727872] 109.920 INFO [discovery] [iface:127.0.0.1] multicast recv socket is bound to 0.0.0.0:9003 Feb 01 16:37:59 hifiberry raat_app[698]: [0000077] [t548345727872] 109.920 INFO [discovery] [iface:127.0.0.1] multicast send socket is bound to 0.0.0.0:32816 Feb 01 16:37:59 hifiberry raat_app[698]: [0000078] [t548345727872] 109.920 INFO [discovery] [iface:192.168.17.50] multicast recv socket is bound to 0.0.0.0:9003 Feb 01 16:37:59 hifiberry raat_app[698]: [0000079] [t548345727872] 109.920 INFO [discovery] [iface:192.168.17.50] multicast send socket is bound to 0.0.0.0:39363 Feb 01 16:37:59 hifiberry raat_app[698]: [0000080] [t548345727872] 109.920 INFO [discovery] unicast socket is bound to 0.0.0.0:9003 Feb 01 16:37:59 hifiberry raat_app[698]: [0000081] [t548345727872] 109.920 TRACE [device] announcing DiscoveryMessage[type=QUERY, transactionid=01878C8D-C8A2-07AA-0355-88AD0CD92B03, Data={ "unique_id": "efcbb0c5-e928-4540-9276-1f0edc81a2cb", "raat_version": "1.1.39", "vendor": "HiFiBerry", "protocol_version": "3", "model": "DAC+", "version": "20240124", "service_id": "5e2042ad-9bc5-4508-be92-ff68f19bdc93", "tcp_port": "34119", } ] Feb 01 16:37:59 hifiberry raat_app[698]: [0000082] [t548345727872] 109.943 DEBUG [discovery] broadcast op is complete Feb 01 16:38:20 hifiberry node[766]: Checking MPD database update status...

[hifiberry]

Not really. The whole graphics stack is not really easy to compile and configure at all. This will probably one of the last things that we can fix.

[diytim]

Does it make sense to test video paramters in config.txt like described here:

https://elinux.org/RPiconfig#Video_mode_options

Regards,

Tim Mager

Von: HiFiBerry @.*** Gesendet: Donnerstag, 1. Februar 2024 16:54 An: hifiberry/hifiberry-os Cc: diytim; Author Betreff: Re: [hifiberry/hifiberry-os] HiFiBerryOs 64 - Alpha 5 - HDMI Display resolution is not recognized (Issue #508)

Not really. The whole graphics stack is not really easy to compile and configure at all. This will probably one of the last things that we can fix.

- Reply to this email directly, view it on GitHub https://github.com/hifiberry/hifiberry-os/issues/508#issuecomment-192164395 6 , or unsubscribe https://github.com/notifications/unsubscribe-auth/BE6OWWHB75P3ZNO6BWYO4MLYR O3CPAVCNFSM6AAAAABCMYVP5KVHI2DSMVQWIX3LMV43OSLTON2WKQ3PNVWWK3TUHMYTSMRRGY2DG OJVGY . You are receiving this because you authored the thread. https://github.com/notifications/beacon/BE6OWWFFOWST5OHLVGS6ONTYRO3CPA5CNFS M6AAAAABCMYVP5KWGG33NNVSW45C7OR4XAZNMJFZXG5LFINXW23LFNZ2KUY3PNVWWK3TUL5UWJTT SRH23I.gif Message ID: @.***>

[hifiberry]

Feel free to try, I can't say if this might help.

[diytim]

Thanks.I´ll give you feedback.

Von: HiFiBerry @.*** Gesendet: Freitag, 2. Februar 2024 08:52 An: hifiberry/hifiberry-os Cc: diytim; Author Betreff: Re: [hifiberry/hifiberry-os] HiFiBerryOs 64 - Alpha 5 - HDMI Display resolution is not recognized (Issue #508)

Feel free to try, I can't say if this might help.

— Reply to this email directly, view it on GitHub https://github.com/hifiberry/hifiberry-os/issues/508#issuecomment-192326416 6 , or unsubscribe https://github.com/notifications/unsubscribe-auth/BE6OWWAPQTG467JC2NATYB3YR SLKZAVCNFSM6AAAAABCMYVP5KVHI2DSMVQWIX3LMV43OSLTON2WKQ3PNVWWK3TUHMYTSMRTGI3DI MJWGY . You are receiving this because you authored the thread. https://github.com/notifications/beacon/BE6OWWHKMPRV2T3TWYK6OCDYRSLKZA5CNFS M6AAAAABCMYVP5KWGG33NNVSW45C7OR4XAZNMJFZXG5LFINXW23LFNZ2KUY3PNVWWK3TUL5UWJTT SUKXKM.gif Message ID: @.***>

[diytim]

Here is my possible solution for configuring individual connected displays:

1. ssh to your hifiberry
2. type mount -o remount,rw /boot to make /boot/config.txt writeable Add the following lines to /boot/config.txt I used WINSCP (ssh with GUI for Windows Users)

# Userdefined HDMI mode, resolution
# hdmi_cvt=<width> <height> <framerate> <aspect> <margins> <interlace> <rb>
# width        width in pixels
# height       height in pixels
# framerate    framerate in Hz
# aspect       aspect ratio 1=4:3, 2=14:9, 3=16:9, 4=5:4, 5=16:10, 6=15:9
# margins    0=margins disabled, 1=margins enabled
# interlace    0=progressive, 1=interlaced
# rb             0=normal, 1=reduced blanking
# hdmi_group=2 means DMT (Display Monitor Timings; the standard typically used by monitors)
# hdmi_mode=87 indicates the userdefined resolution. This is the first mode after official modes (1 to 86)
# hdmi_drive=2 selects the Normal HDMI mode (with sound over hdmi cable)
# Source: http://wiki.sunfounder.cc/index.php?title=Adjust_Resolution_for_Raspberry_Pi

# example: HDMI display with resolution of 1026 x 600, ratio 16:9, margins disabled, interlace progressive, reduced blanking
hdmi_cvt=1024 600 60 3 0 0 1
hdmi_group=2
hdmi_mode=87
hdmi_drive=2

Reboot Hope that helps ...

[diytim]

Raspberry Pi 5 workaround:

1. ssh to your hifiberry type mount -o remount,rw /boot to make /boot/config.txt writeable

2. Copy /lib/firmware/rpi/overlays/vc4-kms-v3d-pi5.dtbo to /boot/overlays/vc4-kms-v3d-pi5.dtbo

3. Edit /boot/config.txt Replace at the end (depending on your previous Raspberry Pi) dtoverlay=vc4-fkms-v3d-pi4,audio=off with dtoverlay=vc4-kms-v3d-pi5,audio=off

[user10072023github]

@diytim did your message here back on Feb 10th fix your issue fully when using these 64 alphas? I followed your instructions editing config.txt according to my screen, so: hdmi_cvt=1920 1080 60 3 0 0 0 hdmi_group=2 #dvt screen hdmi_mode=82 #monitor is 1920x1080p hdmi_drive=1 #dont need/want sound

I've had no luck on my end...

[diytim]

Hi user10072023github,

the I needed workaround only for alpha 5 and it worked for me. Meanwhile with latest alpha´s and RaspBerry Pi 5 it works without changing anything in config.txt.

Attached you´ll find HDMI troubleshooting PDF. Hope that helps.

Regards,

Tim

Von: user10072023github @.*** Gesendet: Donnerstag, 12. September 2024 03:54 An: hifiberry/hifiberry-os Cc: diytim; Mention Betreff: Re: [hifiberry/hifiberry-os] HiFiBerryOs 64 - Alpha 5 - HDMI Display resolution is not recognized (Issue #508)

@diytim https://github.com/diytim did your message here back on Feb 10th fix your issue fully when using these 64 alphas? I followed your instructions editing config.txt according to my screen, so: hdmi_cvt=1920 1080 60 3 0 0 0 hdmi_group=2 #dvt screen hdmi_mode=82 #monitor is 1920x1080p hdmi_drive=1 #dont need/want sound

I've had no luck on my end...

— Reply to this email directly, view it on GitHub https://github.com/hifiberry/hifiberry-os/issues/508#issuecomment-2345096937 , or unsubscribe https://github.com/notifications/unsubscribe-auth/BE6OWWHYN52NEZH443LKHXDZWDX4BAVCNFSM6AAAAABCMYVP5KVHI2DSMVQWIX3LMV43OSLTON2WKQ3PNVWWK3TUHMZDGNBVGA4TMOJTG4 . You are receiving this because you were mentioned. https://github.com/notifications/beacon/BE6OWWENCY6E67OPPVMPJETZWDX4BA5CNFSM6AAAAABCMYVP5KWGG33NNVSW45C7OR4XAZNMJFZXG5LFINXW23LFNZ2KUY3PNVWWK3TUL5UWJTULY5LOS.gif Message ID: @.***>

[user10072023github]

@diytim Response greatly appreciated! Sadly no attachment you mentioned came through. I think that sadly this fix won't work for me anyway because I have a "Waveshare" 13in screen from pishop.us and not the official 7in screen. Sigh, still stuck.

[diytim]

Sorry, I didn´t know that attachments are not allowed.

Here´s the link to the troubleshooting file:

https://pip.raspberrypi.com/categories/685-whitepapers-app-notes/documents/RP-004341-WP/Troubleshooting-KMS-HDMI-output.pdf

Regards,

Tim

Von: user10072023github @.*** Gesendet: Freitag, 13. September 2024 01:28 An: hifiberry/hifiberry-os Cc: diytim; Mention Betreff: Re: [hifiberry/hifiberry-os] HiFiBerryOs 64 - Alpha 5 - HDMI Display resolution is not recognized (Issue #508)

@diytim https://github.com/diytim Response greatly appreciated! Sadly no attachment you mentioned came through. I think that sadly this fix won't work for me anyway because I have a "Waveshare" 13in screen from pishop.us and not the official 7in screen. Sigh, still stuck.

— Reply to this email directly, view it on GitHub https://github.com/hifiberry/hifiberry-os/issues/508#issuecomment-2347405573 , or unsubscribe https://github.com/notifications/unsubscribe-auth/BE6OWWDW672URHHBRKK2S7LZWIPRVAVCNFSM6AAAAABCMYVP5KVHI2DSMVQWIX3LMV43OSLTON2WKQ3PNVWWK3TUHMZDGNBXGQYDKNJXGM . You are receiving this because you were mentioned. https://github.com/notifications/beacon/BE6OWWHANI4CWZL3HWY2TJ3ZWIPRVA5CNFSM6AAAAABCMYVP5KWGG33NNVSW45C7OR4XAZNMJFZXG5LFINXW23LFNZ2KUY3PNVWWK3TUL5UWJTUL5KIQK.gif Message ID: @.***>

[user10072023github]

@diytim Thank you for the link! Unfortunately, this didn't help my issue since I have a different screen but hey I appreciate your time none-the-less