| 1 |
On Tue, Aug 24, 2010 at 4:27 AM, Mick <michaelkintzios@×××××.com> wrote: |
| 2 |
|
| 3 |
> On 24 August 2010 11:23, Adam Carter <adamcarter3@×××××.com> wrote: |
| 4 |
> > |
| 5 |
> >> No. I ditched my xorg.conf completely; it had been there just because I |
| 6 |
> >> couldn't get the Westinghouse monitor to work without it. The Xorg logs |
| 7 |
> >> show it recognizes a boatload of |
| 8 |
> >> modes that the monitor likes, but gives an alibi for not using the HD |
| 9 |
> >> ones. The approach |
| 10 |
> >> does not seem promising. |
| 11 |
> >> |
| 12 |
> >> /var/log/Xorg.0.log attached. I'm paying attention to lines 269 295 327 |
| 13 |
> >> 369 377 380 and 381 |
| 14 |
> >> |
| 15 |
> >> 269: (II) MACH64(0): Modeline "1920x1080"x0.0 148.50 1920 2008 2052 |
| 16 |
> >> 2200 1080 1084 1089 1125 +hsync +vsync (67.5 kHz) |
| 17 |
> >> 295: (II) MACH64(0): Modeline "1920x1080"x60.0 172.80 1920 2040 2248 |
| 18 |
> >> 2576 1080 1081 1084 1118 -hsync +vsync (67.1 kHz) |
| 19 |
> >> 327: (II) MACH64(0): Estimated virtual size for aspect ratio 1.7931 is |
| 20 |
> >> 1920x1080 |
| 21 |
> >> 369: (II) MACH64(0): Not using default mode "1920x1440" (insufficient |
| 22 |
> >> memory for mode) |
| 23 |
> >> 377: (II) MACH64(0): Not using driver mode "1920x1080" (bad mode |
| 24 |
> >> clock/interlace/doublescan) |
| 25 |
> >> 380: (II) MACH64(0): Not using driver mode "1920x1080" (bad mode |
| 26 |
> >> clock/interlace/doublescan) |
| 27 |
> >> 381: (WW) MACH64(0): Shrinking virtual size estimate from 1920x1080 to |
| 28 |
> >> 1280x1024 |
| 29 |
> >> |
| 30 |
> > |
| 31 |
> > I assume 269 and 295 are related to 377 and 380. I remember i had a lot |
| 32 |
> of |
| 33 |
> > pain getting a Geforce 440MX to do 16:9, but it was all in the modelines. |
| 34 |
> > There are some modeline calculators on the web, but be warned that some |
| 35 |
> of |
| 36 |
> > them produce bad output. I did eventually get it to work after a lot of |
| 37 |
> > trial and error. |
| 38 |
> > |
| 39 |
> > Also because of this; |
| 40 |
> > |
| 41 |
> > (II) MACH64(0): <default monitor>: Using hsync range of 30.00-85.00 kHz |
| 42 |
> > (II) MACH64(0): <default monitor>: Using vrefresh range of 55.00-75.00 Hz |
| 43 |
> > (II) MACH64(0): <default monitor>: Using maximum pixel clock of 160.00 |
| 44 |
> MHz |
| 45 |
> > |
| 46 |
> > |
| 47 |
> > you may need to set the ranges in your xorg.conf instead. check the |
| 48 |
> monitors |
| 49 |
> > specs first tho. |
| 50 |
> |
| 51 |
> What does xrandr -q show? |
| 52 |
> -- |
| 53 |
> Regards, |
| 54 |
> Mick |
| 55 |
> |
| 56 |
> |
| 57 |
treat log # xrandr -q |
| 58 |
Screen 0: minimum 320 x 240, current 1280 x 1024, maximum 1440 x 1024 |
| 59 |
default connected 1280x1024+0+0 0mm x 0mm |
| 60 |
1280x1024 60.0* |
| 61 |
1440x900 60.0 |
| 62 |
1280x960 60.0 |
| 63 |
1152x864 75.0 |
| 64 |
1024x768 75.0 70.0 60.0 |
| 65 |
896x672 60.0 |
| 66 |
832x624 75.0 |
| 67 |
800x600 75.0 72.0 60.0 56.0 65.0 |
| 68 |
700x525 75.0 60.0 |
| 69 |
640x512 75.0 60.0 |
| 70 |
640x480 75.0 73.0 67.0 60.0 |
| 71 |
720x400 70.0 |
| 72 |
576x432 75.0 |
| 73 |
512x384 75.0 70.0 60.0 |
| 74 |
416x312 75.0 |
| 75 |
400x300 75.0 72.0 60.0 56.0 |
| 76 |
320x240 75.0 73.0 60.0 |
| 77 |
treat log # |
| 78 |
|
| 79 |
-- |
| 80 |
Kevin O'Gorman, PhD |
Archives