From: eric@cirr.com (Eric Schnoebelen)
To: "Anthony Mori" <tonym@compusource.net>
Cc: parisc-linux@lists.parisc-linux.org
Subject: Re: [parisc-linux] C180 problem
Date: Tue, 31 Jul 2001 17:06:50 -0500 [thread overview]
Message-ID: <200107312206.RAA20934@opus.cirr.com> (raw)
In-Reply-To: Your message of "Mon, 30 Jul 2001 23:48:31 EDT." <004b01c11973$ada28fd0$0b1e7b01@tpburner>
"Anthony Mori" writes:
- Before I changed the Fastboot, When the machine was turned on,
- LED's 2,3,4 were on briefly, then they went out, and LED 1 stayed on.
- Then after a briedf pause, 2,3,4 would start flickering as if it was doing
- something (which it was).
-
- Now, 2,3,4 turn on briefly, then go out, and LED 1 turns on, and that's
- it. Nothing else. No video, nothing (A4071B video card)
Which LED is `1'? (whats the lab beside it?)
According to the C Class (c1x0, c2x0, c3x0) service
handbook, 'net-in' (top or right) LED lit, with no others means
`no memory found.' (with a further comment of ``Likely cause:
SIMMs or processor board'').
There is fault that leaves the hearbeat LED lit (at
least, not according to the documentation.) The SCSI access LED
lit means ``Processor board fault'' (my C110 currently suffers
this.)
--
Eric Schnoebelen eric@cirr.com http://www.cirr.com
There has been an alarming increase in the number of things
you know nothing about.
next prev parent reply other threads:[~2001-07-31 22:07 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2001-07-31 2:34 [parisc-linux] pa-risc project Michael S.Zick
2001-07-31 3:48 ` [parisc-linux] C180 problem Anthony Mori
2001-07-31 6:05 ` Grant Grundler
2001-07-31 18:11 ` Anthony Mori
2001-07-31 22:06 ` Eric Schnoebelen [this message]
2001-07-31 5:59 ` [parisc-linux] pa-risc project Grant Grundler
2001-07-31 11:35 ` [parisc-linux] ESIEE website access is possible now Xavier Debacker
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=200107312206.RAA20934@opus.cirr.com \
--to=eric@cirr.com \
--cc=parisc-linux@lists.parisc-linux.org \
--cc=tonym@compusource.net \
/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.