Hello, My camera module v2 is connected to a Pi Model B running Raspbian Jessie and motion. Randomly, some images it takes are fine, like this one: goodcolor2.jpg :) But more often they are not, like this one. This snowy day is an extreme example, but most exterior shots have this problem. badcolor2...

Does your network really need to be ad hoc?

cyberfantome, what environment is your PI in? If it's only exposed to your home subnet behind a firewall things are pretty simple. If it's exposed to the internet there are more considerations.

This command will install it: sudo apt-get install firmware-ralink

The simplest solution is usually the best, and in the case of wireless that means the 802.11b/g/n standard. See http://elinux.org/RPi_VerifiedPeripherals for lots of wireless hardware that works with the Pi.

You can be sure of one thing about a spinning disk drive--eventually it will fail. For the 64GB you mention, flash is also more economical.

The Pi needs an SDHC card as its boot disk, so consider putting a 64GB SDHC card in the Pi instead of an extra USB drive.

I did not find out why /etc/init.d/vncboot would not run at boot time, but here's a workaround. To start it at boot time add the following line to /etc/rc.local:

sudo service vncboot start

Thanks for your reply, Dougie. I'm using the init.d script from http://elinux.org/RPi_VNC_Server#Run_at_boot . As you suggested I ran sudo update-rc.d vncboot start 99 2 3 4 5 . stop 19 0 1 6 . which returned update-rc.d: using dependency based boot sequencing insserv: warning: current start runleve...

I'm experiencing the same issue as deavmi. I ran the same two update-rc.d commands he mentioned with the same results. vncserver did not start at boot time, so I put a couple of echo statements in the vncboot script and found that it is just not being executed then. But once the Pi is up and running...