[opensuse-factory] How to create write access to /dev/sr0 for K3B in 11.0.42?
Hi, If this subject allready appeared here, my appologises, if i did not see it.. In etc/fstab is no floppydrive visible, nor a dvd drive... proc /proc proc defaults 0 0 sysfs /sys sysfs noauto 0 0 debugfs /sys/kernel/debug debugfs noauto 0 0 usbfs /proc/bus/usb usbfs noauto 0 0 devpts /dev/pts devpts mode=0620,gid=5 0 0 in /mnt the drive is not visible oddball@AMD64x2-sfn1:~> mount /dev/sr0 mount: cannot find /dev/sr0 neither in /etc/fstab nor in /etc/mtab is there something i can do about this, or is it a bug? -- Enjoy your time around, Oddball (Now or never...) OS: Linux 2.6.25.9-3-default x86_64 Current user: oddball@AMD64x2-sfn1 System: openSUSE 11.0.42 (x86_64) Alpha0 KDE: 4.00.85 (KDE 4.0.85 (KDE 4.1 >= 20080703) "release 3.3" --------------------------------------------------------------------- To unsubscribe, e-mail: opensuse-factory+unsubscribe@opensuse.org For additional commands, e-mail: opensuse-factory+help@opensuse.org
On Thursday 10 July 2008 06:51:07 am Oddball wrote: ....
oddball@AMD64x2-sfn1:~> mount /dev/sr0 mount: cannot find /dev/sr0 neither in /etc/fstab nor in /etc/mtab
is there something i can do about this, or is it a bug?
mkdir /mnt/dvd; mount /dev/sr0 /mnt/dvd If it is not in fstab than you have to define mount point by hand. man mount is your friend Though, my crystal ball can't tell me what was the problem to look for /dev/sr0 in fstab or /mnt . Automatic mount usually goes in /media directory. -- Regards, Rajko http://en.opensuse.org/Portal needs helpful hands. --------------------------------------------------------------------- To unsubscribe, e-mail: opensuse-factory+unsubscribe@opensuse.org For additional commands, e-mail: opensuse-factory+help@opensuse.org
Rajko M. schreef:
On Thursday 10 July 2008 06:51:07 am Oddball wrote: ....
oddball@AMD64x2-sfn1:~> mount /dev/sr0 mount: cannot find /dev/sr0 neither in /etc/fstab nor in /etc/mtab
is there something i can do about this, or is it a bug?
mkdir /mnt/dvd; mount /dev/sr0 /mnt/dvd
It will only mount readonly. mount tells me it is write protected, but i allready knew that from K3B... mount: u moet een bestandssysteemsoort aangeven means: you must specify a filesystem
If it is not in fstab than you have to define mount point by hand.
man mount is your friend
Though, my crystal ball can't tell me what was the problem to look for /dev/sr0 in fstab or /mnt .
Automatic mount usually goes in /media directory.
Well, sofar only usb and cardreader goes there.... -- Enjoy your time around, Oddball (Now or never...) OS: Linux 2.6.25.9-3-default x86_64 Current user: oddball@AMD64x2-sfn1 System: openSUSE 11.0.42 (x86_64) Alpha0 KDE: 4.00.85 (KDE 4.0.85 (KDE 4.1 >= 20080703) "release 3.3" --------------------------------------------------------------------- To unsubscribe, e-mail: opensuse-factory+unsubscribe@opensuse.org For additional commands, e-mail: opensuse-factory+help@opensuse.org
-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1 The Friday 2008-07-11 at 10:08 +0200, Oddball wrote:
It will only mount readonly. mount tells me it is write protected, but i allready knew that from K3B...
To access /dev/sr0 rw you have to change its permissions for the group, or add your user to the group. Normally the login process changes the ownership of the device to the user owning the desktop, but I don't know exactly who is responsible for this change nowdays. - -- Cheers, Carlos E. R. -----BEGIN PGP SIGNATURE----- Version: GnuPG v2.0.4-svn0 (GNU/Linux) iD8DBQFId0e7tTMYHG2NR9URAr+QAJ4rgGG/TwpCSiGq2n4QEjO9LoabWQCfRqRn GYMwQEylRQi8miwv0LCfjIk= =xC+6 -----END PGP SIGNATURE----- --------------------------------------------------------------------- To unsubscribe, e-mail: opensuse-factory+unsubscribe@opensuse.org For additional commands, e-mail: opensuse-factory+help@opensuse.org
Carlos E. R. wrote:
The Friday 2008-07-11 at 10:08 +0200, Oddball wrote:
It will only mount readonly. mount tells me it is write protected, but i allready knew that from K3B...
To access /dev/sr0 rw you have to change its permissions for the group, or add your user to the group. Normally the login process changes the ownership of the device to the user owning the desktop, but I don't know exactly who is responsible for this change nowdays.
-- Cheers, Carlos E. R.
I had the problem with /dev/sr0 coming up read only in k3b for a while. To solve it you need to have both user and users in fstab. Regards Dave P --------------------------------------------------------------------- To unsubscribe, e-mail: opensuse-factory+unsubscribe@opensuse.org For additional commands, e-mail: opensuse-factory+help@opensuse.org
Am Freitag, 11. Juli 2008 schrieb Carlos E. R.:
The Friday 2008-07-11 at 10:08 +0200, Oddball wrote:
It will only mount readonly. mount tells me it is write protected, but i allready knew that from K3B...
To access /dev/sr0 rw you have to change its permissions for the group, or add your user to the group.
You do not have to do anything like this at least since SuSE 8.2! http://en.opensuse.org/SDB:8.2_Resource_Manager
Normally the login process changes the ownership of the device to the user owning the desktop,
Not anymore. jan@karl:~> l /dev/sr0 brw-rw----+ 1 root disk 11, 0 11. Jul 2008 /dev/sr0 ^ (ACL) Some time ago, there was the file /etc/logindevperms that changed device permissions (pam_devperm).
but I don't know exactly who is responsible for this change nowdays.
For the basic changes (owner, group, mode): udev. For ACL (indicated by the '+'): hal/hal-resmgr. jan@karl:~> getfacl /dev/sr0 getfacl: Removing leading '/' from absolute path names # file: dev/sr0 # owner: root # group: disk user::rw- user:jan:rw- group::r-- mask::rw- other::--- So, the owner is root, but the current desktop user (that's me) has read and write access, too. This is at least true for 10.3 and I doubt that 11.0 reverted to the old way of granting access to devices. Gruß Jan -- Humpty Dumpty was pushed. --------------------------------------------------------------------- To unsubscribe, e-mail: opensuse-factory+unsubscribe@opensuse.org For additional commands, e-mail: opensuse-factory+help@opensuse.org
On Friday 11 July 2008 10:41:43 am Jan Ritzerfeld wrote:
Am Freitag, 11. Juli 2008 schrieb Carlos E. R.:
The Friday 2008-07-11 at 10:08 +0200, Oddball wrote:
It will only mount readonly. mount tells me it is write protected, but i allready knew that from K3B... ... For the basic changes (owner, group, mode): udev. For ACL (indicated by the '+'): hal/hal-resmgr. jan@karl:~> getfacl /dev/sr0 getfacl: Removing leading '/' from absolute path names # file: dev/sr0 # owner: root # group: disk user::rw- user:jan:rw- group::r-- mask::rw- other::--- ...
The same in 11.0: linux:~# getfacl /dev/sr0 getfacl: Removing leading '/' from absolute path names # file: dev/sr0 # owner: root # group: disk user::rw- user:rm:rw- group::r-- mask::rw- other::--- -- Regards, Rajko http://en.opensuse.org/Portal needs helpful hands. --------------------------------------------------------------------- To unsubscribe, e-mail: opensuse-factory+unsubscribe@opensuse.org For additional commands, e-mail: opensuse-factory+help@opensuse.org
Rajko M. schreef:
On Friday 11 July 2008 10:41:43 am Jan Ritzerfeld wrote:
Am Freitag, 11. Juli 2008 schrieb Carlos E. R.:
The Friday 2008-07-11 at 10:08 +0200, Oddball wrote:
It will only mount readonly. mount tells me it is write protected, but i allready knew that from K3B...
...
For the basic changes (owner, group, mode): udev. For ACL (indicated by the '+'): hal/hal-resmgr. jan@karl:~> getfacl /dev/sr0 getfacl: Removing leading '/' from absolute path names # file: dev/sr0 # owner: root # group: disk user::rw- user:jan:rw- group::r-- mask::rw- other::---
...
The same in 11.0:
linux:~# getfacl /dev/sr0 getfacl: Removing leading '/' from absolute path names # file: dev/sr0 # owner: root # group: disk user::rw- user:rm:rw- group::r-- mask::rw- other::---
Yes, this screen i get also, but if i want to burn an iso, the writerapp (K3B), has no acces to the drive. oddball@AMD64x2-sfn1:~> getfacl /dev/sr0 getfacl: Removing leading '/' from absolute path names # file: dev/sr0 # owner: root # group: disk user::rw- user:oddball:rw- group::r-- mask::rw- other::--- oddball@AMD64x2-sfn1:~> ( i had a screenshot, but it was to big, mailinglist refused to send it, and i could not get my password right for the website, maybe this smaller one works.) but: Did you actualy try to burn something? -- Enjoy your time around, Oddball (Now or never...) OS: Linux 2.6.25.9-3-default x86_64 Current user: oddball@AMD64x2-sfn1 System: openSUSE 11.0.42 (x86_64) Alpha0 KDE: 4.00.85 (KDE 4.0.85 (KDE 4.1 >= 20080703) "release 3.3"
On Monday 14 July 2008 03:56:00 pm Oddball wrote: ...
Did you actualy try to burn something?
Not yet with k3b. I use growisofs recently as it will burn any iso on DVD-RW, which I have few more than I actually need, and I'm low on CD-Rs. Last I burned KDE4-Live CD iso few moments ago. Can you start k3b from konsole and run dmesg right after that. It will give more information what is going on. The device node seems to be set correctly. -- Regards, Rajko http://en.opensuse.org/Portal needs helpful hands. --------------------------------------------------------------------- To unsubscribe, e-mail: opensuse-factory+unsubscribe@opensuse.org For additional commands, e-mail: opensuse-factory+help@opensuse.org
Rajko M. schreef:
On Monday 14 July 2008 03:56:00 pm Oddball wrote: ...
Did you actualy try to burn something?
Not yet with k3b. I use growisofs recently as it will burn any iso on DVD-RW, which I have few more than I actually need, and I'm low on CD-Rs. Last I burned KDE4-Live CD iso few moments ago.
Can you start k3b from konsole and run dmesg right after that. It will give more information what is going on. The device node seems to be set correctly.
I did. When i call from console, K3B KDE4 comes up, but this has still some bugs, and hangs instead of giving an error message... dmesg is quite a lot of info... do you want me to put it somewhere? https://bugzilla.novell.com/show_bug.cgi?id=408252 i filed a bug on the matter.. -- Enjoy your time around, Oddball (Now or never...) OS: Linux 2.6.25.9-3-default x86_64 Current user: oddball@AMD64x2-sfn1 System: openSUSE 11.0.42 (x86_64) Alpha0 KDE: 4.00.85 (KDE 4.0.85 (KDE 4.1 >= 20080703) "release 3.3" --------------------------------------------------------------------- To unsubscribe, e-mail: opensuse-factory+unsubscribe@opensuse.org For additional commands, e-mail: opensuse-factory+help@opensuse.org
On Tuesday 15 July 2008 02:33:59 am Oddball wrote:
Rajko M. schreef:
On Monday 14 July 2008 03:56:00 pm Oddball wrote: ...
Did you actualy try to burn something?
Not yet with k3b. I use growisofs recently as it will burn any iso on DVD-RW, which I have few more than I actually need, and I'm low on CD-Rs. Last I burned KDE4-Live CD iso few moments ago.
Can you start k3b from konsole and run dmesg right after that. It will give more information what is going on. The device node seems to be set correctly.
I did. When i call from console, K3B KDE4 comes up, but this has still some bugs, and hangs instead of giving an error message...
Any other text in console that might help to see where it stops?
dmesg is quite a lot of info... do you want me to put it somewhere? https://bugzilla.novell.com/show_bug.cgi?id=408252 i filed a bug on the matter..
Attach dmesg to bug report. Please run it after you attempt to start k3b from console. -- Regards, Rajko http://en.opensuse.org/Portal needs helpful hands. --------------------------------------------------------------------- To unsubscribe, e-mail: opensuse-factory+unsubscribe@opensuse.org For additional commands, e-mail: opensuse-factory+help@opensuse.org
Am Montag, 14. Juli 2008 schrieb Oddball:
(...). ( i had a screenshot, but it was to big, mailinglist refused to send it, and i could not get my password right for the website, maybe this smaller one works.) (...).
Please post the debug output, i.e., press "Debuguitvoer tonen" and copy the content of the window that will be opened then. In addition, please check which device k3b will use by executing: grep "writer" ~/.kde/share/config/k3brc Gruß Jan -- Most men who run down women are usually running down only one woman. --------------------------------------------------------------------- To unsubscribe, e-mail: opensuse-factory+unsubscribe@opensuse.org For additional commands, e-mail: opensuse-factory+help@opensuse.org
Jan Ritzerfeld schreef:
Am Montag, 14. Juli 2008 schrieb Oddball:
(...). ( i had a screenshot, but it was to big, mailinglist refused to send it, and i could not get my password right for the website, maybe this smaller one works.) (...).
Please post the debug output, i.e., press "Debuguitvoer tonen" and copy the content of the window that will be opened then. In addition, please check which device k3b will use by executing: grep "writer" ~/.kde/share/config/k3brc
Gruß Jan
oddball@AMD64x2-sfn1:~> grep "writer" ~/.kde/share/config/k3brc current_writer=/dev/sr0 writer_device=/dev/sr0 writer_device=/dev/sr0 writer_device=/dev/sr0 oddball@AMD64x2-sfn1:~> Now it worked for the KDE3 version After 'getfacl', i did not reboot the box..(thought it would save the changes imediately.) The output is from the KDE3 version, KDE4 version still has 'device write-protected' problem. System ----------------------- K3b Version: 1.0.5 KDE Version: 3.5.9 "release 52" QT Version: 3.3.8b Kernel: 2.6.25.9-3-default Devices ----------------------- ATAPI DVD DC 16X8X5 103 (/dev/sr0, ) [CD-R, CD-RW, CD-ROM, DVD-ROM, DVD-R, DVD-RW, DVD-R DL, DVD+R, DVD+RW, DVD+R DL] [DVD-ROM, DVD-R sequentieel, DVD-R Dual Layer sequentieel, DVD-R Dual Layer Jump, DVD-RAM, DVD-RW met beperkte overschrijving, DVD-RW sequentieel, DVD+RW, DVD+R, DVD+R Dual Layer, CD-ROM, CD-R, CD-RW] [SAO, TAO, RAW, SAO/R96P, SAO/R96R, RAW/R16, RAW/R96P, RAW/R96R, Beperkt overschrijven, Layer Jump] Used versions ----------------------- cdrecord: 1.1.7.1 cdrecord ----------------------- /usr/bin/X11/wodim: Operation not permitted. Warning: Cannot raise RLIMIT_MEMLOCK limits.scsidev: '/dev/sr0' devname: '/dev/sr0' scsibus: -2 target: -2 lun: -2 Linux sg driver version: 3.5.27 Wodim version: 1.1.7.1 SCSI buffer size: 64512 Beginning DMA speed test. Set CDR_NODMATEST environment variable if device communication breaks or freezes immediately after that. TOC Type: 1 = CD-ROM Driveropts: 'burnfree' Device type : Removable CD-ROM Version : 5 Response Format: 2 Capabilities : Vendor_info : 'ATAPI ' Identification : 'DVD DC 16X8X5 ' Revision : '103 ' Device seems to be: Generic mmc2 DVD-R/DVD-RW. Current: 0x0009 (CD-R) Profile: 0x002B (DVD+R/DL) Profile: 0x001B (DVD+R) Profile: 0x001A (DVD+RW) Profile: 0x0016 (DVD-R/DL layer jump recording) Profile: 0x0015 (DVD-R/DL sequential recording) Profile: 0x0014 (DVD-RW sequential recording) Profile: 0x0013 (DVD-RW restricted overwrite) Profile: 0x0012 (DVD-RAM) Profile: 0x0011 (DVD-R sequential recording) Profile: 0x0010 (DVD-ROM) Profile: 0x000A (CD-RW) Profile: 0x0009 (CD-R) (current) Profile: 0x0008 (CD-ROM) Profile: 0x0002 (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 Drive buf size : 1114112 = 1088 KB FIFO size : 4194304 = 4096 KB Speed set to 5645 KB/s Track 01: data 49 MB Total size: 57 MB (05:39.60) = 25470 sectors Lout start: 57 MB (05:41/45) = 25470 sectors Current Secsize: 2048 ATIP info from disk: Indicated writing power: 5 Is not unrestricted Is not erasable Disk sub type: Medium Type B, low Beta category (B-) (4) ATIP start of lead in: -11824 (97:24/26) ATIP start of lead out: 106350 (23:40/00) Disk type: Short strategy type (Phthalocyanine or similar) Manuf. index: 4 Manufacturer: Computer Support Italy s.r.l. Blocks total: 106350 Blocks current: 106350 Blocks remaining: 80880 Starting to write CD/DVD at speed 32.0 in real SAO mode for single session. Last chance to quit, starting real write in 2 seconds. 1 seconds. 0 seconds. Operation starts. Waiting for reader process to fill input buffer ... input buffer ready. Performing OPC... Sending CUE sheet... Writing pregap for track 1 at -150 Starting new track at sector: 0 Track 01: 0 of 49 MB written. Track 01: 1 of 49 MB written (fifo 78%) [buf 97%] 18.5x. Track 01: 2 of 49 MB written (fifo 51%) [buf 98%] 18.9x. Track 01: 3 of 49 MB written (fifo 26%) [buf 98%] 19.4x. Track 01: 4 of 49 MB written (fifo 100%) [buf 80%] 16.0x. Track 01: 5 of 49 MB written (fifo 100%) [buf 97%] 24.2x. Track 01: 6 of 49 MB written (fifo 100%) [buf 97%] 18.9x. Track 01: 7 of 49 MB written (fifo 100%) [buf 97%] 19.6x. Track 01: 8 of 49 MB written (fifo 100%) [buf 97%] 19.0x. Track 01: 9 of 49 MB written (fifo 100%) [buf 97%] 19.7x. Track 01: 10 of 49 MB written (fifo 100%) [buf 98%] 19.3x. Track 01: 11 of 49 MB written (fifo 98%) [buf 98%] 19.8x. Track 01: 12 of 49 MB written (fifo 98%) [buf 97%] 19.2x. Track 01: 13 of 49 MB written (fifo 100%) [buf 97%] 19.9x. Track 01: 14 of 49 MB written (fifo 100%) [buf 97%] 19.3x. Track 01: 15 of 49 MB written (fifo 100%) [buf 97%] 20.0x. Track 01: 16 of 49 MB written (fifo 100%) [buf 97%] 19.4x. Track 01: 17 of 49 MB written (fifo 100%) [buf 97%] 20.1x. Track 01: 18 of 49 MB written (fifo 100%) [buf 98%] 19.6x. Track 01: 19 of 49 MB written (fifo 100%) [buf 98%] 20.1x. Track 01: 20 of 49 MB written (fifo 100%) [buf 97%] 19.5x. Track 01: 21 of 49 MB written (fifo 100%) [buf 97%] 20.2x. Track 01: 22 of 49 MB written (fifo 100%) [buf 97%] 19.6x. Track 01: 23 of 49 MB written (fifo 100%) [buf 97%] 20.3x. Track 01: 24 of 49 MB written (fifo 100%) [buf 97%] 19.7x. Track 01: 25 of 49 MB written (fifo 100%) [buf 97%] 20.4x. Track 01: 26 of 49 MB written (fifo 100%) [buf 98%] 19.9x. Track 01: 27 of 49 MB written (fifo 100%) [buf 98%] 20.5x. Track 01: 28 of 49 MB written (fifo 100%) [buf 97%] 19.8x. Track 01: 29 of 49 MB written (fifo 100%) [buf 95%] 19.9x. Track 01: 30 of 49 MB written (fifo 100%) [buf 97%] 20.5x. Track 01: 31 of 49 MB written (fifo 100%) [buf 97%] 20.6x. Track 01: 32 of 49 MB written (fifo 100%) [buf 97%] 20.0x. Track 01: 33 of 49 MB written (fifo 100%) [buf 98%] 20.8x. Track 01: 34 of 49 MB written (fifo 100%) [buf 98%] 21.3x. Track 01: 35 of 49 MB written (fifo 100%) [buf 97%] 20.7x. Track 01: 36 of 49 MB written (fifo 100%) [buf 97%] 21.4x. Track 01: 37 of 49 MB written (fifo 100%) [buf 97%] 20.8x. Track 01: 38 of 49 MB written (fifo 100%) [buf 97%] 21.5x. Track 01: 39 of 49 MB written (fifo 98%) [buf 97%] 20.8x. Track 01: 40 of 49 MB written (fifo 100%) [buf 97%] 21.6x. Track 01: 41 of 49 MB written (fifo 100%) [buf 98%] 21.1x. Track 01: 42 of 49 MB written (fifo 100%) [buf 98%] 21.7x. Track 01: 43 of 49 MB written (fifo 100%) [buf 97%] 21.0x. Track 01: 44 of 49 MB written (fifo 98%) [buf 97%] 21.7x. Track 01: 45 of 49 MB written (fifo 100%) [buf 97%] 6.5x. Track 01: 46 of 49 MB written (fifo 100%) [buf 96%] 21.6x. Track 01: 47 of 49 MB written (fifo 100%) [buf 93%] 20.5x. Track 01: 48 of 49 MB written (fifo 100%) [buf 98%] 22.9x. Track 01: 49 of 49 MB written (fifo 100%) [buf 97%] 21.2x. Track 01: Total bytes read/written: 52162560/52162560 (25470 sectors). Writing time: 61.046s Average write speed 12.3x. Min drive buffer fill was 80% Fixating... Fixating time: 5.497s /usr/bin/X11/wodim: fifo had 822 puts and 822 gets. /usr/bin/X11/wodim: fifo was 1 times empty and 647 times full, min fill was 0%. cdrecord command: ----------------------- /usr/bin/X11/wodim -v gracetime=2 dev=/dev/sr0 speed=32 -dao driveropts=burnfree -eject -data -tsize=25470s - -- Enjoy your time around, Oddball (Now or never...) OS: Linux 2.6.25.9-3-default x86_64 Current user: oddball@AMD64x2-sfn1 System: openSUSE 11.0.42 (x86_64) Alpha0 KDE: 4.00.85 (KDE 4.0.85 (KDE 4.1 >= 20080703) "release 3.3" --------------------------------------------------------------------- To unsubscribe, e-mail: opensuse-factory+unsubscribe@opensuse.org For additional commands, e-mail: opensuse-factory+help@opensuse.org
Am Mittwoch, 16. Juli 2008 schrieb Oddball:
[...] Now it worked for the KDE3 version After 'getfacl', i did not reboot the box..(thought it would save the changes imediately.)
getfacl does not change anyting! In contrast to setfacl that would be able to change acl.
The output is from the KDE3 version, KDE4 version still has 'device write-protected' problem.
System ----------------------- K3b Version: 1.0.5 [...]
Such a debug output of the KDE4 version of k3b would be much more helpful, IMHO. Gruß Jan -- Standing in the middle of the road is very dangerous, you get knocked down by the traffic from both sides. --------------------------------------------------------------------- To unsubscribe, e-mail: opensuse-factory+unsubscribe@opensuse.org For additional commands, e-mail: opensuse-factory+help@opensuse.org
participants (5)
-
Carlos E. R. -
Dave Plater -
Jan Ritzerfeld -
Oddball -
Rajko M.