From: Grant Grundler <grundler@cup.hp.com>
To: Steven Pritchard <steve@silug.org>
Cc: parisc-linux@thepuffingroup.com
Subject: Re: [parisc-linux] K100 problem
Date: Fri, 07 Apr 2000 09:34:54 -0700 [thread overview]
Message-ID: <200004071634.JAA06324@milano.cup.hp.com> (raw)
In-Reply-To: Your message of "Fri, 07 Apr 2000 09:40:20 PDT." <200004071440.JAA29458@osiris.silug.org>
Steven Pritchard wrote:
> Ulrich Strelow said:
> > I am not quite sure, but I think you need to set the
> > Keyboard Path to the same value as Console Path when
> > you use a serial console (or PC).
>
> I wondered about that...
>
> How can I reset the Keyboard Path without being able to interrupt the
> boot sequence though?
Disconnect the primary/secondary boot devices?
If autosearch is on, might have to disconnect all bootable devices.
One should land at the PDC prompt once all paths/search have been tried.
grant
>
> 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
>
> ---------------------------------------------------------------------------
> To unsubscribe: send e-mail to parisc-linux-request@thepuffingroup.com with
> `unsubscribe' as the subject.
>
Grant Grundler
Unix Development Lab
+1.408.447.7253
next prev parent reply other threads:[~2000-04-07 16:33 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2000-04-07 12:19 [parisc-linux] K100 problem Ulrich Strelow
2000-04-07 14:40 ` Steven Pritchard
2000-04-07 16:34 ` Grant Grundler [this message]
2000-05-29 8:32 ` [parisc-linux] EISA 10/100 nic for 715 systems ? Ed June
2000-05-29 12:15 ` Dominik Kubla
2000-05-29 13:35 ` Steven Pritchard
2000-05-29 19:39 ` Dominik Kubla
2000-05-30 17:26 ` Barrie Spence
2000-05-29 23:59 ` Grant Grundler
-- strict thread matches above, loose matches on Subject: below --
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
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=200004071634.JAA06324@milano.cup.hp.com \
--to=grundler@cup.hp.com \
--cc=parisc-linux@thepuffingroup.com \
--cc=steve@silug.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