Moode Forum
Moode 4.2 Problem with 5" HDMI screen - Printable Version

+- Moode Forum (https://moodeaudio.org/forum)
+-- Forum: moOde audio player (https://moodeaudio.org/forum/forumdisplay.php?fid=3)
+--- Forum: Support (https://moodeaudio.org/forum/forumdisplay.php?fid=7)
+--- Thread: Moode 4.2 Problem with 5" HDMI screen (/showthread.php?tid=311)

Pages: 1 2 3

RE: Moode 4.2 Problem with 5" HDMI screen - seta_vn - 07-23-2018

This is what i got with the command ~ $ /opt/vc/bin/tvservice -d edid.dat:
pi@moode:~ $ /opt/vc/bin/tvservice -d edid.dat
Written 128 bytes to edid.dat
pi@moode:~ $ /opt/vc/bin/edidparser edid.dat
Enabling fuzzy format match...
Parsing edid.dat...
HDMI:EDID version 1.3, 0 extensions, screen size 15x10 cm
HDMI:EDID features - videodef 0x80 !standby !suspend !active off; colour encodin g:RGB444|YCbCr422; sRGB is not default colourspace; preferred format is native; does not support GTF
HDMI:EDID ignored unknown descriptor tag 0x10
HDMI:EDID ignored unknown descriptor tag 0x10
HDMI:EDID ignored unknown descriptor tag 0x10
HDMI:EDID does not yet know monitor vertical range, setting to default 24 to 120 Hz
HDMI:EDID failed to find a matching detail format for 800x480p hfp:40 hs:48 hbp: 40 vfp:13 vs:3 vbp:29 pixel clock:32 MHz
HDMI:EDID calculated refresh rate is 66 Hz
HDMI:EDID guessing the format to be 800x480p @70 Hz
HDMI:EDID found unknown detail timing format: 800x480p hfp:40 hs:48 hbp:40 vfp:1 3 vs:3 vbp:29 pixel clock:32 MHz
HDMI:EDID established timing I/II bytes are 00 00 00
HDMI:EDID standard timings block x 8: 0x0101 0101 0101 0101 0101 0101 0101 0101
HDMI:EDID adding mandatory support for DMT (4) 640x480p @ 60Hz
HDMI:EDID filtering formats with pixel clock > 162 MHz or h. blanking > 1023
HDMI:EDID no known preferred format has been set
HDMI:EDID filtering preferred group has been changed from Invalid to DMT
HDMI:EDID best score mode initialised to DMT (4) 640x480p @ 60 Hz with pixel clo ck 25 MHz (score 0)
HDMI:EDID best score mode is now DMT (4) 640x480p @ 60 Hz with pixel clock 25 MH z (score 36864)
HDMI:EDID preferred mode is updated to DMT (4) 640x480p @ 60 Hz with pixel clock 25200000 Hz
HDMI:EDID has only DVI support and no audio support
/opt/vc/bin/edidparser exited with code 0

RE: Moode 4.2 Problem with 5" HDMI screen - seta_vn - 07-23-2018

This is very frustrating, yesterday i borrowed a card from a friend with moode 4.1 installed and the screen works just fine but as soon as i put the card with 4.2 in the screen went back to black screen. Volumio & Rune all works fine with Waveshare 5"

RE: Moode 4.2 Problem with 5" HDMI screen - Tim Curtis - 07-23-2018

You could try verifying that local ui is running and there are no obvious catastrophic errors or the like but as I mentioned earlier without one of these screens in hand I'm not able to attempt a repro.

systemctl status localui

Example from system running a Pi-Touch
Code:
pi@rp5:~ $ systemctl status localui
● localui.service - Start Chromium Browser
  Loaded: loaded (/lib/systemd/system/localui.service; disabled; vendor preset: enabled)
  Active: active (running) since Thu 2018-07-19 21:34:35 EDT; 3 days ago
Main PID: 3316 (xinit)
  CGroup: /system.slice/localui.service
          ├─3316 /usr/bin/xinit -- -nocursor
          ├─3319 /usr/lib/xorg/Xorg :0 -nocursor
          ├─3328 /bin/bash /home/pi/.xinitrc
          ├─3334 /usr/lib/chromium-browser/chromium-browser --enable-pinch --kiosk --touch-events --disable-touch-drag-drop --enable-touchview --enable-pinch --window-size
          ├─3345 /usr/lib/chromium-browser/chromium-browser --type=zygote
          ├─3347 /usr/lib/chromium-browser/chromium-browser --type=zygote
          ├─3410 /usr/lib/chromium-browser/chromium-browser --type=gpu-process --field-trial-handle=15890373761339052158,10525936660633702958,131072 --gpu-preferences=KAAA
          └─3565 /usr/lib/chromium-browser/chromium-browser --type=renderer --disable-touch-drag-drop --touch-events --field-trial-handle=15890373761339052158,105259366606

Jul 19 21:34:35 rp5 xinit[3316]:         (++) from command line, (!!) notice, (II) informational,
Jul 19 21:34:35 rp5 xinit[3316]:         (WW) warning, (EE) error, (NI) not implemented, (??) unknown.
Jul 19 21:34:35 rp5 xinit[3316]: (==) Log file: "/var/log/Xorg.0.log", Time: Thu Jul 19 21:34:35 2018
Jul 19 21:34:35 rp5 xinit[3316]: (==) Using system config directory "/usr/share/X11/xorg.conf.d"
Jul 19 21:34:39 rp5 xinit[3316]: Fontconfig warning: "/etc/fonts/fonts.conf", line 160: blank doesn't take any effect anymore. please remove it from your fonts.conf
Jul 19 21:34:40 rp5 xinit[3316]: [3334:3558:0719/213440.177294:ERROR:bus.cc(394)] Failed to connect to the bus: Could not parse server address: Unknown address type (exampl
Jul 19 21:34:41 rp5 xinit[3316]: ATTENTION: default value of option force_s3tc_enable overridden by environment.
Jul 19 21:34:41 rp5 xinit[3316]: [3410:3410:0719/213441.189907:ERROR:sandbox_linux.cc(375)] InitializeSandbox() called with multiple threads in process gpu-process.
Jul 19 21:34:41 rp5 xinit[3316]: [3334:3334:0719/213441.216440:ERROR:gpu_process_transport_factory.cc(1029)] Lost UI shared context.
Jul 19 21:34:41 rp5 xinit[3316]: [1:10:0719/213441.283512:ERROR:command_buffer_proxy_impl.cc(133)] ContextResult::kTransientFailure: Failed to send GpuChannelMsg_CreateComm


RE: Moode 4.2 Problem with 5" HDMI screen - TheOldPresbyope - 07-23-2018

(07-23-2018, 02:05 PM)seta_vn Wrote: This is very frustrating, yesterday i borrowed a card from a friend with moode 4.1 installed and the screen works just fine but as soon as i put the card with 4.2 in the screen went back to black screen. Volumio & Rune all works fine with  Waveshare 5"

How about a more relevant A/B test?

Try using this display with a fresh image of just Raspbian Stretch Lite 2018-06-27 (the version on which moOde r4.2 builds). If it works, then we have reason to believe your problem lies somewhere in the customization that is done to create moOdeOS. If it doesn't work, then we know your problem is not related to moOde and should be discussed in the Raspberry Pi forum or with WaveShare.

Regards,
Kent

RE: Moode 4.2 Problem with 5" HDMI screen - seta_vn - 07-26-2018

To be fair, the screen did work, when i press Alt+f2 & Alt+f2 the screen show the terminal as expected but it's the local UI that shows only black screen

RE: Moode 4.2 Problem with 5" HDMI screen - TheOldPresbyope - 07-26-2018

(07-26-2018, 08:08 AM)seta_vn Wrote: To be fair, the screen did work, when i press Alt+f2 & Alt+f2 the screen show the terminal as expected but it's the local UI that shows only black screen

Ah, that vaults us past a lot of basic troubleshooting. Now we're up to the windowing subsystem. Sorry, I'm out of the house today. Later.

Regards,
Kent

RE: Moode 4.2 Problem with 5" HDMI screen - Bobfossil1 - 07-30-2018

(07-26-2018, 01:38 PM)TheOldPresbyope Wrote:
(07-26-2018, 08:08 AM)seta_vn Wrote: To be fair, the screen did work, when i press Alt+f2 & Alt+f2 the screen show the terminal as expected but it's the local UI that shows only black screen

Ah, that vaults us past a lot of basic troubleshooting. Now we're up to the windowing subsystem. Sorry, I'm out of the house today. Later.

Regards,
Kent

Interested... I have the same problem with a 7 inch waveshare display....

RE: Moode 4.2 Problem with 5" HDMI screen - Tim Curtis - 07-30-2018

What is the output from the command below?

systemctl status localui

-Tim

RE: Moode 4.2 Problem with 5" HDMI screen - Bobfossil1 - 07-30-2018

(07-30-2018, 09:52 AM)Tim Curtis Wrote: What is the output from the command below?

systemctl status localui

-Tim

Hi Tim

This is what I'm getting:

● localui.service - Start Chromium Browser
   Loaded: loaded (/lib/systemd/system/localui.service; disabled; vendor preset: enabled)
   Active: failed (Result: exit-code) since Mon 2018-07-30 22:54:41 BST; 7min ago
  Process: 797 ExecStart=/usr/bin/xinit -- -nocursor (code=exited, status=203/EXEC)
 Main PID: 797 (code=exited, status=203/EXEC)
Jul 30 22:54:41 moode systemd[1]: Started Start Chromium Browser.
Jul 30 22:54:41 moode systemd[1]: localui.service: Main process exited, code=exited, status=203/EXEC
Jul 30 22:54:41 moode systemd[1]: localui.service: Unit entered failed state.
Jul 30 22:54:41 moode systemd[1]: localui.service: Failed with result 'exit-code'.

Thanks

Bob

RE: Moode 4.2 Problem with 5" HDMI screen - Tim Curtis - 07-30-2018

Hi Bob,

Thanks, that indicates that Chromium Browser is not able to start for some reason and thus = no display.

To isolate the issue:

1. Remove the touch panel
2. Revert any custom software configuration to moOde defaults
3. Reboot
4. Don't connect a display to HDMI port
5. sudo systemctl start localui
6. systemctl status localui

The result of this should be a successful Chromium Browser start, if not then it would suggest that something in moOde software config is not default.

-Tim