Bug#326133: xserver-xorg: VIA driver : Option TVVscan not working or unavailable
Hi Luc,
On 9/2/05, Luc Verhaegen <libv@skynet.be> wrote:
> On Fri, Sep 02, 2005 at 01:18:17AM +0200, Roel Teuwen wrote:
>
> > (II) VIA(0): Not a mode defined by the TV Encoder.
>
> > (--) VIA(0): Virtual size is 720x576 (pitch 720)
> > (**) VIA(0): *Default mode "720x576": 28.5 MHz (scaled from -0.0 MHz),
> > 37.5 kHz, 50.0 Hz
> > (II) VIA(0): Modeline "720x576" 28.50 720 728 744 760 576 635 643
> > 750 -hsync +vsync
> > (**) VIA(0): Default mode "720x576Over": 27.0 MHz (scaled from 0.0
> > MHz), 31.2 kHz, 50.0 Hz
> > (II) VIA(0): Modeline "720x576Over" 27.00 720 768 800 864 576 577
> > 579 625 -hsync +vsync
> > (**) VIA(0): Default mode "640x480": 30.0 MHz (scaled from 0.0 MHz),
> > 30.0 kHz, 50.0 Hz
> > (II) VIA(0): Modeline "640x480" 30.00 640 680 808 1000 480 520 523
> > 600 -hsync -vsync
>
> The via driver used to fool some people into thinking that it was running
> their provided or a builtin modeline, while, when lucky, all it cared
> about was H/VDisplay.
Ok, I'm not sure how the modeline ties in with the TVVscan; but the
output you quoted pointed me to the fact that I was indeed using the
"old" method to do overscan. When removing the modeline and simply
defining the 720x576Over resolution to be used, overscan works.
However, Now the image on the TV screen flickers to a point where it
is unusable.
> Now it's no longer fooling anyone much, it's just restricting to what it
> does know, and that is currently what the VT1622 code adds itself. This
> is quite some distance ahead of previous behaviour. Further improvement
> will require a sisctrl like application, which is one of the many things
> on my TODO list.
>
> The list of available modes is provided in the manpage. I have reproduced
> what was accepted by your X, and reported in your log, above.
Yes, I missed these as I did not make the link between the Over suffix
and overscan. I was used to it being a seperate option.
Any hints about the image flicker issue ?
Thank you for your quick reply and apologies for my late one.
Best regards,
Roel
Reply to: