Tagged: xorg Toggle Comment Threads | Keyboard Shortcuts

  • BrainwreckedTech 12:06 am on August 19, 2012 Permalink | Reply
    Tags: , , , , , , xorg   

    HOWTO: Get NVIDIA On Linux To Use Custom Resolutions Over DVI 

    NVIDIA LogoLinux Logo Half

    You want something easy? Cut the EDID pin on a VGA cable, hook up your monitor, configure xorg.conf to whateve resolution you want, and call it a day.

    You want something scary? Do the same with a DVI or HDMI cable and witness the NVIDIA driver do everything in its power keep you from falling down and skinning your knees like you’re 2 years old.

    The problem stems from the fact that digital flat panels have one native resolution. Well, actually, this would be a problem if these monitors didn’t have internal scalers. So now the problem becomes: What device scales better — your NVIDIA GPU or your flat panel? Chances are most people wouldn’t be able to tell. Some might be annoyed that their flat panel just steches everything without regard to aspect ratio.

    But what if you actually want to run at a “non-native” resolution because you’re using an HDTV whose actual native resolution is 1368×768, whose actual native resolution is never reported at all, but reports the max 1920×1080 as it’s native resolution?

    Here’s the slew of options you need:

    Option “UseEDID” “False”
    Tells the driver not to use modes that the display device reports it can use
    Option “UseEDIDFreqs” “False”
    Tells the driver to ignore frequency ranges reported over EDID.
    Option “ExactModeTimingsDVI” “True”
    IMPORTANT! Tells the driver to use timings as-is. Otherwise, it tries to find a best-fit resolution instead. If you leave EDID enabled while connected to an HDTV, you’ll get a 1368×768 resolution scaled to 1920×1080 resolution. If you disable EDID modes, the driver will fall back to 640×480 and then reject your custom resolution as being too large.
    ModeValidation NoDFPNativeResolutionCheck
    Tells the drive not to check resolutions agains the reported native resolution. This comes into play when UseEDID is false since the driver will fall back on 640×480 and then reject your custom resolution as too large.
    ModeValidation other
    Nothing special to note here as these would be used even if you were using a VGA connection.
    Section "Device"
    	Identifier	"DVI0"
    	Option		"UseDisplayDevice"	"DFP-0"
    	Driver		"nvidia"
    	Option		"UseEDID"		"False"
    	Option		"UseEDIDFreqs"		"False"
    	Option		"ExactModeTimingsDVI"	"True"
    	Option		"ModeValidation"	"NoDFPNativeResolutionCheck, NoEdidModes, NoMaxPClkCheck, NoVertRefreshCheck, NoHorizSyncCheck, NoEdidMaxPClkCheck"
    	Option		"NoLogo"		"True"
    	Option		"DPI"			"144 x 144"
    • Tim 9:27 pm on September 17, 2013 Permalink | Reply

      Thanks! Just what I needed.

    • Paul M 12:59 pm on March 22, 2014 Permalink | Reply

      I don’t understand how 1366×768 is set as the resolution?

      • BrainwreckedTech 9:09 am on July 25, 2014 Permalink | Reply

        This article only shows settings you need to use a specific resolution that many will overlook since HDTVs are a relatively new thing. It assumes you already know how to set the resolution but your efforts aren’t working as expected.

    • Jason 2:00 pm on April 1, 2015 Permalink | Reply

      I have a 42″ Samsung that my computer is plugged into. The desktop stretches past the screen.
      In windows I fixed this with nvidia settings. I’m getting closer.

      I fix over scan with the xserver settings in linux. I set it to 41, screen fits perfect. But now all of a sudden the desktop will scroll over to the edge when the mouse gets to close and also to the bottom. It looks like the top of my background is wrapping around the screen. (cutting the top off and then visible at the bottom. also on the right side)

      What can I do to get my desktop to stay in one place!!!!!!?

      also when I launch kodi/xbmc it stretches past the edge.
      The most resent thing i have installed is Florence keyboard. But I dont see how that would affect it.

      Thank you

  • BrainwreckedTech 2:38 pm on May 15, 2012 Permalink | Reply
    Tags: consolekit, display manager, , slim, , xorg   

    Some Display Managers No Longer Require ck-launch-session 

    Linux Logo Did ConsoleKit shutdown, reboot, suspend, and hibernate recently stop working for you? Unable to mount volumes that you were able to before? Chances are you’re probably using an alternative display manager (as opposed to KDM and GDM) and had to specify ck-launch-session to get things working correctly. Some display managers that have opted out of direct ConsoleKit support (usually in the name of being lightweight and/or simple) have started including direct support (my case: SLiM).

    Just remove ck-launch-session from whichever line from whatever configuration file your display manager uses to begin launching an X session.  In the case of SLiM, this is the login_cmd line in /etc/slim.conf.

Compose new post
Next post/Next comment
Previous post/Previous comment
Show/Hide comments
Go to top
Go to login
Show/Hide help
shift + esc