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 have k3b 1.04 installed and previously, it was not burning to dvd at all until I changed the file system from Linux/Unix + Windows to very large files (UDF). Now, I'm having a problem with it hanging when it tries to verify the written data. I have searched the forum and googled this issue and found indications that it may be a kernel problem. I'm running Slackware 12.1 with kernel 2.6.24.5-smp. Now my question is this. Do I need to compile a new current kernel for k3b to work right? If I'm not mistaken, I have read that in Slackware you should stick to the recommended kernels provided in the Slackware discs.
you can upgrade to 1.05 in -current. I have been using it for some time now and it appears to work fine. I know it fixes the verify image problem. I cannot comment on your other issues.
You can compile a newer kernel, but I am unsure if it will fix the said issues you are having. I use newer kernels because of the wireless performance I notice. Just make sure you rebuild packages that are kernel specific (modules,ati/nividia drivers,etc..). This link should help http://alien.slackbook.org/dokuwiki/...kernelbuilding
I have had no such issues with K3B. I cannot remember ever changing the file system --- the default Linux/Unix + Windows works for me.
Recompiling K3B is needed after installing a lot of multimedia software that is not packaged with the stock Slackware, but I have not read anything about needing to recompile the stock Slackware kernels to run K3B.
A while ago I updated to version 1.05. I recompiled and updated 1.05 because I had installed many multimedia packages and for K3B to recognize those packages I had to recompile. But version 1.04 was working fine for me.
One troubleshooting idea is disable the verify option when burning. I rarely use that option.
Another idea is to again run K3B setup. Never hurts.
Thanks for the replies. All of my multimedia software outside of the stock Slackware packages come from slackbuilds.org. I try to not deviate outside of the Slackware tradition of doing things. That's why I'm not too keen on compiling a current kernel. I have reinstalled the k3b package over again. Hope this works. I will also disable the verify option and see how that goes. Getting frustrated making expensive DVD+R coasters.
Well the k3b package is in current, but it is compiled using the same kernel as 12.1. You shouldn't have any problems there. What kind of dvd-burner do you have? I have a usb dvd-burner which is a finicky thing! Do you get these issues from the cli? Sometimes this will help you pinpoint things.
One other side note. When you remove k3b you will still have config files in your /home dir, I would remove those so it would start fresh.
I know that k3b is popular but running mkisofs and cdrecord from the commandline or script is not such a big drama and will eliminate a lot of variables.
OK well to tell the truth I really think that using k3b is like turning on a light switch using a broomstick :-).
Did you upgrade to 12.1 from 12.0?
If you did, did you check that you deleted the old 75-optical-devices.rules from /etc/udev/rules.d (as discussed in CHANGES_AND_HINTS.TXT)?
There is a potential for conflict with the new 70-persistent-cd.rules.
Did you upgrade to 12.1 from 12.0?
If you did, did you check that you deleted the old 75-optical-devices.rules from /etc/udev/rules.d (as discussed in CHANGES_AND_HINTS.TXT)?
There is a potential for conflict with the new 70-persistent-cd.rules.
My 12.1 installation was from a fresh install. I haven't attempted to go through the upgrade route yet. Perhaps one day I'll get the courage to do so. I always read the CHANGES_AND_HINTS.TXT before any installation attempt in order to prevent any strange things from occurring. I guess it's time to learn how to bypass the middle man and come to grips with the commands it uses, like mkisofs and cdrecord for my burning attempts.
The only reason I asked about changing the kernel was due to this:
I personally just make the ISO with k3b and burn it using a script I wrote that burns using growisofs and verifies the md5sum of the DVD. No chance for failure.
LinuxQuestions.org is looking for people interested in writing
Editorials, Articles, Reviews, and more. If you'd like to contribute
content, let us know.