Where to find xorg.conf in ubuntu

If the last few pixels on a scan line appear on the left of the screen, this value should be decreased. VScan vscan specifies the number of times each scanline is painted on the screen. Values less than 1 are treated as 1, which is the default.

Generally, the "DoubleScan" Flag mentioned above doubles this value. ModeLine " name " mode-description This entry is a more compact version of the Mode entry, and it also can be used to specify video modes for the monitor. This is a single line format for specifying video modes. In most cases this isn't necessary because the built-in set of VESA standard modes will be sufficient. The mode-description is in four sections, the first three of which are mandatory.

The first is the dot pixel clock. This is a single number specifying the pixel clock rate for the mode in MHz. The second section is a list of four numbers specifying the horizontal timings.

These numbers are the hdisp , hsyncstart , hsyncend , and htotal values. The third section is a list of four numbers specifying the vertical timings. These numbers are the vdisp , vsyncstart , vsyncend , and vtotal values.

The final section is a list of flags specifying other characteristics of the mode. Interlace indicates that the mode is interlaced. DoubleScan indicates a mode where each scanline is doubled. Composite can be used to specify composite sync on hardware where this is supported. The default is to enable the extension. Option "SyncOnGreen" " bool " This option controls whether the video card should drive the sync signal on the green color pin.

Not all cards support this option, and most monitors do not require it. The default is off. Option "Primary" " bool " This optional entry specifies that the monitor should be treated as the primary monitor. RandR 1. All these keypad available modes are selected from the screen mode list. This list is a copy of the compatibility output monitor mode list. Since this output is the output connected to the lowest dot-area monitor, as determined from its largest size mode, that monitor defines the available zoom modes.

By default, the server will attempt to enable all connected monitors. By default, the server will add default modes; you should only disable this if you can guarantee that EDID will be available at all times, or if you have added custom modelines which the server can use. Option "MaxClock" " frequency " This optional entry specifies the maximum dot clock, in kHz, that is supported by the monitor.

Option "Ignore" " bool " This optional entry specifies that the monitor should be ignored entirely, and not reported through RandR. This is useful if the hardware reports the presence of outputs that don't exist. Valid values for rotation are "normal", "left", "right", and "inverted". These sections provide a way of defining sets of video modes independently of the Monitor sections.

Monitor sections may include the definitions provided in these sections by using the UseModes keyword. In most cases the Modes sections are not necessary because the built-in set of VESA standard modes will be sufficient. Modes sections have the following format: Section "Modes" Identifier " name " entries EndSection The Identifier entry specifies the unique name for this set of mode descriptions.

The other entries permitted in Modes sections are the Mode and ModeLine entries that are described above in the Monitor section. If neither of those is present, the first Screen section found in the config file is considered the active one. SubSection "Display" entries EndSection The Identifier entry is mandatory. All others are optional. The Identifier entry specifies the unique name for this screen. The Screen section provides information specific to the whole screen, including screen-specific Options.

In multi-head configurations, there will be multiple active Screen sections, one for each head. The entries available for this section are: Device " device-id " This entry specifies the Device section to be used for this screen.

When multiple graphics cards are present, this is what ties a specific card to a screen. The device-id must match the Identifier of a Device section in the config file. When multiple graphics cards are present, this is what ties a specific secondary card to a screen. This can be specified up to 4 times for a single screen. Monitor " monitor-id " specifies which monitor description is to be used for this screen.

If a Monitor name is not specified, a default configuration is used. Currently the default configuration may not function as expected on all platforms. VideoAdaptor " xv-id " specifies an optional Xv video adaptor description to be used with this screen.

DefaultDepth depth specifies which color depth the server should use by default. The -depth command line option can be used to override this. If neither is specified, the default depth is driver-specific, but in most cases is 8. DefaultFbBpp bpp specifies which framebuffer layout to use by default. The -fbbpp command line option can be used to override this. In most cases the driver will chose the best default value for this. The only case where there is even a choice in this value is for depth 24, where some hardware supports both a packed 24 bit framebuffer layout and a sparse 32 bit framebuffer layout.

MatchSeat seat-id Only apply this Screen section if X server was started with -seat seat-id option. Options Various Option flags may be specified in the Screen section. Some are driver-specific and are described in the driver documentation. Others are driver-independent, and will eventually be described here. Option "Accel" Enables 2D hardware acceleration. This option is on by default, but it may be necessary to turn it off if there are bugs in the driver.

There are many options to disable specific accelerated operations, listed below. Note that disabling an operation will have no effect if the operation is not accelerated whether due to lack of support in the hardware or in the driver. This may be used to select an alternate implementation for development, debugging, or alternate feature sets. Default: mesa. Option "InitPrimary" " boolean " Use the Int10 module to initialize the primary graphics card.

Normally, only secondary cards are soft-booted using the Int10 module, as the primary card has already been initialized by the BIOS at boot time. Each Screen section may optionally contain one or more Display subsections.

The Display subsection format is described in the section below. The Display subsections are optional. Display subsections have the following format: SubSection "Display" Depth depth entries EndSubSection Depth depth This entry specifies what colour depth the Display subsection is to be used for.

This entry is usually specified, but it may be omitted to create a match-all Display subsection or when wishing to match only against the FbBpp parameter. The range of depth values that are allowed depends on the driver. Most drivers support 8, 15, 16 and Note: depth means the number of bits in a pixel that are actually used to determine the pixel colour.

Most hardware that uses 32 bits per pixel only uses 24 of them to hold the colour information, which means that the colour depth is 24, not FbBpp bpp This entry specifies the framebuffer format this Display subsection is to be used for. This entry is only needed when providing depth 24 configurations that allow a choice between a 24 bpp packed framebuffer format and a 32bpp sparse framebuffer format. In most cases this entry should not be used. Weight red-weight green-weight blue-weight This optional entry specifies the relative RGB weighting to be used for a screen is being used at depth 16 for drivers that allow multiple formats.

This may also be specified from the command line with the -weight option see Xorg 1. Virtual xdim ydim This optional entry specifies the virtual screen resolution to be used. The given value will be rounded down if this is not the case. Video modes which are too large for the specified virtual size will be rejected. If this entry is not present, the virtual screen resolution will be set to accommodate all the valid video modes given in the Modes entry.

Refer to the appropriate driver-specific documentation for details. ViewPort x0 y0 This optional entry sets the upper left corner of the initial display. This is only relevant when the virtual screen resolution is different from the resolution of the initial video mode. If this entry is not given, then the initial display will be centered in the virtual display area. Modes " mode-name " This optional entry specifies the list of video modes to use. Each mode-name specified must be in double quotes.

They must correspond to those specified or referenced in the appropriate Monitor section including implicitly referenced built-in VESA standard modes. The server will delete modes from this list which don't satisfy various requirements. The first valid mode in this list will be the default display mode for startup. The list of valid modes is converted internally into a circular list. When this entry is omitted, the valid modes referenced by the appropriate Monitor section will be used.

If the Monitor section contains no modes, then the selection will be taken from the built-in VESA standard modes. Visual " visual-name " This optional entry sets the default root visual type. This may also be specified from the command line see the Xserver 1 man page. This is only supported at depth 1. The default is black. The default is white. Options Option flags may be specified in the Display subsections.

These may include driver-specific options and driver-independent options. Some of the latter are described above in the section about the Screen section, and they may also be included here. In multi-head configurations, it also specifies the relative layout of the heads. If those options are not used, the first ServerLayout section found in the config file is considered the active one.

If no ServerLayout sections are present, the single active screen and two active core input devices are selected as described in the relevant sections above. InputDevice " idev-id " The Identifier entry specifies the unique name for this server layout. The ServerLayout section provides information specific to the whole session, including session-specific Options.

The ServerFlags options described above may be specified here, and ones given here override those given in the ServerFlags section. The entries that may be used in this section are described here. Screen screen-num "screen-id" position-information One of these entries must be given for each screen being used in a session. The screen-id field is mandatory, and specifies the Screen section being referenced. The screen-num field is optional, and may be used to specify the screen number in multi-head configurations.

When this field is omitted, the screens will be numbered in the order that they are listed in. The numbering starts from 0, and must be consecutive. The position-information field describes the way multiple screens are positioned. There are a number of different ways that this information can be provided: x y Absolute x y These both specify that the upper left corner's coordinates are x , y. The Absolute keyword is optional. Some older versions of XFree86 4. RightOf " screen-id " LeftOf " screen-id " Above " screen-id " Below " screen-id " Relative " screen-id " x y These give the screen's location relative to another screen.

The first four position the screen immediately to the right, left, above or below the other screen. When positioning to the right or left, the top edges are aligned. When positioning above or below, the left edges are aligned.

The Relative form specifies the offset of the screen's origin upper left corner relative to the origin of another screen. InputDevice " idev-id " " option " One of these entries should be given for each input device being used in a session.

Normally at least two are required, one each for the core pointer and keyboard devices. The idev-id field is mandatory, and specifies the name of the InputDevice section being referenced. Multiple option fields may be specified, each in double quotes. The options permitted here are any that may also be given in the InputDevice sections. Normally only session-specific input device options would be used here. The most commonly used options are: "CorePointer" "CoreKeyboard" "SendCoreEvents" and the first two should normally be used to indicate the core pointer and core keyboard devices respectively.

MatchSeat seat-id Only apply this ServerLayout section if X server was started with -seat seat-id option. Options In addition to the following, any option permitted in the ServerFlags section may also be specified here.

When the same option appears in both places, the value given here overrides the one given in the ServerFlags section. Option "IsolateDevice" " bus-id " Restrict device resets to the specified bus-id.

Probably the previous time I generated it I didn't specify the 60 Hz in the nvidia-settings tool and that value was not saved. For now it's working. From there you would be able to use the nvidia settings panel to save to an xorg.

Make sure you backup the file that you have working now, so that if you make a mistake and your interface isn't working any more you can replace the bad file with the good one.

Again, you need root permissions which you can activate by using sudo, you can do sudo mv xorg. Where can I find the configuration files I need to edit? Check the current manual. If you create a xorg. Also check this answer. There are some files in this directory already. You can find more information on xorg.

What is important is that the filenames should start with a two-digit number greater than Another guide - in english - is on x org archive. It did finally error-out, but not before providing a nice new xorg. Thanks cc!

All the other suggestions I had tried failed to produce a file. Yeah for most free graphics drivers, recent releases of Ubuntu haven't required a xorg. You can generate one pretty easily though:.

This works fine for me with Nvidia Optimus Bumblebee without any special configuration, just the defaults:. For more information about monitors. For users running Ubuntu Ubuntu Community Ask! Sign up to join this community. The best answers are voted up and rise to the top. Stack Overflow for Teams — Collaborate and share knowledge with a private group. Create a free Team What is Teams? Learn more. Where is the X.

How do I configure X there? Ask Question. Asked 11 years, 1 month ago. Active 1 year, 9 months ago. Viewed k times. Improve this question. Jorge Castro