Pi 2 model B v 1.2 doesn't run provided image.

[twodeeman]

I tried flashing the "highly recommended" raspbian image (alarmdecoder-raspbian-2016-04-29.img) downloaded from alarmdecoder.com on a Pi 2 model B v 1.2 and I get the 4-fast/4-slow blink failure to boot. So disappointing.

Yes I did unzip it.
Yes I used Etcher on a Mac to flash it to a 32g card. It passed the read-verify test. I tried twice. No joy.

--
n

[kevin]

Please make sure the hashes of the file you downloaded matches the one on the server, that it is indeed a valid copy of the image.

Also, if that is good, please hook a monitor up during the boot process and see what the problem is. Last known status on this was working as intended, but haven't sold pi 2's in quite some time.

[twodeeman]

<sigh!> Yes the MD5 sum of the downloaded zip (ce5a33fe64535b8ecf526e6e5c9bf356) matches the sum given on the download page.

With a monitor attached, all you see is the rainbow pinwheel. Four slow, four fast blinks on the LED. So I'm thinking this "highly recommended" image doesn't work on my new Pi 2B, and I've read elsewhere that it doesn't work on the Pi 3. I'm wondering what _does_ it work on?

I guess I need to do a manual install, but installation instructions scattered on your site don't seem to be consistent with respect to the current version of Raspian. It looks like I'm in for a bit of a slog. I imagine I'll figure it all out eventually, but I'm disappointed. I guess I was expecting something a little more plug-n-play.

Can you point me to installation instructions known good for the latest Raspian Stretch 4.9.59-v7? Or am I on my own?

--
C

[kevin]

It absolutely works on the pi3, you've read old information. The fact it's not working on a pi2 is also news to me - the red pinwheel usually indicates power issues by the way. Just to verify, you have ad2pi powered from panel... you also need to power the raspberry pi from the wall or battery bus via the USB header. I have this exact image running on a pi3 myself. Pi2 hasn't been tested in quite some time because there has been absolutely no reason to purchase pi2's after the pi3 came out - however, it really should still just work. I know the office alarmdecoder at nu tech is on a pi2 currently.

The manual install instructions for the project on github are the latest, but I'd recommend using the docker stuff going forward.

Sorry you are having such a rough time, but I think this would come up more often if it were a problem - many thousands of people are using this exact image.

If you've verified power and it still doesn't work, maybe your flash to the sd card is going poorly. Never used Etcher, no idea what it is. Recommend to use "dd" if using unix derivatives.

[twodeeman]

Power is from a 3A brick. I'm not in the panel yet. No problem booting vanilla raspian images. I actually used dd the first try, then switched to Etcher since it does a nice verify pass. I tried different sd cards -- cards that work fine with other images. No, I really do think that your image doesn't work in a Pi 2 model B v 1.2

As far as the reason to use this 2B 1.2 board rather than a 3 ... ummm... power requirements? Cooling? Price?

I read that the 'recommended' image doesn't work on the 3 in this very forum. Maybe the issue was fixed since that post. You can search for it. I get exactly the same problem: 4-slow/4-fast blinks and a rainbow pinwheel on the HDMI.

Regarding the github instructions, using an unmodified Raspian image, the make on step 8 fails with

src/event/ngx_event_openssl.c: In function ‘ngx_ssl_session_ticket_key_callback’:
src/event/ngx_event_openssl.c:2673:9: error: ‘RAND_pseudo_bytes’ is deprecated [-Werror=deprecated-declarations]
RAND_pseudo_bytes(iv, 16);
^~~~~~~~~~~~~~~~~
In file included from /usr/include/openssl/engine.h:19:0,
from src/event/ngx_event_openssl.h:22,
from src/core/ngx_core.h:73,
from src/event/ngx_event_openssl.c:9:
/usr/include/openssl/rand.h:47:1: note: declared here
DEPRECATEDIN_1_1_0(int RAND_pseudo_bytes(unsigned char *buf, int num))
^
cc1: all warnings being treated as errors
objs/Makefile:767: recipe for target 'objs/src/event/ngx_event_openssl.o' failed
make[1]: *** [objs/src/event/ngx_event_openssl.o] Error 1
make[1]: Leaving directory '/home/alarm/src/nginx-1.7.4'
Makefile:8: recipe for target 'build' failed
make: *** [build] Error 2

I'll probably figure this out eventually, but it's an unexpected slog. I thought this would be plug-n-play with a pre-built image or a simple install process.

--
C

[twodeeman]

The build problem seems related to OpenSSL. With -Werror removed the build dies here

src/event/ngx_event_openssl.c: In function ‘ngx_ssl_dhparam’:
src/event/ngx_event_openssl.c:862:11: error: dereferencing pointer to incomplete
type ‘DH {aka struct dh_st}’
dh->p = BN_bin2bn(dh1024_p, sizeof(dh1024_p), NULL);
^~
src/event/ngx_event_openssl.c: In function ‘ngx_ssl_handshake’:
src/event/ngx_event_openssl.c:1081:31: error: dereferencing pointer to incomplet
e type ‘SSL {aka struct ssl_st}’
if (c->ssl->connection->s3) {
^~
src/event/ngx_event_openssl.c: In function ‘ngx_ssl_connection_error’:
src/event/ngx_event_openssl.c:1817:21: error: ‘SSL_R_NO_CIPHERS_PASSED’ undeclar
ed (first use in this function)
|| n == SSL_R_NO_CIPHERS_PASSED /* 182 */
^~~~~~~~~~~~~~~~~~~~~~~
s

--------------------

Sigh!

--
C

[twodeeman]

The manual install instructions for the project on github are the latest, but I'd recommend using the docker stuff going forward.

Since I can't seem to build the version of nginx the github instructions want me to build, maybe I should try the standard nginx package?

What's this "docker stuff" you refer to?

--
C

[twodeeman]

By the way, step 13 in the github instructions seems bad

sudo cp /opt/alarmdecoder-webapp/contrib/nginx/nginx.service /lib/systemd/system/nginx.service

I mean, in a vanilla install, there won't be any alarmdecoder-webapp in the /opt directory till step 18.
So step 13 is obviously misplaced.

Also, git wasn't in my vanilla raspian, so perhaps it should be added to the list in step 1

--
C

[kevin]

I get it, I'm just trying to help. If you're having such issues I apologize, maybe you can try emailing support and one of the actual staff can help you out. I know last I tried the image it worked fine on all versions of raspberry pi - including the one in my own home (pi 3).

The docker stuff can also be found on github under the nutechsoftware set of repositories if you want to try going that route.

And yes, it does look like a couple of the instructions are misplaced. Regarding the OpenSSL stuff, make sure you've also installed openssl-dev packages along with openssl

[twodeeman]

Thanks for your comments.

Yeah, I guess I'll try contacting support. I battled to the end of the install instructions, but gunicorn didn't start. There were a bunch other things needing some tweeks. I may be the first person who has has tested these installation instructions for the latest Raspian that has bothered to post here.

And I may be the only person who's tried running this on a Pi 2B-1.2 It's a relatively new board, but it's a year old. I figured that would be safe, but I guess the image hasn't been updated since before this version of the Pi was released.

The hardware seems solid. I tried installing the board in a panel and I can connect to ad2pi serial line using cu and see the alarm messages, so that's solid. I just wish there was a quick way to get the web app working.

Oh well, it's always something.

--
C