From: Markus Plail <linux-kernel@gitteundmarkus.de>
To: linux-kernel@vger.kernel.org
Subject: Re: cdrecord and 2.5 kernels
Date: Sun, 01 Jun 2003 20:21:02 +0200 [thread overview]
Message-ID: <87y90lveup.fsf@gitteundmarkus.de> (raw)
In-Reply-To: <8765nqnvyv.fsf@gitteundmarkus.de> (Markus Plail's message of "Sun, 01 Jun 2003 08:38:32 +0200")
On Sun, 01 Jun 2003, Markus Plail wrote:
> I just compiled a few kernels and realized that 2.5.45 was the kernel
> that broke writing DVD/CD-Rs for me. The messages at the bottom are
> from 2.5.70 plus the second sg_io patch.
And now I realized something even more strange: My old acer writer
works just fine with 2.5.70 and ide-cd.
Both work fine when I use ide-scsi. I also swapped the drives to see if
it's a problem with the cabling or the order in which they are
connected to the bus. Nothing changed.
Also with 2.5.44, where I don't get the same error, the TEAC doesn't
work 100% either. Burning a CD-R with it, which should be possible at
max. 16x I get a speed about 67x, both with cdrdao and cdrecord. The so
burned CD-R aren't readable.
regards
Markus
prev parent reply other threads:[~2003-06-01 18:07 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2003-06-01 6:38 cdrecord and 2.5 kernels Markus Plail
2003-06-01 18:21 ` Markus Plail [this message]
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=87y90lveup.fsf@gitteundmarkus.de \
--to=linux-kernel@gitteundmarkus.de \
--cc=linux-kernel@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 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.