[mythtv-users] Horizontal Line Flicker and Motion Drag Lines :(

[Clif Deanhardt]

Hi All,

I'm seeing the horizontal line flicker that I've seen mentioned here before,
as well as the horizontal drag lines on moderately fast moving things on the
screen during playback.  Does anyone know how to clear these? The
infuriating thing is that I'd seen these on a previous incarnation of this
machine (when I was running Mandrake 9) and it was one of the problems that
I was actually able to fix.  But I was dumb enough not to write the fix
down.  Unfortunately,  I had other more serious problems and decided to drop
back to RedHat.  Now all the other problems I was seeing are gone, but these
blasted lines are back!

Does anyone know how to get rid of them? I believe the two are related, and
that the problem lies with the configuration of the video out
drivers/XWindows.  I haven't tested this 'cause I'm  not savy enough to know
how to turn the .nuv files into something I can see on my windows box, so in
the case of the motion drag lines it *might* be the 250 and ivtv, but I
doubt it.

Any help would be most appreciated!

Clif Deanhardt

My Machine ----------------------

VIA KT266 Chipset
Athalon 2300+
256MB Ram
PVR250
NVidia MX440SE TV-Out
RH9
Myth 0.11

My XF86Config file ---------------
# XFree86 4 configuration created by pyxf86config

Section "ServerLayout"
        Identifier     "Default Layout"
        Screen      0  "Screen0" 0 0
        InputDevice    "Mouse0" "CorePointer"
        InputDevice    "Keyboard0" "CoreKeyboard"
        InputDevice    "DevInputMice" "AlwaysCore"
EndSection

Section "Files"
# RgbPath is the location of the RGB database.  Note, this is the name of
the
# file minus the extension (like ".txt" or ".db").  There is normally
# no need to change the default.

# Multiple FontPath entries are allowed (they are concatenated together)
# By default, Red Hat 6.0 and later now use a font server independent of
# the X server to render fonts.

        RgbPath      "/usr/X11R6/lib/X11/rgb"
        FontPath     "unix/:7100"
EndSection

Section "Module"
        Load  "dbe"
        Load  "extmod"
        Load  "fbdevhw"
        Load  "glx"
        Load  "record"
        Load  "freetype"
        Load  "type1"
#       Load  "dri"
        Load  "v4l"
EndSection

Section "InputDevice"
# Specify which keyboard LEDs can be user-controlled (eg, with xset(1))
#       Option  "Xleds"         "1 2 3"

# To disable the XKEYBOARD extension, uncomment XkbDisable.
#       Option  "XkbDisable"

# To customise the XKB settings to suit your keyboard, modify the
# lines below (which are the defaults).  For example, for a non-U.S.
# keyboard, you will probably want to use:
#       Option  "XkbModel"      "pc102"
# If you have a US Microsoft Natural keyboard, you can use:
#       Option  "XkbModel"      "microsoft"
#
# Then to change the language, change the Layout setting.
# For example, a german layout can be obtained with:
#       Option  "XkbLayout"     "de"
# or:
#       Option  "XkbLayout"     "de"
#       Option  "XkbVariant"    "nodeadkeys"
# If you'd like to switch the positions of your capslock and
# control keys, use:
#       Option  "XkbOptions"    "ctrl:swapcaps"
# Or if you just want both to be control, use:
#       Option  "XkbOptions"    "ctrl:nocaps"
#
        Identifier  "Keyboard0"
        Driver      "keyboard"
        Option      "XkbRules" "xfree86"
        Option      "XkbModel" "pc105"
        Option      "XkbLayout" "us"
EndSection

Section "InputDevice"
        Identifier  "Mouse0"
        Driver      "mouse"
        Option      "Protocol" "IMPS/2"
        Option      "Device" "/dev/psaux"
        Option      "ZAxisMapping" "4 5"
        Option      "Emulate3Buttons" "no"
EndSection

Section "InputDevice"
# If the normal CorePointer mouse is not a USB mouse then
# this input device can be used in AlwaysCore mode to let you
# also use USB mice at the same time.
        Identifier  "DevInputMice"
        Driver      "mouse"
        Option      "Protocol" "IMPS/2"
        Option      "Device" "/dev/input/mice"
        Option      "ZAxisMapping" "4 5"
        Option      "Emulate3Buttons" "no"
EndSection

Section "Monitor"
        Identifier   "Monitor0"
        VendorName   "Monitor Vendor"
        ModelName    "eView 17f2"
        DisplaySize  320        240
        HorizSync    30.0 - 70.0
        VertRefresh  50.0 - 160.0
EndSection






 Section "Device"
Identifier  "Videocard0"
Driver      "nvidia"
VendorName  "Chaintech"
BoardName   "nVidia GeForce 4 MX 440"
Option      "RenderAccel" "1"
# TV Out Setup
#Option      "TwinView"
#Option      "TwinViewOrientation" "Clone"
#Option      "SecondMonitorHorizSync" "30-50"
#Option      "SecondMonitorVertRefresh" "60"
#Option      "MetaModes" "800x600, 800x600; 640x480, 640x480;"
#Option      "MetaModes" "1024x768, 1024x768; 800x600, 800x600; 640x480,
640x480;"
Option      "TVStandard" "NTSC-M"
Option      "TVOutFormat" "SVIDEO"
Option      "TVOverScan" "0.6"
Option      "NvAgp" "1"
Option      "ConnectedMonitor" "TV"
EndSection

Section "Monitor"
        Identifier   "Monitor1"
        VendorName   "TV"
        ModelName    "eView 17f2"
        DisplaySize  320        240
        HorizSync    30.0 - 50.0
        VertRefresh  60.0
EndSection


Section "Screen"
        Identifier "Screen0"
        Device     "Videocard0"
        Monitor    "Monitor1"
        DefaultDepth     24
        SubSection "Display"
                Depth     24
                Modes    "640x480"
        EndSubSection
EndSection

Section "DRI"
        Group        0
        Mode         0666
EndSection