public inbox for gentoo-user@lists.gentoo.org
 help / color / mirror / Atom feed
From: Mick <michaelkintzios@gmail.com>
To: gentoo-user@lists.gentoo.org
Subject: Re: [gentoo-user] New HD monitor stretches everything. How to teach Xorg?
Date: Tue, 24 Aug 2010 12:27:10 +0100	[thread overview]
Message-ID: <AANLkTik0hdpBQuCSkE8XbPDmBAY_hzOU+xxfcav_cOAr@mail.gmail.com> (raw)
In-Reply-To: <AANLkTincQ36tn73naFR6gTkq0vY5FMEq1fg0bcvKJ2Ly@mail.gmail.com>

On 24 August 2010 11:23, Adam Carter <adamcarter3@gmail.com> wrote:
>
>> No.  I ditched my xorg.conf completely; it had been there just because I
>> couldn't get the Westinghouse monitor to work without it.  The Xorg logs
>> show it recognizes a boatload of
>> modes that the monitor likes, but gives an alibi for not using the HD
>> ones.  The approach
>> does not seem promising.
>>
>> /var/log/Xorg.0.log attached.  I'm paying attention to lines 269 295 327
>> 369 377 380 and 381
>>
>> 269: (II) MACH64(0): Modeline "1920x1080"x0.0  148.50  1920 2008 2052
>> 2200  1080 1084 1089 1125 +hsync +vsync (67.5 kHz)
>> 295: (II) MACH64(0): Modeline "1920x1080"x60.0  172.80  1920 2040 2248
>> 2576  1080 1081 1084 1118 -hsync +vsync (67.1 kHz)
>> 327: (II) MACH64(0): Estimated virtual size for aspect ratio 1.7931 is
>> 1920x1080
>> 369: (II) MACH64(0): Not using default mode "1920x1440" (insufficient
>> memory for mode)
>> 377: (II) MACH64(0): Not using driver mode "1920x1080" (bad mode
>> clock/interlace/doublescan)
>> 380: (II) MACH64(0): Not using driver mode "1920x1080" (bad mode
>> clock/interlace/doublescan)
>> 381: (WW) MACH64(0): Shrinking virtual size estimate from 1920x1080 to
>> 1280x1024
>>
>
> I assume 269 and 295 are related to 377 and 380. I remember i had a lot of
> pain getting a Geforce 440MX to do 16:9, but it was all in the modelines.
> There are some modeline calculators on the web, but be warned that some of
> them produce bad output. I did eventually get it to work after a lot of
> trial and error.
>
> Also because of this;
>
> (II) MACH64(0): <default monitor>: Using hsync range of 30.00-85.00 kHz
> (II) MACH64(0): <default monitor>: Using vrefresh range of 55.00-75.00 Hz
> (II) MACH64(0): <default monitor>: Using maximum pixel clock of 160.00 MHz
>
>
> you may need to set the ranges in your xorg.conf instead. check the monitors
> specs first tho.

What does xrandr -q show?
-- 
Regards,
Mick



  reply	other threads:[~2010-08-24 11:27 UTC|newest]

Thread overview: 36+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2010-08-24  2:27 [gentoo-user] New HD monitor stretches everything. How to teach Xorg? Kevin O'Gorman
2010-08-24  2:38 ` Bill Longman
2010-08-24  3:58   ` dennisonic
2010-08-24  5:24     ` Kevin O'Gorman
2010-08-24  5:40       ` d.fedorov
2010-08-24  7:30         ` Petri Rosenström
2010-08-24 17:09         ` Kevin O'Gorman
2010-08-24 10:23       ` Adam Carter
2010-08-24 11:27         ` Mick [this message]
2010-08-24 17:10           ` Kevin O'Gorman
2010-08-24 18:48             ` Paul Hartman
2010-08-24 22:07               ` Kevin O'Gorman
2010-08-24 22:18                 ` Paul Hartman
2010-08-24 22:37                   ` Dale
2010-08-24 22:59                     ` Paul Hartman
2010-08-24 23:10                       ` dhk
2010-08-25  0:00                         ` Kevin O'Gorman
2010-08-25  0:07                         ` Dale
2010-08-25 10:38                           ` dhk
2010-08-25  0:03                   ` Kevin O'Gorman
2010-08-25 14:17                     ` Paul Hartman
2010-08-25 14:25                       ` Mick
2010-08-25 14:38                         ` Paul Hartman
2010-08-25 14:44                           ` Mick
2010-08-25 14:57                             ` Paul Hartman
2010-08-25 20:29                               ` Kevin O'Gorman
2010-08-27  2:00                                 ` Walter Dnes
2010-08-25 16:30                             ` Peter Humphrey
2010-08-25 16:39                               ` Maciej Grela
2010-08-25 17:09                                 ` Peter Humphrey
2010-08-25 16:39                               ` Maciej Grela
2010-08-25 19:20                               ` Alan McKinnon
2010-08-24  2:51 ` Adam Carter
2010-08-25 20:48 ` Håkon Alstadheim
2010-08-25 20:56   ` Kevin O'Gorman
2010-08-26  3:11     ` Kevin O'Gorman

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=AANLkTik0hdpBQuCSkE8XbPDmBAY_hzOU+xxfcav_cOAr@mail.gmail.com \
    --to=michaelkintzios@gmail.com \
    --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