From: "David S. Miller" <davem@dm.cobaltmicro.com>
To: ultralinux@vger.kernel.org
Subject: Re: [Q] ultrapenguin-1.1 on UE4000
Date: Thu, 19 Nov 1998 17:15:36 +0000 [thread overview]
Message-ID: <marc-linux-ultrasparc-91154033002674@msgid-missing> (raw)
In-Reply-To: <marc-linux-ultrasparc-91139210917441@msgid-missing>
From: Jakub Jelinek <jj@sunsite.ms.mff.cuni.cz>
Date: Wed, 18 Nov 1998 14:31:39 +0100 (MET)
What's strange is that no SCSI devices has been found, also, the
number of found SBUSes seems to be weird (I always thought every
SBUS board has two SBUSes).
Look closely at his prtconf (he sent it to me privately, and I believe
to you too Jakub). There are 5 types of Ex000 board types I know of:
1) 'cpu' Ultra CPUs and memory simms
2) 'dual-sbus' Two SBUS's, embedded SOC and FAS/HME
3) 'upa-sbus' One UPA (for Creator3D etc.) slot and one SBUS
4) 'dual-sbus-soc+' Same as dual-sbus except uses SOC+
5) 'pci' PSYCHO based PCI board
One of his boards is a upa-sbus one, thus the odd number of SBUS's.
This still doesn't explain why his SCSI disk was not detected. All of
his FAS scsi adapters were detected, and the driver did not print any
errors while probing the SCSI bus each time.. hmmm..
Eric, could you send us the output of "probe-scsi-all" from the PROM
prompt on this box?
Later,
David S. Miller
davem@dm.cobaltmicro.com
next prev parent reply other threads:[~1998-11-19 17:15 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
1998-11-17 21:16 [Q] ultrapenguin-1.1 on UE4000 ebrower
1998-11-18 12:36 ` David S. Miller
1998-11-18 13:31 ` Jakub Jelinek
1998-11-18 13:39 ` Jakub Jelinek
1998-11-18 19:14 ` ebrower
1998-11-19 16:05 ` Matthew Jacob
1998-11-19 17:15 ` David S. Miller [this message]
1998-11-19 18:15 ` ebrower
1998-11-19 19:44 ` David S. Miller
1998-11-19 20:27 ` ebrower
1998-11-19 20:32 ` David S. Miller
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-91154033002674@msgid-missing \
--to=davem@dm.cobaltmicro.com \
--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.