1. The precompiled dtb's -> i can check if we can ship them in the d-i initrd preinstalled, or at least add them for the mini.iso and/or server.iso
2. So for amd64 mini.iso there is a 6M partition free to use for whatever: $ wget http://archive.ubuntu.com/ubuntu/dists/bionic/main/installer-amd64/current/images/netboot/mini.iso $ sudo kpartx -av ./mini.iso $ mount /dev/mapper/loop30p2 /mnt/ $ df -h | grep /mnt /dev/mapper/loop30p2 6.0M 0 6.0M 0% /mnt But i don't see anything similar for arm64 unfortunately. The intention is that when one does dd= of this onto e.g. usb-stick, there is a partition to drop e.g. preseed or some weird dkms drivers there. How much space would we need to drop a dtb? (ie. what's the largest reasonable dtb is?) 3. le sigh ideally we'd then structure the boot entries somehow sensible in subtrees, or offer an edit to specify the right name, cause there are a lot of them. Can grub at all guess/detect the right one to use at all? I.e. at least read the top level vendor and/or model names? Cause it would be nice to load the right one automatically, where possible. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1819443 Title: Cannot boot installer on platforms requiring Device Tree To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/debian-installer/+bug/1819443/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
