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 <vagrant@debian.org>
Date:   Wed Dec 5 17:45:22 2018 +0100

    [armel] Disable OpenRD targets, no longer present in u-boot.

While it's true that there are no u-boot images for OpenRD anymore,
I think the installer and kernel should still work fine (people can
install u-boot from stretch or even use the Marvell u-boot that ships
with the device).

I think the part of the commit above that removed openrd from
build/config/armel/kirkwood/netboot.cfg should be reverted.
(the change to build/boot/arm/armel-kirkwood-u-boot-image-config
is obviously fine)

I don't have an OpenRD anymore but I can probably find someone if
testing is required.

Vagrant, see below:

* Martin Michlmayr <tbm@cyrius.com> [2019-08-06 20:10]:

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 wonder if it would make
sense to add the images back to d-i in a point release.

Basically to revert the change to build/config/armel/kirkwood/netboot.cfg
from commit e799d626f45e9c706d05003e3112d481db2870a9

Vagrant, do you think you could do a bullseye d-i checkout, make that
change and make the OpenRD images available for Rick to test?
(I don't have any ARM machines)

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 from Buster and probably Stretch back before that).  Ideally, I'd like to try Bookworm, but if that's not possible, I'll be happy with Bullseye.

Do you think it's possible to make the install stuff for the OpenRD's sometime soon?

Thanks very much!
Rick

* Cyril Brulebois <kibi@debian.org> [2022-06-22 15:39]:

Thank you!

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).

I guess your build failure is because you reverted the change to
build/boot/arm/armel-kirkwood-u-boot-image-config as well. (I'm only
guessing here since it's been years I looked at this, but I think so.)

(If it builds, can you upload the images somewhere so Rick can test
them?)

Thanks again!

Hi Martin,

Martin Michlmayr <tbm@cyrius.com> (2022-06-09):

Tried that, building in bullseye_armel-dchroot on amdahl (following
instructions at https://dsa.debian.org/doc/schroot/); but it fails to
build since openrd bits are missing from the u-boot package?

    Providing u-boot binaries for dockstar ...
    Providing u-boot binaries for dreamplug ...
    Providing u-boot binaries for guruplug ...
    Providing u-boot binaries for sheevaplug ...
    Providing u-boot binaries for openrd-base ...
    cp: cannot stat '/usr/lib/u-boot/openrd_base/u-boot.kwb': No such file or directory
    make[7]: *** [config/armel/kirkwood/u-boot.cfg:8: u-boot-binaries] Error 1

and indeed:

    $ find /usr/lib/u-boot/ -type f|sort
    /usr/lib/u-boot/dockstar/u-boot.kwb
    /usr/lib/u-boot/dockstar/uboot.elf
    /usr/lib/u-boot/dreamplug/u-boot.kwb
    /usr/lib/u-boot/dreamplug/uboot.elf
    /usr/lib/u-boot/guruplug/u-boot.kwb
    /usr/lib/u-boot/guruplug/uboot.elf
    /usr/lib/u-boot/sheevaplug/u-boot.kwb
    /usr/lib/u-boot/sheevaplug/uboot.elf

For the avoidance of doubt, that chroot has those u-boot packages:

    ii  u-boot:armel   2021.01+dfsg-5
    ii  u-boot-tools   2021.01+dfsg-5

Please let me know if I can be of more assistance regarding building,
backporting, etc.


Cheers,

Martin Michlmayr <tbm@cyrius.com> (2022-06-22):

Sorry, didn't pay enough attention…

Absolutely right.

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 there until it's superseded by
another attempt if required, or until that ends up being published in a
point release).


Cheers,

Downloading the tar-ball and un-tar-ing it I see there's a uImage and uInitrd file for ultimate, but there's also a .dtb file?  Should I include it on the USB-stick as well?  Is there anything else in the tar-ball I should be paying attention to?

I'm hoping to do preliminary testing tonight.  If I don't hear back before then (about midnight Pacific Daylight time) I'll go ahead and put all three files on a USB-stick and see what happens...

Enjoy!
Rick

* Rick Thomas <rbthomas@pobox.com> [2022-06-22 20:05]:

As far as I can tell, the build process appends the DTB to the kernel,
so just loading uImage and uInitrd (as per instructions) should work.

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 same USB stick (a trick I've used frequently in the past).  System booted and ran just fine.

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.
    3) Anything else you might want to try?

Detail:
    The u-boot version that's on the "ultimate" is
=> version
U-Boot 2016.11+dfsg1-4~20170308~1 (Mar 09 2017 - 01:27:49 +0000)
OpenRD-Ultimate
arm-linux-gnueabi-gcc (Debian 6.3.0-8) 6.3.0 20170221
GNU ld (GNU Binutils for Debian) 2.28
=>
    So it's not current, but it's also not the ancient original from 2011.

Enjoy!
Rick

* Rick Thomas <rick.thomas@pobox.com> [2022-06-23 03:20]:

Thank you for testing!

I think the system can boot from SATA (not sure about eSATA).

I don't think so; thanks a lot!

That's fine.

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 next Debian
release?  I thought it was going to get dropped but it's still there.)

Martin Michlmayr <tbm@cyrius.com> (2022-06-23):

From yesterday:
https://lists.debian.org/debian-release/2022/06/msg00192.html


Cheers,

Martin Michlmayr <tbm@cyrius.com> (2022-06-23):

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 certain what you'd like to do with the bug report: consider it
all about restoring netboot support? Or would you like to keep it open
to investigate some possible follow-up regarding u-boot?

Happy to perform s/see: #934072/closes: #934072/ in the changelog if
that makes sense.


Cheers,

* Cyril Brulebois <kibi@debian.org> [2022-06-23 19:42]:

Closing it is fine.

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.

Thank you for resolving this issue!

Martin Michlmayr <tbm@cyrius.com> (2022-06-24):
we'll add that back.

No worries, just applying your suggested changes, you're doing the work.


Cheers,

We believe that the bug you reported is fixed in the latest version of
debian-installer, which is due to be installed in the Debian FTP archive.

A summary of the changes between this version and the previous one is
attached.

Thank you for reporting the bug, which will now be closed.  If you
have further comments please address them to 934072@bugs.debian.org,
and the maintainer will reopen the bug report if appropriate.

Debian distribution maintenance software
pp.
Cyril Brulebois <kibi@debian.org> (supplier of updated debian-installer package)

(This message was generated automatically at their request; if you
believe that there is a problem with it please contact the archive
administrators by mailing ftpmaster@ftp-master.debian.org)
Format: 1.8
Date: Tue, 05 Jul 2022 17:57:59 +0200
Source: debian-installer
Architecture: source
Version: 20210731+deb11u4
Distribution: bullseye
Urgency: medium
Maintainer: Debian Install System Team <debian-boot@lists.debian.org>
Changed-By: Cyril Brulebois <kibi@debian.org>
Closes: 934072
Changes:
 debian-installer (20210731+deb11u4) bullseye; urgency=medium
 .
   * Reinstate some armel netboot targets, as suggested by Martin
     Michlmayr (Closes: #934072) and tested by Rick Thomas (thanks!):
      - openrd-base
      - openrd-client
      - openrd-ultimate
   * Bump Linux kernel ABI to 5.10.0-16.
Checksums-Sha1:
 eb221bc924519585a77a60f5ee6494f48d57aab4 3845 debian-installer_20210731+deb11u4.dsc
 dcc0dc80d5ecd2832c737de2c195b48c2f723f62 1418156 debian-installer_20210731+deb11u4.tar.gz
 0a7cc63a68fa861cd40730a142422818ab946833 12360 debian-installer_20210731+deb11u4_source.buildinfo
Checksums-Sha256:
 bec4c4ed3b9651fcc1fdadbc57e3f48edcb12a92b10d8fcd0082e6211e224f0d 3845 debian-installer_20210731+deb11u4.dsc
 262db08148e40ed88b3aa607eaaafe78103e51a804d965e1ea9e7aa6bb5a0974 1418156 debian-installer_20210731+deb11u4.tar.gz
 c2a6af91b8257c432aa9e6fb51b5928ce7288a316b38058a83e11c711ce03d28 12360 debian-installer_20210731+deb11u4_source.buildinfo
Files:
 57127950f06380db7706cd3b3a51d4e4 3845 devel optional debian-installer_20210731+deb11u4.dsc
 6a641099662bf03bae76f33c621edf77 1418156 devel optional debian-installer_20210731+deb11u4.tar.gz
 a445befa7396e1e8b2e92a4557b1e435 12360 devel optional debian-installer_20210731+deb11u4_source.buildinfo
-----BEGIN PGP SIGNATURE-----

iQJEBAEBCgAuFiEEtg6/KYRFPHDXTPR4/5FK8MKzVSAFAmLEbLwQHGtpYmlAZGVi
aWFuLm9yZwAKCRD/kUrwwrNVICOlEADAZKWiXZY5TxPXt0TRBh5iqFSUm3lZ0syc
VaPePjiATa2wUwbYVfyajIIHax7XtSzY5AU+u4PGBmYrmu4ukvC2bO6f0DQ/Vdd7
k2kWJ7W+9kdcW9zuuu+p1vvPl8nFA3BTYTdZ+biVTv0X/75MYSIhb61MD+tTDLyO
DHivF+K/KycVX7r8Q0GIp1aCaNudnJYeDSWncjzhngmUi3ADQq2NjFI5b9iKhiK/
Mmz9w96ErhugWJLO2CCEYGgjOMtUIS/xrT7vh+BszKGi3ryhWlOxEqHaZqR6AQ/3
+mjgZfKNTQWw8wp5hfNFojzE/XKFqfD1gNiDT4vcH7NIgCK+WjzMh2gYKRfkFVt/
NmhM9zwtDzpyzJQktEoEai0nPh2KtmOK2srE1bnV0sGcGjnFHVxOuw2tFtNOfaZM
GhhDq4z0BureYeebLr4cr+lcOT+rW0XsbuFoB8nIseBiY1KzDooesU5uYmcakF2F
laAX6hXJhV58MocdTmah0ZMAbzTFwHAkVRXZWvl7IOxNn1im4JfOpzhdgg1HxPxA
Aeat72XrJXIF/Sknjqo/n/LFk4bHTHSK4/3n6dE0ba72r0Fb225mha7/iXZfMAap
7GMcZcnNPUpkpkodMaAJcmjAsDLiWJMlWzhxHbW6DKZlvXqMaE75rvjQxApiGNY9
OIywrSV7MQ==
=HVAH
-----END PGP SIGNATURE-----