Package: installation-reports Severity: important Boot method: network Image version: https://d-i.debian.org/daily-images/armhf/daily/device-tree/ 20210719-00:04:35 Date: 2021-07-19
Machine: ASPEED AST2600 EVB Base System Installation Checklist: [O] = OK, [E] = Error (please elaborate below), [ ] = didn't try it Initial boot: [O] Detect network card: [E] Configure network: [ ] Detect media: [ ] Load installer modules: [ ] Clock/timezone setup: [ ] User/password setup: [ ] Detect hard drives: [ ] Partition hard drives: [ ] Install base system: [ ] Install tasks: [ ] Install boot loader: [ ] Overall install: [ ] Comments/Problems: The installer was prepared by creating a FIT to boot from u-boot: mkimage -f auto -A arm -O linux -T kernel -C none \ -a 0x80000000 -e 0x80000000 -d vmlinuz \ -b aspeed-ast2600-evb.dtb -i initrd.gz \ debian-installer And then tftp booted from the vendor u-boot, using a serial console. The installer starts fine but fails when detecting network. The system uses the ftgmac100 network device, and requires the aspeed_mdio module to be present too. The mdio module is not included in the installer so network detection fails. In the past this could be worked around by booting with an upstream kernel with all the required drivers built in, however now d-i will fail the install when it cannot find the kernel version in the apt archives. Being able to override this behaviour would be useful for installing on systems that don't yet have full kernel support in the Debian archive.