OK, I did this, and it works about half-way.
Now it is able to load the driver, when I choose it by hand from the menu,
but it does not automatically "do the right thing" for an unattended
installation. Is there some search path (or similar concept) that I need
to modify to get it to try this driver automatically? Is there someplace
I can give it a "hint"?
-- Rick
Erik Troan writes:
> On Fri, 21 Sep 2001, Rick Koshi wrote:
>
> > mkdir /mnt/new-initrd
> > mount -t ext2 -o loop /tmp/new-initrd.img.uncompressed /mnt/new-initrd
> > mkdir /tmp/new-modules ; cd /tmp/new-modules
> > zcat < /mnt/new-initrd/modules/modules.cgz | cpio -imdv
> > cp -p /lib/modules/2.4.2-2/kernel/drivers/net/8139too.o 2.4.2-2BOOT
>
> You need the driver from the kernel-BOOT package, not from the normal
> kernel. Install the kernel-BOOT and do the same thing, but change this
> cp to:
>
> cp -p /lib/modules/2.4.2-2BOOT/kernel/drivers/net/8139too.o 2.4.2-2BOOT
>
> You're very, very close to getting this to work.
>
> Erik
>
> -------------------------------------------------------------------------------
> | "Who is John Galt?" - Atlas Shrugged by Ayn Rand |
> | |
> | Linux Application Development -- http://people.redhat.com/johnsonm/lad |
>
>
>
> _______________________________________________
> Kickstart-list mailing list
> Kickstart-list@xxxxxxxxxx
> https://listman.redhat.com/mailman/listinfo/kickstart-list
>
