[Date Prev][Date Next] [Thread Prev][Thread Next] [Date Index] [Thread Index]

Re: cdrecod and profile 0x40 (BD-ROM): -atip exits with 255



Giulio Orsero <giulioo@gmail.com> wrote:

> OS: LINUX   kernel 2.4.33  
> USB Blu-ray writer.
>
> I use cdrecord/cdrskin "-atip -v" to detect mounted media type.
>
> Media is BD-R written using cdrskin.
>
> When BD-R is new/unused, both cdrecord and cdrskin tell me "BD-R" and exit
> 0.
>
> After being written (single session, closed, so it's now a BD-ROM):
> - cdrecord tells me it's a BD-ROM but then it exits > 0, not ok for scripts.
> - cdrskin exits 0.
>
> == cdrecord command
> cdrecord-2.01.01a53 dev=1,0,0 -atip -v
> echo "EXIT CODE: $?"
>
> == cdrecord output
> scsidev: '1,0,0'
> scsibus: 1 target: 0 lun: 0
> Linux sg driver version: 3.1.25
> SCSI buffer size: 129024
> Cdrecord-ProDVD-ProBD-Clone 2.01.01a53 (i686-pc-linux-gnu) Copyright (C)
> 1995-2008 Jörg Schilling
> TOC Type: 1 = CD-ROM
> Using libscg version 'schily-0.9'.
> atapi: 1
> Device type    : Removable CD-ROM
> Version        : 2
> Response Format: 2
> Capabilities   :
> Vendor_info    : 'HL-DT-ST'
> Identifikation : 'BD-RE  BE06LU10 '
> Revision       : 'YE03'
> Device seems to be: Generic mmc2 DVD-R/DVD-RW/DVD-RAM.
> Current: BD-ROM
> Profile: BD-ROM (current)
> Profile: CD-RW
> Profile: CD-ROM
> Profile: Removable Disk
> cdrecord-2.01.01a53: Found unsupported 0x40 profile.           <===========
> cdrecord-2.01.01a53: Sorry, no supported CD/DVD/BD-Recorder found on this
> target.
> EXIT CODE: 255
>

I received this messasage already from another person. It looks like a GCC bug.
Did you try to compile cdrecord with Sun Studio?

Check drv_mmc.c


Jörg

-- 
 EMail:joerg@schily.isdn.cs.tu-berlin.de (home) Jörg Schilling D-13353 Berlin
       js@cs.tu-berlin.de                (uni)  
       schilling@fokus.fraunhofer.de     (work) Blog: http://schily.blogspot.com/
 URL:  http://cdrecord.berlios.de/private/ ftp://ftp.berlios.de/pub/schily


Reply to: