SOLVED fix for black screen in 2.16 and later
kusselin last edited by
@sdetweil thank you…it´s working now.
I ran the command as recommended (request was my error as well). I now have this error and MM will not load:
Error: Cannot find module ‘logger’
- at Module._resolveFilename (node:internal/modules/cjs/loader:940:15)
at Function.n._resolveFilename (node:electron/js2c/browser_init:249:1128)
at Function.Module._resolveFilename (/home/pi/MagicMirror/node_modules/module-alias/index.js:49:29)
at Module._load (node:internal/modules/cjs/loader:785:27)
at Function.c._load (node:electron/js2c/asar_bundle:5:13331)
at Module.require (node:internal/modules/cjs/loader:1012:19)
at require (node:internal/modules/cjs/helpers:94:18)
at Object. (/home/pi/MagicMirror/js/app.js:13:13)
at Module._compile (node:internal/modules/cjs/loader:1116:14)
at Object.Module._extensions…js (node:internal/modules/cjs/loader:1169:10)
@lmac well you ran it in the wrong place… oops
cd ~/MagicMirror rm -rf node_modules rm package-lock.json npm install
then for whatever module was causing problem
do the same last 3 steps as above
npm install request --save
Just wanted to say thanks for the fix here.
Did an update and hit exactly this with MMM-GmailFeed and the request module.
Installed it back (with an audit fix afterwards) and now all up and running again
@sdetweil OK, thanks for the pointer.
Always kinda worried when that style of message pops up, for security and suchlike.
I see from the update that my node is very much out of date, so now just backing things up before setting the update script onto it to try and bring that up too.
@darrenhill upgrade is for MM, not node, (altho it might do it, works sometimes, need to move to n) …
easiest is using the node version of nvm, called n
sudo npm i n -g PATH="$PATH" n 16
then node 16 will be installed…
note that you will have to do another npm install in the mm (and maybe module folders)
this the upgrade would do (with force instead of apply)
n also allows you to SWITCH versions, or use a particular version for ONE app…
see n --help
@sdetweil - I did it via your update script, and it has updated Node from v10.x to v16.x (or at least that is what appears to have happened from what I could read).
It’s quite an old install that just sits on my desk and largely gets left to its own devices. It is in a PiTop Ceed rather than a true mirror, and basically the only thing it runs is MM (it’s actually a dual-boot via PINN also with RetroPie, but the Raspi OS partition is essentially only MM). So no need to keep things focussed to one app or anything like that - no issue of cross-contamination.
All is working fine after the update though, so no problems.
@darrenhill cool. thx for the feedback