[Debburn-devel] -header:Cc:jerome.avond at laposte.net

[Thomas Schmitt]

Hi,

> I was able to burn cdrom, but since yesterday i can't, k3b told me
> that cdrecord (an alias for wodim) has no permission on the device.

It would be interesting to see what wodim reports
if used directly.
Like with this command which inquires some media info
  wodim -vvv dev=/dev/sg0 -atip

Especially interesting is the question whether this
command works for the superuser.


> I'm using ubuntu gnu/linux gutsy gibbon 7.10 amd64,
> I TRIED AS ROOT TO SET THE OWNER AND GROUP OF /DEV/SG0 AND 1 TO
> root:cdrom, but it doesn't affect the process,

Did you get that address /dev/sg0 from k3b ?

I assume you are in group cdrom. What permissions do
you see with /dev/sg* and /dev/sr* ?

Would above command work for /dev/sr0 ? (With suitable
permissions set, of course.) 


-----------------------------------------------------------
Adding my own problem report:

My wodim-1.1.6 seems to be in trouble since i
migrated to a new computer.
Its scanning functions only recognize the IDE drives
but not the pseudo-SCSI ones (USB, SATA).

I recently installed SuSE 10.2, kernel 2.6.18.2-34-default.
It is not a general inability of the system. My own burn
program cdrskin can show all four drives :
  0  dev='/dev/sr0'  rwrw-- :  'TSSTcorp'  'CDDVDW SH-S203B'
  1  dev='/dev/sr1'  rwrw-- :  'PHILIPS'  'SPD3300L'
  2  dev='/dev/hda'  rwrw-- :  'HL-DT-ST'  'DVD-ROM GDR8162B'
  3  dev='/dev/hdc'  rwrw-- :  'LITE-ON'  'LTR-48125S'

The problem is reproducible with wodim-1.0pre1
provided by SuSE 10.2 and with wodim-1.1.6 compiled
from source on that same SuSE 10.2.

 $ ./wodim --devices
 ...
  0  dev='/dev/hda'      rwrw-- : 'HL-DT-ST' 'DVD-ROM GDR8162B'
  1  dev='/dev/hdc'      rwrw-- : 'LITE-ON' 'LTR-48125S'
 ...
 $ ./wodim -scanbus
 ...
 scsibus1000:
        1000,0,0 100000) 'HL-DT-ST' 'DVD-ROM GDR8162B' '0015' Removable CD-ROM
        1000,1,0 100001) *
        1000,2,0 100002) 'LITE-ON ' 'LTR-48125S      ' '1S05' Removable CD-ROM
 ...
 $ ./wodim dev=SCSI -scanbus
 ./wodim: No such file or directory. 
 Cannot open SCSI driver!
 For possible targets try 'wodim --devices' or 'wodim -scanbus'.
 ...

For a non-existent file it is quite able to
emit existing error messages :))

This looks much like a .so library linking problem.
But i have no idea which lib is missing, and it
is also not very plausible to have such a problem
with a locally compiled program.


My wodims do operate the missing drives if i guess
their addresses:
  $ ./wodim -vvv /dev/sr0 -atip
  ...
  Identification : 'CDDVDW SH-S203B '
  ...
  $ ./wodim -vvv dev=/dev/sr1 -atip
  ...
  Identification : 'SPD3300L        '
  ...
The addresses /dev/sg0 and /dev/sg2 work too
(sg1 is a SATA disk).
  
--------------------------------------------------------------------


Have a nice day :)

Thomas