Re: [gentoo-user] New HD monitor stretches everything. How to teach Xorg?

[Kevin O'Gorman]

On Tue, Aug 24, 2010 at 11:48 AM, Paul Hartman <
paul.hartman+gentoo@×××××.com <paul.hartman%2Bgentoo@×××××.com>> wrote:

> On Tue, Aug 24, 2010 at 12:10 PM, Kevin O'Gorman <kogorman@×××××.com>
> wrote:
> >
> >
> > On Tue, Aug 24, 2010 at 4:27 AM, Mick <michaelkintzios@×××××.com> wrote:
> >>
> >> On 24 August 2010 11:23, Adam Carter <adamcarter3@×××××.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 #
>
> Until you can replace the video card, maybe you can come up with a
> modeline for a lower resolution with 16:9 aspect ratio, such as:
>
> 852x480
> 1280x720
> 1365x768
> 1600x900
>
> It wouldn't be optimal, but at least it would fill your screen without
> being stretched strangely.
>
>
Yah, I might have some luck with that.  Since I'm years out of practice
fooling with this stuff (last seen in 2002) can someone point me at the
tools for
1) Computing a modeline (I understand the quality varies a lot)
2) Configuring an xorg.conf




-- 
Kevin O'Gorman, PhD