some new RPI-3 boards failing to work

This is because the scheme we're using to determine the model of Pi (2 or 3) in use is too simple, and fails to catch cases of new revisions. An example from a new RPI3 (courtesy of T. Rasmussen):

cat /proc/cpuinfo
...
Hardware    : BCM2709
Revision    : a32082
Serial      : 00000000917fcbad

So revision a32082 is also an RPi-3. But our hostname generation script has this lovely bit of code:

       RPI_ID=`cat /proc/cpuinfo | /bin/grep Serial | /bin/sed -e 's/.*: //; s/^........//;s/^\(....\)/\1====/'  | tr [:lower:] [:upper:]`
        REVISION=`cat /proc/cpuinfo | /bin/grep Revision | /bin/sed -e 's/.*: //'`
        ## get model from revision;
        ## see https://www.element14.com/community/community/raspberry-pi/blog/2016/11/21/how-to-identify-which-model-of-the-raspberry-pi-you-have
        case $REVISION in
            a01040|a01041|a21041|a22042)
                MODEL=RPI2
                ;;
            a02082|a22082)
                MODEL=RPI3
                ;;
            *)
                MODEL=RPI?
                ;;
        esac

Going forward, we should default to RPI3 until we hear of other revisions which are not RPI3. This will require a small update.

jbrzusto / sensorgnome

some new RPI-3 boards failing to work #55