Todd> Is there any chance you have checked the bootparm-howto?
Todd>
Todd> http://sunsite.unc.edu/mdw ??
If you install Debian's doc-linux package, they are also at
/usr/doc/HOWTO/*
As the doc-linux package is updated monthly with the upstream HOWTOs, you
should always look for
> From: [EMAIL PROTECTED] (renald loignon)
> > May I ask, in all seriousness, and without a trace of sarcasm, where in
> > the world (BUT preferably in the Debian installation instructions) one
> > is expected to find this information? I was used to the old
> > "cdu31a=0xPORT,IRQ" syntax from the
Lars:
> Ilucius ([EMAIL PROTECTED]) took it from me
From: llucius <[EMAIL PROTECTED]>
> Yep, your right. I neglected to inform anyone. (face red in shame)
> I've been playing around with this architecture independence stuff that I
> COMPLETELY forgot about it.
Leland, of course I'm happy to g
>Susan:
>> I'm getting confused. Isn't the purpose of /usr/lib/module_help/arguments
>> to document the arguments that can be given to a module when it is
>> activated?
>I don't think the cdu31a information is in there - we must have missed
>it when we created modconf. Also, not everyone uses mod
On Tue, 20 Aug 1996, Lars Wirzenius wrote:
> Bruce Perens:
> > We don't have a person who follows the kernel and keeps an accurate list
> > of module arguments. Also, Lars took on "modconf" when I had too much to
> > do, but he was less than enthusiastic about it. We could use another
> > voluntee
Bruce Perens:
> We don't have a person who follows the kernel and keeps an accurate list
> of module arguments. Also, Lars took on "modconf" when I had too much to
> do, but he was less than enthusiastic about it. We could use another
> volunteer to be the module mayven.
Ilucius ([EMAIL PROTECTED]
Susan:
> I'm getting confused. Isn't the purpose of /usr/lib/module_help/arguments
> to document the arguments that can be given to a module when it is
> activated?
I don't think the cdu31a information is in there - we must have missed
it when we created modconf. Also, not everyone uses modconf,
Bruce Perens wrote:
> From: [EMAIL PROTECTED] (renald loignon)
> > May I ask, in all seriousness, and without a trace of sarcasm, where in the
> > world (BUT preferably in the Debian installation instructions) one is
> > expected to find this information? I was used to the old
> > "cdu31a=0xPORT,I
From: [EMAIL PROTECTED] (renald loignon)
> May I ask, in all seriousness, and without a trace of sarcasm, where in the
> world (BUT preferably in the Debian installation instructions) one is
> expected to find this information? I was used to the old
> "cdu31a=0xPORT,IRQ" syntax from the boot promp
>Use the argument "cdu31a_port=0x340" when you install the module. It also
>understands "cdu31a_irx=N".
May I ask, in all seriousness, and without a trace of sarcasm, where in the
world (BUT preferably in the Debian installation instructions) one is
expected to find this information? I was used t
Hi Michael!
On Sun, 18 Aug 1996 [EMAIL PROTECTED] wrote:
> The drive is defaulted onto 0x340; when I try to add a parameter to the module
> insertion it either fails the same way or gives me an invalid parameter
> message.
Have you tried with the following parameter?
cdu31a_port=0x340
Bye & Go
From: [EMAIL PROTECTED]
> Things go OK until I try to add the cdu31a module to support the CDU33A CDROM
> drive in the Gateway: it fails to insert.
> The drive is defaulted onto 0x340; when I try to add a parameter to the module
> insertion it either fails the same way or gives me an invalid parame
12 matches
Mail list logo
