I've had a similar problem. It's kind of a chicken and egg problem, in
that even if you can somehow load the driver at install time, it will
probably not make it into the initrd file, so your computer won't be able
to boot.
The easiest way is to first install a version that DPT has install disks
for and compile a kernel for the box, so that you will be able to reboot
it after the 6.1 install (they have install disks for 5.2 and 6.0 in the
support section of their web site, as well as a kernel patch).
What I ended up doing then was to download the newest boot/updates images.
I downloaded the 6.1 default kernel and compiled it WITH module support,
to get the dpt_i2o.o module. What I thought should be easy wasn't --
putting this module onto a driver disk like the one on the RH site. There
must be more to it than meets the eye. What I did was mounted the disk
driver disk image using the loop device so that I could copy the module to
it, and then used dd to write out the disk image to the floppy.
For the install, I did a 'linux dd updates text'. After the disk update
part, at the earliest point you can get a bash prompt BEFORE the updates
disk gets read, go to the bash prompt (alt-f2). You now need to remount
the dd disk - so mkdir f, mount -t vfat fd0 f, and insmod dpt_i2o.o -f,
umount f.
This gets kind of hairy for two reasons off the top of my head:
1) The install kernel is a different module version than the regular
source (it has BOOT on it), so you need to force the insmoding of it with
-f.
2) The updates disk blows away the module loader binary off the ramdisk
because otherwise the ramdisk doesn't have enough space on it for the
updates stuff.
With any luck, in one of the other sessions, I forget which, you should
see the messages come up about it detecting /dev/sda, etc. This would
indicate success. Then continue on with the install.
Sadly, this method gets it installed, but does not yield a bootable system
since the boot floppy and kernel that get installed don't know to include
the dpt_i2o.o in the initrd, which someone more knowledgeable than I could
probably get around. This is why it is important the system be bootable
with the DPT driver first before upgrading, since then you will have at
least a bootable kernel in place. Once the system is up again after the
upgrade it is a simple matter to recompile or whatever and be up and
running.
If anyone has better ideas on this, I would love to hear them! I think the
disk driver idea would be useful if someone could figure out exactly what
needs to go in there to make this work! (What I had problems with was the
pcitable entries apparently not matching or something to get it to
recognize the card and this load the driver for it).
Hope this helps.
Terry
===
Terry Letsche | Internet Navigator | [EMAIL PROTECTED] | http://letsche.inav.net
--
To unsubscribe: mail [EMAIL PROTECTED] with "unsubscribe"
as the Subject.
