I've searched high and low for the answer that must be out there because I see threads on this type of subject so often, but I cannot get an answer, so here I come again. I just configured kernel 2.6.10 for my SLACK system and I cannot get either my cdrw or cd-rom to recognize/play audio CDs. They mount and read data CDs. My system obviously recognizes that the drives exist (/dev/hdb and /dev/hda respectively). They worked fine under 2.4.26, and still do actually. I try to play several audio CDs in XMMS as well as try to burn CDs in k3b, with no success. I have added to lilo.conf the line append = "/dev/hda=IDE-CD /dev/hdb=IDE-CD" which I read in a couple of places that this was necessary for the 2.6 kernel - no luck.

Here are some outputs:

tim@sbc:~$ cdrecord dev=ATAPI --scanbus
Cdrecord 2.00.3 (i686-pc-linux-gnu) Copyright (C) 1995-2002 Jörg Schilling
scsidev: 'ATAPI'
devname: 'ATAPI'
scsibus: -2 target: -2 lun: -2
Warning: Using ATA Packet interface.
Warning: The related libscg interface code is in pre alpha.
Warning: There may be fatal problems.
Using libscg version 'schily-0.7'
scsibus0:
0,0,0 0) 'TOSHIBA ' 'CD-ROM XM-6702B ' '1007' Removable CD-ROM
0,1,0 1) 'YAMAHA ' 'CRW2200E ' '1.0D' 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) *

edit: I can play audio files on my hard drive, so everything else is there....

Does it work if you burn a CD with "cdrecord -vv speed=24 dev=ATAPI:0,1,0 <iso file>". Replace the speed with whatever speed that drive runs at. Ignore thee Warnings about the ATA packet interface, it hsould be ok. I'm going to guess it will, as the scanbus most certainly is detecting the CDR drive.

I don't know about K3B specifically, but I know that some of the gui programs haven't been updated to handle the newer non-"scsi emulation" burning interface.

As far as XMMS and audio cd's go... did you check to make sure your XMMS prefs are looking at the /dev/hdx drive indications verses the possible /dev/sdx device nodes you'd probably have been using if you were previously using SCSI-emulation for burning purposes.

I haven't actually tried burning a CD since I'm more interested in getting the burner/rom to just recognize and play an audio CD. I'd guess that it will since the system knows the drive is there, as you said. I looked at the xmms preferences and saw nothing about devices other than their mount points, /mnt/cdr and /mnt/cdrom. I just assume xmms gets the necessary information from fstab, boot record, or somewhere like that. I have changed my fstab to reflect the changes in scsi emulation from 2.4 to 2.6.

lines from fstab:

/dev/cdrom /mnt/cdrom iso9660 noauto,users,ro 0 0
/dev/hdb /mnt/cdr iso9660 noauto,users,rw 0 0

Does any audio work? Can you play .wav or .mp3/ogg files?

<edit> Nevermind, I just cleaned the sleep from my eyes.

In your first post you said you can't burn cd's with k3b but later you said you haven't tried. I would suggest you try burning a cd to see if that works.

Check to see if ide-scsi module is loading, and remove it. You don't even need to build that module now with 2.6 kernel.

The ide-scsi module is not loading. I am burning a CD right now. I finally got xmms to recognize a CD. It was permissions related. I saw that /dev/hdb had root as owner and cdrom as group. I added myself to the group but still had no luck with audio cd recognition. I chmod'ed the device and that worked. Why I didn't need to change permissions to mount a data CD I don't know. I'm still quite confused with all of this, though, and am having buggy problems like never before with programs like xmms since installing the new kernel.

The mount program is suid as root on most systems so if you have the users option on your CD drive in your fstab file you can mount a data cd without having permissions to read the device.

Every time I have to reboot, I must chmod the cd drives to get them to allow xmms to read the audio cd. How do I make this permission change permanent?

I believe (please correct me if I'm wrong) that Slackware 10 uses udev to map device nodes.

This means they are generated on the fly when hardware is initialized. Somewhere on your system (probably /etc/udev/) you should have a permissions file that sets the default permissions for all the device nodes. Typically 0660 is a good setting for cdrom drives if you want all the users to have to be in the cdrom group to use it. If you want everyone to use it then 0666 is a good setting.