From: Art Wagner <awagner@getnet.net>
To: Bob McElrath <mcelrath+kernel@draal.physics.wisc.edu>
Cc: Andre Hedrick <andre@linux-ide.org>,
Alan Cox <alan@lxorguk.ukuu.org.uk>,
linux-kernel@vger.kernel.org
Subject: Re: ide-scsi oops
Date: Sat, 07 Sep 2002 18:30:33 -0700 [thread overview]
Message-ID: <3D7AA839.8040805@getnet.net> (raw)
In-Reply-To: 20020908005032.GB4828@draal.physics.wisc.edu
I have found most of my problems with ide CD-R and CDRW answered by the
CD-Writing-HOWTO from;
http://www.linuxdoc.org/
Bob McElrath wrote:
> Andre Hedrick [andre@linux-ide.org] wrote:
>
>>On Sat, 7 Sep 2002, Bob McElrath wrote:
>>
>>Would you pass hdc=scsi for the next reboot?
>
>
> As this is an IDE device I'm not sure what hdc=scsi should do...
>
> However that seems to get rid of the oops. It appears to operate
> normally (I can mount CD's, DVD's, play DVD's, and play CD's).
> cdparanoia even works (with no sg module installed -- which I thought it
> needed) though while it's running the CPU usage jumps to 100%. :(
>
> I see that the Configure.help now says to use "hdx=scsi". I am not sure
> where I received the information to use "hdx=ide-scsi" but that did work
> with kernel 2.4.18.
>
> Cheers,
> -- Bob
>
> Bob McElrath
> Univ. of Wisconsin at Madison, Department of Physics
>
> "No nation could preserve its freedom in the midst of continual warfare."
> --James Madison, April 20, 1795
I have found most of my questions on ide-scsi answered in the
next prev parent reply other threads:[~2002-09-08 1:25 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2002-09-07 16:37 ide-scsi oops Bob McElrath
2002-09-07 18:01 ` Alan Cox
2002-09-07 18:26 ` Andre Hedrick
2002-09-07 18:33 ` Bob McElrath
2002-09-07 18:47 ` Andre Hedrick
2002-09-08 0:50 ` Bob McElrath
2002-09-08 1:30 ` Art Wagner [this message]
2002-09-08 1:01 ` Bob McElrath
-- strict thread matches above, loose matches on Subject: below --
2002-12-23 20:24 Luben Tuikov
2002-12-23 21:39 ` Willem Riede
2002-12-23 23:47 ` Douglas Gilbert
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=3D7AA839.8040805@getnet.net \
--to=awagner@getnet.net \
--cc=alan@lxorguk.ukuu.org.uk \
--cc=andre@linux-ide.org \
--cc=linux-kernel@vger.kernel.org \
--cc=mcelrath+kernel@draal.physics.wisc.edu \
/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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.