Announcement

Collapse
No announcement yet.

DVI to HDMI Nvidia Overscan

Collapse
X
  • Filter
  • Time
  • Show
Clear All
new posts

  • DVI to HDMI Nvidia Overscan

    Running (2) GTX260 cards via DVI to HDMI Cable to 42 inch LCD TV 1080P. Desktop stretched and to big. I hear this is overscan. Fixed this in windows but need help in linux please. Using Fedora 11...

  • #2
    Wow NO Replies? How long have Nvidia Drivers for linux been out? A week? What about HDTVs?
    This is a joke right? I thought Nvidia had better drivers than ATI in Linux that is why I sold my 4870X2 which had nothing wrong with it except poor linux support and bought TWO XFX Black Edition GTX260's.
    Sheesh... Sad

    Comment


    • #3
      This should be the easiest fix ever as the driver should have built in scaling dont you think???

      Comment


      • #4
        LOL was doing a search to see if ANYONE in the world has figured this out and it took m here...

        Comment


        • #5
          Originally posted by ap90033 View Post
          LOL was doing a search to see if ANYONE in the world has figured this out and it took m here...
          Follow the instructions found here. They are written for Ubuntu, but the procedure for Fedora should be very similar:
          http://ubuntuforums.org/showthread.php?t=1003099&page=2

          Comment


          • #6
            Originally posted by ap90033 View Post
            I thought Nvidia had better drivers than ATI in Linux that is why I sold my 4870X2 which had nothing wrong with it except poor linux support and bought TWO XFX Black Edition GTX260's.
            Sheesh... Sad
            Wow. Thats a pretty dumb thing to do.
            AMD linux drivers are open source (including 3D) for all up to R700 (latest hardware) and they also have closed source drivers (equivalent to nvidia blob drivers) for R600 and R700. The open source R600/R700 is recent and advancing in leaps and bounds. That makes AMD linux support FAR FAR better than that nvidia junk.

            Comment


            • #7
              Originally posted by lbcoder View Post
              Wow. Thats a pretty dumb thing to do.
              AMD linux drivers are open source (including 3D) for all up to R700 (latest hardware) and they also have closed source drivers (equivalent to nvidia blob drivers) for R600 and R700. The open source R600/R700 is recent and advancing in leaps and bounds. That makes AMD linux support FAR FAR better than that nvidia junk.
              So you blame nvidia for not fixing your broken EDID on your TV? Sorry but no driver can fix that. When your correcting overscan in the windows drivers your adjusting modelines as well. You have the same capability in linux which is handled by xorg.conf. Place blame where blame is due.
              Last edited by deanjo; 08-31-2009, 04:37 PM.

              Comment


              • #8
                Originally posted by deanjo View Post
                So you blame nvidia for not fixing your broken EDID on your TV? Sorry but no driver can fix that. When your correcting overscan in the windows drivers your adjusting modelines as well. You have the same capability in linux which is handled by xorg.conf. Place blame where blame is due.
                Who are you referring to that is blaming Nvidia for 'broken' EDID on the TV? I did not see anybody make that statement. The OP asked for help correcting the overscan, which was easy in Windows, and not obvious to a novice Linux user. he may have been a little overzealous in following up his original post a few times, but I imagine he was really frustrated. I've been there too. Correcting modelines manually is not intuitive until after you have done it a few times (if then). Adding the same gui functionality to help generate the correct modelines in Linux as they provide in windows is really not too much to ask, IMO. Is the EDID broken? I think that is debatable. There are a LOT of TVs manufactured for the consumer space that don't allow the user to turn off the overscan. For every application, except as a PC monitor, this is fine. Just about every TV show, DVD movie and video game system is framed with an overscanned screen in mind. And, since those TVs are not marketed as computer monitors the EDID information could be considered perfectly accurate. Would I like to be able to turn off the overscan? Of course I would. But the point is that Nvidia decided it was worthwhile to add the overscan adjustment in their Windows driver gui. So why no in their Linux driver gui? Same thing goes for AMD/ATI.

                Comment


                • #9
                  Originally posted by gsacks View Post
                  Who are you referring to that is blaming Nvidia for 'broken' EDID on the TV? I did not see anybody make that statement. The OP asked for help correcting the overscan, which was easy in Windows, and not obvious to a novice Linux user. he may have been a little overzealous in following up his original post a few times, but I imagine he was really frustrated. I've been there too. Correcting modelines manually is not intuitive until after you have done it a few times (if then). Adding the same gui functionality to help generate the correct modelines in Linux as they provide in windows is really not too much to ask, IMO. Is the EDID broken? I think that is debatable. There are a LOT of TVs manufactured for the consumer space that don't allow the user to turn off the overscan. For every application, except as a PC monitor, this is fine. Just about every TV show, DVD movie and video game system is framed with an overscanned screen in mind. And, since those TVs are not marketed as computer monitors the EDID information could be considered perfectly accurate. Would I like to be able to turn off the overscan? Of course I would. But the point is that Nvidia decided it was worthwhile to add the overscan adjustment in their Windows driver gui. So why no in their Linux driver gui? Same thing goes for AMD/ATI.
                  Actually a gui for modelines would fall in the X devs domain. Modeline is a Xorg configuration option and is not vender specific.

                  Comment


                  • #10
                    Originally posted by deanjo View Post
                    Actually a gui for modelines would fall in the X devs domain. Modeline is a Xorg configuration option and is not vender specific.
                    By that logic, Microsoft would be responsible for providing the overscan adjustment tool for Windows, but in fact both Nvidia and AMD/ATI provide it instead.

                    Besides, even if I accepted you logic, it would only hold true if the Nvidia driver was open source. But the Nvidia binary drivers are incompatible with the X display settings gui. (At least the one supplied with Ubuntu 9.04), and forces you to use the Nvidia supplied X settings program instead. So I would say that Nvidia has clearly occupied that territory and has made the settings very vendor specific at least as far as a front end is concerned.

                    Mind you, I am very happy with the Nvidia driver performance, and extremely happy with VDPAU. That is why I switched from AMD/ATI to Nvidia in the first place. I just do not understand why you would take a position that leaving out a useful feature is defensible for any reason other than that it is a simple oversight, or that they have just not gotten around to it yet.

                    Comment


                    • #11
                      Originally posted by gsacks View Post
                      By that logic, Microsoft would be responsible for providing the overscan adjustment tool for Windows, but in fact both Nvidia and AMD/ATI provide it instead.
                      Adjustment isn't needed in windows when the EDID isn't broken. Window also allows you to use the driver disk that has the scanline info.

                      Besides, even if I accepted you logic, it would only hold true if the Nvidia driver was open source. But the Nvidia binary drivers are incompatible with the X display settings gui. (At least the one supplied with Ubuntu 9.04), and forces you to use the Nvidia supplied X settings program instead. So I would say that Nvidia has clearly occupied that territory and has made the settings very vendor specific at least as far as a front end is concerned.
                      Find a better distro with better setup apps. SaX2 for openSUSE for example generates the xorg just fine for nvidia cards. See:

                      Code:
                      # /.../
                      # SaX generated X11 config file
                      # Created on: 2009-05-02T20:03:14-0600.
                      #
                      # Version: 8.1
                      # Contact: Marcus Schaefer <sax@suse.de>, 2005
                      # Contact: SaX-User list <https://lists.berlios.de/mailman/listinfo/sax-users>
                      #
                      # Automatically generated by [ISaX] (8.1)
                      # PLEASE DO NOT EDIT THIS FILE!
                      #
                      
                      Section "Files"
                        FontPath     "/usr/share/fonts/misc:unscaled"
                        FontPath     "/usr/share/fonts/local"
                        FontPath     "/usr/share/fonts/75dpi:unscaled"
                        FontPath     "/usr/share/fonts/100dpi:unscaled"
                        FontPath     "/usr/share/fonts/Type1"
                        FontPath     "/usr/share/fonts/URW"
                        FontPath     "/usr/share/fonts/Speedo"
                        FontPath     "/usr/share/fonts/PEX"
                        FontPath     "/usr/share/fonts/cyrillic"
                        FontPath     "/usr/share/fonts/latin2/misc:unscaled"
                        FontPath     "/usr/share/fonts/latin2/75dpi:unscaled"
                        FontPath     "/usr/share/fonts/latin2/100dpi:unscaled"
                        FontPath     "/usr/share/fonts/latin2/Type1"
                        FontPath     "/usr/share/fonts/latin7/75dpi:unscaled"
                        FontPath     "/usr/share/fonts/baekmuk:unscaled"
                        FontPath     "/usr/share/fonts/japanese:unscaled"
                        FontPath     "/usr/share/fonts/kwintv"
                        FontPath     "/usr/share/fonts/truetype"
                        FontPath     "/usr/share/fonts/uni:unscaled"
                        FontPath     "/usr/share/fonts/CID"
                        FontPath     "/usr/share/fonts/ucs/misc:unscaled"
                        FontPath     "/usr/share/fonts/ucs/75dpi:unscaled"
                        FontPath     "/usr/share/fonts/ucs/100dpi:unscaled"
                        FontPath     "/usr/share/fonts/hellas/misc:unscaled"
                        FontPath     "/usr/share/fonts/hellas/75dpi:unscaled"
                        FontPath     "/usr/share/fonts/hellas/100dpi:unscaled"
                        FontPath     "/usr/share/fonts/hellas/Type1"
                        FontPath     "/usr/share/fonts/misc/sgi:unscaled"
                        FontPath     "/usr/share/fonts/xtest"
                        FontPath     "/opt/kde3/share/fonts"
                        InputDevices "/dev/gpmdata"
                        InputDevices "/dev/input/mice"
                      EndSection
                      
                      Section "ServerFlags"
                        Option       "AllowMouseOpenFail" "on"
                        Option       "ZapWarning" "on"
                      EndSection
                      
                      Section "Module"
                        Load         "dri"
                        Load         "dbe"
                        Load         "freetype"
                        Load         "extmod"
                        Load         "glx"
                      EndSection
                      
                      Section "InputDevice"
                        Driver       "kbd"
                        Identifier   "Keyboard[0]"
                        Option       "Protocol" "Standard"
                        Option       "XkbLayout" "us"
                        Option       "XkbModel" "logitech_g15"
                        Option       "XkbRules" "xfree86"
                      EndSection
                      
                      
                      Section "InputDevice"
                          Identifier     "Mouse[1]"
                          Driver         "mouse"
                          Option         "Buttons" "5"
                          Option         "Device" "/dev/input/mice"
                          Option         "Name" "ImPS/2 Generic Wheel Mouse"
                          Option         "Protocol" "explorerps/2"
                          Option         "Vendor" "Sysp"
                          Option         "ZAxisMapping" "4 5"
                      EndSection
                      
                      
                      Section "Monitor"
                        Option       "CalcAlgorithm" "XServerPool"
                        DisplaySize  517 323
                        HorizSync    30-81
                        Identifier   "Monitor[0]"
                        ModelName    "SYNCMASTER T260 SYNCMASTER MAGIC T260(DIGITAL)"
                        Option       "PreferredMode" "1920x1200"
                        VendorName   "SAMSUNG"
                        VertRefresh  56-75
                        UseModes     "Modes[0]"
                      EndSection
                      
                      
                      Section "Modes"
                        Identifier   "Modes[0]"
                      EndSection
                      
                      
                      Section "Screen"
                        DefaultDepth 24
                        SubSection "Display"
                          Depth      15
                          Modes      "1920x1200" "1900x1200" "1920x1080" "1600x1200" "1680x1050" "1600x1024" "1600x1000" "1400x1050" "1600x900" "1280x1024" "1440x900" "1280x960" "1366x768" "1360x768" "1280x800" "1152x864" "1280x768" "1280x720" "1024x768" "1280x600" "1024x600" "800x600" "768x576" "640x480" 
                        EndSubSection
                        SubSection "Display"
                          Depth      16
                          Modes      "1920x1200" "1900x1200" "1920x1080" "1600x1200" "1680x1050" "1600x1024" "1600x1000" "1400x1050" "1600x900" "1280x1024" "1440x900" "1280x960" "1366x768" "1360x768" "1280x800" "1152x864" "1280x768" "1280x720" "1024x768" "1280x600" "1024x600" "800x600" "768x576" "640x480" 
                        EndSubSection
                        SubSection "Display"
                          Depth      24
                          Modes      "1920x1200" "1900x1200" "1920x1080" "1600x1200" "1680x1050" "1600x1024" "1600x1000" "1400x1050" "1600x900" "1280x1024" "1440x900" "1280x960" "1366x768" "1360x768" "1280x800" "1152x864" "1280x768" "1280x720" "1024x768" "1280x600" "1024x600" "800x600" "768x576" "640x480" 
                        EndSubSection
                        SubSection "Display"
                          Depth      8
                          Modes      "1920x1200" "1900x1200" "1920x1080" "1600x1200" "1680x1050" "1600x1024" "1600x1000" "1400x1050" "1600x900" "1280x1024" "1440x900" "1280x960" "1366x768" "1360x768" "1280x800" "1152x864" "1280x768" "1280x720" "1024x768" "1280x600" "1024x600" "800x600" "768x576" "640x480" 
                        EndSubSection
                        Device       "Device[0]"
                        Identifier   "Screen[0]"
                        Monitor      "Monitor[0]"
                      EndSection
                      
                      
                      Section "Device"
                        BusID "04:00:00"
                        BoardName    "GeForce GTX 275"
                        Driver       "nvidia"
                        Identifier   "Device[0]"
                        Option       "RenderAccel"
                        Option       "HWcursor"
                        Option         "NvAGP" "0"
                       VendorName   "NVIDIA Corporation"
                      EndSection
                      
                      Section "Device"
                          Identifier     "8800GT 512"
                          Driver         "nvidia"
                          VendorName     "NVIDIA Corporation"
                          BusID          "5:0:0"
                      EndSection
                      
                      
                      Section "ServerLayout"
                        Identifier   "Layout[all]"
                        InputDevice  "Keyboard[0]" "CoreKeyboard"
                        InputDevice  "Mouse[1]" "CorePointer"
                        Option       "Clone" "off"
                        Option       "Xinerama" "off"
                        Screen       "Screen[0]"
                      EndSection
                      
                      
                      Section "DRI"
                          Group      "video"
                          Mode       0660
                      EndSection
                      
                      Section "Extensions"
                        Option "Composite" "on"
                      EndSection
                      None of that was generated with nvidia settings.

                      Mind you, I am very happy with the Nvidia driver performance, and extremely happy with VDPAU. That is why I switched from AMD/ATI to Nvidia in the first place. I just do not understand why you would take a position that leaving out a useful feature is defensible for any reason other than that it is a simple oversight, or that they have just not gotten around to it yet.
                      It's not that it's a oversite, it's that there are tools out there that already do these tasks. SaX2 for example can use the windows .inf file for inputing the correct mode lines, adjust the screen size and position, enable dual head, etc etc. If it's really anyone's over sight it is your distribution that fails at supplying you with the tools to do so.
                      Last edited by deanjo; 09-01-2009, 01:02 AM.

                      Comment


                      • #12
                        Originally posted by deanjo View Post
                        Adjustment isn't needed in windows when the EDID isn't broken. Window also allows you to use the driver disk that has the scanline info.

                        Find a better distro with better setup apps. SaX2 for openSUSE for example generates the xorg just fine for nvidia cards. See:

                        It's not that it's a oversite, it's that there are tools out there that already do these tasks. SaX2 for example can use the windows .inf file for inputing the correct mode lines, adjust the screen size and position, enable dual head, etc etc. If it's really anyone's over sight it is your distribution that fails at supplying you with the tools to do so.
                        Now you are coming across as arrogant. Whether or not that is intended I really can not tell. Nothing in your xorg.conf is making an adjustment for overscan, so you don't seem to have a system that suffers from this issue. A quick google search for 'suse nvidia overscan' will reveal to you that there are in fact people using your favorite distro that also have had trouble figuring this out. I have fixed this problem on my Ubuntu system, so I've got no problem continuing to use said distro. Statements like 'use a better distro', and your earlier statement (paraphrased) 'get a TV that isn't broken' make it clear to me that continuing this discourse is a waste of time. Have a nice day.

                        Comment


                        • #13
                          Originally posted by gsacks View Post
                          Now you are coming across as arrogant. Whether or not that is intended I really can not tell. Nothing in your xorg.conf is making an adjustment for overscan, so you don't seem to have a system that suffers from this issue. A quick google search for 'suse nvidia overscan' will reveal to you that there are in fact people using your favorite distro that also have had trouble figuring this out. I have fixed this problem on my Ubuntu system, so I've got no problem continuing to use said distro. Statements like 'use a better distro', and your earlier statement (paraphrased) 'get a TV that isn't broken' make it clear to me that continuing this discourse is a waste of time. Have a nice day.
                          The same monitor has a broken EDID when using the HDMI interface. Same situation as yours. On the other system ignore EDID is enabled and that was all done via SaX2. So yes I do suffer the exact same issue. The posted Xorg was to prove to you that "forces you to use the Nvidia supplied X settings program instead" is pure bullshit. BTW every feature in the nvidia drivers can be enabled / disabled / or set value too. People post all the time as well no matter what os / card / driver / etc as some people especially n00bs find it easier to ask then to look on their own despite the answer being often right under their nose.

                          BTW: Will gladly post screen shots of SaX if you wish after I get back from work today. Also why do you think XBMC can handle overscan issues through their app and how can it do this? Oh ya, because they wrote in the capability of doing this.
                          Last edited by deanjo; 09-01-2009, 08:44 AM.

                          Comment


                          • #14
                            Originally posted by deanjo View Post
                            So you blame nvidia for not fixing your broken EDID on your TV? Sorry but no driver can fix that. When your correcting overscan in the windows drivers your adjusting modelines as well. You have the same capability in linux which is handled by xorg.conf. Place blame where blame is due.
                            Are you on crack or something? Who said I had any problems with overscan. I don't even own any nvidia garbage any more.

                            Comment


                            • #15
                              Originally posted by deanjo View Post
                              BTW: Will gladly post screen shots of SaX if you wish after I get back from work today. Also why do you think XBMC can handle overscan issues through their app and how can it do this? Oh ya, because they wrote in the capability of doing this.
                              Ok, I really wanted to end this, but the voice inside my head is screaming to get out. XBMC doesn't change anything in the modelines in xorg.conf, or change the resolution on the screen at all. It just scales itself to use the smaller portion of the screen. It can not, for instance, deal with the opposite problem of having a black border around the outer edge due to underscan. In either case, I think we should just agree to disagree at this point. I believe that hardware manufacturers providing a binary driver and software application to control that driver should strive for feature parity between platforms, and currently the gpu vendors are not doing that. You don't seem to agree. All the other arguments on both sides aren't going to change either one of our minds. I've got nothing against Suse, but I am happy with Ubuntu and don't see a need to change. I'm not about to get into a distro argument. Maybe I'll check out Suse again on a spare system someday. I'm sure I've have it installed at some time in the past. I just can't remember. I don't consider myself a nOOb by any stretch, but neither am I a guru. I fall somewhere in between. I first used Linux nearly 16 years ago but never used it as a primary OS until about 2 years ago when I built my first HTPC. I don't really enjoy screwing around with my system that much. I enjoy using it.

                              Comment

                              Working...
                              X