How to override Xorg DPI setting?

zodmaner · 2007-11-09 04:44:25

New xorg brings new problem for me. It seems that the new xorg ignores the DisplaySize option in xorg.conf, results in X using the wrong DPI setting. I set my DisplaySize option to 337 270 (for my 1280x1024 LCD monitor) and this is what xdpyinfo gives me:

  dimensions:    1280x1024 pixels (359x203 millimeters)
  resolution:    91x128 dots per inch

running grep -i DPI /var/log/Xorg.0.log gives this:

(**) RADEON(0): DPI set to (144, 112)

Both, as you can see, is wrong.

So, is there anyway to override xorg DPI setting? I've tried using Option "UseEdidDpi" and Option "DPI" to set my DPI but this also didn't work because xorg just blissfully ignores these options. Could anyone help me? I use ATi open source driver (radeon).

Last edited by zodmaner (2007-11-09 05:00:28)

buttons · 2007-11-09 05:03:38

Those options work fine for me in xorg 7.3:

(**) NVIDIA(0): Option "UseEdidDpi" "FALSE"
(**) NVIDIA(0): Option "DPI" "86 x 86"
(**) NVIDIA(0): DPI set to (86, 86); computed from "DPI" X config option

Seems to be a radeon issue?

zodmaner · 2007-11-09 06:20:09

I've tried those options and this is the message from xorg log:

(**) RADEON(0): DPI set to (144, 112)
(WW) RADEON(0): Option "UseEdidDpi" is not used
(WW) RADEON(0): Option "DPI" is not used

Sadly, it seems that these two options only works on Nvidia card.

mindfall · 2007-11-09 22:27:08

I have a Nvidia card (Gf 4) and setting dpi does not work any longer since the update.

Excerpt from Xorg's log:

(**) NVIDIA(0): Option "UseEdidDpi" "false"
(**) NVIDIA(0): Option "DPI" "96 x 96"
(**) NVIDIA(0): DPI set to (96, 96); computed from "DPI" X config option

So, as far as the log is concerned, it works. However, xdpyinfo reports 77 dots per inch.
Changing dpi with xrandr --dpi 96 also does not work. It's fixed to 77

buttons · 2007-11-09 23:07:17

Very interesting indeed. I went back and checked, but my log is correct...I'm at 86 DPI as requested.

mindfall · 2007-11-10 00:06:36

Hm I think it is a xrandr bug.
Stupid me, I forgot I switch down screen resolution when starting a WM.

In the previous xorg release, changing the resolution would not affect the dpi when explicitly set in xorg.conf.
Manpage also says "Normally, xrandr resets the reported physical size values to keep the DPI constant"

But it seems dpi is always calculated against the highest possible resolution in xorg.conf
I had to request 120 dpi to get 96

Edit: When thinking about it, I guess it's a feature not a bug

Last edited by mindfall (2007-11-10 00:13:31)

wonder · 2007-11-10 10:19:56

you need to write DisplaySize in Monitor Section e.g
DisplaySize 336 269 # 96 1280x1024

336 = 1280/96*25.4
269 = 1024/96*25.4

exiguous · 2007-11-11 03:23:02

zodmaner wrote:

So, is there anyway to override xorg DPI setting?

Possibly the easiest way around this is to set DPI in ~/.Xdefaults or ~/.Xresources:

Xft.dpi: 96

You can apply the setting with

xrdb -merge ~/.Xdefaults (or ~/.Xresources if you use that)

Check with:

xrdb -query | grep dpi

If you really want to use the DisplaySize setting, I do it by specifying the following option in the Device section of xorg.conf:

Option "NoDDC"

Since I'm not using DDC, I use a Modeline. You can generate one with gtf (man gtf) or there are several online Modeline generators. You may be able to specify the mode without a Modeline, but I have found for my setup that Xorg uses the wrong vertical refresh rate unless I tell it the one I want.

Last edited by exiguous (2007-11-11 03:24:32)

zodmaner · 2007-11-11 10:11:41

Thank you for all help & suggestions, guys. I've tried exiguous methods by setting DPI in ~/.Xdefaults file to 96 and putting the Option "NoDDC" in xorg.conf.
Although xrdb -query | grep dpi reports this:

Xft.dpi:        96

But xdpyinfo | grep -B1 dot stills gives me this:

  
  dimensions:    1280x1024 pixels (359x203 millimeters)
  resolution:    91x128 dots per inch

And not only that but my Xorg log still show this:

(**) RADEON(0): Option "NoDDC"
...
(**) RADEON(0): Display dimensions: (337, 270) mm
(**) RADEON(0): DPI set to (144, 112)

Whice shows that "NoDDC" option is working and that Xorg uses my DisplaySize setting (finally!). But for some reason it still sets wrong DPI value (144, 112 instate of 96,96).

Last edited by zodmaner (2007-11-11 10:13:11)

shining · 2007-11-11 10:25:43

My guess is that Xorg doesn't like lies.

More seriously, I don't understand where this (144, 112) value comes from.

zodmaner · 2007-11-11 10:37:40

shining wrote:

My guess is that Xorg doesn't like lies.

Lies? What lies?

More seriously, I don't understand where this (144, 112) value comes from.

Me neither. I guess Xorg compute this value from something or somewhere.

Let me stress again that I did not have this problem back in Xorg 7.2.

shining · 2007-11-11 11:09:12

zodmaner wrote:

shining wrote:
My guess is that Xorg doesn't like lies.
Lies? What lies?

Aren't you trying to lie about the dimensions of your monitor?
What is 359x203 millimeters ?

More seriously, I don't understand where this (144, 112) value comes from.
Me neither. I guess Xorg compute this value from something or somewhere.

If the real dimensions aren't 359x203, that could maybe explain it.

Otherwise, I just read your last post again, and I'm not sure you understood the Xft.dpi stuff.
It won't change the dpi used by Xorg, but that doesn't matter.
Every gtk2 / qt applications use Xft, so they will use the Xft.dpi (which defaults to the dpi detected by Xorg, unless explicitly overridden).

zodmaner · 2007-11-11 11:54:48

My monitor real dimensions is 337.9 x 270.3 mm. 359x203 just come out of no where after I upgrade to Xorg 7.3 (it was 337x270 in Xorg 7.2).

You're right though, I don't understand a thing about Xft.dpi stuff. I just follow advise provided by exiguous in hoping that it might fixes my problem (which it didn't, sadly ).

Last edited by zodmaner (2007-11-11 11:56:06)

shining · 2007-11-11 15:42:27

zodmaner wrote:

My monitor real dimensions is 337.9 x 270.3 mm. 359x203 just come out of no where after I upgrade to Xorg 7.3 (it was 337x270 in Xorg 7.2).

Oh I see. So now that's 2 values we have no idea where it comes from :
359x203 mm reported by xdpyinfo and 144x112 dpi reported by xorg.

I see a new package of the ati driver has just been released : 6.7.195-3
Did you try this already?

Also could you paste your xorg.conf ? Seems like you didn't do that yet.

You're right though, I don't understand a thing about Xft.dpi stuff. I just follow advise provided by exiguous in hoping that it might fixes my problem (which it didn't, sadly ).

What is your problem exactly? Fonts are too big in some applications I suppose? Which applications?

I also saw the xorg-server package had a patch related to DisplaySize that is no longer used :
http://cvs.archlinux.org/cgi-bin/viewcv … text/plain

The code modified by this patch has moved. It isn't in the same .c file anymore, but I found the exact same code in another place. So maybe applying this patch again would help. But looking quickly at the code there, it looks like using Option NoDDC would have the same effect.
But before digging in the code, it's probably better to look at the related bugs on bugs.freedesktop,org first.

Edit : found a similar report, but nothing interesting
https://bugs.freedesktop.org/show_bug.cgi?id=6004

Last edited by shining (2007-11-11 16:38:50)

ralvez · 2007-11-11 15:57:45

This is the formula I use to override Xorg dip settings:

Assuming I want a resolution of 84 dpi at 1024x768 I'll have to calculate 2 numbers...one for horizontal and one for vertical. As my resolution is 1024x768, I will use this as the example. The formula is as follows:

displaysize = (<pixelsize>/DPI-Desired)*25.4

In my case, displaysize = (1024/84)*25.4. This equals 309,638 (round off to 310). I wrote this down for later. Now I need to use 768 (my vertical setting for resolution 1024x768) in the same formula (displaysize =(768/84)*25.4) which comes out to 232.228 (round off to 232).
So, the numbers are 310 and 232 which is what we put in xorg.conf, like this:

DisplaySize 310 232 # 84 DPI @ 1024x768

Hope this helps.

R

exiguous · 2007-11-11 21:35:41

zodmaner wrote:

You're right though, I don't understand a thing about Xft.dpi stuff. I just follow advise provided by exiguous in hoping that it might fixes my problem (which it didn't, sadly ).

As shining explained in post #12, all of your GTK 2 and Qt applications will use that "Xft.dpi: 96" setting, so that fixes your problem of having a DPI of 96.

I'm not sure why your DPI as reported by xdpyinfo is being overridden even with the NoDDC option set. I use the ati driver (r128 specifically) and it works fine with that one. Maybe the radeon driver has a bug (?). It doesn't matter though, since the Xft setting does the job of setting an appropriate DPI for you.

Last edited by exiguous (2007-11-11 21:36:50)

zodmaner · 2007-11-12 04:18:48

You're right shining. I should have explained myself better.

Currently I have 2 main problems:

1. My DPI setting and monitor dimension have been changed from DPI 96 and 337 270 to other values, as explained above. This results in font being too large.

2. My GDM login screen is corrupted. It used wrong resolution (1024x768 instate of 1280x1024) and the screen is heavy distorted like it have been shrinked to fit the monitor screen. I've tried SLiM but it have the same problem so I guess that the problem lies with Xorg. (Maybe I'm wrong here).

Both of these happens after I upgrades to the new Xorg 7.3

As for the DPI problem, well it seems that exiguous advise did the tricks and now GNOME finally uses the correct DPI value (and the font size becomes normal again). Although it stills being wrongly reported in xdpyinfo & in Xorg log.

I still couldn't find any solution to my corrupted GDM login screen. At first I jumped to a conclusion that the problem with my corrupted GDM screen lies with the wrong DPI & monitor dimension values, but I may be wrong here. Fortunately after login GNOME used the correct resoluiton (1280x1024) and I'm able to use my desktop normally.

I've tried the new radeon driver and the problems still persist.

Here is my xorg.conf file.

# File generated by xorgconfig.

#
# Copyright 2004 The X.Org Foundation
#
# Permission is hereby granted, free of charge, to any person obtaining a
# copy of this software and associated documentation files (the "Software"),
# to deal in the Software without restriction, including without limitation
# the rights to use, copy, modify, merge, publish, distribute, sublicense,
# and/or sell copies of the Software, and to permit persons to whom the
# Software is furnished to do so, subject to the following conditions:
# 
# The above copyright notice and this permission notice shall be included in
# all copies or substantial portions of the Software.
# 
# THE SOFTWARE IS PROVIDED "AS IS", WITHOUT WARRANTY OF ANY KIND, EXPRESS OR
# IMPLIED, INCLUDING BUT NOT LIMITED TO THE WARRANTIES OF MERCHANTABILITY,
# FITNESS FOR A PARTICULAR PURPOSE AND NONINFRINGEMENT.  IN NO EVENT SHALL
# The X.Org Foundation BE LIABLE FOR ANY CLAIM, DAMAGES OR OTHER LIABILITY,
# WHETHER IN AN ACTION OF CONTRACT, TORT OR OTHERWISE, ARISING FROM, OUT OF
# OR IN CONNECTION WITH THE SOFTWARE OR THE USE OR OTHER DEALINGS IN THE
# SOFTWARE.
# 
# Except as contained in this notice, the name of The X.Org Foundation shall
# not be used in advertising or otherwise to promote the sale, use or other
# dealings in this Software without prior written authorization from
# The X.Org Foundation.
#

# **********************************************************************
# Refer to the xorg.conf(5) man page for details about the format of 
# this file.
# **********************************************************************

# **********************************************************************
# Module section -- this  section  is used to specify
# which dynamically loadable modules to load.
# **********************************************************************
#
Section "Module"

# This loads the DBE extension module.

    Load        "dbe"      # Double buffer extension

# This loads the miscellaneous extensions module, and disables
# initialisation of the XFree86-DGA extension within that module.
    SubSection  "extmod"
      Option    "omit xfree86-dga"   # don't initialise the DGA extension
    EndSubSection

# This loads the font modules
#    Load        "type1"
    Load        "freetype"
#    Load        "xtt"

# This loads the GLX module
    Load        "glx"
# This loads the DRI module
    Load        "dri"
# From ArchWiki on ATI Radeon:
    Load        "drm"

EndSection

# **********************************************************************
# Files section.  This allows default font and rgb paths to be set
# **********************************************************************

Section "Files"

# The location of the RGB database.  Note, this is the name of the
# file minus the extension (like ".txt" or ".db").  There is normally
# no need to change the default.

#    RgbPath    "/usr/share/X11/rgb"

# Multiple FontPath entries are allowed (which are concatenated together),
# as well as specifying multiple comma-separated entries in one FontPath
# command (or a combination of both methods)
# 
# 

    FontPath   "/usr/share/fonts/misc"

# Commented out because errors in Xorg.0.log
#    FontPath   "/usr/share/fonts/100dpi:unscaled" 
#    FontPath   "/usr/share/fonts/75dpi:unscaled"

    FontPath   "/usr/share/fonts/TTF"
#    FontPath   "/usr/share/fonts/Type1"
#    FontPath   "/usr/lib/X11/fonts/local/"
#    FontPath   "/usr/lib/X11/fonts/misc/"
#    FontPath   "/usr/lib/X11/fonts/75dpi/:unscaled"
#    FontPath   "/usr/lib/X11/fonts/100dpi/:unscaled"
#    FontPath   "/usr/lib/X11/fonts/Speedo/"
#    FontPath   "/usr/lib/X11/fonts/Type1/"
#    FontPath   "/usr/lib/X11/fonts/TrueType/"
#    FontPath   "/usr/lib/X11/fonts/freefont/"
#    FontPath   "/usr/lib/X11/fonts/75dpi/"
#    FontPath   "/usr/lib/X11/fonts/100dpi/"

# The module search path.  The default path is shown here.

#    ModulePath "/usr/lib/modules"

EndSection

# **********************************************************************
# Server flags section.
# **********************************************************************

Section "ServerFlags"

# Uncomment this to cause a core dump at the spot where a signal is 
# received.  This may leave the console in an unusable state, but may
# provide a better stack trace in the core dump to aid in debugging

#    Option "NoTrapSignals"

# Uncomment this to disable the <Ctrl><Alt><Fn> VT switch sequence
# (where n is 1 through 12).  This allows clients to receive these key
# events.

#    Option "DontVTSwitch"

# Uncomment this to disable the <Ctrl><Alt><BS> server abort sequence
# This allows clients to receive this key event.

#    Option "DontZap"

# Uncomment this to disable the <Ctrl><Alt><KP_+>/<KP_-> mode switching
# sequences.  This allows clients to receive these key events.

#    Option "Dont Zoom"

# Uncomment this to disable tuning with the xvidtune client. With
# it the client can still run and fetch card and monitor attributes,
# but it will not be allowed to change them. If it tries it will
# receive a protocol error.

#    Option "DisableVidModeExtension"

# Uncomment this to enable the use of a non-local xvidtune client. 

#    Option "AllowNonLocalXvidtune"

# Uncomment this to disable dynamically modifying the input device
# (mouse and keyboard) settings. 

#    Option "DisableModInDev"

# Uncomment this to enable the use of a non-local client to
# change the keyboard or mouse settings (currently only xset).

#    Option "AllowNonLocalModInDev"

EndSection

# **********************************************************************
# Input devices
# **********************************************************************

# **********************************************************************
# Core keyboard's InputDevice section
# **********************************************************************

Section "InputDevice"

    Identifier    "Keyboard1"
    Driver    "kbd"

# For most OSs the protocol can be omitted (it defaults to "Standard").
# When using XQUEUE (only for SVR3 and SVR4, but not Solaris),
# uncomment the following line.

#    Option     "Protocol"      "Xqueue"

    Option "AutoRepeat" "500 30"

# Specify which keyboard LEDs can be user-controlled (eg, with xset(1))
#    Option    "Xleds"      "1 2 3"

#    Option "LeftAlt"     "Meta"
#    Option "RightAlt"    "ModeShift"

# To customise the XKB settings to suit your keyboard, modify the
# lines below (which are the defaults).  For example, for a non-U.S.
# keyboard, you will probably want to use:
#    Option "XkbModel"    "pc105"
# If you have a US Microsoft Natural keyboard, you can use:
#    Option "XkbModel"    "microsoft"
#
# Then to change the language, change the Layout setting.
# For example, a german layout can be obtained with:
#    Option "XkbLayout"   "de"
# or:
#    Option "XkbLayout"   "de"
#    Option "XkbVariant"  "nodeadkeys"
#
# If you'd like to switch the positions of your capslock and
# control keys, use:
#    Option "XkbOptions"  "ctrl:swapcaps"

# These are the default XKB settings for Xorg
#    Option "XkbRules"    "xorg"
#    Option "XkbModel"    "pc105"
#    Option "XkbLayout"   "us"
#    Option "XkbVariant"  ""
#    Option "XkbOptions"  ""

#    Option "XkbDisable"

    Option "XkbRules"    "xorg"
    Option "XkbModel"    "pc101"
    Option "XkbLayout"    "us"
    Option "XkbOptions"    "grp:alt_shift_toggle,grp_led:scroll"

EndSection


# **********************************************************************
# Core Pointer's InputDevice section
# **********************************************************************

Section "InputDevice"

# Identifier and driver

    Identifier    "Mouse1"
    Driver    "mouse"
    Option "Protocol"    "Auto"    # Auto detect
    Option "Device"      "/dev/input/mice"

# When using XQUEUE, comment out the above two lines, and uncomment
# the following line.

#    Option "Protocol"    "Xqueue"

# Mouse-speed setting for PS/2 mouse.

#    Option "Resolution"    "256"

# Baudrate and SampleRate are only for some Logitech mice. In
# almost every case these lines should be omitted.

#    Option "BaudRate"    "9600"
#    Option "SampleRate"    "150"

# Mouse wheel mapping.  Default is to map vertical wheel to buttons 4 & 5,
# horizontal wheel to buttons 6 & 7.   Change if your mouse has more than
# 3 buttons and you need to map the wheel to different button ids to avoid
# conflicts.

    Option "ZAxisMapping"   "4 5 6 7"

# Emulate3Buttons is an option for 2-button mice
# Emulate3Timeout is the timeout in milliseconds (default is 50ms)

#    Option "Emulate3Buttons"
#    Option "Emulate3Timeout"    "50"

# ChordMiddle is an option for some 3-button Logitech mice

#    Option "ChordMiddle"

EndSection


# **********************************************************************
# Other input device sections 
# this is optional and is required only if you
# are using extended input devices.  This is for example only.  Refer
# to the xorg.conf man page for a description of the options.
# **********************************************************************
#
# Section "InputDevice" 
#    Identifier  "Mouse2"
#    Driver      "mouse"
#    Option      "Protocol"      "MouseMan"
#    Option      "Device"        "/dev/mouse2"
# EndSection
#
# Section "InputDevice"
#    Identifier "spaceball"
#    Driver     "magellan"
#    Option     "Device"        "/dev/cua0"
# EndSection
#
# Section "InputDevice"
#    Identifier "spaceball2"
#    Driver     "spaceorb"
#    Option     "Device"        "/dev/cua0"
# EndSection
#
# Section "InputDevice"
#    Identifier "touchscreen0"
#    Driver     "microtouch"
#    Option     "Device"        "/dev/ttyS0"
#    Option     "MinX"          "1412"
#    Option     "MaxX"          "15184"
#    Option     "MinY"          "15372"
#    Option     "MaxY"          "1230"
#    Option     "ScreenNumber"  "0"
#    Option     "ReportingMode" "Scaled"
#    Option     "ButtonNumber"  "1"
#    Option     "SendCoreEvents"
# EndSection
#
# Section "InputDevice"
#    Identifier "touchscreen1"
#    Driver     "elo2300"
#    Option     "Device"        "/dev/ttyS0"
#    Option     "MinX"          "231"
#    Option     "MaxX"          "3868"
#    Option     "MinY"          "3858"
#    Option     "MaxY"          "272"
#    Option     "ScreenNumber"  "0"
#    Option     "ReportingMode" "Scaled"
#    Option     "ButtonThreshold"       "17"
#    Option     "ButtonNumber"  "1"
#    Option     "SendCoreEvents"
# EndSection

# **********************************************************************
# Monitor section
# **********************************************************************

# Any number of monitor sections may be present

Section "Monitor"

    Identifier  "Philips 170B"

# HorizSync is in kHz unless units are specified.
# HorizSync may be a comma separated list of discrete values, or a
# comma separated list of ranges of values.
# NOTE: THE VALUES HERE ARE EXAMPLES ONLY.  REFER TO YOUR MONITOR'S
# USER MANUAL FOR THE CORRECT NUMBERS.

    HorizSync   31.5 - 82.0

#    HorizSync    30-64         # multisync
#    HorizSync    31.5, 35.2    # multiple fixed sync frequencies
#    HorizSync    15-25, 30-50  # multiple ranges of sync frequencies

# VertRefresh is in Hz unless units are specified.
# VertRefresh may be a comma separated list of discrete values, or a
# comma separated list of ranges of values.
# NOTE: THE VALUES HERE ARE EXAMPLES ONLY.  REFER TO YOUR MONITOR'S
# USER MANUAL FOR THE CORRECT NUMBERS.

    VertRefresh 56.0 - 76.0

# From ArchWiki on Xorg 

    DisplaySize 337 270 # 96 DPI @ 1280x1024 # Check DPI by issuing this command: $ xdpyinfo | grep -B1 dot

# Modeline generated from gtf -1280 -1024 -x -v

#    Modeline "1280x1024_60.00"  108.88  1280 1360 1496 1712  1024 1025 1028 1060  -HSync +Vsync # 1280x1024 @ 60.00 Hz (GTF) hsync: 63.60 kHz; pclk: 108.88 MHz

EndSection


# **********************************************************************
# Graphics device section
# **********************************************************************

# Any number of graphics device sections may be present

# Standard VGA Device:

Section "Device"
    Identifier    "Standard VGA"
    VendorName    "Unknown"
    BoardName    "Unknown"

# The chipset line is optional in most cases.  It can be used to override
# the driver's chipset detection, and should not normally be specified.

#    Chipset    "generic"

# The Driver line must be present.  When using run-time loadable driver
# modules, this line instructs the server to load the specified driver
# module.  Even when not using loadable driver modules, this line
# indicates which driver should interpret the information in this section.

    Driver     "vga"
# The BusID line is used to specify which of possibly multiple devices
# this section is intended for.  When this line isn't present, a device
# section can only match up with the primary video device.  For PCI
# devices a line like the following could be used.  This line should not
# normally be included unless there is more than one video device
# intalled.

#    BusID      "PCI:0:10:0"

#    VideoRam    256

#    Clocks    25.2 28.3

EndSection

# Device configured by xorgconfig:

Section "Device"
    Identifier  "ATI Radeon X700 PRO (RV410)"
    Driver      "ati"
    VideoRam    131072
    # Insert Clocks lines here if appropriate

# From ArchWiki on ATI Radeon

#    Option    "XAANoOffscreenPixmaps" "true" # Don't need if use EXA

# From ArchWiki on Configuring XOrg for Composite

#    Option    "DRI" "true" # Not work? (Got error in Xorg.0.log)

# Performance tuning from ArchWiki on ATI Radeon

    Option    "AGPMode" "8"

    Option      "AccelMethod" "EXA" # Could be problematic # Couldn't start X

    #ColorTiling is completely safe to enable and supposedly is enabled
    # by default. People have noted a performance increase when enabled
    # via xorg.conf.

    Option    "ColorTiling" "on"
    
    Option      "EnablePageFlip" "on"

#    Option      "AGPFastWrite" "yes" # Could be problematic, Doesn't affect PCIE models

# From DRI wiki on ATIRadeon 

#    Option      "AccelMethod" "XAA"

    Option      "AccelDFS" "on" # On for PCIE, off for AGP

    Option      "GARTSize" "64" 

# I add this in myself

    BusID    "PCI:1:0:0"

# Disable DDC

    Option      "NoDDC"

EndSection


# **********************************************************************
# Screen sections
# **********************************************************************

# Any number of screen sections may be present.  Each describes
# the configuration of a single screen.  A single specific screen section
# may be specified from the X server command line with the "-screen"
# option.
Section "Screen"
    Identifier  "Screen 1"
    Device      "ATI Radeon X700 PRO (RV410)"
    Monitor     "Philips 170B"
    DefaultDepth 24

    Subsection "Display"
        Depth       24
        Modes       "1280x1024" 
        ViewPort    0 0
    EndSubsection
EndSection

# **********************************************************************
# ServerLayout sections.
# **********************************************************************

# Any number of ServerLayout sections may be present.  Each describes
# the way multiple screens are organised.  A specific ServerLayout
# section may be specified from the X server command line with the
# "-layout" option.  In the absence of this, the first section is used.
# When now ServerLayout section is present, the first Screen section
# is used alone.

Section "ServerLayout"

# The Identifier line must be present
    Identifier  "Layout 1"

# Each Screen line specifies a Screen section name, and optionally
# the relative position of other screens.  The four names after
# primary screen name are the screens to the top, bottom, left and right
# of the primary screen.  In this example, screen 2 is located to the
# right of screen 1.

    Screen "Screen 1"

# Each InputDevice line specifies an InputDevice section name and
# optionally some options to specify the way the device is to be
# used.  Those options include "CorePointer", "CoreKeyboard" and
# "SendCoreEvents".

    InputDevice "Mouse1" "CorePointer"
    InputDevice "Keyboard1" "CoreKeyboard"

# From ArchWiki on Configuring XOrg for Composite

    Option    "AIGLX" "true"

EndSection

# The following was uncommented according to ArchWiki ATI Radeon  suggestion

Section "DRI"
    Group "video"
    Mode 0660
EndSection

# From ArchWiki on Configuring XOrg for Composite

Section "Extensions"
    Option "Composite" "Enable"
EndSection

I hope that I've explain my problems better this time. If there're anything that you want me to explain better, just say so ok?

Last edited by zodmaner (2007-11-12 11:37:39)

SiD · 2007-11-12 12:54:46

have you tried to add -dpi 96 to the serverargs in the startx script? The script is in /usr/bin .

defaultserverargs="-dpi 96"

Arch Linux

#1 2007-11-09 04:44:25

How to override Xorg DPI setting?

#2 2007-11-09 05:03:38

Re: How to override Xorg DPI setting?

#3 2007-11-09 06:20:09

Re: How to override Xorg DPI setting?

#4 2007-11-09 22:27:08

Re: How to override Xorg DPI setting?

#5 2007-11-09 23:07:17

Re: How to override Xorg DPI setting?

#6 2007-11-10 00:06:36

Re: How to override Xorg DPI setting?

#7 2007-11-10 10:19:56

Re: How to override Xorg DPI setting?

#8 2007-11-11 03:23:02

Re: How to override Xorg DPI setting?

#9 2007-11-11 10:11:41

Re: How to override Xorg DPI setting?

#10 2007-11-11 10:25:43

Re: How to override Xorg DPI setting?

#11 2007-11-11 10:37:40

Re: How to override Xorg DPI setting?

#12 2007-11-11 11:09:12

Re: How to override Xorg DPI setting?

#13 2007-11-11 11:54:48

Re: How to override Xorg DPI setting?

#14 2007-11-11 15:42:27

Re: How to override Xorg DPI setting?

#15 2007-11-11 15:57:45

Re: How to override Xorg DPI setting?

#16 2007-11-11 21:35:41

Re: How to override Xorg DPI setting?

#17 2007-11-12 04:18:48

Re: How to override Xorg DPI setting?

#18 2007-11-12 12:54:46

Re: How to override Xorg DPI setting?

Board footer