From: Steven Pritchard <steve@silug.org>
To: parisc-linux@thepuffingroup.com
Subject: Re: [parisc-linux] K100 problem
Date: Thu, 6 Apr 2000 16:30:46 -0500 (CDT) [thread overview]
Message-ID: <200004062130.QAA25142@osiris.silug.org> (raw)
In-Reply-To: <002801bf9b5f$c12180e0$4b58000f@jh73313p.cup.hp.com> from Jim Hull at "Mar 31, 2000 02:23:35 pm"
Jim Hull said:
> WARN A008 No bootable device found
Apparently the terminal was dead. I hooked it up to my PC and got
output. Now I have another problem... The box outputs to the serial
console, but it doesn't seem to want to take input on the serial
console. Any ideas what might cause that?
Here's the boot messages:
--
Firmware Version 1.8
Duplex Console IO Dependent Code (IODC) revision 4
------------------------------------------------------------------------------
(c) Copyright 1990-1994, Hewlett-Packard Company, All rights reserved
------------------------------------------------------------------------------
Processor Speed State CoProcessor State Cache Size
--------- -------- --------------------- ----------------- ----------
0 100 MHz Active Functional 256 KB
Central Bus Speed (in MHz) : 100
Available Memory (bytes) : 167772160
Good Memory Required (bytes): 16211968
Primary boot path: 8/0.6 (dec)
Alternate boot path: 8/12/5.0 (dec)
Console path: 8/4/0.0 (dec)
Keyboard path: 8/12/7.0 (dec)
CPU 0
WARNING: Memory configuration is not optimized for performance. Refer
to the System Installation or Memory Installation manuals for
memory configuration guidelines.
Processor is starting autoboot process.
To discontinue, press any key within 10 seconds.
10 seconds expired.
Proceeding...
Trying Primary Boot Path
------------------------
Booting...
Boot IO Dependent Code (IODC) revision 7
HARD Booted.
ISL Revision A.00.38 OCT 26, 1994
ISL booting hpux
Boot
: disc(8/0.6.0;0)/stand/vmunix
4334092 + 380928 + 407872 start 0x17ce68
--
It does boot into HP-UX, so if I can figure out a way into it over the
network, I can probably reload the box with IgniteUX and just use it
as a HP-UX system, but obviously life would be easier if I could use
the console...
Steve
--
steve@silug.org | Linux Users of Central Illinois
(618)398-7320 | Meetings the 4th Tuesday of every month
Steven Pritchard | http://www.luci.org/ for more info
next prev parent reply other threads:[~2000-04-06 21:30 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2000-03-31 20:52 [parisc-linux] K100 problem Steven Pritchard
2000-03-31 22:23 ` Jim Hull
2000-04-06 21:30 ` Steven Pritchard [this message]
-- strict thread matches above, loose matches on Subject: below --
2000-04-07 12:19 Ulrich Strelow
2000-04-07 14:40 ` Steven Pritchard
2000-04-07 16:34 ` Grant Grundler
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=200004062130.QAA25142@osiris.silug.org \
--to=steve@silug.org \
--cc=parisc-linux@thepuffingroup.com \
/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.