Black screen on HMDI output, content on remote browser

sdetweil

@chris_d

which pi os?

lsb_release -a

how did u open that terminal window?

chris_d

@sdetweil said in Black screen on HMDI output, content on remote browser:

lsb_release -a

Distributor ID: Raspbian
Description: Raspbian GNU/Linux 10 (buster)
Release: 10
Codename: buster

I am using ssh to remote into the pi
The following thread seems similar, but does not offer a solution
https://forum.magicmirror.builders/topic/17211/having-trouble-with-launch-perhaps-display-value?page=1

sdetweil

@chris_d interesting. I ssh into my mirror systems all the time and never have trouble.

do

pm2 stop all
cd ~/MagicMirror
npm start >somefile.txt 2>&1

wait til the black screen
ctrl-c in the ssh terminal

then nano somefile.txt, scroll down
see if there are any errors reported…

the package.json will set DISPLAY if not set

chris_d

@sdetweil said in Black screen on HMDI output, content on remote browser:

pm2 stop all
cd ~/MagicMirror
npm start >somefile.txt 2>&1

Errors are:
[2883:0119/213451.321388:ERROR:viz_main_impl.cc(186)] Exiting GPU process due to errors during initialization
[2916:0119/213451.509005:ERROR:gpu_memory_buffer_support_x11.cc(44)] dri3 extension not supported.

sdetweil

@chris_d in from to the npm start line do

export ELECTRON_DISABLE_GPU=1

and rerun…

chris_d

@sdetweil said in Black screen on HMDI output, content on remote browser:

export ELECTRON_DISABLE_GPU=1

No error now, but still a black screen

sdetweil

@chris_d on the black screen press ctrl-shift-i to open the developers window, then select the console tab and scroll up for any errors usually red text

MikeBishop

@sdetweil

I’m having what appears to be the same problem – HDMI is black (but apparently happy from the log output), while browser access is fine. I can’t get the dev tools to come up in Electron; perhaps unsurprisingly, the browser dev tools don’t show any errors that weren’t there on my old instance.

sdetweil

@MikeBishop are you also running on buster?

sdetweil

@chris_d try npm start dev to open dev window on startup

also can u try the npm start on the pi desktop, not over ssh?