Bug 182768 - K3B CD writer /dev/sr1 works read-only
Summary: K3B CD writer /dev/sr1 works read-only
Status: RESOLVED FIXED
Alias: None
Product: SUSE Linux 10.1
Classification: openSUSE
Component: KDE (show other bugs)
Version: Final
Hardware: x86 SuSE Linux 10.1
: P5 - None : Normal (vote)
Target Milestone: ---
Assignee: Stephan Binner
QA Contact: E-mail List
URL:
Whiteboard:
Keywords:
Depends on:
Blocks: 184249
  Show dependency treegraph
 
Reported: 2006-06-08 10:02 UTC by Slawek Ligus
Modified: 2007-04-05 11:53 UTC (History)
4 users (show)

See Also:
Found By: Customer
Services Priority:
Business Priority:
Blocker: ---
Marketing QA Status: ---
IT Deployment: ---


Attachments
FSTAB (1.06 KB, application/octet-stream)
2006-06-08 10:04 UTC, Slawek Ligus
Details
y2log from affected machine (309.18 KB, application/gzip)
2006-06-08 10:05 UTC, Slawek Ligus
Details
Full hwinfo (177.19 KB, text/plain)
2006-06-08 10:05 UTC, Slawek Ligus
Details

Note You need to log in before you can comment on or make changes to this bug.
Description Slawek Ligus 2006-06-08 10:02:58 UTC
Customer cannot write data on CDs with k3b. Program
sees CD writer /dev/sr1 as a read-only device. 

Manual edition by "add device" gives error msg:
"Could not find an additional device at /dev/sr1"
 
It is possible to burn a cd with cdrecord and xcdroast

sginfo -l output:
/dev/sr1 /dev/sr0 /dev/sda
/dev/sg0 [=/dev/sda  scsi0 ch=0 id=0 lun=0]
/dev/sg1 [=/dev/sr0  scsi0 ch=0 id=1 lun=0]
/dev/sg2 [=/dev/sr1  scsi1 ch=0 id=1 lun=0]

cdrecord -scanbus:
Cdrecord-Clone 2.01 (i686-suse-linux) Copyright (C) 1995-2004 Jörg Schilling
Note: This version is an unofficial (modified) version
Note: and therefore may have bugs that are not present in the original.
Note: Please send bug reports or support requests to
http://bugs.opensuse.org/
Note: The author of cdrecord should not be bothered with problems in
this version.
Linux sg driver version: 3.5.33
Using libscg version 'schily-0.8'.
cdrecord: Warning: using inofficial libscg transport code version
(okir@suse.de-scsi-linux-sg.c-1.83-resmgr-patch '@(#)scsi-linux-sg.c
1.83 04/05/20 Copyright 1997 J. Schilling').
scsibus0:
       0,0,0     0) 'IBM     ' 'DDYS-T36950N    ' 'S93E' Disk
       0,1,0     1) 'PIONEER ' 'DVD-ROM DVD-305 ' '1.03' 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) *
scsibus1:
       1,0,0   100) *
       1,1,0   101) 'YAMAHA  ' 'CRW2100S        ' '1.0H' Removable CD-ROM
       1,2,0   102) *
       1,3,0   103) *
       1,4,0   104) *
       1,5,0   105) *
       1,6,0   106) *
       1,7,0   107) *

---
Including /etc/fstab, y2log, full hwinfo.txt
Comment 1 Slawek Ligus 2006-06-08 10:04:24 UTC
Created attachment 87924 [details]
FSTAB
Comment 2 Slawek Ligus 2006-06-08 10:05:08 UTC
Created attachment 87927 [details]
y2log from affected machine
Comment 3 Slawek Ligus 2006-06-08 10:05:41 UTC
Created attachment 87928 [details]
Full hwinfo
Comment 4 Hartmut Meyer 2006-06-08 10:18:13 UTC
I don't know how k3b handles SCSI devices, but /dev/srX are by definition read-only devices. It might be that /dev/sgX must be used instead. Like /dev/sg1 instead of /dev/sr1
Comment 5 Ulrich Hiller 2006-06-08 12:29:57 UTC
>I don't know how k3b handles SCSI devices, but /dev/srX are by definition
>read-only devices. It might be that /dev/sgX must be used instead. Like
>/dev/sg1 instead of /dev/sr1

This is a bit confusing with /dev/sr* and /dev/sg*.
I open the k3b setup and see under the devices:
YAMAHA CRW2100S     /dev/sr1
YAMAHA CRW2100S     /dev/sg2
So, k3b seems to recognize the CD-RW under both devices: /dev/sr1 AND /dev/sg2
But in the configure menu "devices" it is only /dev/sr1

When I try under 'configure' 'add device ...' to add /dev/sg2 I get "Could not find an additional device at /dev/sg2".

Is there a way to add/change devices under k3b?
Comment 6 Hartmut Meyer 2006-06-08 12:45:50 UTC
I cannot test this with SCSI devices (I don't have any). But in the k3b configure ("k3b einrichten ...") dialoge you can "add device" ("Gerät hinzufügen ...").

Try with /dev/sg1

Again: it might be that k3b claims to use the /dev/srX devices in order to make it easier to understand for the average user (many don't know about /dev/sgX) even when it really is using the corresponding /dev/sgX device file instead.

Does your YAMAHA CRW2100S work with k3b in SUSE Linux 10.1?
Comment 7 Ulrich Hiller 2006-06-08 13:00:54 UTC
> I cannot test this with SCSI devices (I don't have any). 

I can do it for you if you tell me what to do ....


> But in the k3b configure ("k3b einrichten ...") dialoge you can "add device" >("Gerät hinzufügen ...").
>
> Try with /dev/sg1

I get the message: "Could not find an additional device at /dev/sg1"

>Again: it might be that k3b claims to use the /dev/srX devices in order to make
>it easier to understand for the average user (many don't know about /dev/sgX)
>even when it really is using the corresponding /dev/sgX device file instead.

The question is how I can switch it without getting the message "Could not find an additional device at ....."

> Does your YAMAHA CRW2100S work with k3b in SUSE Linux 10.1?

Only as a readonly device (in opposite to SuSE 10.0 where I could burn).
But I am, under 10.1, able to burn with cdrecord and xcdroast.


Comment 8 Hartmut Meyer 2006-06-08 13:17:18 UTC
Ulrich, what is the output of

  sginfo -l

?
Comment 9 Hartmut Meyer 2006-06-08 13:53:41 UTC
I just heard from Slawek, that you are the customer he was talking about.

Ok, so please try with

  /dev/sg2

("sginfo -l" said that /dev/sr1 -> /dev/sg2)
Comment 10 Ulrich Hiller 2006-06-08 14:00:50 UTC
'sginfo -l' gives

/dev/sr1 /dev/sr0 /dev/sda
/dev/sg0 [=/dev/sda  scsi0 ch=0 id=0 lun=0]
/dev/sg1 [=/dev/sr0  scsi0 ch=0 id=1 lun=0]
/dev/sg2 [=/dev/sr1  scsi1 ch=0 id=1 lun=0]


>Ok, so please try with
>
>  /dev/sg2

You mean adding the the device /dev/sg2 in k3b?

That gives 
"Could not find an additional device at /dev/sg2"

Or did I misunderstand you?
Comment 11 Hartmut Meyer 2006-06-08 14:08:32 UTC
Yes, that is what I meant.

And since it's not working, we can only wait for the developers (or another person with a SCSI CD/DVD writer) to give some input.

My idea about /dev/sgX instead of /dev/srX might have been wronge anyway ...

For completenes, could you please also provide us with the output of

  hwinfo --cdrom

?
Comment 12 Stephan Kulow 2006-06-08 14:12:54 UTC
I only have a SATA burner and it works just fine there ;(

Comment 13 Ulrich Hiller 2006-06-08 14:14:59 UTC
>For completenes, could you please also provide us with the output of
>
>  hwinfo --cdrom

Here it is:
15: SCSI 01.0: 10602 CD-ROM (DVD)
  [Created at block.195]
  UDI: /org/freedesktop/Hal/devices/storage_model_DVD_ROM_DVD_305
  Unique ID: twPO.QHroqGdz7c3
  Parent ID: y9as.5nOCMXDYzrE
  SysFS ID: /block/sr0
  SysFS BusID: 0:0:1:0
  SysFS Device Link: /devices/pci0000:00/0000:00:1e.0/0000:02:0a.0/host0/target0:0:1/0:0:1:0
  Hardware Class: cdrom
  Model: "PIONEER DVD-ROM DVD-305"
  Vendor: "PIONEER"
  Device: "DVD-ROM DVD-305"
  Revision: "1.03"
  Driver: "aic7xxx", "sr"
  Device File: /dev/sr0 (/dev/sg1)
  Device Files: /dev/sr0, /dev/disk/by-path/pci-0000:02:0a.0-scsi-0:0:1:0, /dev/dvd, /dev/cdrom
  Device Number: block 11:0 (char 21:1)
  Features: DVD, DVD-RW, DVD+R, DVD+RW, DVD+DL
  Drive status: no medium
  Config Status: cfg=no, avail=yes, need=no, active=unknown
  Attached to: #10 (SCSI storage controller)
  Drive Speed: 40

16: SCSI 101.0: 10602 CD-ROM (CD-R)
  [Created at block.195]
  UDI: /org/freedesktop/Hal/devices/storage_model_CRW2100S
  Unique ID: K6gS.Tb70yy1EXKB
  Parent ID: BVjG.WsvlrmNH3M8
  SysFS ID: /block/sr1
  SysFS BusID: 1:0:1:0
  SysFS Device Link: /devices/pci0000:00/0000:00:1e.0/0000:02:0d.0/host1/target1:0:1/1:0:1:0
  Hardware Class: cdrom
  Model: "YAMAHA CRW2100S"
  Vendor: "YAMAHA"
  Device: "CRW2100S"
  Revision: "1.0H"
  Driver: "aic7xxx", "sr"
  Device File: /dev/sr1 (/dev/sg2)
  Device Files: /dev/sr1, /dev/disk/by-path/pci-0000:02:0d.0-scsi-0:0:1:0, /dev/cdrecorder
  Device Number: block 11:1 (char 21:2)
  Features: CD-R, CD-RW
  Drive status: no medium
  Config Status: cfg=no, avail=yes, need=no, active=unknown
  Attached to: #12 (SCSI storage controller)
  Drive Speed: 40
Comment 14 Forgotten User RlXLgpWK5h 2006-06-17 17:17:09 UTC
I can second this bug. I have the same CD-R Writer and the same Problem!
Comment 15 Forgotten User RlXLgpWK5h 2006-06-17 21:40:46 UTC
sorry .. i have
Vendor_info    : 'YAMAHA  '
Identifikation : 'CRW4260         '
Revision       : '1.0j'
Device seems to be: Generic mmc CD-RW.

worked find under 10.0 ... only recognized as a reader with k3b (on /dev/sr0)
when trying to add /dev/sg0 manually, this does not work... X-CD-Roast also detects the writer not automatically but when adding as /dev/sg0 manually it works

hopefully someone will fix this bug soon, otherwise i must either downgrade to 10.0 or buy new hardware :(
Comment 16 Forgotten User RlXLgpWK5h 2006-09-13 12:04:54 UTC
okay.. this was not suses fault... i talked to developer of k3b and it is fixed in newer versions...

i am using k3b 0.12.17 now, and burning with my yamah scsi writer works fine :-)
Comment 17 Sebastian Trueg 2007-02-16 10:03:02 UTC
Will there be an updated k3b in suse 10.1? Can this bug be closed or do we need a patch?
Comment 18 Stephan Binner 2007-04-05 11:53:36 UTC
I don't think that we will make an online update for k3b on 10.1 anymore (except a security problem for it occurs). Feel free to attach a patch/mention the revision which fixed it for his case though.

PS: the latest k3b version 1.0 is available in the KDE build service project at http://software.opensuse.org/download/KDE:/Backports/SUSE_Linux_10.1/