Your message dated Wed, 06 Feb 2008 01:00:31 +0100
with message-id <[EMAIL PROTECTED]>
and subject line bug probably solved
has caused the attached Bug report to be marked as done.
This means that you claim that the problem has been dealt with.
If this is not the case it is now your responsibility to reopen the
Bug report if necessary, and/or fix the problem forthwith.
(NB: If you are a system administrator and have no idea what I am
talking about this indicates a serious mail system misconfiguration
somewhere. Please contact me immediately.)
Debian bug tracking system administrator
(administrator, Debian Bugs database)
--- Begin Message ---
Package: cdw
Version: 0.3.3-2
Severity: normal
--- Please enter the report below this line. ---
I have external CDRW driver for USB. Dmesg gives:
scsi 3:0:0:0: CD-ROM Slimtype DVDRW SOSW-852S PSX3 PQ: 0 ANSI: 0
sr0: scsi3-mmc drive: 24x/24x writer cd/rw xa/form2 cdda tray
sr 3:0:0:0: Attached scsi CD-ROM sr0
sr 3:0:0:0: Attached scsi generic sg0 type 5
This gives me not enough helpfull informations. But K3B starts and is working
with this drive
seamlessly without problems. On the start of K3B in terminal is shown:
...
/dev/scd0 resolved to /dev/scd0
/dev/scd0 is block device (0)
/dev/scd0 seems to be cdrom
bus: 3, id: 0, lun: 0
(K3bDevice::Device) /dev/scd0: init()
(K3bDevice::Device) /dev/scd0 feature: CD Mastering
(K3bDevice::Device) /dev/scd0 feature: CD Track At Once
(K3bDevice::Device) /dev/scd0 feature: DVD+R
(K3bDevice::Device) /dev/scd0 feature: DVD+RW
(K3bDevice::Device) /dev/scd0 feature: DVD+R Double Layer
(K3bDevice::Device) /dev/scd0 feature: DVD-R/-RW Write
(K3bDevice::Device) /dev/scd0 feature: Rigid Restricted Overwrite
(K3bDevice::Device) /dev/scd0: dataLen: 60
(K3bDevice::Device) /dev/scd0: checking for TAO
(K3bDevice::Device) /dev/scd0: checking for SAO
(K3bDevice::Device) /dev/scd0: checking for SAO_R96P
(K3bDevice::Device) /dev/scd0: checking for SAO_R96R
(K3bDevice::Device) /dev/scd0: checking for RAW_R16
(K3bDevice::Device) /dev/scd0: checking for RAW_R96P
(K3bDevice::Device) /dev/scd0: checking for RAW_R96R
(K3bDevice::DeviceManager) setting current write speed of device /dev/scd0 to
2822
....
Could not resolve /dev/scd1
/dev/scd1 resolved to /dev/scd1
(K3bDevice::Device) could not open device /dev/scd1 for reading
(No such file or directory)
could not open device /dev/scd1 (No such file or directory)
(K3bDevice::DeviceManager) found config entry for devicetype: MATSHITA DVD-ROM
SR-8177
(K3bDevice::DeviceManager) found config entry for devicetype: Slimtype DVDRW
SOSW-852S
DiskInfo:
Mediatype: CD-RW
Current Profile: CD-RW
Disk state: empty
Empty: 1
Rewritable: 1
Appendable: 0
Sessions: 0
Tracks: 0
Layers: 1
Capacity: 79:57:74 (LBA 359849) (736970752 Bytes)
Remaining size: 79:57:74 (LBA 359849) (736970752 Bytes)
Used Size: 00:00:00 (LBA 0) (0 Bytes)
(K3bDevice::Device) /dev/scd0: Number of supported write speeds via 2A: 2
(K3bDevice::Device) /dev/scd0 : 2822 KB/s
(K3bDevice::Device) /dev/scd0 : 1764 KB/s
...
So I think the right setting is:
SCSI device: 3,0,0
CD Reader/Wirter: /dev/scd0 (there is TYPO by the way)
But with this settings wenn I try to write an image, it is immediatelly done
and after "pressing any
key" is ejected drive tray from my internal CD Drive. Not from this external
USB drive. And nothing
is done on external drive.
--- System information. ---
Architecture: i386
Kernel: Linux 2.6.23-1-686
Debian Release: lenny/sid
600 testing www.debian-multimedia.org
600 testing gd.tuwien.ac.at
500 unstable gd.tuwien.ac.at
400 stable security.debian.org
--- Package information. ---
Depends (Version) | Installed
====================================-+-====================
genisoimage | 9:1.1.6-1
libc6 (>= 2.7-1) | 2.7-6
libcdio7 | 0.78.2+dfsg1-2
libncursesw5 (>= 5.6+20071006-3) | 5.6+20080105-1
wodim | 9:1.1.6-1
--- End Message ---
--- Begin Message ---
Package: cdw
Version: 0.3.3-2
--- Please enter the report below this line. ---
This problem is caused due to dependency to cdrecord instead of wodim.
After making symlink of cdrecord to wodim I have discovered other problems. I
have described them in
Bug #464234.
I am closing this bugreport prior to the new bugreport #464234
--- End Message ---
