Display/wifi/account/plugins problem

To summarize, or get a clear understanding:

  • Rpi4 + External monitor works (WiFI+Audio+Screen => OK)
  • Rpi4 + External monitor + adding info to userconfig.txt (screen + Audio => NOT OK, WiFi => OK)
  • rPi4 + Chinese display + adding info to userconfig.txt (screen + Audio => NOT OK, WiFi => OK)

Monitor, lcd = same problems WITH info in userconfig

I would be surprised if this would work with audio taking that CEC is overridden with 7" HDMI screen parameters. This is expected behaviour and there is no point spending time on it.

Let’s focus on this one only without Touch Plugin installed first.

Kind Regards,

Hey @Grg,

Whilst looking into the official Raspberry Pi video documentation here: raspberrypi_documentation/configuration/config-txt/video.md at master · tback/raspberrypi_documentation · GitHub
I have doubts regarding validity of some parameter value.


hdmi_drive

The hdmi_drive command allows you to choose between HDMI and DVI output modes.

hdmi_drive result
1 Normal DVI mode (no sound)
2 Normal HDMI mode (sound will be sent if supported and enabled)

As such, we use hdmi_drive=2 (normal HDMI mode), however Aliexpress link shows use of hdmi_drive=1


config_hdmi_boost

Configures the signal strength of the HDMI interface. The default value is 0 and the maximum is 11.

The default value for the original Model B and A is 2. The default value for the Model B+ and all later models is 5.

If you are seeing HDMI issues (speckling, interference) then try 7. Very long HDMI cables may need up to 11, but values this high should not be used unless absolutely necessary.

Aliexpress link shows use of config_hdmi_boost=7


hdmi_force_edid_audio

Setting hdmi_force_edid_audio to 1 pretends that all audio formats are supported by the display, allowing passthrough of DTS/AC3 even when this is not reported as supported.

Perhaps we should include.


TEST

Update your /boot/userconfig.txt as follows (comment out or remove everything else):

dtoverlay=vc4-kms-v3d

hdmi_group=2
hdmi_mode=87
hdmi_cvt 1024 600 60 6 0 0 0
display_rotate=0
hdmi_drive=2
config_hdmi_boost=7
hdmi_force_edid_audio=1

Kind Regards,

hello guys again.

I did both activities that You suggest:

  1. Touch display plugin reainstallation - no effects. - video stops after half minute, no audio

  2. new userconfig.txt vales - like in the post42 by nerd - no effects - video stops after 30seconds, no audio.

Without entries everything works :slight_smile:

Just a (stupid?) question… Did you disable screen saver in the plugin settings, something like no screen saver while playing?

Yes it is turned off

Erm… What is it that we are troubleshooting here then?

:slight_smile:

Because resolution is not right, vision is not filling the display completely, touchscreen does not match with the screen?

@gvolt - perhaps you can chip in with your expertise here.

Kind Regards,

Please post the output of

cat /boot/userconfig.txt

I assume that you have not changed “/boot/config.txt” and “/boot/volumioconfig.txt”. However, if this is the case, undo your changes.

#settings put by the user:

dtoverlay=vc4-kms-v3d

hdmi_group=2
hdmi_mode=87
hdmi_cvt 1024 600 60 6 0 0 0
display_rotate=0
hdmi_drive=2
config_hdmi_boost=7
hdmi_force_edid_audio=1

I did not put any changes in other files.

Did you already try without dtoverlay=vc4-kms-v3d?

After removing such line, screen doesn`t stop!
But unfortunately i cannot connect to wifi…

And what about:

? Do those problems persist even without dtoverlay=vc4-kms-v3d or not?

What about?

I changed one problem to the other…

With dtoverlay=vc4-kms-v3d screen and soubd via HDMI does not works,
without dtoverlay=vc4-kms-v3d WiFi is unable to connect, but screen (and probabbly sound i think - no possibility to play without net connection) works.

Now try adding

dtoverlay=vc4-kms-v3d
disable_fw_kms_setup=1

to “/boot/userconfig.txt”.

No screen and sound.
Wifi connection works.

Edit:

Have one idea more: this is how my screen looks now and works…(with userinfo.txt empty). Thin black stripes of inactive display area are surrounding the on-screen view.

https://zapodaj.net/plik-7JH271Lx5v

Maybe it is possible to adjust the touch screen area to fit to what is on the screen?

I’m already trying everything possible, I think I could live with smaller display area. :frowning:

Hey @gvolt,

Got the same KD070V02 delivered today.

Long story short :face_with_symbols_over_mouth: no one likes to be lied to by subpar electronics. Modeset presented by EDID:

[    50.335] (II) modeset(0): Supported established timings:
[    50.335] (II) modeset(0): 720x400@70Hz
[    50.335] (II) modeset(0): 640x480@60Hz
[    50.335] (II) modeset(0): 640x480@72Hz
[    50.335] (II) modeset(0): 640x480@75Hz
[    50.335] (II) modeset(0): 800x600@56Hz
[    50.335] (II) modeset(0): 800x600@60Hz
[    50.335] (II) modeset(0): 800x600@72Hz
[    50.335] (II) modeset(0): 800x600@75Hz
[    50.335] (II) modeset(0): 832x624@75Hz
[    50.335] (II) modeset(0): 1024x768@60Hz
[    50.335] (II) modeset(0): 1024x768@70Hz
[    50.335] (II) modeset(0): 1024x768@75Hz
[    50.335] (II) modeset(0): 1280x1024@75Hz
[    50.335] (II) modeset(0): Manufacturer's mask: 0
[    50.335] (II) modeset(0): Supported detailed timing:
[    50.335] (II) modeset(0): clock: 50.4 MHz   Image Size:  476 x 268 mm
[    50.335] (II) modeset(0): h_active: 1024  h_sync: 1068  h_sync_end 1156 h_blank_end 1344 h_border: 0
[    50.335] (II) modeset(0): v_active: 600  v_sync: 603  v_sync_end 609 v_blanking: 625 v_border: 0
[    50.335] (II) modeset(0): Serial No: 0
[    50.335] (II) modeset(0): Ranges: V min: 56 V max: 75 Hz, H min: 30 H max: 83 kHz, PixClock max 215 MHz
[    50.335] (II) modeset(0): Monitor name: HDMI
[    50.335] (II) modeset(0): Supported detailed timing:
[    50.335] (II) modeset(0): clock: 27.0 MHz   Image Size:  697 x 392 mm
[    50.335] (II) modeset(0): h_active: 720  h_sync: 732  h_sync_end 796 h_blank_end 864 h_border: 0
[    50.335] (II) modeset(0): v_active: 576  v_sync: 581  v_sync_end 586 v_blanking: 625 v_border: 0
[    50.335] (II) modeset(0): Supported detailed timing:
[    50.335] (II) modeset(0): clock: 74.2 MHz   Image Size:  697 x 392 mm
[    50.335] (II) modeset(0): h_active: 1920  h_sync: 2008  h_sync_end 2052 h_blank_end 2200 h_border: 0
[    50.335] (II) modeset(0): v_active: 540  v_sync: 542  v_sync_end 547 v_blanking: 562 v_border: 0
[    50.335] (II) modeset(0): Supported detailed timing:
[    50.335] (II) modeset(0): clock: 74.2 MHz   Image Size:  697 x 392 mm
[    50.335] (II) modeset(0): h_active: 1920  h_sync: 2448  h_sync_end 2492 h_blank_end 2640 h_border: 0
[    50.335] (II) modeset(0): v_active: 540  v_sync: 542  v_sync_end 547 v_blanking: 562 v_border: 0
[    50.335] (II) modeset(0): Supported detailed timing:
[    50.335] (II) modeset(0): clock: 74.2 MHz   Image Size:  697 x 392 mm
[    50.335] (II) modeset(0): h_active: 1280  h_sync: 1720  h_sync_end 1760 h_blank_end 1980 h_border: 0
[    50.335] (II) modeset(0): v_active: 720  v_sync: 725  v_sync_end 730 v_blanking: 750 v_border: 0
[    50.335] (II) modeset(0): Supported detailed timing:
[    50.335] (II) modeset(0): clock: 148.5 MHz   Image Size:  697 x 392 mm
[    50.335] (II) modeset(0): h_active: 1920  h_sync: 2448  h_sync_end 2492 h_blank_end 2640 h_border: 0
[    50.335] (II) modeset(0): v_active: 1080  v_sync: 1084  v_sync_end 1089 v_blanking: 1125 v_border: 0

The vc4-kms-v3d overlay is consistent and kernel evicts vc4 with printing what it thinks the screen should be:

[    51.246] (II) modeset(0): EDID vendor "DWE", prod id 8448
[    51.246] (II) modeset(0): Using EDID range info for horizontal sync
[    51.246] (II) modeset(0): Using EDID range info for vertical refresh
[    51.246] (II) modeset(0): Printing DDC gathered Modelines:

As such it needs to be pushed to Modeline “FIXED_MODE” with vc4-fkms-v3d.

Kind Regards,

Hey @Grg,

Please update your /boot/userconfig.txt to:

# Add your custom config.txt options to this file, which will be preserved during updates
[all]
max_framebuffers=2

dtoverlay=vc4-fkms-v3d
hdmi_force_mode=1
hdmi_group=2
hdmi_mode=87
hdmi_cvt 1024 600 60 6 0 0 0
hdmi_drive=2
config_hdmi_boost=7

Please let us know if this solves “the lies”.

Kind Regards,

What a PITA… :grimacing:

Thanks for investigating!