ATAPI Burning: No Disk / Wrong Disk!

[spoonfork]

While trying to burn ISO images, I always get the folllowing:

Code: Select all

Cdrecord-Clone 2.01a27 (i686-pc-linux-gnu) Copyright (C) 1995-2004 J�rg Schilling
TOC Type: 1 = CD-ROM
scsidev: 'ATAPI:0,0,0'
devname: 'ATAPI'
scsibus: 0 target: 0 lun: 0
Warning: Using ATA Packet interface.
Warning: The related libscg interface code is in pre alpha.
Warning: There may be fatal problems.
Using libscg version 'schily-0.8'.
Driveropts: 'burnfree'
SCSI buffer size: 64512
atapi: 1
Device type    : Removable CD-ROM
Version        : 0
Response Format: 1
Vendor_info    : 'MITSUMI '
Identifikation : 'CR-48XGTE       '
Revision       : '1.0F'
Device seems to be: Philips CDD-522.
Current: 0x0000
Profile: 0x000A
Profile: 0x0009
Profile: 0x0008
Using generic SCSI-3/mmc   CD-R/CD-RW driver (mmc_cdr).
Driver flags   : MMC-2 SWABAUDIO BURNFREE
Supported modes: TAO PACKET SAO SAO/R96P RAW/R16 RAW/R96R
FIFO size      : 4194304 = 4096 KB
pregap1: -1
Track 01: data   643 MB         padsize:   30 KB
Total size:      739 MB (73:15.72) = 329679 sectors
Lout start:      739 MB (73:17/54) = 329679 sectors
cdrecord: No disk / Wrong disk!

cdrecord detects my drive fine...

Code: Select all

Cdrecord-Clone 2.01a27 (i686-pc-linux-gnu) Copyright (C) 1995-2004 J�rg Schilling
scsidev: 'ATAPI'
devname: 'ATAPI'
scsibus: -2 target: -2 lun: -2
Warning: Using ATA Packet interface.
Warning: The related libscg interface code is in pre alpha.
Warning: There may be fatal problems.
Using libscg version 'schily-0.8'.
scsibus0:
        0,0,0     0) 'MITSUMI ' 'CR-48XGTE       ' '1.0F' Removable CD-ROM
        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) *

I have no scsi emulation in my kernel? Is this a must? I've figured since cdrecord can detect my device, then writing should be possible.

However, it always says No Disk / Wrong Disk!

Any ideas?

[NitroPye]

You do not need scsi emulation in a 2.6 kernel, but in a 2.4 kernel you would need scsi emulation and the proper kernel boot parameters. I do not know how cdrecord detects devices but it might be independant of whether or not you can actualy use it