On Sep 12, 2016, at 2:30 PM, Vagrant Cascadian <vagr...@aikidev.net> wrote:

> Control: severity 836925 important
> 
> On 2016-09-07, Rick Thomas wrote:
>> I installed the new u-boot using the procedure in
>> /usr/share/doc/u-boot/README.Debian
>> 
>> The newly installed u-boot loaded and executed after a linux "reboot"
>> command.
>> 
>> Unfortunately it destroyed the u-boot environment, so it tried to boot
>> using the default env.  This failed to boot Linux.
> 
> What version of u-boot were you upgrading from?

I’m pretty sure it was “U-Boot 2016.01-rc3+dfsg1-3 (Jan 02 2016 - 23:19:11 
+0000)".  That’s the version on its twin.  I’m pretty sure I upgraded them both 
at the same time with the same version.

In case it matters, the /boot partition is on the SDcard.

> 
> The u-boot env values were changed somewhere around 2016.01, possibly:
> 
>  https://bugs.debian.org/781874
> 
> Or has the u-boot environment configuration changed again since then?

It seems likely that the environment configuration changed between 
2016.01-rc3+dfsg1-3 and 2016.09~rc2+dfsg1-1.  Would it be possible for you to 
check that?

> I went to Martin's page,
>> https://www.cyrius.com/debian/kirkwood/sheevaplug/install/ , and
>> followed the instructions there to restore the environment for booting
>> from the SD card.  I also had to restore the "ethaddr" u-boot
>> environment variable.
> 
>> After having restored the u-boot environment, I issued a "reset", and
>> it then happily booted as expected.
> 
>> I'd recommend that /usr/share/doc/u-boot/README.Debian give a warning
>> about needing to restore the u-boot environment, at least for the
>> sheevaplug.
> 
> Or NEWS.Debian, given that it can actually cause a failure to
> boot.

Yeah, you’re right.  NEWS.Debian would be the right place.

> If you could propose some text describing the issue, when it is
> encountered, and what to do about it, that would be helpful; the details
> of the issue are a bit unclear to me to start writing anything.

If you can verify exactly when the environment config changed, I’ll try to 
describe what I did to fix the problem.

> live well,
>  vagrant

Reply via email to