All of lore.kernel.org
 help / color / mirror / Atom feed
From: desrt <desrt@desrt.ca>
To: Ben Collins <bcollins@debian.org>
Cc: linux-kernel@vger.kernel.org
Subject: Re: ieee1394: Node 01:1023 has non-standard ROM format (0 quads), cannot parse
Date: 23 Jan 2003 21:33:33 -0500	[thread overview]
Message-ID: <1043375612.1889.7.camel@nothing.desrt.ca> (raw)
In-Reply-To: <20030124014815.GB4524@hopper.phunnypharm.org>

> If one cdrom works in the enclosure and another doesn't, then I suspect
> something is weird with the enclosure's detection of the device you
> placed in it. Are you sure that the master/slave jumpers are set
> correctly for the enclosure? Anything else it needs?
They were both set to master.  The enclosure itself doesn't have any
jumpers really, but I changed the jumpers around on the dvd drive (after
receiving your email) and tested various combinations (ie: master,
slave, cable select, and the DMA jumper on/off.)  None of these worked.

Some other stuff I played with:  I noticed that the drive locks shut
with the 'busy' light on.  but:
- drive not connected to enclosure: eject works, busy light off
- drive connected to enclosure, but enclosure not plugged into firewire
bus (ie: controller card): eject doesn't work, busy light on
- connected, on the bus, ohci1394 module not loaded: eject works, busy
light off
- connected, on bus, ohci1394 loaded: eject doesn't work, busy light on

Also, transitioning from one of the 'working' states to one of the
non-working states doesn't work (ie: the unloading the ohci1394
driver.)  The drive gets "stuck" in it's busy-not-working state until
you powercycle the enclosure.

Is it possible that my enclosure just doesn't support DVD drives?

Thanks again


  reply	other threads:[~2003-01-24  2:25 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2003-01-24  1:35 ieee1394: Node 01:1023 has non-standard ROM format (0 quads), cannot parse desrt
2003-01-24  1:48 ` Ben Collins
2003-01-24  2:33   ` desrt [this message]
2003-01-24  2:43     ` Ben Collins
2003-01-24  2:47       ` desrt
2003-01-24  3:21 ` James H. Cloos Jr.

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=1043375612.1889.7.camel@nothing.desrt.ca \
    --to=desrt@desrt.ca \
    --cc=bcollins@debian.org \
    --cc=linux-kernel@vger.kernel.org \
    /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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.