Re: CD Writer does not work for audio CD

From: Robert Storey (y2kbug_at_ms25.hinet.net)
Date: 12/31/03

  • Next message: Robert Storey: "Re: "best practices" on debian"
    Date: Wed, 31 Dec 2003 22:00:43 +0800
    To: debian-user@lists.debian.org
    
    

    I've always had bad luck with CDBakeoven. Things have worked much better
    (for me at least) with K3b and XCDRoast.

    That having been said, before you can get any atapi CD drive to work
    with cdrecord, you need to enable scsi emulation. It's a (minor) pain,
    and I've heard that this won't be necessary with the 2.6 kernel, but for
    the 2.4.x kernel it's required. Look at the output of "cdrecord
    -scanbus" to see if you have scsi emulation already enabled:

    bob@sonic:~> cdrecord -scanbus
    Cdrecord-Clone 2.01a19 (i686-pc-linux-gnu) Copyright (C) 1995-2003 Jörg
    Schilling
    Linux sg driver version: 3.1.25
    Using libscg version 'schily-0.7'
    scsibus0:
    cdrecord.mmap: Warning: controller returns wrong size for CD
    capabilities page.
            0,0,0 0) 'ATAPI-CD' 'ROM-DRIVE-52MAX ' '52GV' Removable
    CD-ROM
            0,1,0 1) 'RICOH ' 'MP7520A ' '1.25' Removable
    CD-ROM
            0,2,0 2) *
            0,3,0 3) *
            0,4,0 4) *
            0,5,0 5) *
            0,6,0 6) *
            0,7,0 7) *

    If that didn't work, see below...

    I don't know if you're booting with lilo or grub, but you need to pass
    an option similar to this to the kernel in /etc/lilo.conf or
    /boot/grub/menu.lst:

      hdc=scsi hdd=scsi

    In the above case, my two CD drives are /dev/hdc and /dev/hdd - it won't
    work for you if your drive(s) are configured differently. One good way
    to find out what you've got is to use the eject command, for example:

      eject /dev/hdc

    If the drive ejects, you know that one is /dev/hdc.

    You may also need to edit file /etc/fstab (backup the old one first).
    Something like this:

      /dev/cdrom /cdrom iso9660 defaults,ro,user,noexec,noauto 0 0
      /dev/cdrom1 /cdrom1 iso9660 defaults,ro,user,noexec,noauto 0 0

    Make sure you do have the directories /cdrom and /cdrom1 - create them
    if you don't.

    Finally, you need symbolic links for the above devices. Delete the
    existing ones, and create new ones:

      rm /dev/cdrom
      rm /dev/cdrom1
      ln -s /dev/scd0 /dev/cdrom
      ln -s /dev/scd1 /dev/cdrom1

    Check to make sure this worked:

      bob@sonic:~> ls -l /dev/cdrom*
      lrwxrwxrwx 1 root root 9 Dec 21 20:45 /dev/cdrom ->
    /dev/scd0
      lrwxrwxrwx 1 root root 9 Dec 21 20:45 /dev/cdrom1 ->
    /dev/scd1

    That ought to do it. Reboot.

    cdrecord -scanbus should report good results now.

    Hope that helps. (Also, hope I got all of the above correct - if not,
    I'm prepared to be flamed, drawn, and quartered).

    regards,
    Robert

    On Wed, 31 Dec 2003 12:08:25 +0100
    Georg Hellwig <georg.hellwig@gmx.de> wrote:

    > I changed form Suse to Woody. Apart from some smaller Problems I got
    > the system installed. However I have difficulties in using CDBakeoven
    > to burn and copy audio cd's
    >
    > First of all:
    > The cd RW is regonised ...I did every thing according the HOWTO and
    > installed the modules
    > cdrecord -scanbus shows:
    > ---------------------------------------------------------------------
    > -------- Cdrecord 1.10 (i686-pc-linux-gnu) Copyright (C) 1995-2001
    > Jörg Schilling
    > Linux sg driver version: 3.1.22
    > Using libscg version 'schily-0.5'
    > scsibus0: 0,0,0 0) 'ATAPI ' 'CD-RW 52XMax ' '180D'
    > Removable CD-ROM
    > ---------------------------------------------------------------------
    > ------ Every user is in the group cdrom, I installed cdparanoia and
    > cdda2wav. On comandline cdparanoia -vsQ resulted in....:
    > ########################################################
    > g@g:~$ cdparanoia -vsQ
    > cdparanoia III release 9.8 (March 23, 2001)
    > (C) 2001 Monty <monty@xiph.org> and Xiphophorus
    >
    > Report bugs to paranoia@xiph.org
    > http://www.xiph.org/paranoia/
    >
    > Checking /dev/cdrom for cdrom...
    > Testing /dev/cdrom for cooked ioctl() interface
    > /dev/scd0 is not a cooked ioctl CDROM.
    > Testing /dev/cdrom for SCSI interface
    > No generic SCSI device found to match CDROM device
    > /dev/scd0
    >
    > Checking /dev/cdroms/cdrom0 for cdrom...
    > Could not stat /dev/cdroms/cdrom0: No such file or directory
    >
    > Checking /dev/cdroms/cdroma for cdrom...
    > Could not stat /dev/cdroms/cdroma: No such file or directory
    >
    > Checking /dev/cdroms/cdrom1 for cdrom...
    > Could not stat /dev/cdroms/cdrom1: No such file or directory
    >
    > Checking /dev/cdroms/cdromb for cdrom...
    > Could not stat /dev/cdroms/cdromb: No such file or directory
    >
    > Checking /dev/cdroms/cdrom2 for cdrom...
    > Could not stat /dev/cdroms/cdrom2: No such file or directory
    > Checking /dev/sbpcdc for cdrom...
    > Could not stat /dev/sbpcdc: No such file or directory
    >
    > Checking /dev/sbpcd3 for cdrom...
    > Testing /dev/sbpcd3 for cooked ioctl() interface
    > Unable to open /dev/sbpcd3: No such device or address
    > Testing /dev/sbpcd3 for SCSI interface
    > /dev/sbpcd3 is not a SCSI device
    >
    > Checking /dev/sbpcdd for cdrom...
    > Could not stat /dev/sbpcdd: No such file or directory
    >
    > Checking /dev/sonycd for cdrom...
    > Testing /dev/sonycd for cooked ioctl() interface
    > Unable to open /dev/sonycd: No such device or address
    > Testing /dev/sonycd for SCSI interface
    > /dev/sonycd is not a SCSI device
    >
    > Checking /dev/mcd for cdrom...
    > Testing /dev/mcd for cooked ioctl() interface
    > Unable to open /dev/mcd: No such device or address
    > Testing /dev/mcd for SCSI interface
    > /dev/mcd is not a SCSI device
    >
    > Checking /dev/sjcd for cdrom...
    > Testing /dev/sjcd for cooked ioctl() interface
    > Unable to open /dev/sjcd: No such device or address
    > Testing /dev/sjcd for SCSI interface
    > /dev/sjcd is not a SCSI device
    >
    > Checking /dev/cm206cd for cdrom...
    > Could not stat /dev/cm206cd: No such file or directory
    >
    > Checking /dev/gscd for cdrom...
    > Could not stat /dev/gscd: No such file or directory
    >
    > Checking /dev/optcd for cdrom...
    > Testing /dev/optcd for cooked ioctl() interface
    > Unable to open /dev/optcd: No such device or address
    > Testing /dev/optcd for SCSI interface
    > /dev/optcd is not a SCSI device
    >
    >
    >
    > No cdrom drives accessible to g found.
    > ############################################################
    > It seem it is a problem of the rights....
    > any ideas ? help will be wellcome,
    >
    > regards, Georg
    >
    >
    > --
    > To UNSUBSCRIBE, email to debian-user-request@lists.debian.org
    > with a subject of "unsubscribe". Trouble? Contact
    > listmaster@lists.debian.org
    >

    -- 
    To UNSUBSCRIBE, email to debian-user-request@lists.debian.org 
    with a subject of "unsubscribe". Trouble? Contact listmaster@lists.debian.org
    

  • Next message: Robert Storey: "Re: "best practices" on debian"

    Relevant Pages

    • Re: amd64 cdrom access locks system
      ... >> interrupts and other kernel state problems regardless of what ... >> interface it should get spanked somehow but should it be able to ... I will always get the lost interrupts from the command "cdrecord -atip". ... tried other drives without success so I don't believe that is the problem. ...
      (Linux-Kernel)
    • Re: cdrecord problem
      ... wodim: Invalid argument. ... The config.gz accompanying the linux-image-2.6.18-5-k7 confirms that the kernel was not compiled with SCSI emulation as this is no longer necessary for 2.6 kernels. ... Joerg Schily also responded with an emphatic message that linux uses an old, broken version of his cdrecord program and recommending I download the latest version of the original free program. ... With the original cdrecord the cdrecord -scanbus finds both drives immediately but when I try to burn a cd neither works. ...
      (Debian-User)
    • Re: ide-scsi is deprecated for cd burning!
      ... >The woody version of cdrecord is too old to play nicely with 2.6 ... >Linux kernel developers for years - the bitching about the driver in ... of trouble burning CD's with the two drives I have in 2.6.5 and SCSI ... through the headphone jack and audio electronics in the drive. ...
      (Debian-User)
    • Re: K3b and root
      ... I'm not even using SuSE. ... However, when I was running SuSE, I ran the latest kernel for 9.1 from the ... you should look at cdrecord. ... I know that I've run into problems in 9.0 where I had to cause my IDE drives ...
      (alt.os.linux.suse)
    • Re: memory not released after using cdrecord/cdrdao (was: audio cd writing causes massive swap and c
      ... The kernel is most definitely not releasing the memory ... I further would have to say that the kernel isn't being ... >after cdrdao or cdrecord have used it, ... the Linux Kernel maintainers have not been very helpful with Linux ...
      (Linux-Kernel)