Hi all

I am a member of the CDROM group (accessed via kuser as root and I entered my userid as a member) and manually changed the permissions as well for the device, yet whenever I open ripperX it always gives me an error 32 and tells me to ensure I am a member of the CD group or have proper permissions.

What gives? Any help?

Have you logged out since? Adding yourself to new groups won't take effect until your next login.

What happens when you try to mount a CD manually?
Can you open and close the tray (eject, eject -t)?

If you can't do that, then there must be some error with the permissions.

You mean the permissions and the group too, right?

Hey there ioerror

Yep I've logged out and back in again. I can play the CD as a user as well as mount the CD when it only has data on it, as well as eject using "eject".
Evidently I am allowed to access it, so I just don't know what ripperX is going on about.

Presumably some problem with ripperX then (no idea what it could be, I've never heard of it before). Have you tried any other ripper programs?

Do you know what this error 32 is? Is it some internal ripperX thing? If it's referring to a system error number, on Linux error number 32 is EPIPE (broken pipe), maybe it's trying to run a sub-process and not finding it or something?

edit:
Most graphical rippers use cdparanoia to do the actual work, maybe that's what it can't find, though why that would result in a broken pipe I don't know.

Have you tried running cdparanoia from the command line?

Hi again

This is an excerpt from cdparanoia -vsQ at the command line:

Checking /dev/hdb for cdrom...
Testing /dev/hdb for cooked ioctl() interface
Device /dev/hdb is not a CDROM
Testing /dev/hdb for SCSI interface
/dev/hdb is not a SCSI device

This is just bizarre - when I boot up /dev/hdb is identified as a CDROM drive and this is what I added to the LILO line hdb=ide-scsi for emulation.

That's weird. It should show up as one or the other. Are you sure all the relevant modules are being loaded?

Info on scsi devices is in /proc/scsi (you should have a /proc/scsi/ide-scsi/0), and /proc/sys/dev/cdrom has (some) info any IDE cdrom(s). There may be a clue in there somewhere.

Output from less /proc/sys/dev/cdrom/info:

CD-ROM information, Id: cdrom.c 3.12 2000/10/18

drive name: sr0
drive speed: 52
drive # of slots: 1
Can close tray: 1
Can open tray: 1
Can lock tray: 1
Can change speed: 1
Can select disk: 0
Can read multisession: 1
Can read MCN: 1
Reports media changed: 1
Can play audio: 1
Can write CD-R: 1
Can write CD-RW: 1
Can read DVD: 0
Can write DVD-R: 0
Can write DVD-RAM: 0

Unless I've killed too many brain cells already, this would suggest that my system can actually find my cdrom. Perhaps the problem is not so much with my system and instead with cdparanoia ... although that hardly seems likely.

Are you using the 2.6.? kernel? If so, you don't need the "hdb=ide-scsi". The new kernel doesn't use it anymore. Try editing lilo, run /sbin/lilo when you're done and reboot or unload that module. That's probably what's causing your error.

Nope I am using the vanilla 2.4.* kernel that ships with Slack 10.2. I only know of ripperX and grip, but since I have not loaded the Gnome libraries, grip won't work. Are there other ripping programs - perhaps I could download those and experiment. No doubt that they are all front-ends for cdparanoia, and from a previous post, if cdparanoia can't find my cdrom, then I guess that I am up shit creek without a cd-ripper, unless I invoke the program as root.
Still, I am really curious as to what is causing this problem, so at an intellectual level it would be nice to get to the bottom of this.
Cheers for any further help

Try if you can find any info on cdparanoia website, man pages, other documents etc. I guess that if ripping works as root, then the problem must be related to permissions. Try compiling cdparanoia yourself, instead of using the default. Package maintainers sometimes make broken builds by mistake.

I guess the error is related to permissions also, but for the life of me I cannot figure out anything about how to correct it from the ripperX website and the docs don't address this.
However, I have found a fix: cdparanoia apparently uses an 'sg' interface to read scsi devices.
By changing permissions here, this seems to work.

Therefore the fix is:
and hey presto! works like a charm