Martin Michlmayr (2022-06-24):
> If armel stays in bookworm, it might make sense to re-enable u-boot
> for that release, but we'd first file a bug on the u-boot package.
Looks like a plan: if that happens, get u-boot updated, let us know, and
we'll add that back.
> Thank you for resolving this
* Cyril Brulebois [2022-06-23 19:42]:
> Here's what I just pushed to the bullseye branch (which is going to be
> used when building d-i for the next point release):
>
> https://salsa.debian.org/installer-team/debian-installer/-/commit/3ef30be60ab128f53a0cd16e6c1e91a3123988b4
>
> I'm not
Martin Michlmayr (2022-06-23):
> OpenRD was actually restored in u-boot upstream, but I doubt it's
> worth the effort to add it back to Debian since there are so few
> users. Then again, if you get OpenOCD running and want to try, maybe
> Vagrant could re-enable it. (Is armel going to be in the
Martin Michlmayr (2022-06-23):
> (Is armel going to be in the next Debian release? I thought it was
> going to get dropped but it's still there.)
From yesterday:
https://lists.debian.org/debian-release/2022/06/msg00192.html
Cheers,
--
Cyril Brulebois (k...@debian.org)
* Rick Thomas [2022-06-23 03:20]:
> Short story:
> Works a treat!
Thank you for testing!
> Next test:
> 1) Install from/to a uSD card
> 2) Install from a uSD card to an eSATA disk drive --leaving the /boot
> partition on the uSD.
I think the system can boot from SATA (not sure
Short story:
Works a treat!
Longer story:
Details will have to wait (it's 3AM right now) but to keep it short -- I
put the two uI* files (ignored the .dtb file) onto an ext2 partition of a USB
stick. Followed the instructions on Martin's page, and successfully installed
back to the
* Rick Thomas [2022-06-22 20:05]:
> Great! Thanks! Now for testing: what exactly should I do with this
> tar-ball? I've been relying on Martin's instruction page at
> https://www.cyrius.com/debian/kirkwood/openrd/install/ which only
> mentions downloading two files (uImage and uInitrd) and
On Wed, Jun 22, 2022, at 7:27 AM, Cyril Brulebois wrote:
>> (If it builds, can you upload the images somewhere so Rick can test
>> them?)
>
> Sure, that was the plan all along.
>
> https://people.debian.org/~kibi/openrd4bullseye/ has the tarball after a
> full debian-installer build (it'll stay
Martin Michlmayr (2022-06-22):
> I think you completely reverted commit e799d626f4. You should only
> revert the change to build/config/armel/kirkwood/netboot.cfg but not
> the change to build/boot/arm/armel-kirkwood-u-boot-image-config
> (since OpenRD for u-boot was removed).
Sorry, didn't pay
Hi Martin,
Martin Michlmayr (2022-06-09):
> I became aware recently that this was never fixed. Rick Thomas has
> two OpenRD (Ultimate and Client) and could test the images.
>
> Since bullseye is the last release to support these devices (I think?
> I never know what the status of armel is), I
* Cyril Brulebois [2022-06-22 15:39]:
> > Basically to revert the change to build/config/armel/kirkwood/netboot.cfg
> > from commit e799d626f45e9c706d05003e3112d481db2870a9
> Tried that, building in bullseye_armel-dchroot on amdahl (following
> instructions at
Hi all,
This has suddenly had it's priority raised a bit for me. I was fiddling around
with my Ultimate OpenRD, and I managed to render the boot disk un-bootable.
I'd like to re-install with either Bullseye or Bookworm (Prior to my fumble
fingers, it was happily running Bullseye via upgrade
Vagrant, see below:
* Martin Michlmayr [2019-08-06 20:10]:
> I noticed that there are no pre-built images for OpenRD in buster
> anymore.
>
> I found:
>
> commit e799d626f45e9c706d05003e3112d481db2870a9
> Author: Vagrant Cascadian
> Date: Wed Dec 5 17:45:22 2018 +0100
>
> [armel]
Package: debian-installer
Version: 20190702
Severity: important
I noticed that there are no pre-built images for OpenRD in buster
anymore.
I found:
commit e799d626f45e9c706d05003e3112d481db2870a9
Author: Vagrant Cascadian
Date: Wed Dec 5 17:45:22 2018 +0100
[armel] Disable OpenRD
14 matches
Mail list logo
