public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: "P. Christeas" <p_christ@hol.gr>
To: Mike Houston <mikeserv@bmts.com>
Cc: lkml <linux-kernel@vger.kernel.org>
Subject: Re: 2.6.0-test9 breaks cdrecord w. ide-scsi device
Date: Fri, 31 Oct 2003 17:35:44 +0200	[thread overview]
Message-ID: <200310311735.45859.p_christ@hol.gr> (raw)
In-Reply-To: <20031030171432.03dcaa76.mikeserv@bmts.com>

> Hello
>
> I don't really know what the problem with ide-scsi is (I'm not much of a
> programmer) but is there any particular reason you're clinging to the old
> ide-scsi method for CD writing? This has been broken a few times now in the
> 2.5/2.6 tree. Even when it is working, it's still somewhat broken and they
> know it. I have found that the maximum speed I can get is 16x using
> ide-scsi in the 2.6 tree.
>
> There is now ide-cd writing support, and cdrecord 2 supports it. I build
> that stuff modular, so I just load the ide-cd and isofs modules (modprobe
> takes care of the rest). I achieve the fastest writing speeds I've ever
> had, using this driver. Far better than ide-scsi or even Sleazy CD Creator
> in Windows.
>
> In the cdrecord command, everything is the same except you use
> dev=/dev/hdxx instead of the dev=x,x,x scsi target notation. For example:
>
> cdrecord -v speed=48 dev=/dev/hdd -data filename.iso
>
> Just in case you didn't know this or have never tried this. I hope it helps
> you.
>
It's true that I hadn't tried the native ATAPI method lately.
My point, however, was that there is a regression from -test8 to -test9 about 
cdrecord-ing.


  parent reply	other threads:[~2003-10-31 15:35 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2003-10-30 22:12 2.6.0-test9 breaks cdrecord w. ide-scsi device P. Christeas
     [not found] ` <20031030171432.03dcaa76.mikeserv@bmts.com>
2003-10-31 15:35   ` P. Christeas [this message]
2003-11-01 10:19   ` P. Christeas
2003-11-21 17:34     ` bill davidsen

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=200310311735.45859.p_christ@hol.gr \
    --to=p_christ@hol.gr \
    --cc=linux-kernel@vger.kernel.org \
    --cc=mikeserv@bmts.com \
    /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