OpenSUSE :: Cdrecord Has No Permission To Open The Device?
Jan 7, 2010
Still getting the "cdrecord has no permission to open the device" error when trying to burn an iso image to a DVD-RW.
I did yet another clean install of openSUSE 11.2 64 on my desktop computer, did updates, added Nvidia and Packman repos (it's not a repo problem as I tried it several times on a totally clean install), added codecs and stuff as advised by caf.
I updated the DVD drive firmware earlier today.
My user is a member of ALL groups.
Drive is an LG GH22NSS50 (sata)
It all works (with the same DVD-RW) under winxp on the same machine.
Is it HAL or something else that blocks permission to devices?
I'm really getting sick to death of this problem, and would be happy just to get rid of anything blocking permissions to the DVD drive.
I was trying to burn an .iso with K3b a little while ago, and had some problems. First of all, even though I chose 8x to burn my (16x) DVD, it switched to 11x or 12x around halfway through the burning process. There were also some ticking noises that I'm pretty sure were coming from the DVD writer, not terribly loud, but noticeable. This had never happened before. Finally, it got stuck at about 98% (but not frozen, as the time elapsed kept going), and did not finish burning--got an error message (and a bad disc): "cdrecord has no permission to open the device"
I inspected the disc and there was one dark spot (on the dye) about halfway through the disc, very thin and couple of millimeters long. (This was present only after burning). I'm using Ubuntu 10.04, K3b version 1.91.0, Lite-On DVDRW SHW-160P6S
I tried to burn with k3b but after a while the fateful message "cdrecord has no permission to write to the device. " Then I launched k3bsetup and I selected the burning group. Did not exist. I created it and now i'm included in it. Then I checked all the boxes for the write permissions of the programs used by k3b and the writer. Now it works. But after reboot, the box of the burner device is not checked. So I have to select it each time. Boring. DO you know how to save the setting permanently
this error spams about 100 times, then the scanner does indeed work. So I'm not completely broken, but the error messages are of concern, and it slows down the process of scanning for the time it takes to do the messages.
Error in console:
libusb couldn't open USB device /dev/bus/usb/001/001: Permission denied. libusb requires write access to USB device nodes.
I have installed it (11.3) with KDE desktop.I have a problem with openening a device (harddisc) directly from sysinfo:/It is a ext4 partition, but also with my others (ntfs), this error occurs...
I'm having trouble mounting hard drives and partitions - and am rather nervous about using Yast partitioner to do this. Is there something that would tell me about mount points in Yast partitioner? So far I haven't been able to find that information anywhere. I don't want to lose information on existing drives and partitions but do want to be able to access them.Some of them appear under disk information in "My Computer" but if I try to mount them I get this error message.There is no application installed that can open files of the type block device (inode/blockdevice).I was trying to edit fstab,his didn't seem straightforward either. I've been hacking this about in other Linux distros - so not entirely clueless
I rebooted my server and out of nowhere the RAID5 array won't assemble. I've tried everything I could think of to reassemble the thing. I fear that the array is ruined, but I can't imagine how. Here are various bits of information: The simplest failure (with and without partition numbers, which have not been needed in the past):
Code:
richard@nas:~$ sudo mdadm --assemble --verbose /dev/md0 /dev/sd[bcd] mdadm: looking for devices for /dev/md0 mdadm: cannot open device /dev/sdb: Device or resource busy
Currently running rc2. Downloaded 11.2 final DVD, md5sum is good, burned DVD, YaST says media check is good. (And for completeness burned a second DVD and get the same problem.)
On booting from the DVD I select "Installation" - a kernel loads and starts checking available h/w devices then crashes with the above message.
Followed by Please append a correct "root=" boot option.
Tried with root=sda1 (partition that is /) and only change is unknown-block (0,0)
My best guess is that I have EXT4 (did a clean install of RC2)? And/or I dont have a swap partition?
I have an HP OfficeJet 5610v installed on my system, and cups can print the test page. I can also get the test page to print via [URL] which appears to be printed under the anonymous user. Now if I attempt to print the test page via the printer control panel from windows, I get the following sets of error:
D [11/Feb/2010:11:21:29 -0500] [Job 6] libusb couldn't open USB device /dev/bus/usb/001/001: Permission denied. D [11/Feb/2010:11:21:29 -0500] [Job 6] libusb requires write access to USB device nodes. D [11/Feb/2010:11:21:29 -0500] [Job 6] libusb couldn't open USB device /dev/bus/usb/002/001: Permission denied. D [11/Feb/2010:11:21:29 -0500] [Job 6] libusb requires write access to USB device nodes. D [11/Feb/2010:11:21:29 -0500] [Job 6] libusb couldn't open USB device /dev/bus/usb/003/001: Permission denied. D [11/Feb/2010:11:21:29 -0500] [Job 6] libusb requires write access to USB device nodes.
CUPS is showing that the "user" is my XP login name so I added that user to Linux and even added that account to the "lp" group and still get the above errors.
I recently compile Kernel 2.6.34 (to fix the AMD PowerNow issue with 1055T processor, and it worked!) However, the device /dev/shm starts up at boot as Read-Only.
Google Chrome requires this device to be user-writable, or it won't start up. Presumably, the stock kernels (and all that are updated) have it set to User-Write. I have not noticed any other ill effects with the permission being read-only. If I do: sudo chmod a+w /dev/shm Everything will work from there, but each time I reboot, I have to do that. How do I make that permission-change permanent?
I just setup a FireWire audio interface. Everything works fine, except for I need rw-rw-rw- permissions on /dev/fw0. I can always sudo chmod 666 /dev/fw0 just before setting the thing up, but then it will be gone on the next rebooting.The solution to modify /etc/udev/rules.d/020-permissions.rules (which is for Ubuntu Breezy) doesn't go well for Ubuntu 10.10 Maverick because there is no /etc/udev/rules.d directory.
For example /dev/loop*, /dev/raw/*, etc., they are automatically reset to root/root after rebooted.Change the owner/permission of device files maybe not a good idea, though. I just want to know if it is possible and how?
This is the command line I used to run cdrecord. Afterwards, I ran 'cdrecord -media-info' on the same disc and, as a result, I got the messages contained in the file I am adjoining. There, two consecutive warnings can be seen, which I quote:
Quote:
The disk, after recording, however, is both readable by GNU/linux and another O.S. What is the meaning of those warnings and what are its possible implications? I would like to know.
On one of my machines the DVD/DVDRW/CDROM drive appears as /dev/hdc and is not identified as an optical drive by HAL. It is owned by root: disk and thus no users get permission to read/write in the device (not even those in the cdrom group). This stops playing DVDs, ripping CDs, no notifications appear when a disk is inserted, etc. etc. When I set the permissions for all to read/write from the device then users can access but still no notifications are shown.
On all my other machines the optical drive is identified as /dev/sr0 and is owned by root:cdrom . All have Slack 13.1 . Previously with Slack 12.2 this machine still had the drive in /dev/hdc but the permissions were right (I think because I added it to /etc/fstab with options for users to access it). I believe the problem is down to HAL not setting this drive to the correct group, but how do I fix it? I hate HAL, it has a mind of its own, just like in the scifi movie
I realize the information found here is potentially biased, but it made me curious where Fedora stands. Now that even Debian has agreed to distribute the original fork of Cdrtools, is Fedora considering that option? Several other distros are distributing the original fork now, and it's where active development is ongoing.
I am using Oracle Enterprise Linux version 4 update 7. I would like to create and burn iso images via the terminal. Assume I have a folder called movies in directory /root/Desktop.I would like to create a movie.iso image ans burn it using mkisofs and cdrecord.
It has worked in the last week or so. Not sure when I ran it last. Now only root can run Open Office. The menu and a quick start Icon both give no response but su can call from the command line. I,user, can't. Seems there was a big OO update in the last several days, this might be the cause. I spoke too soon. Now su will not get it either. I tried su -l and su with no success. Also an Icon for OO quick start has gone away.
I'm getting error from KVM when i try to create new machine. I have install group Virtualization. From gui virtual-manager (after being asked for root passwd) tried to create new machine. When pressed on 'Finish' got this 'Permission denied' error: Code: Unable to complete install '<class 'libvirt.libvirtError'> internal error Process exited while reading console log output: char device redirected to /dev/pts/3 qemu: could not open disk image /sonik_data/software_archive/CentOS-5.5-x86_64-netinstall.iso: Permission denied
Traceback (most recent call last): File "/usr/share/virt-manager/virtManager/create.py", line 1567, in do_install dom = guest.start_install(False, meter = meter) File "/usr/lib/python2.7/site-packages/virtinst/Guest.py", line 1023, in start_install return self._do_install(consolecb, meter, removeOld, wait) File "/usr/lib/python2.7/site-packages/virtinst/Guest.py", line 1088, in _do_install "install") File "/usr/lib/python2.7/site-packages/virtinst/Guest.py", line 1059, in _create_guest dom = self.conn.createLinux(start_xml, 0) File "/usr/lib64/python2.7/site-packages/libvirt.py", line 1277, in createLinux if ret is None:raise libvirtError('virDomainCreateLinux() failed', conn=self) libvirtError: internal error Process exited while reading console log output: char device redirected to /dev/pts/3 qemu: could not open disk image /sonik_data/software_archive/CentOS-5.5-x86_64-netinstall.iso: Permission denied
It's running as a root, what permissions we are talking about here? I'm running F14, kernel 2.6.35.10-72.fc14.x86_64, libvirtd 0.8.3
I installed wvdial on my Satellite Toshiba laptop. All works well but I have to use the <wvdial> command as root. If I try to use it as a user i get an error message Cannot open /dev/ttyACM0: Permission denied So Im just wondering; is it ok to use wvdial as root?
