LinuxQuestions.org

LinuxQuestions.org (/questions/)
-   Slackware (https://www.linuxquestions.org/questions/slackware-14/)
-   -   TV-out is working but picture "scrolls" and dosent fill... (https://www.linuxquestions.org/questions/slackware-14/tv-out-is-working-but-picture-scrolls-and-dosent-fill-421886/)

zanor 03-05-2006 01:11 PM

TV-out is working but picture "scrolls" and dosent fill...
 
Hi!

Just got TV-out working in KDE with my ATI PowerColor 9550 card in clone view.
But the picture on my TV dosent show the whole screen but follows the mouse as it reaches the edge if you understand.
Does anyone know how to scale or fix this?

And an other thing, in WinXP I could choose to "overscan" so the picture would cover my whole TV screen and not have those black bars at top and bottom. Is there a simular feauture in Linux?

btw, this is my xorg.conf file:
Code:

Section "ServerLayout"

# The Identifier line must be present
# Each Screen line specifies a Screen section name, and optionally
# the relative position of other screens.  The four names after
# primary screen name are the screens to the top, bottom, left and right
# of the primary screen.  In this example, screen 2 is located to the
# right of screen 1.
# Each InputDevice line specifies an InputDevice section name and
# optionally some options to specify the way the device is to be
# used.  Those options include "CorePointer", "CoreKeyboard" and
# "SendCoreEvents".
        Identifier    "Simple Layout"
        Screen      0  "aticonfig Screen 0" 0 0
        InputDevice    "Mouse1" "CorePointer"
        InputDevice    "Keyboard1" "CoreKeyboard"
EndSection

Section "Files"

# 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 (which are concatenated together),
# as well as specifying multiple comma-separated entries in one FontPath
# command (or a combination of both methods)
#
# If you don't have a floating point coprocessor and emacs, Mosaic or other
# programs take long to start up, try moving the Type1 and Speedo directory
# to the end of this list (or comment them out).
#
# ModulePath can be used to set a search path for the X server modules.
# The default path is shown here.
#    ModulePath "/usr/X11R6/lib/modules"
        RgbPath      "/usr/X11R6/lib/X11/rgb"
        FontPath    "/usr/X11R6/lib/X11/fonts/local/"
        FontPath    "/usr/X11R6/lib/X11/fonts/misc/"
        FontPath    "/usr/X11R6/lib/X11/fonts/75dpi/:unscaled"
        FontPath    "/usr/X11R6/lib/X11/fonts/100dpi/:unscaled"
        FontPath    "/usr/X11R6/lib/X11/fonts/Type1/"
        FontPath    "/usr/X11R6/lib/X11/fonts/CID/"
        FontPath    "/usr/X11R6/lib/X11/fonts/Speedo/"
        FontPath    "/usr/X11R6/lib/X11/fonts/75dpi/"
        FontPath    "/usr/X11R6/lib/X11/fonts/100dpi/"
        FontPath    "/usr/X11R6/lib/X11/fonts/cyrillic/"
EndSection

Section "Module"

# This loads the DBE extension module.
# This loads the miscellaneous extensions module, and disables
# initialisation of the XFree86-DGA extension within that module.
# This loads the font modules
# This loads the GLX module
        Load  "dbe"          # Double buffer extension
        SubSection "extmod"
                Option            "omit xfree86-dga"  # don't initialise the DGA extension
        EndSubSection
        Load  "type1"
        Load  "freetype"
    #Load        "speedo"
        Load  "glx"
        Load  "dri"
EndSection

Section "InputDevice"

# For most OSs the protocol can be omitted (it defaults to "Standard").
# When using XQUEUE (only for SVR3 and SVR4, but not Solaris),
# uncomment the following line.
#    Option    "Protocol"      "Xqueue"
# Set the keyboard auto repeat parameters.  Not all platforms implement
# this.
#    Option    "AutoRepeat"    "500 5"
# Specifiy 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 European
# keyboard, you will probably want to use one of:
#
#    Option    "XkbModel"      "pc102"
#    Option    "XkbModel"      "pc105"
#
# If you have a Microsoft Natural keyboard, you can use:
#
#    Option    "XkbModel"      "microsoft"
#
# If you have a US "windows" keyboard you will want:
#
#    Option    "XkbModel"      "pc104"
#
# 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"
# These are the default XKB settings for X.Org
#
#    Option    "XkbRules"      "xorg"
#    Option    "XkbModel"      "pc101"
#    Option    "XkbOptions"    ""
        Identifier  "Keyboard1"
        Driver      "kbd"
        Option            "XkbLayout" "no"
#    Option    "XkbVariant"    ""
EndSection

Section "InputDevice"

# Identifier and driver
# On platforms where PnP mouse detection is supported the following
# protocol setting can be used when using a newer PnP mouse:
#    Option    "Protocol"      "Auto"
# The available mouse protocols types that you can set below are:
#    Auto BusMouse GlidePoint GlidePointPS/2 IntelliMouse IMPS/2
#    Logitech Microsoft MMHitTab MMSeries Mouseman MouseManPlusPS/2
#    MouseSystems NetMousePS/2 NetScrollPS/2 OSMouse PS/2 SysMouse
#    ThinkingMouse ThinkingMousePS/2 Xqueue
# which is usually a symbolic link to the real device.
#  Option "Device"      "/dev/ttyS0"
#  Option "Device"      "/dev/ttyS1"
# When using XQUEUE, comment out the above two lines, and uncomment
# the following line.
#    Option "Protocol"        "Xqueue"
# Baudrate and SampleRate are only for some Logitech mice. In
# almost every case these lines should be omitted.
#    Option "BaudRate"                "9600"
#    Option "SampleRate"        "150"
# Emulate3Buttons is an option for 2-button Microsoft mice
# Emulate3Timeout is the timeout in milliseconds (default is 50ms)
#    Option "Emulate3Buttons"
#    Option "Emulate3Timeout"    "50"
# ChordMiddle is an option for some 3-button Logitech mice
#    Option "ChordMiddle"
        Identifier  "Mouse1"
        Driver      "mouse"
        Option            "Protocol" "IMPS/2"
        Option            "ZAxisMapping" "4 5"
# The mouse device.  The device is normally set to /dev/mouse,
        Option            "Device" "/dev/mouse"
#  Option "Device"      "/dev/psaux"
EndSection

Section "Monitor"

# HorizSync is in kHz unless units are specified.
# HorizSync may be a comma separated list of discrete values, or a
# comma separated list of ranges of values.
# NOTE: THE VALUES HERE ARE EXAMPLES ONLY.  REFER TO YOUR MONITOR'S
# USER MANUAL FOR THE CORRECT NUMBERS.
#    HorizSync        30-64        # multisync
#    HorizSync        31.5, 35.2    # multiple fixed sync frequencies
#    HorizSync        15-25, 30-50  # multiple ranges of sync frequencies
# VertRefresh is in Hz unless units are specified.
# VertRefresh may be a comma separated list of discrete values, or a
# comma separated list of ranges of values.
# NOTE: THE VALUES HERE ARE EXAMPLES ONLY.  REFER TO YOUR MONITOR'S
# USER MANUAL FOR THE CORRECT NUMBERS.
        Identifier  "My Monitor"
        HorizSync    31.5 - 50.0
        VertRefresh  40.0 - 90.0
EndSection

Section "Monitor"
        Identifier  "aticonfig Monitor 0"
EndSection

Section "Device"
        Identifier  "ATI Graphics Adapter 0"
        Driver      "fglrx"
        Option            "(null)"
        Option            "TVFormat" "PAL-B"
        Option            "DesktopSetup" "Clone"
        Option            "OverlayOnTV" "1"
        Option            "TVStandard" "PAL-D"
        Option            "ForceMonitors" "crt1,tv"
        BusID      "PCI:1:0:0"
EndSection

Section "Screen"

# If your card can handle it, a higher default color depth (like 24 or 32)
# is highly recommended.
#  DefaultDepth 8
#  DefaultDepth 16
#  DefaultDepth 32
# "1024x768" is also a conservative usable default resolution.  If you
# have a better monitor, feel free to try resolutions such as
# "1152x864", "1280x1024", "1600x1200", and "1800x1400" (or whatever your
# card/monitor can produce)
        Identifier "Screen 1"
        Device    "ATI Graphics Adapter 0"
        Monitor    "My Monitor"
        DefaultDepth    24
        SubSection "Display"
                Depth    8
                Modes    "1600x1200" "1024x768" "800x600" "640x480"
        EndSubSection
        SubSection "Display"
                Depth    16
                Modes    "1600x1200" "1024x768" "800x600" "640x480"
        EndSubSection
        SubSection "Display"
                Depth    24
                Modes    "1600x1200" "1024x768" "800x600" "640x480"
        EndSubSection
        SubSection "Display"
                Depth    32
                Modes    "1024x768" "800x600" "640x480"
        EndSubSection
EndSection

Section "Screen"
        Identifier "aticonfig Screen 0"
        Device    "ATI Graphics Adapter 0"
        Monitor    "aticonfig Monitor 0"
        DefaultDepth    24
        SubSection "Display"
                Viewport  0 0
                Depth    24
        EndSubSection
EndSection

Section "DRI"
        Mode        0666
EndSection


yuchai 03-06-2006 09:36 AM

What method are you using to connect to the TV?

If you're using Svideo or composite out I believe the max resolution on the TV is 1024 x 768. If you use any higher resolution it would resort to the scrolling.

shilo 03-07-2006 03:10 AM

I am not familiar with ATI cards, but I may be able to help.

I have set up a box that connects only to a TV. The resolution is correct, but I observed the same problem as you, where the virtual size of the screen/desktop was larger than the actual resolution. This caused the scrolling like you are talking about. This also happened on regular monitors. I hope this makes sense:

Before:

Code:

Section "Screen"
    Identifier  "Screen 1"
    Device    "Card0"
    Monitor    "My Monitor"
    DefaultDepth 24

    SubSection    "Display"
        Viewport    0 0
        Depth      24
        Modes      "1280x960" "1280x1024" "1024x768" "800x600" "640x480"
        EndSubSection
EndSection

After:

Code:

Section "Screen"
    Identifier  "Screen 1"
    Device    "Card0"
    Monitor    "My Monitor"
    DefaultDepth 24

    SubSection    "Display"
        Viewport    0 0
        Depth      24
        Modes      "1280x960" "1280x1024" "1024x768" "800x600" "640x480"
        Virtual    1280 960
    EndSubSection
EndSection

Read /var/log/Xorg.0.log to see if this will help you. Basically, you will see that the vitual size is not equal to the actual resolution. Add a line like the above in red, only make it for the resoltution that you want. THis only works if the log shows the correct resolution but wrong virtual size.

For overscan, I use NVIDIA, which provides documentation for implementing overscan. Check the DOCS for ATI. The may provide similar.

aihaike 03-10-2006 07:20 AM

Hello,

praticaly, after set up the xorg file, whao can i display what I have on my screen on tv? I mean, is there key combination?
Do i have to set up the scrren section before use my tv and then set up bask to use my screen?
I've a slackware 10.2 on a dell inspiron 5100 ....
Thanks.
Eric.


All times are GMT -5. The time now is 11:07 AM.