Linux PARISC architecture development
 help / color / mirror / Atom feed
From: "Beerse, Corne" <c.beerse@torex-hiscom.nl>
To: "'maillist parisc-linux'" <parisc-linux@parisc-linux.org>,
	"'maillist HP-UX-admin'" <hpux-admin@DutchWorks.nl>
Subject: [parisc-linux] testing HP-PA risc hardware
Date: Fri, 1 Aug 2003 16:29:35 +0200	[thread overview]
Message-ID: <03Aug1.164945cest.119089@ns.hiscom.nl> (raw)

[-- Attachment #1: Type: text/plain, Size: 1057 bytes --]

Hi,

Here I have an HP D370 machine that (during my holidays) crashed. Since the
machine was replaced since long and only kept running for fast access to old
stuff, not a real problem.

At first, we suspected the boot disk since its led keeps buring. However,
booting HP-UX from CDRom for a new fresh install, the boot of the kernel
crashes at roughly the same point, even with all disks removed. Hence we
suspected the core memory. However, changing or replacing the memory does
not change anything in the behavoure.

Is there a way to somehow test the hardware of a PA-Risc machine? Either
from HP or from the linux world?

Kind of like the test tools as found on the (intel-) linux distributions?

btw: I can get debian-woody booted up to the message that if this is the
last message on screen, check the faq. A second terminal (HP 700/96) on tty1
shows a lot of (vt100?) junk. How can I either put the HP700/96 terminal in
VT100 mode or whats the magic name of this terminal in the 'TERM=...' kernel
parameter?



CBee


mailto:c.beerse@torex-hiscom.nl

[-- Attachment #2: Type: text/html, Size: 1653 bytes --]

             reply	other threads:[~2003-08-01 14:29 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2003-08-01 14:29 Beerse, Corne [this message]
2003-08-01 14:39 ` [parisc-linux] testing HP-PA risc hardware Jan-Benedict Glaw
2003-08-01 15:04 ` Joel Soete

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=03Aug1.164945cest.119089@ns.hiscom.nl \
    --to=c.beerse@torex-hiscom.nl \
    --cc=hpux-admin@DutchWorks.nl \
    --cc=parisc-linux@parisc-linux.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