No supported write modes with LG GSA-H62N SATA DVD+RW

2007-09-09 Thread Joe MacDonald
I've seen a couple of discussions about similar problems to mine with
different models (the H30N seemed to be a hot topic about six weeks ago) but
I haven't seen any suggestions that make things work (or at least point to a
cause of the failure) for me.  First, the facts.

- I bought this drive back in the spring.  It appears to work fine in WinXP
with Nero 7.something or other.

- I started off with Ubuntu 6.10 and upgraded to 7.04, neither of which
seemed to work.

- cat /proc/version
Linux version 2.6.20-16-generic ([EMAIL PROTECTED]) (gcc version 4.1.2 (Ubuntu
4.1.2-0ubuntu4)) #2 SMP Fri Aug 31 00:55:27 UTC 2007

- I went and grabbed the latest official cdrecord:
cdrecord -version
Cdrecord-ProDVD-ProBD-Clone 2.01.01a35 (i686-pc-linux-gnu) Copyright (C)
1995-2007 J�rg Schilling

- It seems to find the drive okay:
cdrecord -scanbus
Cdrecord-ProDVD-ProBD-Clone 2.01.01a35 (i686-pc-linux-gnu) Copyright (C)
1995-2007 J�rg Schilling
Linux sg driver version: 3.5.34
Using libscg version 'schily-0.9'.
scsibus0:
0,0,0 0) 'HL-DT-ST' 'DVDRAM GSA-H62N ' 'CL00' 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) *

- Any attempt to write (-tao, -sao, -dao, -raw) gives me what appears to be
the same errors:

cdrecord -v speed=1 dev=0,0,0 -audio gbtrack_01.wav gbtrack_02.wav
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.
Cdrecord-ProDVD-ProBD-Clone 2.01.01a35 (i686-pc-linux-gnu) Copyright (C)
1995-2007 J�rg Schilling
TOC Type: 0 = CD-DA
scsidev: '0,0,0'
scsibus: 0 target: 0 lun: 0
Linux sg driver version: 3.5.34
Using libscg version 'schily-0.9'.
SCSI buffer size: 64512
atapi: 1
Device type: Removable CD-ROM
Version: 5
Response Format: 2
Capabilities   :
Vendor_info: 'HL-DT-ST'
Identifikation : 'DVDRAM GSA-H62N '
Revision   : 'CL00'
Device seems to be: Generic mmc2 DVD-R/DVD-RW/DVD-RAM.
Current: CD-R
Profile: DVD-RAM
Profile: DVD-R sequential recording
Profile: DVD-R/DL sequential recording
Profile: DVD-R/DL layer jump recording
Profile: DVD-RW sequential recording
Profile: DVD-RW restricted overwrite
Profile: DVD+RW
Profile: DVD+R
Profile: DVD+R/DL
Profile: DVD-ROM
Profile: CD-R (current)
Profile: CD-RW
Profile: CD-ROM
Profile: Removable Disk
Using generic SCSI-3/mmc   CD-R/CD-RW driver (mmc_cdr).
Driver flags   : MMC-3 SWABAUDIO BURNFREE
Supported modes:
Drive buf size : 1053696 = 1029 KB
Drive pbuf size: 1966080 = 1920 KB
Drive DMA Speed: 16457 kB/s 93x CD 11x DVD 3x BD
FIFO size  : 4194304 = 4096 KB
cdrecord: Drive does not support SAO recording.
cdrecord: Illegal write mode for this drive.

Does anyone have any suggestions?

-- 
-Joe.


Re: No supported write modes with LG GSA-H62N SATA DVD+RW

2007-09-10 Thread Joerg Schilling
"Joe MacDonald" <[EMAIL PROTECTED]> wrote:

> I've seen a couple of discussions about similar problems to mine with
> different models (the H30N seemed to be a hot topic about six weeks ago) but
> I haven't seen any suggestions that make things work (or at least point to a
> cause of the failure) for me.  First, the facts.
>
> - I bought this drive back in the spring.  It appears to work fine in WinXP
> with Nero 7.something or other.
>
> - I started off with Ubuntu 6.10 and upgraded to 7.04, neither of which
> seemed to work.
>
> - cat /proc/version
> Linux version 2.6.20-16-generic ([EMAIL PROTECTED]) (gcc version 4.1.2 (Ubuntu
> 4.1.2-0ubuntu4)) #2 SMP Fri Aug 31 00:55:27 UTC 2007
>
> - I went and grabbed the latest official cdrecord:
> cdrecord -version
> Cdrecord-ProDVD-ProBD-Clone 2.01.01a35 (i686-pc-linux-gnu) Copyright (C)
> 1995-2007 J???rg Schilling
>
> - It seems to find the drive okay:
> cdrecord -scanbus
> Cdrecord-ProDVD-ProBD-Clone 2.01.01a35 (i686-pc-linux-gnu) Copyright (C)
> 1995-2007 J???rg Schilling
> Linux sg driver version: 3.5.34
> Using libscg version 'schily-0.9'.
> scsibus0:
> 0,0,0 0) 'HL-DT-ST' 'DVDRAM GSA-H62N ' 'CL00' 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) *
>
> - Any attempt to write (-tao, -sao, -dao, -raw) gives me what appears to be
> the same errors:
>
> cdrecord -v speed=1 dev=0,0,0 -audio gbtrack_01.wav gbtrack_02.wav
> 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.
> Cdrecord-ProDVD-ProBD-Clone 2.01.01a35 (i686-pc-linux-gnu) Copyright (C)
> 1995-2007 J???rg Schilling
> TOC Type: 0 = CD-DA
> scsidev: '0,0,0'
> scsibus: 0 target: 0 lun: 0
> Linux sg driver version: 3.5.34
> Using libscg version 'schily-0.9'.
> SCSI buffer size: 64512
> atapi: 1
> Device type: Removable CD-ROM
> Version: 5
> Response Format: 2
> Capabilities   :
> Vendor_info: 'HL-DT-ST'
> Identifikation : 'DVDRAM GSA-H62N '
> Revision   : 'CL00'
> Device seems to be: Generic mmc2 DVD-R/DVD-RW/DVD-RAM.
> Current: CD-R
> Profile: DVD-RAM
> Profile: DVD-R sequential recording
> Profile: DVD-R/DL sequential recording
> Profile: DVD-R/DL layer jump recording
> Profile: DVD-RW sequential recording
> Profile: DVD-RW restricted overwrite
> Profile: DVD+RW
> Profile: DVD+R
> Profile: DVD+R/DL
> Profile: DVD-ROM
> Profile: CD-R (current)
> Profile: CD-RW
> Profile: CD-ROM
> Profile: Removable Disk
> Using generic SCSI-3/mmc   CD-R/CD-RW driver (mmc_cdr).
> Driver flags   : MMC-3 SWABAUDIO BURNFREE
> Supported modes:
> Drive buf size : 1053696 = 1029 KB
> Drive pbuf size: 1966080 = 1920 KB
> Drive DMA Speed: 16457 kB/s 93x CD 11x DVD 3x BD
> FIFO size  : 4194304 = 4096 KB
> cdrecord: Drive does not support SAO recording.
> cdrecord: Illegal write mode for this drive.

Please try to run cdrecord on a different OS (e.g. Solaris or Win32).

Your mail does not include any hint to the problem but other similar
reports make it highly probable that this is caused by a bug in the Linux 
kernel.

There are well known reports that verify that Linux under some conditions
bastardizes the "blank" command before sending iit to the drive. I myself
did see Linux bastardizing the "read toc" command. In my case, booting the
same hardware with Solaris or SCO Unixware did solve the problem.

Jörg

-- 
 EMail:[EMAIL PROTECTED] (home) Jörg Schilling D-13353 Berlin
   [EMAIL PROTECTED](uni)  
   [EMAIL PROTECTED] (work) Blog: http://schily.blogspot.com/
 URL:  http://cdrecord.berlios.de/old/private/ ftp://ftp.berlios.de/pub/schily


-- 
To UNSUBSCRIBE, email to [EMAIL PROTECTED]
with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]



Re: No supported write modes with LG GSA-H62N SATA DVD+RW

2007-09-10 Thread Rob Bogus

Joe MacDonald wrote:
I've seen a couple of discussions about similar problems to mine with 
different models (the H30N seemed to be a hot topic about six weeks 
ago) but I haven't seen any suggestions that make things work (or at 
least point to a cause of the failure) for me.  First, the facts.


- I bought this drive back in the spring.  It appears to work fine in 
WinXP with Nero 7.something or other.


- I started off with Ubuntu 6.10 and upgraded to 7.04, neither of 
which seemed to work.


- cat /proc/version
Linux version 2.6.20-16-generic ([EMAIL PROTECTED]) (gcc version 4.1.2 
(Ubuntu 4.1.2-0ubuntu4)) #2 SMP Fri Aug 31 00:55:27 UTC 2007


- I went and grabbed the latest official cdrecord:
cdrecord -version
Cdrecord-ProDVD-ProBD-Clone 2.01.01a35 (i686-pc-linux-gnu) Copyright 
(C) 1995-2007 J�rg Schilling


Do realize some things about this software, unlike most other CD burning 
software it must be run as root, due to using some restricted commands 
which other burning software packages avoid. You might try "cdrskin" 
software and see if that works better, or "wodim" which I thought came 
with ubuntu.


- It seems to find the drive okay:
cdrecord -scanbus
Cdrecord-ProDVD-ProBD-Clone 2.01.01a35 (i686-pc-linux-gnu) Copyright 
(C) 1995-2007 J�rg Schilling

Linux sg driver version: 3.5.34
Using libscg version 'schily-0.9'.
scsibus0:
0,0,0 0) 'HL-DT-ST' 'DVDRAM GSA-H62N ' 'CL00' 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) *

- Any attempt to write (-tao, -sao, -dao, -raw) gives me what appears 
to be the same errors:


cdrecord -v speed=1 dev=0,0,0 -audio gbtrack_01.wav gbtrack_02.wav
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.
Cdrecord-ProDVD-ProBD-Clone 2.01.01a35 (i686-pc-linux-gnu) Copyright 
(C) 1995-2007 J�rg Schilling

TOC Type: 0 = CD-DA
scsidev: '0,0,0'
scsibus: 0 target: 0 lun: 0
Linux sg driver version: 3.5.34
Using libscg version 'schily-0.9'.
SCSI buffer size: 64512
atapi: 1
Device type: Removable CD-ROM
Version: 5
Response Format: 2
Capabilities   :
Vendor_info: 'HL-DT-ST'
Identifikation : 'DVDRAM GSA-H62N '
Revision   : 'CL00'
Device seems to be: Generic mmc2 DVD-R/DVD-RW/DVD-RAM.
Current: CD-R
Profile: DVD-RAM
Profile: DVD-R sequential recording
Profile: DVD-R/DL sequential recording
Profile: DVD-R/DL layer jump recording
Profile: DVD-RW sequential recording
Profile: DVD-RW restricted overwrite
Profile: DVD+RW
Profile: DVD+R
Profile: DVD+R/DL
Profile: DVD-ROM
Profile: CD-R (current)
Profile: CD-RW
Profile: CD-ROM
Profile: Removable Disk
Using generic SCSI-3/mmc   CD-R/CD-RW driver (mmc_cdr).
Driver flags   : MMC-3 SWABAUDIO BURNFREE
Supported modes:
Drive buf size : 1053696 = 1029 KB
Drive pbuf size: 1966080 = 1920 KB
Drive DMA Speed: 16457 kB/s 93x CD 11x DVD 3x BD
FIFO size  : 4194304 = 4096 KB
cdrecord: Drive does not support SAO recording.
cdrecord: Illegal write mode for this drive.

Does anyone have any suggestions?

--
-Joe. 



--
E. Robert Bogusta
 It seemed like a good idea at the time




Re: No supported write modes with LG GSA-H62N SATA DVD+RW

2007-09-10 Thread Joerg Schilling
Rob Bogus <[EMAIL PROTECTED]> wrote:

> > - I went and grabbed the latest official cdrecord:
> > cdrecord -version
> > Cdrecord-ProDVD-ProBD-Clone 2.01.01a35 (i686-pc-linux-gnu) Copyright 
> > (C) 1995-2007 J???rg Schilling
>
> Do realize some things about this software, unlike most other CD burning 
> software it must be run as root, due to using some restricted commands 
> which other burning software packages avoid. You might try "cdrskin" 
> software and see if that works better, or "wodim" which I thought came 
> with ubuntu.

Please do not try to spread FUD!

wodim is full of bugs and it's users usually spend their time to write bug 
reports that are ignored. 

 Let us discuss the quality of "wodim" (really cdrkit).. a few weeks 
 ago, I did check the bugtracking system from Ubuntu together with the Ubuntu 
 cdrecording group. It turned out that _all_ bugs in the Ubuntu BTS that are 
 related to the CD/DVD recording software a caused by "cdrkit" - the wodim 
 bundle. 

 -   Some of the bugs have been fixed in the original during the past 2 
years 
 and thus are no longer present in the original cdrtools 

 -   The other bugs are bugs that have been introduced by the "wodim 
 maintainers" 

 Check  http://cdrecord.berlios.de/new/private/linux-dist.html#problems 
 for a shortened list of the main problems. 

I cannot talk about "cdrskin" as it is non-portable 

I guess that it supports only a very limited set of functions that may under
_some_ conditions _and_ newer Linux kernel work, but as I did write many times 
before, in general, you need root privileges on Linux.

Jörg

-- 
 EMail:[EMAIL PROTECTED] (home) Jörg Schilling D-13353 Berlin
   [EMAIL PROTECTED](uni)  
   [EMAIL PROTECTED] (work) Blog: http://schily.blogspot.com/
 URL:  http://cdrecord.berlios.de/old/private/ ftp://ftp.berlios.de/pub/schily


-- 
To UNSUBSCRIBE, email to [EMAIL PROTECTED]
with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]



Re: No supported write modes with LG GSA-H62N SATA DVD+RW

2007-09-10 Thread Norbert Preining
On Mon, 10 Sep 2007, Joerg Schilling wrote:
> before, in general, you need root privileges on Linux.

Don't spread FUD yourself. Your rejected to provide a list of SCSI
commands several times. No wonder that kernel people igored you.

Best wishes

Norbert

---
Dr. Norbert Preining <[EMAIL PROTECTED]>Vienna University of Technology
Debian Developer <[EMAIL PROTECTED]> Debian TeX Group
gpg DSA: 0x09C5B094  fp: 14DF 2E6C 0307 BE6D AD76  A9C0 D2BF 4AA3 09C5 B094
---
GILDERSOME (adj.) Descriptive of a joke someone tells you which starts
well, but which becomes so embellished in the telling that you start
to weary of it after scarcely half an hour.
--- Douglas Adams, The Meaning of Liff


-- 
To UNSUBSCRIBE, email to [EMAIL PROTECTED]
with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]



Re: No supported write modes with LG GSA-H62N SATA DVD+RW

2007-09-10 Thread Thomas Schmitt
Hi,

(On 3rd, 4th try:
 My previous messages seem not to have reached
 the list. 
 On 2nd try:
 I sent this message to list and poster a few
 hours before but it did not show up on the list.)



Joe MacDonald:
> I've seen a couple of discussions about similar problems to mine with
> different models (the H30N seemed to be a hot topic about six weeks ago)
> but I haven't seen any suggestions that make things work (or at least
> point to a cause of the failure) for me.

There was one incident of a remedy:
The user exchanged the SATA controller which connected
the drive with the computer.


> Supported modes:
> ...
> cdrecord: Drive does not support SAO recording.

In previous cases this has turned out to be the
result of failed attempts to set various write
modes.
The immediate error was with MMC command MODE SELECT
which returned an error condition saying that the
sent mode page 05h had the wrong length.

It has been tested with both lengths which are
described in the MMC-5 specs. No success.

Then the user bought the new controller.


> - I bought this drive back in the spring.  It appears to work fine in
> WinXP with Nero 7.something or other.

This is the really embarrassing part of those
error reports: The Windowers know a way to make
that combination of drive and controller work.
We don't - yet.

It might be that it is a bug with Linux and
certain SATA controllers.
But that would be a really smart bug. It disguises
very successfully as a bug of the drive.




Questions:

- Can you find out the type of that SATA controller ?
  
- Would it work with growisofs and DVD-R or unformatted
  DVD-RW ?
  (For these media the drive gets sent a mode page 05h,
   like with CD-R, CD-RW.)

- Are you willing to do experiments with program cdrskin ?
  I suppose them to be harmless, but they will at least
  cost some time and in worst case a reboot - if we manage
  to get the drive stuck by innovative combinations of
  MMC commands.
  (My next plan would be to fetch a mode page 05h and 
   to see how long the reply is. It would need to do
   some programming in the underlying libburn before we
   can start.)


Have a nice day :)

Thomas

-- 
Ist Ihr Browser Vista-kompatibel? Jetzt die neuesten 
Browser-Versionen downloaden: http://www.gmx.net/de/go/browser


-- 
To UNSUBSCRIBE, email to [EMAIL PROTECTED]
with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]



Re: No supported write modes with LG GSA-H62N SATA DVD+RW

2007-09-10 Thread Joerg Schilling
Norbert Preining <[EMAIL PROTECTED]> wrote:

> On Mon, 10 Sep 2007, Joerg Schilling wrote:
> > before, in general, you need root privileges on Linux.
>
> Don't spread FUD yourself. Your rejected to provide a list of SCSI
> commands several times. No wonder that kernel people igored you.

You are a well known troll who did already spread FUD many times.


You even try to influence people by using a special way of spreading your lies.

Anybody with basic programming skills is able to extract the list of SCSI 
commands from cdrecord.

In addition, the list has been send to the Linux kernel people but it has been
ignored. 


Jörg

-- 
 EMail:[EMAIL PROTECTED] (home) Jörg Schilling D-13353 Berlin
   [EMAIL PROTECTED](uni)  
   [EMAIL PROTECTED] (work) Blog: http://schily.blogspot.com/
 URL:  http://cdrecord.berlios.de/old/private/ ftp://ftp.berlios.de/pub/schily


-- 
To UNSUBSCRIBE, email to [EMAIL PROTECTED]
with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]



Re: No supported write modes with LG GSA-H62N SATA DVD+RW

2007-09-10 Thread Joerg Schilling
"Thomas Schmitt" <[EMAIL PROTECTED]> wrote:

> > - I bought this drive back in the spring.  It appears to work fine in
> > WinXP with Nero 7.something or other.
>
> This is the really embarrassing part of those
> error reports: The Windowers know a way to make
> that combination of drive and controller work.
> We don't - yet.


??? Who is 'we'?

Did you try Solaris on this hardware?


> It might be that it is a bug with Linux and
> certain SATA controllers.
> But that would be a really smart bug. It disguises
> very successfully as a bug of the drive.
>
>
> 
>
> Questions:
>
> - Can you find out the type of that SATA controller ?
>   
> - Would it work with growisofs and DVD-R or unformatted
>   DVD-RW ?
>   (For these media the drive gets sent a mode page 05h,
>like with CD-R, CD-RW.)
>
> - Are you willing to do experiments with program cdrskin ?

Cdrecord contains all special tricks that may be needed in order
to run a mode select command to drives with buggy firmware.

The OP did not send any cdrecord SCSI trace. If he did, we couild discuss
the problem.

Jörg

-- 
 EMail:[EMAIL PROTECTED] (home) Jörg Schilling D-13353 Berlin
   [EMAIL PROTECTED](uni)  
   [EMAIL PROTECTED] (work) Blog: http://schily.blogspot.com/
 URL:  http://cdrecord.berlios.de/old/private/ ftp://ftp.berlios.de/pub/schily


-- 
To UNSUBSCRIBE, email to [EMAIL PROTECTED]
with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]



Re: No supported write modes with LG GSA-H62N SATA DVD+RW

2007-09-10 Thread Thomas Schmitt
Hi,

me:
> > We don't [know the trick] - yet.
Joerg Schilling:
> ??? Who is 'we'?

The users, the Linux people, me, and who else
tried to find out what's wrong with those systems.


Joerg Schilling:
> in general, you need root privileges on Linux.

But for what ? Make me smarter.

I do not know a single incident where root privileges
made the difference between working and not working
if access permissions to /dev/sgN resp. /dev/srM
were granted.
If you need to get outmost process priority -
ok, then you need to be superuser. I don't think this
belongs _inside_ the burn program.


Whatever:
The problem in this thread has multiply been verified
to appear for the superuser as well.


It is either a bug in Linux or a peculiarity of
the drive-controller combination which we do not
know yet but which is known to Microsoft or Nero AG.

In any case we should try to help exploring.
Known facts:
It only happens with newer Linux and SATA drives.
Many newer Linuxes with SATA drives work without problems.
There seem to be SATA controller hardware issues involved.


> The OP did not send any cdrecord SCSI trace.

The state of the exploration is that sending 
any mode pages 05h fails. Just believe me, for once.

I still hope to find somebody who is willing to
pick up the thread so we can continue trying to find
the reason. (We = experimenter + me + evtl. helpers)


Have a nice day :)

Thomas

-- 
Pt! Schon vom neuen GMX MultiMessenger gehört?
Der kanns mit allen: http://www.gmx.net/de/go/multimessenger


-- 
To UNSUBSCRIBE, email to [EMAIL PROTECTED]
with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]



Re: No supported write modes with LG GSA-H62N SATA DVD+RW

2007-09-10 Thread Joe MacDonald
Hi Jörg,

On 9/10/07, Joerg Schilling <[EMAIL PROTECTED]> wrote:
>
> "Joe MacDonald" <[EMAIL PROTECTED]> wrote:
>
> > I've seen a couple of discussions about similar problems to mine with
> > different models (the H30N seemed to be a hot topic about six weeks ago)
> but
> > I haven't seen any suggestions that make things work (or at least point
> to a
> > cause of the failure) for me.  First, the facts.
> >
> > - I bought this drive back in the spring.  It appears to work fine in
> WinXP
> > with Nero 7.something or other.
> >
> > - I started off with Ubuntu 6.10 and upgraded to 7.04, neither of which
> > seemed to work.
> >
> > - cat /proc/version
> > Linux version 2.6.20-16-generic ([EMAIL PROTECTED]) (gcc version 
> > 4.1.2(Ubuntu
> > 4.1.2-0ubuntu4)) #2 SMP Fri Aug 31 00:55:27 UTC 2007
> >
> > - I went and grabbed the latest official cdrecord:
> > cdrecord -version
> > Cdrecord-ProDVD-ProBD-Clone 2.01.01a35 (i686-pc-linux-gnu) Copyright (C)
> > 1995-2007 J???rg Schilling
> >
> > - It seems to find the drive okay:
> > cdrecord -scanbus
> > Cdrecord-ProDVD-ProBD-Clone 2.01.01a35 (i686-pc-linux-gnu) Copyright (C)
> > 1995-2007 J???rg Schilling
> > Linux sg driver version: 3.5.34
> > Using libscg version 'schily-0.9'.
> > scsibus0:
> > 0,0,0 0) 'HL-DT-ST' 'DVDRAM GSA-H62N ' 'CL00' 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) *
> >
> > - Any attempt to write (-tao, -sao, -dao, -raw) gives me what appears to
> be
> > the same errors:
> >
> > cdrecord -v speed=1 dev=0,0,0 -audio gbtrack_01.wav gbtrack_02.wav
> > 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.
> > Cdrecord-ProDVD-ProBD-Clone 2.01.01a35 (i686-pc-linux-gnu) Copyright (C)
> > 1995-2007 J???rg Schilling
> > TOC Type: 0 = CD-DA
> > scsidev: '0,0,0'
> > scsibus: 0 target: 0 lun: 0
> > Linux sg driver version: 3.5.34
> > Using libscg version 'schily-0.9'.
> > SCSI buffer size: 64512
> > atapi: 1
> > Device type: Removable CD-ROM
> > Version: 5
> > Response Format: 2
> > Capabilities   :
> > Vendor_info: 'HL-DT-ST'
> > Identifikation : 'DVDRAM GSA-H62N '
> > Revision   : 'CL00'
> > Device seems to be: Generic mmc2 DVD-R/DVD-RW/DVD-RAM.
> > Current: CD-R
> > Profile: DVD-RAM
> > Profile: DVD-R sequential recording
> > Profile: DVD-R/DL sequential recording
> > Profile: DVD-R/DL layer jump recording
> > Profile: DVD-RW sequential recording
> > Profile: DVD-RW restricted overwrite
> > Profile: DVD+RW
> > Profile: DVD+R
> > Profile: DVD+R/DL
> > Profile: DVD-ROM
> > Profile: CD-R (current)
> > Profile: CD-RW
> > Profile: CD-ROM
> > Profile: Removable Disk
> > Using generic SCSI-3/mmc   CD-R/CD-RW driver (mmc_cdr).
> > Driver flags   : MMC-3 SWABAUDIO BURNFREE
> > Supported modes:
> > Drive buf size : 1053696 = 1029 KB
> > Drive pbuf size: 1966080 = 1920 KB
> > Drive DMA Speed: 16457 kB/s 93x CD 11x DVD 3x BD
> > FIFO size  : 4194304 = 4096 KB
> > cdrecord: Drive does not support SAO recording.
> > cdrecord: Illegal write mode for this drive.
>
> Please try to run cdrecord on a different OS (e.g. Solaris or Win32).


I'm not at the affected machine right now, so it'll be a few more hours
before I get a chance, but I'll give that a try.  I don't have a Solaris x86
version, but since I'm already dual-booting into WinXP, trying a Win32
cdrecord should be easy.

Your mail does not include any hint to the problem but other similar
> reports make it highly probable that this is caused by a bug in the Linux
> kernel.


I'll be happy to try whatever diagnostics you want me to try if we can find
the source of the problem.  I just want to either get it working or be
reasonably confident I know what the root cause is.  As you say here,
there's not much to go on right now, but my feeling has been that it was
something in the linux kernel as well.

When I get a chance to try this with Windows, I'll follow up.  It'll be six
hours or so at least before I get there.

Thanks,
-Joe.

There are well known reports that verify that Linux under some conditions
> bastardizes the "blank" command before sending iit to the drive. I myself
> did see Linux bastardizing the "read toc" command. In my case, booting the
> same hardware with Solaris or SCO Unixware did solve the problem.
>
> Jörg
>
> --
> EMail:[EMAIL PROTECTED] (home) Jörg Schilling D-13353
> Berlin
>[EMAIL PROTECTED](uni)
>[EMAIL PROTECTED] (work) Blog:
> http://schily.blogspot.com/
> URL:  http://cdrecord.berlios.de/old/private/
> ftp://ftp.berlios.de/pub/schily
>



-- 
-Joe.


Re: No supported write modes with LG GSA-H62N SATA DVD+RW

2007-09-10 Thread Joe MacDonald
Hi Thomas,

On 9/10/07, Thomas Schmitt <[EMAIL PROTECTED]> wrote:
>
> Hi,
>
> > I've seen a couple of discussions about similar problems to mine with
> > different models (the H30N seemed to be a hot topic about six weeks ago)
> > but I haven't seen any suggestions that make things work (or at least
> > point to a cause of the failure) for me.
>
> There was one incident of a remedy:
> The user exchanged the SATA controller which connected
> the drive with the computer.


I'm not completely opposed to that, but I've been considering that a
non-solution so far since it appears that the controller isn't completely
defective, just not completely functional in Linux.

The controller I'm using is the on-board one with my motherboard, an older
DFI K8M800, which makes it difficult to find out exactly what hardware the
put on the board unless you know what you're looking for, and when it comes
to SATA stuff, I don't, really.  lspci reports it as:

00:0f.0 RAID bus controller: VIA Technologies, Inc. VIA VT6420 SATA RAID
Controller (rev 80)
Subsystem: DFI Inc Unknown device 1004
Control: I/O+ Mem+ BusMaster+ SpecCycle- MemWINV- VGASnoop- ParErr-
Stepping- SERR- FastB2B-
Status: Cap+ 66MHz- UDF- FastB2B+ ParErr- DEVSEL=medium >TAbort-
SERR-  Link [ALKA] -> GSI 20
(level, low) -> IRQ 16
[   19.005841] sata_via :00:0f.0: routed to hard irq line 11
[   19.005956] ata1: SATA max UDMA/133 cmd 0x0001e200 ctl 0x0001e302 bmdma
0x0001e600 irq 16
[   19.006055] ata2: SATA max UDMA/133 cmd 0x0001e400 ctl 0x0001e502 bmdma
0x0001e608 irq 16
[   19.006144] scsi0 : sata_via
[   19.211755] ata1: SATA link up 1.5 Gbps (SStatus 113 SControl 300)
[   19.382064] ATA: abnormal status 0x7F on port 0x0001e207
[   19.392764] ATA: abnormal status 0x7F on port 0x0001e207
[   19.559211] ata1.00: ATAPI, max UDMA/100
[   19.726873] ata1.00: configured for UDMA/100
[   19.726942] scsi1 : sata_via
[   19.934288] ata2: SATA link down 1.5 Gbps (SStatus 0 SControl 300)
[   19.944979] ATA: abnormal status 0x7F on port 0x0001e407
[   19.948040] scsi 0:0:0:0: CD-ROMHL-DT-ST DVDRAM GSA-H62N
CL00 PQ: 0 ANSI: 5
[   19.974628] sr0: scsi3-mmc drive: 48x/48x writer dvd-ram cd/rw xa/form2
cdda tray
[   19.974710] Uniform CD-ROM driver Revision: 3.20
[   19.974930] sr 0:0:0:0: Attached scsi CD-ROM sr0
[   19.978871] sr 0:0:0:0: Attached scsi generic sg0 type 5

I trimmed the IDE bits, but I'll provide a full dmesg if anyone thinks
that's likely to be enlightening.


>
> Questions:
>
> - Can you find out the type of that SATA controller ?


Let me know if the information above isn't what you were looking for and
I'll do some more digging around.

- Would it work with growisofs and DVD-R or unformatted
>   DVD-RW ?
>   (For these media the drive gets sent a mode page 05h,
>like with CD-R, CD-RW.)


I'll have to get back to you on that, I'll try that when I get in front of
the machine again in a few hours.

- Are you willing to do experiments with program cdrskin ?


At this stage I'll entertain any suggestions if it helps me figure out what
the root cause is.  I'd rather find a solution that uses cdrecord, but as
far as I'm concerned I'm still in the analysis phase of the problem, not the
part where I try to actually fix anything.  :-)

Thanks for the suggestions, please pass me along any instructions you have
on what I should try.

-- 
-Joe.


Re: No supported write modes with LG GSA-H62N SATA DVD+RW

2007-09-10 Thread Joe MacDonald
Thanks, Jörg,

Assuming there's no magic solution in the SCSI trace I just sent out, I'll
follow up in a few hours with the results of testing cdrecord in my WinXP
install and my try at it with the SchilliX CD.  I'm downloading it now and
it looks like it should be done by the time I'm ready to try it out.

-Joe.

On 9/10/07, Joerg Schilling <[EMAIL PROTECTED]> wrote:
>
> "Joe MacDonald" <[EMAIL PROTECTED]> wrote:
>
> > > Please try to run cdrecord on a different OS (e.g. Solaris or Win32).
> >
> >
> > I'm not at the affected machine right now, so it'll be a few more hours
> > before I get a chance, but I'll give that a try.  I don't have a Solaris
> x86
> > version, but since I'm already dual-booting into WinXP, trying a Win32
> > cdrecord should be easy.
>
> Thank you!
>
> > Your mail does not include any hint to the problem but other similar
> > > reports make it highly probable that this is caused by a bug in the
> Linux
> > > kernel.
> >
> >
> > I'll be happy to try whatever diagnostics you want me to try if we can
> find
> > the source of the problem.  I just want to either get it working or be
> > reasonably confident I know what the root cause is.  As you say here,
> > there's not much to go on right now, but my feeling has been that it was
> > something in the linux kernel as well.
>
> You may already run on Linux (via "script")
>
> cdrecord -checkdrive -V
>
> and remove the last part that only contains calls to "read buffer".
>
> The mode select calls show the right information for debugging.
>
> > When I get a chance to try this with Windows, I'll follow up.  It'll be
> six
> > hours or so at least before I get there.
>
> If it also does not work on Windows, I would like to see a test on
> Solaris.
>
> You may do this with without installing things by e.g. running a SchilliX
> CD
>
> ftp://ftp.berlios.de/pub/schillix/
>
> ftp://ftp.berlios.de/pub/schillix/SchilliX-0.5.2.iso.bz2
>
> if a bit old but should be sufficient for you for a simple test.
>
> The nice thing with Solaris is that you get more than 16 bytes of Sense
> data
> which may include a byte/bit pointer for "illegal byte in CDB" messages.
>
>
> Jörg
>
> --
> EMail:[EMAIL PROTECTED] (home) Jörg Schilling D-13353
> Berlin
>[EMAIL PROTECTED](uni)
>[EMAIL PROTECTED] (work) Blog:
> http://schily.blogspot.com/
> URL:  http://cdrecord.berlios.de/old/private/
> ftp://ftp.berlios.de/pub/schily
>



-- 
-Joe.


Re: No supported write modes with LG GSA-H62N SATA DVD+RW

2007-09-10 Thread Joerg Schilling
"Joe MacDonald" <[EMAIL PROTECTED]> wrote:

> > Please try to run cdrecord on a different OS (e.g. Solaris or Win32).
>
>
> I'm not at the affected machine right now, so it'll be a few more hours
> before I get a chance, but I'll give that a try.  I don't have a Solaris x86
> version, but since I'm already dual-booting into WinXP, trying a Win32
> cdrecord should be easy.

Thank you!

> Your mail does not include any hint to the problem but other similar
> > reports make it highly probable that this is caused by a bug in the Linux
> > kernel.
>
>
> I'll be happy to try whatever diagnostics you want me to try if we can find
> the source of the problem.  I just want to either get it working or be
> reasonably confident I know what the root cause is.  As you say here,
> there's not much to go on right now, but my feeling has been that it was
> something in the linux kernel as well.

You may already run on Linux (via "script")

cdrecord -checkdrive -V

and remove the last part that only contains calls to "read buffer".

The mode select calls show the right information for debugging.

> When I get a chance to try this with Windows, I'll follow up.  It'll be six
> hours or so at least before I get there.

If it also does not work on Windows, I would like to see a test on Solaris.

You may do this with without installing things by e.g. running a SchilliX CD

ftp://ftp.berlios.de/pub/schillix/

ftp://ftp.berlios.de/pub/schillix/SchilliX-0.5.2.iso.bz2

if a bit old but should be sufficient for you for a simple test.

The nice thing with Solaris is that you get more than 16 bytes of Sense data
which may include a byte/bit pointer for "illegal byte in CDB" messages.


Jörg

-- 
 EMail:[EMAIL PROTECTED] (home) Jörg Schilling D-13353 Berlin
   [EMAIL PROTECTED](uni)  
   [EMAIL PROTECTED] (work) Blog: http://schily.blogspot.com/
 URL:  http://cdrecord.berlios.de/old/private/ ftp://ftp.berlios.de/pub/schily


-- 
To UNSUBSCRIBE, email to [EMAIL PROTECTED]
with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]



Re: No supported write modes with LG GSA-H62N SATA DVD+RW

2007-09-10 Thread Joerg Schilling
"Joe MacDonald" <[EMAIL PROTECTED]> wrote:

> Thanks, Jörg,
>
> Assuming there's no magic solution in the SCSI trace I just sent out, I'll
> follow up in a few hours with the results of testing cdrecord in my WinXP
> install and my try at it with the SchilliX CD.  I'm downloading it now and
> it looks like it should be done by the time I'm ready to try it out.

The OpenSolaris release in this SchilliX release definitely does not correctly
handle the VIA SATA interface correctly except if in PATA compat mode.

I am sorry, but I have no idea how to switch.

Jörg

-- 
 EMail:[EMAIL PROTECTED] (home) Jörg Schilling D-13353 Berlin
   [EMAIL PROTECTED](uni)  
   [EMAIL PROTECTED] (work) Blog: http://schily.blogspot.com/
 URL:  http://cdrecord.berlios.de/old/private/ ftp://ftp.berlios.de/pub/schily


-- 
To UNSUBSCRIBE, email to [EMAIL PROTECTED]
with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]



Re: No supported write modes with LG GSA-H62N SATA DVD+RW

2007-09-10 Thread Joerg Schilling
"Joe MacDonald" <[EMAIL PROTECTED]> wrote:

> > There was one incident of a remedy:
> > The user exchanged the SATA controller which connected
> > the drive with the computer.
>
>
> I'm not completely opposed to that, but I've been considering that a
> non-solution so far since it appears that the controller isn't completely
> defective, just not completely functional in Linux.
>
> The controller I'm using is the on-board one with my motherboard, an older
> DFI K8M800, which makes it difficult to find out exactly what hardware the
> put on the board unless you know what you're looking for, and when it comes
> to SATA stuff, I don't, really.  lspci reports it as:
>
> 00:0f.0 RAID bus controller: VIA Technologies, Inc. VIA VT6420 SATA RAID
> Controller (rev 80)
> Subsystem: DFI Inc Unknown device 1004
> Control: I/O+ Mem+ BusMaster+ SpecCycle- MemWINV- VGASnoop- ParErr-

As I know that there have been problems with this controller on Solaris until 
very recently, did you try to switch the BIOS to run this controller in PATA
compat mode?

Jörg

-- 
 EMail:[EMAIL PROTECTED] (home) Jörg Schilling D-13353 Berlin
   [EMAIL PROTECTED](uni)  
   [EMAIL PROTECTED] (work) Blog: http://schily.blogspot.com/
 URL:  http://cdrecord.berlios.de/old/private/ ftp://ftp.berlios.de/pub/schily


-- 
To UNSUBSCRIBE, email to [EMAIL PROTECTED]
with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]



Re: No supported write modes with LG GSA-H62N SATA DVD+RW

2007-09-10 Thread Thomas Schmitt
Hi,

me: 
> > The user exchanged the SATA controller
Joe MacDonald:
> I'm not completely opposed to that, but I've been considering that a
> non-solution so far since it appears that the controller isn't completely
> defective, just not completely functional in Linux.

I will hardly tell you to throw away the
problematic controller before we found out
what's going on. Call it selfish curiosity. :))

A test swap would be of great interest though.
After all, there is only _one_ known success
with exchanging controllers. It can have had
many causes.


>  - Can you find out the type of that SATA controller ?
> Let me know if the information above isn't what you were looking for and

Since i got no clue about SATA either
it shall suffice for now.

> 00:0f.0 RAID bus controller: VIA Technologies, Inc. VIA VT6420 SATA RAID

... grepping ...

Andreas Klauer, Wed, 4 Apr 2007:
http://lists.debian.org/cdwrite/2007/04/msg00033.html
> I'm trying to get my Samsung SH-S183A SATA drive to work.
> ...
> The board is an ASUS A7V880, with a VIA VT6420 SATA RAID Controller
> (integrated into VT8237 southbridge)
Andreas Klauer, Mon, 2 Jul 2007:
http://lists.debian.org/cdwrite/2007/07/msg1.html
> No, I gave up on it. I just bought a VIA SATA PCI controller (VT6421), 
> which works for the device also in Linux.

I think the suspect got a name for now.


> At this stage I'll entertain any suggestions if it helps me figure out
> what the root cause is.  I'd rather find a solution that uses cdrecord,
> but as far as I'm concerned I'm still in the analysis phase of the
> problem, not the part where I try to actually fix anything.  :-)


(Preliminarily outdated, see below:
 Ok. I'll prepare a test program and tell your where
 to download the tarball.
)

If we find a remedy then it will be published of course,
so Joerg can decide what to do or not to do in cdrecord.

Maybe the remedy has to be found in the kernel.
I could back you with MMC knowlege if you post your
problem to LKML. With the kernel itself i have not
much of competence. My delivery point is ioctl(SGIO)
by which i send SPC/SBC/MMC commands and receive
eventual replies.
>From then on it's the job of kernel, bus, controller,
and drive.

Either my command is bad or that chain is bad.
Much points to the chain, meanwhile.

After all, commands of cdrecord, growisofs and
cdrskin did not succeed. All three are independend
in that aspect. Only common properties of all three
are the specs of MMC mode page 05h, the SPC command
MODE SELECT and the Linux ioctl SGIO.
(I anticipate growisofs on DVD-R[W] will not work.
For Andreas it didn't.)


New mail with SCSI trace of cdrecord.
There's a MODE SENSE of mode page 05h i.e. that's
already the experiment which i wanted to do next:

> Executing 'mode sense g1' command on Bus 0 Target 0, Lun 0 timeout 40s
> CDB:  5A 00 05 00 00 00 00 00 3C 00
> cmd finished after 0.001s timeout 40s
> Mode Sense Data 00 3A 41 00 00 00 00 00 05 32 61 04 08 10 00 00 00 00 00
> 00 00 00 00 96 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00
> 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00

The thing reports a page length of 32h.
That's exactly the page length which fails with
wodim and with cdrskin.

With Andreas i tested to send pages of lenght 32h
as well as of length 36h. Both failed with a
SCSI error about bad length.


That means it can last a bit longer until i have
an idea about the next experiment.
Currently i feel clueless.

Above mode sense data mean according to MMC-5 Table 664:
  Write Type is 1 = TAO, Burnfree available, no Test Write,
  Track mode 4, Data Block type 8 (= Mode 1),
  Audio Pause length 96h (=2 seconds)
This all looks totally normal.


Have a nice day :)

Thomas

-- 
Der GMX SmartSurfer hilft bis zu 70% Ihrer Onlinekosten zu sparen! 
Ideal für Modem und ISDN: http://www.gmx.net/de/go/smartsurfer


-- 
To UNSUBSCRIBE, email to [EMAIL PROTECTED]
with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]



Re: No supported write modes with LG GSA-H62N SATA DVD+RW

2007-09-10 Thread Joe MacDonald
On 9/10/07, Joe MacDonald <[EMAIL PROTECTED]> wrote:
>
> Thanks, Jörg,
>
> Assuming there's no magic solution in the SCSI trace I just sent out, I'll
> follow up in a few hours with the results of testing cdrecord in my WinXP
> install and my try at it with the SchilliX CD.  I'm downloading it now and
> it looks like it should be done by the time I'm ready to try it out.


So I downloaded a copy of the latest cdrtools from
http://www.student.tugraz.at/thomas.plank/ and gave it a try on my WinXP
install.  Other than the drive showing up at a different spot (2,0,0 rather
than 1,0,0) it seemed to behave the same as the -scanbus in Linux, but when
I went to burn an audio disc everything worked great.  So I'm guessing this
is an indication of a problem in the Linux device driver, maybe at the SATA
level, maybe in SG?

Do you still want me to try this with the Solaris CD?  I can't seem to find
any BIOS option that'll let me force it into PATA compat mode (which doesn't
really surprise me, the BIOS on this board seems curiously light on some
options), so I'm suspecting it's just not going to work since you've already
found problems with this SATA device in the past.

What would you like me to try next?

[EMAIL PROTECTED] ~/cdrtools-2.01.01a35-win32-bin
$ ./cdrecord.exe -scanbus
Cdrecord-ProDVD-ProBD-Clone 2.01.01a35 (i686-pc-cygwin) Copyright (C)
1995-2007
Jцrg Schilling
Using libscg version 'schily-0.9'.
scsibus0:
0,0,0 0) 'ST325082' '4A  ' '3.AA' 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) HOST ADAPTOR
scsibus1:
1,0,0   100) *
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) HOST ADAPTOR
scsibus2:
2,0,0   200) 'HL-DT-ST' 'DVDRAM GSA-H62N ' 'CL00' Removable CD-ROM
2,1,0   201) *
2,2,0   202) *
2,3,0   203) *
2,4,0   204) *
2,5,0   205) *
2,6,0   206) *
2,7,0   207) HOST ADAPTOR
scsibus3:
3,0,0   300) 'JY7912V ' 'HWG710G ' '1.0 ' Removable CD-ROM
3,1,0   301) 'JY7912V ' 'HWG710G ' '1.0 ' Removable CD-ROM
3,2,0   302) *
3,3,0   303) *
3,4,0   304) *
3,5,0   305) *
3,6,0   306) *
3,7,0   307) HOST ADAPTOR
scsibus4:
4,0,0   400) 'USB2.0  ' 'CF  CardReader  ' '' Removable Disk
4,1,0   401) *
4,2,0   402) *
4,3,0   403) *
4,4,0   404) *
4,5,0   405) *
4,6,0   406) *
4,7,0   407) HOST ADAPTOR
scsibus5:
5,0,0   500) 'USB2.0  ' 'CBO CardReader  ' '' Removable Disk
5,1,0   501) *
5,2,0   502) *
5,3,0   503) *
5,4,0   504) *
5,5,0   505) *
5,6,0   506) *
5,7,0   507) HOST ADAPTOR

[EMAIL PROTECTED] ~/cdrtools-2.01.01a35-win32-bin
$ ./cdrecord.exe -v speed=1 -audio dev=2,0,0 Blues\ Traveller/Carolina\
Blues.w
av Blues\ Traveller/01\ Felicia.wav Blues\ Traveller/02\ Justify\ the\
Thrill.w
av Blues\ Traveller/03\ Canadian\ Rose.wav Blues\ Traveller/04\ Business\
as\ U
sual.wav Blues\ Traveller/05\ Yours.wav Blues\ Traveller/06\ Psycho\ Joe\
\(Goe
s\ to\ the\ Electric\ Chair\).wav Blues\ Traveller/07\ Great\ Big\ World.wavBl
ues\ Traveller/08\ Battle\ of\ Someone.wav Blues\ Traveller/09\ Most\
Precariou
s.wav Blues\ Traveller/10\ The\ Gunfighter.wav Blues\ Traveller/11\ Last\
Night
\ I\ Dreamed.wav Blues\ Traveller/12\ Make\ My\ Way.wav
./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
defau
lts.
Cdrecord-ProDVD-ProBD-Clone 2.01.01a35 (i686-pc-cygwin) Copyright (C)
1995-2007
Jцrg Schilling
TOC Type: 0 = CD-DA
scsidev: '2,0,0'
scsibus: 2 target: 0 lun: 0
Using libscg version 'schily-0.9'.
SCSI buffer size: 64512
atapi: -1
Device type: Removable CD-ROM
Version: 0
Response Format: 2
Capabilities   :
Vendor_info: 'HL-DT-ST'
Identifikation : 'DVDRAM GSA-H62N '
Revision   : 'CL00'
Device seems to be: Generic mmc2 DVD-R/DVD-RW/DVD-RAM.
Current: CD-R
Profile: DVD-RAM
Profile: DVD-R sequential recording
Profile: DVD-R/DL sequential recording
Profile: DVD-R/DL layer jump recording
Profile: DVD-RW sequential recording
Profile: DVD-RW restricted overwrite
Profile: DVD+RW
Profile: DVD+R
Profile: DVD+R/DL
Profile: DVD-ROM
Profile: CD-R (current)
Profile: CD-RW
Profile: CD-ROM
Profile: Removable Disk
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
LAYE
R_JUMP
Drive buf size : 1053696 = 1029 KB
Drive pbuf size: 1966080 = 1920 KB
Drive DMA Speed: 14304 kB/s 81x CD 10x DVD 3x BD
FIFO size  : 4194304 = 4096 KB
Track 01

Re: No supported write modes with LG GSA-H62N SATA DVD+RW

2007-09-10 Thread Joerg Schilling
"Joe MacDonald" <[EMAIL PROTECTED]> wrote:

> On 9/10/07, Joe MacDonald <[EMAIL PROTECTED]> wrote:
> >
> > Thanks, Jörg,
> >
> > Assuming there's no magic solution in the SCSI trace I just sent out, I'll
> > follow up in a few hours with the results of testing cdrecord in my WinXP
> > install and my try at it with the SchilliX CD.  I'm downloading it now and
> > it looks like it should be done by the time I'm ready to try it out.
>
>
> So I downloaded a copy of the latest cdrtools from
> http://www.student.tugraz.at/thomas.plank/ and gave it a try on my WinXP
> install.  Other than the drive showing up at a different spot (2,0,0 rather
> than 1,0,0) it seemed to behave the same as the -scanbus in Linux, but when
> I went to burn an audio disc everything worked great.  So I'm guessing this
> is an indication of a problem in the Linux device driver, maybe at the SATA
> level, maybe in SG?

Correct, it must be a Linux device driver bug.

BTW: it still may be the well known bug with PATA that causes some commands to
fail with "illegal field in cdb".


> Do you still want me to try this with the Solaris CD?  I can't seem to find
> any BIOS option that'll let me force it into PATA compat mode (which doesn't
> really surprise me, the BIOS on this board seems curiously light on some
> options), so I'm suspecting it's just not going to work since you've already
> found problems with this SATA device in the past.
>
> What would you like me to try next?

Thank you for the test, if it works on win32, it cannot be a drive firmware bug
that may need special care and a workaround in cdrecord.

There is no need to run a Solaris test.

Jörg

-- 
 EMail:[EMAIL PROTECTED] (home) Jörg Schilling D-13353 Berlin
   [EMAIL PROTECTED](uni)  
   [EMAIL PROTECTED] (work) Blog: http://schily.blogspot.com/
 URL:  http://cdrecord.berlios.de/old/private/ ftp://ftp.berlios.de/pub/schily


-- 
To UNSUBSCRIBE, email to [EMAIL PROTECTED]
with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]



Re: No supported write modes with LG GSA-H62N SATA DVD+RW

2007-09-11 Thread Thomas Schmitt
Hi,

Joe MacDonald:
> So I'm guessing this is an indication of a problem
> in the Linux device driver, maybe at the SATA level,
> maybe in SG?

I would assume that SG is not to blame but rather
the SATA specific code. Possibly even specific to
the VIA VT6240 SATA controller.

Burning seems to work with a VIA VT6421 and with a
nVidia CK804 controller (i asked a friend about
his well working hardware with contemporary SuSE
Linux).

Do you plan to go on with exploring the problem ?

One would have to bring it to the attention of
the SCSI driver developers. For that one would have
to describe the command sent and the error reply
received. I assume cdrecord -V can tell both.

Else we could repeat the old experiment which i made
with a user on the debburn-devel list.
It resulted in this error
   5 1A 00 PARAMETER LIST LENGTH ERROR
when any mode page was sent.

If you post a bug report then please point me
to the place where the discussion happens.
(I would either start with a request for advise
at ubuntu-users or directly jump into the cold
water of LKML.)
I am very interested in learning which kernels
are affected and whether there is a remedy.


Non-technical hint:
It will be psycho-dynamically helpful if you
can point to growisofs or cdrskin as failing
programs too.
If the developers blame the problem on cdrecord
alone, then this should help to bring the discussion
back to a technical level.


Have a nice day :)

Thomas

-- 
Pt! Schon vom neuen GMX MultiMessenger gehört?
Der kanns mit allen: http://www.gmx.net/de/go/multimessenger


-- 
To UNSUBSCRIBE, email to [EMAIL PROTECTED]
with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]



Re: No supported write modes with LG GSA-H62N SATA DVD+RW

2007-09-11 Thread Joerg Schilling
"Thomas Schmitt" <[EMAIL PROTECTED]> wrote:

> Joe MacDonald:
> > So I'm guessing this is an indication of a problem
> > in the Linux device driver, maybe at the SATA level,
> > maybe in SG?
>
> I would assume that SG is not to blame but rather
> the SATA specific code. Possibly even specific to
> the VIA VT6240 SATA controller.

There is no known problem with drives on a classical SCSI transport.
This makes a SG problem less probable but not impossible.


> Non-technical hint:
> It will be psycho-dynamically helpful if you
> can point to growisofs or cdrskin as failing
> programs too.
> If the developers blame the problem on cdrecord
> alone, then this should help to bring the discussion
> back to a technical level.

If the Linux developers would take similar problems more seriously,
they could have been fixed long ago. If other programs do not fail,
this does not verify a problem in cdrecord. We have the case that
cdrdao is able to blank media on some platforms while cdrecord fails
with "illegal field in CDB" by sending exactly the same SCSI command. 
The fact that the Linux hackers claim that this is a cdrecord bug, just
disqualifies their skills.

Jörg

-- 
 EMail:[EMAIL PROTECTED] (home) Jörg Schilling D-13353 Berlin
   [EMAIL PROTECTED](uni)  
   [EMAIL PROTECTED] (work) Blog: http://schily.blogspot.com/
 URL:  http://cdrecord.berlios.de/old/private/ ftp://ftp.berlios.de/pub/schily


-- 
To UNSUBSCRIBE, email to [EMAIL PROTECTED]
with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]



Re: No supported write modes with LG GSA-H62N SATA DVD+RW

2007-09-11 Thread Bill Davidsen

Joerg Schilling wrote:

"Joe MacDonald" <[EMAIL PROTECTED]> wrote:

  

Thanks, Jörg,

Assuming there's no magic solution in the SCSI trace I just sent out, I'll
follow up in a few hours with the results of testing cdrecord in my WinXP
install and my try at it with the SchilliX CD.  I'm downloading it now and
it looks like it should be done by the time I'm ready to try it out.



The OpenSolaris release in this SchilliX release definitely does not correctly
handle the VIA SATA interface correctly except if in PATA compat mode.

I am sorry, but I have no idea how to switch.


Would it be possible and reasonable to at least detect the problem and 
output an informative error message? The sentence above is a good start, 
although I assume that this limitation is on all O/S. (Am I wrong?) 
Until or unless you are able to get the information you need on mode 
setting that would save you from future questions.


--
Bill Davidsen <[EMAIL PROTECTED]>
 "We have more to fear from the bungling of the incompetent than from
the machinations of the wicked."  - from Slashdot




Re: No supported write modes with LG GSA-H62N SATA DVD+RW

2007-09-11 Thread Bill Davidsen

Thomas Schmitt wrote:

Hi,

(On 3rd, 4th try:
 My previous messages seem not to have reached
 the list. 
 On 2nd try:

 I sent this message to list and poster a few
 hours before but it did not show up on the list.)



Joe MacDonald:
  

I've seen a couple of discussions about similar problems to mine with
different models (the H30N seemed to be a hot topic about six weeks ago)
but I haven't seen any suggestions that make things work (or at least
point to a cause of the failure) for me.



There was one incident of a remedy:
The user exchanged the SATA controller which connected
the drive with the computer.


  

Supported modes:
...
cdrecord: Drive does not support SAO recording.



In previous cases this has turned out to be the
result of failed attempts to set various write
modes.
The immediate error was with MMC command MODE SELECT
which returned an error condition saying that the
sent mode page 05h had the wrong length.

It has been tested with both lengths which are
described in the MMC-5 specs. No success.

  
I have seen this. Would it be reasonable to put debug in the kernel for 
this reproducible case, such that it's easier to track what the kernel 
is telling the controller?

Then the user bought the new controller.


  

- I bought this drive back in the spring.  It appears to work fine in
WinXP with Nero 7.something or other.



This is the really embarrassing part of those
error reports: The Windowers know a way to make
that combination of drive and controller work.
We don't - yet.

It might be that it is a bug with Linux and
certain SATA controllers.
But that would be a really smart bug. It disguises
very successfully as a bug of the drive.




Questions:

- Can you find out the type of that SATA controller ?
  
- Would it work with growisofs and DVD-R or unformatted

  DVD-RW ?
  (For these media the drive gets sent a mode page 05h,
   like with CD-R, CD-RW.)

- Are you willing to do experiments with program cdrskin ?
  I suppose them to be harmless, but they will at least
  cost some time and in worst case a reboot - if we manage
  to get the drive stuck by innovative combinations of
  MMC commands.
  (My next plan would be to fetch a mode page 05h and 
   to see how long the reply is. It would need to do

   some programming in the underlying libburn before we
   can start.)


Have a nice day :)
  


Thanks for being willing to help track this, it really would be nice to 
understand it. I'm guessing it's not in the driver itself but in the 
command filter, simply because this behavior has been seen in various 
hardware.


--
Bill Davidsen <[EMAIL PROTECTED]>
 "We have more to fear from the bungling of the incompetent than from
the machinations of the wicked."  - from Slashdot


--
To UNSUBSCRIBE, email to [EMAIL PROTECTED]
with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]



Re: No supported write modes with LG GSA-H62N SATA DVD+RW

2007-09-11 Thread Bill Davidsen

Joerg Schilling wrote:

If the Linux developers would take similar problems more seriously,
they could have been fixed long ago. If other programs do not fail,
this does not verify a problem in cdrecord. We have the case that
cdrdao is able to blank media on some platforms while cdrecord fails
with "illegal field in CDB" by sending exactly the same SCSI command. 
  


It may well be the same command, but not the same data in the page.


The fact that the Linux hackers claim that this is a cdrecord bug, just
disqualifies their skills.
  


If you believe that the exact command, with the exact same data, on the 
exact same alignment, run as the same real and effective user, on a 
device in the same mode, works for cdrdao and not cdrecord because of a 
kernel bug with identifies your software and treats it specially... I 
think that "disqualifies" your grip on reality. You are doing something 
different, and that's a technical problem, not an evil conspiracy.

Jörg

  

--

Bill Davidsen <[EMAIL PROTECTED]>
 "We have more to fear from the bungling of the incompetent than from
the machinations of the wicked."  - from Slashdot




Re: No supported write modes with LG GSA-H62N SATA DVD+RW

2007-09-11 Thread Thomas Schmitt
Hi,

me:
> > Non-technical hint:
> > It will be psycho-dynamically helpful if you
> > can point to growisofs or cdrskin as failing

Joerg Schilling:
> If other programs do not fail,
> this does not verify a problem in cdrecord.

This is well understood.

Vice versa the failure of other programs
would be a valuable information, if confirmed
by Joe.

If on the one hand cdrecord succeeds on XP
and on the other hand cdrecord and growisofs
fail on that Linux system, then it is obvious
that the common hub is in the combination of
kernel and controller.
The SCSI command's form is out of suspicion,
the controller-drive combination is ok.

So the central suspect is the transport,
beginning at ioctl(SGIO) and ending at the
VIA VT6240 SATA controller.


It will ease the communications with any
Linux kernel people if it is made clear
that they will not have to debug underneath
cdrecord.
They love you as much as you love them.

Therefore my hint to Joe.


To Joe MacDonald:

I would appreciate if you exposed yourself
to the rough social winds near the kernel.
We only have a chance to get a remedy if
there is a machine for hunting down the bug.
Yours is the only candidate, currently.

I am asking around where else one could get
advise for Ubuntu 7.04 and a particular SATA
controller.
(I myself use a kernel 2.4 with ide-scsi
emulation resp. usb-scsi.)

I have been pointed to Ubuntu kernel-team
  https://lists.ubuntu.com/mailman/listinfo/kernel-team
which despite its official purpose 
"coordinate and plan kernel uploads for Ubuntu"
has some requests and bug reports in its archives.

Maybe Bill has a proposal ?


Bill Davidsen:
> Would it be reasonable to put debug in the kernel for 
> this reproducible case, such that it's easier to track what the kernel 
> is telling the controller?

If you would team up with Joe and make his kernel
tell what it is thinking then i could provide
the program which sends the commands.

It would be interesting to see how many
mode page bytes are actually transmitted to the
drive, and/or whether the error message is possibly
fabricated by the driver.


> I'm guessing it's not in the driver itself but in the 
> command filter, simply because this behavior has been seen in various 
> hardware.

I am in doubt with the command filter theory.
My favorite suspect is that VIA VT6240 in conjunction
with its driver.
Whatever, it's mere guessing in front of a blackbox yet.


Have a nice day :)

Thomas


-- 
To UNSUBSCRIBE, email to [EMAIL PROTECTED]
with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]



Re: No supported write modes with LG GSA-H62N SATA DVD+RW

2007-09-11 Thread Joerg Schilling
Bill Davidsen <[EMAIL PROTECTED]> wrote:

> Thanks for being willing to help track this, it really would be nice to 
> understand it. I'm guessing it's not in the driver itself but in the 
> command filter, simply because this behavior has been seen in various 
> hardware.

It is definitely not the command filter.

Jörg

-- 
 EMail:[EMAIL PROTECTED] (home) Jörg Schilling D-13353 Berlin
   [EMAIL PROTECTED](uni)  
   [EMAIL PROTECTED] (work) Blog: http://schily.blogspot.com/
 URL:  http://cdrecord.berlios.de/old/private/ ftp://ftp.berlios.de/pub/schily


-- 
To UNSUBSCRIBE, email to [EMAIL PROTECTED]
with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]



Re: No supported write modes with LG GSA-H62N SATA DVD+RW

2007-09-11 Thread Joerg Schilling
Bill Davidsen <[EMAIL PROTECTED]> wrote:

> Joerg Schilling wrote:
> > If the Linux developers would take similar problems more seriously,
> > they could have been fixed long ago. If other programs do not fail,
> > this does not verify a problem in cdrecord. We have the case that
> > cdrdao is able to blank media on some platforms while cdrecord fails
> > with "illegal field in CDB" by sending exactly the same SCSI command. 
> >   
>
> It may well be the same command, but not the same data in the page.

You are uninformed as usual: blank unit does not have data in pages.

Jörg

-- 
 EMail:[EMAIL PROTECTED] (home) Jörg Schilling D-13353 Berlin
   [EMAIL PROTECTED](uni)  
   [EMAIL PROTECTED] (work) Blog: http://schily.blogspot.com/
 URL:  http://cdrecord.berlios.de/old/private/ ftp://ftp.berlios.de/pub/schily


-- 
To UNSUBSCRIBE, email to [EMAIL PROTECTED]
with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]



Re: No supported write modes with LG GSA-H62N SATA DVD+RW

2007-09-11 Thread Joe MacDonald
Hi Thomas,

On 9/11/07, Thomas Schmitt <[EMAIL PROTECTED]> wrote:
>
> Hi,
>
> Joe MacDonald:
> > So I'm guessing this is an indication of a problem
> > in the Linux device driver, maybe at the SATA level,
> > maybe in SG?
>
> I would assume that SG is not to blame but rather
> the SATA specific code. Possibly even specific to
> the VIA VT6240 SATA controller.
>
> Burning seems to work with a VIA VT6421 and with a
> nVidia CK804 controller (i asked a friend about
> his well working hardware with contemporary SuSE
> Linux).
>
> Do you plan to go on with exploring the problem ?


I absolutely do.  I realized that in a couple of my later replies to Jörg
yesterday I inadvertently cut the list from the recipient lists, I'll
probably send out an update on what he was able to learn from my further
testing with Windows for the sake of anyone coming by later and looking at
the list archives.

In short, though, burning with cdrecord works (I think as expected) in
Windows, which I think everyone can already guess from the exchanges on the
list.

Either way, it doesn't work in linux so doing backups to DVDs (which is
generally how I like doing my backups) becomes a pain, to say the least, if
I have to backup my ext3 partition data from Windows.  So I'm pretty
motivated to see this one through.  And buying an add-on SATA controller is
my last resort since that benefits no one but me.  :-)

Else we could repeat the old experiment which i made
> with a user on the debburn-devel list.
> It resulted in this error
>5 1A 00 PARAMETER LIST LENGTH ERROR
> when any mode page was sent.


That was the list of steps you sent yesterday?  I was focused on Jörg's
suggestions since my preference is to continue using what I know (that would
be cdrecord) but I'm all for gathering as much data as I can before I try to
approach SCSI and/or SATA developers.

If you post a bug report then please point me
> to the place where the discussion happens.


Will do.  My preference at this point would be to do it somewhere like the
Ubuntu bug tracker, but that will complicate things slightly since Ubuntu
ships wodim and most of my testing has been post-wodim-removal. But we'll
see how that goes.  I had remarkable success there before when I brought up
alsa problems.

-- 
-Joe.


Re: No supported write modes with LG GSA-H62N SATA DVD+RW

2007-09-11 Thread Joe MacDonald
Hey Bill,

On 9/11/07, Bill Davidsen <[EMAIL PROTECTED]> wrote:
>
> Thomas Schmitt wrote:
>
> > Joe MacDonald:
>
> >> Supported modes:
> >> ...
> >> cdrecord: Drive does not support SAO recording.
> >>
> >
> > In previous cases this has turned out to be the
> > result of failed attempts to set various write
> > modes.
> > The immediate error was with MMC command MODE SELECT
> > which returned an error condition saying that the
> > sent mode page 05h had the wrong length.
> >
> > It has been tested with both lengths which are
> > described in the MMC-5 specs. No success.
> >
> >
> I have seen this. Would it be reasonable to put debug in the kernel for
> this reproducible case, such that it's easier to track what the kernel
> is telling the controller?


Sure, be happy to.  Where would you suggest I start putting my printks?  I
have nearly no working knowledge of the SCSI components of the kernel so if
you've got pointers that'll be faster than me breaking out cscope and
navigating the code by hand, I'm all ears.

-- 
-Joe.


Re: No supported write modes with LG GSA-H62N SATA DVD+RW

2007-09-11 Thread Joerg Schilling
"Joe MacDonald" <[EMAIL PROTECTED]> wrote:

> In short, though, burning with cdrecord works (I think as expected) in
> Windows, which I think everyone can already guess from the exchanges on the
> list.
>
> Either way, it doesn't work in linux so doing backups to DVDs (which is
> generally how I like doing my backups) becomes a pain, to say the least, if
> I have to backup my ext3 partition data from Windows.  So I'm pretty
> motivated to see this one through.  And buying an add-on SATA controller is
> my last resort since that benefits no one but me.  :-)

If this is important for you and if someone could confirm that there is no 
problem with a different controller, it may make sense to spend ~ 20 Euro for
a new controller.

> That was the list of steps you sent yesterday?  I was focused on Jörg's
> suggestions since my preference is to continue using what I know (that would
> be cdrecord) but I'm all for gathering as much data as I can before I try to
> approach SCSI and/or SATA developers.

I would also like to see that this is carried to the driver developers.


> Will do.  My preference at this point would be to do it somewhere like the
> Ubuntu bug tracker, but that will complicate things slightly since Ubuntu
> ships wodim and most of my testing has been post-wodim-removal. But we'll
> see how that goes.  I had remarkable success there before when I brought up
> alsa problems.

Ubuntu is currently on a move back to cdrtools. This may take a while because 
there is still a lot of FUD against cdrtools that claims there is a license 
problem in cdrtools. If it would be sufficient, that Eben Moglen (law professor)
confirmed that what's done in cdrtools is perfectly OK and that not a single
lawyer confirmed the strange claims from the few Debian maintainers that 
attacked the cdrtools project, things would be easy. Unfortunately the FUD 
from these Debian maintainers was very effective and it takes long discussions 
to convince the related people.

Here is the current state of what is expected to appear in the free extensions
for Ubuntu hopefully soon.

http://ppa.launchpad.net/ubuntu-burning/ubuntu/pool/multiverse/c/cdrtools/
https://launchpad.net/~ubuntu-burning/+archive

This happened after I checked all Ubuntu bug reports against "cdrtools" which
currently really is wodim. It turned out that all bug reports that are really
related to the recording software (and not to the Linux kernel or other external
problems) are specific to the "cdrkit" package and cannot be found in cdrtools.

As wodim is unmaintained and as all packet related bugs disappear after 
upgrading 
to cdrtools, it will help many people that have become victims of the incident 
that has been initiated by few Debian maintainers.

Jörg

-- 
 EMail:[EMAIL PROTECTED] (home) Jörg Schilling D-13353 Berlin
   [EMAIL PROTECTED](uni)  
   [EMAIL PROTECTED] (work) Blog: http://schily.blogspot.com/
 URL:  http://cdrecord.berlios.de/old/private/ ftp://ftp.berlios.de/pub/schily


-- 
To UNSUBSCRIBE, email to [EMAIL PROTECTED]
with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]



Re: No supported write modes with LG GSA-H62N SATA DVD+RW

2007-09-11 Thread Thomas Schmitt
Hi,

me:
> > Else we could repeat the old experiment which i made
> >   with a user on the debburn-devel list.
> >   It resulted in this error
> >  5 1A 00 PARAMETER LIST LENGTH ERROR
> >   when any mode page was sent.
Joe MacDonald:
> That was the list of steps you sent yesterday? 

I learned from your remote experiment with the
empty tray on Linux that the drive gives no hint
of an unusual length of mode page 05h.

> > > Date: Mon, 10 Sep 2007 13:12:24 -0400

This here inquired the mode page 05h from the drive:

Executing 'mode sense g1' command on Bus 0 Target 0, Lun 0 timeout 40s
CDB:  5A 00 05 00 00 00 00 00 3C 00
cmd finished after 0.001s timeout 40s
Mode Sense Data 00 3A 41 00 00 00 00 00 05 32 61 04 08 10 00 00 00 00 00
00 00 00 00 96 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00
00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00


I also believe to see the failed attempts to
set that mode page for testing the available
write modes.
Search for: "CDB:  55 10 00 00 00 00 00 00 3C"

Executing 'mode select g1' command on Bus 0 Target 0, Lun 0 timeout 40s
CDB:  55 10 00 00 00 00 00 00 3C 00
cdrecord: Input/output error. mode select g1: scsi sendcmd: no error
CDB:  55 10 00 00 00 00 00 00 3C 00
status: 0x2 (CHECK CONDITION)
Sense Bytes: 70 00 05 00 00 00 00 0A 55 00 00 0C 1A 00 00 00
Sense Key: 0x5 Illegal Request, Segment 0
Sense Code: 0x1A Qual 0x00 (parameter list length error) Fru 0x0
Sense flags: Blk 0 (not valid)
resid: 60
cmd finished after 0.003s timeout 40s

We don't see the mode page itself, but the Parameter
List Length 3Ch in byte 7+8 of the CDB would match a
page length of 32h which is typical for mode page 05h
and also is the replied length above.


We see several of these calls. All fail with
Sense Key: 0x5 Illegal Request, Segment 0
Sense Code: 0x1A Qual 0x00 (parameter list length error) Fru 0x0

The same was experienced by cdrskin a few months ago.
So i would say the symptoms are stable and reproducible
on several individual systems.

So the bug is ripe to be shown to the kernel people.


> Ubuntu ships wodim and most of my testing has been post-wodim-removal.

I am quite sure that you will see the same failing
commands in a trace of wodim. My first encounter with
the problem was on debburn-devel list about wodim.
Option -V should work with wodim too.

I am looking forward in great hope to your further
activities in this case.


Have a nice day :)

Thomas


-- 
To UNSUBSCRIBE, email to [EMAIL PROTECTED]
with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]



Fwd: No supported write modes with LG GSA-H62N SATA DVD+RW

2007-09-11 Thread Joe MacDonald
I'd mentioned that I'd forward the exchange that I accidentally took
off-list yesterday for the benefit of anyone following along or coming by
later and finding this in the archives.  I won't bother sending them all,
just two that seem to have the most relevant information.

-- Forwarded message --
From: Joe MacDonald <[EMAIL PROTECTED]>
Date: Sep 10, 2007 8:03 PM
Subject: Re: No supported write modes with LG GSA-H62N SATA DVD+RW
To: Joerg Schilling <[EMAIL PROTECTED]>



On 9/10/07, Joerg Schilling <[EMAIL PROTECTED]> wrote:
>
> "Joe MacDonald" <[EMAIL PROTECTED]> wrote:
>
> > Okay, so where does this leave me in terms of writing CDs/DVDs in
> Linux?  Is
> > this pretty much out of your hands since it looks very much like
> something
> > below the cdrecord level, or is there something more I can do to narrow
> this
> > down (hopefully to something fixable)?  Or am I looking to take this up
> with
> > the kernel folks now?
>
> The difference between Linux & Win32 is definitely below the cdrecord
> code.
>
> I have one question: Did you run this with administrator privileges?


In Windows?  Yes, the account I log in as has admin privileges.

Could could try to prepend ASPI: vs. SPTI: to the dev= parameter
> to verify whether this was ASPI or SPTI?


Sure thing.  It seems less happy now:

$ ./cdrecord.exe -v speed=1 -audio dev=ASPI:2,0,0 tmp/*.wav
./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.
Cdrecord-ProDVD-ProBD-Clone 2.01.01a35 (i686-pc-cygwin) Copyright (C)
1995-2007 Jцrg Schilling
TOC Type: 0 = CD-DA
scsidev: 'ASPI:2,0,0'
devname: 'ASPI'
scsibus: 2 target: 0 lun: 0
Can not load ASPI driver! ./cdrecord: No such file or directory. Cannot open
oruse SCSI driver.
./cdrecord: For possible targets try 'cdrecord -scanbus'. Make sure you are
root.
./cdrecord: For possible transport specifiers try 'cdrecord dev=help'.

But everything is fine if I pre-pend SPTI: or leave the dev= option bare, as
in my previous test.  Does that tell you anything useful?

-J.

Unless the win32 drivers modify the SCSI commands as a workaround, the
> problem
> must be inside the linux kernel.
>
> If the related Linux drivers are developed in a professional environment,
> then
> the developer should have a logic analyzer that allows to snoop at SATA
> level
> and should be able to fetch the drive you have.
>
> Jörg
>
> --
> EMail:[EMAIL PROTECTED] (home) Jörg Schilling D-13353
> Berlin
>[EMAIL PROTECTED] (uni)
>[EMAIL PROTECTED] (work) Blog:
> http://schily.blogspot.com/
> URL:   http://cdrecord.berlios.de/old/private/
> ftp://ftp.berlios.de/pub/schily
>



-- 
-Joe.

-- 
-Joe.


Fwd: No supported write modes with LG GSA-H62N SATA DVD+RW

2007-09-11 Thread Joe MacDonald
The second of the two messages I planned to add back into the list.

-- Forwarded message --
From: Joerg Schilling <[EMAIL PROTECTED]>
Date: Sep 11, 2007 6:41 AM
Subject: Re: No supported write modes with LG GSA-H62N SATA DVD+RW
To: [EMAIL PROTECTED]

"Joe MacDonald" <[EMAIL PROTECTED]> wrote:

> In Windows?  Yes, the account I log in as has admin privileges.
>
> Could could try to prepend ASPI: vs. SPTI: to the dev= parameter
> > to verify whether this was ASPI or SPTI?
>

OK, thank you.

I know that Win32 emulates SCSI drives on top of ATA drives when using
SPTI. Inn theory, Win32 could implement a workaround but I believe that
in case of mode select, this is less probable.

Jörg

--
EMail:[EMAIL PROTECTED] (home) Jörg Schilling D-13353 Berlin
   [EMAIL PROTECTED](uni)
   [EMAIL PROTECTED] (work) Blog:
http://schily.blogspot.com/
URL:  http://cdrecord.berlios.de/old/private/
ftp://ftp.berlios.de/pub/schily


-- 
-Joe.


Re: No supported write modes with LG GSA-H62N SATA DVD+RW

2007-09-11 Thread Thomas Schmitt
Hi,

i see one potential MODE SELECT with page 05h succeeding
in the cdrecord command trace. It is the first of all:

Executing 'mode select g1' command on Bus 0 Target 0, Lun 0 timeout 40s
CDB:  55 10 00 00 00 00 00 00 3C 00
cmd finished after 0.002s timeout 40s

Shortly after, the setting gets inquired:

Executing 'mode sense g1' command on Bus 0 Target 0, Lun 0 timeout 40s
CDB:  5A 00 05 00 00 00 00 00 3C 00
cmd finished after 0.001s timeout 40s
Mode Sense Data 00 3A 41 00 00 00 00 00 05 32 61 04 08 10 00 00 00 00 00
00 00 00 00 96 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00
00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00

This is set to Write Type TAO ("61" says so).

Later there appears this message:

> Supported modes: SAO

To Joerg:
Is this hardcoded for DVD media ?
Or did i oversee the MODE SELECT which succeeded
in setting a SAO mode page 05h ?


Have a nice day :)

Thomas


-- 
To UNSUBSCRIBE, email to [EMAIL PROTECTED]
with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]



Re: No supported write modes with LG GSA-H62N SATA DVD+RW

2007-09-12 Thread Bill Davidsen

Joerg Schilling wrote:

Bill Davidsen <[EMAIL PROTECTED]> wrote:

  
Thanks for being willing to help track this, it really would be nice to 
understand it. I'm guessing it's not in the driver itself but in the 
command filter, simply because this behavior has been seen in various 
hardware.



It is definitely not the command filter.
  


So are you saying that all of the drivers which show this behavior have 
the same bug, added by chance by the various people who wrote them, or 
??? Will you share your reason for being certain that the problem is not 
in the shared code?


--
bill davidsen <[EMAIL PROTECTED]>
 CTO TMR Associates, Inc
 Doing interesting things with small computers since 1979


--
To UNSUBSCRIBE, email to [EMAIL PROTECTED]
with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]



Re: No supported write modes with LG GSA-H62N SATA DVD+RW

2007-09-12 Thread Bill Davidsen

Joerg Schilling wrote:

Bill Davidsen <[EMAIL PROTECTED]> wrote:

  

Joerg Schilling wrote:


If the Linux developers would take similar problems more seriously,
they could have been fixed long ago. If other programs do not fail,
this does not verify a problem in cdrecord. We have the case that
cdrdao is able to blank media on some platforms while cdrecord fails
with "illegal field in CDB" by sending exactly the same SCSI command. 
  
  

It may well be the same command, but not the same data in the page.



You are uninformed as usual: blank unit does not have data in pages.

  
The original post was talking about sending a mode page, so I have no 
idea what you are talking about.

See <[EMAIL PROTECTED]> for what we're talking about.

--
bill davidsen <[EMAIL PROTECTED]>
 CTO TMR Associates, Inc
 Doing interesting things with small computers since 1979


--
To UNSUBSCRIBE, email to [EMAIL PROTECTED]
with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]



Re: No supported write modes with LG GSA-H62N SATA DVD+RW

2007-09-12 Thread Bill Davidsen

Joe MacDonald wrote:

Hi Thomas,

On 9/11/07, *Thomas Schmitt* <[EMAIL PROTECTED] 
> wrote:


Hi,

Joe MacDonald:
> So I'm guessing this is an indication of a problem
> in the Linux device driver, maybe at the SATA level,
> maybe in SG?

I would assume that SG is not to blame but rather
the SATA specific code. Possibly even specific to
the VIA VT6240 SATA controller.

Burning seems to work with a VIA VT6421 and with a
nVidia CK804 controller (i asked a friend about
his well working hardware with contemporary SuSE
Linux).

Do you plan to go on with exploring the problem ?


I absolutely do.  I realized that in a couple of my later replies to 
Jörg yesterday I inadvertently cut the list from the recipient lists, 
I'll probably send out an update on what he was able to learn from my 
further testing with Windows for the sake of anyone coming by later 
and looking at the list archives.


In short, though, burning with cdrecord works (I think as expected) in 
Windows, which I think everyone can already guess from the exchanges 
on the list.


Either way, it doesn't work in linux so doing backups to DVDs (which 
is generally how I like doing my backups) becomes a pain, to say the 
least, if I have to backup my ext3 partition data from Windows.  So 
I'm pretty motivated to see this one through.  And buying an add-on 
SATA controller is my last resort since that benefits no one but me.  :-)


You might as well try growisofs, it's easy to learn, will create an ISO 
image with mkisofs if asked, or burn a prepared image, or burn from a 
pipe. Only drawback is burning DVD only, no CD. For backup that's 
unlikely to be an issue.
I understand your wish to stay with the familiar, but at the moment 
growisofs would be a data point as to works or not, and a way for you to 
move forward. And if the bug can be shown in other software, kernel 
developers might look at it more readily.


Else we could repeat the old experiment which i made
with a user on the debburn-devel list.
It resulted in this error
   5 1A 00 PARAMETER LIST LENGTH ERROR
when any mode page was sent.


That was the list of steps you sent yesterday?  I was focused on 
Jörg's suggestions since my preference is to continue using what I 
know (that would be cdrecord) but I'm all for gathering as much data 
as I can before I try to approach SCSI and/or SATA developers.


If you post a bug report then please point me
to the place where the discussion happens. 



Will do.  My preference at this point would be to do it somewhere like 
the Ubuntu bug tracker, but that will complicate things slightly since 
Ubuntu ships wodim and most of my testing has been post-wodim-removal. 
But we'll see how that goes.  I had remarkable success there before 
when I brought up alsa problems.
Does ubuntu still use wodim? I thought that there was a move to go back 
to cdrtools.


--
bill davidsen <[EMAIL PROTECTED]>
 CTO TMR Associates, Inc
 Doing interesting things with small computers since 1979




Re: No supported write modes with LG GSA-H62N SATA DVD+RW

2007-09-13 Thread Thomas Schmitt
Hi,

> So am I doing something wrong, or is this behaviour consistent with what
> we might expect out of the problem, based on what we were seeing in
> cdrecord?

It is the same failure as with cdrecord:

> cdrecord: Input/output error. mode select g1: scsi sendcmd: no error
> ...
> Sense Key: 0x5 Illegal Request, Segment 0
> Sense Code: 0x1A Qual 0x00 (parameter list length error) Fru 0x0

growisofs:
> :-[ MODE SELECT failed with SK=5h/ASC=1Ah/ACQ=00h]: Input/output error

Same command attempted, same error codes returned.


If i remember right, growisofs encountered a different
error when writing to DVD+RW (which needs no mode page 05h).


Have a nice day :)

Thomas
 


-- 
To UNSUBSCRIBE, email to [EMAIL PROTECTED]
with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]



Re: No supported write modes with LG GSA-H62N SATA DVD+RW

2007-09-14 Thread Bill Davidsen

Joe MacDonald wrote:

Hi guys,

I'll follow up the other replies in a bit when I get more information, 
but I thought I'd try to get the answer to the growisofs requests now.


On 9/12/07, * Bill Davidsen* <[EMAIL PROTECTED] 
> wrote:


Joe MacDonald wrote:
> Either way, it doesn't work in linux so doing backups to DVDs (which
> is generally how I like doing my backups) becomes a pain, to say the
> least, if I have to backup my ext3 partition data from Windows.  So
> I'm pretty motivated to see this one through.  And buying an add-on
> SATA controller is my last resort since that benefits no one but
me.  :-)

You might as well try growisofs, it's easy to learn, will create
an ISO
image with mkisofs if asked, or burn a prepared image, or burn from a
pipe. Only drawback is burning DVD only, no CD. For backup that's
unlikely to be an issue.


So I tried a couple of different options, first with an ISO I had 
created a while back and second with just a pile of files on my hard 
disk that I wanted to back up.  Neither one resulted in any level of 
success, but I'm not completely convinced this wasn't a case of pilot 
error.  So here's my results:


[EMAIL PROTECTED]:/tmp# file backup.iso
backup.iso: ISO 9660 CD-ROM filesystem data UDF filesystem data 
(unknown version, id 'NSR0

[EMAIL PROTECTED]:/tmp# ls -lh backup.iso
-rw-r--r-- 2 root root 3.7G 2006-06-06 00:14 backup.iso
[EMAIL PROTECTED]:/tmp# ls -l /dev/dvd*
lrwxrwxrwx 1 root root 4 2007-09-13 12:57 /dev/dvd -> scd0
lrwxrwxrwx 1 root root 4 2007-09-13 12:57 /dev/dvdrw -> scd0
[EMAIL PROTECTED]:/tmp# ls -l /dev/scd0
brw-rw 1 root cdrom 11, 0 2007-09-13 12:57 /dev/scd0
[EMAIL PROTECTED]:/tmp# growisofs -Z /dev/dvd -J -R -input-charset=iso8859-1 
./backup.iso
Executing 'genisoimage -J -R -input-charset=iso8859-1 ./backup.iso | 
builtin_dd of=/dev/dvd obs=32k seek=0'

:-[ MODE SELECT failed with SK=5h/ASC=1Ah/ACQ=00h]: Input/output error

Which is when I started to think I must be doing something wrong. 


Since it was an ISO image, you didn't want to do anything but burn it...
  growisofs -Z /dev/dvd=backup.iso


Anyway, my second test, was with the collection of .flac files:

[EMAIL PROTECTED] :/tmp# growisofs -Z /dev/dv -speed=1 -J -R 
-input-charset=iso8859 "/home/joe/cds/Matthew Good" 
"/home/joe/cds/Nine Inch Nails/" "/home/joe/cd

s/The Tragically Hip/"
Using IN_A_000 for  /In a Coma (disc 2) (In a Coma (disc 1))
:-[ MODE SELECT failed with SK=5h/ASC=1Ah/ACQ=00h]: Input/output error

And I'm not seeing anything interesting in dmesg:

[EMAIL PROTECTED]:/tmp# dmesg
[___snip___]
[   31.043343] libata version 2.20 loaded.
[   31.044366] sata_via :00:0f.0: version 2.1
[   31.044665] ACPI: PCI Interrupt Link [ALKA] enabled at IRQ 20
[   31.044738] ACPI: PCI Interrupt :00:0f.0[B] -> Link [ALKA] -> 
GSI 20 (level, low) -> IRQ 16

[   31.044924] sata_via :00:0f.0: routed to hard irq line 11
[   31.045040] ata1: SATA max UDMA/133 cmd 0x0001e200 ctl 0x0001e302 
bmdma 0x0001e600 irq 16
[   31.045140] ata2: SATA max UDMA/133 cmd 0x0001e400 ctl 0x0001e502 
bmdma 0x0001e608 irq 16

[   31.045229] scsi0 : sata_via
[   31.062598] usbcore: registered new interface driver usbfs
[   31.062686] usbcore: registered new interface driver hub
[   31.062768] usbcore: registered new device driver usb
[   31.092812] USB Universal Host Controller Interface driver v3.0
[   31.114790] via-rhine.c:v1.10-LK1.4.2 Sept-11-2006 Written by 
Donald Becker

[   31.125811] ieee1394: Initialized config rom entry `ip1394'
[   31.245121] ata1: SATA link up 1.5 Gbps (SStatus 113 SControl 300)
[   31.247832] Floppy drive(s): fd0 is 1.44M
[   31.278089] FDC 0 is a post-1991 82077
[   31.411458] ATA: abnormal status 0x7F on port 0x0001e207
[   31.422159] ATA: abnormal status 0x7F on port 0x0001e207
[   31.584631] ata1.00: ATAPI, max UDMA/100
[   31.748318] ata1.00: configured for UDMA/100
[   31.748388] scsi1 : sata_via
[   31.951772] ata2: SATA link down 1.5 Gbps (SStatus 0 SControl 300)
[   31.962463] ATA: abnormal status 0x7F on port 0x0001e407
[   31.965375] scsi 0:0:0:0: CD-ROMHL-DT-ST DVDRAM 
GSA-H62N  CL00 PQ: 0 ANSI: 5

[   31.967496] VP_IDE: IDE controller at PCI slot :00: 0f.1
[   31.967591] ACPI: PCI Interrupt :00:0f.1[A] -> Link [ALKA] -> 
GSI 20 (level, low) -> IRQ 16

[   31.967774] VP_IDE: chipset revision 6
[   31.967835] VP_IDE: not 100% native mode: will probe irqs later
[   31.967907] VP_IDE: VIA vt8237 (rev 00) IDE UDMA133 controller on 
pci:00:0f.1
[   31.967987] ide0: BM-DMA at 0xe800-0xe807, BIOS settings: 
hda:DMA, hdb:pio
[   31.968159] ide1: BM-DMA at 0xe808-0xe80f, BIOS settings: 
hdc:pio, hdd:pio

[   31.968328] Probing IDE interface ide0...
[   31.994222] sr0: scsi3-mmc drive: 125x/125x writer dvd-ram cd/rw 
xa/form2 cdda tray

[   31.994304] Uniform CD-ROM driver Revision: 3.20
[   31.994544] sr 0:0:0:0: Attached scsi CD-ROM sr0
[   31.998445] 

Re: No supported write modes with LG GSA-H62N SATA DVD+RW

2007-09-15 Thread mike-a

For what it is worth I have the following to add to all the discussion.
I have a pioneer 212 (sata) DVD which I have tried on two computers an ECS
KV2 Lite +Dualcore 3800  and an MSI K8T Neo +Turion MT32 both running Fedora
7.
Neither cdrecord nor growisofs work on CD, DVD-R nor DVD+R (various errors)
WIN XP works, but only if DMA is disabled for the drive. I get about 2.5x
write speed with the 3800+.
Both machines have a VIA VT6420 Raid controller (in ide mode)
I tried my burner on a friends machine with nvidia sata controller and
everything worked fine. (I bought the 212 because he had several on several
machines and they worked fine)

It apeared that when writing (which succeded on dvd+r - just incorrect data
and occasionaly some data was written onto a CD) that the data was prepended
by 32 bytes every 32K on the DVD-r and some smaller number (i now forget) on
a CD
  2a 00 00 00 00 00 00 00  10 00 00 00 00 00 00 00 
|*...|
0010  00 23 05 40 00 00 00 10  00 23 05 40 00 00 00 10 
|[EMAIL PROTECTED]@|

8000  2a 00 00 00 00 10 00 00  10 00 00 00 00 10 00 00 
|*...|
8010  00 00 00 00 00 00 00 00  00 00 00 00 00 00 00 00 
||

0001  2a 00 00 00 00 20 00 00  10 00 00 00 00 20 00 00  |* ...
..|
00010010  00 00 00 00 00 00 00 00  00 00 00 00 00 00 00 00 
||
etc.
The 32 bytes of data at the end were lost. This was not entirely consistant
and occassioanly a full buffer was written correctly.
It looks like I eill need to get a PATA burner!
mike

-- 
View this message in context: 
http://www.nabble.com/No-supported-write-modes-with-LG-GSA-H62N-SATA-DVD%2BRW-tf4410956.html#a12691688
Sent from the cdwrite mailing list archive at Nabble.com.


-- 
To UNSUBSCRIBE, email to [EMAIL PROTECTED]
with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]



Re: No supported write modes with LG GSA-H62N SATA DVD+RW

2007-09-15 Thread Thomas Schmitt
Hi,

mike-a:
> I have a pioneer 212 (sata) DVD
> running Fedora 7
> Neither cdrecord nor growisofs work
> WIN XP works, but only if DMA is disabled for the drive
> Both machines have a VIA VT6420
> I tried my burner on a friends machine with nvidia sata
> controller and everything worked fine.

This matches well the image which emerges
for this issue.
Trouble maker is the VT6420 with Linux,
not the drives, not the burner software.


>   2a 00 00 00 00 00 00 00  10 00
> 8000  2a 00 00 00 00 10 00 00  10 00
> 0001  2a 00 00 00 00 20 00 00  10 00

Arghh ! These are SCSI commands 2Ah WRITE 10
which send 16 blocks = 32 KB of data to LBA
addresses 0, 16, 32.
Something (the controller ?) did put copies of the
commands at the head of the data payload.

This would explain why we get parameter
length errors with mode page 05h.
The drive really receives too many bytes.


> The 32 bytes of data at the end were lost.

The write command announced 32 KiB. So what is
surplus at the beginning of the payload will
get truncated at the end ... somehow.
(I wonder why this happened quite gracefully
and did not get everything stuck, though.)


Thanks for this report. It confirms the suspicion
against the VT6420 controller and it even gives
an idea what is actually going wrong.


> It looks like I will need to get a PATA burner!

Or you get that "VIA SATA PCI controller (VT6421)"
which brought the remedy for Andreas Klauer in July.


Have a nice day :)

Thomas


-- 
To UNSUBSCRIBE, email to [EMAIL PROTECTED]
with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]



Fwd: No supported write modes with LG GSA-H62N SATA DVD+RW

2007-09-15 Thread Joe MacDonald
Once again I accidentally cut the list of my replies.

-- Forwarded message --
From: Joe MacDonald <[EMAIL PROTECTED]>
Date: Sep 14, 2007 10:58 AM
Subject: Re: No supported write modes with LG GSA-H62N SATA DVD+RW
To: Bill Davidsen <[EMAIL PROTECTED]>



On 9/14/07, Bill Davidsen <[EMAIL PROTECTED]> wrote:
>
> Joe MacDonald wrote:
> > Hi guys,
> >
> > I'll follow up the other replies in a bit when I get more information,
> > but I thought I'd try to get the answer to the growisofs requests now.
> >
> > On 9/12/07, * Bill Davidsen* <[EMAIL PROTECTED]
> > <mailto:[EMAIL PROTECTED]>> wrote:
> >
> > Joe MacDonald wrote:
> > > Either way, it doesn't work in linux so doing backups to DVDs
> (which
> > > is generally how I like doing my backups) becomes a pain, to say
> the
> > > least, if I have to backup my ext3 partition data from
> Windows.  So
> > > I'm pretty motivated to see this one through.  And buying an
> add-on
> > > SATA controller is my last resort since that benefits no one but
> > me.  :-)
> >
> > You might as well try growisofs, it's easy to learn, will create
> > an ISO
> > image with mkisofs if asked, or burn a prepared image, or burn from
> a
> > pipe. Only drawback is burning DVD only, no CD. For backup that's
> > unlikely to be an issue.
> >
> >
> > So I tried a couple of different options, first with an ISO I had
> > created a while back and second with just a pile of files on my hard
> > disk that I wanted to back up.  Neither one resulted in any level of
> > success, but I'm not completely convinced this wasn't a case of pilot
> > error.  So here's my results:
> >
> > [EMAIL PROTECTED]:/tmp# file backup.iso
> > backup.iso: ISO 9660 CD-ROM filesystem data UDF filesystem data
> > (unknown version, id 'NSR0
> > [EMAIL PROTECTED]:/tmp# ls -lh backup.iso
> > -rw-r--r-- 2 root root 3.7G 2006-06-06 00:14 backup.iso
> > [EMAIL PROTECTED]:/tmp# ls -l /dev/dvd*
> > lrwxrwxrwx 1 root root 4 2007-09-13 12:57 /dev/dvd -> scd0
> > lrwxrwxrwx 1 root root 4 2007-09-13 12:57 /dev/dvdrw -> scd0
> > [EMAIL PROTECTED]:/tmp# ls -l /dev/scd0
> > brw-rw 1 root cdrom 11, 0 2007-09-13 12:57 /dev/scd0
> > [EMAIL PROTECTED]:/tmp# growisofs -Z /dev/dvd -J -R -input-charset=iso8859-1
> > ./backup.iso
> > Executing 'genisoimage -J -R -input-charset=iso8859-1 ./backup.iso |
> > builtin_dd of=/dev/dvd obs=32k seek=0'
> > :-[ MODE SELECT failed with SK=5h/ASC=1Ah/ACQ=00h]: Input/output error
> >
> > Which is when I started to think I must be doing something wrong.
>
> Since it was an ISO image, you didn't want to do anything but burn it...
>growisofs -Z /dev/dvd=backup.iso


Ah, okay.  I wasn't clear from the manpage if that /dev/dvd=backup.iso was
for any ol' ISO image or just one that was DVD-video formatted.  It seemed
odd to me that it would be, but there seems to be a lot of stuff happening
behind the curtain for growisofs.  :-)

Anyway, just re-tried it (remembered to leave the machine up and with a
blank DVD in the tray today) and got what looks like the same response:

[EMAIL PROTECTED]:/tmp# growisofs -Z /dev/dvd=backup.iso
Executing 'builtin_dd if= backup.iso of=/dev/dvd obs=32k seek=0'
:-[ MODE SELECT failed with SK=5h/ASC=1Ah/ACQ=00h]: Input/output error

> Anyway, my second test, was with the collection of .flac files:
> >
> > [EMAIL PROTECTED] :/tmp# growisofs -Z /dev/dv -speed=1 -J -R
> > -input-charset=iso8859 "/home/joe/cds/Matthew Good"
> > "/home/joe/cds/Nine Inch Nails/" "/home/joe/cd
> > s/The Tragically Hip/"
> > Using IN_A_000 for  /In a Coma (disc 2) (In a Coma (disc 1))
> > :-[ MODE SELECT failed with SK=5h/ASC=1Ah/ACQ=00h]: Input/output error
> >
> > And I'm not seeing anything interesting in dmesg:
> >
> > [EMAIL PROTECTED]:/tmp# dmesg
> > [___snip___]
> > [   31.043343] libata version 2.20 loaded.
> > [   31.044366] sata_via :00:0f.0: version 2.1
> > [   31.044665] ACPI: PCI Interrupt Link [ALKA] enabled at IRQ 20
> > [   31.044738] ACPI: PCI Interrupt :00:0f.0[B] -> Link [ALKA] ->
> > GSI 20 (level, low) -> IRQ 16
> > [   31.044924] sata_via :00:0f.0: routed to hard irq line 11
> > [   31.045040] ata1: SATA max UDMA/133 cmd 0x0001e200 ctl 0x0001e302
> > bmdma 0x0001e600 irq 16
> > [   31.045140] ata2: SATA max UDMA/133 cmd 0x0001e400 ctl 0x0001e502
> > bmdma 0x0001e608 irq 16
> > [   31.