Display/wifi/account/plugins problem

@Grg Please do not use ‘wtf’, @Wheaten and @nerd are doing their best to support you with an unsupported chinese device, give them time.
Please keep it civil.

Please provide a link to this exact screen.
Seems it’s everything but compatible.

And connect the rPi to a cabled network.

Yes you are right sorry for dirty words.
This is what happen when you have a lack of vocabulary :laughing: I’m foreigner :stuck_out_tongue_winking_eye:

But I didn’t even connect the screen, just changed the userconfig.txt entries.

That’s what I put there:

hdmi_group=2
hdmi_mode=87
hdmi_cvt=1024 600 60 6 0 0 0

Screen model is: KD070V02

Can you post link to your particular screen please? A quick search for “KD070V02” returns quite a large suspects volume.

On the other hand:

hdmi_cvt=

When using the VC4 KMS graphics driver, the complete display pipeline is managed by Linux - this includes the HDMI outputs. These settings only apply to the legacy FKMS and firmware-based graphics driver.

I wonder if this is not sending gpu somewhere awry without EDID present or poorly configured in the display itself.

However we are depending on kms; not fkms pipeline; hence try configuration in /boot/userconfig.txt

# Enable explicitly pi4 kms pipeline
[pi4]
display_auto_detect=1
dtoverlay=vc4-kms-v3d-pi4

# Push legacy controls, do not use = character with hdmi_cvt
[all]
hdmi_group=2
hdmi_mode=87
hdmi_cvt 1024 600 60 6 0 0 0
hdmi_drive=1

Report your findings.

Display type:

nerd
I have put what you proposed.

Now my system is able to connect with wifi an log-in to my account.
New problem - no sound and no display (it works ca. half of minute after boot ald turns black.
Problem not on the chinesse display but my previous normal monitor :frowning:
I was able to made a log.

http://logs.volumio.org/volumio/PxwMpPd.html

Hey @Grg,

I am a bit lost with your goal.

Please detail as much as you can of what is that you are trying to achieve. What is connected with what, what port, what cable, what power delivery is connected to what device. All partaking devices versions brand, make, etc. Please do not assume that anyone in this community is a mind-reader. Every detail, however small it seems may have an adverse impact on your particular use case.

Kind Regards,

So ok.

system is normal RPi4 with normal power supply.
vision and sound is on HDMI…nothing unusual.
i gave information at the beginning of this topic BTW.

I have bough small lcd and tried to install it on my system that worked fine with old monitor till the moment when i put any entries to userconfig.txt.
But to simplyfy case for you guys - LCD is lying in the box and i fight with problems on my old monitor - when everyting will by fine on proper resolution i will just change the device on the other end of HDMI.

Even now after i remove entries from userconfig - system has vision and sound…
And again: without entries system works on my both displays (with wrong resolution)
With any entry to userconfig: not working property (all problems described above)…

Dont know what to write more…

Hey @Grg,

Thank you for providing all the information so far! To better assist you, I’ll guide you step by step and ask for a few additional details to ensure we’re addressing everything properly.

Here is a table listing the different versions of the Raspberry Pi 4 Model B (4B) along with key specifications:

Version Release Date RAM Options Processor WiFi & Bluetooth Ethernet USB Ports HDMI Ports Power Input
Raspberry Pi 4B (1GB) June 2019 1GB LPDDR4 (discontinued) Broadcom BCM2711 (Quad-core Cortex-A72 @ 1.5GHz) WiFi 5 (802.11ac) & Bluetooth 5.0 Gigabit Ethernet 2 × USB 3.0, 2 × USB 2.0 2 × micro HDMI (4K@60Hz support) USB-C (5V 3A recommended)
Raspberry Pi 4B (2GB) June 2019 2GB LPDDR4 Broadcom BCM2711 (Quad-core Cortex-A72 @ 1.5GHz) WiFi 5 (802.11ac) & Bluetooth 5.0 Gigabit Ethernet 2 × USB 3.0, 2 × USB 2.0 2 × micro HDMI (4K@60Hz support) USB-C (5V 3A recommended)
Raspberry Pi 4B (4GB) June 2019 4GB LPDDR4 Broadcom BCM2711 (Quad-core Cortex-A72 @ 1.5GHz) WiFi 5 (802.11ac) & Bluetooth 5.0 Gigabit Ethernet 2 × USB 3.0, 2 × USB 2.0 2 × micro HDMI (4K@60Hz support) USB-C (5V 3A recommended)
Raspberry Pi 4B (8GB) May 2020 8GB LPDDR4 Broadcom BCM2711 (Quad-core Cortex-A72 @ 1.5GHz) WiFi 5 (802.11ac) & Bluetooth 5.0 Gigabit Ethernet 2 × USB 3.0, 2 × USB 2.0 2 × micro HDMI (4K@60Hz support) USB-C (5V 3A recommended)

Let me know specific hardware form the table above you use.

1. Clarify Your Goal

From what I understand:

  • You want to configure your Raspberry Pi 4 to work with a 7-inch LCD touchscreen display.
  • Currently, your system works (sound and display) on an old monitor, but any changes to userconfig.txt break the WiFi connection or functionality.
  • Your aim is to make the LCD work, but only after ensuring the current setup (with the old monitor) is stable.

If this is correct, let’s proceed step by step. If I’ve misunderstood, feel free to correct or add more details.


2. Details Needed

Before diving into troubleshooting, can you clarify the following?

  1. Audio Setup

    • How is audio routed? Is it:
      • Through the HDMI port?
      • Something else?
  2. Display Ports

    • Which HDMI port on the Raspberry Pi are you using? (HDMI0 is the port closest to the power supply.)
    • Does the issue persist if you try the other HDMI port?
  3. Cables and Power Supply

    • What power supply are you using for the Raspberry Pi? (Voltage and amperage, e.g., 5V 3A.)
    • What cables are used for connecting the display (e.g., HDMI and USB for touch)?
  4. Testing Scenarios

    • When does the sound stop working? Immediately after adding the LCD settings in userconfig.txt, or after connecting the LCD physically?
    • Does the sound stop for both the old monitor and the new LCD?

3. Step-by-Step Troubleshooting

Let’s address this methodically:

A. Stabilize Current Setup (Old Monitor)

  1. Fresh Installation:

    • Start with a fresh Volumio image on the SD card.
    • Do not modify any system files.
    • Set up the system and ensure:
      • WiFi connects properly.
      • Your MyVolumio account logs in.
      • Web radio and Spotify play as expected.
  2. Test HDMI Ports:

    • Test HDMI0 and HDMI1 separately to see if one works better for your setup.
  3. Share Logs:

    • If any issues arise, generate and share fresh debug logs.

B. Introduce LCD Settings (Without Connecting the LCD)

  1. Add the following to /boot/userconfig.txt:
    [pi4]
    dtoverlay=vc4-kms-v3d-pi4
    hdmi_force_hotplug=1
    display_auto_detect=1
    
    [all]
    hdmi_group=2
    hdmi_mode=87
    hdmi_cvt 1024 600 60 6 0 0 0
    hdmi_drive=2
    
  2. Restart and test the system with your old monitor still connected.
    • Does WiFi remain stable?
    • Is the sound working?

C. Connect the LCD (After Stabilization)

  1. Once the system is stable with the old monitor and the LCD settings applied, physically connect the LCD using HDMI and USB (for touch functionality).
  2. Restart the system and check:
    • Does the LCD display correctly?
    • Is sound working?
    • Is WiFi still stable?

D. Logs for Issues

  • If any problems occur at any step, share a fresh debug log and describe:
    • What you changed before the issue occurred.
    • Which HDMI port is in use.
    • How audio is routed.

4. General Notes

  • If WiFi issues persist, consider connecting the Raspberry Pi to a wired network during the setup phase for stability.
  • The LCD may require a separate power source if it draws too much power from the Raspberry Pi via USB.
  • If you suspect hardware incompatibility with the LCD, it may help to test it on a different device to verify functionality.

Let’s take this one step at a time to simplify troubleshooting. Community members are here to help you through each step!

Kind Regards,

Wow - nerd - You are super-consequent :slight_smile:

My system is Rpi4 4MB (details above)

  1. My goal is to have sytem workeing on 7 inch LCD (details above).

    1. Audio via HDMI
    2. HDMI0 (only that works)
    3. 5V 3A power adapter USBc
    4. It is clear fo me that it stops after reboot generally when changes are applied.
      I wont make the sound before the vision stops - maybe HDMi port stops? Vision stops after ca 30 seconds
      Same problem on monitor and LCD.
  2. A. 1. Done - with Your kind help!
    2. Only HDMI0 works
    3. http://logs.volumio.org/volumio/Fzq2pDY.html
    B . 1. Done - problems sterted. No vision after 30 seconds, no sound!!
    2. http://logs.volumio.org/volumio/JGku325.html

Enough information for today - IMHO HDMI port stops.
ood is that WIFI works.

Hey @Grg,

Thank you for the detailed update and for clarifying the setup! It seems like we’re narrowing down the issue to the HDMI port potentially stopping after a short time. I have one question about how you’re routing the audio in your setup:

  • Where is the audio physically played when using HDMI?
    • Is it through built-in speakers on your monitor or LCD?
    • Or is there an external device (e.g., speakers or an audio extractor) connected to the monitor or LCD?

This information will help determine if the HDMI port is stopping entirely or if it’s just the display, and whether we might need additional steps to troubleshoot the audio issue.

Looking forward to your findings!

Kind Regards,

Both, monitor and LCD display have jack audio output. Both outputs stop working after Your point 2.B.1. :slight_smile: entries ane present in ucerconfig file together with vision (this one stops after 30 seconds ca.).
Greetings

Hey @Grg,

Thank you for the update! It’s good to know that the current configuration in /boot/userconfig.txt is set up for the 7-inch HDMI touchscreen, but if I’m not mistaken, the Touch Display plugin was initially configured for the original screen. This mismatch might indeed be contributing to the issue. A more thorough approach would be to uninstall and reinstall the plugin, ensuring it properly detects and configures for the 7-inch touchscreen.

1. Steps to Test and Reconfigure the Touch Display Plugin

A. Uninstall the Plugin

  1. Navigate to Plugins > Installed Plugins in the Volumio interface.
  2. Uninstall the Touch Display plugin completely.

B. Test HDMI Audio and Video Without the Plugin

  1. Reboot the system after uninstalling the plugin.
  2. Test whether:
    • Audio over HDMI works without interruptions.
    • Video output remains stable for more than 30 seconds.

If the system works correctly at this point, it’s likely that the plugin was misconfigured or causing conflicts.

C. Reinstall the Plugin

  1. Go to Plugins > Plugin Store, find the Touch Display plugin, and install it again.
  2. Ensure that the plugin settings are updated to match the 7-inch touchscreen’s resolution (1024x600).

D. Reboot and Test

  1. Restart the Raspberry Pi after reinstalling the plugin.
  2. Verify:
    • Video stability (on the 7-inch touchscreen).
    • Audio playback over HDMI.

2. Additional Notes

  • If HDMI audio and video fail even with the plugin uninstalled, the issue might lie elsewhere (e.g., userconfig.txt settings or hardware).
  • If everything works with the plugin uninstalled but fails after reinstalling, we can delve deeper into the plugin’s behavior and logs.

Let us know the results of these steps.

Kind Regards,

Should I test it WITH your entries in userconfig??

I’m sorry but I do not understand what is it you asked here.

Let’s tidy this up a bit. You have two screens:

Screen 1 (old)

This statement alone suggests that your setup was working fine without any explicit entries in /boot/userconfig.txt file. You refer to this screen as “old”. My preference would be to have technical details of what you call “old”. Can you respond with model and make of “old”?

Screen 2 (KD070V02)

Whilst following on your test results we have defined a subset of parameters required to be added to the /boot/userconfig.txt file:

[pi4]
display_auto_detect=1
dtoverlay=vc4-kms-v3d-pi4

[all]
hdmi_group=2
hdmi_mode=87
hdmi_cvt 1024 600 60 6 0 0 0
hdmi_drive=2

Further testing

With Touch Screen plugin uninstalled confirm audio working (or not) state. Each time configure your audio Playback Options as there may be specific EDID information retrieved from connected screen.

Screen Userconfig Playback Options Result Alsa audio
Screen 1 No added parameters
Original configuration
Configure HDMI audio output Report result please Output from alsa -l
Screen 2 Parameters specific for this screen as discussed in this thread Configure HDMI audio output Report result please Output from alsa -l

Kind Regards,

No no no, to much :wink:

I proof that no matter what is connected to hdmi the system behavior/ problems are the same.

Let’s make an appointment that I will perform “touch screen” plugin reinstall test with entries to userconfig.txt
After all, it’s supposed to work on 1024x600 res.

Hey @Grg,

I am completely lost:

Screen Userconfig Playback Options Result Alsa audio
Screen 1 No added parameters. Original configuration Configure HDMI audio output Report result please Output from alsa -l

Which is reverting to exactly the same point which you wrote working. :confused:

Are you saying that it is not working any-more? Should this be the case, what else you have changed and kept it secret?

Goes without saying:

  • Community help is as accurate as information you provide.
  • Focus on one change at the time. Test change impact.

Kind Regards,

Why You dig in the oldest posts? It was on the beginning.

I write recently several times that system works without entries in userconfig.txt and does not work properly with such entries.

I will provide test like I wrote in the post 35 and give feedback in my post below ….

Just a question:
How do you add these entries to /boot/userconfig.txt.
Which programs are being used, I get the impression you’re using notepad?
Which breaks <cr> and <lf> (windows vs linux)
If the answer is yes.
Use either notepad++ on Windows or nano via SSH.

I learned how to use ssh and use nano to edit file without removing SD card.

To summarize, or get a clear understanding:

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