[Date Prev][Date Next] [Thread Prev][Thread Next] [Date Index] [Thread Index]

Re: v4 x screen size and flicker



On Sat, Mar 17, 2001 at 12:10:51PM -0800, Bill Wohler wrote:
>   I just upgraded to X v4 (woody) and selected the mga driver for my
>   Matrox Millenium G200. I have an NEC MultiSync 6FG (21") monitor. I
>   now have two problems:
>   
>     1. Large margins around the screen.
>     2. Incredible flicker.
> 
>   At 1280x1024, there is now a large margin around the screen: 1 cm
>   top and bottom, 2 cm right and left. xvidtune can't make it bigger.
>   Is xvidtune still used in v4 (since I noticed that the mode lines
>   are cheerfully no longer in the configuration) or is there a newer
>   tool that I can use to adjust the size? I don't really want to
>   adjust the monitor size (much) since the size was perfect under v3
>   and the size in the console is fine.
> 
>   Also note that my 1024x768 screen is also small; however, my 800x600
>   screen extends past the edges of the monitor.
> 
>   Also, there is now noticeable flicker which is giving me quite a
>   headache. I've used the same horizontal and vertical refresh rates
>   that were present in v3, but I see in the log below that I'm only
>   pulling 60 Hz, rather than 75 or higher. Suggestions?

Hi Bill.

I just set up X 3.3.6 on my latest box just last week.  Here is
something I discovered, although it won't help your woes on 1280x1024.
The refresh rates on your other resolutions is about 85 Hz, which is
getting near the upper limit on your monitor.  In my case I was also
frustrated by an picture I couldn't resize.  After further investigation
I found that the X server deletes all but the "best" video modes.  So I
commented out all but a standard VESA mode at 72 Hz.  Now I had a much
better alinged screen that I could tweak to be centered and then used my
monitor adjustments (NEC XV15) to bring the screen edge-to-edge.  The
result was that for 800x600 and 1024x768 I now had a nice full screen
display, while 640x480 and text mode have a bit of a border which is not
a problem.

>   I also noted that mga_hal failed to load. Is this a problem?
> 
>   Are there any other tools besides SuperProbe that can be used to
>   debug/adjust these things?
> 
>   Thanks for any help you all can provide.
> 
>   Here's the log:

<snip>
> 
> (==) MGA(0): Using gamma correction (1.0, 1.0, 1.0)
> (==) MGA(0): Min pixel clock is 12 MHz
> (==) MGA(0): Max pixel clock is 250 MHz
> (II) MGA(0): NEC MultiSync 6FG: Using hsync range of 27.00-79.00 kHz
> (II) MGA(0): NEC MultiSync 6FG: Using vrefresh range of 55.00-90.00 Hz
> (II) MGA(0): Clock range:  12.00 to 250.00 MHz
> (WW) MGA(0): Default mode "1280x960" deleted (hsync out of range)
> (WW) MGA(0): Default mode "1280x1024" deleted (hsync out of range)
> (WW) MGA(0): Default mode "1280x1024" deleted (hsync out of range)
> (WW) MGA(0): Default mode "1600x1200" deleted (hsync out of range)
> (WW) MGA(0): Default mode "1600x1200" deleted (hsync out of range)
> (WW) MGA(0): Default mode "1600x1200" deleted (hsync out of range)
> (WW) MGA(0): Default mode "1600x1200" deleted (hsync out of range)
> (WW) MGA(0): Default mode "1792x1344" deleted (hsync out of range)
> (WW) MGA(0): Default mode "1792x1344" deleted (bad mode clock/interlace/doublescan)
> (WW) MGA(0): Default mode "1856x1392" deleted (hsync out of range)
> (WW) MGA(0): Default mode "1856x1392" deleted (bad mode clock/interlace/doublescan)
> (WW) MGA(0): Default mode "1920x1440" deleted (hsync out of range)
> (WW) MGA(0): Default mode "1920x1440" deleted (bad mode clock/interlace/doublescan)
> (--) MGA(0): Virtual size is 1280x1024 (pitch 1280)
> (**) MGA(0): Default mode "1280x1024": 108.0 MHz, 64.0 kHz, 60.0 Hz
> (**) MGA(0): Default mode "1024x768": 94.5 MHz, 68.7 kHz, 85.0 Hz
> (**) MGA(0): Default mode "800x600": 56.3 MHz, 53.7 kHz, 85.1 Hz
> (**) MGA(0): Default mode "640x480": 36.0 MHz, 43.3 kHz, 85.0 Hz
> (==) MGA(0): DPI set to (75, 75)
> (II) MGA(0): YDstOrg is set to 0

Of course, with the changes from 3.3.x to 4.0.x the problem could be
elsewhere.  Such is the bleeding edge.

- Nate >>

-- 
 Wireless | Amateur Radio Station N0NB          | "None can love freedom
 Internet | n0nb@networksplus.net               | heartily, but good
 Location | Wichita, Kansas USA EM17hs          | men; the rest love not
   Wichita area exams; ham radio; Linux info @  | freedom, but license."
             http://www.qsl.net/n0nb/           | -- John Milton



Reply to: