From: Jens Axboe <axboe@suse.de>
To: Chris Clayton <chris@theclaytons.giointernet.co.uk>
Cc: Alan Jenkins <sourcejedi@phonecoop.coop>, linux-kernel@vger.kernel.org
Subject: Re: CDMRW in 2.6
Date: Fri, 13 Aug 2004 13:47:11 +0200 [thread overview]
Message-ID: <20040813114711.GM2663@suse.de> (raw)
In-Reply-To: <200408131247.58289.chris@theclaytons.giointernet.co.uk>
On Fri, Aug 13 2004, Chris Clayton wrote:
> On Friday 13 Aug 2004 08:01, Jens Axboe wrote:
> > (don't trim cc lists...)
> >
> > On Fri, Aug 13 2004, Alan Jenkins wrote:
> > > Jens Axboe wrote:
> > > >On Mon, Aug 09 2004, Chris Clayton wrote:
> > > >>cdrom: hdc: mrw address space DMA selected
> > > >>cdrom open: mrw_status 'mrw complete'
> > > >>hdc: command error: status=0x51 { DriveReady SeekComplete Error }
> > > >>hdc: command error: error=0x54
> > > >>end_request: I/O error, dev hdc, sector 1048576
> > > >
> > > >Command was aborted, probably the media isn't writable after all. Can
> > > >you try and force a full format with cdrwtool?
> > >
> > > I don't like to sound critical or "me too"-ish, but I have had the same
> > > problem with my LiteOn Combo SOHC-5232K. The error and status codeswere
> > > the same. I contacted Jens Axboe, but he wasn't able to help me and
> > > suggested it was a firmware problem. I'll try the suggestion. I hope
> > > this isn't a problem with a ll LiteOn drives.
> >
> > It is suspicious, since Chris is using a LiteOn as well. I have no clues
> > what is wrong so far, I can just see that it's aborting the write
> > command.
>
> Actually, it's even more suspicious than that. As I said in the first
> message in this thread, this is my second Lite-on drive - I replaced
> the original (with a model that mt-rainier.org/ shows as being
> validated) in an attempt to get Mt Rainier working. Furthermore, my
> attempts to find a solution on LKML unearted a posting by Doug
> Holland, who was also reporting problems with a Lite-on drive
> (http://marc.theaimsgroup.com/?l=linux-kernel&m=107955822109371&w=2).
I have a few drives here, it works fine for me. The implementation is
constructed after the first pre-drafts of mt rainier. I'd like to get it
working on the Lite-on, without a drive (or acces to one) it's going to
be time consuming.
--
Jens Axboe
next prev parent reply other threads:[~2004-08-13 11:48 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
2004-08-09 16:25 Chris Clayton
2004-08-12 20:23 ` Bill Davidsen
2004-08-13 12:08 ` Chris Clayton
2004-08-13 7:15 ` Jens Axboe
2004-08-13 7:55 ` Alan Jenkins
2004-08-13 8:01 ` Jens Axboe
2004-08-13 12:47 ` Chris Clayton
2004-08-13 11:47 ` Jens Axboe [this message]
2004-12-22 1:24 ` Daniel Drake
2004-08-13 12:53 ` Chris Clayton
2004-08-13 11:54 ` Jens Axboe
2004-08-13 14:35 ` Chris Clayton
2004-08-13 13:50 ` Jens Axboe
2004-08-13 16:15 ` Chris Clayton
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=20040813114711.GM2663@suse.de \
--to=axboe@suse.de \
--cc=chris@theclaytons.giointernet.co.uk \
--cc=linux-kernel@vger.kernel.org \
--cc=sourcejedi@phonecoop.coop \
/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
Powered by JetHome