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