Frans Pop <[EMAIL PROTECTED]> wrote:
> It seems overly complex to me.
> Why not just put the modules on a webserver somewhere and then just use a
> preseed-early script to do wget and depmod? If that is done before Detect
> disks, then it should possibly even be loaded automatically.
> And then us
I looked at the cd-drivers.img, net-drivers-1.img, net-drivers-2.img
images and I see that there are udeb packages, plus some additional
files to indicate what the modules are, PCI device IDs and the like.
I suppose what I'm asking really is, how do I build a udeb with
my module, what additional f
Frans Pop <[EMAIL PROTECTED]> 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
Geert Stappers <[EMAIL PROTECTED]> wrote:
> > I need to use a kernel module at install time and thereafter,
> > for a RAID card that isn't supported in the standard kernels.
>
> Please spent effort in a dialog with the manufacturer of the RAID card.
> Explain them that you what to use their prod
I need to use a kernel module at install time and thereafter,
for a RAID card that isn't supported in the standard kernels.
I could build a custom installer/kernel, but I'd really like
to only install the driver module so that the system can still
make use of the standard updated kernels. Presum
5 matches
Mail list logo
