Read the statement by Michael Teeuw here.
First start from the mirror does not work
-
Hi I am having this same issue. Did you ever get it working?
-
Maybe I’m missing something here, but it seems you try to run
npm startfrom a remote shell. That does not work since it doesn’t know on which screen to start. Try:DISPLAY=:0 npm start -
@MichMich Hi! I am running npm start directly on the pi, and I get the same exact error.
-
-
Interesting as I didn’t have to do that as a separate step. However, as I posted in a different thread yesterday, keeping the base software on your Raspberry Pi is important.
-
Mhh maybe we should add those dependencies and/or
apt-get upgradeto the installer script? -
I vote no because that’s outside the scope of MM. However, we could adjust the installer to pause and ask the user if they have performed an update/upgrade on their base rpi before continuing on with the MM install. This gives the user an opportunity to exit the installer and do the requires prerequisites before returning to the installer (at which point they can then say ‘yes’ to the question.)
-
@KirAsh4 I did the manual install for mine anyways, but I could have sworn I did an update / upgrade but I may be wrong.
Maybe it’s something that can just be added to the install instructions as a small note.
-
You know, I have a spare rpi-3 sitting at home. I’ll wipe it clean and start fresh when I get home later and see if I run into issues. All in the name of science!
-
@KirAsh4 haha alright go for it! Let us know what comes of it.
-
Will do. Right after I inspect the 3D print that I left going since last night, and I start the next print. And after I swap a laptop with a friend. And after I have dinner. And after I help another friend with their phone. And after i do some laser cutting of mock up pieces for an art piece. And after I dig up the electronic bits I need for a kid’s costume. And after I … and after … and … oh you’ll hear from me some time in 2036. Really, I promise.
(Is there ever such a thing as having too many projects going at the same time?)
-
@KirAsh4 Haha I know that feeling!
-
Ok, I finally had time last night to run through a complete setup and install, from taking the rpi out of its box to having MM up and running. I did not have to manually install any of the aforementioned packages. Which makes me wonder, @EoF, were you running the full Jessie distribution, or Jessie-Lite? If it’s Jessie-Lite, you would’ve had to install a lot more than just those few pieces as it does not come with an X-server.
Anyway, I’ll have a step-by-step tutorial written up soon …hmm, let’s check calendar … oh yeah, some time in 2036.
-
@KirAsh4 Hi! Glad you finally got around to testing this! I did in fact use the lite version of Jessie, so that would explain it then.
-
Right, the lite version wouldn’t have any of those packages installed, nor would it have an X-server, so you would’ve had to do that yourself. :)
-
I had the same erorr and I did use the full Jessie distribution. In my case “npm start” showed the same error but the problem was before at “npm install”.
I never really took the time to watch the entire npm install routine, because it took a while. I had my rasbperry connected via usb on my tv. And while running npm install it rebooted! So in my case it was caused by an inadequate power supply. Switched to a plug and everything worked fine.
Perhaps somebody runs into the same error like me.
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