public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: John Bradford <john@grabjohn.com>
To: lkml@scienceworks.com
Cc: linux-kernel@vger.kernel.org, vojtech@suse.cz
Subject: Re: Promise PDC20268 FastTrack 100 TX2 (PDC20268)
Date: Mon, 20 Jan 2003 19:12:53 +0000 (GMT)	[thread overview]
Message-ID: <200301201912.h0KJCrru006239@darkstar.example.net> (raw)
In-Reply-To: <20030120183442.GA3440@poseidon.wasserstadt.de> from "lkml@scienceworks.com" at Jan 20, 2003 07:34:42 PM

> I have a Promise FastTrack 100 TX2 (PDC20268) IDE-controller
> (BIOS v2.00.0.24) used in a linux MD-RAID.  Aside from various
> other annoying Promise-problems, I am not able to perform a
> remote boot because the brain-dead Promise-BIOS "complains" that
> no array is defined, and requires one to press ESC to continue
> booting.  I would very much appreciate any tips as to how I can
> circumvent this "feature".

Well, if you don't usually need a keyboard on that machine, in theory,
you might be able to connect the keyboard input to the PS/2 mouse port
of another machine, and write a program to send the correct bytes for
that keypress to the other machine.  Then, you could reboot the
machine with the Promise card in it, then log in to the other machine,
and run the program to send the keypress.

Not sure how practical this solution would be though...  You'd
probably have to simulate the keyboard initialisation responses as
well, which would make it a bit complicated

John.

  reply	other threads:[~2003-01-20 19:03 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2003-01-20 18:34 Promise PDC20268 FastTrack 100 TX2 (PDC20268) lkml
2003-01-20 19:12 ` John Bradford [this message]
2003-01-25 11:44   ` Vojtech Pavlik
2003-01-20 19:46 ` Milan Roubal

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=200301201912.h0KJCrru006239@darkstar.example.net \
    --to=john@grabjohn.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=lkml@scienceworks.com \
    --cc=vojtech@suse.cz \
    /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