public inbox for gentoo-user@lists.gentoo.org
 help / color / mirror / Atom feed
From: "Kevin O'Gorman" <kogorman@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 10:10:21 -0700	[thread overview]
Message-ID: <AANLkTinVk7HSfHKS4YBQSqH+G=vxtMQu6u1gGBCvgoJ9@mail.gmail.com> (raw)
In-Reply-To: <AANLkTik0hdpBQuCSkE8XbPDmBAY_hzOU+xxfcav_cOAr@mail.gmail.com>

[-- Attachment #1: Type: text/plain, Size: 2842 bytes --]

On Tue, Aug 24, 2010 at 4:27 AM, Mick <michaelkintzios@gmail.com> wrote:

> 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
>
>
treat log # xrandr -q
Screen 0: minimum 320 x 240, current 1280 x 1024, maximum 1440 x 1024
default connected 1280x1024+0+0 0mm x 0mm
   1280x1024      60.0*
   1440x900       60.0
   1280x960       60.0
   1152x864       75.0
   1024x768       75.0     70.0     60.0
   896x672        60.0
   832x624        75.0
   800x600        75.0     72.0     60.0     56.0     65.0
   700x525        75.0     60.0
   640x512        75.0     60.0
   640x480        75.0     73.0     67.0     60.0
   720x400        70.0
   576x432        75.0
   512x384        75.0     70.0     60.0
   416x312        75.0
   400x300        75.0     72.0     60.0     56.0
   320x240        75.0     73.0     60.0
treat log #

-- 
Kevin O'Gorman, PhD

[-- Attachment #2: Type: text/html, Size: 3779 bytes --]

  reply	other threads:[~2010-08-24 17:10 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
2010-08-24 17:10           ` Kevin O'Gorman [this message]
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='AANLkTinVk7HSfHKS4YBQSqH+G=vxtMQu6u1gGBCvgoJ9@mail.gmail.com' \
    --to=kogorman@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