Hi, I have just installed a new LG cd writer into this machine, and was having trouble burning with it. I am running Red Hat 9 Kernel 2.4.20-8. Blanking works fine, heres what i get when I try to burn:

[root@localhost root]# cdrecord -v dev=0,0,0 -data backupimage

........

Starting to write CD/DVD at speed 4 in real TAO mode for single session.
Last chance to quit, starting real write 0 seconds. Operation starts.
Waiting for reader process to fill input buffer ... input buffer ready.
BURN-Free is OFF.
Performing OPC...
cdrecord: Input/output error. read track info: scsi sendcmd: no error
CDB: 52 01 00 00 00 FF 00 00 1C 00
status: 0x2 (CHECK CONDITION)
Sense Bytes: 70 00 05 00 00 00 00 0A 00 00 00 00 30 06 00 00
Sense Key: 0x5 Illegal Request, Segment 0
Sense Code: 0x30 Qual 0x06 (cannot format medium - incompatible medium) Fru 0x0
Sense flags: Blk 0 (not valid)
cmd finished after 0.000s timeout 240s
Writing time: 0.231s
Average write speed 999.0x.
Fixating...
Fixating time: 0.001s
cdrecord: fifo had 64 puts and 0 gets.
cdrecord: fifo was 0 times empty and 0 times full, min fill was 100%.

thanks in advance for any help..

Are you sure that's your device? cdrecord --scanbus to check. Haven't seen a 0,0,0 device before, but anythign's possible. You will also want to specify generic-mmc-raw mode when writing. I also have a LG drive.

The rest of the errors look like the data you are trying to write isn't there or isn't in the right format. I dunno, but do the previous stuff first when diagnosing.

cdrecord: Input/output error. read track info: scsi sendcmd: no error

Sense Code: 0x30 Qual 0x06 (cannot format medium - incompatible medium) Fru 0x0

The format medium is the CD-R/RW. Sounds like a problem with the CD disk. Do you get the same error message when trying to burn on to other disks?

You maybe trying to access the wrong device.

Have you set up your /etc/cdrecord/cdrecord file something like this
(obviously using the correct values for your drive).

#*****************************************************************************#
#
# file : /etc/cdrecord/cdrecord
#
#*---------------------------------------------------------------------------*#
#
CDR_DEVICE="HP CD-Writer+ 8200"
#
CDR_SPEED=4
#
CDR_FIFOSIZE=2m
#
#.............................................................................#
#
# drive name device speed fifosize driveropts
#
"HP CD-Writer+ 8200"= 0,0,0 4 2m ""
#
#*****************************************************************************#

I am pretty sure I am using the right media because Windows has no problems writing to it, and I have actually burned twice successfully from Linux before. (dont know what I did differently, same command). Using -scanbus, the device number is correct, and blanking a CDRW always worked. This is a resent error I got trying to burn. If it helps, the burner is a primary slave and there is a secondary slave cd drive attached.


Track 01: 0 of 139 MB written.cdrecord: Input/output error. write_g1: scsi sendcmd: no error
CDB: 2A 00 00 00 00 00 00 00 1F 00
status: 0x2 (CHECK CONDITION)
Sense Bytes: 70 00 04 00 00 00 00 0A 00 00 00 00 08 03 00 00
Sense Key: 0x4 Hardware Error, Segment 0
Sense Code: 0x08 Qual 0x03 (logical unit communication crc error (ultra-dma/32)) Fru 0x0
Sense flags: Blk 0 (not valid)
cmd finished after 0.005s timeout 40s

write track data: error after 0 bytes
Sense Bytes: 70 00 00 00 00 00 00 0A 00 00 00 00 00 00 00 00 00 00
Writing time: 10.959s
Average write speed 87.7x.
Fixating...
Fixating time: 80.472s
cdrecord: fifo had 64 puts and 1 gets.
cdrecord: fifo was 0 times empty and 0 times full, min fill was 100%.

Here is the output of -scanbus. The device is now 1,0,0 after I connected a USB card reader, still no luck burnin with dev=1,0,0 though.
As far as the /etc/cdrecord.conf file, for some reason its comming up as a YAMAHA drive which is weird. Could it be using the same modules??
AsCdrecord 2.0 (i686-pc-linux-gnu) Copyright (C) 1995-2002 J�g
Using libscg version 'schily-0.7'
scsibus0:
0,0,0 0) 'SanDisk ' 'ImageMate CF-SD1' '0100' Removable Disk
0,1,0 1) *
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) 'HL-DT-ST' 'CD-RW GCE-8520B ' '1.02' Removable CD-ROM
1,1,0 101) *
1,2,0 102) *
1,3,0 103) *
1,4,0 104) *
1,5,0 105) *
1,6,0 106) *
1,7,0 107) *

Just went through the syslogs and found this mess:

I/O error: dev 0b:00, sector 233500
SCSI cdrom error : host 1 channel 0 id 0 lun 0 return code = 28000000
Current sd0b:00: sense key Hardware Error
Additional sense indicates Logical unit communication CRC error (Ultra-DMA/32)
I/O error: dev 0b:00, sector 1248
SCSI cdrom error : host 1 channel 0 id 0 lun 0 return code = 28000000
Current sd0b:00: sense key Hardware Error
Additional sense indicates Logical unit communication CRC error (Ultra-DMA/32)
I/O error: dev 0b:00, sector 1024
UDF-fs DEBUG misc.c:274:udf_read_tagged: block=256, location=256: read failed
UDF-fs DEBUG super.c:1211:udf_load_partition: No Anchor block found
UDF-fs: No partition found (1)
SCSI cdrom error : host 1 channel 0 id 0 lun 0 return code = 28000000
Current sd0b:00: sense key Hardware Error
Additional sense indicates Logical unit communication CRC error (Ultra-DMA/32)
I/O error: dev 0b:00, sector 64
isofs_read_super: bread failed, dev=0b:00, iso_blknum=16, block=16



much much much longer than this though.

I have 2 machines one with a Yamaha CRW-F1E with the 2@tattoo and I also have a sony CRX215E5 drive and I have tried X-CD-Roast, KonCD and GNOME Toaster and I get the same stuff as listed in the top message.
I have tried TDK 2X/4X and I then tried memorex 700mb 80min multi speed cdrw media that goes up to 12X. guess what no go. I then went and found as many web pages and wrote a letter to a person of one of them about this.
Now one thing I will also note that when I used GNOME TOASTER it popped up a web page to check for drivers. cdrado.sourceforge.net/drivers do a search on this as its an HTML page thing. Keep you posted.

Can you succeed using the command line?

# CD burning info
Is it configured and what is the device? Command this to find out:
cdrecord -scanbus
Adding an IDE CD-Writer to Linux
CD Writing HOWTO
Burning CDs on Linux

# Burn an ISO to disk
cdrecord -v speed=<burning speed> dev=<your device> /path/to/foo.iso
# Burn from disk to disk
cdrecord -v dev=<your device> speed=<burning speed> -isosize /dev/cdrom
# Generate an ISO from a directory.
mkisofs -Jr -o foo.iso /path/to/directory
mkisofs -vrTJUV "Label" -o foo.iso /path/to/directory
# Generate an ISO from a CD
dd if=/dev/cdrom of=foo.iso
Linux MP3 CD Burning mini-HOWTO
# Convert mp3 to wav with lame
for i in *.mp3; do lame --decode $i `basename $i .mp3`.wav; done
# Burn a CD from wav files
cdrecord -v -audio -pad speed=<burning speed> dev=<your device> /path/to/*.wav
# Erase a CDRW
cdrecord -v dev=<your device> speed=<burning speed> blank=fast

When I run the cdrecord --scanbus it comes up just like it should in my redhat book as scsibus 0,0,0 Pioneer DVD-RW DVR-105 1.21 removable CD-ROM
the next one 0,1,0 1)Yamaha CRW-F1E 1.0c Removable CD-ROM.
What I'm trying to do is learn this O/S from both the command prompt and the GUI. I did blank the CDRW in windows XP on the Yamaha with no problem and put a jpg image on it and then pull it up just fine in REDHAT 8.0 but for trying to get it to blank the CDRW not. It comes up with -tfs bad block something iso9660 ,kudzu,noauto. I haven't tried the command line yet. But I might just do it again for aggervation and post the info that it spits out after it finishes.

Be in touch.

I have also tried GTOASTER and recieved the exact same error message I did when using command line. This led me to believe that GTOASTER is jsut a graphical interface of CDRECORD and not a different program.

How do you mean "its coming up as" ?

Why have you not edited this file and put in the appropriate values for your drived, as suggested in an earlier posting?

Well I did now, without better results... as I understand it (i could be wrong) it will only read from that file as long as i dont specify a device in the cdrecord command line, which I did.

I think it is safe to assume that you do not have an SMP system,
and that if you did have an SMP system you were not booting it with
an SMP kernel.

So the question that needs to be asked, are you booting a kernel
with APIC support (either compiled in or as a module)?

Corin: me being a newb, I have absolutely no Idea what SMP or APIC means. I didnt even compile the kernel myself, Just installed Red Hat and it detected the drive and did all the SCSI emulation.