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. It's rather cdrecord insisting on scanning buses itself and bitching about direct device names... > First problem is that cdrecord now must reload media often, runs slowly, > and burns slowly. Reading CD/RW disks burned under 2.6.x is much slower > than those burned under kernel 2.4 (same version of cdrecord in all > cases). 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. -- Matthias Andree Encrypt your mail: my GnuPG key ID is 0x052E7D95 - To unsubscribe from this list: send the line "unsubscribe linux-kernel" in the body of a message to majordomo _at_ vger.kernel.org More majordomo info at http://vger.kernel.org/majordomo-info.html Please read the FAQ at http://www.tux.org/lkml/
Follow-Ups:
- Re: kernel 2.6.1 and cdrecord on ATAPI busCharles Shannon Hendrix
- kernel 2.6.1 and cdrecord on ATAPI busCharles Shannon Hendrix
- Prev by Date: Re: 2.6.1-mm4
- Next by Date: Mouse issues in 2.6
- Previous by thread: Re: kernel 2.6.1 and cdrecord on ATAPI bus
- Next by thread: Re: kernel 2.6.1 and cdrecord on ATAPI bus
- Indexes:[Main][Thread]