> 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.
