Read the statement by Michael Teeuw here.
YAPi0 Installer Stretch Lite
-
pi@RasPiZeroW:~ $ cd ~/MagicMirror/ pi@RasPiZeroW:~/MagicMirror $ pm2 stop 0 [PM2] Applying action stopProcessId on app [0](ids: 0) [PM2] [MagicMirror](0) ✓ ┌─────────────┬────┬─────────┬──────┬─────┬─────────┬─────────┬────────┬─────┬────────┬──────┬──────────┐ │ App name │ id │ version │ mode │ pid │ status │ restart │ uptime │ cpu │ mem │ user │ watching │ ├─────────────┼────┼─────────┼──────┼─────┼─────────┼─────────┼────────┼─────┼────────┼──────┼──────────┤ │ MagicMirror │ 0 │ 2.8.0 │ fork │ 0 │ stopped │ 31 │ 0 │ 0% │ 0 B │ pi │ disabled │ └─────────────┴────┴─────────┴──────┴─────┴─────────┴─────────┴────────┴─────┴────────┴──────┴──────────┘ Use `pm2 show <id|name>` to get more details about an app pi@RasPiZeroW:~/MagicMirror $ npm start > magicmirror@2.8.0 start /home/pi/MagicMirror > sh run-start.sh /home/pi/MagicMirror/node_modules/electron/dist/electron: error while loading shared libraries: libgtk-3.so.0: cannot open shared object file: No such file or directory npm ERR! code ELIFECYCLE npm ERR! syscall spawn npm ERR! file sh npm ERR! errno ENOENT npm ERR! magicmirror@2.8.0 start: `sh run-start.sh` npm ERR! spawn ENOENT npm ERR! npm ERR! Failed at the magicmirror@2.8.0 start script. npm ERR! This is probably not a problem with npm. There is likely additional logging output above. npm ERR! A complete log of this run can be found in: npm ERR! /home/pi/.npm/_logs/2019-09-25T17_26_03_649Z-debug.log pi@RasPiZeroW:~/MagicMirror $
-
you MUST install the graphical UI desktop on the pi, right? MM uses graphics to display the screen.
-
hmm, I guess I have to investigate about this in a few weeks.
So far many thanks for your help here. Will have a look later today and see what can I handle. Otherwise later. I have to run for a meeting now.
-
@sdetweil said in YAPi0 Installer Stretch Lite:
graphical UI desktop on the pi
I wonder. I understood Pi0 don’t need to have UI installed. therefor I installed the light raspbian image - maybe I’m wrong :confounded_face:Do I have to install lightdm or other?
And then I assume use raspi-config to boot to desktop?
-
@bdream you can do node serveronly , instead of npm start…
for pm2, edit installers/mm.sh and change npm start to node serveronly
then pm2 restart 0
others have had success at running UI on p0 as well…
make sure u change config/config.js to allow other machines to connect
to allow alladdress: “”,
and
ipWhitelist: [], -
Í’m back now and started to work further on my Pi0 with MM installation.
I tried to get UI desktop running by installing lightdm.
Then reconfigured Boot option to start Desktopn and Auotologin.
After reboot, wich looks good, PI starts an give Debian logon screen.How to autologon?
After I put in my credentials pi and raspberry I stuck in login-loop.
-
Any idea what to do?
Maybe Pi0 is not the Hardware MM will run good. Especialy in regards to upcoming updates :dizzy_face:
But this small device will give more oportunities for nice looking projects based on MM :grinning_face_with_smiling_eyes: -
@bdream others have made it work… you may have to reinstall the base raspian image to get the graphical desktop running properly…
I don’t have one of these pi0 devices to test with
-
@sdetweil many thanks for your guidance.
I thaught Pi0 must get installed without GUI :worried_face: my fault.
I will start again and see what happen.
I’ll let you know if success yur script! -
@bdream U can run it in serveronly mode
Have to edit the installers/mm.sh
Or run_start.sh to donode serveronly
The use browser from some other system