From: Robin Theander <Robin.Theander@tellabs.com>
To: parisc-linux@thepuffingroup.com
Subject: Re: [parisc-linux] 712/60 booting problem
Date: Thu, 14 Dec 2000 12:01:06 +0100 [thread overview]
Message-ID: <3A38A872.BF943E41@tellabs.com> (raw)
In-Reply-To: 3A374648.213EA4AC@de.origin-it.com
Well not really a boot problem but a few related questions.
If I do a
boot scsi.6.0 isl
palo displays the "options" menu and asks for some action (number or
'b').
At this point the box is dead - no response from keyboard or serial.
Is this supposed to work on this HW?
Can I control the console output (serial or STI/PDC) with a console=...
parameter in the boot string. This is the CDROM 0.5 stock kernel+palo
installed on a HD.
Can I change the /dev/console device numbers to do the same?
Before I get too far.. Is the STI mode working at all on a 712/60? The
docs and reports are a bit vague on this.
TIA.
Regards,
Robin.
Matthias.Wientapper@de.origin-it.com wrote:
> (ASIC-Designers love their HPs, eh?)
Well, we are doing all the ASIC work on Suns - and I'm edging PC's with
Linux in where I can. My 712/60 is an old decommissioned dns server.
Getting rid of H-PUX makes it a great toy - thanks guys.
--
ASIC Design Engineer
Tellabs Denmark A/S
Direct: +45 4473 2942
robin.theander@tellabs.com
next parent reply other threads:[~2000-12-14 10:59 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <3A374648.213EA4AC@de.origin-it.com>
2000-12-14 11:01 ` Robin Theander [this message]
2000-12-13 9:45 [parisc-linux] 712/60 booting problem Robin Theander
2000-12-13 9:54 ` Matthias Wientapper
-- strict thread matches above, loose matches on Subject: below --
2000-12-12 9:36 Marko.T.Niskanen
2000-12-12 8:40 Marko.T.Niskanen
2000-12-12 17:14 ` Alex deVries
2000-12-12 6:05 Marko.T.Niskanen
2000-12-12 7:22 ` Matt Taggart
2000-12-11 8:31 Marko.T.Niskanen
2000-12-11 16:02 ` Alex deVries
2000-12-12 4:46 ` Alex deVries
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=3A38A872.BF943E41@tellabs.com \
--to=robin.theander@tellabs.com \
--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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox