Read the statement by Michael Teeuw here.
updated installer script available for testing
-
@Neebotol looks like npm is not able to run after the node upgrade…
do this
rm -rf MagicMirror npm clean cachethen start the installer script again
-
@Neebotol said in updated installer script available for testing:
I’m a little desperate,
We’ve all been there.
but I’m not giving up!
:thumbsup:
-
@sdetweil Thanks for your help in getting my installation sorted out Sam.
-
@Mykle1 said in updated installer script available for testing:
@Neebotol said in updated installer script available for testing:
I’m a little desperate,
We’ve all been there.
but I’m not giving up!
:thumbsup:
Yep! :handshake:
-
@Neebotol is MM working ok now?
-
@sdetweil Hello! thank you for the way you’re helping people in this project.
I just solved the problem tonight after more than 20 hours on it! It was really stupid, I used another SD card and it just worked. (I don’t understand too much because the SD card I was using until now was of good quality)
Have a good day!
-
@Neebotol great work!! Yeh, having a bad card will.make things very challenging.
Thanks for the feedback
-
Hey @sdetweil,
Forgot I did not get back to you. After much testing it was not feasible to use an rpi zero. Actually the ram/memory was ok, the main limitation was the cpu.
I was using htop to monitor this during boot and normal usage, is was constantly at 100%. This caused really slow boot time and could not load the modules fully even if left for several hours.
As soon as I went back to my rpi3 with the same modules it started very quick in comparison with no boot issues.
-
@NathTheDude thank you for the feedback. Yes Pi 0 is really limited in what it can do.
-
@NathTheDude using the new run-start.sh which launches chrome to connect to the MM serverOnly instance… I see 45% usage in htop for the initial config.
electron has become unavailable for armv6l and node >8, so we’ve had to go split mode
