[Date Prev][Date Next] [Thread Prev][Thread Next] [Date Index] [Thread Index]

Bug#658759: u-boot: fails to boot compressed 3.2.y kernels



For what its worth, many of us are now in the process of flashing in new u-boot binaries...
http://forum.doozan.com/read.php?3,6965,6965#msg-6965
I went ahead and posted revised binaries for 3 affected kirkwood machines: Seagate Dockstar, Pogoplug V1/E01 and Pogoplug V2/E02.    I haven't yet done anything in terms of a new binary for the Seagate GoFlex Net/Home series.  The Pogoplug V4 series seems to be unaffected by the problem.

Users from both forums.doozan.com and archlinuxarm.org are aware of it and I haven't seen any reports of problems, only of "booting" (the desired behavior).  These two communities are a large slice of users, but I haven't contacted anyone from plugcomputers.org (or whatever they call themselves).

With netconsole enabled, it is a pretty painless procedure (not more inherently risky than the original installation of Jeff Doozan's original u-boot replacement).  The process is not obtrusive or overly invasive - it is a true drop-in flash/bootloader upgrade.  The env vars are not affected.

Dave

On Mon, Mar 12, 2012 at 6:25 AM, Ian Campbell <ijc@hellion.org.uk> wrote:
On Mon, 2012-03-12 at 08:41 +0000, Ian Campbell wrote:
> On Sun, 2012-03-11 at 16:29 -0500, Jonathan Nieder wrote:
> > Ben Hutchings wrote[1]:
> >
> > > My understanding is that in general we cannot assume that uboot is
> > > upgradable at all, because:
> > >
> > > 1. Linux may not have access to the flash partition containing it.
>
> On the dreamplug I have:

I suppose it went slightly over my head that this issue applies to other
platforms than dreamplug. Oh well, I hope what followed was useful
nonetheless.

BTW I wonder if a suitable workaround might be to have the kernel
disable these same caches early on?

Ian.
--
Ian Campbell
Current Noise: Earth - The Rakehell

       A couple of kids tried using pickles instead of paddles for a Ping-Pong
game.  They had the volley of the Dills.



Reply to: