Hi Finn, Am 06.02.2022 um 17:02 schrieb Finn Thain:
On Sun, 6 Feb 2022, Michael Schmitz wrote:Hi Carlos, even 7 MB uncompressed seems a little big to me (if using modules for anything not essential to boot).Maybe CONFIG_DEBUG_INFO needs to be disabled: $ ./scripts/config -d CONFIG_DEBUG_INFO
That appears to be the cause, yes.But the size of the original vmlinux file (88 MB in my case with Carlos' .config) is a red herring - what matters is the size of the uncompressed kernel as loaded by the boot loader (after stripping off symbols and debug info). My kernel build command does generate a 'vmlinux.gz' file of 2.6 MB from the 88 MB original, which comes to 5.1 MB uncompressed. That's perfectly OK.
I suspect the difference in size (7 MB vs. 5.1 MB) is due to gcc versions. Either way, the solution is to use the vmlinux.gz file (and eventually unzip that if amiboot can't load compressed images) instead of vmlinux.
An alternative approach would be, $ make ARCH=m68k amiga_defconfigIf you can send me your .config (or a link to download the kernel image package), I'll compare with what I've used for v5.15. The tricky part might be generating the initrd image in the cross build setup - the script does not have an option to search for kernel image and modules outside the cross build hosts' root fs AFAICS. You may have to hack mkinitramfs or manually extract an existing initrd (cpio archiive format) and repack after replacing the modules directory.If you're building your own, you can arrange to have the critical drivers built-in i.e. just what's necessary to mount the rootfs. After that modules can be loaded automatically.
True - building udeb packages on a cross compile platform (as Carlos would like to do) might be a little too tricky.
The problem with debian-installer is that the initial root filesystem is the initrd, and the persistent root filesystem is populated from udebs and regular packages fetched from the package repositories.
Having the apne driver (along with disk drivers, partition support and filesystems required) built-in ought to allow that initial step to complete, but this will leave you with kernel image and modules from the udeb kernel packages installed on the disk root filesystem. You'd have to copy the custom-built modules from the AmigaOS partition and install them by hand at the end of the install.
The installer will attempt to load modules from the initrd to get to a known sane system state before beginning the install AFAIR, so replacing the modules on the initrd very likely will still be required.
I'll try replacing modules on an old initrd image using cpio to see how far that gets me ...
Cheers, Michael