Read the statement by Michael Teeuw here.
Disable GPU? MESA-LOADER failure on fresh manual install
-
@Corvidael how did you launch magicmirror? npm start in the MagicMirror folder
or using pm2?in either case, before issuing
npm start
manually or in the script you created. or in a terminal session
do
export ELECTRON_DISABLE_GPU=1 npm start
-
@sdetweil
Thank you. I’ve been using ‘npm run start’ as per the documentation off the manual installation instructions.
Just tried ‘npm start’ as well, which also seems to work identically (again, new to npm, so not sure of the difference)manually exporting the GPU disable at the terminal command line has proven to fix the error for that single run, but after a reboot and not manually entering the export of the GPU disable from command line again, the problem returns.
Seems my solution is starting to boil down to understanding the exact process of how npm launches when issuing the ‘start’ command, and finding the config script?
-
@Corvidael yes, you have to do it EVERY time you do npm start/npm run start
(you don’t need run for the start command, but do for any other)
so. however your autostart gets done, edit that to add the disable before the npm start
-
In the file MagicMirror/package.json, in the first liine of the “scripts” section, update the “start” line to be “start”: “DISPLAY=”${DISPLAY:=:0}" ./node_modules/.bin/electron --disable-gpu js/electron.js".
Butch
-
@butchkemper the ENV variable does it so u don’t have to edit package.json
-
@sdetweil … so, are you gonna add this to the script? 😉
-
@BKeyport no… it’s not fatal, just annoying.
maybe someone will figure out how to configure the video drivers in config.txt