Using cdrecord on 2.6.9

[Collins Richey]

On Fri, 22 Oct 2004 23:08:45 -0500, David Bandel <david.bandel at gmail.com> wrote:
> On Fri, 22 Oct 2004 22:34:43 -0400, Kurt Wall <kwall at kurtwerks.com> wrote:
> >
> > Okay, how the heck do I use cdrecord on kernel 2.6.9? I know that
> > "hdd=ide-scsi" has gone away in the 2.6 kernel, replaced by "hdd=scsi".
> > The kernel at least saw this boot param, as this snippet from dmesg shows:
> >
> > Kernel command line: BOOT_IMAGE=269 ro video=rivafb:1600x1200 hdd=scsi
> > ide_setup: hdd=scsi
> >
> > It's also properly detected my IDE CD-RW:
> >
> > hdd: OPTORITE CD-RW CW4802, ATAPI CD/DVD-ROM drive
> > [...]
> > ide-cd: passing drive hdd to ide-scsi emulation.
> 
> I have an Optorite as well and it has been giving me fits.  Won' t
> work any more with SCSI emulation.  Unfortunately, I get a warning
> using IDE and a hang, but the gist of what you should now be doing is:
> 
> rip out all the SCSI emulation (especially from the boot sequence),
> but also all the modules.
> 
> once the above is done, try:
> cdrecord ATA: -scanbus
> 
> In your cdrecord (in /etc), put:
> CDR_DEVICE=cdrw
> cdrw=ATA:1,0,0  12      16m     ""
> 
> the cdrw line is ATA: followed by the value returned by cdrecord ATA:
> -scanbus for your cdrw device, followed by the recording speed,
> followed by the buffer size, followed by "" or perhaps burnfree.
> 
> >
> > So far, so good. No joy with cdrecord -scanbus, though:
> >
> > # cdrecord -scanbus
> > drecord 2.00.3 (i686-pc-linux-gnu) Copyright (C) 1995-2002 J?rg Schilling
> > cdrecord: No such file or directory. Cannot open '/dev/pg*'. Cannot open SCSI driver.
> > cdrecord: For possible targets try 'cdrecord -scanbus'. Make sure you are root.
> > cdrecord: For possible transport specifiers try 'cdrecord dev=help'.
> >
> > Am I missing drivers? This all worked just fine under 2.4.2x.
> 
> Mine returns warnings about a broken IDE then hangs when I try to use
> it, so I'm not yet sure what I'm missing, but the above should help
> get you started.
> 

In the kernels prior to 2.6.8, cdrecord was seemingly immune to the
dma setting, but now if dma is set the driver hangs the system. Just
include 'hdparm d 0 /dev/hdx' or change your hdparm setting (for me
this is /etc/conf.d/hdparm on gentoo). I have a desktop and a laptop
system. Without any human intervention, the laptop starts with dma
disabled for the cdwriter, but the desktop turns on dma without being
asked.

Meanwhile, I'm curious if the cdrecord author will ever do anything
except gripe that the kernel api for cdwriter devices has changed.
This is one of the drawbacks of needing to rely on code that is not
really open source. nvidia, at least, seems marginally more responsive
to changes in the kernel.

-- 
 /\/\
(CR) Collins Richey
 \/\/        "I hear you're single again." "Spouse 2.0 had fewer bugs than
              Spouse 1.0, but the maintenance ... was too much for my OS."
                  - Glitch (tm)