Oh, when I tried it with the default “linaro” user it works… :) I used “my own” user at first… Now I’m going to add modules! :)

@Sean what did you put in your mm.sh?
I can’t get the MM to run… I only get errors… :/ I’m on development branch…

got this in the npm-debug.log:

cat npm-debug.log
0 info it worked if it ends with ok
1 verbose cli [ '/usr/bin/nodejs', '/usr/bin/npm', 'start' ]
2 info using npm@3.10.10
3 info using node@v6.11.2
4 verbose run-script [ 'prestart', 'start', 'poststart' ]
5 info lifecycle magicmirror@2.1.3-dev~prestart: magicmirror@2.1.3-dev
6 silly lifecycle magicmirror@2.1.3-dev~prestart: no script for prestart, continuing
7 info lifecycle magicmirror@2.1.3-dev~start: magicmirror@2.1.3-dev
8 verbose lifecycle magicmirror@2.1.3-dev~start: unsafe-perm in lifecycle true
9 verbose lifecycle magicmirror@2.1.3-dev~start: PATH: /usr/lib/node_modules/npm/bin/node-gyp-bin:/home/snille/MagicMirror/node_modules/.bin:/usr/local/bin:/usr/bin:/bin:/usr/local/games:/usr/games
10 verbose lifecycle magicmirror@2.1.3-dev~start: CWD: /home/snille/MagicMirror
11 silly lifecycle magicmirror@2.1.3-dev~start: Args: [ '-c', 'sh run-start.sh' ]
12 silly lifecycle magicmirror@2.1.3-dev~start: Returned: code: 1  signal: null
13 info lifecycle magicmirror@2.1.3-dev~start: Failed to exec start script
14 verbose stack Error: magicmirror@2.1.3-dev start: `sh run-start.sh`
14 verbose stack Exit status 1
14 verbose stack     at EventEmitter. (/usr/lib/node_modules/npm/lib/utils/lifecycle.js:255:16)
14 verbose stack     at emitTwo (events.js:106:13)
14 verbose stack     at EventEmitter.emit (events.js:191:7)
14 verbose stack     at ChildProcess. (/usr/lib/node_modules/npm/lib/utils/spawn.js:40:14)
14 verbose stack     at emitTwo (events.js:106:13)
14 verbose stack     at ChildProcess.emit (events.js:191:7)
14 verbose stack     at maybeClose (internal/child_process.js:891:16)
14 verbose stack     at Process.ChildProcess._handle.onexit (internal/child_process.js:226:5)
15 verbose pkgid magicmirror@2.1.3-dev
16 verbose cwd /home/snille/MagicMirror
17 error Linux 4.4.71+
18 error argv "/usr/bin/nodejs" "/usr/bin/npm" "start"
19 error node v6.11.2
20 error npm  v3.10.10
21 error code ELIFECYCLE
22 error magicmirror@2.1.3-dev start: `sh run-start.sh`
22 error Exit status 1
23 error Failed at the magicmirror@2.1.3-dev start script 'sh run-start.sh'.
23 error Make sure you have the latest version of node.js and npm installed.
23 error If you do, this is most likely a problem with the magicmirror package,
23 error not with npm itself.
23 error Tell the author that this fails on your system:
23 error     sh run-start.sh
23 error You can get information on how to open an issue for this project with:
23 error     npm bugs magicmirror
23 error Or if that isn't available, you can get their info via:
23 error     npm owner ls magicmirror
23 error There is likely additional logging output above.
24 verbose exit [ 1, true ]

Mmmm… I’m thinking MinnowBoard Turbot… Maybe? :)

Just got mine as well. :)
Here you can find the OS (and other stuff), if someone else is looking.
Tinker Board Software

@rcollie I’m on develop branch and I’m using this to be able to access the mirror from anywhere (inside my network). I had to add the “address: “0.0.0.0”.” some time ago… :)

var config = {
	port: 8080,
	ipWhitelist: [],
	address: "0.0.0.0",
...

Try it… :)

@sithas

Easiest fix:
Replace those files with their defaults and then run the update.

You can also “stash” your changes with git stash -u
Then if you want you can reapply your changes again after updating with git stash pop

Or, you can just “kill” the changes with git clean -f
But then you WILL loose what you have edited in the files for ever!

@Mykle1 Here is my full “list”. :)

processor       : 0
model name      : ARMv7 Processor rev 4 (v7l)
BogoMIPS        : 76.80
Features        : half thumb fastmult vfp edsp neon vfpv3 tls vfpv4 idiva idivt vfpd32 lpae evtstrm crc32
CPU implementer : 0x41
CPU architecture: 7
CPU variant     : 0x0
CPU part        : 0xd03
CPU revision    : 4

processor       : 1
model name      : ARMv7 Processor rev 4 (v7l)
BogoMIPS        : 76.80
Features        : half thumb fastmult vfp edsp neon vfpv3 tls vfpv4 idiva idivt vfpd32 lpae evtstrm crc32
CPU implementer : 0x41
CPU architecture: 7
CPU variant     : 0x0
CPU part        : 0xd03
CPU revision    : 4

processor       : 2
model name      : ARMv7 Processor rev 4 (v7l)
BogoMIPS        : 76.80
Features        : half thumb fastmult vfp edsp neon vfpv3 tls vfpv4 idiva idivt vfpd32 lpae evtstrm crc32
CPU implementer : 0x41
CPU architecture: 7
CPU variant     : 0x0
CPU part        : 0xd03
CPU revision    : 4

processor       : 3
model name      : ARMv7 Processor rev 4 (v7l)
BogoMIPS        : 76.80
Features        : half thumb fastmult vfp edsp neon vfpv3 tls vfpv4 idiva idivt vfpd32 lpae evtstrm crc32
CPU implementer : 0x41
CPU architecture: 7
CPU variant     : 0x0
CPU part        : 0xd03
CPU revision    : 4

Hardware        : BCM2835
Revision        : a02082
Serial          : x

@ceddirr I saw your questions about the project… Answers below. :)

First, I forgot to say thank you for your kind words!

Question: “Which order is it? At first the IR frame, then the one way mirror, and finally the screen, is it correct?”

Answer: Correct, from the “front” the IR-Frame is first, placed directly on to the mirror and behind the mirror sits the screen. :)

Question: “I can see that the custom css of the MMM-Memo is already written in css file from the module’s folder. But, how do you manage to use it, and have this look with your memos? Mine are just white and simple… Thank you =)”

Answer: Well, I’m actually not doing so much in the CSS file. The only thing I set in the custom.css is the size of the Memo. The rest is “built in”.

This is the CSS part (in my custom.css file):

/* MMM-Memo -----------------------------------------*/
.MMM-Memo .small {
	font-family: "Roboto Condensed", sans-serif;
}
.note {
  width: 500px;
  height: 200px;
}
/*****************************************************/

And this is in my config.js:

{
	module: "MMM-Memo",
	position: "upper_third",
	classes: "default everyone",
	config: {
		memoTitle: "Flyginformation",
		memoDisplayIfEmpty: false,
		memoRotation: -4,
		format: "YYYY-MM-DD - HH:mm",
		memoWidth: 500,
		memoDisplayHeader: true,
		memoDisplayDuration: true,
		memoDisplayId: true,
		memoColorBackground: "LightGoldenrod",
		memoDisplayNotification: true,
	}
},

You can see all the options for the config on the MMM-Memo’s git.
There are lot’s and lot’s of options for colors and themes. :)

@Mykle1 Lets see…
Do (in SSH): cat /proc/cpuinfo

Paste the result from hardware and revision… :)

Hardware        : BCM2835
Revision        : a02082

I think it’s the “last” revision that is important.

Pi 3 Model B	1GB	a02082 (Sony, UK)
Pi 3 Model B	1GB	a22082 (Embest, China)

More info about revisions…

Mine is from UK it seams. :)

@Mykle1 Don’t worry about it. You provided the information. :) But if you want to do it anyway, do it via SSH instead, you need to have more “screen-space” to fit all the information at the same time. Check my screenshot. The number of columns and rows are much higher. :)