Linux - HardwareThis forum is for Hardware issues.
Having trouble installing a piece of hardware? Want to know if that peripheral is compatible with Linux?
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.
Introduction to Linux - A Hands on Guide
This guide was created as an overview of the Linux Operating System, geared toward new users as an exploration tour and getting started guide, with exercises at the end of each chapter.
For more advanced trainees it can be a desktop reference, and a collection of the base knowledge needed to proceed with system and network administration. This book contains many real life examples derived from the author's experience as a Linux system and network administrator, trainer and consultant. They hope these examples will help you to get a better understanding of the Linux system and that you feel encouraged to try out things on your own.
Click Here to receive this Complete Guide absolutely free.
d--------- 2 me root 172 2008-04-14 23:25 /media/<DVD LABEL>
Same thing for the DVD writer.
I tried to look through the /etc/udev/rules.d/, but was not sure which rule mounts it to /media/<DISK LABEL>, or sets the permission. I tried to add my own rule to /etc/udev/rules.d/10-local.rules with the following entries:
If the drives are showing up in /dev then I don't see what creating a udev rule is going to do besides giving us consistent /dev names for the device.
I'm not certain what daemons/groups KDE uses to handle HAL events but I would start by looking there. A quick google for KDE, HAL and Daemon returned this page - http://wiki.kde.org/tiki-index.php?p...US+for+KDE+3.x Which should help despite being a few years old. Of course, you do not want to blindly follow the instructions on this page but they should give you a good idea of how HAL and Dbus should work on KDE.
You could try placing a line in fstab to supercede how and where these devices get mounted. Personally I would rather get dbus and hal working like their supposed to. good luck
Thanks. Yeah, upon more searching I think hal is handling the removable media, but still not sure how to get it fixed. I tried to put the two devices in fstab, but after doing that KDE mounting dialog hangs, kded uses 100% CPU (on one core of my Pentium D), although the mount actually succeeded behind the scene. After clicking Cancel of the mount dialog, kded still runs at 100% CPU.
Killing of kded showed the following trace:
(no debugging symbols found)
(no debugging symbols found)
#5 0xb64d91af in ?? () from /usr/lib/libdbus-1.so.3
#6 0x00000000 in ?? ()
Trying fstab way under XFCE works though.
And I just tried the same thing (auto-mounting without fstab) under my Ubuntu 8.04 and got the same error (permission is set to 000). So it is not a KDE and Slackware specific problem.
Last edited by pumpump; 05-04-2008 at 09:27 AM.
Reason: Add more information
Thanks. Slackware does not use ivman (at least there is no such package).
I will try the ubuntu forum solution tonight and update.
Update - tried the ubuntu forum way. Added a rule to /etc/hal/fdi/policy. Does not work.
<match key="volume.fstype" string="udf">
<merge key="volume.policy.mount_option.umask" type="string">0000</merge> <!-- or whatever you desire -->
Last edited by pumpump; 05-05-2008 at 09:29 AM.
I found something. The problem is not due to hardware or software, it is related to the DVD. Somehow when I put in a DVD(+R) disk burnt using K3B (somemore with more than 4gb file), it has this problem. If I put in a CD-ROM, a normal DVD, or a DVD+R burnt under Windows, it can be mounted with right permissions (when device is not in fstab, didn't try the other way).
The DVD was burnt using k3b with the following settings:
Does anyone know what setting caused this problem? Thanks.
If the DVDs I burnt (using k3b and cdrtools 2.1.1a38) are mounted using iso9660 type, the permissions are ok. If mounted using udf, the permission is "d---------".
I am not sure whose problem is this... cdrtools? mount? or something else?
But before that is solved, anyone knows how to instruct hal to mount the DVDs using iso9660 instead of udf? As I said above, if I put the dvd drives into fstab with type iso9660, kded (kde mediamanager) will hang at mounting time, so cannot do that.
Last edited by pumpump; 05-06-2008 at 08:48 PM.
Reason: add tags
Hello I have found that K3B uses growisofs to create and burn the DVD and there is the problem. Specifically, growisofs calls mkisofs without the -r option, hence the UDF iso is created without permissions.
To solve it I have done it manually:
1) Create a UDF iso image with the -r to allow reading and the -V option for the DVD title: