From: Charles Shannon Hendrix <shannon@widomaker.com>
To: Linux Kernel <linux-kernel@vger.kernel.org>
Subject: Re: kernel 2.6.1 and cdrecord on ATAPI bus
Date: Sat, 17 Jan 2004 10:49:05 -0500 [thread overview]
Message-ID: <20040117154905.GB26248@widomaker.com> (raw)
In-Reply-To: <20040117042208.GA8664@merlin.emma.line.org>
[-- Warning: decoded text below may be mangled, UTF-8 assumed --]
[-- Attachment #1: Type: text/plain; charset=unknown-8bit, Size: 1251 bytes --]
Sat, 17 Jan 2004 @ 05:22 +0100, Matthias Andree said:
> On Fri, 16 Jan 2004, Charles Shannon Hendrix wrote:
>
> > I'm now running kernel 2.6.1, and using cdrecord with ATAPI is
> > problematic.
>
> I don't find it is.
Well, some of us are lucky that way...
> It's rather cdrecord insisting on scanning buses itself and bitching
> about direct device names...
Scanning busses doesn't appear to be the problem.
>From looking at strace, I see it scanning all devices themselves and
then trying ioctl(3,...) on them if they exist.
It isn't complaining about direct device names at all, and it finds the
right one and attempts to use it.
ioctl() fails with an EIO error a few times and cdrecord prints an error
than it can't read the drive.
> Interesting. I use dev=/dev/hdc and it works fine for me (Plextor 48X),
> but then again, I'm also running the latest cdrecord alpha.
% cdrecord -version
Cdrecord 2.00.3 (i686-pc-linux-gnu) Copyright (C) 1995-2002 Jörg Schilling
I can try an alpha version, but from running strace on cdrecord, it
seems like Linux is the problem. Several ioctl() calls are failing just
before cdrecord prints an error message and exits.
--
UNIX/Perl/C/Pizza____________________s h a n n o n@wido !SPAM maker.com
next prev parent reply other threads:[~2004-01-17 16:43 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2004-01-17 3:19 kernel 2.6.1 and cdrecord on ATAPI bus Charles Shannon Hendrix
2004-01-17 4:08 ` Måns Rullgård
2004-01-17 4:22 ` Matthias Andree
2004-01-17 15:49 ` Charles Shannon Hendrix [this message]
2004-01-17 17:36 ` Andreas Schwab
2004-01-17 18:54 ` Charles Shannon Hendrix
2004-01-17 22:45 ` Gene Heskett
2004-01-25 17:44 ` Jens Axboe
2004-01-26 2:17 ` Bill Davidsen
2004-01-26 15:38 ` Ken Moffat
2004-01-27 0:59 ` Charles Shannon Hendrix
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=20040117154905.GB26248@widomaker.com \
--to=shannon@widomaker.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