To enable motion to run as a daemon on startup do the following:
and change start_motion_daemon=no to start_motion_daemon=yes
Next enable motion by entering the following at the command line:
sudo systemctl enable motion
You can confirm motion is running by checking the output from the following command:
The B+ had a single core Broadcom BCM2835 Arm 6, with 512MB of RAM.
the Raspberry Pi 2 (is newer) has a quad core BCM2836 Arm 7, with 1GB of RAM. As a result of the quad core CPU the Raspberry Pi 2 has a higher current draw.
Adafruit put together a nice comparison of the two, that includes a section detailing how to tell them apart.
Yes, all of the B+'s GPIO pins have internal pull-up or pull-down resistors that can be controlled from your code.
Pull-up is 50K min – 65K max.
Pull-down is 50K min – 60K max.
More info on the GPIO can be found here and here.
Example usage frm the PI4J documentation:
// provision gpio pin #02 as an input pin with its internal pull down resistor enabled
Turns out the file is now called alsa.conf and is found in /usr/share/alsa.
Changed the lines
to card 1 and that's me up and running. Looks like others have different problems with other sound cards so worth looking at other solutions too. Found some good suggestions (including my solution) here:
I did a little digging on this and tracked down the purpose for most of the user groups:
pi User-specific group. A group is automatically created for
each new user; you can ignore this.
adm Allows access to log files in /var/log and using xconsole
dialout Allows access to serial ports/modem reconfiguration, etc.
cdrom Uncreatively, ...
This should be able to be fixed by either providing the FTP credentials in your wp-config.php file (in the root directory of the Wordpress install) or by changing ownership of the Wordpress install. I recommend the changing ownership option.
On my Debian WordPress server (not Raspbian, but regular Debian Wheezy), my entire installation ...
I have eight pi3s in a room which is 22-24°C. They range in temperature between ~45°C and ~50°C when idle, with each pi being fairly consistent in temperature +-2°C (sorry, not terribly accurate values, they are from squinting at a plot). Mine aren't in any kind of enclosure, but are mounted on the underside of a plate with reasonably free air flow.
So your ...
If more is better the Pi2 clearly wins. Double size of RAM (1 GB vs. 512 MB) could make the difference for demanding applications.
The Pi2's quad-core CPU @ 900 MHz vs. single-core CPU @ 700 MHz, obviously provides more computational power. The blog @ RPi.org claims an performance increase up to 6x (expect that value highly dependent on the application).
The Pi2 has four cores, see https://www.raspberrypi.org/products/raspberry-pi-2-model-b/
The B+ (like all the other Pis apart from the Pi2) has a single core, see https://www.raspberrypi.org/products/raspberry-pi-1-model-b/
Presuming you are referring to Raspbian, the same SD card should work unless you have removed kernel.img from the boot partition and/or corresponding directories from /lib/modules.
If you are referring to an OS that is Pi 2/3 only (e.g., various forms of Ubuntu) then no, it will not work on a B+.
Also, if you have specified a specific kernel in /boot/...
Your problem is probably due to the fact that you pulled the plug on the RPi while it was busy doing something important. In general, it's a bad idea to pull the plug on any computer, including the RPi.
Your SD card is displaying a small capacity in Windows, because of the way Windows works. On removable media, Windows will only ever display the first ...
As of the time of this writing, there are no Guinness World Records related to the Raspberry Pi. There are a few about Linux in general, but I was unable to find anything that contained raspberry pi or raspbian.
Search for yourself: http://www.guinnessworldrecords.com/search
It sounds like it could be an issue with your SD card. The size discrepancy in Windows is expected because of how the Raspberry Pi OS formats the SD card (most of it isn't visible to Windows). The Windows Chkdsk would only scan the partitions it can see, so the Linux partition could still be corrupted. Your Pi hardware is most likely fine though.
I have a RPI3 with a mini heatsink, like the following image:
Both heat sinks (14x14x11 mm and 9x9x12 mm) are made of aluminium and the fan is a SEPA MF15B-05 (15x15x5mm, 5V-0.06A) that is soldered to the printed circuit board (so it is permanent :P)
So the iddle temperature with Raspbian Lite, WIFI connection and SSH active connection is about ~37°C in a ...
I have downloaded most of centos 7 img from : http://mirror.centos.org/altarch/7/isos/i386/
That will not work. "i386" refers to the Intel 80386 instruction set architecture (ISA). This was the prevailing 32-bit ISA used by chip makers like Intel, AMD and IBM until the development of the x86-64 (aka. AMD64) ISA now used in most personal computers.
Straight to the point: none.
You can get maybe half-decent performance with Razdroid AKA CyanogenMod that's been ported to the first generation Pis (B+, B, A+, etc.). Usable, but not decent at all (for my standards). The cursor itself jumps around.
For decent performance, try to get a Pi 2. Android works with Berryboot. Just a bit of lag especially on ...
I've had various flavours of pi tucked behind my tv running kodi for years now, upgrading whenever a new model turns up. The biggest differences you're likely to notice moving between the pi A/B -> A+/B+ -> pi 2 -> pi 3 are the performance of the graphics (faster, slicker menus), and the performance of the scraping system. The scraping part is a much bigger ...
I have Kodi running (as part of OpenELEC) on a Raspberry Pi model B (not the +) and it does just fine, including playing Blue-Ray videos over the network. So the answer is: yes, it will run fine - however, if you install Kodi on a "normal" raspbian installation there is more overhead than running it as part of the immensely tuned OpenELEC.
Phone power supplies are not as reliable as dedicated switching power supplies. You can buy a switching power supply for the rPi for very little money (this one for example). A powered hub might work, but depending on the hub you might get feedback issues. A separate, well spec-ed power supply (at least 1.5A for rPi. 2A for rPi2) is the best way to go.
There's this, but it's pretty hard to beat a regular breadboard for prototyping. If you don't want to use all the pins or a ribbon cable you could just get a bunch of these to make individual connections with no soldering. You can also first make your circuit up on a breadboard, and when you get it how you want it make a permanent board, which would be light ...
It's always worth double checking the connections if a circuit doesn't work.
Remember that you also need to connect a Pi ground to an external device you want to control from a Pi GPIO. WIthout the ground there will be no return path for the control signal.
Have you tried using http://www.noip.com/ 's dynamic vpn service? Just install noip2 on your pi, follow the instructions on the website, forward port 22 on your router, and voila you have a domain that allows points to your dynamic ip at home.
You don't mention which GPS module you have, so I can not provide a definitive yes, but given the right GPS module it is possible using the UART (tx/rx pins). Another alternative depending on your module is to use one of the USB ports (either directly connected for modules that have a usb cable or via a USB to TTL cable). Adafruit has a complete tutorial ...
If you are connecting pin 4 (5v) to ground pressing the button is shorting your power supply.
The power supply will then shutdown and cut power to the Pi -- killing your ssh connection.
Then it reboots after you release the button and you can repeat the process.
If you want GPIO 4 I think that is pin 7.
According to the Adafruit site "The basic form-factor of the Pi 2 Model B is nearly 100% the same as the Pi model B+ ...This means that 99% of cases designed for the Raspberry Pi Model B+ will work with the Raspberry Pi 2 Model B." You may just be in the 1%.
Having said that you may be able to clearance the case with some sanding etc. to get it to fit. ...
I'm posting this as it's the answer I got to but all credit is due to the commenter @Joan!
/boot/config.txt does not have device_tree=, thus enabling device tree. It does not contain any w1-* lines at all.
Result: lsmod shows that neither w1-gpio nor w1-therm are there (nor wire which is usually there when the other two are).