Just upgraded to 2.18, runs, but no display

fribse

Hi all

One more to the list of people having problems after 2.18.
I’m running a RPi to show the magicmirror.
I can see on ‘http://mirror:8080’ that it renders the page.
But nothing is shown on the monitor
By now in my debugging I only have these modules activated:
“compliments”
“alert”
“updatenotification”
“clock”
“calendar”
“weather”
“newsfeed”
As far as I know, all core modules.
I see this in the logfile:

0|MagicMir | [974:0213/131905.747644:ERROR:viz_main_impl.cc(161)] Exiting GPU process due to errors during initialization
0|MagicMir | [1014:0213/131907.005140:ERROR:viz_main_impl.cc(161)] Exiting GPU process due to errors during initialization
0|MagicMir | [1036:0213/131907.699933:ERROR:sandbox_linux.cc(376)] InitializeSandbox() called with multiple threads in process gpu-process.

sdetweil

@fribse yes, can reinstall like that.

as for black screen there is this

https://forum.magicmirror.builders/topic/15778/fix-for-black-screen-in-2-16-and-later

my upgrade only handles 2 known libs missing, request and valid-url

if there is another, I’d update my script.

sdetweil

@fribse how did u upgrade? git clone & npm install, or my script?

if you open the dev window, ctrl-shift-i on the keyboard and select the console tab, do you see any other errors?

what pi is this?
can u show output of

node -v
npm -v

fribse

@sdetweil I used your script (of course )
It’s a Raspberry Pi 3 Model B Rev 1.2
According to /sys/firmware/devicetree/base/model

node -v
v16.14.0
npm -v
8.3.1

I’ve now tried to only load the clock module, same result.

No message in the debug console, except the happy ones.

Btw. release shows:

/etc/*release
PRETTY_NAME=“Raspbian GNU/Linux 10 (buster)”
NAME=“Raspbian GNU/Linux”
VERSION_ID=“10”
VERSION=“10 (buster)”
VERSION_CODENAME=buster
ID=raspbian
ID_LIKE=debian
HOME_URL=“http://www.raspbian.org/”
SUPPORT_URL=“http://www.raspbian.org/RaspbianForums”
BUG_REPORT_URL=“http://www.raspbian.org/RaspbianBugs”

fribse

@sdetweil Can I attempt a reinstall by just renaming the MagicMirror folder?
I’ve also lost my most appreciated module, MMM-MQTTBridge, so I would love to just go back to the 2.17.1 if possible at all and the node.js and npm to be on an older (working) version

bugsounet

I see this in the logfile:

0|MagicMir | [974:0213/131905.747644:ERROR:viz_main_impl.cc(161)] Exiting GPU process due to errors during initialization
0|MagicMir | [1014:0213/131907.005140:ERROR:viz_main_impl.cc(161)] Exiting GPU process due to errors during initialization
0|MagicMir | [1036:0213/131907.699933:ERROR:sandbox_linux.cc(376)] InitializeSandbox() called with multiple threads in process gpu-process.

Generaly:

50% of problems come from the person behind the terminal
48% of other problem are person don’t read pre-require
2% of rest are main coding problem

Are you sure that you are in 2% of people ?

So: Just use node v14.x

sdetweil

@fribse yes, can reinstall like that.

as for black screen there is this

https://forum.magicmirror.builders/topic/15778/fix-for-black-screen-in-2-16-and-later

my upgrade only handles 2 known libs missing, request and valid-url

if there is another, I’d update my script.

fribse

@bugsounet Ha ha ha, no, I’m not blaiming anybody except myself.
How do I
“So: Just use node v14.x”

@sdetweil I just did a reinstall, and now it displays stuff on the screen.
I do see this in the logs repeated over and over (as I said, fresh install):

0|MagicMirror  | [6213:0213/182653.081807:ERROR:socket_posix.cc(96)] CreatePlatformSocket() failed: Adressefamilien er ikke understøttet af protokollen (97)

Now I’ll try to add modules from my old config to see if it keeps working.

fribse

@fribse Ok, so the black screen has nothing to do with the error:

0|MagicMirror  | [1554:0213/183501.650842:ERROR:viz_main_impl.cc(161)] Exiting GPU process due to errors during initialization
0|MagicMirror  | [1601:0213/183503.081619:ERROR:viz_main_impl.cc(161)] Exiting GPU process due to errors during initialization
0|MagicMirror  | [1621:0213/183503.548717:ERROR:sandbox_linux.cc(376)] InitializeSandbox() called with multiple threads in process gpu-process.

As that is still shown when I start the software…

sdetweil

@fribse never seen that before

fribse

@sdetweil Glad to show you something new
I wonder if it’s the

gpu_mem=128

in boot/config.txt
?

Well, after doing a reinstall, module for module, it’s working with everything except that the Screencast module interferes with the remote module for the Home Assistant Integration (which uses the remote module).

So a success for now, and then I hope the integration to HA will get working.
Thans @sdetweil and @bugsounet !

SOLVED Just upgraded to 2.18, runs, but no display

I am not a magician