Having trouble with launch- perhaps display value?

[Remco]

Hi,

I have done a manual update of MM and pi when the problems started.
I have also tried to run your installation script but the problem is still there. I have also tried to update node.js and npm to the latest versions.

These are requested outputs:

$ node -v
v18.10.0

$ npm -v
8.19.2

$ lsb_release -a
No LSB modules are available.
Distributor ID: Raspbian
Description: Raspbian GNU/Linux 10 (buster)
Release: 10
Codename: buster

$ uname -a
Linux raspberrypi 5.15.56-v7+ #1575 SMP Fri Jul 22 20:28:11 BST 2022 armv7l GNU/Linux

$ ps -ef | grep -i x11
pi 27931 5155 0 22:18 pts/0 00:00:00 grep --color=auto -i x11

[sdetweil]

@Remco said in Having trouble with launch- perhaps display value?:

pi 27931 5155 0 22:18 pts/0 00:00:00 grep --color=auto -i x11

ok, try this

ps -ef  | grep Xorg 

is this a server machine?, or does it have a display? where MM is shown?

[Remco]

Hi,

MM is running on a Pi with it’s own screen.
But in the meantime I got it working again. I found this threat with had similar errors as I had when running ‘startx’.

After I removed this driver MM started again:
sudo mv /usr/share/X11/xorg.conf.d/99-fbturbo.conf ~
startx

But I do still have the following errors in the error-log:

[16183:1013/103255.149031:ERROR:viz_main_impl.cc(186)] Exiting GPU process due to errors during initialization
[16220:1013/103256.721936:ERROR:gpu_memory_buffer_support_x11.cc(44)] dri3 extension not supported.
[16188:1013/103256.801401:ERROR:command_buffer_proxy_impl.cc(126)] ContextResult::kTransientFailure: Failed to send GpuControl.CreateCommandBuffer.

[sdetweil]

@Remco for the gpu errors do

add

export ELECTRON_DISABLE_GPU=1

in the script that starts mm
just before the npm start line

[sdetweil]

@Remco also, if u ran my upgrade script, can u send me the ~/MagicMirror/installers/upgrade.log file

use my userid at gmail