On Mon, 5 Mar 2001, Ray Zupancic wrote:
> I'm not used to the issue of unsuppoted boot devices. I have an on-board
> SCSI controller (sym53c8(1010)) that isn't supported by the RH7 or RH6.2
> install. I have a disk image from LSILogic that allows me to use the
> linux dd install option on RH7, and I can get it working. There is no
> such image for RH6.2. Does anyone know (for 6.2):
>
> --are there instructions somewhere for building install-time driver disks?
> --If I build a kernel with static support for this SCSI, and use it to
> retool the boot.img (no trivial thing given the size constraints and the
> need to take stuff out of modules.cgz to find room) for the install, how
> do I then get this install kernel on the machine after it places it's
> packaged kernel on the machine?
>
> There is probably some simple way to do the latter that I just am not
> seeing--I broke out of the install script at the end and had some luck
> installing my own kernel, but that is arduous. This whole issue of
> unsupported boot devices is like a chicken and the egg runaround for me
> and I have no good grasp on the best strategy to use.
>
> Thanks for any help or advice you can give on this.
>
> --rayz
>
>
If you have the source code for the driver, and access to a working
system running the same kernel, you can try compiling it as a module,
and building a driver disk. I have not built a driver disk, so maybe
someone that has can help. I know install will ask for one if you do an
expert install.
I do not know if the install program will use the module off the driver
disk when building the initial RAM disk. You may have to copy the
module to the proper directory by hand before install builds it.
I wish I could give you specifics, but this will hopefully point you in
the right direction.
Mikkel
--
Do not meddle in the affairs of dragons,
for you are crunchy and taste good with ketchup.
_______________________________________________
Redhat-list mailing list
[EMAIL PROTECTED]
https://listman.redhat.com/mailman/listinfo/redhat-list
