From: desrt <desrt@desrt.ca>
To: linux-kernel@vger.kernel.org
Subject: ieee1394: Node 01:1023 has non-standard ROM format (0 quads), cannot parse
Date: 23 Jan 2003 20:35:35 -0500 [thread overview]
Message-ID: <1043372135.1442.7.camel@nothing.desrt.ca> (raw)
Hello.
I just got a new plextor combo (read dvd, write cd) drive and installed
it into my firewire drive enclosure. The CD-ROM drive that was in there
previously was working fine. I am using an Audigy as my firewire
controller.
Now, on attach/power on/modprobe ohci1394/etc I get this message:
ieee1394: Node 01:1023 has non-standard ROM format (0 quads), cannot
parse
I get the same message with 2.4.20, .21-pre3, and 2.5.59.
I've tried increasing the number of attempts that the loop in nodemgr.c
makes to attempt to get this quantity from 4 tries (1 second) to 40 (10
seconds.) The only difference that made was that the error takes longer
to appear.
Not sure if this is useful information, but this is what it says with
the CD-ROM drive in (ie: when it is working)
ieee1394: Device added: Node[01:1023] GUID[0030999550551539]
[NewMotion Technology Corp. ]
I've googled and searched the list archives at no avail. IRC also isn't
working out.
If anybody has experienced this before, has any ideas, would like
information about the problem or even knows of a better forum to direct
this question to, your help would be greatly appreciated. Please CC: me
a copy of your reply as I am not on the list.
Thanks in advance,
Ryan
next reply other threads:[~2003-01-24 1:27 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2003-01-24 1:35 desrt [this message]
2003-01-24 1:48 ` ieee1394: Node 01:1023 has non-standard ROM format (0 quads), cannot parse Ben Collins
2003-01-24 2:33 ` desrt
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=1043372135.1442.7.camel@nothing.desrt.ca \
--to=desrt@desrt.ca \
--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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox