Bug#837629: OpenRD* with debian's u-boot 2016.09

[Rick Thomas]

On 11/02/16 10:38, Vagrant Cascadian wrote:

I've uploaded u-boot 2016.11~rc3 to the cascadia.debian.net
repository. I won't hold my breath, but give it a try...
Good thing you didn't hold your breath.  I tried it.  Same result as 
before:  No response after "reset".


I think I heard that support for armel will be withdrawn from Debian 
after Stretch.  If that's true,

there's not much percentage in expending any more effort on this project.

It was worth a try, I guess, but facts are facts and time marches on.

Let me know if there's anything else I can do that would be helpful. For 
example, I've got a couple of sheevaplug devices.  Has anything more 
recent than "2016.09-rc2+dfsg1-1 (Aug 30, 2016)" been

tested on a sheevaplug?

Rick

Bug#837629: OpenRD* with debian's u-boot 2016.09

[Rick Thomas]

On Nov 2, 2016, at 10:38 AM, Vagrant Cascadian  wrote:

> I've uploaded u-boot 2016.11~rc3 to the cascadia.debian.net
> repository. I won’t hold my breath, but give it a try...

I will.  No promises on the target date, but “soon”!  (-;

> Another option which might help debug the issue is to build u-boot
> mainline from source with an older GCC, such as what's shipped in
> jessie. You could then build the individual targets rather than the
> whole package, and it shouldn't take too long. Could also insert some
> printf statements in the early boot, maybe to figure out exactly where
> it is failing...

I’ve never done anything like that.  (Though I’m familiar with the usual UNIX 
software development tools, such as gnu-autoconf, gcc and make, etc.  And I’d 
be glad to learn what I don’t know.) Would you be willing to walk me through 
the steps?

Thanks!
Rick

Bug#837629: OpenRD* with debian's u-boot 2016.09

[Vagrant Cascadian]

On 2016-10-27, Rick Thomas wrote:
> On Oct 5, 2016, at 1:26 PM, Vagrant Cascadian  wrote:
>> On 2016-10-03, Rick Thomas wrote:
 deb http://cascadia.debian.net/~vagrant/debian UNRELEASED main
 
 The repository should be signed by my key, available in the
 debian-keyring package in the archive
 (F0ADA5240891831165DF98EA7CFCD8CD257721E9).
...
> Unfortunately testing u-boot on OpenRD fell by the wayside.
> I gather that the current u-boot in experimental has OpenRD support removed?

Both in experimental and unstable.


> But… as of now, all the “interesting” bits are temporarily under control.
> Would you like me to test something?

I've uploaded u-boot 2016.11~rc3 to the cascadia.debian.net
repository. I won't hold my breath, but give it a try...


Another option which might help debug the issue is to build u-boot
mainline from source with an older GCC, such as what's shipped in
jessie. You could then build the individual targets rather than the
whole package, and it shouldn't take too long. Could also insert some
printf statements in the early boot, maybe to figure out exactly where
it is failing...


live well,
  vagrant


signature.asc
Description: PGP signature

Bug#837629: OpenRD* with debian's u-boot 2016.09

[Rick Thomas]

On Oct 5, 2016, at 1:26 PM, Vagrant Cascadian  wrote:

> On 2016-10-03, Rick Thomas wrote:
>> On Oct 1, 2016, at 3:39 PM, Vagrant Cascadian  wrote:
>>> On 2016-09-17, Rick Thomas wrote:
 On Sep 16, 2016, at 3:19 PM, Vagrant Cascadian  wrote:
> https://bugs.debian.org/837629
> ...
>>> deb http://cascadia.debian.net/~vagrant/debian UNRELEASED main
>>> 
>>> The repository should be signed by my key, available in the
>>> debian-keyring package in the archive
>>> (F0ADA5240891831165DF98EA7CFCD8CD257721E9).
>>> 
>>> There were two critical fixes in 2016.09.01, *maybe* they fix the issue?
> 
> And now uploaded 2016.11~rc1 to my "UNRELEASED" repository, please test
> that...
> 
> 
>>> If not, I'll likely be removing OpenRD* from the packages on future
>>> uploads.
> ...
>> Sadly, it doesn’t look like it fixed the problem.  Still nothing after
>> installing the new u-boot.kwb and typing “reset”.
>> 
>> let me know if there’s anything more I can do to help…
> 
> If it's not fixed in 2016.11~rc1, the only thing left to try is git
> bisecting the issue...
> 
> 
> live well,
>  vagrant

Hi,

It’s been an “interesting” month (in the sense of the ancient curse: “May you 
live in interesting times!”)

Unfortunately testing u-boot on OpenRD fell by the wayside.
I gather that the current u-boot in experimental has OpenRD support removed?

But… as of now, all the “interesting” bits are temporarily under control.
Would you like me to test something?

Rick

Bug#837629: OpenRD* with debian's u-boot 2016.09

[Vagrant Cascadian]

On 2016-10-05, Vagrant Cascadian wrote:
> On 2016-10-03, Rick Thomas wrote:
>> On Oct 1, 2016, at 3:39 PM, Vagrant Cascadian  wrote:
>>> On 2016-09-17, Rick Thomas wrote:
 On Sep 16, 2016, at 3:19 PM, Vagrant Cascadian  wrote:
...
>>> If not, I'll likely be removing OpenRD* from the packages on future
>>> uploads.
> ...
>> Sadly, it doesn’t look like it fixed the problem.  Still nothing after
>> installing the new u-boot.kwb and typing “reset”.
>>
>> let me know if there’s anything more I can do to help…
>
> If it's not fixed in 2016.11~rc1, the only thing left to try is git
> bisecting the issue...

Could also try building with a different version of gcc (e.g. the one in
jessie, or gcc-5* from sid, which may take more configuring). There may
be issues triggered by gcc-6...


live well,
  vagrant


signature.asc
Description: PGP signature

Bug#837629: OpenRD* with debian's u-boot 2016.09

[Rick Thomas]

On Oct 5, 2016, at 1:26 PM, Vagrant Cascadian  wrote:

> And now uploaded 2016.11~rc1 to my "UNRELEASED" repository, please test
> that…

Will do. Sometime this weekend.

> 
>> let me know if there’s anything more I can do to help…
> 
> If it's not fixed in 2016.11~rc1, the only thing left to try is git
> bisecting the issue...

Are you located in the US?

If you think it would help, I could loan you one of the OpenRD devices,
as long as I can ship it without getting customs and immigration involved.

Rick

Bug#837629: OpenRD* with debian's u-boot 2016.09

[Vagrant Cascadian]

On 2016-10-03, Rick Thomas wrote:
> On Oct 1, 2016, at 3:39 PM, Vagrant Cascadian  wrote:
>> On 2016-09-17, Rick Thomas wrote:
>>> On Sep 16, 2016, at 3:19 PM, Vagrant Cascadian  wrote:
 https://bugs.debian.org/837629
...
>>  deb http://cascadia.debian.net/~vagrant/debian UNRELEASED main
>> 
>> The repository should be signed by my key, available in the
>> debian-keyring package in the archive
>> (F0ADA5240891831165DF98EA7CFCD8CD257721E9).
>> 
>> There were two critical fixes in 2016.09.01, *maybe* they fix the issue?

And now uploaded 2016.11~rc1 to my "UNRELEASED" repository, please test
that...


>> If not, I'll likely be removing OpenRD* from the packages on future
>> uploads.
...
> Sadly, it doesn’t look like it fixed the problem.  Still nothing after
> installing the new u-boot.kwb and typing “reset”.
>
> let me know if there’s anything more I can do to help…

If it's not fixed in 2016.11~rc1, the only thing left to try is git
bisecting the issue...


live well,
  vagrant


signature.asc
Description: PGP signature

Bug#837629: OpenRD* with debian's u-boot 2016.09

[Rick Thomas]

On Oct 1, 2016, at 3:39 PM, Vagrant Cascadian  wrote:

> On 2016-09-17, Rick Thomas wrote:
>> On Sep 16, 2016, at 3:19 PM, Vagrant Cascadian  wrote:
>>> https://bugs.debian.org/837629
>>> 
>>> If it can't be fixed, I'll likely remove OpenRD ultimate at some point
>>> so that u-boot 2016.09 can migrate to stretch... but it would be more
>>> ideal to fix it, of course! :)
>> 
>> It looks like you’ll have to pull OpenRD support out of this version.
>> I tried 2016.09+dfsg-1 on my OpenRD “Client”.  I got the same result
>> with it as I got with 2016.09~rc2+dfsg1-1 on the “Ultimate”, no
>> response following u-boot “reset” command.
> 
> I've uploaded packages based on 2016.09.01 to:
> 
>  deb http://cascadia.debian.net/~vagrant/debian UNRELEASED main
> 
> The repository should be signed by my key, available in the
> debian-keyring package in the archive
> (F0ADA5240891831165DF98EA7CFCD8CD257721E9).
> 
> There were two critical fixes in 2016.09.01, *maybe* they fix the issue?
> 
> If not, I'll likely be removing OpenRD* from the packages on future
> uploads.
> 
> 
> live well,
>  vagrant

Sadly, it doesn’t look like it fixed the problem.  Still nothing after 
installing the new u-boot.kwb and typing “reset”.

let me know if there’s anything more I can do to help…

Rick

Bug#837629: OpenRD* with debian's u-boot 2016.09

[Rick Thomas]

OK.  I’ll give it a try.

More when I know more.

Rick

On Oct 1, 2016, at 3:39 PM, Vagrant Cascadian  wrote:

> On 2016-09-17, Rick Thomas wrote:
>> On Sep 16, 2016, at 3:19 PM, Vagrant Cascadian  wrote:
>>> https://bugs.debian.org/837629
>>> 
>>> If it can't be fixed, I'll likely remove OpenRD ultimate at some point
>>> so that u-boot 2016.09 can migrate to stretch... but it would be more
>>> ideal to fix it, of course! :)
>> 
>> It looks like you’ll have to pull OpenRD support out of this version.
>> I tried 2016.09+dfsg-1 on my OpenRD “Client”.  I got the same result
>> with it as I got with 2016.09~rc2+dfsg1-1 on the “Ultimate”, no
>> response following u-boot “reset” command.
> 
> I've uploaded packages based on 2016.09.01 to:
> 
>  deb http://cascadia.debian.net/~vagrant/debian UNRELEASED main
> 
> The repository should be signed by my key, available in the
> debian-keyring package in the archive
> (F0ADA5240891831165DF98EA7CFCD8CD257721E9).
> 
> There were two critical fixes in 2016.09.01, *maybe* they fix the issue?
> 
> If not, I'll likely be removing OpenRD* from the packages on future
> uploads.
> 
> 
> live well,
>  vagrant

Bug#837629: OpenRD* with debian's u-boot 2016.09

[Vagrant Cascadian]

On 2016-09-17, Rick Thomas wrote:
> On Sep 16, 2016, at 3:19 PM, Vagrant Cascadian  wrote:
>>  https://bugs.debian.org/837629
>> 
>> If it can't be fixed, I'll likely remove OpenRD ultimate at some point
>> so that u-boot 2016.09 can migrate to stretch... but it would be more
>> ideal to fix it, of course! :)
>
> It looks like you’ll have to pull OpenRD support out of this version.
> I tried 2016.09+dfsg-1 on my OpenRD “Client”.  I got the same result
> with it as I got with 2016.09~rc2+dfsg1-1 on the “Ultimate”, no
> response following u-boot “reset” command.

I've uploaded packages based on 2016.09.01 to:

  deb http://cascadia.debian.net/~vagrant/debian UNRELEASED main

The repository should be signed by my key, available in the
debian-keyring package in the archive
(F0ADA5240891831165DF98EA7CFCD8CD257721E9).

There were two critical fixes in 2016.09.01, *maybe* they fix the issue?

If not, I'll likely be removing OpenRD* from the packages on future
uploads.


live well,
  vagrant


signature.asc
Description: PGP signature

Bug#837629: OpenRD* with debian's u-boot 2016.09

[Rick Thomas]

On Sep 16, 2016, at 3:19 PM, Vagrant Cascadian  wrote:

> There is at one report of an OpenRD ultimate that would not boot with
> the 2016.09~rc2 version of u-boot in debian. Uploaded 2016.09+dfsg-1 to
> unstable a few days ago. Would you be able to confirm if OpenRD variants
> that you have still work with the version in unstable?
> 
>  https://bugs.debian.org/837629
> 
> If it can't be fixed, I'll likely remove OpenRD ultimate at some point
> so that u-boot 2016.09 can migrate to stretch... but it would be more
> ideal to fix it, of course! :)
> 
> 
> live well,
>  vagrant

Sorry!

It looks like you’ll have to pull OpenRD support out of this version.  I tried 
2016.09+dfsg-1 on my OpenRD “Client”.  I got the same result with it as I got 
with 2016.09~rc2+dfsg1-1 on the “Ultimate”, no response following u-boot 
“reset” command.

Enjoy!
Rick

Bug#837629: OpenRD* with debian's u-boot 2016.09

[Vagrant Cascadian]

There is at one report of an OpenRD ultimate that would not boot with
the 2016.09~rc2 version of u-boot in debian. Uploaded 2016.09+dfsg-1 to
unstable a few days ago. Would you be able to confirm if OpenRD variants
that you have still work with the version in unstable?

  https://bugs.debian.org/837629

If it can't be fixed, I'll likely remove OpenRD ultimate at some point
so that u-boot 2016.09 can migrate to stretch... but it would be more
ideal to fix it, of course! :)


live well,
  vagrant


signature.asc
Description: PGP signature