LinuxQuestions.org - Using the K3B

- Linux - Software (https://www.linuxquestions.org/questions/linux-software-2/)

- - Using the K3B (https://www.linuxquestions.org/questions/linux-software-2/using-the-k3b-218818/)

Hi,
I'm having problems burning with K3B on my Gentoo Linux. I have two Teac 40X burners on a Silocon Image IDE RAID controller. The program fails to auto-detect the burning speed. If I set it manually to 40x I get a buffer underrung error and If I set it to 1x I get a cdrecord error. Here is the debug output:

Code:

System

-----------------------

K3b Version:0.11.12 

KDE Version: 3.2.3

QT Version: 3.3.2



cdrecord

-----------------------

Cdrecord-Clone 2.01a28 (i686-pc-linux-gnu) Copyright (C) 1995-2004 Jörg Schilling

TOC Type: 1 = CD-ROM

Using libscg version 'schily-0.8'.

Driveropts: 'burnfree'

scsidev: '/dev/ide/host2/bus0/target0/lun0/cd'

devname: '/dev/ide/host2/bus0/target0/lun0/cd'

scsibus: -2 target: -2 lun: -2

Warning: Open by 'devname' is unintentional and not supported.

Linux sg driver version: 3.5.27

SCSI buffer size: 0

/usr/bin/cdrecord: Invalid argument. Cannot get SCSI I/O buffer.



cdrecord comand:

-----------------------

/usr/bin/cdrecord -v gracetime=2 dev=/dev/ide/host2/bus0/target0/lun0/cd speed=4 -dao -dummy driveropts=burnfree -eject -data -tsize=358484s - 



mkisofs

-----------------------

358484



mkisofs comand:

-----------------------

/usr/bin/mkisofs -gui -graft-points -volid Queen -volset  -appid K3B THE CD KREATOR VERSION 0.11.12 (C) 2003 SEBASTIAN TRUEG AND THE K3B TEAM -publisher  -preparer K3b - Version 0.11.12 -sysid LINUX -volset-size 1 -volset-seqno 1 -sort /tmp/kde-jure/k3bY4sCjb.tmp -rational-rock -hide-list /tmp/kde-jure/k3byBTj6a.tmp -full-iso9660-filenames -iso-level 2 -path-list /tmp/kde-jure/k3bsqs5ib.tmp

So what should I do? Is there perhaps something I missed when I compiled my 2.6.7 kernel?

George

Re: Using the K3B

Quote:

Originally posted by george_mercury
I have two Teac 40X burners on a Silocon Image IDE RAID controller.

That's probably your problem right there. The RAID controller is no doubt messing it up.
RAID controllers are designed for hard drives, not CD burners.

Try the burners on IDE, and see if it works.

Well, it is not a RAID-only controller. I have disabled raid in bios, so it should act as a normal IDE controller. Anyway, it works well in Windows, so I don't see why it shouldn't in Linux.

Any other ideas?

Quote:

Originally posted by george_mercury
I have disabled raid in bios, so it should act as a normal IDE controller.

Not necessarily. Linux usually ignores the BIOS, so unless you disabled it via module parameters or something else, it's just another RAID controller to Linux. Windows uses the BIOS which would explain why it works there.