Bug 124258 - K3B doesn't get scsi devices
Summary: K3B doesn't get scsi devices
Status: RESOLVED FIXED
Alias: None
Product: k3b
Classification: Applications
Component: general (show other bugs)
Version: unspecified
Platform: unspecified Linux
: NOR normal
Target Milestone: ---
Assignee: Sebastian Trueg
URL:
Keywords:
Depends on:
Blocks:
 
Reported: 2006-03-25 20:34 UTC by Norbert Pfistner
Modified: 2006-04-09 00:39 UTC (History)
0 users

See Also:
Latest Commit:
Version Fixed In:


Attachments

Note You need to log in before you can comment on or make changes to this bug.
Description Norbert Pfistner 2006-03-25 20:34:42 UTC
Version:           0.12.12 (using KDE 3.5.1, Debian Package 4:3.5.1-2 (testing/unstable))
Compiler:          Target: i486-linux-gnu 
OS:                Linux

I tried running k3b with Linux (i686) release 2.6.15-1-686 but it took a long time to scan the devices and it didn't get my scsi devices: a cdrom and a cdburner. Both LED's on the devices flickered some times during the search while the splash scren was displayed. So at least I guess the devices have been scanned but not detected correctly.
After that only my IDE cdrom was in the device list and my scsi devices where missing. Adding the scsi devices manually with the configuration failed also.

I tried running K3B as root with the same result -- just to make sure that it was not a problem with permissions.

So I rebooted my machine with the "old" kernel:
Running Linux (i686) release 2.6.12-1-686 everything works fine as it did before installing the new kernel. 

This bug seems to be related to bug ID 117693.

Maybe it helps to say that neither cdrdao nor cdrecord seems to have problems with the 2.6.15 kernel.
Comment 1 gio_ors_67 2006-04-08 11:22:44 UTC
the same for me with 2.6.16:

SCSI DVD & CD-RW attached on adaptec 2904 (AIC7xxx module)
-------------------
starting k3b with kernel 2.6.16:
on splash screen 

 (scsi0:A:0:0): No or incomplete CDB sent to device.
 scsi0: Issued Channel A Bus Reset. 1 SCBs aborted
 (scsi0:A:0:0): Unexpected busfree in Message-out phase
 SEQADDR == 0x167
 (scsi0:A:1:0): No or incomplete CDB sent to device.
 scsi0: Issued Channel A Bus Reset. 1 SCBs aborted
 (scsi0:A:1:0): No or incomplete CDB sent to device.
 scsi0: Issued Channel A Bus Reset. 1 SCBs aborted
 (scsi1:A:0:0): No or incomplete CDB sent to device.
 (scsi1:A:0:0): Protocol violation in Message-in phase.  Attempting to abort.
 (scsi1:A:0:0): Abort Tag Message Sent
 (scsi1:A:0:0): SCB 25 - Abort Tag Completed.
 (scsi1:A:0:0): No or incomplete CDB sent to device.
 (scsi1:A:0:0): Protocol violation in Message-in phase.  Attempting to abort.
 (scsi1:A:0:0): Abort Tag Message Sent
 (scsi1:A:0:0): SCB 28 - Abort Tag Completed.
 (scsi1:A:2:0): No or incomplete CDB sent to device.
 scsi1: Issued Channel A Bus Reset. 1 SCBs aborted
 (scsi1:A:2:0): No or incomplete CDB sent to device.
 scsi1: Issued Channel A Bus Reset. 1 SCBs aborted 

many times on \var\log messages, and

k3b: ERROR: (K3bDevice::Device) Unable to do inquiry.

many times on console.

finally k3b starts but no device is detected

k3b 0.12.14

cdrecord --scanbus works fine
Comment 2 Sebastian Trueg 2006-04-09 00:38:58 UTC
will be fixed in 0.12.15.
the kernel guys simply disabled functionality which was used by k3b...
Comment 3 Sebastian Trueg 2006-04-09 00:39:09 UTC
*** Bug has been marked as fixed ***.