Black screen on HMDI output, content on remote browser

chris_d

I have recently updated and rebuilt my MM installation.
I can browse to my MM via a remote web browser and things display fine, however on the HDMI output of the PI itself I just have a black screen.

In the logs I see,

[1502:0115/164948.881957:ERROR:viz_main_impl.cc(186)] Exiting GPU process due to errors during initialization
[1538:0115/164949.052412:ERROR:gpu_memory_buffer_support_x11.cc(44)] dri3 extension not supported.
[1507:0115/164949.107262:ERROR:command_buffer_proxy_impl.cc(128)] ContextResult::kTransientFailure: Failed to send GpuControl.CreateCommandBuffer.

I wonder if anyone might be able to point me in the right direction.

sdetweil

@chris_d maybe turn off GPU useage

in the place where u start MM do

export ELECTRN_DISABLE_GPU=1

before the npm start line

if using pm2, that is ~/MagicMirror/installers/mm.sh

to test , if using pm2, then

pm2 stop all 
cd ~/MagicMirror 
export ELECTRN_DISABLE_GPU=1
npm start

if it works, update the mm.sh
and then pm2 start all

chris_d

@sdetweil That didn’t seem to work. It did eliminate any errors on startup, but the screen remainis blank.
the command to start in mm.sh is

DISPLAY=:0 npm start

sdetweil

@chris_d yes, so you would ad the export before the

DISPLAY… npm start line…

so, lets try something else

stop magicmirror

then

cd ~/MagicMirror
./node_modules/.bin/electron

does electron window come up?

chris_d

does electron window come up?

No. I get ./node_modules/.bin.electron: No such file or directory

sdetweil

@chris_d sorry typo in my instructions, a dot instead of a slash… see and try again

chris_d

@sdetweil
The platform failed to initialize.Missing X server or $DISPLAY

sdetweil

@chris_d you are running the full desktop os, right? text/cli mode doesn’t work, unless u want to run server only and view from somewhere else.

chris_d

@sdetweil I am running the full desktop. yes.
This used to work but following a Magic Mirror and pi system update it no longer does.
I can see the desktop on boot up, but when pm2 runs the mirror then I get the blank screen.

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?

MikeBishop

@sdetweil

Bullseye, looks like. Whatever’s in the newest RPi OS release, anyway.

For the moment, I’ve swapped back to the other SD card that’s working. System’s been a little flaky the last few days, figured I’d try a fresh install on a new card in case that’s starting to go; hit this issue on the new one. When I have a few minutes to pull the Pi from the mirror and bring it back to my desk, I’ll give npm start dev a try on the newer one.