9fans - fans of the OS Plan 9 from Bell Labs
 help / color / mirror / Atom feed
From: "Ronald G. Minnich" <rminnich@lanl.gov>
To: 9fans@cse.psu.edu
Subject: Re: [9fans] 00E & projector
Date: Sat,  1 Feb 2003 10:58:39 -0700	[thread overview]
Message-ID: <Pine.LNX.4.44.0302011054380.22495-100000@carotid.ccs.lanl.gov> (raw)
In-Reply-To: <fea7bb9660c40612ceb19573270d5304@plan9.bell-labs.com>

On Sat, 1 Feb 2003, Russ Cox wrote:

> Are you running your screen at a higher resolution
> than the projector supports?  That's what it sounds
> like.  It's also possible we screwed up the CRT
> code -- it doesn't get exercised much -- but usually
> if you Fn-F7 to get it working before aux/vga,
> it keeps working.

Another common problem when you go to graphics mode on older thinkpads --
there is a "feature" that doesn't work with all projectors in which the
thinkpad hardware tries to autodetect external vga, and won't drive it
unless it detects it. Well, guess what, it didn't always work, as I found
at one conference where I went through three projectors and had to give up
and "talk to my slides" while the audience watched a blank screen for 45
minutes. I doubt more than 75% of them fell asleep, but I'm an optimist --
oh, no, wait, I'm not.

There was a linux utility to fix this on the 570, and I wonder if the same
problem exists on the 600. The linux utility just jammed some random magic
hardware bit and all was well (disabled the hardware mis-feature).
So it can look like a resolution problem but actually be something else.
Best bet is try 640x480 first, and if that doesn't fix it, then the
problem is something else.

ron



  parent reply	other threads:[~2003-02-01 17:58 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2003-02-01 13:29 sah
2003-02-01 15:37 ` Russ Cox
2003-02-01 16:48   ` Sam
2003-02-01 17:58   ` Ronald G. Minnich [this message]
2003-02-25 14:01     ` Sam
2003-02-25 16:47       ` Jack Johnson
2003-02-25 19:52       ` northern snowfall

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=Pine.LNX.4.44.0302011054380.22495-100000@carotid.ccs.lanl.gov \
    --to=rminnich@lanl.gov \
    --cc=9fans@cse.psu.edu \
    /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).