| View previous topic :: View next topic |
| Author |
Message |
lost+found
Guru
Joined: 15 Nov 2004
Posts: 509
Location: North~Sea~Coa~s~~t~~~
|
 Posted: Wed Feb 01, 2006 8:31 pm Post subject: K3b - can't add SCSI burner [SOLVED] |
 |
|
Is there a way to add a SCSI burner/cdrom to K3b? Cause, when I add /dev/sg0 or /dev/sr0, it says: ERRORR!!! Could not find an additional device at /dev/sg0 ... /dev/sr0. 
On the commandline I use "cdrecord dev=0,4,0": that works. Same for Arson (declared dEaD in CVS, I think they're right)... So I know it should work. I'm in all groups, rw, root etc.
Thank you so much.
Cheers.
2-2-2006: I discovered that cat gives no output as well. | Code: | sh-3.00# cat /dev/sr0
sh-3.00# |
But I can still mount any cd in the drive. Maybe there is something wrong with udev/kernel , and not k3b... 
Last edited by lost+found on Fri Sep 15, 2006 10:21 pm; edited 2 times in total |
|
| Back to top |
|
 |
coco-loco
Apprentice
Joined: 30 Oct 2005
Posts: 249
|
| Posted: Thu Feb 02, 2006 1:34 pm Post subject: |
|
|
If I remember that right, I stumbled over a post lately that mentioned a bug in k3b that leads into such a problem with recent kernels, but I can't remember where it was (Actually I looked for something else at this time).
Have a look in the bug-list on the k3b-homepage, maybe that helps.
_________________
In 2007 Windows will come with command-line tools - an attempt to behave like a real OS? |
|
| Back to top |
|
|
lost+found
Guru
Joined: 15 Nov 2004
Posts: 509
Location: North~Sea~Coa~s~~t~~~
|
| Posted: Thu Feb 02, 2006 2:01 pm Post subject: |
|
|
coco-loco, thanks for the tip. i'll try to find the info...
3-2-2006: It feels like this is a kernel issue. Not fixed in gentoo-sources-2.6.15-r2...
Djeez, what a mess 
| Code: | sh-3.00# k3b: ERROR: (K3bDevice::Device) Unable to do inquiry.
k3b: ERROR: (K3bDevice::Device) Unable to do inquiry.
k3b: ERROR: (K3bDevice::Device) Unable to do inquiry.
k3b: ERROR: (K3bDevice::Device) Unable to do inquiry.
k3b: ERROR: (K3bDevice::Device) Unable to do inquiry.
k3b: ERROR: (K3bDevice::Device) Unable to do inquiry.
k3b: ERROR: (K3bDevice::Device) Unable to do inquiry.
k3b: ERROR: (K3bDevice::Device) Unable to do inquiry.
k3b: ERROR: (K3bDevice::Device) Unable to do inquiry.
k3b: ERROR: (K3bDevice::Device) Unable to do inquiry.
k3b: ERROR: (K3bDevice::Device) Unable to do inquiry.
k3b: ERROR: (K3bDevice::Device) Unable to do inquiry.
k3b: ERROR: (K3bDevice::Device) Unable to do inquiry.
k3b: ERROR: (K3bDevice::Device) Unable to do inquiry.
sh-3.00# dmesg
<snip>
ACPI: PCI Interrupt Link [LNKA] enabled at IRQ 5
PCI: setting IRQ 5 as level-triggered
ACPI: PCI Interrupt 0000:00:04.0[A] -> Link [LNKA] -> GSI 5 (level, low) -> IRQ 5
ahc_pci:0:4:0: Host Adapter Bios disabled. Using default SCSI device parameters
scsi0 : Adaptec AIC7XXX EISA/VLB/PCI SCSI HBA DRIVER, Rev 7.0
<Adaptec 2902/04/10/15/20C/30C SCSI adapter>
aic7850: Single Channel A, SCSI Id=7, 3/253 SCBs
Vendor: YAMAHA Model: CRW6416S Rev: 1.0d
Type: CD-ROM ANSI SCSI revision: 02
target0:0:4: Beginning Domain Validation
target0:0:4: FAST-10 SCSI 10.0 MB/s ST (100 ns, offset 15)
target0:0:4: Domain Validation skipping write tests
target0:0:4: Ending Domain Validation
sr0: scsi3-mmc drive: 16x/16x writer cd/rw xa/form2 cdda tray
sr 0:0:4:0: Attached scsi CD-ROM sr0
sr 0:0:4:0: Attached scsi generic sg0 type 5
<snip>
Device not ready. Make sure there is a disc in the drive.
Device not ready. Make sure there is a disc in the drive.
Device not ready. Make sure there is a disc in the drive.
Device not ready. Make sure there is a disc in the drive.
Device not ready. Make sure there is a disc in the drive.
(scsi0:A:4:0): No or incomplete CDB sent to device.
scsi0: Issued Channel A Bus Reset. 1 SCBs aborted
(scsi0:A:4:0): No or incomplete CDB sent to device.
scsi0: Issued Channel A Bus Reset. 1 SCBs aborted
(scsi0:A:4:0): No or incomplete CDB sent to device.
scsi0: Issued Channel A Bus Reset. 1 SCBs aborted
sr 0:0:4:0: SCSI error: return code = 0x70000
Device not ready. Make sure there is a disc in the drive.
(scsi0:A:4:0): No or incomplete CDB sent to device.
scsi0: Issued Channel A Bus Reset. 1 SCBs aborted
(scsi0:A:4:0): No or incomplete CDB sent to device.
scsi0: Issued Channel A Bus Reset. 1 SCBs aborted
(scsi0:A:4:0): No or incomplete CDB sent to device.
scsi0: Issued Channel A Bus Reset. 1 SCBs aborted
sr 0:0:4:0: SCSI error: return code = 0x70000
Device not ready. Make sure there is a disc in the drive.
(scsi0:A:4:0): No or incomplete CDB sent to device.
scsi0: Issued Channel A Bus Reset. 1 SCBs aborted
(scsi0:A:4:0): No or incomplete CDB sent to device.
scsi0: Issued Channel A Bus Reset. 1 SCBs aborted
(scsi0:A:4:0): No or incomplete CDB sent to device.
scsi0: Issued Channel A Bus Reset. 1 SCBs aborted
sr 0:0:4:0: SCSI error: return code = 0x70000
sh-3.00# |
|
|
| Back to top |
|
|
Polynomial-C
Retired Dev
Joined: 01 Jun 2003
Posts: 1432
Location: Germany
|
|
| Back to top |
|
|
lost+found
Guru
Joined: 15 Nov 2004
Posts: 509
Location: North~Sea~Coa~s~~t~~~
|
| Posted: Sat Feb 04, 2006 9:12 am Post subject: |
|
|
Hi,
So, this is a known bug. I guess we must be patient...
A SCSI address like 0,4,0 still works, instead of /dev files. For the moment, luckily Arson still compiles, and only needs 0,4,0... Maybe some other frontends will work this way too. |
|
| Back to top |
|
|
lost+found
Guru
Joined: 15 Nov 2004
Posts: 509
Location: North~Sea~Coa~s~~t~~~
|
| Posted: Sun Feb 12, 2006 8:34 am Post subject: |
|
|
Not fixed in 2.6.15-gentoo-r5. I wonder what those compilation warnings are about...
| Code: | sh-3.00# mount /boot; mount /mnt/backup; make && make modules_install && REL=`ls -l /usr/src/linux | sed -e 's:.*linux-\(.*\):\1:'` && cp -b arch/i386/boot/bzImage /boot/kernel-$REL && cp -b .config /boot/config-$REL && cp -b .config /mnt/backup/config-$REL
mount: /dev/hda1 already mounted or /boot busy
mount: according to mtab, /dev/hda1 is already mounted on /boot
<snip>
CC drivers/scsi/scsi.o
CC drivers/scsi/hosts.o
CC drivers/scsi/scsi_ioctl.o
CC drivers/scsi/constants.o
CC drivers/scsi/scsicam.o
CC drivers/scsi/scsi_error.o
CC drivers/scsi/scsi_lib.o
drivers/scsi/scsi_lib.c:1035: warning: 'scsi_prepare_flush_fn' defined but not used
drivers/scsi/scsi_lib.c:1050: warning: 'scsi_end_flush_fn' defined but not used
CC drivers/scsi/scsi_scan.o
CC drivers/scsi/scsi_sysfs.o
CC drivers/scsi/scsi_devinfo.o
CC drivers/scsi/scsi_sysctl.o
CC drivers/scsi/scsi_proc.o
CC drivers/scsi/sr.o
CC drivers/scsi/sr_ioctl.o
CC drivers/scsi/sr_vendor.o
LD drivers/scsi/scsi_mod.o
CC drivers/scsi/scsi_transport_spi.o
SHIPPED drivers/scsi/aic7xxx/aic7xxx_seq.h
SHIPPED drivers/scsi/aic7xxx/aic7xxx_reg.h
CC drivers/scsi/aic7xxx/aic7xxx_core.o
CC drivers/scsi/aic7xxx/aic7xxx_93cx6.o
CC drivers/scsi/aic7xxx/aic7xxx_pci.o
CC drivers/scsi/aic7xxx/aic7xxx_osm.o
drivers/scsi/aic7xxx/aic7xxx_osm.c: In function `ahc_linux_register_host':
drivers/scsi/aic7xxx/aic7xxx_osm.c:1100: warning: ignoring return value of `scsi_add_host', declared with attribute warn_unused_result
CC drivers/scsi/aic7xxx/aic7xxx_proc.o
CC drivers/scsi/aic7xxx/aic7xxx_osm_pci.o
LD drivers/scsi/aic7xxx/aic7xxx.o
LD drivers/scsi/aic7xxx/built-in.o
LD drivers/scsi/qla2xxx/built-in.o
LD drivers/scsi/sr_mod.o
CC drivers/scsi/sg.o
LD drivers/scsi/built-in.o
<snip>
|
|
|
| Back to top |
|
|
coco-loco
Apprentice
Joined: 30 Oct 2005
Posts: 249
|
| Posted: Sun Feb 12, 2006 9:15 am Post subject: |
|
|
Actually, scsi_prepare_flush_fn and scsi_end_flush_fn are warnings that happen often. These are variables that are declared in the code without being used later on. This does not really represent any problem, the compiler just displays the message and ignores them.
Ignoring the return of the function scsi_add_host however might be another cup of tea, it seems to scan the scsi devices and returns appearently a null value when there's no device at the respective port. I just had a short glance at the code, but I'm not sure if this has really an impact.
To me, it seems to be a problem related to the k3b frontend that tries to overgive a wrong value, since it works with other apps.
_________________
In 2007 Windows will come with command-line tools - an attempt to behave like a real OS? |
|
| Back to top |
|
|
lost+found
Guru
Joined: 15 Nov 2004
Posts: 509
Location: North~Sea~Coa~s~~t~~~
|
| Posted: Sun Feb 12, 2006 9:50 pm Post subject: |
|
|
Hmm. I'll keep an eye on k3b too. Not fixed in yesterday's k3b-0.12.11...
|
|
| Back to top |
|
|
steve_v
Guru
Joined: 20 Jun 2004
Posts: 388
Location: New Zealand
|
| Posted: Sat Feb 18, 2006 4:50 am Post subject: |
|
|
| Same here, only seems to occur when programs try to access the drive via HAL with kernel >2.6.13, anything that doesn't use hal works fine, and hal is okay on <2.6.14. |
|
| Back to top |
|
|
Polynomial-C
Retired Dev
Joined: 01 Jun 2003
Posts: 1432
Location: Germany
|
|
| Back to top |
|
|
steve_v
Guru
Joined: 20 Jun 2004
Posts: 388
Location: New Zealand
|
| Posted: Sat Feb 18, 2006 5:48 am Post subject: |
|
|
You may well be right. However k3b (if compiled with hal support) will still try to call hal to find drives even if hald is not running... I am now compiling kdebase & k3b without hal support.
I came (jumped) to the previous conclusion because I get these errors while trying to extract audio with k3b or kaudiocreator, yet cdda2wav (kaudiocreator's backend) works flawlessly, as do cdparanoia, cdrecord, readcd etc. (which k3b uses).
Has anyone had these errors with an app NOT linked to libhal?
Steve. |
|
| Back to top |
|
|
Polynomial-C
Retired Dev
Joined: 01 Jun 2003
Posts: 1432
Location: Germany
|
| Posted: Sat Feb 18, 2006 6:02 am Post subject: |
|
|
Hi,
maybe my previous answer was a little bit confusing. I have no hal installed at all and none of my apps is compiled with hal-support and I still get these errors with k3b and kscd when running them with kernel >=2.6.14.
| Code: | | app-cdr/k3b-0.12.12 +alsa +arts -css -debug -dvdr -encode +ffmpeg -flac -hal +kde +mp3 -musepack -musicbrainz -sndfile -vcd +vorbis -xinerama |
Cheers
Poly
_________________
The manual said "Requires Windows10 or better" so I installed GNU/Linux...
my portage overlay
Need a stage1 tarball? (Unofficial builds) |
|
| Back to top |
|
|
steve_v
Guru
Joined: 20 Jun 2004
Posts: 388
Location: New Zealand
|
| Posted: Sat Feb 18, 2006 6:06 am Post subject: |
|
|
I stand corrected.
Bugger, back to the drawing board. |
|
| Back to top |
|
|
lost+found
Guru
Joined: 15 Nov 2004
Posts: 509
Location: North~Sea~Coa~s~~t~~~
|
| Posted: Sat Feb 18, 2006 12:44 pm Post subject: |
|
|
Hey, Poly
I don't think so. I read the bug report, but my permissions are OK by default, I think. I didn't make any changes myself.
| Code: | # ls -l /dev/sg0 /dev/sr0 /dev/pktcdvd/pktcdvd0
brw-rw---- 1 root cdrw 253, 0 Feb 18 12:08 /dev/pktcdvd/pktcdvd0
crw-rw---- 1 root cdrom 21, 0 Feb 2 07:52 /dev/sg0
brw-rw---- 1 root cdrom 11, 0 Feb 2 07:52 /dev/sr0 |
I'm in group cdrom cdrw, but did try executing as root too... The burner is my *only* SCSI dev. Here cdrecord dev=0,4,0 dev=/dev/sg0 dev=/dev/sr0 is working as user and root (just retried all in -dummy blank mode).
B.t.w. UDF packet writing isn't working anymore as well, and that's a non-K3b non-cdrecord thing... | Code: | sh-3.00# cdrwtool -d /dev/sr0 -q
using device /dev/sr0
wait_cmd: Input/output error
Command failed: 5c 00 00 00 00 00 00 00 0c 00 00 00 - sense 06.28.00
sh-3.00# /sbin/mke2fs /dev/pktcdvd/sr0
mke2fs 1.38 (30-Jun-2005)
mke2fs: Input/output error while trying to determine filesystem size
sh-3.00# cat /dev/sr0
sh-3.00# |
Plus cat /dev/sr0 not working anymore (I used to check md5sums that way), this makes me think that at least there's something wrong with the kernel.
I don't know starting what versions the trouble began. I did a gcc-3.4.4-r1 upgrade last month, including 'emerge -e', recompiling all packages. Before that, I was 5 months behind on keeping up to date...
Regards.
28-02-2006 http://bugzilla.kernel.org/show_bug.cgi?id=5659
29-02-2006 All works fine again, downgrading the kernel.
Last edited by lost+found on Thu Mar 02, 2006 10:22 pm; edited 6 times in total |
|
| Back to top |
|
|
Polynomial-C
Retired Dev
Joined: 01 Jun 2003
Posts: 1432
Location: Germany
|
| Posted: Sat Feb 18, 2006 1:25 pm Post subject: |
|
|
Hi,
@lost+found: It's not mainly about the wrong permissions in that bugreport but about cdrecord looking at the wrong devicefile (/dev/sg0) when the writer is not /dev/sg0. But you're right. If you only have one SCSI-device, this would become /dev/sg0 and then cdrecord indeed looks for the correct device.
Cheers
Poly
_________________
The manual said "Requires Windows10 or better" so I installed GNU/Linux...
my portage overlay
Need a stage1 tarball? (Unofficial builds) |
|
| Back to top |
|
|
|
Desktop Environments
