Linux - NewbieThis Linux forum is for members that are new to Linux.
Just starting out and have a question?
If it is not in the man pages or the how-to's this is the place!
Notices
Welcome to LinuxQuestions.org, a friendly and active Linux Community.
You are currently viewing LQ as a guest. By joining our community you will have the ability to post topics, receive our newsletter, use the advanced search, subscribe to threads and access many other special features. Registration is quick, simple and absolutely free. Join our community today!
Note that registered members see fewer ads, and ContentLink is completely disabled once you log in.
If you have any problems with the registration process or your account login, please contact us. If you need to reset your password, click here.
Having a problem logging in? Please visit this page to clear all LQ-related cookies.
Get a virtual cloud desktop with the Linux distro that you want in less than five minutes with Shells! With over 10 pre-installed distros to choose from, the worry-free installation life is here! Whether you are a digital nomad or just looking for flexibility, Shells can put your Linux machine on the device that you want to use.
Exclusive for LQ members, get up to 45% off per month. Click here for more info.
I'm using Fedora Core 2 and I'd like to connect my nVidia FX5700 card with my TV.
I tried using yanc, but this didn't work cause of x.org.
I just bought my first TV in 4 years, so I really don't know how to start.
(I do know it's PAL)
# 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
# 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 "XkbModel" "pc105"
Option "XkbLayout" "be"
EndSection
TwinView can put the same image on your monitor and TV, or just select one of the two outputs. Unfortunately, you have to run them both at the same refresh rate.
Xinerama puts the screens next to each other to make one big virtual desktop; unfortunately, you can only use acceleration on one output with Xinerama.
I have an nVidia GFX 5800 and a PAL TV (UK => PAL-I).
I've got the TV more-or-less working in TwinView. The only problem I get is that the colours go wobbly on my TV; this is probably a timing problem, please see my other thread for details.
Here's some bits of my XFree86Config file; It's a bit rough but I hope it may come in useful. Please post details if you can get it working properly!
Code:
Section "Monitor"
DisplaySize 250 190
HorizSync 15-50
Identifier "Monitor[0]"
ModelName "1451"
Option "DPMS"
VendorName "CTX"
VertRefresh 45-90
# VertRefresh 1-1200
UseModes "Modes[0]"
EndSection
Section "Modes"
Identifier "Modes[0]"
Modeline "1024x768" 61.89 1024 1096 1200 1344 768 769 772 794
Modeline "800x600" 51.73 800 840 928 1024 600 681 684 628
Modeline "640x480" 36.97 640 720 784 832 480 481 484 505
ModeLine "1024x768PAL" 25 1024 1056 1152 1256 768 836 838 960
EndSection
Section "Screen"
DefaultDepth 16
SubSection "Display"
Depth 16
Modes "1024x768PAL" "800x600" "640x480"
EndSubSection
Device "Device[0]"
Identifier "Screen[0]"
Monitor "Monitor[0]"
EndSection
Section "Device"
Identifier "Device[0]"
Driver "nvidia"
VendorName "NVidia"
BoardName "NVIDIA GeForce FX (generic)"
Option "TwinView" "true"
Option "TVStandard" "PAL-I" # PAL-N shows as B/W
Option "TVOutFormat" "SVIDEO"
Option "SecondMonitorHorizSync" "15.625" # "28-50" # 28-33 def
Option "SecondMonitorVertRefresh" "50-60"
Option "TwinViewOrientation" "CLONE"
Option "ConnectedMonitor" "TV" # Use CRT,TV for both
# TODO: Use NULL to indicate not to use a given mode. Can also add +x+y offset
# Can also add @mode for panning resolution
Option "MetaModes" "1024x768,1024x768;800x600,800x600;640x480,640x480"
EndSection
Your monitor is turning off because you don't have it listed as a connected device:
Code:
Option "ConnectedMonitor" "CRT,TV"
In order for that to work, X will need to know about a resolution that is valid both for the monitor and the TV. TVs generally operate at either 50Hz (PAL) or 60Hz (NTSC), whereas monitors tend to have a lower bound at around 60-70Hz, so there may not even be a valid mode for both devices (in which case, you'll need to use Xinerama not TwinView).
As for the colours, you may have a wrong TVStandard (see the driver doc for a list of valid settings), or your ModeLine itself might be wrong. You might improve the signal somewhat by adding a custom mode-line (hence the 1024x768PAL mode in my previous post), and referencing it in the screen section.
LinuxQuestions.org is looking for people interested in writing
Editorials, Articles, Reviews, and more. If you'd like to contribute
content, let us know.
