From: jim roy <jim@nga.com>
To: linux-admin <linux-admin@vger.kernel.org>
Subject: lost my Monitor/keyboard
Date: Mon, 19 Aug 2002 13:06:11 -0700 [thread overview]
Message-ID: <20020819130611.K323@redwing> (raw)
I have 3 linux machines which share a keyboard/monitor
via a simple data switch. One of them has recently
lost contact, with both keyboard and Monitor.
I don't think it's the switch, because I changed to
an empty port and got the same result.
Perhaps the video card failed, but I would expect that
I could still log, typing into the dark. Checking the
log files from a telnet session on another machine shows
that this is not happening....
This is a machine I really do not want to reboot if there
is a chance that I'll have to muck about with new parts
to get it going again.
Any advice on debugging this problem??
Jim Roy
next reply other threads:[~2002-08-19 20:06 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2002-08-19 20:06 jim roy [this message]
2002-08-19 22:13 ` lost my Monitor/keyboard Mat Harris
2002-08-20 8:38 ` terry white
-- strict thread matches above, loose matches on Subject: below --
2002-08-20 0:47 johnjulian1
[not found] <20020820092449.Q323@redwing>
2002-08-20 18:35 ` terry white
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=20020819130611.K323@redwing \
--to=jim@nga.com \
--cc=linux-admin@vger.kernel.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;
as well as URLs for NNTP newsgroup(s).