If you just need a new module, you can add that to the ramdisk. There's a "my_modules" path in there to put it in and an INSMOD_COMMANDS file to add the required commands to load it. If a new kernel is required, the existing one would just need to be replaced.
Have you tried the SIS kernel and found that it fails? If its just the module its a fairly simple patch, but changing the kernel gets more complex. Please let us know the results, the SI guys can include the driver for this adapter in future kernels if it is available. Mike On Wed, 2003-01-29 at 17:51, Neil Gorsuch wrote: > I am bringing up oscar on a very new set of hardware that requires a new > network driver module. We have a kernel_picker module that swaps in a new > kernel and/or lib/modules tree into the sis client image on disk. However, > that doesn't help in the initial installation, the kernel file and ramdisk > in /tftpboot crashes on this system. If I am substituting a new kernel > and/or modules into the client image, should I just go ahead and also > change the kernel and/or ramdisk in tftpboot? Please feel free to phone me > at 217-244-0424 I need to solve this soon. > > > > ------------------------------------------------------- > This SF.NET email is sponsored by: > SourceForge Enterprise Edition + IBM + LinuxWorld = Something 2 See! > http://www.vasoftware.com > _______________________________________________ > Sisuite-devel mailing list > [EMAIL PROTECTED] > https://lists.sourceforge.net/lists/listinfo/sisuite-devel -- Michael Chase-Salerno <[EMAIL PROTECTED]> ------------------------------------------------------- This SF.NET email is sponsored by: SourceForge Enterprise Edition + IBM + LinuxWorld = Something 2 See! http://www.vasoftware.com _______________________________________________ Sisuite-devel mailing list [EMAIL PROTECTED] https://lists.sourceforge.net/lists/listinfo/sisuite-devel
