Do you mean a screen like this?:
If you using a RPi 3 B+, it may just be out of date firmware (see here) - you need to use newer image with the right firmware such as the offical Raspbian image - older and derivative images may still need to be updated for now (e.g. OctoPrint    )
Various troubleshooting methods can be found here:
With current ...
I've made this answer to summarize the experience to this issue. We are talking about Raspberry Pi 3 Model B+, released on 2018-03-14. It has some new and updated features compared to Raspberry Pi 3 Model B.
A 1.4GHz 64-bit quad-core ARM Cortex-A53 CPU
Dual-band 802.11ac wireless LAN and Bluetooth 4.2
Faster Ethernet (Gigabit Ethernet over USB 2.0), maximum ...
Found myself in the same situation just now. Took quite some time to figure out (taking into account that I had neither a USB keyboard nor a Linux computer around this was a long quest).
The reason for this problem appearing seemingly out of the blue is fsck - the automated file system check, which runs on startup.
During this check fsck may discover that ...
I just ran into this issue myself. I found two ways to create the SD card using the .tar.gz images provided by ArchLinuxARM, provided you have a USB SD card reader.
Method 1: Raspberry Pi + USB card reader + 1 additional SD card
This method requires an additional SD card and a USB card reader. It uses Linux on your Raspberry Pi to build an new SD card that ...
I had the exact same issue on a P3 - tried different ISOs but no joy
I was able to fix by disabling cloud init via ssh.
1) get the IP address of the Pi - I was at home so just logged onto my router and got it from there
2) in windows command line on another machine login using command :
ssh ubuntu@[ip address]
the default password is 'ubuntu'
3) you ...
The Pi's UART has a fault (in the firmware). Whenever the port is opened there is a 30 µs low glitch on TXD.
See http://elinux.org/RPi_Serial_Connection#Unwanted_serial_garbage_input and search for glitch.
You will need to find a workaround as the fault will not be fixed.
Overclocked use may permanently damage components enough to cause them to misbehave (even under normal operating conditions) without becoming totally unusable.
In general, overclockers claim that testing can ensure that an overclocked system is stable and functioning correctly. Although software tools are available for ...
The reason why the ISC DHCPv4 server service fails is that at the time it is started the network interface configuration might not have been finished. As systemd cannot know when a service really has become ready (as opposed to have been started successfully), the usual start dependency service unit settings don't help either. Often, you'll find ugly ...
You've not explained or shown how you have your batteries arranged, nor provided any specs on them. But it seems likely they are in series - thereby providing ~ 9V output.
Batteries in series can provide no more current that a single battery, and even a good quality AA cell isn't capable of much more than 1 amp. And so your battery pack will be unable to ...
One simple approach is to get a PC with Linux (even a LiveCD distribution - Ubuntu allows booting from CD for example) will suffice. Every modern Linux will recognize both SD partitions out of the box and allow you to modify their contents.
The IPE home page seems to be no more accessible.
It should not be used since it seems not to be maintained anymore.
For the record, here is a link to the old IPE homepage at web.archive.org
Depending of what you use your RPi for, you may be insterested in IPE, which is a "blackout-proof flavour of Raspbian".
I plan to use it to boot my ...
Finally I found the problem that is my power supply. It is not 5V output it is around 6.8V that is why color screen after that load some cord and it load again and again. If you find how to check voltage Raspberry pi B+ and B this is the Video I founded. Thank You.
All the boot files are on a FAT32 sector, which is readable and writeable by all common operating systems.
You can place the SD card in an SD card reader, delete the bad kernel, and rename the good kernel from any Windows, or Mac, or Linux machine.
I had this problem too, it never got past that boot screen. It turned out it was a power supply problem. Pi 3 requires 2 A, and I had a 1.5 A micro USB adapter. When I switched to a 2 A adapter it worked as expected.
The rainbow square is an under-voltage warning. You might consider upgrading to a more powerful power supply (more amps, not more volts).
To further answer your question I have tried to reproduce your issue. I have installed a new sd card with Raspbian Stretch and inserted in a B+. It boots normally and has been running ever since. Also after reboots....
Since I found the solution myself, I am posting it here, very grateful to every author of the raspberry pi forum posts.
1. Part 1 - getting command line in the boot
Got "Cannot open access to console, the root account is locked." error.
Mount the SDCard on another computer (any type).
Tip: if you don't have a SDCard reader on your ...
If you want to edit files on the root partition, an easy way is to download some Linux distribution (Ubuntu for example) flash it to an USB stick and boot from it. Here is a tutorial how to do it.
When you successfully booted Ubuntu you can edit your fstab with sudoedit /media/ubuntu/rootfs/etc/fstab
If you want to edit it from "Files" hit Ctrl + l and ...
I don't see that connecting pin 40 (GPIO21, aux SPI SCLK) to ground would have any bad effect.
Most GPIO are set as inputs. Connecting an input mode GPIO to ground or 3V3 is normal operation and has no bad effect.
If the GPIO was set in output mode and set high then it might damage the GPIO if connected to ground for an extended period. I don't think a ...
You can get the Raspberry Pi 4 to boot with Alpine Linux 3.10.2 by adding the following two files into the FAT32 (boot) partition: start4.elf and fixup4.dat.
They can be obtained from the official repository:
bootcode.bin is ignored by the Raspberry Pi 4.
The alpine linux config.txt is also old, ...
I found what I believe was the cause, and it now appears to be fixed.
Since this machine has a battery-backed RTC on it, fake-hwclock had been uninstalled long ago. When looking at the dump from 'journalctl -xb' I noticed the timestamps were all from several months back (about the time the machine was made, perhaps), and then didn't jump to the present ...
Try plugin your display to the other port. I spent an hour to figure out that my display was not on the primary display port and the secondary port was showing rainbow. Switched my display to primary port i.e. next to the power input and it came up :-)
I found the solution to my problem. Maybe it helps for others.
If you are running RT Kernel on Raspberry pi and having a problem to mount root file system, then add the following option to BOOT/cmdline.txt file.
It has already mentioned and solved in the following post
I understand your frustration, but there is one caution in your post "system updates itself fine, pull power, wait 20 seconds, plug back in". NEVER turn off the power on ANY computer without shutting down properly.
For Linux this is sudo shutdown -h now (or similar).
Shutting down may damage the filesystem, and from reports on this Forum the SDcard on the ...
How to get the TTL console working on the Raspberry Pi
STEP 1Edit /boot/cmdline.txt and make sure you have the following:
dwc_otg.lpm_enable=0 console=ttyAMA0,115200 kgdboc=ttyAMA0,115200 console=tty1 elevator=deadline root=/dev/mmcblk0p2 rootfstype=ext4 rootwait
The important part here is to have console=ttyAMA0,115200 and kgdboc=ttyAMA0,115200
Just to put in answer form. Per official raspberry pi site, the dd command should be
dd bs=4M if=2014-09-09-wheezy-raspbian.img of=/dev/mmcblk0
Edit: obviously changing image name to that of your image.
Once an SD card starts producing errors I believe it is defunct. They generally use a methodology called wear levelling (apparently often via a 32-bit ARM microcontroller) to maximize their lifespan.1
This means the addresses the card exposes are virtual, they do not literally correspond to specific physical blocks; a consequence of wear levelling is that ...
I faced a similar issue and the problem ended up being my SD card. I also had no display and the similar red and green light issue.
To rectify, I configured my SD card to Raspbian using Win32DiskImager and it worked. I was using the same Pi as you too.