Hi Dan,

> - compile the .h and .c from dandelion.com in the linux src tree.  (make
> modules)
> - take the resulting DAC960.o file and gzip it. copy the DAC960.o.gz to
> /mnt/floppy and rename it modules.cgz.

 That procedure is not correct. cgz stands for .cpio.gz, so it is a gzipped 
cpio archive. What you want to do is decompress the existing modules.cgz, add 
your new module to it and make it into an gzipped archive again, something 
like:

a)cp /work/modules.cgz /work/modules.cpio.gz
b) gzip -d /work/modules.cpio.gz
c) cpio -i -F /work/modules.cpio --list > mod-list
d) cpio -i -F /work/modules.cpio -d
 This creates the file mod-list and the directory containing the modules.
This directory contains the driver files.
e) copy your module to this directory
f) You must add the added drivers to mod-list
Reconstruct the archive:
g) cpio -o < mod-list > modules.cpio
h) gzip -9 modules.cpio

 You now have a usable modules.cgz.

> - create a modinfo file like the following:
> Version 0
> DAC960
>       scsi
>       "Mylex AcceleRaid 352 DAC960"
> 
> But then what do I put in the pcitable file?

 In the pcitable file you make an entry with the module name, a descriptor, 
and both manufacturer and device ID. These ID's are shown at boot by the bios.

 Concerning the end of your subject line "Driver disk creation - where do I 
find the .config file that was used to create the driver disk vmlinuz file?", 
I think the kernel image is probably the same image as in the package kernel-
BOOT-##. You can find the standard config files in the source tree 
(/usr/src/linux/configs). You most probaly need the kernel-BOOT config when 
compiling modules for a driver disk. For your installed system you need the 
"full" driver though. I don't know how RedHat usually handles this, but you 
might have to post install the full driver by hand.
 You can also check the kernel-BOOT package to see if there is a precompiled 
module you can use.

                                Bye,

                                Leonard.

 P.S. I wrote a kind of rough mini howto on how to edit a (net)boot floppy, 
which is rather appropriate to this situation (if you know how to fill in the 
differences). I'll send the question and my answer to it to you off list.



_______________________________________________
Redhat-list mailing list
[EMAIL PROTECTED]
https://listman.redhat.com/mailman/listinfo/redhat-list

Reply via email to