Your "5.1V 850mA" PSU may be "marginal" (5V 1000mA is recommended for a Model B). The best check of this is to measure the voltage between the test points TP1 & TP2 (marked as susch on the PCB) - it should be at least 4.75V. A secondary issue could be too much resistive "voltage droop" because of a poor quality power cable (same test applies).Ahammer18 wrote:Let me start off by listing my specs:
Rpi model B
Debian "Wheezy" Raspian (Latest update)
5.1 V = 850mA Motorola Cellphone Charger as Psu
4 GB Lexar Multi-use Sd Card
I have one simple problem. When I boot up Raspian for the first time in awhile, it runs fine. The GUI loads fine and everything is well. The problem starts when I reboot the Pi. Once the Pi shuts off and turns back on, I am greeted by a rainbow splash screen.
I have seen forum posts regarding the rainbow screen, but I haven't seen any that included my problem with rebooting the Pi.
Any help would be greatly appreciated.
How is that comment not a non-sequitur?smeezekitty wrote:How is that a problem?
You're commenting on my forum signature.Ahammer18 wrote:So is running 5 V through the pi a problem?
"How is it a problem" actually makes sense. Mine does it too and I assume it is by design.DougieLawson wrote:How is that comment not a non-sequitur?smeezekitty wrote:How is that a problem?
To some extent I think the O.P. may have been open to mis-interpretation ie. if only the RGB splash screen was being seen it could have been a problem. Said splash screen is related to the very first part of the boot process but, depending upon the monitor/TV and/or installation type (eg. NOOBS cf. raw image) may not be seen because the display in use "activates" too late. (A simpler example w.r.t. my setup is that I have to switch my "shared" monitor between VGA, for my netbook, to DVI, for a Pi, within the time the splash screen is being generated in order to see it. That's not always possible )smeezekitty wrote:"How is it a problem" actually makes sense. Mine does it too and I assume it is by design.DougieLawson wrote:How is that comment not a non-sequitur?smeezekitty wrote:How is that a problem?
So unless there is an actually problem other than the splash screen, why worry?
Just to clarify (I'm not able to check this at the moment), are you literally just adding the line 'boot_delay=1' to the text file? I now have this in my Raspbian image:Richard-TX wrote:I had a problem with 2 new Pis that I just bought. Both of the made in the UK and from Allied. They would intermittently hang on the rainbow screen. adding boot_delay=1 to the /boot/config.txt file fixed it. The big question is what did the UK builder change? I have Sony built and China built Rpi's and none of them hang. Just these 2 new ones.
Code: Select all
# uncomment if you get no picture on HDMI for a default "safe" mode #hdmi_safe=1 # uncomment this if your display has a black border of unused pixels visible # and your display can output without overscan #disable_overscan=1 # uncomment the following to adjust overscan. Use positive numbers if console # goes off screen, and negative if there is too much border #overscan_left=16 #overscan_right=16 #overscan_top=16 #overscan_bottom=16 # uncomment to force a console size. By default it will be display's size minus # overscan. #framebuffer_width=1280 #framebuffer_height=720 # uncomment if hdmi display is not detected and composite is being output #hdmi_force_hotplug=1 # uncomment to force a specific HDMI mode (this will force VGA) #hdmi_group=1 #hdmi_mode=1 # uncomment to force a HDMI mode rather than DVI. This can make audio work in # DMT (computer monitor) modes #hdmi_drive=2 # uncomment to increase signal to HDMI, if you have interference, blanking, or # no display #config_hdmi_boost=4 # uncomment for composite PAL #sdtv_mode=2 #uncomment to overclock the arm. 700 MHz is the default. #arm_freq=800 # for more options see http://elinux.org/RPi_config.txt boot_delay=1