From: "D. Lance Robinson" <lancer@airways.com>
To: linux-scsi@vger.rutgers.edu
Cc: linuxppc-dev@lists.linuxppc.org
Subject: Re: Diamond Fireport 40 (Sym875)
Date: Thu, 10 Dec 1998 09:52:41 -0700 [thread overview]
Message-ID: <366FFC59.32C325A7@airways.com> (raw)
In-Reply-To: Pine.LNX.4.03.9811252309520.23541-100000@mercator.cs.kuleuven.ac.be
Geert Uytterhoeven wrote:
>...
> I borrowed a FirePort 40 from a friend for testing.
>
...
> The Viking was the last drive on the chain. I tried playing with the
> termination jumper (read: what I thought was the termination jumper, left my
> specs somewhere else :-(, but to no avail. I connected a borrowed CD-Writer
> (PLEXTOR CD-R PX-R412C Rev 1.04) with correct termination to the end of the
> chain to make sure it was no termination problem, but that didn't help.
>
> Then I removed the Viking from the chain, and everything worked fine. Could it
> be that the cable was too long to use FAST-20 transfers with the Viking? It was
> about 75 cm long.
>
Geert,
You still probably have a termination problem. You say that the CD-R
works fine. This is a narrow device and only terminates the narrow
signals. The best thing is to use a wide active terminator at the end of
the cable.
<>< Lance.
[[ This message was sent via the linuxppc-dev mailing list. Replies are ]]
[[ not forced back to the list, so be sure to Cc linuxppc-dev if your ]]
[[ reply is of general interest. To unsubscribe from linuxppc-dev, send ]]
[[ the message 'unsubscribe' to linuxppc-dev-request@lists.linuxppc.org ]]
next parent reply other threads:[~1998-12-10 16:52 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <Pine.LNX.4.03.9811252309520.23541-100000@mercator.cs.kuleuven.ac.be>
1998-12-10 16:52 ` D. Lance Robinson [this message]
1998-12-16 9:13 ` Diamond Fireport 40 (Sym875) Geert Uytterhoeven
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=366FFC59.32C325A7@airways.com \
--to=lancer@airways.com \
--cc=linux-scsi@vger.rutgers.edu \
--cc=linuxppc-dev@lists.linuxppc.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.