Hi Leonard
Thanks for the comments. You are entirely correct, except perhaps for the
last part here about what did and did not work for me. I did indeed build
the modules and install them - after all everything works fine once it
boots.
Clearly booting a scsi system with a modular kernel works - it's done all
the time.
My current experience:
1. booting off floppy worked - stock kernel, and modules
2. booting off custom kernel with scsi support worked
3. booting off disk worked - stock kernel, and modules, and initrd.img
from floppy copied to /boot
BUT
booting off the disk with stock kernel and modules failed without the
initrd.img off the floppy. The only difference i can see here is that the
initrd I (and the 6.2 installer) created is not working (at least with
that module's option).
So other than not understanding what is wrong with the initrd.img I
created, there are no mismatch issues.
I fear I might have drug this thread on too long as it is, but I have yet
to try one suggestion from brother Borho - not using the io argument, or
calling it ioport. Perhaps I will try that tomorrow and end this ordeal :)
charles
On Thu, 3 Aug 2000, Leonard den Ottolander wrote:
<snip>
> Charles wrote:
> > Actually I just chickened out and compiled the aha1542 support into the
> > kernel :0
>
> So, if you can boot using this aha1542 controller you could boot using an
> initrd containing the module. It makes no difference whether you use a kernel
> with the driver compiled in or you use a module and an initrd. Use what you
> like best. If you are using the SCSI drive as / it's not a bad idea to compile
> aha1542 support into the kernel.
> One thing to take care of when using modules, use matching modules/kernel. If
> you try using the initrd.img from the bootfloppy, you should also use the
> kernel from the floppy.
>
> > loading aha1542 module
> > /lib/aha1542.o: invalid parameter parm_io
>
> might indicate such a conflict. Maybe you built a new kernel and forgot to
> make or install the new modules?
>
> Hope this helps you even further ;),
>
> Leonard.
--
To unsubscribe: mail [EMAIL PROTECTED] with "unsubscribe"
as the Subject.
