[ARMedslack] A perplexing Raspberry Pi problem and my workaround. Comments?

[Steve Pirk]

I have 3 RPi devices, and have only fired up one so far using the Raspian
image. Let me try all 3 with a Slackware arm build and see if I can
duplicate your error on any of them. If I get one that hangs, I can try
your workaround to see if it is consistent.

-- steve <http://pirk.com>



On Mon, Aug 27, 2012 at 12:26 PM, Rob Clark <rclark at clavi.net> wrote:

> First, let me thank Stuart Winter and the other contributors for
> Slackware ARM on the Raspberry Pi.
>
> My problem:
> I am fortunate to have two RPi boards of nearly sequential serial
> numbers to play with.  I had absolutely no trouble booting and
> installing Slackware ARM on _one_ of them, but they other hangs on boot,
> either with the rainbow screen, or no video output at all.
>
> Debian-wheezy and Arch Linux from the raspberrypi.org site both work on
> both boards.
>
> The problem is the same booting from either the installation image
> raspi-slack-installer-01Aug12.img.xz or on a fully installed Slackware
> ARM made on the working RPi.  It boots on one device, but not the other.
>
> I tried different SDHC cards, power supplies, keyboards, etc. to no
> avail.  Switch everything to the other RPi, and it works fine.
>
> My workaround:
> Based on something I read on the Raspberry Pi troubleshooting forum, I
> copied the start.elf and loader.bin from debian-wheezy to the first
> partition of the raspi-slack-installer-01Aug12.  Now I am able to boot
> on the balky RPi.
>
> This is dumb luck because I charged ahead without understanding the boot
> process on ARM.  So I offer this information, for whatever it's worth :)
> _______________________________________________
> ARMedslack mailing list
> ARMedslack at lists.armedslack.org
> http://lists.armedslack.org/mailman/listinfo/armedslack
>
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.armedslack.org/pipermail/armedslack/attachments/20120827/7341c888/attachment.html>