** Reply to message from Audioslave - 7M3 - Live <[EMAIL PROTECTED]> on Sun, 23 Mar 2003 10:15:05 -0500
Audioslave - 7M3 - Live wrote:
When using the nautilus burn window, to try to make a CD. This is the dialog error that I got.
hint: /dev/sg0 is now supposed to be my reader. /dev/sg1 is supposed to be my burner.
confusions: What is telling these devices what to do?
cdrecord: For possible transport specifiers try 'cdrecord dev=help'.
cdrecord: For possible targets try 'cdrecord -scanbus'. Make sure you are root.
cdrecord: Permission denied. Cannot open '/dev/sg0'. Cannot open SCSI driver.
scsibus: 0 target: 1 lun: 0
scsidev: '0,1,0'
cdrecord: WARNING: This causes a high risk for buffer underruns.
cdrecord: Permission denied. WARNING: Cannot set priority using setpriority().
cdrecord: Operation not permitted. WARNING: Cannot set RR-scheduler
cdrecord: WARNING: This causes a high risk for buffer underruns.
cdrecord: Operation not permitted. WARNING: Cannot do mlockall(2).
<snip>
These look like permission errors. Try doing:
chown <your_user>.<your_user> /dev/sg0 chown <your_user>.<your_user> /dev/sg1
then try it again. Looks like Nautilus should be taught to use consolehelper when it needs to.
jb
-- Jack Bowling mailto:[EMAIL PROTECTED] Prince George, BC
If cdrecord tried to use the sg0 device, it would most likely be writing to a device driver that had no actual device attatched to it. I have a reader attached to hdc. hdd is identified as sg1 now, for the burn mode and a symlink to /dev/cdwriter that points to /dev/sg1.
When I get to my desktop, I'll check the device permissions.
It seems that the latest phoebe kernel-2.4.20-2.48 used to always try to make a symlink from my hdc and hdd drive and put links like /dev/cdrom >> /dev/hdc and /dev/cdrom2 >> /dev/hdd. It did this regardless of my attempts to edit these links to their proper setup. I left the fstab entry in my file and just added a link for the proper device /dev/scd0.
There was a link that was automatically created for /dev/cdwriter that pointed to /dev/sd0.
With the latest accessable kernel for rawhide, the situation changed a bit and all my cdrom devices were referred to as scdx devices. Also, the link that did point to /dev/cdwriter changed itself to point to /dev/sg1.
It didn't find an scsi device at /dev/sg0 because there was no hdc=ide-scsi loaded as a parameter to my kernel. There was a parameter for hdd=ide-scsi for my burner, but it tried to burn on my reader.
I had magicdev running. It is what brought up the burn window for the files to be selected for. It cached these, but did not burn these files. CDreaders aren't too sucessful at burning cds.
My theory is that since cdrecord uses it's scanbus feature to select the burner. It interacts with whatever program is setting the /etc/fstab entries.
The way that my system now recognizes /dev/hdc as /dev/scd0 and /dev/hdd as /dev/scd1 makes sense to me. The way that /dev/sg0 matches up with scd0 and that scd1 matches up with sg1 also makes sense to me.
I figure that since the burn feature uses cdroast as it's program. The settings that were used for the phoebe kernel were still in place for the burn session. If I tried it again, after logging out, then back into gnome, the settings might point to the correct reader and writer devices. Now the settings for cdrecord are associated to the correct devices. Burner set to burning device. Reader set to primary reader and writer set to secondary reading use.
The cdrom that I reverted to burn with cdroast did not seem to be of the best quality. It did seem to burn alright though. (No coaster). I will check it out on the laptop later.
Thanks for your suggestion about the device permissions being incorrect though.
Jim
-- Nothing is so firmly believed as that which we least know. -- Michel de Montaigne
-- Phoebe-list mailing list [EMAIL PROTECTED] https://listman.redhat.com/mailman/listinfo/phoebe-list
