'Debug'? colored screen on start, no boot [Solved]


13 posts
by Spider.007 » Mon Jun 04, 2012 7:08 pm
I was upgrading my Archlinux system on RPi, while watching a movie, while running atop to monitor progress. At the last package (xorg-server), the RPi hang. After rebooting it, I get some sort of debug-screen on my monitor, but the RPi doesn't boot any further. Obviously I can re-install the sd-card, but is this fixable? During the upgrade I also updated to the latest firmware, and the reboot might have caused some corruption, but I didn't find any topics about anyone experiencing this specific problem...

cmdline.txt:
Code: Select all
dwc_otg.dma_enable=1 dwc_otg.dma_burst_size=256 dwc_otg.lpm_enable=0 dwc_otg.dma_enable=1 console=ttyAMA0,115200 kgdboc=ttyAMA0,115200 console=tty1 loglevel=2 root=/dev/mmcblk0p2 rootfstype=ext4 rootwait


config.txt:
Code: Select all
hdmi_mode=16
arm_freq=900
disable_overscan=1


A quick photo to illustrate the problem:
Image
Posts: 34
Joined: Sat May 19, 2012 11:24 am
by dom » Tue Jun 05, 2012 9:31 am
That test pattern is displayed by start.elf before it loads the kernel.
If it remains on screen for longer than a second it suggests the kernel.img is not found or is bad.
Raspberry Pi Engineer & Forum Moderator
Raspberry Pi Engineer & Forum Moderator
Posts: 4742
Joined: Wed Aug 17, 2011 7:41 pm
Location: Cambridge
by Spider.007 » Wed Jun 06, 2012 10:55 am
Yep, you are absolutely correct! The kernel.img is indeed corrupt, I will replace it with an old version, so I can boot again, and upgrade to the latest img

Thanks!
Posts: 34
Joined: Sat May 19, 2012 11:24 am
by ianjcraven » Wed Jun 06, 2012 11:59 am
You've overclocked the frequency of your Pi to 900mhz if I read your config.txt correctly.

I'm surprised it boots at all :)
Posts: 16
Joined: Mon May 14, 2012 8:19 am
by Spider.007 » Wed Jun 06, 2012 4:03 pm
ianjcraven wrote:You've overclocked the frequency of your Pi to 900mhz if I read your config.txt correctly.

I'm surprised it boots at all :)

You shouldn't, it works fine!
Posts: 34
Joined: Sat May 19, 2012 11:24 am
by dom » Wed Jun 06, 2012 4:38 pm
@Spider.007
I added your photo to:
http://elinux.org/R-Pi_Troubleshooting# ... ash_screen
Hope you don't mind!
Raspberry Pi Engineer & Forum Moderator
Raspberry Pi Engineer & Forum Moderator
Posts: 4742
Joined: Wed Aug 17, 2011 7:41 pm
Location: Cambridge
by Spider.007 » Wed Jun 06, 2012 8:19 pm
I don't mind, I was thinking of asking for it since it might help other people being in a FAQ!
Posts: 34
Joined: Sat May 19, 2012 11:24 am
by ethzero » Wed Jun 06, 2012 11:05 pm
Hmm. That's very interesting mentioning about the "kernel.img" being "bad".

I've got exactly the same problem and behaviour when setting up a clean ArchLinux the other day:
a) Burnt initial image to SD card, works fine, rebooted
b) resized partition, rebooted fine, expanded filesystem, rebooted fine.
c) Did a "pacman -Syu" to bring base OS up to date (along with linux-raspberry images & firmware), rebooted ***hung at "rainbow" screen***

On my other SD card updating it up to 3.??.17 it was fine.

Wondering if this isn't a problem with ArchLinux or indeed further upstream with the RPi kernel itself affecting any OS you on it?

Many others appear to be getting similar sounding issues:
viewtopic.php?f=28&t=7601
viewtopic.php?f=28&t=7359
From age 8: Atari 800 XL > Spectrum ZX81 > Amiga 500+ > ESCOM 486+OS/2 warp (!), Few Dell Towers and Laptops (1 Alienware)

Currently in use: Dell XPS 630 > 2G iPod touch > 1G iPad 3G > 15" MacBook Pro > Raspberry Pi, Model-B :)
User avatar
Posts: 6
Joined: Fri May 18, 2012 1:18 pm
by Spider.007 » Thu Jun 07, 2012 8:15 am
well, actually my kernel.img was just gone, so I had to find another one (the _debug version worked, but somehow didn't give me a working console long enough to fix the problem).
Posts: 34
Joined: Sat May 19, 2012 11:24 am
by ethzero » Sun Jun 10, 2012 10:50 am
As suspected, all issues went away with 3.1.9-19 kernel and associated updates
From age 8: Atari 800 XL > Spectrum ZX81 > Amiga 500+ > ESCOM 486+OS/2 warp (!), Few Dell Towers and Laptops (1 Alienware)

Currently in use: Dell XPS 630 > 2G iPod touch > 1G iPad 3G > 15" MacBook Pro > Raspberry Pi, Model-B :)
User avatar
Posts: 6
Joined: Fri May 18, 2012 1:18 pm
by nburn42 » Fri Sep 11, 2015 8:30 am
Just two cents, I once had this error because I plugged in an image I was running on a Pi 1 B+ into a Pi 2 B.

Maybe this will help someone else in the future. I also added a kernel driver so I might have had some interesting configuration.
Posts: 1
Joined: Fri Sep 11, 2015 8:26 am
by eiger3970 » Tue Oct 06, 2015 1:59 am
My Raspberry Pi 2 Model B won't load my Micro SD which works on my Raspberry Pi 1 Model B+?
Same start.elf test pattern showing on the monitor.

I would have thought the OS Linux raspberrypi 3.12.28+ #709 PREEMPT Mon Sep 8 15:28:00 BST 2014 armv6l GNU/Linux would have worked?

I'm guessing I need to install the latest Raspbian Jessie.

FYI, here's the config.txt, which seems to be missing the code kernel=.
I guess that's the old Wheezy OS without that code, that seems to be needed?
Code: Select all
# For more options and information see
# http://www.raspberrypi.org/documentation/configuration/config-txt.md
# Some settings may impact device functionality. See link above for details

# 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
Posts: 37
Joined: Fri Feb 08, 2013 11:39 am
by rpdom » Tue Oct 06, 2015 4:45 am
Boot code prior to some time around Feb this year won't work on a Pi 2. You need to update.

If you are running from a plain Raspbian card then running "sudo apt-get update && sudo apt-get upgrade" on the old Pi will update the card.

If the card has NOOBS then there's some additional fiddling around that needs doing and you'd be better off using installing from scratch.
User avatar
Posts: 8919
Joined: Sun May 06, 2012 5:17 am
Location: Essex, UK