Read the statement by Michael Teeuw here.
cannot get Raspberry pi 2 to run
-
Super frustrating experience trying to get MagicMirror up and running on a raspberry pi model 2 b. I tried to do the manual installation and got the error:
curl -sL https://deb.nodesource.com/setup_16.x | sudo -E bash - ## Installing the NodeSource Node.js 16.x repo... ## You appear to be running on ARMv6 hardware. Unfortunately this is not currently supported by the NodeSource Linux distributions. Please use the 'linux-armv6l' binary tarballs available directly from nodejs.or >So I went ahead and ran the script below:
bash -c "$(curl -sL https://raw.githubusercontent.com/sdetweil/MagicMirror_scripts/master/raspberry.sh)"Everything seemed to work well and I get the message below.
[PM2] Saving current process list... [PM2] Successfully saved in /home/pi/.pm2/dump.pm2 Do you want to disable the screen saver? (y/N)?y We're ready! Run pm2 start MagicMirror from the ~/MagicMirror directory to start your MagicMirror.when I type ‘pm2 start MagicMirror’ It says process started successfully, displays the table with id, name, node, etc and then just returns the prompt. Nothing happens. I’m super frustrated. I am going through all this due to a corrupted SD card but I didn’t have this kind of trouble getting it to work originally
I appreciate any help.
-
@sdetweil OK So I went ahead and did the whole thing over again for the fourth time with the exact method you outlined. It works. It would be nice to somehow let the next poor sod who wants to waste 2 days of their life of the right way to do this on a pi2.
-
@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
-
@sdetweil ```
No LSB modules are available.
Distributor ID: Raspbian
Description: Raspbian GNU/Linux 11 (bullseye)
Release: 11
Codename: bullseye -
@theaddies yep, can’t run bullseye on armv6l
must be the legacy image, buster
SOOO
reflash SD card w buster and run install againchromium is compiled for armv7, so instructions armv6 doesn’t have, this illegal instruction error
need to add another test to install
-
@sdetweil Oh wow. Sorry for all the trouble. What a pain.
-
@theaddies no worries.
I’ll update install to end if not buster on armv6l,
then u would have known -
@sdetweil Thanks for all the help. I have several pi4s I just want to use the model 2 because the mirror is a perfect application for the older computer.
-
@theaddies understood
-
@sdetweil After I run the install script, what do I do. Since the script disables the screen saver and configures the Mirror to autostart I thought I would not need to do anything else. However, pm2 status all reveals that there is nothing running. I run pm2 status all and it is blank.
I am not sure if I should follow the process in the link below.
https://howchoo.com/g/ntcymzbimjv/how-to-install-magic-mirror-on-your-raspberry-piWhen I reboot the mirror I get the magicmirror2 logo showing up and it seems to be booting up but then the screen goes blank and I have nothing. It is almost like it reboots the pi.
-
@theaddies send me the ~/install.log
and do the same chromium
and
./run-start.sh
testslsb_release -a
to confirm buster
-
@theaddies you should not need to do anything. it should be setup to autostart
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