et:
Interesting question. I don't know the answer with Linux. I have never tried using
that old a 486 in that manner: disconnecting the keyboard after boot-up, then trying
to access a Linux operating system on connecting it up again. Last time I did anything
like that was in the days of Windo
Warren,
Check in the Bios Setup if it's set to stop on errors or only keyboard errors.
Use F1 to continue.
HTHs,
Richard.
On 24 Sep 2002 08:21:02 -0600 Warren Post <[EMAIL PROTECTED]> wrote:
> This is a hardware problem, not a Linux problem. But perhaps someone
> has faced this problem before
On Tuesday 24 September 2002 07:21 am, Warren Post scribbled something about:
> This is a hardware problem, not a Linux problem. But perhaps someone has
> faced this problem before.
>
> I've amazed my friends by setting up a Linux-firewall-on-a-floppy in our
> city hall on an ancient 486 that was
Warren,
If your 80486 CMOS BIOS is that old, where it doesn't offer you the opportunity to
ignore the a missing keyboard, then that's the way it is. I suppose someone may have
devised a null plug to compensate. Late-model 486 boards came out with this capability
and that's been the case with
This is a hardware problem, not a Linux problem. But perhaps someone has
faced this problem before.
I've amazed my friends by setting up a Linux-firewall-on-a-floppy in our
city hall on an ancient 486 that was retired ages ago. But when I try to
run it headless, it won't boot unless I plug a keyb