Read the statement by Michael Teeuw here.
Black screen after MM v2.4.0 update.
-
I also have a black screen.
Tried both optionsdtoverlay=vc4-fkms-v3dand
dtoverlay=vc4-kms-v3d -
I have a similar problem, after starting the MM the screen freezes, only way to unfreeze it is to close electron. Have tried both options too.
After enabling either of the OpenGL drivers i get the followed errors:
> magicmirror@2.4.0 start /home/pi/MagicMirror > sh run-start.sh libGL error: MESA-LOADER: failed to retrieve device information MESA-LOADER: failed to retrieve device information MESA-LOADER: failed to retrieve device information Starting MagicMirror: v2.4.0 Loading config ... Loading module helpers ... No helper found for module: alert. No helper found for module: MMM-Cursor. Initializing new module helper ... Module helper loaded: updatenotification Initializing new module helper ... Module helper loaded: MMM-Buttons Initializing new module helper ... Module helper loaded: MMM-DWD-WarnWeather Initializing new module helper ... Module helper loaded: MMM-DHT-Sensor No helper found for module: clock. No helper found for module: compliments. No helper found for module: helloworld. Initializing new module helper ... Module helper loaded: MMM-Remote-Control Initializing new module helper ... Module helper loaded: MMM-MyWeather No helper found for module: MMM-SimpleLogo. Initializing new module helper ... Module helper loaded: MMM-PiLights All module helpers loaded. Starting server on port 8080 ... Server started ... Connecting socket for: updatenotification Connecting socket for: MMM-Buttons Starting node helper for: MMM-Buttons Connecting socket for: MMM-DWD-WarnWeather MMM-DWD-WarnWeather helper started... Connecting socket for: MMM-DHT-Sensor MMM-DHT-Sensor helper started ... Connecting socket for: MMM-Remote-Control Starting node helper for: MMM-Remote-Control Connecting socket for: MMM-MyWeather MMM-WunderGround helper started ... Connecting socket for: MMM-PiLights [2018-07-03 15:42:24] [MMM-PiLights] Starting node_helper Sockets connected & modules started ... Launching application. (node:1057) UnhandledPromiseRejectionWarning: Unhandled promise rejection (rejection id: 1): TypeError: Cannot read property 'refs' of undefined (node:1057) [DEP0018] DeprecationWarning: Unhandled promise rejections are deprecated. In the future, promise rejections that are not handled will terminate the Node.js process with a non-zero exit code. (node:1057) UnhandledPromiseRejectionWarning: Unhandled promise rejection (rejection id: 2): TypeError: Cannot read property 'refs' of undefined (node:1057) UnhandledPromiseRejectionWarning: Unhandled promise rejection (rejection id: 3): TypeError: Cannot read property 'refs' of undefined (node:1057) UnhandledPromiseRejectionWarning: Unhandled promise rejection (rejection id: 4): TypeError: Cannot read property 'refs' of undefined (node:1057) UnhandledPromiseRejectionWarning: Unhandled promise rejection (rejection id: 5): TypeError: Cannot read property 'refs' of undefined (node:1057) UnhandledPromiseRejectionWarning: Unhandled promise rejection (rejection id: 6): TypeError: Cannot read property 'refs' of undefined (node:1057) UnhandledPromiseRejectionWarning: Unhandled promise rejection (rejection id: 7): TypeError: Cannot read property 'refs' of undefinedEdit: MM works without any OpenGL Drivers, but CPU usage is pretty high and the Node errors are still there.
-
After 2.4.0, Asus Tinker Board cannot display MM. I think it might be related with this openGL issues. Is there any way to solve this?
ATB has no openGL desktop driver likevc4-kms-v3d. Fakevc4-kms-v3ddoes not help. -
I can’t access my mirror remotely anymore. Will I need to format my sd card and try again?
-
I am having the same issues and tried alot right now.
Tried the
dtoverlay=vc4-fkms-v3das well asdtoverlay=vc4-kms-v3das well asdeleting that phraseI downgraded electron to
npm install electron@1.4.15since i found that helped in the V2.30 problems.I cant currently show the log from starting MagicMirror since i remotly access it and the MM just goes “all black” over the remote-access-page and I cant close it.
I really just want to downgrad the MM to 2.3 since it worked absolutly fine with it…
Additional software I use is MM-PIR
-
-
@mykle1
Thanks Mykle1
Just how do i tell my pi to get the specific version? I am not versed in programming or coding or anything and couldnt find something online that told me how to install a specific version -
Did anyone find a fix here? just updated and same thing here. Hopefully i can get this back working tomorrow.
-
One way is to go to that link I gave you and download the version you want and install it manually.
-
Bumping this because I’m also having issues. A lot of time on google says it’s not just a MagicMirror issue, but lots of people have problems with the OpenGL drivers. My screen is blanking after some time no matter what, but I also found the hard way that it messes with
tvservice(like the Remote Control module uses) – turning my HDMI off straight up insta-shut down my pi! Gonna have to keep researching for sure. -
I just updated and this is shown at the end of the install.
MagicMirror installation successful! > magicmirror@2.4.1 install-fonts /home/pi/MagicMirror > cd fonts && npm install npm WARN postcss-html@0.12.0 requires a peer of postcss-less@>=1.1.0 but none was installed. npm WARN postcss-html@0.12.0 requires a peer of postcss-scss@>=1.0.0 but none was installed. npm WARN postcss-html@0.12.0 requires a peer of sugarss@>=1.0.0 but none was installed. npm WARN stylelint-config-standard@16.0.0 requires a peer of stylelint@^7.8.0 but none was installed. pi@raspberrypi:~/MagicMirror $I applied
dtoverlay=vc4-kms-v3dto the config.txt ( also tried with fkms)
Reboot and I get a black screen.
When I remove dtoverlay=vc4-kms-v3d then the mirror boots up.
Any suggestions? -
@mykle1
Just found your guide: https://forum.magicmirror.builders/topic/5274/how-to-manually-install-mm-on-your-pi-for-absolute-beginnersGoing at it now and see if it works - thanks for the patience and writing that guide!
-
@kastore said in Black screen after MM v2.4.0 update.:
thanks for the patience and writing that guide!
You’re welcome, sir. :-)
-
Got my mirror working again. Had to go over the opengl drivers again and using the fake kms driver did the trick. However one problem remains, i had to also disable the MMM-Pir-Sensor module because that was messing with the system. But also my custom.css is not being used atm, and i cant figure out why its not grabbing it.
-
Anyone else struggling with using MMM-Pir-Sensor after the new update?
-
Yes, I am having the same black screen. I have to disable PIR to be able to use MM at all. I also noted that after I installed PIR I could no longer SSH into the Pi from my desktop computer, whereas I could from my mobile phone. Anyway, the black screen is the main concern right now. I’ll post if I discover anything helpful.
-
Not sure if I’m having the same issue, stupidly updated electron as npm was claiming 1.7.13 had a critical vulnerability (after installing MMM-voice) Then got the backscreen issue. rolled back electron to 1.7.13 & the issue persists.
Node v9.11.1
npm 6.1.0Thought I’d uploaded the log file but not sure if others can see it. That snippet below is the first error after ALL_MODULES_STARTED
13:01:19.440 main.js:40 Uncaught TypeError: Cannot read property ‘appendChild’ of undefined
at main.js:40
at Array.forEach ()
at createDomObjects (main.js:24)
at Object.modulesStarted (main.js:471)
at startModules (loader.js:59)
at loader.js:40
at HTMLLinkElement.stylesheet.onload (loader.js:203)
(anonymous) @ main.js:40
createDomObjects @ main.js:24
modulesStarted @ main.js:471
startModules @ loader.js:59
(anonymous) @ loader.js:40
stylesheet.onload @ loader.js:20313:01:20.056 TypeError: Cannot read property ‘getElementsByClassName’ of null
at moduleNeedsUpdate (main.js:176)
at main.js:144
at Promise ()
at updateDomWithContent (main.js:137)
at main.js:119
at
Promise rejected (async)
(anonymous) @ main.js:121
Promise resolved (async)
(anonymous) @ main.js:118
updateDom @ main.js:109
updateDom @ main.js:514
updateDom @ module.js:358Any pointers as to how to get it working again? It was working perfectly before MMM-voice & buggering around with electron.
Tried a fresh install with the same result :( -
I’m also having the black screen of death. I tried both overlay options, and I tried commenting it out alltogether. I also ran the 2.4.1 update, but still getting black screen. Runs normally with the new update though when I comment out the PIR module in the config.js file.
-
@shane1234 if u have the PIR module loaded, and do ctrl-shift-i (lower case letter i), it will open the debug env, and then select the console tab… do you see any errors?
also, if u start from a terminal window, alt-spacebar, n will minimze the mirror screen so you can see the terminal window node_helper outputs… anything there?
usually a module.js error kills with MM screen…
-
Mine after upgrade it’s freezing when trying to run magicmirror. Also try both kms driver and fake kms driver.
Hello! It looks like you're interested in this conversation, but you don't have an account yet.
Getting fed up of having to scroll through the same posts each visit? When you register for an account, you'll always come back to exactly where you were before, and choose to be notified of new replies (either via email, or push notification). You'll also be able to save bookmarks and upvote posts to show your appreciation to other community members.
With your input, this post could be even better 💗
Register Login