SlackwareThis Forum is for the discussion of Slackware Linux.
Notices
Welcome to LinuxQuestions.org, a friendly and active Linux Community.
You are currently viewing LQ as a guest. By joining our community you will have the ability to post topics, receive our newsletter, use the advanced search, subscribe to threads and access many other special features. Registration is quick, simple and absolutely free. Join our community today!
Note that registered members see fewer ads, and ContentLink is completely disabled once you log in.
With Slackware 10.2 I have had good luck with cdrecord, and now I would like to burn some DVDs, but evidently I need to modify cdrecord with "proDVD" or somehow acquire "dvdrecord" capabilities. Can anyone point me in the right direction? As for k3b and xcdroast, I have tried to use them but have despaired at conjuring the magic formulae necessary for navigating their GUIs, but if anyone can recommend any HOWTOs for them as well I would certainly appreciate that too.
ProDVD is one way to burn dvd's Dvd+rw tools is the other. The later is included with slackware under ap/ and does not require a key. The previous maintainer of cdrtools writes proDVD and he is at odds with the rest of the linux community. There appears to be a community effort to shift away from his software. Google for dvd+rw tools to see how to use after you install. I have used dvdrw tools to burn dual layer dvd's succesfully.
Thank you for your replies. It seems that I already had "dvd+rw-tools" on my system but didn't realize it. I have tried to use "growisofs" to burn an iso image (a Fedora installation DVD) a few times now but have not succeeded. From the command:
"# growisofs -Z /dev/sr0 FC-5-x86...iso"
I get the followinf error report:
"[WRITE@LBA=10h failed with SK=5h/ASC=21h/ACQ=02h]: Input/output error"
Of course I don't have the faintest idea of what that means. Do you have any ideas about where I could research the failure codes for this program so that I might decypher this, or, preferably, could you perhaps tell me what this code means and how I could rectify the problems which caused it?
Distros using the 2.6 kernel usually do not have scsi emulation set up. "sr0" is a scsi drive and will work on the 2.4 kernel series with scsi emulation set up. This is actually one issue with cdrtools. The cdrtools maintainer is hardcore unix and feels that drives should have "proper names". Linus Torvald feels that scsi emulation is an ugly hack and the kernel developers have moved toward /dev/hd* as Chinaman said.
/dev/sr0 = /dev/hdc
/dev/sr1 = /dev/hdd
Thanks again for the replies, but nothing seems to work. I keep getting this same error message on the command line, "[WRITE@LBA=10h failed with SK=5h/ASC=21h/ACQ=02h]: Input/output error", and "/var/log/messages" shows "...kernel: sr0: CDROM not ready yet." Yet I am running (or trying to run) growisofs as "root" from a root log-in to KDE; I have a symbolic link of "/dev/cdrom" connecting to "/dev/sr0", and have tried "growisofs" with the listing of each directory to no avail. Running as root, or trying to, should obviate any questions about "sudo" problems I would think, and I don't seem to have any problems accessing that DVD drive in other contexts. I'm running Slackware 10.2 with kernel 2.4.31 on a dual-core AMD processor and trying to burn a DVD with a NEC ND-3550A. As for the Internet in general, I have so far been unable to find any site with a listing of growisofs's error codes, so if anyone knows where that sort of information might be buried we could all benefit by such a revelation.
That command you're running, try this.
Issue "dmesg | grep -i atapi" to find out the DEVICE NAME or your drive.
Then issue "growisofs -dvd-compat -Z /dev/hd*=image.iso"
as root, from the directory with the image. So change the
hd* to your device.
*Seems like I've read this somewhere before ...
You could issue and read "man growisofs" too.
Last edited by Bruce Hill; 04-08-2006 at 08:30 PM.
I have NEC 2500A and there aren't any problems. I don't know why your cdrom became scsi (it didn't happen me) type, but kernel recompile into 2.6 should solve this problem.
Lemmie try this again:
Thank you, everyone, for your time and your replies. I finally got growisofs to burn a DVD with Slackware 10.2 by identifying my drive as "/dev/hdc" (which it is) instead of "/dev/sr0" (which it also is). I boot Slackware 10.2 (kernel 2.4.31) with SCSI emulation for the NEC ND3550-A for the sake of "cdrecord". Evidently "growisofs" prefers that I identify it as "hdc". I can't remember if I passed the parameter "hdc=ide-scsi" to the kernel for that particular boot or not, but I think that I did. Anyway, that was the source of the problem - evidently.
Hey, Woody. You don't need SCSI emulation (faking it) for cdrecord, either. The maintainer of it, Joerg Schilling, would not fix it to use device names (/dev/hdc) rather than fake names (dev/dev=0,1,0 or /dev/scd0) in earlier days of the 2.6.x.y kernel when asked; so Linus Torvalds and Jens Axbode "patched it" and now you can do this. Because you are using an ATAPI device, not a SCSI device.
I've been doing it for about 2 years, daily, so here are a few of the commands I use with device names:
Code:
To blank a CD-RW
cdrecord -v dev=/dev/hda blank=fast
To blank a DVD+RW
su -c "growisofs -Z /dev/dvd=/dev/zero"
dvd+rw-format -force -lead-out /dev/dvd
To burn an image of a CD to the hd
dd if=/dev/hda of=namethecd.iso
To make a CD from an ISO image
cdrecord -v -eject driveropts=burnfree dev=/dev/hda /path/to/file.iso
To burn an ISO image to DVD
growisofs -dvd-compat -Z /dev/hd*=image.iso
Another thing, he turns burnfree off in cdrecord by default, which is not good. But you can add this and fix it:
Code:
To enable BurnProof when using cdrecord:
You can enable it with "driveropts=burnfree".
Another useful option is fs=<number>m, which sets the
buffer size to <number> megabytes.
You might have just got here (using Linux), I don't know; but we've been putting up with the prima donna Joerg Schilling for years.
And you can use cdrecord as a normal user, and not root if you so choose. But it's better to use root, even as:
Code:
su -c "cdrecord -v -eject driveropts=burnfree dev=/dev/hda /path/to/file.iso"
to lock the memory, or something like that. I forget -- I'm just a redneck, you know.
So now you don't have to append "hdc=ide-scsi" in LiLO, or when you boot, either -- to properly use cdrecord. Be free!
Last edited by Bruce Hill; 04-11-2006 at 09:38 PM.
LinuxQuestions.org is looking for people interested in writing
Editorials, Articles, Reviews, and more. If you'd like to contribute
content, let us know.