| Author |
Message |
|
Mnemic
|
 Posted: Mon Dec 19, 2005 2:00 pm |
|
|
Joined: Fri Aug 27, 2004 8:08 am
Posts: 25
Location:
Nashville, TN
|
|
I'm trying to find some information about the best way to drive a flatpanel TVs, that have a Fixed Pixel Resolution, yet accept signals upto 1080i.
I have a Sharp Aquos 32" LCD TV, that has a Native resolution of 1366x768 (Wide XGA), but will accept a 1080i signal.
Now I know 1080i DVI + Nvidia are not friends right now, so the solution for now would be a VGA->Component and send the TV a 1080i signal over component, send a 720P over DVI or try and Run the TV in its native pixel resolution of 1366x768.
Whats the General concensus when it comes to driving non-true 1080i displays that support 1080i?
_________________
PVR-350
pcHDTV-5500
USB 150MCE IR-Receiver
Geforce 6600GT AGP
|
|
| Top |
|
 |
|
ceenvee703
|
Posted: Mon Dec 19, 2005 4:22 pm |
|
|
Joined: Fri Apr 02, 2004 10:08 am
Posts: 1637
Location:
Virginia, USA
|
|
You could send it 1080i, but it will end up scaling it to its native resolution of 1366x768.
I would say to send it as close to 1366x768 as you can, via DVI. Why go digital->analog (VGA)->analog(component)->digital (TV) if you can just stay digital via DVI?
I run 1280x720 over DVI and like it just fine. I'd love to find a 1:1 pixel mapped modeline at 1366x768 but have stopped losing sleep over it.
|
|
| Top |
|
|
|
Mnemic
|
Posted: Tue Dec 20, 2005 10:15 am |
|
|
Joined: Fri Aug 27, 2004 8:08 am
Posts: 25
Location:
Nashville, TN
|
Few updates.
Played around with it for a few hours last night.
Took awhile to get the hang of it, Been a long time since I've had to deal with modelines in X... Like Pre-autodetect monitor settings in X.. 
Even Tried using my laptop + powerstrip, which ultimately just ended up in fustration, so I went the Linux Trial + Error route. Note that With JUST the DVI pluged in, the bios and linux console work from the start. TV shows 1080i from bootup, and whenever on a console.
Initaly I was using the nvidia Driver installed by R5A26. The stupid dde autotection stuff was running everytime, and when it did, It would not accept a modeline I provided. It kept defaulting to 640x480 output to the Aquos, which worked with X. Renaming the library /usr/X11RC/lib/libdde.o (? think that was the location/file) made it skip auto-detection, and finaly got 1280x720 and even a variant of 1366x768 working. both with about 5% too much overscan all around, a step in the right direction. However at these resolutions, X would take all of the CPU and pretty much nearly lock up the box whenever I initated Watch TV, or any recordings. Did not try mplayer.
Next I upgraded to the latest NV Drivers available 8174, which has a diffrent autodetection scheme, and was back to the problem of it not accepting my modelines, and defaulting to 800x600 now. however At this point I found some the "startx -- -logverbose 6" command, and gave it a whirl. Interestingly enough, The Logfile for X this time had the DisplayPanel's ranges listed! Finaly something useful to work with 
Hsync, Vsync, and a number of predefined Modelines all in the log file. X log also said "Adding modeline:" for the 4 or so predefined modelines, but I could not get it to use any of them. So Armed with my TV's requested specs I headed to http://xtiming.sourceforge.net/cgi-bin/xtiming.pl and began making custom modelines for my display. Every modeline I made this way worked, but have the same ~5% too much overscan on all borders. I'm currently using a variant of 1366x768@60 Generated by the web generator. tonite I'm going to start reducing pixels until I get it centered and have the overscan issues taken care of.
Step in the right direction!
_________________
PVR-350
pcHDTV-5500
USB 150MCE IR-Receiver
Geforce 6600GT AGP
|
|
| Top |
|
|
|
Liv2Cod
|
Posted: Tue Dec 20, 2005 11:37 am |
|
|
Joined: Fri May 21, 2004 11:55 pm
Posts: 1206
Location:
Silicon Valley, CA
|
|
Overscan is the dirty little secret of HDTV manufacturers. I don't know why overscan even exists for digital TV, but it does.
I have an "analog" TV (CRT based rear projection) and I had to get it "tuned" to eliminate the overscan at great expense. I hoped that the new generation of digital display devices would finally make overscan a thing of the past, but the manufacturers have kept it in, making digital TV much more of a hit-and-miss game for picture quality.
I think digital TVs should behave more like monitors, with at least an option of zero overscan.
_________________ Do you code to live, or live to code? Search LinHES forum through Google
|
|
| Top |
|
|
|
ceenvee703
|
Posted: Tue Dec 20, 2005 11:54 am |
|
|
Joined: Fri Apr 02, 2004 10:08 am
Posts: 1637
Location:
Virginia, USA
|
Quote: I don't know why overscan even exists for digital TV, but it does.
My guess is that sooooo much production is done assuming overscan exists, that stuff would start showing up on-screen that isn't supposed to display ("hey, it's outside of action-safe, no one'll ever see it!"). So someone (networks? studios? other?) pushed to include overscan in digital TVs as well.
|
|
| Top |
|
|
|
Mnemic
|
Posted: Tue Dec 20, 2005 12:00 pm |
|
|
Joined: Fri Aug 27, 2004 8:08 am
Posts: 25
Location:
Nashville, TN
|
Liv2Cod wrote: I think digital TVs should behave more like monitors, with at least an option of zero overscan.
I whole heardly agree... Its stupid. The View Modes are not even an option on my TV when its using the DVI. Its locked in. I think the more commercial Panels handle straight PC signals much better, and act like a monitor.
Its interesting however to actualy "see" more of the picture when watching via firewire through the Mythbox, then when watching directly from Component. makes you realize even with these Settop Boxes, they are doing something to compensate for overscan.
the LCD Panel, when I hooked it upto the DVI on my laptop, even autodeteced in windows, it was overscanned.
Maybe we just need to cut back plastic off our Displays
ARRR! D'ere be 'iden Pixels under Thar Plastic!
_________________
PVR-350
pcHDTV-5500
USB 150MCE IR-Receiver
Geforce 6600GT AGP
|
|
| Top |
|
|
|
WheatKing
|
Posted: Wed Jan 04, 2006 10:04 pm |
|
|
Joined: Fri Jan 30, 2004 10:48 pm
Posts: 31
|
|
if possible.. drive it at it's native panel rate...
your PC can probably scale the video much better than the chipset inside of the tv.. unless your running it though an external scaler (lumagen or dvdo iscan) or your tv has a high quality farouja chipset in it to handle the scaling..
most digital tv's with wxga chipsets i've seen have horrible scalers.
|
|
| Top |
|
|
|
RichardBronosky
|
Posted: Thu Jan 19, 2006 5:11 pm |
|
|
Joined: Tue Aug 16, 2005 11:50 am
Posts: 181
Location:
Douglasville, GA
|
|
So what was the solution you used? I have one of these TVs too. LC32D4U to be exact.
I would love to know the exact modeline you used. I am also having a problem with the terminal be way overscan so much that I must use the remote to adjust the position just to see a document in VI.
I am totally new to Linux and freex86, so if you can give me file paths with your answers that would be great!
|
|
| Top |
|
|
|
finger51
|
Posted: Mon May 29, 2006 11:34 am |
|
|
Joined: Tue Mar 22, 2005 11:56 am
Posts: 110
Location:
San Francisco
|
ceenvee703 wrote: I'd love to find a 1:1 pixel mapped modeline at 1366x768 but have stopped losing sleep over it.
I've got the HP version of that panel and I'm using this ML:
works great @1368x768
Modeline "1368x768" 85.86 1368 1440 1584 1800 768 769 772 795 -hsync -vsync
only two lines of overscan - give it a shot!
_________________
R5F27 | M2NPV-VM | 4600+ 65W AM2X2 | CORSAIR TWIN2X1024A-6400 | 2x HD-5000 |
DVI to HP LC3700N
|
|
| Top |
|
|
|
RichardBronosky
|
Posted: Wed May 31, 2006 7:26 am |
|
|
Joined: Tue Aug 16, 2005 11:50 am
Posts: 181
Location:
Douglasville, GA
|
finger51 wrote: give it a shot!
Could you paste your entire Monitor and Screen sections? I can't get that line to work cause I get "(hsync out of range)" in my /var/log/XFree86.0.log
If nothing else, what HorizSync and VertRefresh are you using?
|
|
| Top |
|
|
|
RichardBronosky
|
Posted: Wed May 31, 2006 8:28 am |
|
|
Joined: Tue Aug 16, 2005 11:50 am
Posts: 181
Location:
Douglasville, GA
|
This has gotten me closer, but it's still getting re-aliased and looks a little choppy. But I think it may be better the 720p mode I was using.
Modeline "1400x808@60i" 41.28 1400 1432 1584 1616 808 826 830 849 interlace
Any idea how to change the GDM wallpaper to a pattern that will help me do minor adjusting to the sizing and get rid of the re-aliasing? I need a pattern image and instructions on how to change it.
I gave up on working on this months ago, but I've gotten a little better with Linux now, and think I may be able to take it on again.
Edit: I just found http://www.knoppmythwiki.org/index.php?page=TestPattern which I will try, but I'd still like to know how to change the wallpaper.
|
|
| Top |
|
|
|
finger51
|
Posted: Wed May 31, 2006 2:27 pm |
|
|
Joined: Tue Mar 22, 2005 11:56 am
Posts: 110
Location:
San Francisco
|
RichardBronosky wrote: Could you paste your entire Monitor and Screen sections?
here ya go:
Code: #/etc/X11/XF86Config-4
Section "ServerLayout"
Identifier "XFree86 Configured"
Screen 0 "Screen0" 0 0
InputDevice "Keyboard0" "CoreKeyboard"
# PS/2 Mouse using /dev/input/mice in Kernel 2.6
# Serial Mouse not detected
InputDevice "USB Mouse" "CorePointer"
EndSection
Section "ServerFlags"
Option "AllowMouseOpenFail" "true"
EndSection
Section "Files"
RgbPath "/usr/X11R6/lib/X11/rgb"
ModulePath "/usr/X11R6/lib/modules"
FontPath "/usr/X11R6/lib/X11/fonts/misc:unscaled"
FontPath "/usr/X11R6/lib/X11/fonts/misc"
FontPath "/usr/X11R6/lib/X11/fonts/75dpi:unscaled"
FontPath "/usr/X11R6/lib/X11/fonts/75dpi"
FontPath "/usr/X11R6/lib/X11/fonts/100dpi:unscaled"
FontPath "/usr/X11R6/lib/X11/fonts/100dpi"
FontPath "/usr/X11R6/lib/X11/fonts/Speedo"
FontPath "/usr/X11R6/lib/X11/fonts/PEX"
# Additional fonts: Locale, Gimp, TTF...
FontPath "/usr/X11R6/lib/X11/fonts/cyrillic"
# FontPath "/usr/X11R6/lib/X11/fonts/latin2/75dpi"
# FontPath "/usr/X11R6/lib/X11/fonts/latin2/100dpi"
# True type and type1 fonts are also handled via xftlib, see /etc/X11/XftConfig!
FontPath "/usr/X11R6/lib/X11/fonts/Type1"
FontPath "/usr/share/fonts/ttf/western"
FontPath "/usr/share/fonts/ttf/decoratives"
FontPath "/usr/share/fonts/truetype"
FontPath "/usr/share/fonts/truetype/openoffice"
FontPath "/usr/share/fonts/truetype/ttf-bitstream-vera"
FontPath "/usr/share/fonts/latex-ttf-fonts"
FontPath "/usr/X11R6/lib/X11/fonts/defoma/CID"
FontPath "/usr/X11R6/lib/X11/fonts/defoma/TrueType"
EndSection
Section "Module"
Load "ddc" # ddc probing of monitor
# Load "GLcore"
Load "dbe"
# Load "dri"
Load "extmod"
Load "glx"
Load "bitmap" # bitmap-fonts
Load "speedo"
Load "type1"
Load "freetype"
Load "record"
EndSection
Section "InputDevice"
Identifier "Keyboard0"
Driver "keyboard"
Option "CoreKeyboard"
Option "XkbRules" "xfree86"
Option "XkbModel" "pc105"
Option "XkbLayout" "us"
EndSection
Section "InputDevice"
Identifier "Serial Mouse"
Driver "mouse"
Option "Protocol" "Microsoft"
Option "Device" "/dev/ttyS0"
Option "Emulate3Buttons" "true"
Option "Emulate3Timeout" "70"
Option "SendCoreEvents" "true"
EndSection
Section "InputDevice"
Identifier "PS/2 Mouse"
Driver "mouse"
Option "Protocol" "auto"
Option "ZAxisMapping" "4 5"
Option "Device" "/dev/psaux"
Option "Emulate3Buttons" "true"
Option "Emulate3Timeout" "70"
Option "SendCoreEvents" "true"
EndSection
Section "InputDevice"
Identifier "USB Mouse"
Driver "mouse"
Option "Device" "/dev/input/mice"
Option "SendCoreEvents" "true"
Option "Protocol" "IMPS/2"
Option "ZAxisMapping" "4 5"
Option "Buttons" "5"
EndSection
# Auto-generated by KNOPPIX mkxf86config
Section "Monitor"
Identifier "Monitor0"
Option "DPMS" "true"
# Inserted by dfinger
Option "IgnoreEDID" "True"
# HorizSync 28.0 - 78.0 # Warning: This may fry very old Monitors
HorizSync 28.0 - 96.0 # Warning: This may fry old Monitors
VertRefresh 50.0 - 75.0 # Very conservative. May flicker.
# VertRefresh 50.0 - 62.0 # Extreme conservative. Will flicker. TFT default.
# Default modes distilled from
# "VESA and Industry Standards and Guide for Computer Display Monitor
# Timing", version 1.0, revision 0.8, adopted September 17, 1998.
# $XFree86: xc/programs/Xserver/hw/xfree86/etc/vesamodes,v 1.4 1999/11/18 16:52:17 tsi Exp $
# 640x350 @ 85Hz (VESA) hsync: 37.9kHz
ModeLine "640x350" 31.5 640 672 736 832 350 382 385 445 +hsync -vsync
# 640x400 @ 85Hz (VESA) hsync: 37.9kHz
ModeLine "640x400" 31.5 640 672 736 832 400 401 404 445 -hsync +vsync
# 720x400 @ 85Hz (VESA) hsync: 37.9kHz
ModeLine "720x400" 35.5 720 756 828 936 400 401 404 446 -hsync +vsync
# 640x480 @ 60Hz (Industry standard) hsync: 31.5kHz
ModeLine "640x480" 25.2 640 656 752 800 480 490 492 525 -hsync -vsync
# 640x480 @ 72Hz (VESA) hsync: 37.9kHz
ModeLine "640x480" 31.5 640 664 704 832 480 489 491 520 -hsync -vsync
# 640x480 @ 75Hz (VESA) hsync: 37.5kHz
ModeLine "640x480" 31.5 640 656 720 840 480 481 484 500 -hsync -vsync
# 640x480 @ 85Hz (VESA) hsync: 43.3kHz
ModeLine "640x480" 36.0 640 696 752 832 480 481 484 509 -hsync -vsync
# 800x600 @ 56Hz (VESA) hsync: 35.2kHz
ModeLine "800x600" 36.0 800 824 896 1024 600 601 603 625 +hsync +vsync
# 800x600 @ 60Hz (VESA) hsync: 37.9kHz
ModeLine "800x600" 40.0 800 840 968 1056 600 601 605 628 +hsync +vsync
# 800x600 @ 72Hz (VESA) hsync: 48.1kHz
ModeLine "800x600" 50.0 800 856 976 1040 600 637 643 666 +hsync +vsync
# 800x600 @ 75Hz (VESA) hsync: 46.9kHz
ModeLine "800x600" 49.5 800 816 896 1056 600 601 604 625 +hsync +vsync
# 800x600 @ 85Hz (VESA) hsync: 53.7kHz
ModeLine "800x600" 56.3 800 832 896 1048 600 601 604 631 +hsync +vsync
# 1024x768i @ 43Hz (industry standard) hsync: 35.5kHz
ModeLine "1024x768" 44.9 1024 1032 1208 1264 768 768 776 817 +hsync +vsync Interlace
Modeline "1368x768" 85.86 1368 1440 1584 1800 768 769 772 795 -hsync -vsync
# 1024x768 @ 60Hz (VESA) hsync: 48.4kHz
ModeLine "1024x768" 65.0 1024 1048 1184 1344 768 771 777 806 -hsync -vsync
# 1024x768 @ 70Hz (VESA) hsync: 56.5kHz
ModeLine "1024x768" 75.0 1024 1048 1184 1328 768 771 777 806 -hsync -vsync
# 1024x768 @ 75Hz (VESA) hsync: 60.0kHz
ModeLine "1024x768" 78.8 1024 1040 1136 1312 768 769 772 800 +hsync +vsync
# 1024x768 @ 85Hz (VESA) hsync: 68.7kHz
ModeLine "1024x768" 94.5 1024 1072 1168 1376 768 769 772 808 +hsync +vsync
# 1152x864 @ 75Hz (VESA) hsync: 67.5kHz
ModeLine "1152x864" 108.0 1152 1216 1344 1600 864 865 868 900 +hsync +vsync
# 1280x960 @ 60Hz (VESA) hsync: 60.0kHz
ModeLine "1280x960" 108.0 1280 1376 1488 1800 960 961 964 1000 +hsync +vsync
# 1280x960 @ 85Hz (VESA) hsync: 85.9kHz
ModeLine "1280x960" 148.5 1280 1344 1504 1728 960 961 964 1011 +hsync +vsync
# 1280x1024 @ 60Hz (VESA) hsync: 64.0kHz
ModeLine "1280x1024" 108.0 1280 1328 1440 1688 1024 1025 1028 1066 +hsync +vsync
# 1280x1024 @ 75Hz (VESA) hsync: 80.0kHz
ModeLine "1280x1024" 135.0 1280 1296 1440 1688 1024 1025 1028 1066 +hsync +vsync
# 1280x1024 @ 85Hz (VESA) hsync: 91.1kHz
ModeLine "1280x1024" 157.5 1280 1344 1504 1728 1024 1025 1028 1072 +hsync +vsync
# 1600x1200 @ 60Hz (VESA) hsync: 75.0kHz
ModeLine "1600x1200" 162.0 1600 1664 1856 2160 1200 1201 1204 1250 +hsync +vsync
# 1600x1200 @ 65Hz (VESA) hsync: 81.3kHz
ModeLine "1600x1200" 175.5 1600 1664 1856 2160 1200 1201 1204 1250 +hsync +vsync
# 1600x1200 @ 70Hz (VESA) hsync: 87.5kHz
ModeLine "1600x1200" 189.0 1600 1664 1856 2160 1200 1201 1204 1250 +hsync +vsync
# 1600x1200 @ 75Hz (VESA) hsync: 93.8kHz
ModeLine "1600x1200" 202.5 1600 1664 1856 2160 1200 1201 1204 1250 +hsync +vsync
# 1600x1200 @ 85Hz (VESA) hsync: 106.3kHz
ModeLine "1600x1200" 229.5 1600 1664 1856 2160 1200 1201 1204 1250 +hsync +vsync
# 1792x1344 @ 60Hz (VESA) hsync: 83.6kHz
ModeLine "1792x1344" 204.8 1792 1920 2120 2448 1344 1345 1348 1394 -hsync +vsync
# 1792x1344 @ 75Hz (VESA) hsync: 106.3kHz
ModeLine "1792x1344" 261.0 1792 1888 2104 2456 1344 1345 1348 1417 -hsync +vsync
# 1856x1392 @ 60Hz (VESA) hsync: 86.3kHz
ModeLine "1856x1392" 218.3 1856 1952 2176 2528 1392 1393 1396 1439 -hsync +vsync
# 1856x1392 @ 75Hz (VESA) hsync: 112.5kHz
ModeLine "1856x1392" 288.0 1856 1984 2208 2560 1392 1393 1396 1500 -hsync +vsync
# 1920x1440 @ 60Hz (VESA) hsync: 90.0kHz
ModeLine "1920x1440" 234.0 1920 2048 2256 2600 1440 1441 1444 1500 -hsync +vsync
# 1920x1440 @ 75Hz (VESA) hsync: 112.5kHz
ModeLine "1920x1440" 297.0 1920 2064 2288 2640 1440 1441 1444 1500 -hsync +vsync
# Additional modelines
ModeLine "1800x1440" 230 1800 1896 2088 2392 1440 1441 1444 1490 +HSync +VSync
ModeLine "1800x1440" 250 1800 1896 2088 2392 1440 1441 1444 1490 +HSync +VSync
# Extended modelines with GTF timings
# 640x480 @ 100.00 Hz (GTF) hsync: 50.90 kHz; pclk: 43.16 MHz
ModeLine "640x480" 43.16 640 680 744 848 480 481 484 509 -HSync +Vsync
# 768x576 @ 60.00 Hz (GTF) hsync: 35.82 kHz; pclk: 34.96 MHz
ModeLine "768x576" 34.96 768 792 872 976 576 577 580 597 -HSync +Vsync
# 768x576 @ 72.00 Hz (GTF) hsync: 43.27 kHz; pclk: 42.93 MHz
ModeLine "768x576" 42.93 768 800 880 992 576 577 580 601 -HSync +Vsync
# 768x576 @ 75.00 Hz (GTF) hsync: 45.15 kHz; pclk: 45.51 MHz
ModeLine "768x576" 45.51 768 808 888 1008 576 577 580 602 -HSync +Vsync
# 768x576 @ 85.00 Hz (GTF) hsync: 51.42 kHz; pclk: 51.84 MHz
ModeLine "768x576" 51.84 768 808 888 1008 576 577 580 605 -HSync +Vsync
# 768x576 @ 100.00 Hz (GTF) hsync: 61.10 kHz; pclk: 62.57 MHz
ModeLine "768x576" 62.57 768 816 896 1024 576 577 580 611 -HSync +Vsync
# 800x600 @ 100.00 Hz (GTF) hsync: 63.60 kHz; pclk: 68.18 MHz
ModeLine "800x600" 68.18 800 848 936 1072 600 601 604 636 -HSync +Vsync
# 1024x768 @ 100.00 Hz (GTF) hsync: 81.40 kHz; pclk: 113.31 MHz
ModeLine "1024x768" 113.31 1024 1096 1208 1392 768 769 772 814 -HSync +Vsync
# 1152x864 @ 60.00 Hz (GTF) hsync: 53.70 kHz; pclk: 81.62 MHz
ModeLine "1152x864" 81.62 1152 1216 1336 1520 864 865 868 895 -HSync +Vsync
# 1152x864 @ 85.00 Hz (GTF) hsync: 77.10 kHz; pclk: 119.65 MHz
ModeLine "1152x864" 119.65 1152 1224 1352 1552 864 865 868 907 -HSync +Vsync
# 1152x864 @ 100.00 Hz (GTF) hsync: 91.50 kHz; pclk: 143.47 MHz
ModeLine "1152x864" 143.47 1152 1232 1360 1568 864 865 868 915 -HSync +Vsync
# 1280x960 @ 72.00 Hz (GTF) hsync: 72.07 kHz; pclk: 124.54 MHz
ModeLine "1280x960" 124.54 1280 1368 1504 1728 960 961 964 1001 -HSync +Vsync
# 1280x960 @ 75.00 Hz (GTF) hsync: 75.15 kHz; pclk: 129.86 MHz
ModeLine "1280x960" 129.86 1280 1368 1504 1728 960 961 964 1002 -HSync +Vsync
# 1280x960 @ 100.00 Hz (GTF) hsync: 101.70 kHz; pclk: 178.99 MHz
ModeLine "1280x960" 178.99 1280 1376 1520 1760 960 961 964 1017 -HSync +Vsync
# 1280x1024 @ 100.00 Hz (GTF) hsync: 108.50 kHz; pclk: 190.96 MHz
ModeLine "1280x1024" 190.96 1280 1376 1520 1760 1024 1025 1028 1085 -HSync +Vsync
# 1400x1050 @ 60.00 Hz (GTF) hsync: 65.22 kHz; pclk: 122.61 MHz
ModeLine "1400x1050" 122.61 1400 1488 1640 1880 1050 1051 1054 1087 -HSync +Vsync
# 1400x1050 @ 72.00 Hz (GTF) hsync: 78.77 kHz; pclk: 149.34 MHz
ModeLine "1400x1050" 149.34 1400 1496 1648 1896 1050 1051 1054 1094 -HSync +Vsync
# 1400x1050 @ 75.00 Hz (GTF) hsync: 82.20 kHz; pclk: 155.85 MHz
ModeLine "1400x1050" 155.85 1400 1496 1648 1896 1050 1051 1054 1096 -HSync +Vsync
# 1400x1050 @ 85.00 Hz (GTF) hsync: 93.76 kHz; pclk: 179.26 MHz
ModeLine "1400x1050" 179.26 1400 1504 1656 1912 1050 1051 1054 1103 -HSync +Vsync
# 1400x1050 @ 100.00 Hz (GTF) hsync: 111.20 kHz; pclk: 214.39 MHz
ModeLine "1400x1050" 214.39 1400 1512 1664 1928 1050 1051 1054 1112 -HSync +Vsync
# 1600x1200 @ 100.00 Hz (GTF) hsync: 127.10 kHz; pclk: 280.64 MHz
ModeLine "1600x1200" 280.64 1600 1728 1904 2208 1200 1201 1204 1271 -HSync +Vsync
EndSection
Section "Device"
### Available Driver options are:-
# sw_cursor is needed for some ati and radeon cards
#Option "sw_cursor"
#Option "hw_cursor"
#Option "NoAccel"
#Option "ShowCache"
#Option "ShadowFB"
#Option "UseFBDev"
#Option "Rotate"
Identifier "Card0"
# The following line is auto-generated by KNOPPIX mkxf86config
Driver "nvidia"
VendorName "All"
BoardName "All"
# BusID "PCI:1:0:0"
EndSection
Section "Screen"
Identifier "Screen0"
Device "Card0"
Monitor "Monitor0"
DefaultColorDepth 24
SubSection "Display"
Depth 1
Modes "1024x768" "800x600" "640x480"
EndSubSection
SubSection "Display"
Depth 4
Modes "1024x768" "800x600" "640x480"
EndSubSection
SubSection "Display"
Depth 8
Modes "1024x768" "800x600" "640x480"
EndSubSection
SubSection "Display"
Depth 15
Modes "1024x768" "800x600" "640x480"
EndSubSection
SubSection "Display"
Depth 16
Modes "1024x768" "800x600" "640x480"
EndSubSection
SubSection "Display"
Depth 24
Modes "1368x768" "1024x768" "800x600" "640x480"
EndSubSection
SubSection "Display"
Depth 32
Modes "1368x768" "1024x768" "800x600" "640x480"
EndSubSection
EndSection
Section "DRI"
Mode 0666
EndSection
_________________
R5F27 | M2NPV-VM | 4600+ 65W AM2X2 | CORSAIR TWIN2X1024A-6400 | 2x HD-5000 |
DVI to HP LC3700N
|
|
| Top |
|
|
|
afrosheen
|
Posted: Wed May 31, 2006 3:52 pm |
|
|
Joined: Sat Mar 26, 2005 3:49 pm
Posts: 290
|
|
I doubt this will help you much as the Aquos won't let you come up with a dot-for-dot mode. I've searched far and wide and experimented a little, and even via DVI-HDMI you can't avoid overscan.
However, what HAS worked better for me is to put mythgui and playback in a different size, separate from X's resolution. I feed my Aquos a 720p signal and resize the gui+playback to a much smaller size so it fits on the screen perfectly despite overscan. I still get re-aliased through the Sharp's hardware but there's no way around that on these LCDs unfortunately.
Tonight I plan to try feeding it a 1080i signal and resizing the gui again because 720p looks bugged out on my screen (flickery in some spots and generally not good). Plus my LCD has a bad HDMI port and after 2 months Sharp has done nothing to fix it. I hate Sharp.
|
|
| Top |
|
|
|
RichardBronosky
|
Posted: Wed May 31, 2006 7:40 pm |
|
|
Joined: Tue Aug 16, 2005 11:50 am
Posts: 181
Location:
Douglasville, GA
|
afrosheen wrote: I feed my Aquos a 720p signal and resize the gui+playback to a much smaller size so it fits on the screen perfectly despite overscan. I still get re-aliased through the Sharp's hardware but there's no way around that on these LCDs unfortunately. I have been doing just this very thing. The unavoidable overscan problem has also been my experience. afrosheen wrote: Tonight I plan to try feeding it a 1080i signal and resizing the gui again
This is exactly what I did today. I used the modeline that I posted above, and changed Setup>Appearance>Screen Settings to 1354,768,5,39,Y,Y,N. Then using the arrows on my TV remote I adjusted the position to where all I could see was the Myth GUI.
I recommend doing "mysqldump --add-drop-table mythconverg settings >backup_of.mythconverg.settings.sql" as root first, in case you choose to rollback.
|
|
| Top |
|
|
|
afrosheen
|
Posted: Wed May 31, 2006 7:56 pm |
|
|
Joined: Sat Mar 26, 2005 3:49 pm
Posts: 290
|
|
I think there's one more thing you can do, but you better be really committed to MythTV. After opening the Aquos service menu, you can go through and tweak the X and Y sizes. I'll let you know if it worked or not and post details later. It's a scary thing but I must kill the overscan or I'll never be happy with this setup.
|
|
| Top |
|
|
View unanswered posts
View active topics
Print view
Previous topic Next topic 
LinHES Home
Board index
FAQ
Search
Login 
Register
