From: Florian Lohoff <flo@rfc822.org>
To: ultralinux@vger.kernel.org
Subject: Re: RAID is now working...
Date: Wed, 22 Sep 1999 01:02:19 +0000 [thread overview]
Message-ID: <marc-linux-ultrasparc-93799324406052@msgid-missing> (raw)
In-Reply-To: <marc-linux-ultrasparc-93761559712738@msgid-missing>
On Sun, Sep 19, 1999 at 07:40:59PM -0400, David Cooley wrote:
>
> Mine started doing that on the second PTI card I installed... Got looking
> at the boot messages where it first detects the cards... My old one
> (working fine) is detected as ultra scsi... the "new one" is detected as
> fast scsi... Both cards have the same SUN part number on them, but the
> "new" one has ver 1.71 on the sticker on the prom on the board, and the
> "old" one (the one that works all the time) has 1.73 on it. The code read
> by the kernel driver in the boards is 1.21 for the one that fails and 1.25
> on the good one.
I just had a quick look. The Driver Firmware in the Kernel source
seems to be 1.31 (For non-PTI and 1.24 for PTI)... In one of the latest
Sun patches i found a 1.32 (Reverse *ng*n**r*ng). Ill try to make a
qlogicpti_asm.c compatible file (Without knowing what i am doing).
As my cards dont state "Performance Technologies" i think the 1.31 gets
loaded currently (dmesg states Firmware 1.21 but per design the firmware
gets loaded on initialization)
So long ...
Flo
--
Florian Lohoff flo@rfc822.org +49-5241-470566
... The failure can be random; however, when it does occur, it is
catastrophic and is repeatable ... Cisco Field Notice
prev parent reply other threads:[~1999-09-22 1:02 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
1999-09-18 0:44 RAID is now working David A. Cooley
1999-09-18 1:41 ` David S. Miller
1999-09-18 1:50 ` David A. Cooley
1999-09-19 21:02 ` Florian Lohoff
1999-09-19 23:40 ` David Cooley
1999-09-21 12:27 ` Florian Lohoff
1999-09-22 1:02 ` Florian Lohoff [this message]
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=marc-linux-ultrasparc-93799324406052@msgid-missing \
--to=flo@rfc822.org \
--cc=ultralinux@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.