I am in the process of trying out Christophers' steps right now.
I want to make sure I didn't mess up the boot portion. To run the BOOT
kernel, I did the following steps:
1) edit /etc/lilo.conf -- I added a second section to lilo.conf and
altered the image line to point to the BOOT kernel:
image=/boot/vmlinuz-2.4.2-2
label=linux
read-only
root=/dev/hda10
image=/boot/vmlinuz-2.4.2-2BOOT
label=linux-BOOT
read-only
root=/dev/hda10
2) run /sbin/lilo since the lilo.conf file has changed
3) Reboot system in the BOOT kernel (i.e label should be "linux-BOOT")
Is that all accurate?
Ed Brown
<ebrown@xxxxxxxx> To: kickstart-list@xxxxxxxxxx
Sent by: cc:
kickstart-list-admin Subject: Re: Help needed adding modules to the boot image
@redhat.com
No Phone Info
Available
03/24/2003 02:06 PM
Please respond to
kickstart-list
Rebecca,
These are good suggestions and may solve your problem. Let me remind
you
too that you have to have be running the BOOT version of the kernel at the
time
that you compile the module.
-Ed
Christopher Malek wrote:
> On Mon, Mar 24, 2003 at 10:29:28AM -0600, Rebecca.R.Hepper@xxxxxxxxxxx
wrote:
> >
> > Thanks for the response, Ed. I followed the steps you suggested for
> > compiling my module. I do end up with a different module than what I
get
> > by using my compilation steps. When I try to kickstart, I never see
the
> > e100 module try to get loaded and my Alt-F3 screen shows
> > * found nothing
> > * no appropriate device for kickstart method is available
> >
> > Why doesn't it automatically try to load the e100 module?
>
> Did you update the module-info and pcitable files in the modules
> directory of the initrd?
>
> If this is a hardware driver, you need to add a line to pcitable for
> the driver. anaconda compares the vendor and device codes it discovered
> from scanning the PCI bus to the lines in that file. You need to figure
> out the vendor and device codes for the hardware, and associate our
> driver with those codes.
>
> On a Linux box where you have a working e100 card of the same type:
>
> 1. Do 'lspci' to find your card. Record the value for the first
> column for that card (looks like "XX:XX.X").
> 2. Do 'lspci -n' and look for the line that starts with the value you
> recorded in step 1. Record the value from the last column (looks
> like "AAAA:BBBB", and may have "(rev XX)" after it)
>
> Now to update the info on the boot floppy.
>
> 3. First, unpack the floppy image
>
> image=<name of boot image file>
>
> mkdir /mnt/initrd
> mount -o loop ${image} /mnt/floppy
> cd /mnt/floppy
> gunzip -c initrd.img > /tmp/initrd
> mount -o loop /tmp/initrd /mnt/initrd
>
> mkdir /tmp/modules
> cd /tmp/modules
> zcat /mnt/initrd/modules/modules.cgz | cpio -i -d
>
> 4. Add the driver --
>
> cp e100.o /tmp/modules/${KERN_VERS}BOOT
>
> 5. Rebuild modules.cgz:
>
> cd /tmp/modules
> find . -type f | cpio -H crc -o | gzip -9 > /tmp/modules.cgz
> mv /tmp/modules.cgz /mnt/initrd/modules/modules.cgz
>
> 5. Now add a line like this to /mnt/initrd/modules/pcitable (AAAA:BBBB
> comes from step 2):
>
> 0xAAAA 0xBBBB "e100" "Intel Etherblah blah"
>
> 6. Add this to /mnt/initrd/modules/module-info:
>
> e100
> eth
> "Intel Etherblah blah"
>
> 7. And unmount
>
> umount /mnt/initrd
> gzip /tmp/initrd
> cp /tmp/initrd.gz /mnt/floppy/initrd.img
> umount /mnt/floppy
>
> Should work.
>
> Chris
>
> --
> cmalek@xxxxxxxxxxx
> Nosce Teipsum
> Office: (626) 395-2593
> Fax: (626) 792-4257
> Mail Stop: 014-81
>
> _______________________________________________
> Kickstart-list mailing list
> Kickstart-list@xxxxxxxxxx
> https://listman.redhat.com/mailman/listinfo/kickstart-list
_______________________________________________
Kickstart-list mailing list
Kickstart-list@xxxxxxxxxx
https://listman.redhat.com/mailman/listinfo/kickstart-list
