public inbox for gentoo-user@lists.gentoo.org
 help / color / mirror / Atom feed
From: Dan Farrell <dan@spore.ath.cx>
To: gentoo-user@lists.gentoo.org
Subject: Re: [gentoo-user] Switched monitors, having resolution problems
Date: Thu, 1 Mar 2007 08:40:02 -0600	[thread overview]
Message-ID: <20070301084002.7fab56da@pascal.spore.ath.cx> (raw)
In-Reply-To: <bf0e048a0702282102l5602235evaa07299ebe0cea9e@mail.gmail.com>

On Thu, 1 Mar 2007 07:02:40 +0200
"Vlad Dogaru" <ddvlad@gmail.com> wrote:


> I'll add this to the list of things I learned today. Apologies for the
> inconvenience.
no inconvenience here, but others on the mailinglist have no doubt
learned as well .. so thanks for the convenience ; )

> I am now using a VESA-compatible modeline for 1280x1024@75 (not sure
> about the last one). I just pasted it from ddcxinfo-knoppix, knowing
> the monitor would work with these settings.
that looks good. the @75 is just part of the arbitrary modeline name,
but actually refers to the refresh rate being used - a nice, fliker
free 75Hz (or kHz, whichever it is i can't rememver)
> One more question, though. If I switch back to my older, smaller
> monitor and forget to change the modeline, will it get fried? I seem
> to see this warning quite often.
I have seen that warning too, but I haven't yet been able to actually
break a monitor like that.  I think the current technology (circa early
to mid 90s and up) no longer has this problem.  However, don't take it
from me as fact, but a guess correlating with the experiences I have
had.  Usually, newer monitors simply show an 'out of range' box on the
screen, and older ones show an image composed entirely of quickly
waving gray black and white horizontal lines; the monitor in this case
has always happily performed afterwords just fine at supported
resolutions.  

there is one thing i would mention though.  You know how as monitors
wear out they get blurrier and blurrer, and image quality decreases?
Well, setting the refresh rate too high on some older, cheaper
monitors seems to result in a much accellerated blurification process.
> Thanks for the help,
> Vlad
any time. 
-dan
-- 
gentoo-user@gentoo.org mailing list



      reply	other threads:[~2007-03-01 14:49 UTC|newest]

Thread overview: 10+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2007-02-27 23:36 [gentoo-user] Switched monitors, having resolution problems Vlad Dogaru
2007-02-27 23:48 ` Hemmann, Volker Armin
2007-02-28  0:03   ` Vlad Dogaru
2007-02-28  0:54     ` Hemmann, Volker Armin
2007-02-28  1:05       ` Dan Farrell
2007-02-28  4:55         ` Vlad Dogaru
2007-02-28  8:58           ` Nelson, David (ED, PAR&D)
2007-02-28 22:38             ` Dan Farrell
2007-03-01  5:02               ` Vlad Dogaru
2007-03-01 14:40                 ` Dan Farrell [this message]

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=20070301084002.7fab56da@pascal.spore.ath.cx \
    --to=dan@spore.ath.cx \
    --cc=gentoo-user@lists.gentoo.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