That's the new undervoltage symbol. Your Pi's power supply is marginal or insufficient for its requirements.
From the raspberrypi.org blog page:
Finally on the subject of icons, in the past if your Pi was working
particularly hard, you might have noticed some yellow and red squares
appearing in the top-right corner of the screen, which were
This is still not documented anywhere, but the rc_gui tool (I'm assuming it would be a graphical user interface to the raspi-config if I were to ever install the full desktop) uses command line options to the raspi-config bash script. You can see the full list of options in the C source code. UPDATE: The official repo has disappeared for some reason. This is ...
At least nowadays, raspi-config seems to support noninteractive mode:
cat /boot/cmdline.txt # show original cmdline.txt
raspi-config nonint do_serial 1 # disable serial console
cat /boot/cmdline.txt # confirm changes
raspi-config nonint do_serial 0 # enable serial console
cat /boot/cmdline.txt # confirm changes
with this, ...
The lightning bolt means that the Pi is not receiving the required voltage. This may be due to the power supply you are using or the cable (if seperate). You should switch to a better supply/cable as undervolting can lead to SD card corruption and other difficult to trace issues.
You don't mention what model Pi you ae using and what if anything you have ...
I just had this same problem. Here is what eventually worked after reading this (From the comments it looks like you had the same issue as I did):
vcgencmd get_camera (Returned supported=1 detected=0)
Check to make sure ribbon was facing the right way (it was)
Check to make sure ribbon is all the way in the connector slot (it was)
Check to make sure ribbon ...
There is a two part mechanism which takes responsibility for this on Raspbian; likely the best idea is to take care of both parts if they are enabled.
The first is that the original /boot/cmdline.txt includes this:
Referring to a script with that path on the root partition, which will be used as the init process ...
OK. raspi-config is actually a bit of bash, so it's quite easy to see what it does:
# $1 is 0 to disable camera, 1 to enable it
# Stop if /boot is not a mountpoint
if ! mountpoint -q /boot; then
[ -e /boot/config.txt ] || touch /boot/config.txt
if [ "$1" -eq 0 ]; then # disable camera
set_config_var start_x 0 /...
edit your /boot/config.txt file and make sure the following lines look like this:
start_x=1 # essential
gpu_mem=128 # at least, or maybe more if you wish
disable_camera_led=1 # optional, if you don't want the led to glow
I found a solution that uses raspi-config.
I played around with it for a bit, and found something (NOTE: You may need to update raspi-config)
To enable Auto-login with raspi-config:
Run: sudo raspi-config
Choose option 3: Boot Options
Choose option B1: Desktop / CLI
Choose option B2: Console Autologin
Select Finish, and reboot the pi.
The pi should then ...
Triggerhappy is only used in raspi-config's init script, see line 17 of the init script. There it checks if any of the Shift keys is hold down at boot time to disable the ondemand scaling governor.
That means that raspi-config itself does not really need triggerhappy, just its boot up script. And the way that script uses thd doesn't seem to need the daemon ...
The lightning bolt means that you don't have enough power going to the Raspberry Pi.
Almost any standard micro USB cable will be able to power the Pi. Most of us have one or two laying around from getting them for our phones and we could easily use what we have to charge our phones to power the RPi.
However, the Raspberry Pi should have a 5 volt 2 amp ...
raspi-config is POSIX shell script and fairly easy to read if you understand shell scripting; on Raspbian it's in /usr/bin, and runs via an init service the first time you boot, but is kept updated thereafter. The version I'm referring to is from a Raspbian jessie system and was last modified August 10/2016.
Can somebody tell [me] what the Expand ...
But on a new Pi (Raspbian/B+) I could not get it to work until I followed the Advanced option in raspi-config and enbaled i2c there(and rebooted).
This is because newer Raspbian kernels use device tree "to manage some resource allocation and module loading":
The main impact of using Device Tree is to change from everything on, relying on module ...
Check if your boot folder is empty using cd /boot/ in a terminal session. If so, you should be able to mount it to the SD card using a simple command.
sudo mount /dev/mmcblk0p1 /boot
All this command does is mount the boot partition on your SD card. Which explains the The boot partition is not mounted - cannot configure. error. sudo raspi-config looks ...
What raspi-config does is changing the /boot/config.txt. There is a string inside that file which says start_x=0 when camera is disabled. By changing that to start_x=1 will enable the camera. You will have to reboot after you edited the file.
I made a script that searches the /boot/config.txt for the string "start_x=0" and if it finds it changes it to "...
After some digging, I found a rather simple solution. You'll have to edit your config.txt file. Located on the FAT partition of your raspberry pi SD card.
It's perfectly possible to do it using the pi itself, or you could just plug the microSD card on your computer and use your favorite editor for this.
Ok, now to the configurations...
I'm assuming you're ...
A USB OTG connection seems like the best option here. It will be much faster than about any alternative (certainly faster than I2C or UART), and with the g_ether driver you will be able to use it as a regular network, so your videos can be either streamed or saved as files and transmitted using HTTP, FTP, netcat etc.
You will need a micro USB cable and a ...
By far the easiest options for moving large amounts of data between Pi Zeros and other Pis are USB OTG, which has already been covered by Dmitry Grigoryev's answer, and ethernet or WiFi.
While USB OTG will work great if your Pis are fairly close together, the run length specification for USB tops out at around about 5 metres. Further apart than that and ...
will the entire system halt until the network is up
where in the boot-up sequence is crontab activated?
Crontabs are managed by cron, a system daemon started by init, which on Raspbian jessie is systemd.
Exactly when a service is started in terms of time depends on what it depends on, and a degree of indeterminacy, since things that do not depend ...
SSH is achieved just by creating a new user (useradd) and making a small edit to sshd_config. First lets create the user:
Once the user is created, if you want it to have root access, add it to the sudo group:
usermod -aG sudo UserName
Next we want to edit the sshd_config as root:
If you're looking to do a robot then I'd recommend using something like Nanpy. It essentially requires flashing the Arduino and connecting it to the Pi via USB. It's pretty quick and painless to set-up.
You can write your Arduino code in Python and communicate with the GPIO on the Pi within the same script, which can be handy. I've used it on a small robot ...
I ended up getting around this problem by doing the following:
Running a DHCP server on the laptop
Connecting the RPi to the ethernet port directly
Granting the RPi an IP through the DHCP server
SSHing into it
Manually running the raspi-config program from the terminal
Selecting "Finish" (otherwise it keeps popping up).
The problem is in Putty not the Pi. To fix the problem:
Load the stored profile for the Pi (I assume you have saved you connection details).
Open Putty Configuration.
From the left side menu click Translation from the Window section.
In the Remote character set dropdown select UTF-8.
Make sure that Use Unicode line drawing code points is selected.
Save the ...
I had the same issue
pi@jarvis:~ $ hcitool dev
with a inactive hciuart.service
pi@jarvis:~ $ systemctl status hciuart.service
● hciuart.service - Configure Bluetooth Modems connected by UART
Loaded: loaded (/lib/systemd/system/hciuart.service; enabled)
Active: inactive (dead)
pi@jarvis:~ $ sudo systemctl start hciuart.service
The base image is sized so that it will take as little as possible of the SD card space as practical. That's probably 4GB for Raspbian (full). Many people will use larger capacity cards. Unless the file system is expanded all the extra space provided by larger capacity cards will be wasted.
Use the df -h command to see the SD card utilisation before and ...
First edit /boot/cmdline.txt and append init=/usr/lib/raspi-config/init_resize.sh on to the first (and only) line
e.g. it may end up looking like
dwc_otg.lpm_enable=0 console=serial0,115200 console=tty1 root=PARTUUID=a8fe70f4-02 rootfstype=ext4 elevator=deadline fsck.repair=yes rootwait init=/usr/lib/raspi-config/init_resize.sh
next, you'll need to create ...