Read the statement by Michael Teeuw here.
Raspberry Pi Zero W for Magic Mirror
-
Hello all giving MM a try again on a Rpi zero and have been trying to run the script in this thread but keeping getting the following message
Am I missing something to by pass the Xorg check?
OS
achild@raspberrypi:~ $ cat /etc/os-release
PRETTY_NAME=“Raspbian GNU/Linux 12 (bookworm)”
NAME=“Raspbian GNU/Linux”
VERSION_ID=“12”
VERSION=“12 (bookworm)”
VERSION_CODENAME=bookworm
ID=raspbian
ID_LIKE=debian
HOME_URL=“http://www.raspbian.org/”
SUPPORT_URL=“http://www.raspbian.org/RaspbianForums” -
@funkdafied I have just pushed a fix for that… (was a test for text mode or graphical mode)
(and I see I have to expand the test for the Bookworm compositor too,edit: just fixed that too)but it won’t help in your situation…
you cannot run MagicMirror on bookworm successfully on a pi0-w, armv6l
takes too much memoryyou need to use the legacy 32 bit image (bullseye)
-
@sdetweil thank you that worked to a point please have a look at the below with the errors I getting:
-
@funkdafied I cannot recreate this…
try this to increase the timeout
You can extend timeout with those two commands: npm config set fetch-retry-maxtimeout 6000000 npm config set fetch-retry-mintimeout 1000000 enter image description here Source: https://docs.npmjs.com/cli/v9/using-npm/config#fetch-retry-maxtimeout
-
@sdetweil Thank you that did the trick. Only issue I see to be running into at the moment is Midori telling me it can’t find the page it is looking for.
-
@funkdafied ok,
when you run on a device that doesn’t have electron support, it doesn’t get installed via MM as expected…
then my install script changes the startup to use my run-start.sh script
which launches MagicMirror in server mode
and waits for the ready message>>> Ready to go! Please point your browser to: http://0.0.0.0:8080 <<<
and then launches midori like this (with whatever the port number is in the message)
midori http://localhost:8080 -e Fullscreen -e Navigationbar
just for grins can you do
cd ~/MagicMirror npm start server
to see if that message appears
-
@funkdafied I think we solved this on discord
-