mirror of https://lore.kernel.org/lkml/
 help / color / mirror / Atom feed
From: "Gustavo Guillermo Pérez" <gustavo@compunauta.com>
To: linux-usb-devel@lists.sourceforge.net
Cc: Alan Stern <stern@rowland.harvard.edu>,
	Jeff Garzik <jgarzik@pobox.com>,
	Linux Kernel Mailing List <linux-kernel@vger.kernel.org>
Subject: Re: [linux-usb-devel] Re: /dev/sr0 not ready, but working
Date: Tue, 22 Nov 2005 20:21:58 -0600	[thread overview]
Message-ID: <200511222021.59075.gustavo@compunauta.com> (raw)
In-Reply-To: <Pine.LNX.4.44L0.0511221349360.21136-100000@iolanthe.rowland.org>

El Martes, 22 de Noviembre de 2005 12:56, Alan Stern escribió:
> On Tue, 22 Nov 2005, Gustavo Guillermo Pérez wrote:
> > Yes, I do the same operations as iee1394 and USB, and here we go:
> > 1) ieee1394 Dirty DVD+RW ad UdfFileSystem without pktcdvd cause +rw
> > No Real problems, the errors on logical sectors was and old bad mount,
> > but the second one writing 5 o 6 MB of a lot of small files does not
> > produce the error.
> > 2) ieee1394 Normal growisofs -Z /dev/sr0 -J -r /folder
> > No errors on the media, writing as iso not packet.
> > The error appears while writing the DVD+RW 96 times, not the same udf
> > disk. 3) Reading from The writed disc
> > No error, normal operation.
> > 4)Changing to USB Interface and ShutDown the iee1394, and do the udf
> > Stuff. Normal operation no errors on the DVD-RW media.
> > 5) USB Writing Normal growisofs -Z /dev/sr0 -J -r /folder
> > No errors on the media, writing as iso not packet.
> > The error appears while writing the DVD-RW 57 times, not the same udf
> > disk, less data less errors.
> > 6) Reading data from USB Interface.
> > No errors normal operation.
> > 7) lspci, lsusb
> > The mouse is not relevant, I was plugged today.
> >
> > Working with +RW -RW -R and +R, allways writing not udf packets the error
> > appears. As IDE interface the drive does not produce any device not ready
> > error.
>
> I know practically nothing about how your device works, so this is just a
> guess.  It seems likely that the IEEE1394-USB/ATA interface controller
> translates the commands it receives over the external bus into a sequence
> of ATA or ATAPI commands that is somewhat different from the sequence of
> commands Linux would use if the drive were directly attached to an IDE
> controller.  As a result, perhaps the drive sends those "not ready"
> replies when you use it over an external bus but not when you use attach
> it over ATA.
>
> Or maybe not...  Maybe the drive _does_ send those "not ready" messages
> and the IDE driver ignores them instead of printing them in the system
> log.  Or perhaps those messages are sent by the bus interface controller
> and not by the drive itself.  I just don't know.
>
> Alan Stern
Ok, yes may be the drive sends some command bad back translated to the system. 
And may be is not important, cause drive works, and media almost never get 
badwritten.

-- 
Gustavo Guillermo Pérez
Compunauta uLinux
www.compunauta.com

  parent reply	other threads:[~2005-11-23  2:22 UTC|newest]

Thread overview: 10+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2005-11-21 22:00 Gustavo Guillermo Pérez
2005-11-21 23:25 ` Jeff Garzik
2005-11-22 15:36   ` [linux-usb-devel] " Alan Stern
2005-11-22 17:43     ` Gustavo Guillermo Pérez
2005-11-22 18:56       ` Alan Stern
2005-11-22 19:00         ` Jeff Garzik
2005-11-24 15:03           ` Mark Lord
2005-11-24 17:28             ` Alan Stern
2005-11-23  2:21         ` Gustavo Guillermo Pérez [this message]
2005-11-22 18:59     ` Jeff Garzik

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=200511222021.59075.gustavo@compunauta.com \
    --to=gustavo@compunauta.com \
    --cc=jgarzik@pobox.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux-usb-devel@lists.sourceforge.net \
    --cc=stern@rowland.harvard.edu \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox

all inboxes | Powered by JetHome®