Unable to burn media with IDE burner in VMware ESX Server 3.5

[Aaron Tang]

Hi,
   The IDE burner can be identified by issuing "cdrecord -scanbus dev=ATAPI" in esx 3.5, but burning/blanking failed.
   any workaround except for recompiling the kernal?Thx

[Joerg Schilling-3]

Aaron Tang <twwbooleana@...> wrote:

>
> Hi,
>    The IDE burner can be identified by issuing "cdrecord -scanbus dev=ATAPI"
> in esx 3.5, but burning/blanking failed.
>    any workaround except for recompiling the kernal?Thx

I have no idea how to help you as you did not send any relevent information.

Jörg

--
 EMail:joerg@... (home) Jörg Schilling D-13353 Berlin
       js@...                (uni)  
       joerg.schilling@... (work) Blog: http://schily.blogspot.com/
 URL:  http://cdrecord.berlios.de/private/ ftp://ftp.berlios.de/pub/schily
_______________________________________________
Cdrecord-support mailing list
Cdrecord-support@...
https://lists.berlios.de/mailman/listinfo/cdrecord-support

[Aaron Tang]

Hi, this is what I got by issuing "cdrecord dev=ATAPI:/dev/hda a.iso"
=====================================================================
./cdrecord: No write mode specified.
./cdrecord: Asuming -sao mode.
./cdrecord: If your drive does not accept -sao, try -tao.
./cdrecord: Future versions of cdrecord may have different drive dependent defaults.
scsidev: 'ATAPI:/dev/hda'
devname: 'ATAPI:/dev/hda'
scsibus: -2 target: -2 lun: -2
Warning: dev=ATA: is preferred over dev=ATAPI:.
Warning: Using ATA Packet interface.
Warning: The related Linux kernel interface code seems to be unmaintained.
Warning: There is absolutely NO DMA, operations thus are slow.
SCSI buffer size: 64512
Cdrecord-ProDVD-ProBD-Clone 2.01.01a44 (i686-pc-linux-gnu) Copyright (C) 1995-2008 J鰎g Schilling
TOC Type: 1 = CD-ROM
Using libscg version 'schily-0.9'.
atapi: 1
Device type    : Removable CD-ROM
Version        : 0
Response Format: 2
Capabilities   :
Vendor_info    : 'HL-DT-ST'
Identifikation : 'RW/DVD GCC-T10N '
Revision       : '1.00'
Device seems to be: Generic mmc2 DVD-ROM.
Current: CD-RW
Profile: DVD-ROM
Profile: CD-ROM
Profile: CD-R
Profile: CD-RW (current)
Using generic SCSI-3/mmc   CD-R/CD-RW driver (mmc_cdr).
Driver flags   : MMC-3 SWABAUDIO BURNFREE
Supported modes: TAO PACKET SAO SAO/R96P SAO/R96R RAW/R16 RAW/R96P RAW/R96R
Drive buf size : 1601712 = 1564 KB
FIFO size      : 4194304 = 4096 KB
./cdrecord: Drive needs to reload the media to return to proper status.
./cdrecord: Cannot load media with this drive!
./cdrecord: Try to load media by hand.
Track 01: data   266 MB        
Total size:      306 MB (30:20.36) = 136527 sectors
Lout start:      306 MB (30:22/27) = 136527 sectors
Current Secsize: 2048
ATIP info from disk:
  Indicated writing power: 3
  Reference speed: 6
Disk Is not unrestricted
Disk Is erasable
  Disk sub type: High speed Rewritable (CAV) media (1)
  ATIP start of lead in:  -11625 (97:27/00)
  ATIP start of lead out: 359849 (79:59/74)
  1T speed low:  4 1T speed high: 10
  2T speed low:  4 2T speed high:  0 (reserved val  6)
  power mult factor: 1 5
  recommended erase/write power: 5
  A1 values: 24 1A D8
  A2 values: 26 B2 4A
Disk type:    Phase change
Manuf. index: 0
Manufacturer: Illegal Manufacturer code

    Capacity  Blklen/Sparesz.  Format-type  Type
           0                0         0x00  Reserved (0)
           0                0         0x00  Reserved (0)
Trying to clear drive status.
Re-load disk and hit <CR>
./cdrecord: Cannot load media with this drive!
./cdrecord: Try to load media by hand.
./cdrecord: Cannot load media.
=====================================================================
    As you can see, my burner is identified by cdrecord, but a "Re-load" operation seems making it unloadable?
    Also, "dmesg | grep '^hd'" presents the burner correctly, and so does"cdrecord -scanbus dev=ATAPI".
    The only concern I have now is whether it's caused by the lack of ide-scsi....coz when I issued "modprobe -l | grep ide", only "ide-type.o" and "ide-floppy.o" were in the results. So I asked previously apart from recompiling the kernal with ide-scsi included, if or not there is a workaround? even a way to determine the root cause will be appreciated.  Thx~~~

Joerg Schilling-3 wrote:

Aaron Tang <[e-mail]> wrote:

>
> Hi,
>    The IDE burner can be identified by issuing "cdrecord -scanbus dev=ATAPI"
> in esx 3.5, but burning/blanking failed.
>    any workaround except for recompiling the kernal?Thx

I have no idea how to help you as you did not send any relevent information.

Jörg

--
 EMail:[e-mail] (home) Jörg Schilling D-13353 Berlin
       [e-mail]                (uni)  
       [e-mail] (work) Blog: http://schily.blogspot.com/
 URL:  http://cdrecord.berlios.de/private/ ftp://ftp.berlios.de/pub/schily
_______________________________________________
Cdrecord-support mailing list
[e-mail]
https://lists.berlios.de/mailman/listinfo/cdrecord-support

[Joerg Schilling-3]

Aaron Tang <twwbooleana@...> wrote:

>
> Hi, this is what I got by issuing "cdrecord dev=ATAPI:/dev/hda a.iso"
> =====================================================================
> ./cdrecord: No write mode specified.
> ./cdrecord: Asuming -sao mode.
> ./cdrecord: If your drive does not accept -sao, try -tao.
> ./cdrecord: Future versions of cdrecord may have different drive dependent
> defaults.
> scsidev: 'ATAPI:/dev/hda'
> devname: 'ATAPI:/dev/hda'
> scsibus: -2 target: -2 lun: -2
> Warning: dev=ATA: is preferred over dev=ATAPI:.
> Warning: Using ATA Packet interface.
> Warning: The related Linux kernel interface code seems to be unmaintained.
> Warning: There is absolutely NO DMA, operations thus are slow.

You are forinc cdrecord to do something bad by giving it a bad dev= parameter.
Why did you do this instead of using the documented way?

I am sorry, but as you use something that is not really supported by the Linux
kernel, there may be many problems outside the influence of cdrecord.

> SCSI buffer size: 64512
> Cdrecord-ProDVD-ProBD-Clone 2.01.01a44 (i686-pc-linux-gnu) Copyright (C)
> 1995-2008 J???g Schilling
> TOC Type: 1 = CD-ROM
> Using libscg version 'schily-0.9'.
> atapi: 1
> Device type    : Removable CD-ROM
> Version        : 0
> Response Format: 2
> Capabilities   :
> Vendor_info    : 'HL-DT-ST'
> Identifikation : 'RW/DVD GCC-T10N '
> Revision       : '1.00'
> Device seems to be: Generic mmc2 DVD-ROM.
> Current: CD-RW
> Profile: DVD-ROM
> Profile: CD-ROM
> Profile: CD-R
> Profile: CD-RW (current)
> Using generic SCSI-3/mmc   CD-R/CD-RW driver (mmc_cdr).
> Driver flags   : MMC-3 SWABAUDIO BURNFREE
> Supported modes: TAO PACKET SAO SAO/R96P SAO/R96R RAW/R16 RAW/R96P RAW/R96R
> Drive buf size : 1601712 = 1564 KB
> FIFO size      : 4194304 = 4096 KB
> ./cdrecord: Drive needs to reload the media to return to proper status.
> ./cdrecord: Cannot load media with this drive!
> ./cdrecord: Try to load media by hand.

As I do not see any cdrecord error message, I cannot comment this.

It may be that your OS or your cable are defectice and modify the drive
information data.

Please send the cdrecord -prcap information

Jörg

--
 EMail:joerg@... (home) Jörg Schilling D-13353 Berlin
       js@...                (uni)  
       joerg.schilling@... (work) Blog: http://schily.blogspot.com/
 URL:  http://cdrecord.berlios.de/private/ ftp://ftp.berlios.de/pub/schily
_______________________________________________
Cdrecord-support mailing list
Cdrecord-support@...
https://lists.berlios.de/mailman/listinfo/cdrecord-support

[Aaron Tang]

    It is the problem of lacking ide-scsi module...After I compile ide-scsi as a kernel module, and install it on esx server with booting param "hda=scsi" appended in /boot/grub/menu.lst, cdrecord can now burn and blank media correctly.
    However, there is still a flaw....Actually, cdrecord works well when I feed "dev=" the name of device file(e.g. dev=/dev/sr0) aforetime though this doesn't obey the cdrecord's doc. To preserve a consistent way, we use this pattern...
    Since cdrecord can locate the target device with device file provided, my question is how to find the corresponding identifier in terms of "x,x,x" to a device file name.Thx~~

Joerg Schilling-3 wrote:

Aaron Tang <[e-mail]> wrote:

>
> Hi, this is what I got by issuing "cdrecord dev=ATAPI:/dev/hda a.iso"
> =====================================================================
> ./cdrecord: No write mode specified.
> ./cdrecord: Asuming -sao mode.
> ./cdrecord: If your drive does not accept -sao, try -tao.
> ./cdrecord: Future versions of cdrecord may have different drive dependent
> defaults.
> scsidev: 'ATAPI:/dev/hda'
> devname: 'ATAPI:/dev/hda'
> scsibus: -2 target: -2 lun: -2
> Warning: dev=ATA: is preferred over dev=ATAPI:.
> Warning: Using ATA Packet interface.
> Warning: The related Linux kernel interface code seems to be unmaintained.
> Warning: There is absolutely NO DMA, operations thus are slow.

You are forinc cdrecord to do something bad by giving it a bad dev= parameter.
Why did you do this instead of using the documented way?

I am sorry, but as you use something that is not really supported by the Linux
kernel, there may be many problems outside the influence of cdrecord.

> SCSI buffer size: 64512
> Cdrecord-ProDVD-ProBD-Clone 2.01.01a44 (i686-pc-linux-gnu) Copyright (C)
> 1995-2008 J???g Schilling
> TOC Type: 1 = CD-ROM
> Using libscg version 'schily-0.9'.
> atapi: 1
> Device type    : Removable CD-ROM
> Version        : 0
> Response Format: 2
> Capabilities   :
> Vendor_info    : 'HL-DT-ST'
> Identifikation : 'RW/DVD GCC-T10N '
> Revision       : '1.00'
> Device seems to be: Generic mmc2 DVD-ROM.
> Current: CD-RW
> Profile: DVD-ROM
> Profile: CD-ROM
> Profile: CD-R
> Profile: CD-RW (current)
> Using generic SCSI-3/mmc   CD-R/CD-RW driver (mmc_cdr).
> Driver flags   : MMC-3 SWABAUDIO BURNFREE
> Supported modes: TAO PACKET SAO SAO/R96P SAO/R96R RAW/R16 RAW/R96P RAW/R96R
> Drive buf size : 1601712 = 1564 KB
> FIFO size      : 4194304 = 4096 KB
> ./cdrecord: Drive needs to reload the media to return to proper status.
> ./cdrecord: Cannot load media with this drive!
> ./cdrecord: Try to load media by hand.

As I do not see any cdrecord error message, I cannot comment this.

It may be that your OS or your cable are defectice and modify the drive
information data.

Please send the cdrecord -prcap information

Jörg

--
 EMail:[e-mail] (home) Jörg Schilling D-13353 Berlin
       [e-mail]                (uni)  
       [e-mail] (work) Blog: http://schily.blogspot.com/
 URL:  http://cdrecord.berlios.de/private/ ftp://ftp.berlios.de/pub/schily
_______________________________________________
Cdrecord-support mailing list
[e-mail]
https://lists.berlios.de/mailman/listinfo/cdrecord-support

[Joerg Schilling-3]

Aaron Tang <twwbooleana@...> wrote:

>
>     It is the problem of lacking ide-scsi module...After I compile ide-scsi
> as a kernel module, and install it on esx server with booting param
> "hda=scsi" appended in /boot/grub/menu.lst, cdrecord can now burn and blank
> media correctly.
>     However, there is still a flaw....Actually, cdrecord works well when I
> feed "dev=" the name of device file(e.g. dev=/dev/sr0) aforetime though this
> doesn't obey the cdrecord's doc. To preserve a consistent way, we use this
> pattern...
>     Since cdrecord can locate the target device with device file provided,
> my question is how to find the corresponding identifier in terms of "x,x,x"
> to a device file name.Thx~~

See man page: cdrecord -scanbus

> Joerg Schilling-3 wrote:
> >
> > Aaron Tang <twwbooleana@...> wrote:
> >
> >>
> >> Hi, this is what I got by issuing "cdrecord dev=ATAPI:/dev/hda a.iso"
> >> =====================================================================
> >> ./cdrecord: No write mode specified.
> >> ./cdrecord: Asuming -sao mode.
> >> ./cdrecord: If your drive does not accept -sao, try -tao.
> >> ./cdrecord: Future versions of cdrecord may have different drive
> >> dependent
> >> defaults.
> >> scsidev: 'ATAPI:/dev/hda'
> >> devname: 'ATAPI:/dev/hda'
> >> scsibus: -2 target: -2 lun: -2
> >> Warning: dev=ATA: is preferred over dev=ATAPI:.
> >> Warning: Using ATA Packet interface.
> >> Warning: The related Linux kernel interface code seems to be
> >> unmaintained.

Well, I already mentioned that using dev=ATAPI:/dev/hda  is a bad idea.

Jörg

--
 EMail:joerg@... (home) Jörg Schilling D-13353 Berlin
       js@...                (uni)  
       joerg.schilling@... (work) Blog: http://schily.blogspot.com/
 URL:  http://cdrecord.berlios.de/private/ ftp://ftp.berlios.de/pub/schily
_______________________________________________
Cdrecord-support mailing list
Cdrecord-support@...
https://lists.berlios.de/mailman/listinfo/cdrecord-support

[Michael Shell]

On Tue, 24 Feb 2009 00:25:48 -0800 (PST)
Aaron Tang <twwbooleana@...> wrote:

> It is the problem of lacking ide-scsi module...After I compile
> ide-scsi as a kernel module, and install it on esx server with
> booting param "hda=scsi" appended in /boot/grub/menu.lst,
> cdrecord can now burn and blank media correctly.


Don't use the hda=scsi stuff anymore. And, in what follows,
it is required that you *don't* use it. (You'll need to reboot
after removing the hda=scsi kernel boot parameters.)

The chants you probably want under Linux are:


cdrecord dev=ATA: -scanbus

cdrecord dev=ATA:1,0,0 file.img


where the "1,0,0" is whatever parameters your drive is using
as reported by the dev=ATA: -scanbus.


  Cheers,

  Mike Shell
_______________________________________________
Cdrecord-support mailing list
Cdrecord-support@...
https://lists.berlios.de/mailman/listinfo/cdrecord-support

[Joerg Schilling-3]

Michael Shell <list1@...> wrote:

> The chants you probably want under Linux are:
>
>
> cdrecord dev=ATA: -scanbus
>
> cdrecord dev=ATA:1,0,0 file.img

This is not correct!

If you have just one drive, call:

cdrecord

else call:

cdrecord -scanbus

and then use one of the listed devices.

Jörg

--
 EMail:joerg@... (home) Jörg Schilling D-13353 Berlin
       js@...                (uni)  
       joerg.schilling@... (work) Blog: http://schily.blogspot.com/
 URL:  http://cdrecord.berlios.de/private/ ftp://ftp.berlios.de/pub/schily
_______________________________________________
Cdrecord-support mailing list
Cdrecord-support@...
https://lists.berlios.de/mailman/listinfo/cdrecord-support

[Michael Shell]

On Wed, 25 Feb 2009 16:56:24 +0100
Joerg.Schilling@... (Joerg Schilling) wrote:

> This is not correct!
>
> If you have just one drive, call:
>
> cdrecord
>
> else call:
>
> cdrecord -scanbus
>
> and then use one of the listed devices.

  Jörg,

I know I am not running the very latest cdrecord, but I haven't got
around to updating my system and I have been very happy with my
version of cdrecord (2.01.01a2) with the dev=ATA: interface. I
have used it a lot and it has served me well. Perhaps it will
do so for the original poster as well.

On my system:

[root]: cdrecord -scanbus
Cdrecord-Clone 2.01 (i586-pc-linux-gnu) Copyright (C) 1995-2004 Jörg Schilling
cdrecord: Warning: Running on Linux-2.6.25.4
cdrecord: There are unsettled issues with Linux-2.5 and newer.
cdrecord: If you have unexpected problems, please try Linux-2.4 or Solaris.
cdrecord: No such file or directory. Cannot open '/dev/pg*'. Cannot open SCSI driver.
cdrecord: For possible targets try 'cdrecord -scanbus'.
cdrecord: For possible transport specifiers try 'cdrecord dev=help'.


However:

[root]: cdrecord dev=ATA: -scanbus
Cdrecord-Clone 2.01 (i586-pc-linux-gnu) Copyright (C) 1995-2004 Jörg Schilling
cdrecord: Warning: Running on Linux-2.6.25.4
cdrecord: There are unsettled issues with Linux-2.5 and newer.
cdrecord: If you have unexpected problems, please try Linux-2.4 or Solaris.
scsidev: 'ATA:'
devname: 'ATA'
scsibus: -1 target: -1 lun: -1
Warning: Using badly designed ATAPI via /dev/hd* interface.
Linux sg driver version: 3.5.27
Using libscg version 'schily-0.8'.
scsibus0:
        0,0,0     0) *
        0,1,0     1) 'MATSHITA' 'LS-120 VER5   00' 'F515' Removable Disk
        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) '_NEC    ' 'DVD_RW ND-4551A ' '1-09' 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) *



If you changed this behavior since 2.01.01a2, do let us know with which
version the change occurred (if you know off the top of your head). The
original poster is using 2.01.01a44.

I tried to update to 2.01.01a58 to retest the above, however make complained:


checking if Linux include file /usr/src/linux/include/linux/ext2_fs.h is broken... yes
checking if Linux include file scsi/scsi.h is broken... no
checking if Linux include file /usr/src/linux/include/scsi/scsi.h is broken... no
checking if Linux include file scsi/sg.h is broken... no
checking if Linux include file /usr/src/linux/include/scsi/sg.h is broken... no

Warning: *** /usr/src/linux/include contains broken include files ***
Warning: *** /usr/src/linux/include is not used this reason ***
Warning: This may result in the inability to use recent Linux kernel interfaces

Warning: *** linux/ext2_fs.h is not usable at all ***
Warning: *** This makes it impossible to support Linux file flags ***
You may try to compile using 'make COPTX=-DTRY_EXT2_FS'


And thus, trying 2.01.01a58 will have to wait until I update my system.


  Cheers,

  Mike
_______________________________________________
Cdrecord-support mailing list
Cdrecord-support@...
https://lists.berlios.de/mailman/listinfo/cdrecord-support

[Joerg Schilling-3]

Michael Shell <list1@...> wrote:

> On Wed, 25 Feb 2009 16:56:24 +0100
> Joerg.Schilling@... (Joerg Schilling) wrote:
>
> > This is not correct!
> >
> > If you have just one drive, call:
> >
> > cdrecord
> >
> > else call:
> >
> > cdrecord -scanbus
> >
> > and then use one of the listed devices.

> I know I am not running the very latest cdrecord, but I haven't got
> around to updating my system and I have been very happy with my
> version of cdrecord (2.01.01a2) with the dev=ATA: interface. I
> have used it a lot and it has served me well. Perhaps it will
> do so for the original poster as well.

I am sorry, you are using a 4 year old version and the version you are using
does not run well on Linux because the Linux kernel people introduced an
incompatible kernel interface change that broke all applications that were
using SCSI generic in the way itwas documented.

> On my system:
>
> [root]: cdrecord -scanbus
> Cdrecord-Clone 2.01 (i586-pc-linux-gnu) Copyright (C) 1995-2004 Jörg Schilling
> cdrecord: Warning: Running on Linux-2.6.25.4

Linux ist an OS witzh extremely non-stable interfaces.
If you like to run an old version of cdrecord, you of course need to run a Linux
version that implements the interfaces from the time cdrecord was released.
The Linux kernel you are running did not intentionally break cdrecord-2.01

If you are unwilling to upgrade cdrecord, you of course need to run a correct
Linux kernel that fits this version of cdrecord.

For your cdrecord, the following Linux kernel are OK:

2.2.26 Fenruary 2004

2.4.26 April 2004

Your Linux kernel is from May 2008!!!!!!!

If you do not like to upgrade to a recent cdrecord version that knows about
the incompatibilities in your current Linux kernel, please choose the Linux
kernel you prefer from the list above.....


>
> If you changed this behavior since 2.01.01a2, do let us know with which
> version the change occurred (if you know off the top of your head). The
> original poster is using 2.01.01a44.

This is what the AN* files are for, please read....

> I tried to update to 2.01.01a58 to retest the above, however make complained:
>
>
> checking if Linux include file /usr/src/linux/include/linux/ext2_fs.h is broken... yes
> checking if Linux include file scsi/scsi.h is broken... no
> checking if Linux include file /usr/src/linux/include/scsi/scsi.h is broken... no
> checking if Linux include file scsi/sg.h is broken... no
> checking if Linux include file /usr/src/linux/include/scsi/sg.h is broken... no
>
> Warning: *** /usr/src/linux/include contains broken include files ***
> Warning: *** /usr/src/linux/include is not used this reason ***
> Warning: This may result in the inability to use recent Linux kernel interfaces
>
> Warning: *** linux/ext2_fs.h is not usable at all ***
> Warning: *** This makes it impossible to support Linux file flags ***
> You may try to compile using 'make COPTX=-DTRY_EXT2_FS'

If you like to complain about this kind of broken kernel include files, you
need to complain at your Linux distributor.

The Schily makefile system (together with my sources) does it's best to work around
non-working Linux include files. The message above is a hint on that "star"
cannot be compiled with EXT filesystem flag support on your distribution.

Jörg

--
 EMail:joerg@... (home) Jörg Schilling D-13353 Berlin
       js@...                (uni)  
       joerg.schilling@... (work) Blog: http://schily.blogspot.com/
 URL:  http://cdrecord.berlios.de/private/ ftp://ftp.berlios.de/pub/schily
_______________________________________________
Cdrecord-support mailing list
Cdrecord-support@...
https://lists.berlios.de/mailman/listinfo/cdrecord-support

[Michael Shell]

On Thu, 26 Feb 2009 10:26:42 +0100
Joerg.Schilling@... (Joerg Schilling) wrote:


> I am sorry, you are using a 4 year old version and the version you are
> using does not run well on Linux because the Linux kernel people
> introduced an incompatible kernel interface change that broke all
> applications that were using SCSI generic in the way itwas documented.


I checked my notes and this happened with 2.6.8.1 (I don't know if
newer kernels have a working ide-scsi system again) at which point
I went to dev=ATA:. After upgrading to the latest cdrecord, the
dev=ATA: is no longer needed as Jörg said (it automatically goes
to ATA if one does not use the hda=scsi ide-scsi stuff).

BTW, why is 1000 prefixed to the scsibus number now? It's OK, I'm
just curious.


To Aaron: make sure you have SCSI generic support and SCSI CDROM
support in the kernel.


  Cheers and thank you,

  Mike Shell
_______________________________________________
Cdrecord-support mailing list
Cdrecord-support@...
https://lists.berlios.de/mailman/listinfo/cdrecord-support

[Joerg Schilling-3]

Michael Shell <list1@...> wrote:

> On Thu, 26 Feb 2009 10:26:42 +0100
> Joerg.Schilling@... (Joerg Schilling) wrote:
>
>
> > I am sorry, you are using a 4 year old version and the version you are
> > using does not run well on Linux because the Linux kernel people
> > introduced an incompatible kernel interface change that broke all
> > applications that were using SCSI generic in the way itwas documented.
>
>
> I checked my notes and this happened with 2.6.8.1 (I don't know if

You are correct, 2.6.8.1 is the Lunux kernel with the incompatible interface
change that caused cdrtools not to work any longer.


> newer kernels have a working ide-scsi system again) at which point
> I went to dev=ATA:. After upgrading to the latest cdrecord, the
> dev=ATA: is no longer needed as Jörg said (it automatically goes
> to ATA if one does not use the hda=scsi ide-scsi stuff).
>
> BTW, why is 1000 prefixed to the scsibus number now? It's OK, I'm
> just curious.

Well, the problem is that the Linux kernel does not implement clean orthogonal
SCSI support. There are even 2-3 competitive drivers for the same hardware that
don't know from each other.....

As the Linux kernel interface changed so frequent and so in depth during the
past 14 years, I decided to first wait at least 6 months after a new
incompatibile kernel interface change before trying to implement a workaround
and to implement the workaround in a way that leaves room for further
workarounds.

The 1000 prefix maps to the device support in the linux kernel that was not
implemented in a clean orthogonal way.

Note that all CD/DVD/BD writers are native SCSI devices and should be supported
inside a single orthogonal SCSI framework. With ATAPIoverSATA drives this is
true again for newer Linux kernels, but ATAPIoverPATA drives are not integrated
into the Linux kernel driver framework.

Jörg

--
 EMail:joerg@... (home) Jörg Schilling D-13353 Berlin
       js@...                (uni)  
       joerg.schilling@... (work) Blog: http://schily.blogspot.com/
 URL:  http://cdrecord.berlios.de/private/ ftp://ftp.berlios.de/pub/schily
_______________________________________________
Cdrecord-support mailing list
Cdrecord-support@...
https://lists.berlios.de/mailman/listinfo/cdrecord-support