From: davidsen@tmr.com (bill davidsen)
To: linux-kernel@vger.kernel.org
Subject: Re: no atapi cdrecord burning with 2.6.0-test11-bk10 / bk13
Date: 17 Dec 2003 16:30:46 GMT [thread overview]
Message-ID: <brq0bm$69i$1@gatekeeper.tmr.com> (raw)
In-Reply-To: Pine.LNX.4.21.0312171604390.32339-100000@needs-no.brain.uni-freiburg.de
In article <Pine.LNX.4.21.0312171604390.32339-100000@needs-no.brain.uni-freiburg.de>,
Thomas Voegtle <thomas@voegtle-clan.de> wrote:
|
| Hello,
|
| cdrecord -dev=ATAPI -scanbus with 2.6.0-test11-bk10 and bk13 shows this:
|
| scsibus0:
| 0,0,0 0) '' '' '' NON CCS Disk
| 0,1,0 1) '' '' '' NON CCS Disk
|
|
| but this works well with 2.6.0-test11.
| =>
|
| 0,0,0 0) 'CREATIVE' ' CD5233E ' '2.05' Removable CD-ROM
| 0,1,0 1) 'PLEXTOR ' 'CD-R PX-W1610A' '1.04' Removable CD-ROM
|
| SuSE 9.0
|
| please cc me, I'm not subscribed
I see the same results, also using wli-2. I'll try mm1 as soon as it
completes compilation.
I assume that this breakage is unintentional, but it's not clear if it's
a bug in the kernel or cdrecord not coping with something actually fixed
in the kernel.
I may get a chance to look at it tomorrow, I don't think I have a stock
test11 kernel left :-(
--
bill davidsen <davidsen@tmr.com>
CTO, TMR Associates, Inc
Doing interesting things with little computers since 1979.
next prev parent reply other threads:[~2003-12-17 16:42 UTC|newest]
Thread overview: 16+ messages / expand[flat|nested] mbox.gz Atom feed top
2003-12-17 15:09 no atapi cdrecord burning with 2.6.0-test11-bk10 / bk13 Thomas Voegtle
2003-12-17 15:20 ` Måns Rullgård
2003-12-17 16:08 ` Thomas Voegtle
2003-12-17 17:23 ` Martin Schlemmer
2003-12-17 16:19 ` Gene Heskett
2003-12-17 16:25 ` Thomas Voegtle
2003-12-17 16:41 ` Gene Heskett
2003-12-17 16:49 ` Jens Axboe
2003-12-17 17:27 ` Gene Heskett
2003-12-17 18:33 ` Jens Axboe
2003-12-17 21:47 ` bill davidsen
2003-12-17 16:30 ` bill davidsen [this message]
2003-12-17 16:48 ` Jens Axboe
2003-12-17 17:35 ` Thomas Voegtle
2003-12-17 18:11 ` Martin Schlemmer
2003-12-17 18:32 ` Jens Axboe
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='brq0bm$69i$1@gatekeeper.tmr.com' \
--to=davidsen@tmr.com \
--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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox