Содержание
- CD-RW не жжот!
- Re: CD-RW не жжот!
- Re: CD-RW не жжот!
- Re: CD-RW не жжот!
- Re: CD-RW не жжот!
- Re: CD-RW не жжот!
- Re: CD-RW не жжот!
- Re: CD-RW не жжот!
- Arch Linux
- #1 2020-11-08 10:09:41
- [SOLVED] Brasero won’t write to disc because of permissions
- #2 2020-11-08 10:14:52
- Re: [SOLVED] Brasero won’t write to disc because of permissions
- #3 2020-11-08 11:32:11
- Re: [SOLVED] Brasero won’t write to disc because of permissions
- #4 2020-11-08 11:36:23
- Re: [SOLVED] Brasero won’t write to disc because of permissions
- #5 2020-11-08 15:16:44
- Re: [SOLVED] Brasero won’t write to disc because of permissions
- #6 2020-11-08 15:50:46
- Re: [SOLVED] Brasero won’t write to disc because of permissions
- #7 2020-11-08 15:54:07
- Re: [SOLVED] Brasero won’t write to disc because of permissions
- #8 2020-11-08 16:12:24
- Re: [SOLVED] Brasero won’t write to disc because of permissions
- #9 2020-11-08 16:39:56
- Re: [SOLVED] Brasero won’t write to disc because of permissions
- k3b fails to burn cd with firewire device
- Bug Description
- K3b doesn’t work #19154
- Comments
- Issue description
- Steps to reproduce
- Technical details
CD-RW не жжот!
Re: CD-RW не жжот!
>Error: Cannot gain SYS_RAWIO capability.Is cdrecord installed SUID root?
Хотя у меня всё работает без SUID.
Re: CD-RW не жжот!
>Хотя у меня всё работает без SUID.
У меня на 2.4 тоже работало без СУИД, Я думаю не в этом дело, а в этом:
/usr/bin/cdrecord: Operation not permitted. Cannot send SCSI cmd via ioctl
Feb 25 10:21:52 comp kernel: scsi: unknown opcode 0x01
Re: CD-RW не жжот!
В ядре видимо надо покапаться. Где то что то не проставил. Не помню, что, но очень давно проблему такую решал пересборкой ядрышка.
Re: CD-RW не жжот!
>У меня на 2.4 тоже работало без СУИД,
У меня на 2.6.13 (SUSE 10.0) тоже. Может патчи какие-то. Но SUID ты попробуй поставить (желательно разрешить исполнение только группе, куда входит только твой юзер).
Re: CD-RW не жжот!
а в 2.6 диски жгут через ATA или SCSI?
Re: CD-RW не жжот!
нужно ли включать в ядре SCSI emulation support (BLK_DEV_IDESCSI)?
WARNING: ide-scsi is no longer needed for cd writing applications!
The 2.6 kernel supports direct writing to ide-cd, which eliminates
the need for ide-scsi + the entire scsi stack just for writing a
cd. The new method is more efficient in every way.
Re: CD-RW не жжот!
Через cdrecord жжот, через К3B не жжот. Млять!
Источник
Arch Linux
You are not logged in.
#1 2020-11-08 10:09:41
[SOLVED] Brasero won’t write to disc because of permissions
I don’t know if this problem is a simple one, but I’m stuck.
I tried to burn an ISO to CD-R with Brasero. Before the writing begins it gives me this message «You do not have the required permissions to use this drive» and it ejects the disc.
I added the user to these groups: storage, disk, optical, but the outcome was the same.
I read the wiki (Optical disc drive page) and I tried to burn the ISO with the cdrecord CLI command as a user and it failed. But with the same command with sudo succeded.
What kind of permission I’m missing here?
Thanks for any help.
Last edited by pavlosdec (2020-11-12 17:44:34)
#2 2020-11-08 10:14:52
Re: [SOLVED] Brasero won’t write to disc because of permissions
This is the output of cdrecord used by normal user:
Last edited by pavlosdec (2020-11-08 16:13:17)
#3 2020-11-08 11:32:11
Re: [SOLVED] Brasero won’t write to disc because of permissions
Sometimes I seem a bit harsh — don’t get offended too easily! PGP: 7C848198AE93D3BB
#4 2020-11-08 11:36:23
Re: [SOLVED] Brasero won’t write to disc because of permissions
I think it clould be tha same. And it is still unsolved.
I will keep an eye on that thread, thank you.
#5 2020-11-08 15:16:44
Re: [SOLVED] Brasero won’t write to disc because of permissions
Can you verify that the group for the drive is ‘optical’ and that there exist group write permissions? Post the output of ls -l /dev/sr0
After you added your user to the ‘optical’ group, did you log out and log back in? As a sanity check, what is the output of groups ?
Nothing is too wonderful to be true, if it be consistent with the laws of nature — Michael Faraday
Sometimes it is the people no one can imagine anything of who do the things no one can imagine. — Alan Turing
—
How to Ask Questions the Smart Way
#6 2020-11-08 15:50:46
Re: [SOLVED] Brasero won’t write to disc because of permissions
I did all that but the issue is this
The problem is the latest version of cdrtools. When I downgraded to the previous version there was no issue.
So, I think I will be ignoring the package’s latest version for now.
P.S. Should I mark this as SOLVED. (kinda. )
Last edited by pavlosdec (2020-11-08 15:51:40)
#7 2020-11-08 15:54:07
Re: [SOLVED] Brasero won’t write to disc because of permissions
ewaller:
Even if one is in optical, it won’t work. cdrecord requires various other privileges — not merely access to the device file.
Just to make it clear:
Sometimes I seem a bit harsh — don’t get offended too easily! PGP: 7C848198AE93D3BB
#8 2020-11-08 16:12:24
Re: [SOLVED] Brasero won’t write to disc because of permissions
Okay, good to know. I always try for the low hanging fruit first 
Nothing is too wonderful to be true, if it be consistent with the laws of nature — Michael Faraday
Sometimes it is the people no one can imagine anything of who do the things no one can imagine. — Alan Turing
—
How to Ask Questions the Smart Way
#9 2020-11-08 16:39:56
Re: [SOLVED] Brasero won’t write to disc because of permissions
I had this problem a while back and discovered on a working machine that the permission for /usr/bin/cdrecord was
-rws—s—x 1 root root 574448 Jul 7 16:35 cdrecord
once I did a «sudo chmod u+s cdrecord» on the non-working machine it worked. I think I may have done g+s as well but that probably wasn’t necessary.
If I was clever I might be able to tell you why it worked.
Last edited by Spinnekop (2020-11-08 16:44:58)
Umuntu Ngumuntu Ngabantu
—————————————
a person is a person through other people
Источник
k3b fails to burn cd with firewire device
| Affects | Status | Importance | Assigned to | Milestone |
|---|---|---|---|---|
| k3b (Ubuntu) |
Bug Description
k3b fails to burn a CD with a firewire LG DVD drive. It consistently fails to burns CDs, however I
have burnt DVDRW with no problems and DVD RAM with no problems. The error log is attached-
Devices
——- ——- ——- —
HL-DT-ST DVDRAM GSA-5163D A103 (/dev/scd0, ) at [CD-R; CD-RW; CD-ROM; DVD-ROM; DVD-RAM; DVD-R;
DVD-RW; DVD+R; DVD+RW] [DVD-ROM; DVD-R Sequential; DVD-RAM; DVD-RW Restricted Overwrite; DVD-RW
Sequential; DVD+RW; DVD+R; DVD+R Double Layer; CD-ROM; CD-R; CD-RW] [SAO; TAO; RAW; SAO/R16;
RAW/R96P; RAW/R96R]
HP CD-Writer+ 9100 1.0c (/dev/hdd, ) at [CD-R; CD-RW; CD-ROM] [Error] [SAO; TAO; RAW; RAW/R96R]
System
——- ——- ——- —
K3b Version: 0.11.24
KDE Version: 3.4.0
QT Version: 3.3.3
Kernel: 2.6.10-6-k7
cdrecord
——- ——- ——- —
/usr/bin/cdrecord: Warning: Running on Linux-2.6.10-6-k7
/usr/bin/cdrecord: There are unsettled issues with Linux-2.5 and newer.
/usr/bin/cdrecord: If you have unexpected problems, please try Linux-2.4 or Solaris.
/usr/bin/cdrecord: Operation not permitted. WARNING: Cannot set RR-scheduler
/usr/bin/cdrecord: Permission denied. WARNING: Cannot set priority using setpriority().
/usr/bin/cdrecord: WARNING: This causes a high risk for buffer underruns.
scsidev: ‘1,0,0’
scsibus: 1 target: 0 lun: 0
Linux sg driver version: 3.5.31
/usr/bin/cdrecord: Warning: using unofficial version of libscg (ubuntu-0.8ubuntu1 ‘@(#)scsitransp.c
1.91 04/06/17 Copyright 1988,1995,2000-2004 J. Schilling’).
SCSI buffer size: 64512
/usr/bin/cdrecord: This version of cdrecord does not include DVD-R/DVD-RW support code.
/usr/bin/cdrecord: See /usr/share/ doc/cdrecord/ README. DVD.Debian for details on DVD support.
Cdrecord-Clone 2.01a38 (i686-pc-linux-gnu) Copyright (C) 1995-2004 Joerg Schilling
NOTE: this version of cdrecord is an unofficial (modified) release of cdrecord
and thus may have bugs that are not present in the original version.
Please send bug reports and support requests to .
The original author should not be bothered with problems of this version.
TOC Type: 1 = CD-ROM
Using libscg version ‘ubuntu- 0.8ubuntu1’ .
Driveropts: ‘burnfree’
atapi: 1
Device type : Removable CD-ROM
Version : 2
Response Format: 2
Capabilities :
Vendor_info : ‘HL-DT-ST’
Identifikation : ‘DVDRAM GSA-5163D’
Revision : ‘A103’
Device seems to be: Generic mmc2 DVD-R/DVD-RW.
Current: 0x0009
Profile: 0x0012
Profile: 0x0011
Profile: 0x0014
Profile: 0x0013
Profile: 0x001A
Profile: 0x001B
Profile: 0x002B
Profile: 0x0010
Profile: 0x0009 (current)
Profile: 0x000A
Profile: 0x0008
Profile: 0x0002
Using generic SCSI-3/mmc CD-R/CD-RW driver (mmc_cdr).
/usr/bin/cdrecord: Input/output error. read buffer: scsi sendcmd: retryable error
CDB: 3C 00 00 00 00 00 00 FC 00 00
status: 0x0 (GOOD STATUS)
cmd finished after 129.974s timeout 40s
/usr/bin/cdrecord: No such device or address. Cannot send SCSI cmd via ioctl
/usr/bin/cdrecord: No such device or address. Cannot send SCSI cmd via ioctl
/usr/bin/cdrecord: No such device or address. Cannot send SCSI cmd via ioctl
/usr/bin/cdrecord: No such device or address. Cannot send SCSI cmd via ioctl
/usr/bin/cdrecord: No such device or address. Cannot send SCSI cmd via ioctl
/usr/bin/cdrecord: No such device or address. Cannot send SCSI cmd via ioctl
/usr/bin/cdrecord: No such device or address. Cannot send SCSI cmd via ioctl
/usr/bin/cdrecord: No such device or address. Cannot send SCSI cmd via ioctl
/usr/bin/cdrecord: No such device or address. Cannot send SCSI cmd via ioctl
/usr/bin/cdrecord: No such device or address. Cannot send SCSI cmd via ioctl
/usr/bin/cdrecord: No such device or address. Cannot send SCSI cmd via ioctl
/usr/bin/cdrecord: No such device or address. Cannot send SCSI cmd via ioctl
/usr/bin/cdrecord: No such device or address. Cannot send SCSI cmd via ioctl
Driver flags : MMC-3 SWABAUDIO BURNFREE
Supported modes: TAO PACKET SAO SAO/R96P SAO/R96R RAW/R16 RAW/R96P RAW/R96R
Drive buf size : 1053696 = 1029 KB
FIFO size : 4194304 = 4096 KB
/usr/bin/cdrecord: No such device or address. Cannot send SCSI cmd via ioctl
/usr/bin/cdrecord: No such device or address. Cannot send SCSI cmd via ioctl
/usr/bin/cdrecord: No such device or address. Cannot send SCSI cmd via ioctl
/usr/bin/cdrecord: No such device or address. Cannot send SCSI cmd via ioctl
Message repeated > 1000 times
/usr/bin/cdrecord: No such device or address. Cannot send SCSI cmd via ioctl
/usr/bin/cdrecord: No such device or address. Cannot send SCSI cmd via ioctl
/usr/bin/cdrecord: No such device or address. Cannot send SCSI cmd via ioctl
cdrecord comand:
——- ——- ——- —
/usr/bin/ cdrecord. mmap -v gracetime=2 dev=1,0,0 speed=40 -tao driveropts=burnfree -eject -overburn
-data /home/smedi/ Desktop/ WPRO.iso
The kernel error messages-
Dec 10 12:41:02 localhost kernel: Test Unit Ready 00 00 00 00 00
Dec 10 12:41:02 localhost kernel: cdrom: This disc doesn’t have any tracks I recognize!
Dec 10 12:42:29 localhost kernel: Test Unit Ready 00 00 00 00 00
Dec 10 12:42:29 localhost kernel: Read Buffer 00 00 00 00 00 00 fc 00 00
Dec 10 12:43:09 localhost kernel: Test Unit Ready 00 00 00 00 00
Dec 10 12:43:19 localhost kernel: Test Unit Ready 00 00 00 00 00
Dec 10 12:43:19 localhost kernel: Read Buffer 00 00 00 00 00 00 fc 00 00
Dec 10 12:43:29 localhost kernel: Test Unit Ready 00 00 00 00 00
Dec 10 12:44:09 localhost last message repeated 3 times
Dec 10 12:44:39 localhost last message repeated 2 times
Dec 10 12:44:39 localhost kernel: scsi: Device offlined — not ready after error recovery: host 1
channel 0 id 0 lun 0
Dec 10 12:44:39 localhost kernel: scsi: Device offlined — not ready after error recovery: host 1
channel 0 id 0 lun 0
Dec 10 12:44:39 localhost kernel: SCSI error: host 1 id 0 lun 0 return code = 4000000
Dec 10 12:44:39 localhost kernel: ^ISense class 0, sense error 0, extended sense 0
I am unsure if this is a problem with k3b or the firewire modules. I have therefore loaded the sbp2
module with the following options as recommended at the Linux IEEE 1394 site-
1: modprobe ohci1394
2: modprobe sbp2 serialize_io=1 max_speed=0
3: modprobe sg
4: modprobe sr_mod
The device works reliably with no problems under windows.
Источник
K3b doesn’t work #19154
Issue description
Hello! I’m trying to write files to a CD and getting error:
Running K3bsetup results in /home/foobar/.nix-profile/bin/k3bsetup: line 16: kcmshell4: command not found .
For example 1 month ago k3b worked 100%.
Steps to reproduce
Technical details
- System: (NixOS: 17.03pre92039.adfcc2d )
The text was updated successfully, but these errors were encountered:
Try adding your user to cdrom group. However, k3bsetup is another problem.
@abbradar adding myself to cdrom group doesn’t help 🙁
I have the same problem, being in the «cdrom» group doesn’t help and k3bsetup results in /run/current-system/sw/bin/k3bsetup: line 16: kcmshell4: command not found
At the moment I can’t burn a cd. Brasero doesn’t list my write device and can only write images to my hard drive, and k3b has the same issue as OP. I don’t know how to do it otherwise. I’m in the cdrom group.
I also tried to chown /dev/cdrom to my user without sucess. (I changed it back to root:cdrom).
same issue with 17.03 stable
Just helped someone work around this; stracing k3b gave the cdrecord command it was running, and invoking that manually produced this:
Running the command as root did work; reading man 7 capabilities implies that CAP_SYS_ADMIN grants certain privileged block-device ioctls.
My personal suggestion would be to add a CAP_SYS_ADMIN file capability to the cdrecord binary, and make it executable only by the cdrom group.
Still doesn’t work in Nixos Small Unstable; running it as root (gksu k3b) works.
- System: (NixOS: nixos-version , Ubuntu/Fedora: lsb_release -a , . )
- Nix version: (run nix-env —version )
nix-env (Nix) 1.11.15
- Nixpkgs version: (run nix-instantiate —eval » » -A lib.nixpkgsVersion )
- Sandboxing enabled: (run grep build-use-sandbox /etc/nix/nix.conf )
I managed to burn a blu-ray with 17.09.2138.48bf1f43cd (Hummingbird) with K3b without using root. K3b showed an error at the end of the burning process (99% done) but the disc seemed perfectly readable by other computers. I think I’ve had the same issue before NixOS with K3b on other Linux distros too.
Well, this was weird: After successfully writing two discs, I got the permission error on one project which tried to write multiple files to a blu-ray. When I removed all but one file, the disc wrote ok (see my previous comment). I didn’t start debugging whether the issue was the number of files (greater than one), the total size of files (although well below maximum capacity), the file types or something else. But anyway it worked with one file with size around 25-35GB but not with three files totalling to size around 45GB (capacity
50GB). Anyway, just thought I’d share if this helps someone else.
k3b package doesn’t have K3bsetup executable anymore:
It also seems to work for me now. Could someone else try it out?
I’m in the cdrom group but it’s still not working for me
Hi, I’m suffering from the same problem (using NixOS 18.03). I discovered that k3b used to use cdrkit instead of cdrtools ( #6002 ), but it was — possibly inadvertently — changed with this commit: e690c3a . I replaced cdrtools with cdrkit in the k3b wrapper script by hand, which fixed the problem on my machine.
Maybe it suffices to replace cdrtools with cdrkit in the k3b build recipe to fix this?
By the way, I also played around with the cdrom group, but it’s apparently not needed: Users seem to gain r/w-access to optical drives simply by logging in.
Thank you for your contributions.
This has been automatically marked as stale because it has had no activity for 180 days.
If this is still important to you, we ask that you leave a comment below. Your comment can be as simple as «still important to me». This lets people see that at least one person still cares about this. Someone will have to do this at most twice a year if there is no other activity.
Here are suggestions that might help resolve this more quickly:
Источник
| View previous topic :: View next topic | |||||||||||||
| Author | Message | ||||||||||||
|---|---|---|---|---|---|---|---|---|---|---|---|---|---|
| Fog_Watch Apprentice  
Joined: 24 Jul 2006 |
|
||||||||||||
| Back to top |
|
||||||||||||
 |
|||||||||||||
| energyman76b Advocate  
Joined: 26 Mar 2003 |
|
||||||||||||
| Back to top |
|
||||||||||||
|
|||||||||||||
| Fog_Watch Apprentice
Joined: 24 Jul 2006 |
|
||||||||||||
| Back to top |
|
||||||||||||
|
|||||||||||||
| energyman76b Advocate
Joined: 26 Mar 2003 |
|
||||||||||||
| Back to top |
|
||||||||||||
|
|||||||||||||
| Fog_Watch Apprentice
Joined: 24 Jul 2006 |
|
||||||||||||
| Back to top |
|
||||||||||||
|
|||||||||||||
| energyman76b Advocate
Joined: 26 Mar 2003 |
|
||||||||||||
| Back to top |
|
||||||||||||
|
|||||||||||||
| Fog_Watch Apprentice
Joined: 24 Jul 2006 |
|
||||||||||||
| Back to top |
|
||||||||||||
|
|||||||||||||
| energyman76b Advocate
Joined: 26 Mar 2003 |
|
||||||||||||
| Back to top |
|
||||||||||||
|
|||||||||||||
| Fog_Watch Apprentice
Joined: 24 Jul 2006 |
|
||||||||||||
| Back to top |
|
||||||||||||
|
|||||||||||||
| energyman76b Advocate
Joined: 26 Mar 2003 |
|
||||||||||||
| Back to top |
|
||||||||||||
|
|||||||||||||
|
|
You cannot post new topics in this forum |
0
0
HELP!
System
-----------------------
K3b Version: 0.12.10
KDE Version: 3.5.1
QT Version: 3.3.5
Kernel: 2.6.14.2
Devices
-----------------------
SONY CD-RW CRX230ED 4YS1 (/dev/ide/host0/bus1/target1/lun0/cd, ) at /media/rw [CD-R; CD-RW; CD-ROM] [CD-ROM; CD-R; CD-RW] [SAO; TAO; RAW; SAO/R96P; SAO/R96R; RAW/R16; RAW/R96P; RAW/R96R]
K3b
-----------------------
Size of filesystem calculated: 22628
Used versions
-----------------------
cdrecord: 2.1.1a03
cdrecord
-----------------------
/usr/bin/cdrecord: Warning: Running on Linux-2.6.14.2
/usr/bin/cdrecord: There are unsettled issues with Linux-2.5 and newer.
/usr/bin/cdrecord: If you have unexpected problems, please try Linux-2.4 or Solaris.
/usr/bin/cdrecord: Operation not permitted. WARNING: Cannot set RR-scheduler
/usr/bin/cdrecord: Permission denied. WARNING: Cannot set priority using setpriority().
/usr/bin/cdrecord: WARNING: This causes a high risk for buffer underruns.
scsidev: '/dev/ide/host0/bus1/target1/lun0/cd'
devname: '/dev/ide/host0/bus1/target1/lun0/cd'
scsibus: -2 target: -2 lun: -2
Warning: Open by 'devname' is unintentional and not supported.
Linux sg driver version: 3.5.27
Error: Cannot gain SYS_RAWIO capability.Is cdrecord installed SUID root?
: Operation not permitted
/usr/bin/cdrecord: Warning: using inofficial version of libscg (debian-0.8debian2 '@(#)scsitransp.c 1.91 04/06/17 Copyright 1988,1995,2000-2004 J. Schilling').
SCSI buffer size: 64512
Cdrecord-Clone 2.01.01a03 (i686-pc-linux-gnu) Copyright (C) 1995-2005 Joerg Schilling
NOTE: this version of cdrecord is an inofficial (modified) release of cdrecord
and thus may have bugs that are not present in the original version.
Please send bug reports and support requests to <cdrtools@packages.debian.org>.
The original author should not be bothered with problems of this version.
TOC Type: 1 = CD-ROM
Using libscg version 'debian-0.8debian2'.
Driveropts: 'burnfree'
atapi: 1
Device type : Removable CD-ROM
Version : 0
Response Format: 2
Capabilities :
Vendor_info : 'SONY '
Identifikation : 'CD-RW CRX230ED '
Revision : '4YS1'
Device seems to be: Generic mmc CD-RW.
Current: 0x000A
Profile: 0x000A (current)
Profile: 0x0009
Profile: 0x0008
Profile: 0x0002
Using generic SCSI-3/mmc CD-R/CD-RW driver (mmc_cdr).
Driver flags : MMC-3 SWABAUDIO BURNFREE FORCESPEED
Supported modes: TAO PACKET SAO SAO/R96P SAO/R96R RAW/R16 RAW/R96P RAW/R96R
Drive buf size : 1419264 = 1386 KB
FIFO size : 4194304 = 4096 KB
/usr/bin/cdrecord: Operation not permitted. Cannot send SCSI cmd via ioctl
Track 01: data 44 MB
Total size: 50 MB (05:01.70) = 22628 sectors
Lout start: 51 MB (05:03/53) = 22628 sectors
cdrecord command:
-----------------------
/usr/bin/cdrecord.mmap -v gracetime=2 dev=/dev/ide/host0/bus1/target1/lun0/cd speed=52 -dao driveropts=burnfree -data -tsize=22628s -
mkisofs
-----------------------
22628
INFO: UTF-8 character encoding detected by locale settings.
Assuming UTF-8 encoded filenames on source filesystem,
use -input-charset to override.
/usr/bin/mkisofs: Connection reset by peer. cannot fwrite 32768*1
mkisofs command:
-----------------------
/usr/bin/mkisofs -gui -graft-points -volid K3b data project -volset -appid K3B THE CD KREATOR (C) 1998-2005 SEBASTIAN TRUEG AND THE K3B TEAM -publisher -preparer -sysid LINUX -volset-size 1 -volset-seqno 1 -sort /tmp/kde-maker/k3bDoY9la.tmp -rational-rock -hide-list /tmp/kde-maker/k3b2roKba.tmp -joliet -hide-joliet-list /tmp/kde-user/k3b8aWtwa.tmp -full-iso9660-filenames -iso-level 2 -path-list /tmp/kde-user/k3bZhRNqc.tmp
И снова проблемы с записью через терминал
Модератор: Модераторы разделов
-
Pantera2007
- Сообщения: 107
- ОС: Fedora
И снова проблемы с записью через терминал
Здравствуйте уважаемые форумчане!
Примерно полгода назад уже решала проблему с записю образа (iso) Запись образа (iso) через консоль — проблема была в 14 версии Fedora и тогда все решилось банальным размонтированием привода.
В Fedora 16 все было прекрасно, а вот в Fedora 17 проблемы с записью повторяются, еще хуже чем в Fedora 14. Сам образ с диска создается (использую команду: dd if=/dev/cdrom of=cd_gal.iso). Диск можно отмонтировать/примонтировать, но при попытке выяснить параметры моего привода выводится:
Предложение почитать README.ATAPI.setup мне в принципе ничего не дала, почему то там рассматривается старое ядро, да еще и другого дистирибутива (файл прикладываю — не могу загрузить):
Код: Выделить всё
Howto setup an ATAPI CD-RW/DVD+-RW recorder on Debian/Ubuntu
============================================================
This guide should be applicable to most kernel 2.6 using distributions of
GNU/Linux. For installations with kernel 2.4, continue reading below.
Kernel 2.6.*
============
If you have just one CD writer in your computer, CD-writing should work out of
the box. There should be a symbolic link /dev/cdrw which points to your actual
CD-Writer's device (e. g. /dev/hdb). If the link is not present (eg. the
system is not using udev/devfs) or if you want to use a different device as
default, you can configure the device in /etc/wodim.conf:
CDR_DEVICE=/dev/hdd
would configure the default device to be /dev/hdd, i. e. the slave
device on the secondary IDE bus.
You can always override this default setting with wodim's "dev"
option:
wodim dev=/dev/hdc ...
Only users part of the system group "cdrom" are able to write CDs.
If you wish to allow non-root users to write CDs then add your users to the
cdrom group ("adduser user cdrom") and let the user completely logout and
re-login.
Note: with certain kernel versions wodim can fail with this message:
"wodim: Operation not permitted. Cannot send SCSI cmd via ioctl"
In this case it still does need the suid bit - please send patches if you have
identified the reason of that problem.
Kernel 2.4.* (for 2.5/2.6, see above)
=====================================
Where we start:
Linux: Kernel 2.4.20-bf2.4 (Debian package kernel-image-2.4.20-bf2.4)
Distribution: Debian Woody 3.0r2, i386
Devices: one CDRW-Writer, one CDROM-drive, both ATAPI
1. Become root, try "grep hd.: /var/log/kern.log" to find out where your
ATAPI-devices are connected to (hd?-names).
2. Edit your boot configuration file, eg. /etc/lilo.conf if you use
lilo or the batch-file if you boot via loadlin.
3. Find a line where you can append additional kernel parameters, eg.
"append=" in lilo.conf or the loadlin-line in the batch file.
4. Append sth. like this: "hdb=ide-scsi hdc=ide-scsi max_scsi_luns=1"
The hdX-parameters defines devices that should be mapped to SCSI
latter. You may do it with non-writers too, since the emulation layer
is almost complete. Or omit some so the devices will use their
native drivers (eg. ide-cd).
5. Save the file, reinstall the bootloader (ie. running "/sbin/lilo")
6. Call "modconf" in a console or xterm, enter the section
"kernel/drivers/scsi", load "sg" and "ide-scsi"
7. Reboot Debian, watch while booting, you should see a line like this:
"Detected scsi CD-ROM sr0 at scsi0, channel 0, id 0, lun 0".
Your old ATAPI devices virtually don't exist any longer, you cannot refer to
/dev/hd* as CDROM drives. Use the SCSI equivalents instead, /dev/sr*.
8. Become root, setup devices:
cd /dev
MAKEDEV sg scd
ln -s scd0 cdrom # NOTE: or cdrw, first check which drive is here
ln -s scd1 cdrw # NOTE: see above, maybe cdrom
Check the new SCSI settings:
wodim -scanbus
Setup wodim's environment - edit /etc/wodim.conf:
CDR_DEVICE=cdrw
cdrw=1,0,0 4 8m
cdrom=1,2,0 0 0m
Insert the right values, the fields are described in the manpage
of wodim. Alternatively, you may use these values as
wodim-parameter or take a frontend with an own configuration
scheme, then you don't need to modify /etc/wodim.conf.
The columns must be separated by tabs.
9. It's done! Insert a CD and try "wodim -v -toc". To create your first CD-ROM, try:
mkisofs -v -r -J /directory/to/be/written | wodim -v -dummy -
(read wodim(1), "man 1 wodim", for details)
10. If you wish to allow non-root users to write CDs, you must give them
permissions to do so. Set suid-root permissions on the executable,
then add your users to the cdrom group ("adduser user cdrom") and
let the user completely logout and re-login.Аналогично и с чтением wodim dev=help и man wodim — тоже не принесло положительных результатов.
RFRemix 17, ядро 3.6.11-1.fc17.i686.PAE.
Предложите мне какие-нибудь варианты, чтобы можно было записать образ через терминал.
P.S. Графические программы предлагать не надо (дело принципа)
-
Bizdelnick
- Модератор
- Сообщения: 19826
- Статус: nulla salus bello
- ОС: Debian GNU/Linux
Re: И снова проблемы с записью через терминал
Сообщение
Bizdelnick » 11.01.2013 00:09
Что с sudo не работает — странно. А без него и не должно, пока в группу cdrom не добавитесь.
Пишите правильно:
| в консоли вку́пе (с чем-либо) в общем вообще |
в течение (часа) новичок нюанс по умолчанию |
приемлемо проблема пробовать трафик |
-
Pantera2007
- Сообщения: 107
- ОС: Fedora
Re: И снова проблемы с записью через терминал
Сообщение
Pantera2007 » 11.01.2013 19:58
Bizdelnick писал(а): ↑
11.01.2013 00:09
Что с sudo не работает — странно. А без него и не должно, пока в группу cdrom не добавитесь.
Толку от того, что добавилась в группу cdrom — ноль
Кстати в Fedora 14 (специально посмотрела) нет диска в дисководе, есть диск без разницы от суперпользователя или от себя — параметры дисковода определяются. Прекрасно помню, что в 16 Fedora, вообще проблем не было, а здесь ну прямо проблема из ничего))
-
Bizdelnick
- Модератор
- Сообщения: 19826
- Статус: nulla salus bello
- ОС: Debian GNU/Linux
Re: И снова проблемы с записью через терминал
Сообщение
Bizdelnick » 12.01.2013 15:51
Fedora, говорите… А после setenforce 0 (от root) не начинает чудесным образом работать?
Пишите правильно:
| в консоли вку́пе (с чем-либо) в общем вообще |
в течение (часа) новичок нюанс по умолчанию |
приемлемо проблема пробовать трафик |
-
Pantera2007
- Сообщения: 107
- ОС: Fedora
Re: И снова проблемы с записью через терминал
Сообщение
Pantera2007 » 12.01.2013 15:55
Bizdelnick писал(а): ↑
12.01.2013 15:51
Fedora, говорите… А после setenforce 0 (от root) не начинает чудесным образом работать?
SELinux я отключаю сразу после установки дистирибутива — слишком много проблем с ним — я пока не разобралась с ним))
Все тоже самое
wodim: No such file or directory.
Cannot open SCSI driver!
For possible targets try ‘wodim —devices’ or ‘wodim -scanbus’.
For possible transport specifiers try ‘wodim dev=help’.
For IDE/ATAPI devices configuration, see the file README.ATAPI.setup from
the wodim documentation.
-
drBatty
- Сообщения: 8735
- Статус: GPG ID: 4DFBD1D6 дом горит, козёл не видит…
- ОС: Slackware-current
- Контактная информация:
Re: И снова проблемы с записью через терминал
Сообщение
drBatty » 12.01.2013 20:25
Pantera2007
а какие права у файла wodim? может есть смысл поставить права 4711? (это вредно для безопасности, но для десктопа ИМХО это не только допустимо, но и очень желательно)
Pantera2007 писал(а): ↑
11.01.2013 19:58
Толку от того, что добавилась в группу cdrom — ноль
ИМХО может потребоваться полная перезагрузка.
-
Pantera2007
- Сообщения: 107
- ОС: Fedora
Re: И снова проблемы с записью через терминал
Сообщение
Pantera2007 » 12.01.2013 23:01
drBatty писал(а): ↑
12.01.2013 20:25
Pantera2007
а какие права у файла wodim? может есть смысл поставить права 4711? (это вредно для безопасности, но для десктопа ИМХО это не только допустимо, но и очень желательно)
Поставила — нулевой результат (после полной перезагрузки проверяла). Привод не определяется (параметры)
На всякий случай приведу вывод команды wodim -checkdrive (насколько поняла сам привод то обнаруживается, а вот параметры диска не определяются):
Код: Выделить всё
Device was not specified. Trying to find an appropriate drive...
Detected CD-R drive: /dev/sr0
Using /dev/cdrom of unknown capabilities
Device type : Removable CD-ROM
Version : 5
Response Format: 2
Capabilities :
Vendor_info : 'HL-DT-ST'
Identification : 'DVDRAM GSA-T40N '
Revision : 'JT03'
Device seems to be: Generic mmc2 DVD-R/DVD-RW.
Using generic SCSI-3/mmc CD-R/CD-RW driver (mmc_cdr).
Driver flags : MMC-3 SWABAUDIO BURNFREE
Supported modes: TAO PACKET SAO SAO/R96P SAO/R96R RAW/R16 RAW/R96P RAW/R96R
Открыла Brasero — почему то не стоит галка на модуле отвечающем за запись, ссылаясь что cdrecord является ссылкой на другое приложение
Может быть этот факт влияет на запись через терминал?
-
drBatty
- Сообщения: 8735
- Статус: GPG ID: 4DFBD1D6 дом горит, козёл не видит…
- ОС: Slackware-current
- Контактная информация:
Re: И снова проблемы с записью через терминал
Сообщение
drBatty » 12.01.2013 23:41
Pantera2007 писал(а): ↑
12.01.2013 23:01
На всякий случай приведу вывод команды wodim -checkdrive (насколько поняла сам привод то обнаруживается, а вот параметры диска не определяются):
вроде всё правильно определилось…
Pantera2007 писал(а): ↑
12.01.2013 23:01
Открыла Brasero — почему то не стоит галка на модуле отвечающем за запись, ссылаясь что cdrecord является ссылкой на другое приложение
насколько я знаю, wodim и cdrecord это _разные_ программы. Причём именно они диски и пишут. А всякие brasero — это просто окошечки, что-бы в консоли команды по 10 раз не набирать. Но один раз вам набрать похоже придётся, потому как то, что у вас там вбито — почему-то не работает.
-
drBatty
- Сообщения: 8735
- Статус: GPG ID: 4DFBD1D6 дом горит, козёл не видит…
- ОС: Slackware-current
-
Контактная информация:
Re: И снова проблемы с записью через терминал
Сообщение
drBatty » 13.01.2013 00:39
Bizdelnick писал(а): ↑
13.01.2013 00:27
Это нормально, cdrecord обыно — симлинк на wodim.
дык ТСу и пишет: cdrecord это НЕ cdrecord.
Pantera2007 писал(а): ↑
12.01.2013 23:01
cdrecord является ссылкой на другое приложение
очевидно brasero этой сборки/версии не умеет работать с wodim’ом. И кстати, ЕМНИП, wodim это форк cdrecord’а, потому команды там похожие, но не идентичные.
-
Bizdelnick
- Модератор
- Сообщения: 19826
- Статус: nulla salus bello
- ОС: Debian GNU/Linux
Re: И снова проблемы с записью через терминал
Сообщение
Bizdelnick » 13.01.2013 00:51
drBatty писал(а): ↑
13.01.2013 00:39
дык ТСу и пишет: cdrecord это НЕ cdrecord.
Дык я и объясняю ТСу, почему пишет. Будем дальше играть в КО?
Пишите правильно:
| в консоли вку́пе (с чем-либо) в общем вообще |
в течение (часа) новичок нюанс по умолчанию |
приемлемо проблема пробовать трафик |
-
yars
- Сообщения: 1144
- Статус: Slacker!
- ОС: Slackware64-current
Re: И снова проблемы с записью через терминал
Сообщение
yars » 13.01.2013 13:13
Bizdelnick писал(а): ↑
13.01.2013 00:27
Это нормально, cdrecord обыно — симлинк на wodim.
Хм, а у меня wodim не установлен и cdrecord — это:
Код: Выделить всё
yars@localhost:~$ which cdrecord
/usr/bin/cdrecord
yars@localhost:~$ ls -l `which cdrecord`
-rwxr-xr-x 1 root root 468920 авг. 20 23:13 /usr/bin/cdrecord*
yars@localhost:~$ file `which cdrecord`
/usr/bin/cdrecord: ELF 32-bit LSB executable, Intel 80386, version 1 (SYSV), dynamically linked (uses shared libs), stripped
yars@localhost:~$-
Pantera2007
- Сообщения: 107
- ОС: Fedora
Re: И снова проблемы с записью через терминал
Сообщение
Pantera2007 » 13.01.2013 14:10
Вывод команд:which cdrecord, ls -l `which cdrecord`, file `which cdrecord`:
Код: Выделить всё
galina@localhost ~]$ which cdrecord
/usr/bin/cdrecord
galina@localhost ~]$ ls -l `which cdrecord`
lrwxrwxrwx. 1 root root 26 окт. 22 18:55 /usr/bin/cdrecord -> /etc/alternatives/cdrecord
galina@localhost ~]$ file `which cdrecord`
/usr/bin/cdrecord: symbolic link to `/etc/alternatives/cdrecord'Вот что интересно: я добилась, чтобы стало записывать на диск через терминал … но без всяких параметров диска, т.е. указываю dev=/dev/sr0 — записывает и с командой wodim и с командой cdrecord — вывод один в один:
Код: Выделить всё
sudo wodim/cdrecord dev=/dev/sr0 folder_image.iso
[sudo] password for galina:
wodim: No write mode specified.
wodim: Assuming -tao mode.
wodim: Future versions of wodim may have different drive dependent defaults.
Device type : Removable CD-ROM
Version : 5
Response Format: 2
Capabilities :
Vendor_info : 'HL-DT-ST'
Identification : 'DVDRAM GSA-T40N '
Revision : 'JT03'
Device seems to be: Generic mmc2 DVD-R/DVD-RW.
Using generic SCSI-3/mmc DVD-R(W) driver (mmc_mdvd).
Driver flags : SWABAUDIO BURNFREE
Supported modes: PACKET SAO
Speed set to 5540 KB/s
Starting to write CD/DVD at speed 4.0 in real unknown mode for single session.
Last chance to quit, starting real write in 0 seconds. Operation starts.
Track 01: Total bytes read/written: 10964992/10964992 (5354 sectors).
Errno: 5 (Input/output error), flush cache scsi sendcmd: no error
CDB: 35 00 00 00 00 00 00 00 00 00
status: 0x2 (CHECK CONDITION)
Sense Bytes: 72 0B 00 00 00 00 00 0E 09 0C 00 00 00 03 00 00
Sense Key: 0x0 No Additional Sense, Segment 11
Sense Code: 0x00 Qual 0x03 (setmark detected) Fru 0x0
Sense flags: Blk 0 (not valid)
cmd finished after 130.368s timeout 120s
Trouble flushing the cache
wodim: Cannot fixate disk.Записывается (при отмонтировании привода (umount работает корректно)), зато потом диск никак нельзя обратно примонтировать, только если вручную кнопку на дисководе нажать и опять диск вставить.
Я вот думаю, может у меня не хватает пакетов (может нужно доустанавливать пакеты, чтобы более корректно все происходило), например таких пакетов как cdrskin? или cdw?
И вообще, почему, если используется символьная ссылка (отмонтирование то происходит по umount /dev/cdrom, запись делается не с выбором параметров по wodim -scanbus (dev=0,0,0), а просто /dev/sr0?
-
landgraf
- Сообщения: 2140
- Статус: *бунту ненавистник
- ОС: linux
- Контактная информация:
Re: И снова проблемы с записью через терминал
Сообщение
landgraf » 13.01.2013 17:59
Pantera2007 писал(а): ↑
13.01.2013 14:10
/usr/bin/cdrecord: symbolic link to `/etc/alternatives/cdrecord’
ну тогда еще можно продолжить
$ alternatives —display cdrecord
cdrecord — status is auto.
link currently points to /usr/bin/wodim
/usr/bin/wodim — priority 50
slave cdrecord-dvdrecord: /usr/bin/wodim
slave cdrecord-readcd: /usr/bin/readom
slave cdrecord-cdrecordman: /usr/share/man/man1/wodim.1.gz
slave cdrecord-dvdrecordman: /usr/share/man/man1/wodim.1.gz
slave cdrecord-readcdman: /usr/share/man/man1/readom.1.gz
Current `best’ version is /usr/bin/wodim.
-
Pantera2007
- Сообщения: 107
- ОС: Fedora
Re: И снова проблемы с записью через терминал
Сообщение
Pantera2007 » 13.01.2013 18:04
landgraf писал(а): ↑
13.01.2013 17:59
Pantera2007 писал(а): ↑
13.01.2013 14:10
/usr/bin/cdrecord: symbolic link to `/etc/alternatives/cdrecord’
ну тогда еще можно продолжить
$ alternatives —display cdrecord
cdrecord — status is auto.
link currently points to /usr/bin/wodim
/usr/bin/wodim — priority 50
slave cdrecord-dvdrecord: /usr/bin/wodim
slave cdrecord-readcd: /usr/bin/readom
slave cdrecord-cdrecordman: /usr/share/man/man1/wodim.1.gz
slave cdrecord-dvdrecordman: /usr/share/man/man1/wodim.1.gz
slave cdrecord-readcdman: /usr/share/man/man1/readom.1.gz
Current `best’ version is /usr/bin/wodim.
Ну да у меня тоже самое:
Код: Выделить всё
[galina@localhost ~]$ alternatives --display cdrecord
cdrecord - статус "авто".
ссылка сейчас указывает на /usr/bin/wodim
/usr/bin/wodim - приоритет 50
slave cdrecord-dvdrecord: /usr/bin/wodim
slave cdrecord-readcd: /usr/bin/readom
slave cdrecord-cdrecordman: /usr/share/man/man1/wodim.1.gz
slave cdrecord-dvdrecordman: /usr/share/man/man1/wodim.1.gz
slave cdrecord-readcdman: /usr/share/man/man1/readom.1.gz
Текущая `лучшая' версия - /usr/bin/wodim.И что мне это даст?
-
drBatty
- Сообщения: 8735
- Статус: GPG ID: 4DFBD1D6 дом горит, козёл не видит…
- ОС: Slackware-current
- Контактная информация:
Re: И снова проблемы с записью через терминал
Сообщение
drBatty » 13.01.2013 18:27
Pantera2007 писал(а): ↑
13.01.2013 18:04
И что мне это даст?
то, что это НЕ cdrecord, а другая программа. Чем так мучится, я-бы с полным путём запускал исполняемый файл (а не ссылку на ссылку на ссылку. Проблема ещё и в том, что ссылки root’а, ссылки юзера, и ссылки через sudo могут указывать на три _разных_ места)
-
Pantera2007
- Сообщения: 107
- ОС: Fedora
Re: И снова проблемы с записью через терминал
Сообщение
Pantera2007 » 13.01.2013 18:38
drBatty писал(а): ↑
13.01.2013 18:27
то, что это НЕ cdrecord, а другая программа. Чем так мучится, я-бы с полным путём запускал исполняемый файл (а не ссылку на ссылку на ссылку. Проблема ещё и в том, что ссылки root’а, ссылки юзера, и ссылки через sudo могут указывать на три _разных_ места)
Я поняла, что это не cdrecord, а wodim
А полным путем исполняемый файл это как? 
-
Pantera2007
- Сообщения: 107
- ОС: Fedora
Re: И снова проблемы с записью через терминал
Сообщение
Pantera2007 » 13.01.2013 19:32
yars писал(а): ↑
13.01.2013 19:16
А настоящий cdrecord у вас где лежит? Ух, как сложно в Fedora это дело устроено
Ввиду незнания Fedora (), думаю, найти можно так:
/usr/bin/cdrecord
а далее одни отказы в доступе
find: `/proc/41/task/41/ns’: Отказано в доступе
find: `/proc/41/fd’: Отказано в доступе
find: `/proc/41/fdinfo’: Отказано в доступе
find: `/proc/41/ns’: Отказано в доступе
find: `/proc/45/task/45/fd’: Отказано в доступе
find: `/proc/45/task/45/fdinfo’: Отказано в доступе
find: `/proc/45/task/45/ns’: Отказано в доступе
find: `/proc/45/fd’: Отказано в доступе
….. (список довольно внушительный)
Если через sudo, то более коротко, но тоже с отказом в доступе 
sudo find / -name cdrecord -executable
[sudo] password for galina:
/usr/bin/cdrecord
/etc/alternatives/cdrecord
find: `/run/user/galina/gvfs’: Отказано в доступе
-
Bizdelnick
- Модератор
- Сообщения: 19826
- Статус: nulla salus bello
- ОС: Debian GNU/Linux
Re: И снова проблемы с записью через терминал
Сообщение
Bizdelnick » 13.01.2013 19:48
yars писал(а): ↑
13.01.2013 19:16
А настоящий cdrecord у вас где лежит?
Всего одна альтернатива же показана. Значит других не установлено. Да и сдох вроде давным-давно тот cdrecord, который не wodim.
yars писал(а): ↑
13.01.2013 19:16
Ух, как сложно в Fedora это дело устроено
Вообще альтернативы из Дебиана пошли, а сейчас их где только нет.
Пишите правильно:
| в консоли вку́пе (с чем-либо) в общем вообще |
в течение (часа) новичок нюанс по умолчанию |
приемлемо проблема пробовать трафик |
-
Pantera2007
- Сообщения: 107
- ОС: Fedora
Re: И снова проблемы с записью через терминал
Сообщение
Pantera2007 » 13.01.2013 20:21
Bizdelnick писал(а): ↑
13.01.2013 19:48
Всего одна альтернатива же показана. Значит других не установлено.
А какие еще альтернативы есть? Если сказали «А» — давайте говорите и «Б». 
Что еще должно или не должно быть установлено?
В 14 Fedora все ограничилось отмонтированием привода, чтобы запись пошла, а в 16 вообще никаких проблем не было. Чего в 17 изменилось?
-
Pantera2007
- Сообщения: 107
- ОС: Fedora
Re: И снова проблемы с записью через терминал
Сообщение
Pantera2007 » 13.01.2013 20:24
yars писал(а): ↑
13.01.2013 20:21
У меня такой:
Код: Выделить всё
cdrecord --version Cdrecord-ProDVD-ProBD-Clone 3.01a08 (i686-pc-linux-gnu) Copyright (C) 1995-2012 Joerg Schilling
А у меня:
Cdrecord-yelling-line-to-tell-frontends-to-use-it-like-version 2.01.01a03-dvd
Wodim 1.1.11
Copyright © 2006 Cdrkit suite contributors
Based on works from Joerg Schilling, Copyright © 1995-2006, J. Schilling
И о чем это говорит?
-
Pantera2007
- Сообщения: 107
- ОС: Fedora
Re: И снова проблемы с записью через терминал
Сообщение
Pantera2007 » 13.01.2013 20:41
yars писал(а): ↑
13.01.2013 20:29
Мой на cdrecord —help выводит кучу опций.
У меня тоже куча опций, только основная (как я делала и делаю в 14 Fedora) cdrecord —scanbus отвечает:
wodim: No such file or directory.
Cannot open SCSI driver!
For possible targets try ‘wodim —devices’ or ‘wodim -scanbus’.
For possible transport specifiers try ‘wodim dev=help’.
For IDE/ATAPI devices configuration, see the file README.ATAPI.setup from
the wodim documentation.
Короче, я так поняла, что не надо определять параметры моего привода — просто достаточно вместо параметров указать/dev/sr0 и запись будет осуществляться
-
yars
- Сообщения: 1144
- Статус: Slacker!
- ОС: Slackware64-current
Re: И снова проблемы с записью через терминал
Сообщение
yars » 13.01.2013 20:54
Странно:
Код: Выделить всё
yars@localhost:~/works$ cdrecord -scanbus
Cdrecord-ProDVD-ProBD-Clone 3.01a08 (i686-pc-linux-gnu) Copyright (C) 1995-2012 Joerg Schilling
cdrecord: Нет такого файла или каталога. Cannot open '/dev/pg*'. Cannot open or use SCSI driver.
cdrecord: For possible targets try 'cdrecord -scanbus'. Make sure you are root.
cdrecord: For possible transport specifiers try 'cdrecord dev=help'.
yars@localhost:~/works$Победилось так:
Код: Выделить всё
root@localhost:~# ln -s /dev/sr0 /dev/pg1
root@localhost:~# ls -l /dev/sr0 /dev/pg1
lrwxrwxrwx 1 root root 8 янв. 13 20:52 /dev/pg1 -> /dev/sr0
brw-rw---- 1 root cdrom 11, 0 янв. 13 06:13 /dev/sr0
root@localhost:~# cdrecord -scanbus
Cdrecord-ProDVD-ProBD-Clone 3.01a08 (i686-pc-linux-gnu) Copyright (C) 1995-2012 Joerg Schilling
Using libscg version 'schily-0.9'.
scsibus0:
0,0,0 0) *
0,1,0 1) 'VBOX ' 'CD-ROM ' '1.0 ' Removable CD-ROM
0,2,0 2) *
0,3,0 3) *
0,4,0 4) *
0,5,0 5) *
0,6,0 6) *
0,7,0 7) *
Да, живу сейчас под виртуалкой 
Но еще не проверял, пишет, или нет. Вариант с подсовыванием имени реального устройства почему-то не подошел.
UPD: Блин, и не подойдет же:
0,1,0 1) ‘VBOX ‘ ‘CD-ROM ‘ ‘1.0 ‘ Removable CD-ROM
UPD2: А, нашел, надо птичку посадить на место в настройках.
Description
David Nielsen
2006-02-06 09:48:05 UTC
cdrecord: No write mode specified.
cdrecord: Asuming -tao mode.
cdrecord: Future versions of cdrecord may have different drive dependent defaults.
cdrecord: Continuing in 5 seconds...
Cdrecord-Clone 2.01.01a03-dvd (i686-pc-linux-gnu) Copyright (C) 1995-2005 Jörg
Schilling
NOTE: This version contains the OSS DVD extensions for cdrtools and thus may
have bugs related to DVD issues that are not present in the original
cdrtools. Please send bug reports or support requests to
http://bugzilla.redhat.com/bugzilla The original cdrtools author should
not be bothered with problems in this version.
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.
scsidev: 'ATA:1,0,0'
devname: 'ATA'
scsibus: 1 target: 0 lun: 0
Linux sg driver version: 3.5.27
Using libscg version 'schily-0.8'.
cdrecord: Warning: using inofficial libscg transport code version (schily - Red
Hat-scsi-linux-sg.c-1.85-RH '@(#)scsi-linux-sg.c 1.85 05/05/16 Copyright
1997 J. Schilling').
Device type : Removable CD-ROM
Version : 0
Response Format: 1
Vendor_info : 'PLEXTOR '
Identifikation : 'DVDR PX-716AL '
Revision : '1.00'
Device seems to be: Generic mmc2 DVD-R/DVD-RW.
cdrecord: Operation not permitted. Cannot send SCSI cmd via ioctl
I apologize for the bugzilla fuck up that caused this to be reported like 8 times.
This bug causes GUIs like nautilus-cd-burner to fail with rather uninformative
error messages.
Comment 1
Harald Hoyer
2006-02-06 09:55:57 UTC
I thought I already fixed this bug... do you use the latest rawhide version of cdrecord???
Comment 2
David Nielsen
2006-02-06 10:19:32 UTC
Rawhide, updated as of 06 Feb. 2006 rpm -q cdrecord cdrecord-2.01.01.0.a03-2
Comment 3
Harald Hoyer
2006-02-06 12:21:41 UTC
What did you try? Burn or blank? DVD or CDR?
Comment 4
David Nielsen
2006-02-06 12:38:50 UTC
blanking CD-RW (cdrecord -dev=ATA:1,0,0 -blank=fast) cdrecord: Operation not permitted. Cannot send SCSI cmd via ioctl blanking CD-RW (cdrecord -dev=ATA:1,0,0 -blank=all) cdrecord: Operation not permitted. Cannot send SCSI cmd via ioctl burning .iso to CDR (cdrecord -dev=ATA:1,0,0 -driveropts=burnfree -data anonymos-shmoo.iso) cdrecord: Operation not permitted. Cannot send SCSI cmd via ioctl Trying to burn the FC4 DVD image to a DVD-RW disc with information on it yeilds nautilus-cd-burner response that I should insert a rewritable DVD disc or a DVDR with 2.4gb of space - however this disc contains the FC4 DVD data. From cdrecord in cli blanking and burning works though in this case.
Comment 5
Harald Hoyer
2006-02-06 15:01:01 UTC
Do you really own the device? $ ls -l /dev/hd?
Comment 6
David Nielsen
2006-02-06 15:18:28 UTC
Yes I do brw------- 1 david disk 22, 0 6 feb 15:48 /dev/hdc
Comment 7
Harald Hoyer
2006-02-06 15:23:37 UTC
could you please install ltrace and do: $ ltrace cdrecord -dev=ATA:1,0,0 -blank=fast 2>&1 | tee cdrecord-ltrace.txt and attach cdrecord-ltrace.txt
Comment 9
Harald Hoyer
2006-02-06 16:39:59 UTC
hmm.... output of: $ cdrecord -dev=ATA:1,0,0 debug=1000 -blank=fast -VVVVVVVVVVVVVV -vvvvvvvvvv
Comment 11
Harald Hoyer
2006-02-06 16:57:33 UTC
Kernel does not allow the user to send SG_IO commands for Plextor drives.
Comment 12
David Nielsen
2006-02-15 21:19:51 UTC
*** Bug 179861 has been marked as a duplicate of this bug. ***
Comment 13
Dave Jones
2006-03-07 04:30:31 UTC
unlikely to be fixed by release time, and not blocker material (which is "cant install / can't update" right now). This needs work upstream. The problem iirc is that we can't do the 'allowed safe commands' on a per-device basis right now.
Comment 14
Leszek Matok
2006-03-23 17:05:39 UTC
This also happens to real SCSI burner (my TEAC CD-R55S). Making image from nautilus' CD/DVD creator (which can't burn it by itself) and using `cdrecord -v image.iso` as root correctly writes to the disk. Thus my try to chmod u+s `which cdrecord`, but then I get: Cdrecord-Clone 2.01.01a03-dvd (i686-pc-linux-gnu) Copyright (C) 1995-2005 JÄÅrg Schilling NOTE: (blah blah) TOC Type: 1 = CD-ROM cdrecord: Resource temporarily unavailable. Cannot get mmap for 4198400 Bytes on /dev/zero. IIRC, setuid bit on cdrecord doesn't work since kernel 2.6.7 or 2.6.9 anyhow, besides it can be considered insecure (what if an evil iso file could crash cdrecord?) so this doesn't bother me. Still, a normal user would just go on and log in to GNOME as root (if it's possible nowadays) to use nautilus-cd-burner/K3b/xcdroast. This situation encourages, or even forces some users to open their systems to all kinds of dangers, so is this really not blocker material? All this work is being put in SELinux and security, but I do su - to backup my data and someone else may even log in as root possibly only to... read files downloaded from the Internet (like isos). I realize in reality the average user won't open the system to attacks (it's not that obvious that root can burn CD-s when I can't), he/she'll just think Fedora 5 can't burn CD's (which is partly right) (last Fedora version I remember being able to use my burner without root was 1 or 2 before some kernel update). Since my burner is the only SCSI device in my system, using external PCI controller, which has separate device driver, can the safe or unsafe commands be allowed per-driver/module for folks like me? Or can cdrecord accept setuid (this would still require some kernel change if the situation hasn't changed since FC2)?
Comment 15
Jeff Peterson
2006-04-04 02:23:13 UTC
While using Fedora Core 4, I had no problem buring CDs onto my Plextor SCSI CD-RW drive as a normal user. After I upgraded to Fedora Core 5, I could no longer burn CDs as a normal user. I have to make CDs as root What changed?
Comment 16
Barry Powell
2006-04-07 13:54:20 UTC
I am having the same problem with a Plextor PX-716A and 2.6.16-1.2080_FC5, which worked fine under FC4 after we got past kernel 2.6.9. I assume that this is good old SG_IO issue again. I tried upgrading the firmware on my Plextor to the latest firmware, this has no effect. I also have a Dell latitude D510 (DVD/cdrw), where cdrecord works like a charm for non root users. I do have a work around though for my Plextor. I have installed cdrecord from my FC4 installation onto FC5. The cdrecord erase test can now be ran as a normal user. So what has changed in cdrecord between FC4 and FC5?
Comment 17
drago01
2006-04-08 06:27:25 UTC
same problem here: I have to burners installed 1,0,0 100) 'PLEXTOR ' 'DVDR PX-755A ' '1.02' Removable CD-ROM 1,1,0 101) 'LITE-ON ' 'LTR-52246S ' '6S0F' Removable CD-ROM the second one works fine the first one only as root. cdrecord: Operation not permitted. Cannot send SCSI cmd via ioctl
Comment 18
drago01
2006-04-08 11:06:51 UTC
downgraded to FC4 cdrecord an it seems to work fine.
Comment 19
M. Steinborn
2006-04-15 14:07:47 UTC
Compareable here:
1,0,0 100) 'PLEXTOR ' 'CD-R PX-W2410A' '1.04' Removable CD-ROM
does not work, while
1,1,0 101) 'TEAC ' 'DV-W50D ' '1.06' Removable CD-ROM
works fine.
With "cdrtools-2.01.01a07.tar.bz2" from ftp.berlios.de
(compiled and made suid root) both are working fine (but of cause no dvd support).
Comment 20
Igor Miletic
2006-04-20 04:23:36 UTC
Same problem with NEC 3500A. It was working fine just 3 days ago. Current version of cdrdao is cdrdao-1.2.1-1 I tried to burn cue/bin image on blank 700MB write once disk and it gave me same error.
Comment 21
Jugoslav Gacas
2006-04-25 18:43:51 UTC
I own PLEXTOR PX-W5224A and have same problem with cdrecord and every program
using it as backend (nautilus-burner, gnomebaker, ...).
While trying to work the problem out I noticed something strange. When
cdrecord is using ATA transport it doesn't work when invoked by user, but when
ATAPI transport is specified cdrecord works when invoked by user.
Here is how that look like:
1. ATA transport
[juga@onosendai ~]$ cdrecord dev=ATA:1,0,0 -checkdrive
Cdrecord-Clone 2.01.01a03-dvd (i686-pc-linux-gnu) Copyright (C) 1995-2005 Jörg
Schilling
NOTE: This version contains the OSS DVD extensions for cdrtools and thus may
have bugs related to DVD issues that are not present in the original
cdrtools. Please send bug reports or support requests to
http://bugzilla.redhat.com/bugzilla The original cdrtools author should
not be bothered with problems in this version.
scsidev: '/dev/hdc'
devname: '/dev/hdc'
scsibus: -2 target: -2 lun: -2
Linux sg driver version: 3.5.27
Using libscg version 'schily-0.8'.
cdrecord: Warning: using inofficial libscg transport code version (schily - Red
Hat-scsi-linux-sg.c-1.85-RH '@(#)scsi-linux-sg.c 1.85 05/05/16 Copyright
1997 J. Schilling').
Device type : Removable CD-ROM
Version : 0
Response Format: 1
Vendor_info : 'PLEXTOR '
Identifikation : 'CD-R PX-W5224A'
Revision : '1.03'
Device seems to be: Generic mmc CD-RW.
cdrecord: Operation not permitted. Cannot send SCSI cmd via ioctl
2. ATAPI transport
[juga@onosendai ~]$ cdrecord dev=ATAPI:0,0,0 -checkdrive
Cdrecord-Clone 2.01.01a03-dvd (i686-pc-linux-gnu) Copyright (C) 1995-2005 Jörg
Schilling
NOTE: This version contains the OSS DVD extensions for cdrtools and thus may
have bugs related to DVD issues that are not present in the original
cdrtools. Please send bug reports or support requests to
http://bugzilla.redhat.com/bugzilla The original cdrtools author should
not be bothered with problems in this version.
scsidev: 'ATAPI:0,0,0'
devname: 'ATAPI'
scsibus: 0 target: 0 lun: 0
Use of ATA is preferred over ATAPI.
Warning: Using ATA Packet interface.
Warning: The related Linux kernel interface code seems to be unmaintained.
Warning: There is absolutely NO DMA, operations thus are slow.
Using libscg version 'schily-0.8'.
Device type : Removable CD-ROM
Version : 0
Response Format: 1
Vendor_info : 'PLEXTOR '
Identifikation : 'CD-R PX-W5224A'
Revision : '1.03'
Device seems to be: Generic mmc CD-RW.
Using generic SCSI-3/mmc CD-R/CD-RW driver (mmc_cdr).
Driver flags : MMC-3 SWABAUDIO BURNFREE
Supported modes: TAO PACKET SAO SAO/R96P SAO/R96R RAW/R16 RAW/R96P RAW/R96R
Also you can notice the warning sign:
Warning: Using ATA Packet interface.
Warning: The related Linux kernel interface code seems to be unmaintained.
Warning: There is absolutely NO DMA, operations thus are slow.
Maybe this will help solving this really irritating problem!
Comment 22
Jeff Peterson
2006-05-03 01:20:11 UTC
I rolled back to the previous version of cdrdao 1.1.9-9 and now I can burn CDs with my SCSI PlexWriter CDRW. The newer version of cdrdao 1.2.1-1 is the one giving the above errors. Jeff Peterson
Comment 23
Charles Lee
2006-05-23 11:35:03 UTC
(In reply to comment #22)
> I rolled back to the previous version of cdrdao 1.1.9-9 and now I can burn CDs
> with my SCSI PlexWriter CDRW. The newer version of cdrdao 1.2.1-1 is the one
> giving the above errors.
>
> Jeff Peterson
This is untrue. Rolling cdrdao back has no effect at all on the problem - I'm
pretty sure it's a kernel issue.
Is there any progress resolving this?
Thanks.
Comment 24
James Elliott
2006-05-24 05:40:36 UTC
Whoops, count me among the people nailed by this. I've just moved my homebrew (admittedly overly baroque) music jukebox system from an old RedHat 7.1 system to a spanking new Fedora Core 5 system, and I can no longer import nor burn CDs, because that requires a non-root Java process to be able to operate cdrdao and cdrecord. I hope there is a fix on the horizon!
Comment 25
Gérard Milmeister
2006-05-26 18:43:46 UTC
Me too: Plextor 716A What is the difference between cdrecord 2.01.01.0.a03-3 and 2.01.1-9 (the old one)
Comment 26
Gérard Milmeister
2006-05-27 22:59:54 UTC
(In reply to comment #25)
> Me too: Plextor 716A
BTW, in contrast to cdrecord, growisofs works, also with nautilus-cd-burner.
However the choice of writing speeds is strange:
31x (the lowest one)
47x
62x
94x
125x
These cannot be correct of course. The speed flag is passed on to
growisofs, so it probably uses the highest speed available, which
is problematic.
Comment 27
David W. Legg
2006-06-07 18:36:32 UTC
Same symptoms with a PlexWriter CD-R PX-W4012A on FC5 (fully updated.) Kernel is kernel-2.6.16-1.2122_FC5.
Comment 28
Paul Erickson
2006-06-18 14:05:10 UTC
I am having trouble burning cds to my plextor cd-r px-w4824a Gnomebaker produces the error messages below, when I try. Thanks in advance. cdrecord: No write mode specified. cdrecord: Asuming -tao mode. cdrecord: Future versions of cdrecord may have different drive dependent defaults. cdrecord: Continuing in 5 seconds... 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. scsidev: '/dev/hdd' devname: '/dev/hdd' scsibus: -2 target: -2 lun: -2 Linux sg driver version: 3.5.27 cdrecord: Warning: using inofficial libscg transport code version (schily - Red Hat-scsi-linux-sg.c-1.85-RH '@(#)scsi-linux-sg.c 1.85 05/05/16 Copyright 1997 J. Schilling'). SCSI buffer size: 64512 cdrecord: Operation not permitted. Cannot send SCSI cmd via ioctl Cdrecord-Clone 2.01.01a03-dvd (i686-pc-linux-gnu) Copyright (C) 1995-2005 Jörg Schilling NOTE: This version contains the OSS DVD extensions for cdrtools and thus may have bugs related to DVD issues that are not present in the original cdrtools. Please send bug reports or support requests to http://bugzilla.redhat.com/bugzilla The original cdrtools author should not be bothered with problems in this version. TOC Type: 3 = CD-ROM XA mode 2 Using libscg version 'schily-0.8'. atapi: 1 Device type : Removable CD-ROM Version : 0 Response Format: 1 Vendor_info : 'PLEXTOR ' Identifikation : 'CD-R PX-W4824A' Revision : '1.01' Device seems to be: Generic mmc CD-RW. Current: 0x0009 Profile: 0x0008 Profile: 0x0009 (current) Profile: 0x000A
Comment 29
Barry Powell
2006-06-24 17:07:40 UTC
Just to save other people testing this, I have just re-tested with Kernel
2.6.17-1.2139_FC5 and a Plextor PX-716A. The problem still exists.
FC4 cdrecord 2.01-dvd works with Plextor PX-716A
FC5 cdrecord 2.01.01a03-dvd - doesn't work
looks like I will be using the old FC4 version of cdrecord for a while longer
yet ;-)
Comment 30
David Nielsen
2006-06-24 17:33:24 UTC
Shipping FC5 with this bug was embarrasing, shipping FC6 with it would be downright shameful - can we get a pledge going to get this fixed? I'll start out with offering 100USD for this to be fixed before FC6 Final as it's holding me back from advocating GNU/Linux to anyone who shelled out for a decent quality burner, not to mention holding me back from burning using any kind of sane approach. I'll also donate any amount of time needed for testing potential fixes.
Comment 31
Leszek Matok
2006-06-24 22:00:19 UTC
Current kernel 2.6.17-1.2139_FC5 + cdrecord-2.01.01.0.a10-0.FC5.1 from updates-testing still give me the same error for my old TEAC CD-R55S (which isn't decent quality for David, but it does the job) as normal user. But suddenly, chmod u+s /usr/bin/cdrecord made it work! (Current FC5 version gave me the /dev/zero error message). So it's fixed for me in updates-testing for FC5. It seems 5.90 aka 6test1 has the same version onboard. Other users may be scared of suid cdrecord. Can't the "allowed safe commands" be set per-program by selinux? cdrecord won't try to record to hard drives anyhow, right?
Comment 32
David Nielsen
2006-06-24 22:34:51 UTC
Running cdrecord suid would not be considered a viable solution I think, maybe something like switching to libburn (and the cdrecord compatible wrapper for that) would work better longterm. For now I think we'll have to wait for DaveJ or a similar guru to actually propose a solution that would work for FC6.
Comment 33
drago01
2006-06-25 06:06:43 UTC
the solution for looks simple just downgrade and report it upstream.
Comment 34
Leszek Matok
2006-06-25 10:11:25 UTC
There is no upstream, read: "The original cdrtools author should not be bothered with problems in this version." But try the version from updates-testing - it's based on new cdrecord, which includes DVD recording without patches, so I guess it's closer to upstream now and partly fixed the issue for me (using suid, but I'm brave).
Comment 35
Rahul Sundaram
2006-06-26 22:22:57 UTC
Reassigning to -devel
Comment 36
R P Herrold
2006-07-27 21:16:39 UTC
SCSI commands is simply the wrong place to solve the issue. This is a polict
issue. What works is a fix with sudo, and in the %post of cdrecord:
NONCE=`grep '/usr/bin/cdrecord' /etc/sudoers | awk '{print $1}'`
[ "x$NONCE" = "x" ] &&
echo "ALL ALL = NOPASSWD: /usr/bin/cdrecord" >> /etc/sudoers
and a Requires: sudo
in the .spec file.
One could get fancy, and tie it into an active console login only. of course,
but if a person has a shell account on a box, any manner of local escalation
attacks are present.
david -- send the $100 to the FSF please
Comment 37
Leszek Matok
2006-07-27 21:27:28 UTC
I prefer making it setuid root - not only it doesn't require additional package and doesn't do anything in %post, but can drop privileges as soon as it's possible (and afair it does, or at least tries). Also works from guis with no effort at all. Now we want to make it work without becoming root at all.
Comment 38
James Elliott
2006-07-27 21:38:16 UTC
Right. Sudo is not an option, nor is requiring it to be setuid. I need to be able to run this as a user command because an unprivileged tomcat process needs to be able to operate these commands for my elaborate jukebox system to work properly. They used to work, they need to work again. Don't make me go back to RedHat 7!
Comment 39
David Nielsen
2006-07-27 23:15:56 UTC
As mentioned earlier in this bug (comment #32), any solution suid, sudo or similar is not a solution to this problem as it only brings back the security issue we were trying to fix. DaveJ has yet to comment on the solution he would like to see, I would also like everyone here to add to the pledge rather than leaving it at a the 100 USD I can afford to spend, we should all pool together for a solution that is acceptable for inclusion in Fedora Core 6. As mentioned that excludes all manners of running as root, sorry. Time is running out, Test 2 hits soonish and that leaves only precious little time to make this work. Don't let FC ship another release that doesn't burn CDs, it's a regression and it is preventing a lot of users from doing what is to be considered an every day task.
Comment 40
drago01
2006-07-28 11:26:36 UTC
we should capture the commands that are required and patch the kernel to allow them; this is somehow a hack but its better than no burning and it would be more secure than sbit (and other root hacks)
Comment 41
Rahul Sundaram
2006-08-22 14:38:47 UTC
Does the cdrecord downgrade in the development tree change anything?
Comment 42
Barry Powell
2006-08-26 15:15:05 UTC
Based upon a sample of one test to a CDRW - It works! :-) I had actually replaced my Plextor with a different model just so that I could burn some disks. Any how getting back to this thread. I installed FC5 + all updates for 26 Aug on my old test pc. Installed Plextor PX-716 drive, as expected it didn't work as a non root user. Installed glibc + glibc-common + cdrecord-2.01-10 from development. Now normal users can burn CDROMs again (I will test DVD writing later). I can attached cdrecord debug outputs if they are required. This is excellent news and I hope this makes FC6
Comment 43
Barry Powell
2006-08-26 15:42:03 UTC
I can now also confirm that DVD writing also works with cdrecord-2.01-10
Comment 44
Christian Nolte
2006-08-27 16:39:16 UTC
Just a quick "me-too". It works for me! Thanks.
Comment 45
Rahul Sundaram
2006-09-05 21:36:51 UTC
Ok guys. Judging from the above comments it appears that the downgrade to solve the GPL/CDDL combination mess in later versions of cdrecord appears to fix this problem as a nice side effect just as I thought. We have a ongoing discussion on linux scsi list to solve the general issue but that shouldnt affect users now. Thank you for all the testing and feedback. I am closing this bug now.
INTELLIGENT WORK FORUMS
FOR COMPUTER PROFESSIONALS
Contact US
Thanks. We have received your request and will respond promptly.
Log In
Come Join Us!
Are you a
Computer / IT professional?
Join Tek-Tips Forums!
- Talk With Other Members
- Be Notified Of Responses
To Your Posts - Keyword Search
- One-Click Access To Your
Favorite Forums - Automated Signatures
On Your Posts - Best Of All, It’s Free!
*Tek-Tips’s functionality depends on members receiving e-mail. By joining you are opting in to receive e-mail.
Posting Guidelines
Promoting, selling, recruiting, coursework and thesis posting is forbidden.
Students Click Here
smitty mkcd fails with DVD-R : Cannot send SCSI cmd via ioctlsmitty mkcd fails with DVD-R : Cannot send SCSI cmd via ioctl(OP) 17 Apr 05 14:40 Hi Running cdrecord … If you would like to attempt to write to another CD or DVD, replace Can anyone help me to find out what’s happening and how to create my mksysb backup? Red Flag SubmittedThank you for helping keep Tek-Tips Forums free from inappropriate posts. |
Join Tek-Tips® Today!
Join your peers on the Internet’s largest technical computer professional community.
It’s easy to join and it’s free.
Here’s Why Members Love Tek-Tips Forums:
Talk To Other Members- Notification Of Responses To Questions
- Favorite Forums One Click Access
- Keyword Search Of All Posts, And More…
Talk To Other MembersRegister now while it’s still free!
Already a member? Close this window and log in.
Join Us Close
- Index
- » Applications & Desktop Environments
- » [SOLVED] Brasero won’t write to disc because of permissions
Pages: 1
#1 2020-11-08 10:09:41
- pavlosdec
- Member
- Registered: 2019-03-10
- Posts: 17
[SOLVED] Brasero won’t write to disc because of permissions
I don’t know if this problem is a simple one, but I’m stuck.
I tried to burn an ISO to CD-R with Brasero. Before the writing begins it gives me this message «You do not have the required permissions to use this drive» and it ejects the disc.
I added the user to these groups: storage, disk, optical, but the outcome was the same.
I read the wiki (Optical disc drive page) and I tried to burn the ISO with the cdrecord CLI command as a user and it failed. But with the same command with sudo succeded…
What kind of permission I’m missing here?
Thanks for any help.
Last edited by pavlosdec (2020-11-12 17:44:34)
#2 2020-11-08 10:14:52
- pavlosdec
- Member
- Registered: 2019-03-10
- Posts: 17
Re: [SOLVED] Brasero won’t write to disc because of permissions
This is the output of cdrecord used by normal user:
Cdrecord-ProDVD-ProBD-Clone 3.02a09 (x86_64-unknown-linux-gnu) Copyright (C) 1995-2016 Joerg Schilling
TOC Type: 1 = CD-ROM
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.
cdrecord: Insufficient 'file read' privileges. You will not be able to open all needed devices.
cdrecord: Insufficient 'file write' privileges. You will not be able to open all needed devices.
cdrecord: Insufficient 'device' privileges. You may not be able to send all needed SCSI commands, this my cause various unexplainable problems.
cdrecord: Insufficient 'memlock' privileges. You may get buffer underruns.
cdrecord: Insufficient 'priocntl' privileges. You may get buffer underruns.
cdrecord: Insufficient 'network' privileges. You will not be able to do remote SCSI.
scsidev: '/dev/sr0'
devname: '/dev/sr0'
scsibus: -2 target: -2 lun: -2
Warning: Open by 'devname' is unintentional and not supported.
Linux sg driver version: 3.5.27
Using libscg version 'schily-0.9'.
SCSI buffer size: 64512
atapi: 1
Device type : Removable CD-ROM
Version : 5
Response Format: 2
Capabilities :
Vendor_info : 'HL-DT-ST'
Identifikation : 'DVDRAM GH22NS50 '
Revision : 'TN02'
Device seems to be: Generic mmc2 DVD-R/DVD-RW/DVD-RAM.
Current: CD-R
Profile: DVD-RAM
Profile: DVD-R sequential recording
Profile: DVD-R/DL sequential recording
Profile: DVD-R/DL layer jump recording
Profile: DVD-RW sequential recording
Profile: DVD-RW restricted overwrite
Profile: DVD+RW
Profile: DVD+R
Profile: DVD+R/DL
Profile: DVD-ROM
Profile: CD-R (current)
Profile: CD-RW
Profile: CD-ROM
Profile: Removable Disk
Using generic SCSI-3/mmc CD-R/CD-RW driver (mmc_cdr).
Driver flags : MMC-3 SWABAUDIO BURNFREE
Supported modes: TAO PACKET SAO SAO/R96P SAO/R96R RAW/R16 RAW/R96P RAW/R96R LAYER_JUMP
Drive buf size : 1053696 = 1029 KB
Drive pbuf size: 1966080 = 1920 KB
cdrecord: Warning: DMA resid 0 for 'read buffer', actual data is too short.
cdrecord: Warning: The DMA speed test has been skipped.
FIFO size : 4194304 = 4096 KB
Track 01: data 562 MB
Total size: 646 MB (64:00.97) = 288073 sectors
Lout start: 646 MB (64:02/73) = 288073 sectors
cdrecord: Operation not permitted. rezero unit: scsi sendcmd: fatal error
CDB: 01 00 00 00 00 00
cdrecord: Operation not permitted. Cannot send SCSI cmd via ioctl.
cdrecord: Operation not permitted. Cannot open or use SCSI driver.
cdrecord: For possible targets try 'cdrecord -scanbus'. Make sure you are root.
cdrecord: For possible transport specifiers try 'cdrecord dev=help'.Last edited by pavlosdec (2020-11-08 16:13:17)
#3 2020-11-08 11:32:11
- mpan
- Member
- Registered: 2012-08-01
- Posts: 986
- Website
Re: [SOLVED] Brasero won’t write to disc because of permissions
Sometimes I seem a bit harsh — don’t get offended too easily! PGP: 7C848198AE93D3BB
#4 2020-11-08 11:36:23
- pavlosdec
- Member
- Registered: 2019-03-10
- Posts: 17
Re: [SOLVED] Brasero won’t write to disc because of permissions
I think it clould be tha same. And it is still unsolved…
I will keep an eye on that thread, thank you…
#5 2020-11-08 15:16:44
- ewaller
- Administrator
- From: Pasadena, CA
- Registered: 2009-07-13
- Posts: 19,010
Re: [SOLVED] Brasero won’t write to disc because of permissions
Can you verify that the group for the drive is ‘optical’ and that there exist group write permissions? Post the output of ls -l /dev/sr0
After you added your user to the ‘optical’ group, did you log out and log back in? As a sanity check, what is the output of groups ?
Nothing is too wonderful to be true, if it be consistent with the laws of nature — Michael Faraday
Sometimes it is the people no one can imagine anything of who do the things no one can imagine. — Alan Turing
—
How to Ask Questions the Smart Way
#6 2020-11-08 15:50:46
- pavlosdec
- Member
- Registered: 2019-03-10
- Posts: 17
Re: [SOLVED] Brasero won’t write to disc because of permissions
I did all that but the issue is this
The problem is the latest version of cdrtools. When I downgraded to the previous version there was no issue.
So, I think I will be ignoring the package’s latest version for now…
P.S. Should I mark this as SOLVED??? (kinda…)
Last edited by pavlosdec (2020-11-08 15:51:40)
#7 2020-11-08 15:54:07
- mpan
- Member
- Registered: 2012-08-01
- Posts: 986
- Website
Re: [SOLVED] Brasero won’t write to disc because of permissions
ewaller:
Even if one is in optical, it won’t work. cdrecord requires various other privileges — not merely access to the device file.
Just to make it clear:
$ ls -l /dev/sr0
brw-rw----+ 1 root optical 11, 0 Nov 3 01:44 /dev/sr0
$ groups
lp http video audio optical storage scanner users wireshark data500 beepersSometimes I seem a bit harsh — don’t get offended too easily! PGP: 7C848198AE93D3BB
#8 2020-11-08 16:12:24
- ewaller
- Administrator
- From: Pasadena, CA
- Registered: 2009-07-13
- Posts: 19,010
Re: [SOLVED] Brasero won’t write to disc because of permissions
Okay, good to know. I always try for the low hanging fruit first
Nothing is too wonderful to be true, if it be consistent with the laws of nature — Michael Faraday
Sometimes it is the people no one can imagine anything of who do the things no one can imagine. — Alan Turing
—
How to Ask Questions the Smart Way
#9 2020-11-08 16:39:56
- Spinnekop
- Member
- Registered: 2018-02-16
- Posts: 24
Re: [SOLVED] Brasero won’t write to disc because of permissions
I had this problem a while back and discovered on a working machine that the permission for /usr/bin/cdrecord was
-rws—s—x 1 root root 574448 Jul 7 16:35 cdrecord
once I did a «sudo chmod u+s cdrecord» on the non-working machine it worked. I think I may have done g+s as well but that probably wasn’t necessary.
If I was clever I might be able to tell you why it worked…
Last edited by Spinnekop (2020-11-08 16:44:58)
Umuntu Ngumuntu Ngabantu
—————————————
a person is a person through other people
#10 2020-11-09 05:23:35
- mpan
- Member
- Registered: 2012-08-01
- Posts: 986
- Website
Re: [SOLVED] Brasero won’t write to disc because of permissions
ewaller wrote:
Okay, good to know. I always try for the low hanging fruit first
No need to feel bad about it. I find the “just setuid the binary” solution to be dirty and suggest it only as a temporary way to circumvent the problem until the package is fixed. Ideally, as suggested by the cdrtools page and 3.01 release notes, that should be solved using capabilities.
I would probably ask the same question as you did, if not that this is an n-th person who experiences the same problem (me included).
Spinnekop wrote:
I think I may have done g+s as well but that probably wasn’t necessary.
To clarify: indeed it is not necessary. A process running as root is already a root. 
Last edited by mpan (2020-11-09 05:25:39)
Sometimes I seem a bit harsh — don’t get offended too easily! PGP: 7C848198AE93D3BB
#11 2020-11-09 08:16:12
- scdbackup
- Member
- Registered: 2013-05-30
- Posts: 72
Re: [SOLVED] Brasero won’t write to disc because of permissions
Hi,
congrats to finding the solution.
As programmer of libburn i have to state that the view of cdrecord on
permissions is unfounded and gets deliberately enforced by a piece of
code in cdrecord, not by the Linux kernel.
With mere rw-permission to the device file it is possible to do all SCSI
transactions which are necessary for burning.
Everybody who has a text editor and a C compiler can get rid of the
demand for any superuser powers, be they coarse or finely granulated.
It is about 9 code lines (and 9 comment lines) in cdrecord.c :
/*
* Linux-2.6.8.1 did break the SCSI pass through kernel interface.
* Since then, many SCSI commands are filtered away by the Linux kernel
* if we do not have root privilleges. Since REZERO UNIT is in the list
* of filtered SCSI commands, it is a good indicator on whether we run
* with the needed privileges. Failing here is better than failing later
* with e.g. vendor unique commands, where cdrecord would miss
* functionality or fail completely after starting to write.
*/
seterrno(0);
scgp->silent++;
code = rezero_unit(scgp); /* Not supported by some drives */
scgp->silent--;
err = geterrno();
if (code < 0 && (err == EPERM || err == EACCES)) {
linuxcheck(); /* For version 1.413 of cdrecord.c */
scg_openerr("");
}Throw them out and be free.
Have a nice day 
Thomas
#12 2020-11-12 17:42:26
- pavlosdec
- Member
- Registered: 2019-03-10
- Posts: 17
Re: [SOLVED] Brasero won’t write to disc because of permissions
Solved by updating cdrtools to 3.02a09-4
#13 2020-11-13 04:23:47
- mpan
- Member
- Registered: 2012-08-01
- Posts: 986
- Website
Re: [SOLVED] Brasero won’t write to disc because of permissions
scdbackup: don’t forget to remove the whole comment above, explaining why those lines are required for cdrecord to work properly. Though you may report that as a bug: if it is not needed, it may be removed upstream.
Last edited by mpan (2020-11-13 04:25:07)
Sometimes I seem a bit harsh — don’t get offended too easily! PGP: 7C848198AE93D3BB
Comments
Yarny0
added a commit
to Yarny0/nixpkgs
that referenced
this issue
Aug 4, 2018
The k3b package uses a wrapper script to inject binaries
that are called by k3b and do the actual work into PATH.
Most of those binaries are beyond reproach.
There are, however, legitimate reasons to replace
cdrtools with cdrkit, or with nothing at all to encourage
k3b to use suid wrappers from the surrounding PATH.
To ease the use of such cdrtools replacements,
this commit moves the wrapper script into its
own derivation (created with symlinkJoin).
To use k3b with cdrkit, this line in configuration.nix
suffices and won't trigger a rebuild of k3b itself:
> environment.systemPackages = with pkgs; [ k3b.override { cdrtools = cdrkit; } ];
Using "null" for cdrtools is possible and will skip
the addition of cdrtools to PATH in the wrapper script.
This commit is motivated by
NixOS#19154 .
stale
bot
added
the
2.status: stale
https://github.com/NixOS/nixpkgs/blob/master/.github/STALE-BOT.md
label
Jun 4, 2020
stale
bot
removed
the
2.status: stale
https://github.com/NixOS/nixpkgs/blob/master/.github/STALE-BOT.md
label
Jun 4, 2020
stale
bot
added
the
2.status: stale
https://github.com/NixOS/nixpkgs/blob/master/.github/STALE-BOT.md
label
Jan 15, 2021
stale
bot
removed
the
2.status: stale
https://github.com/NixOS/nixpkgs/blob/master/.github/STALE-BOT.md
label
Feb 4, 2021
stale
bot
added
the
2.status: stale
https://github.com/NixOS/nixpkgs/blob/master/.github/STALE-BOT.md
label
Aug 4, 2021
stale
bot
removed
the
2.status: stale
https://github.com/NixOS/nixpkgs/blob/master/.github/STALE-BOT.md
label
Nov 4, 2021
ngiger
added a commit
to ngiger/nixpkgs
that referenced
this issue
Apr 7, 2022
eliandoran
pushed a commit
to eliandoran/nixpkgs
that referenced
this issue
Apr 23, 2022
