From: James Lamanna <jlamanna@its.caltech.edu>
To: linux-kernel@vger.kernel.org
Subject: Fasttrak100 questions...
Date: Fri, 24 Nov 2000 14:46:32 -0800 [thread overview]
Message-ID: <3A1EEFC8.16A48C24@its.caltech.edu> (raw)
So, I have a system that has 2 45GB IDE drives connected
up to a Promise Technologies Fasttrack 100.
Promise Techonologies currently has a driver that you can compile
against a 2.2 kernel into a module, but it also includes one
proprietary object file.
During my linux installation I was able to preload the module and
have it detect the drives fine as a scsi device, so I was able to
install the base system onto them.
The question is, is there a way to compile this module into the kernel
so that it will automatically detect the card? A simple linking of the
module into the scsi library by editing the Makefile doesn't seem to do
it. It doesn't detect the drives if I boot off of a floppy with this
kernel on it.
Also, is it possible for Lilo to even boot this without a RAM disk
somewhere? I guess Lilo has to know about the drive, but it can't know
without the module...so am I screwed into using floppies with a
RAM disk image anyways?
Thanks,
--James Lamanna
-
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@vger.kernel.org
Please read the FAQ at http://www.tux.org/lkml/
next reply other threads:[~2000-11-24 23:09 UTC|newest]
Thread overview: 34+ messages / expand[flat|nested] mbox.gz Atom feed top
2000-11-24 22:46 James Lamanna [this message]
2000-11-25 1:35 ` Fasttrak100 questions Andre Hedrick
2000-11-25 12:10 ` Henning P. Schmiedehausen
2000-11-25 17:20 ` Andre Hedrick
2000-11-25 17:22 ` Andre Hedrick
2000-11-29 19:53 ` Dr. Kelsey Hudson
2000-11-29 20:08 ` Henning P . Schmiedehausen
2000-11-29 21:11 ` Andre Hedrick
2000-11-29 22:12 ` Stop your abusive language! (Re: Fasttrak100 questions...) Dominik Kubla
2000-11-29 23:52 ` Fasttrak100 questions Jeff V. Merkey
2000-11-30 15:14 ` Christopher Friesen
2000-11-30 18:43 ` Jeff V. Merkey
2000-11-30 18:09 ` Christopher Friesen
2000-11-30 20:10 ` Jeff V. Merkey
2000-12-02 3:44 ` Peter Samuelson
2000-12-03 22:54 ` Pavel Machek
2000-12-05 4:10 ` Peter Samuelson
2000-11-29 20:42 ` Alan Cox
2000-11-29 21:05 ` Andre Hedrick
2000-11-29 21:10 ` James A Sutherland
2000-11-29 21:18 ` Alan Cox
2000-11-29 21:30 ` Andre Hedrick
2000-12-02 16:50 ` Pavel Machek
2000-12-02 17:18 ` Alan Cox
2000-12-02 23:46 ` Theodore Y. Ts'o
2000-12-03 1:21 ` Jeff V. Merkey
2000-12-03 1:31 ` Jeff V. Merkey
2000-12-03 3:42 ` Theodore Y. Ts'o
2000-12-03 5:11 ` Jeff V. Merkey
2000-12-05 7:07 ` Brian F. G. Bidulock
2000-12-05 8:25 ` Jeff V. Merkey
-- strict thread matches above, loose matches on Subject: below --
2000-12-03 16:41 Wayne.Brown
2000-12-03 17:49 ` Pavel Machek
2000-12-03 18:45 ` Alan Cox
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=3A1EEFC8.16A48C24@its.caltech.edu \
--to=jlamanna@its.caltech.edu \
--cc=linux-kernel@vger.kernel.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox