Read the statement by Michael Teeuw here.
cannot get Raspberry pi 2 to run
-
@theaddies armv6 is slow. could be 3 minutes til mm comes up.
can you show me the output of
pm2 logs --lines=50the script should have modified package.json start clause to be ./run-start.sh
no electron is available for armv6 anymore, so I try to launch chromium.
also send me the ~/install.log
sane userid at gmail -
@sdetweil It is slow, but I have been working on this for 12 hours so there is ample time for something to have worked.
pi@raspberrypi:~ $ pm2 logs --lines=50 [PM2] Spawning PM2 daemon with pm2_home=/home/pi/.pm2 [PM2] PM2 Successfully daemonized [TAILING] Tailing last 50 lines for [all] processes (change the value with --lines option) /home/pi/.pm2/pm2.log last 50 lines: PM2 | 2023-04-07T18:26:05: PM2 log: App [MagicMirror:0] online PM2 | 2023-04-07T18:26:45: PM2 log: App [MagicMirror:0] exited with code [0] via signal [SIGINT] PM2 | 2023-04-07T18:26:45: PM2 log: App [MagicMirror:0] starting in -fork mode- PM2 | 2023-04-07T18:26:45: PM2 log: App [MagicMirror:0] online PM2 | 2023-04-07T18:27:25: PM2 log: App [MagicMirror:0] exited with code [0] via signal [SIGINT] PM2 | 2023-04-07T18:27:25: PM2 log: App [MagicMirror:0] starting in -fork mode- PM2 | 2023-04-07T18:27:25: PM2 log: App [MagicMirror:0] online PM2 | 2023-04-07T18:28:09: PM2 log: App [MagicMirror:0] exited with code [0] via signal [SIGINT] PM2 | 2023-04-07T18:28:09: PM2 log: App [MagicMirror:0] starting in -fork mode- PM2 | 2023-04-07T18:28:09: PM2 log: App [MagicMirror:0] online PM2 | 2023-04-07T18:28:57: PM2 log: App [MagicMirror:0] exited with code [0] via signal [SIGINT] PM2 | 2023-04-07T18:28:57: PM2 log: App [MagicMirror:0] starting in -fork mode- PM2 | 2023-04-07T18:28:57: PM2 log: App [MagicMirror:0] online PM2 | 2023-04-07T18:29:49: PM2 log: App [MagicMirror:0] exited with code [0] via signal [SIGINT] PM2 | 2023-04-07T18:29:49: PM2 log: App [MagicMirror:0] starting in -fork mode- PM2 | 2023-04-07T18:29:49: PM2 log: App [MagicMirror:0] online PM2 | 2023-04-07T18:30:28: PM2 log: App [MagicMirror:0] exited with code [0] via signal [SIGINT] PM2 | 2023-04-07T18:30:28: PM2 log: App [MagicMirror:0] starting in -fork mode- PM2 | 2023-04-07T18:30:28: PM2 log: App [MagicMirror:0] online PM2 | 2023-04-07T18:31:08: PM2 log: App [MagicMirror:0] exited with code [0] via signal [SIGINT] PM2 | 2023-04-07T18:31:08: PM2 log: App [MagicMirror:0] starting in -fork mode- PM2 | 2023-04-07T18:31:09: PM2 log: App [MagicMirror:0] online PM2 | 2023-04-07T18:31:48: PM2 log: App [MagicMirror:0] exited with code [0] via signal [SIGINT] PM2 | 2023-04-07T18:31:48: PM2 log: App [MagicMirror:0] starting in -fork mode- PM2 | 2023-04-07T18:31:49: PM2 log: App [MagicMirror:0] online PM2 | 2023-04-07T18:32:28: PM2 log: App [MagicMirror:0] exited with code [0] via signal [SIGINT] PM2 | 2023-04-07T18:32:28: PM2 log: App [MagicMirror:0] starting in -fork mode- PM2 | 2023-04-07T18:32:28: PM2 log: App [MagicMirror:0] online PM2 | 2023-04-07T18:33:09: PM2 log: pm2 has been killed by signal, dumping process list before exit... PM2 | 2023-04-07T18:33:09: PM2 log: Deleting process 0 PM2 | 2023-04-07T18:33:09: PM2 log: Stopping app:MagicMirror id:0 PM2 | 2023-04-07T18:33:10: PM2 log: App [MagicMirror:0] exited with code [0] via signal [SIGTERM] PM2 | 2023-04-07T18:33:12: PM2 log: pid=10286 msg=process killed PM2 | 2023-04-07T18:33:12: PM2 log: Exited peacefully PM2 | 2023-04-07T18:36:32: PM2 log: =============================================================================== PM2 | 2023-04-07T18:36:33: PM2 log: --- New PM2 Daemon started ---------------------------------------------------- PM2 | 2023-04-07T18:36:33: PM2 log: Time : Fri Apr 07 2023 18:36:33 GMT-0400 (Eastern Daylight Time) PM2 | 2023-04-07T18:36:33: PM2 log: PM2 version : 5.3.0 PM2 | 2023-04-07T18:36:33: PM2 log: Node.js version : 16.13.0 PM2 | 2023-04-07T18:36:33: PM2 log: Current arch : arm PM2 | 2023-04-07T18:36:33: PM2 log: PM2 home : /home/pi/.pm2 PM2 | 2023-04-07T18:36:33: PM2 log: PM2 PID file : /home/pi/.pm2/pm2.pid PM2 | 2023-04-07T18:36:33: PM2 log: RPC socket file : /home/pi/.pm2/rpc.sock PM2 | 2023-04-07T18:36:33: PM2 log: BUS socket file : /home/pi/.pm2/pub.sock PM2 | 2023-04-07T18:36:33: PM2 log: Application log path : /home/pi/.pm2/logs PM2 | 2023-04-07T18:36:33: PM2 log: Worker Interval : 30000 PM2 | 2023-04-07T18:36:33: PM2 log: Process dump file : /home/pi/.pm2/dump.pm2 PM2 | 2023-04-07T18:36:33: PM2 log: Concurrent actions : 2 PM2 | 2023-04-07T18:36:33: PM2 log: SIGTERM timeout : 1600 PM2 | 2023-04-07T18:36:33: PM2 log: =============================================================================== -
@sdetweil Log file sent.
-
@theaddies got the log,let’s try this
in terminal window, pm2 stop all
cd ~/MagicMirror ./run-start.sh -
@sdetweil I get this.
Ready to go! Please point your browser to: http://localhost:8080 Starting chromium browser now, have patience, it takes a minute ./run-start.sh: line 147: 1281 Illegal instruction "$b" -noerrdialogs -kiosk -start_maximized --new-window --site-per-process --no-zygote --no-sandbox --disable-infobars --app=http://localhost:$port --ignore-certificate-errors-spki-list --ignore-ssl-errors --ignore-certificate-errors --user-data-dir=$r 2> /dev/null -
@theaddies The way I want to run the mirror is that it automatically opens and displays the mirror at boot. I sometimes see things for serveronly and I am not sure if that is what is being configured. I don’t think that is what I want.
-
@theaddies ok, a little more info
type in terminal window
which chromium
which chromium-browserthey should return the file path to one of those
whichever gives a path copy paste that in the terminal window
and see if it will start
I’ve never seen a pi 2, but this all works on pi 0w, also armv6l
-
@theaddies because there is no electron browser anymore for armv6l
I change the setup to serveronly, and then launch chrome browser over the server. you get the same result
-
/usr/bin/chromium-browser Illegal Instruction -
@theaddies ok, so there is that problem
oh, which raspi os image are you using?
MUST be the legacy image, 32 bit
lsb_release - a
will tell us
if buster is legacy
