Re: Custom driver image for etch
Frans Pop <firstname.lastname@example.org> wrote:
> Basically you need to build your driver module against the kernel headers
> for the same kernel the installer uses (which is the -486 flavor of the
> i386 kernel) and make sure the ABI matches. So, if 'uname -a' in the
> installer gives you 2.6.18-6-486, you need to build your module against
> You can then just copy that module into the correct place under /lib/
> modules in the installer, run 'depmod -a' and 'modprobe <module>'.
> Note that you will also need to build the module for the kernel flavor you
> intend to install for the target system and then before you reboot the
> system copy that into /target/lib/modules and chroot into /target to run
> depmod -a and update the initrd.
Thanks for the details.
But is there really no way to automate this?
I asked about an additional driver image because that way I can
presumably set up a preseed to pull that in and do this all