Read the statement by Michael Teeuw here.
First start from the mirror does not work
-
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.