Nvidia, Modelines, Overscan...8.10

[ogbk]

Hello,

Did anyone manage to fix the problem that changing H2/H3 V2/V3 fields doesn't seem to have any effect? I see a couple of people seem to have had a similar problem, but no-one seems to have resolved it yet.

I can get the X config working, but no matter what I change these values to, it still won't move the desktop from the top left corner?

I'm running an asrock 330 (with Nvidia ion) connected to a Samsung le32r41bx TV.

[bbear1]

Sorry to be late to catch up on this thread but for some reason I rarely get the notification emails when someone updates this thread.

I am able to adjust the size and position of the display on my Panasonic 42" plasma, but I was got nowhere with it until I switched from using component cables to DVI/HDMI.

I forget where I read it (nvidia forums probably) but I recall that there was a problem when using component as the timing settings in the xorg.conf get ignored. From what I can remember you just have basic settings available in xorg.conf for NTSC, PAL, etc. I don't know what cable you are using however.

I am now using a DVI to HDMI cables and the nvidia driver respects the settings in my xorg.conf. I don't force the timings in my xorg.conf however, instead it just points to a custom EDID bin file which I created using a Excel spreadsheet which I put together some time ago.

Messing around with the EDID data is tricky (and potentially dangerous), that is what I put together a spreadsheet to help me work out the correct EDID bytes.

[ogbk]

The connection is HDMI>HDMI so it should work really. I'll take a look at the custom eDID thing then as that looks like the best hope.

thanks

[bbear1]

ogbk,
ok, hdmi connection rules out the component problem I mentioned, however it is always possible that the EDID being read from your TV is bad (it happens with some screens apparently)

If you look at your xorg log file does it say that your modeline has been successfully validated?

[Gorthaur]

I know this thread has been here for a long time and I it's been a while since I posted in this thread but if you can download the latest NVIDIA driver, right now I'm using version 190.53, it is possible to adjust overscan compensation going into NVIDIA X server settings. Look for the option Overscan Compensation. Hope it helps somehow.

[wurzel21]

as a noobie was hoping the overscan option in 190.53 driver would be my saviour
But I can not find it any where on the NVIDIA x server settings app.

any ideas please

[Bullwinkle_Moose]

The problem is that only one version of the NVIDIA driver apparently had the overscan compensation slider, and there are reports it doesn't work on some systems. For those still having issues, see http://www.nvnews.net/vbulletin/showthread.php?t=148662

[przemeklach]

I know this thread has been here for a long time and I it's been a while since I posted in this thread but if you can download the latest NVIDIA driver, right now I'm using version 190.53, it is possible to adjust overscan compensation going into NVIDIA X server settings. Look for the option Overscan Compensation. Hope it helps somehow.

Hi,

So yes I confirm that the above mentioned works; however, the setting for adjusting for the overscan disappears when I change my resolution to 1920x1080: the option is only available when I have 720 selected. I don't understand why this happens. Has anyone come across this problem and fixed it?

I'm running an Acer AR1600 hooked up to a Sharp Aquos 42 inch tv using HDMI.

Thanks in advance.

[samuelkarush]

im using this guide in karmic 9.10, its gotten me a almost there, but the custom modeline i created isnt being validated, as shown in xorg.log.
My Xorg.conf file didnt have a monitor section, so I added that. I commented out the options in the device section so i could get back to a usable resolution. heres the xorg file:

Section "Screen"
Identifier "Default Screen"
DefaultDepth 24

SubSection "Display"
Modes "1280x720"
EndSubSection

EndSection

Section "Monitor"
Identifier "SANYO LCD"
Option "ExactModeTimingsDVI" "TRUE"
HorizSync 15-46
VertRefresh 59-61
Modeline "1280x720" 74.25 1280 1390 1430 1650 720 725 730 750 +hsync +vsync
Modeline "720x480" 27.00 720 736 798 858 480 489 495 525 -hsync -vsync
Endsection


Section "Module"
Load "glx"
EndSection

Section "Device"
Identifier "Default Device"
Driver "nvidia"
Option "NoLogo" "True"
##Option "UseEDID" "False"
##Option "ModeValidation" "NoEdidModes"
EndSection



One thing i noticed, which may mean nothing, is that with this xorg.conf file, the xorg.log shows that the display device is a sanyo lcd. If i uncomment the above lines, the display device is just dfp-0.
the modelines are exactly the values i got from running: X -verbose 6 > ~/xlog.txt 2>&1

any ideas why this modeline wouldnt be validated?

ok, i figured out why it wasnt validated, i had to add this to the screen section :
Monitor "SANYO LCD"
this matches the identifier in the monitor section.

ok, so now i can edit the h1 values with multiples of 8, x will start and display, but display looks no different. if i edit v1, i get no display, regardless of multiples i use.


ok, heres where im at. ive tried a ton of xorg options i read about, none have an effect on my use of modeline. i can get a very small change in the h1 value to have an effect, but any changes to v1,2,3 will leave me with a blank screen when i start x. I do however see a difference in where the login information is placed on the screen when i stop x. It is further down the screen than normal.
so i read about creating a custom modeline earlier in this thread. sounds great, but i dont use windows, so i found this:http://sathyasays.com/2008/10/26/how...#comment-39052, which was simple enough to edit the edid.bin i pulled from my tv. I put the file in X11 and put the right options in xorg.conf and pointed it to the new edid. and.... it is ignored. i tried putting it in the device, screen and monitor sections and have tried everything i have seen using google the last couple days, but nvidia-auto-select takes over. i could put a dear john letter in there for all it cares. it seems like i could at least get some kind of error reported? I am using this command every time i start x to see what is going on: sudo X -verbose 6 > ~/xlog1.txt 2>&1
im not done trying, but i have to wonder, is there some characteristic of my tv that is holding me back? I did notice that when i got the new edid.bin file built, when i used parse-edid to read it the hsync and vsync values where out of range of what info i got from the the tv. maybe this is the problem?

[SpiffWilkie]

I am trying to follow instructions as written starting in post 35 but am having issues getting morefunc to behave on my system. Is there anyone that could possible pop my edid data into the spreadsheet and give me the results? This is my edid.bin data as given by Monitor Asset Manager. I am going bonkers trying to get this thing sorted out in Ubuntu on an Acer Revo. The overscan is killing me. Thanks.

Monitor
  Model name............... LC-47SB57UT
  Manufacturer............. Sharp
  Plug and Play ID......... SHP4757
  Serial number............ n/a
  Manufacture date......... 2009, ISO week 0
  -------------------------
  EDID revision............ 1.3
  Input signal type........ Digital
  Color bit depth.......... Undefined
  Display type............. RGB color
  Screen size.............. 1040 x 580 mm (46.9 in)
  Power management......... Not supported
  Extension blocs.......... 1 (CEA-EXT)
  -------------------------
  DDC/CI................... n/a

Color characteristics
  Default color space...... Non-sRGB
  Display gamma............ 2.20
  Red chromaticity......... Rx 0.643 - Ry 0.332
  Green chromaticity....... Gx 0.272 - Gy 0.599
  Blue chromaticity........ Bx 0.152 - By 0.067
  White point (default).... Wx 0.285 - Wy 0.293
  Additional descriptors... None

Timing characteristics
  Horizontal scan range.... 15-76kHz
  Vertical scan range...... 55-71Hz
  Video bandwidth.......... 150MHz
  CVT standard............. Not supported
  GTF standard............. Not supported
  Additional descriptors... None
  Preferred timing......... Yes
  Native/preferred timing.. 1920x1080p at 60Hz (16:9)
    Modeline............... "1920x1080" 148.500 1920 2008 2052 2200 1080 1084 1089 1125 +hsync +vsync
  Detailed timing #1....... 1280x768p at 60Hz (16:9)
    Modeline............... "1280x768" 68.250 1280 1328 1360 1440 768 771 778 790 +hsync -vsync

Standard timings supported
     720 x  400p at  70Hz - IBM VGA
     640 x  480p at  60Hz - IBM VGA
     800 x  600p at  60Hz - VESA
    1024 x  768p at  60Hz - VESA
    1280 x  720p at  60Hz - VESA STD
    1280 x 1024p at  60Hz - VESA STD
    1440 x  900p at  60Hz - VESA STD
    1680 x 1050p at  60Hz - VESA STD

EIA/CEA-861 Information
  Revision number.......... 3
  DTV underscan............ Not supported
  Basic audio.............. Supported
  YCbCr 4:4:4.............. Supported
  YCbCr 4:2:2.............. Supported
  Native formats........... 1
  Detailed timing #1....... 1280x720p at 60Hz (16:9)
    Modeline............... "1280x720" 74.250 1280 1390 1430 1650 720 725 730 750 +hsync +vsync
  Detailed timing #2....... 720x480p at 60Hz (16:9)
    Modeline............... "720x480" 27.000 720 736 798 858 480 489 495 525 -hsync -vsync
  Detailed timing #3....... 1920x1080i at 60Hz (16:9)
    Modeline............... "1920x1080" 74.250 1920 2008 2052 2200 1080 1084 1094 1124 interlace +hsync +vsync
  Detailed timing #4....... 1440x480i at 60Hz (16:9)
    Modeline............... "1440x480" 27.000 1440 1478 1602 1716 480 488 494 524 interlace -hsync -vsync

CE video data (timings supported)
    1920 x 1080i at  60Hz - HDTV (16:9, 1:1)
    1280 x  720p at  60Hz - HDTV (16:9, 1:1)
     720 x  480p at  60Hz - EDTV (16:9, 32:27)
     720 x  480p at  60Hz - EDTV (4:3, 8:9)
     640 x  480p at  60Hz - Default (4:3, 1:1)
    1920 x 1080p at  60Hz - HDTV (16:9, 1:1) [Native]
     720 x  480i at  60Hz - Doublescan (16:9, 32:27)
     720 x  480i at  60Hz - Doublescan (4:3, 8:9)
    1920 x 1080p at  24Hz - HDTV (16:9, 1:1)
    NB: NTSC refresh rate = (Hz*1000)/1001

CE audio data (formats supported)
  LPCM    2-channel, 16/20/24 bit depths at 32/44/48 kHz

CE vendor specific data (VSDB)
  IEEE registration number. 0x000C03
  CEC physical address..... 0.3.0.0
  Supports AI (ACP, ISRC).. Yes
  Supports 48bpp........... No
  Supports 36bpp........... Yes
  Supports 30bpp........... Yes
  Supports YCbCr 4:4:4..... No
  Supports dual-link DVI... No
  Maximum TMDS clock....... 150MHz

Report information
  Date generated........... 4/28/2010
  Software revision........ 2.50.0.849
  Operating system......... 5.1.2600.2.Service Pack 2

Raw data
  00,FF,FF,FF,FF,FF,FF,00,4D,10,57,47,01,01,01,01,00,13,01,03,80,68,3A,78,0A,8D,10,A4,55,45,99,27,
  11,49,4B,A1,08,00,81,C0,81,80,95,00,B3,00,01,01,01,01,01,01,01,01,02,3A,80,18,71,38,2D,40,58,2C,
  45,00,0F,48,42,00,00,1E,A9,1A,00,A0,50,00,16,30,30,20,37,00,0F,48,42,00,00,1A,00,00,00,FC,00,4C,
  43,2D,34,37,53,42,35,37,55,54,0A,20,00,00,00,FD,00,37,47,0F,4C,0F,00,0A,20,20,20,20,20,20,01,8D,
  02,03,21,71,49,05,04,03,02,01,90,07,06,20,23,09,07,07,67,03,0C,00,30,00,B0,1E,E3,05,03,01,E2,00,
  0F,01,1D,00,72,51,D0,1E,20,6E,28,55,00,0F,48,42,00,00,1E,8C,0A,D0,8A,20,E0,2D,10,10,3E,96,00,0F,
  48,42,00,00,18,01,1D,80,18,71,1C,16,20,58,2C,25,00,0F,48,42,00,00,9E,8C,0A,A0,14,51,F0,16,00,26,
  7C,43,00,0F,48,42,00,00,98,00,00,00,00,00,00,00,00,00,00,00,00,00,00,00,00,00,00,00,00,00,00,66