Hi
I also had problem making a custom boot floppy
useding Chuck's script so i made so changes to it
and now it's working, (Thanks Chuck)
god luck
/Jugge
On Tuesday 22 May 2001 10:34, you wrote:
> Hi
>
> I'm desperatly trying to make custom bootnet disk.
> Indeed my ethernet driver are on the driver disk.
>
> I have followed the instruction of the page
> http://www.introcomp.co.uk/linux/bootdisk.html
> modified with the post of Chuck Moss in the list
> I make my kickstart file with mkkickstart
>
> I got the disk made but when i boot i go on interactive
> mode with the message on the console screen
>
> unknow module 8139too
> no suitable driver for kickstart installation
>
> 8139too is the driver for my ethernet card.
>
> Can someone help me?
>
> Thanks in advance
# License: Gnu Public License
# Author: Jörgen Johansson
# Description: Step by step instuctons for add/remove drivers for redhat 7.1
# boot floppy image.
#
# Credits: To Chuck Moss for his mod_boot_floppy.sh,v 1.2 as it was used
# for guidelines.
Change the content on your Bootdisk add/remove drivers
prereq.
copy of the standard boot and drivers images
/mnt/cdrom/images/bootnet.img and drivers.img
1. Set things up for us
1. mkdir /tmp/boot
2. mkdir /tmp/boot/custum_img
3. mkdir /tmp/boot/initrd_img
4. mkdir /tmp/boot/modules
5. mkdir /tmp/drivers
6. mkdir /tmp/drivers/drivers_img
7. mkdir /tmp/drivers/modules
8. cp /mnt/cdrom/images/bootnet.img /tmp/boot/custom.img
9. cp /mnt/cdrom/images/drivers.img /tmp/drivers/
2. Mount and decompress the files from boot image
1. get into boot working dir. cd /tmp/boot
2. mount custum.img as filesystem mount -o loop custum.img custum_img
3. decompress the initrd gzip -dc custum_img/initrd.img >initrd.ext2
4. mount initrd.ext2 as filesystem mount -o loop initrd.ext2 initrd_img
5. get modules from initrd_img gzip -dc initrd_img/modules/modules.cgz >modules.cpio
6. extract cpio archive into /tmp/boot/modules cd /tmp/boot/modules; cpio -idumv </tmp/boot/modules.cpio
3. Mount and decompress the files from drivers image
1. get into images working dir. cd /tmp/drivers
2. mount drivers.img as filesystem mount -o loop drivers.img drivers_img
3. get modules from drivers_img gzip -dc drivers_img/modules.cgz >modules.cpio
4. extract cpio archive into /tmp/drivers/modules cd /tmp/drivers/modules; cpio -idumv </tmp/drivers/modules.cpio
4. Make the changes that's requeried i.e get new modules in place
1. copy new modules from /tmp/drivers/modules/2.4.2-2BOOT to /tmp/boot/modules/2.4.2-2BOOT
2. remove unwanted modules in 2.4.2-2BOOT
3. edit /tmp/boot/initrd_img/modules/module-info remove old modules enter info for new modules /tmp/drivers/drivers_img/modinfo
4. check /tmp/drivers_img/modules.dep to find new dependencies if any update /tmp/boot/initrd_img/modules/modules.dep
5. check /tmp/drivers_img/pcitable to find new hardware update /tmp/boot/initrd_img/modules/pcitable
5. Rebuild the new boot disk
1. get into modules dir. cd /tmp/boot/modules
2. create new modules.cpio file find 2.4.2-2BOOT -print -depth |cpio -H crc -ovF modules.cpio 2> /dev/null
3. compress modules.cpio gzip -S .cgz modules.cpio
4. remove old modules.cgz rm /tmp/boot/initrd_img/modules/modules.cgz
5. mv new modules.cgz in place mv modules.cpio.cgz /tmp/boot/initrd_img/modules/modules.cgz
6. get into boot dir. cd /tmp/boot/initrd_img
7. create zerofile touch zerofile
8. fill up filesystem with zero's cat /dev/zero >zerofile 2> /dev/null
9. sync filesystem to disk sync
10. remove zerofile rm zerofile
12. cd /tmp/boot
11. unmount initrd filesystem umount initrd_img
12. recompress initrd.ext2 gzip initrd.ext2
13. remove old initrd.img rm custum_img/initrd.img
14. place new initrd on boot img mv initrd.ext2.gz custum_img/initrd.img
15. unmount bootnet filesystem umount custum_img
6. place custum.img on boot disk
1. dd if=custum.img of=/dev/fdo
