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.
If you have any problems with the registration process or your account login, please contact us. If you need to reset your password, click here.
Having a problem logging in? Please visit this page to clear all LQ-related cookies.
Get a virtual cloud desktop with the Linux distro that you want in less than five minutes with Shells! With over 10 pre-installed distros to choose from, the worry-free installation life is here! Whether you are a digital nomad or just looking for flexibility, Shells can put your Linux machine on the device that you want to use.
Exclusive for LQ members, get up to 45% off per month. Click here for more info.
I started a thread CD/DVD/BD/M-Disc drives not writing, but it turned out to be a specifically Slackware 14 problem (or one of the kernel it uses.)
I built a new PC a few weeks ago and two LG CD/DVD/BD-DL/M-Disc drives. I have been using Slackware since 1997 (and continuously since about 2005) and have known how to set up the basics, like adding a user in the proper groups, for years. The drive I tried to make a DVD with in k3b just starts to write something before the data, says it cannot write for some reason, ruins the disc, and stops (I may have written the exact error message in that other thread.) The commands 'cdrecord -scanbus,' 'cdrecord dev=help' show no information about my new drives. However, when I used a Live DVD of another distribution, it detected the drives and was able to complete writing a DVD with the one that Slackware could not.
I never thought I would live to see a day like this, when I could not do something in Slackware that I could on a distribution mainly for new users.
Actually, I just tried an idea someone gave me on the other thread, and it made the drives visible in cdrecord... I still have to see if they will write properly, but I will leave this here anyway, because Slackware people should be aware of it.
I was answering edorig and do not really see what jefro is saying. Since this is a Slackware problem, I made a thread in its forum: CD/DVD/BD/M-Disc drives not writing.
Maybe business_kid's idea will work. I will try that.
I have suffered from the exact same problem trying to burn dvds using k3b in various releases of slackware (although not all, or on all machines, for some reason). There are a few possibly relevant points in CHANGES_AND_HINTS.TXT:
Quote:
If your cd/dvd drive is not visible inside a gtk-based desktop environment
(e.g. Xfce), you may need to add "comment=x-gvfs-show" to the /etc/fstab
line for the device. For more information, see this document: http://git.gnome.org/browse/gvfs/tre...t-is-shown.txt
and
Quote:
If you have permission errors when attempting to burn a cdrom or dvd image,
such as the following:
/usr/bin/cdrecord: Operation not permitted. Cannot send SCSI cmd via ioctl
then cdrecord almost certainly needs root privileges to work correctly.
One potential solution is to make the cdrecord and cdrdao binaries suid root,
but this has possible security implications. The safest way to do that is
to make those binaries suid root, owned by a specific group, and executable
by only root and members of that group. For most people, the example below
will be sufficient (but adjust as desired depending on your specific needs):
chown root:cdrom /usr/bin/cdrecord /usr/bin/cdrdao
chmod 4750 /usr/bin/cdrecord /usr/bin/cdrdao
If you don't want all members of the 'cdrom' group to be able to execute the
two suid binaries, then create a special group (such as 'burning' which is
recommended by k3b), use it instead of 'cdrom' in the line above, and add
to it only the users you wish to have access to cdrecord and cdrdao.
You may have seen these already.
I found it is easiest to burn dvds using commands similar to those quoted in the isolinux/README.TXT from the command line, e.g.
Before you run cdrecord you must first "modprobe sg" as the SCSI generic module is used by cdrecord's functions but for some reason is not loading automatically anymore.
I recently got myself a blu-ray burner (~2 weeks ago) and swapped it out for my dvd burner. It's an LG WH14NS40 and has worked fantastically on my slackware 14. Once in a great while I have a problem with burning something to a dvd, but I've contributed that to the dvd's being really old (>6 years with max write speed 4x) and used an awful lot. They will do the 'can't write thing' on me but usually after I've formatted or erased them.
I see in the output of cdrecord -dummy that you have the warnings:
Quote:
cdrecord: Operation not permitted. Warning: Cannot raise RLIMIT_MEMLOCK limits.
cdrecord: Cannot allocate memory. WARNING: Cannot do mlockall(2).
cdrecord: WARNING: This causes a high risk for buffer underruns.
cdrecord: Operation not permitted. WARNING: Cannot set RR-scheduler.
cdrecord: Permission denied. WARNING: Cannot set priority using setpriority().
cdrecord: WARNING: This causes a high risk for buffer underruns.
This indicates that you don't have the permissions to raise the priority of the cdrecord process
nor prevent it from being swapped (with the mlockall system call). Since Linux is multitasking,
in these conditions the cdrecord may get interrupted while writing to the optical disk. If the interruption is long
enough, that can ruin the CD. So if your attempts to burn CDs fail, you should try to run cdrecord as root.
In a previous thread, I mentioned that if that worked, you could make cdrecord setuid root provided there is no security risk.
Please post your thread once and in only one forum. Posting a single thread in the most relevant forum will make it easier for members to help you and will keep the discussion in one place. This thread is being closed because it is a duplicate.
I guess I marked this as solved because I got it working, but I forgot how now. I know I had quit trying to use k3b and used cdrecord or growisofs (and maybe making the device links mentioned above, though cdrecord seems to be detecting my drives now) and that worked, but lately I am trying k3b again, and even if I set it at 1x, it says that is not supported and increases it to 8x. K3b has made me four coasters today, and I do not want to try for a fifth... but if I try 2x or 4x will that work, or does this mean 8x is the slowest. It is also strange, because the discs from the package I am using all worked up to about 12x, but not 16x (as they are labelled)--I was writing them fine at 12x or maybe 8x in Slackware 13.37. What k3b says now is that there is an i/o error of code 254.
What does that even mean? It seems 'modprobe sg' (which I have had in rc.local since wildwizard mentioned that) helps with cdrecord, but not k3b, which was part of my original question.
But, the latest version is a pain if you don't have kde installed. There's a thread a year ago(?) where I had that problem, so you could add 'business_kid' as a search term. K3b also used automatically convert mp3 files to .wav when adding files to audio cds and I got coasters because of that.
Your original problem was drive access. That's sorted. Making duds is another one. Give us the full story on that one if you are trying for a fix on that
Your original problem was drive access. That's sorted. Making duds is another one. Give us the full story on that one if you are trying for a fix on that
I quote from my original post, 'I tried to write a plain OS DVD in K3B, and it says I do not have 'permission,' after it starts to write anyway and ruins the disc (though my user is in the cdrom group.)'
Apparently 'modprobe sg' and following the instructions in CHANGES_AND_HINTS.TXT, as well as perhaps some other stuff (not officially documented), usually solves the problem every time I upgrade or reinstall (which I did several times recently, maybe in August, but now again for 14.1, and maybe had forgotten what to do)... sometimes there may be other problems, but I think I have to try what business_kid said, again. Anyway, I will mark it as solved again, because that is probably it, and I did get it working on 14.0 a couple times.
LinuxQuestions.org is looking for people interested in writing
Editorials, Articles, Reviews, and more. If you'd like to contribute
content, let us know.