From: Andrew Schulman <andrex@alumni.utexas.net>
To: Jamie Lenehan <lenehan@twibble.org>
Cc: linux-scsi@vger.kernel.org, dc395x@twibble.org
Subject: Re: dc395x: CD writer causes endless "sg_to_virt failed" loop
Date: Wed, 31 Mar 2004 03:29:17 -0500 [thread overview]
Message-ID: <200403310329.17654.andrex@alumni.utexas.net> (raw)
In-Reply-To: <20040330035115.GA3680@twibble.org>
> So you could wait for 2.6.5-rc3/2.6.5 to be released, upgrade to
> 2.6.5-rc3-bkx (where bkx is a bk snapshot with x >=2), or go back to the
> kernel you were using previously but copy the drivers/scsi/dc395x.c and
> drivers/scsi/dc395x.h from the 2.6.5-rc2 kernel into it.
Good news: my drive works properly now in 2.6.5-rc3. "sg_to_virt failed"
messages are gone and the drive operates normally. Unfortunately, my nvidia
driver won't compile in that kernel...
FYI, copying dc395x.{c,h} from 2.6.5-rc3 into 2.6.3 source didn't work. The
driver built okay, but at insertion time I got error messages about
unresolved symbols.
Anyway, it looks like you've corrected the CD drive problem. Thanks. Now I
just hope the nvidia problem gets resolved by the time 2.6.5 is released.
Andrew.
next prev parent reply other threads:[~2004-03-31 8:29 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2004-03-27 14:57 dc395x: CD writer causes endless "sg_to_virt failed" loop Andrew Schulman
2004-03-27 16:10 ` Jamie Lenehan
2004-03-29 4:03 ` Andrew Schulman
2004-03-30 3:51 ` Jamie Lenehan
2004-03-31 8:29 ` Andrew Schulman [this message]
[not found] ` <200403271759.08361.andrex@alumni.utexas.net>
2004-04-05 5:20 ` Andrew Schulman
2004-04-06 14:01 ` Jamie Lenehan
2004-04-06 16:06 ` Andrew Schulman
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=200403310329.17654.andrex@alumni.utexas.net \
--to=andrex@alumni.utexas.net \
--cc=dc395x@twibble.org \
--cc=lenehan@twibble.org \
--cc=linux-scsi@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