From: Mat Harris <mat.harris@genestate.com>
To: jim roy <jim@nga.com>
Cc: linux-admin <linux-admin@vger.kernel.org>
Subject: Re: lost my Monitor/keyboard
Date: Mon, 19 Aug 2002 23:13:20 +0100 [thread overview]
Message-ID: <20020819221320.GA31793@genestate.com> (raw)
In-Reply-To: <20020819130611.K323@redwing>
[-- Attachment #1: Type: text/plain, Size: 1244 bytes --]
try ripping out the switch and plugging the stuff straign into the box
or else swap with another set of ports that work on another box. Is
everything ok when you shell into it remoteley?
On Mon, Aug 19, 2002 at 01:06:11 -0700, jim roy wrote:
> 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
>
> -
> To unsubscribe from this list: send the line "unsubscribe linux-admin" in
> the body of a message to majordomo@vger.kernel.org
> More majordomo info at http://vger.kernel.org/majordomo-info.html
--
Mat Harris OpenGPG Public Key ID: CC14DD34
mat.harris@genestate.com www.genestate.com
[-- Attachment #2: Type: application/pgp-signature, Size: 232 bytes --]
next prev parent reply other threads:[~2002-08-19 22:13 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2002-08-19 20:06 lost my Monitor/keyboard jim roy
2002-08-19 22:13 ` Mat Harris [this message]
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=20020819221320.GA31793@genestate.com \
--to=mat.harris@genestate.com \
--cc=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).