In General Slow Performance

ravisghosh · 2007-01-22 11:25:53

Recently, I have been finding that everything is somewhat slower than it used to be. I'm unable to pin point after which upgrade it is like this, but i guess it was after upgrading to voodo (but thats just a guess). Its overall slow performance rather than any particular program, thunar opens slow, changing tab in opera is slow and likewise. Any guess guys?

Sekre · 2007-01-22 13:52:13

check if you have direct rendering on.
if it's off it can sometimes cause incredible slowdown on my systems at least.

$ glxinfo | grep -i "direct rendering"

ravisghosh · 2007-01-23 02:51:23

This is what i get with the above code:

[shantanu@bluehead ~]$ glxinfo | grep -i "direct rendering"
Xlib:  extension "GLX" missing on display ":0.0".
Xlib:  extension "GLX" missing on display ":0.0".
Xlib:  extension "GLX" missing on display ":0.0".
Error: couldn't find RGB GLX visual
Xlib:  extension "GLX" missing on display ":0.0".
Xlib:  extension "GLX" missing on display ":0.0".
Xlib:  extension "GLX" missing on display ":0.0".
Xlib:  extension "GLX" missing on display ":0.0".
[shantanu@bluehead ~]$

What does that imply by the way?

Cerebral · 2007-01-23 03:05:51

That implies you don't have hardware rendering enabled on your video card - do you have the line

Load "glx"

anywhere in /etc/X11/xorg.conf?

If you answered "yes" to that question, then what's the output of

grep "(EE)|(WW)" /var/log/Xorg.0.log

?

ravisghosh · 2007-01-23 04:24:09

ya i do have that like but thats commented out.

# This loads the GLX module
#    Load       "glx"

here is the output of the desired command:

[shantanu@bluehead ~]$ grep "(EE)|(WW)" /var/log/Xorg.0.log
        (WW) warning, (EE) error, (NI) not implemented, (??) unknown.
(WW) `fonts.dir' not found (or not valid) in "/usr/share/fonts/75dpi".
(WW) `fonts.dir' not found (or not valid) in "/usr/share/fonts/100dpi".
(WW) Open ACPI failed (/var/run/acpid.socket) (No such file or directory)
(WW) (640x350,Samsung Samtron 45Bn) mode clock 31.5MHz exceeds DDC maximum 0MHz
(WW) (640x400,Samsung Samtron 45Bn) mode clock 31.5MHz exceeds DDC maximum 0MHz
(WW) (720x400,Samsung Samtron 45Bn) mode clock 35.5MHz exceeds DDC maximum 0MHz
(WW) (640x480,Samsung Samtron 45Bn) mode clock 25.2MHz exceeds DDC maximum 0MHz
(WW) (640x480,Samsung Samtron 45Bn) mode clock 31.5MHz exceeds DDC maximum 0MHz
(WW) (640x480,Samsung Samtron 45Bn) mode clock 31.5MHz exceeds DDC maximum 0MHz
(WW) (640x480,Samsung Samtron 45Bn) mode clock 36MHz exceeds DDC maximum 0MHz
(WW) (800x600,Samsung Samtron 45Bn) mode clock 36MHz exceeds DDC maximum 0MHz
(WW) (800x600,Samsung Samtron 45Bn) mode clock 40MHz exceeds DDC maximum 0MHz
(WW) (800x600,Samsung Samtron 45Bn) mode clock 50MHz exceeds DDC maximum 0MHz
(WW) (800x600,Samsung Samtron 45Bn) mode clock 49.5MHz exceeds DDC maximum 0MHz
(WW) (800x600,Samsung Samtron 45Bn) mode clock 56.3MHz exceeds DDC maximum 0MHz
(WW) (1024x768,Samsung Samtron 45Bn) mode clock 65MHz exceeds DDC maximum 0MHz
(WW) (1024x768,Samsung Samtron 45Bn) mode clock 75MHz exceeds DDC maximum 0MHz
(WW) (1024x768,Samsung Samtron 45Bn) mode clock 78.8MHz exceeds DDC maximum 0MHz
(WW) (1024x768,Samsung Samtron 45Bn) mode clock 94.5MHz exceeds DDC maximum 0MHz
(WW) (1152x864,Samsung Samtron 45Bn) mode clock 108MHz exceeds DDC maximum 0MHz
(WW) (1280x960,Samsung Samtron 45Bn) mode clock 108MHz exceeds DDC maximum 0MHz
(WW) (1280x1024,Samsung Samtron 45Bn) mode clock 108MHz exceeds DDC maximum 0MHz
(WW) (1280x1024,Samsung Samtron 45Bn) mode clock 135MHz exceeds DDC maximum 0MHz
(WW) (832x624,Samsung Samtron 45Bn) mode clock 57.284MHz exceeds DDC maximum 0MH                                                               z
(WW) (1152x768,Samsung Samtron 45Bn) mode clock 64.995MHz exceeds DDC maximum 0M                                                               Hz
(WW) (1152x864,Samsung Samtron 45Bn) mode clock 121.5MHz exceeds DDC maximum 0MH                                                               z
(WW) (1400x1050,Samsung Samtron 45Bn) mode clock 122MHz exceeds DDC maximum 0MHz
(WW) (1600x1024,Samsung Samtron 45Bn) mode clock 106.91MHz exceeds DDC maximum 0                                                               MHz
(WW) (848x480,Samsung Samtron 45Bn) mode clock 31.49MHz exceeds DDC maximum 0MHz
(WW) (848x480,Samsung Samtron 45Bn) mode clock 37.52MHz exceeds DDC maximum 0MHz
(WW) (848x480,Samsung Samtron 45Bn) mode clock 40.96MHz exceeds DDC maximum 0MHz
(WW) (848x480,Samsung Samtron 45Bn) mode clock 47.39MHz exceeds DDC maximum 0MHz
(WW) (1152x864,Samsung Samtron 45Bn) mode clock 81.62MHz exceeds DDC maximum 0MH                                                               z
(WW) (1152x864,Samsung Samtron 45Bn) mode clock 96.77MHz exceeds DDC maximum 0MH                                                               z
(WW) (1152x864,Samsung Samtron 45Bn) mode clock 104.99MHz exceeds DDC maximum 0M                                                               Hz
(WW) (1152x864,Samsung Samtron 45Bn) mode clock 119.65MHz exceeds DDC maximum 0M                                   (WW) (1280x800,Samsung Samtron 45Bn) mode clock 83.46MHz exceeds DDC maximum 0MH                                                               z
(WW) (1280x800,Samsung Samtron 45Bn) mode clock 98.89MHz exceeds DDC maximum 0MH                                                               z
(WW) (1280x800,Samsung Samtron 45Bn) mode clock 107.21MHz exceeds DDC maximum 0M                                                               Hz
(WW) (1280x800,Samsung Samtron 45Bn) mode clock 123.38MHz exceeds DDC maximum 0M                                                               Hz
(WW) (1280x720,Samsung Samtron 45Bn) mode clock 74.48MHz exceeds DDC maximum 0MH                                                               z
(WW) (1280x720,Samsung Samtron 45Bn) mode clock 89.04MHz exceeds DDC maximum 0MH                                                               z
(WW) (1280x720,Samsung Samtron 45Bn) mode clock 95.65MHz exceeds DDC maximum 0MH                                                               z
(WW) (1280x720,Samsung Samtron 45Bn) mode clock 110.01MHz exceeds DDC maximum 0M                                                               Hz
(WW) (1280x768,Samsung Samtron 45Bn) mode clock 80.14MHz exceeds DDC maximum 0MH                                                               z
(WW) (1280x768,Samsung Samtron 45Bn) mode clock 94.98MHz exceeds DDC maximum 0MH                                                               z
(WW) (1280x768,Samsung Samtron 45Bn) mode clock 102.98MHz exceeds DDC maximum 0M                                                               Hz
(WW) (1280x768,Samsung Samtron 45Bn) mode clock 118.53MHz exceeds DDC maximum 0M                                                               Hz
(WW) I810(0): xf86AllocateGARTMemory: allocation of 1024 pages failed
(WW) I810(0): Direct rendering disabled
[shantanu@bluehead ~]$

So, direct rendering is off. now, how do i turn that on.

Snowman · 2007-01-23 05:28:44

Uncomment
Load "glx"
And install libgl-dri if it's not installed.
Make sure that your user is in the video group.

ravisghosh · 2007-01-23 19:32:11

I followed snowman, I cannot say the performance has improved quite a bit, but then I tried the command suggested by Sekre:

[shantanu@bluehead ~]$ glxinfo | grep -i "direct rendering"
direct rendering: No
[shantanu@bluehead ~]$

So direct rendering is still not enabled. Will enabling that enhance the performance and if yes, then how to do that?

Also, now I have another problem. After i followed snowman's instructions, now whenever I shutdown or restart, it asks for my password which was not the case earlier.

Sekre · 2007-01-24 11:21:53

enabling direct rendering will give you a boost in performance, yes

first what kind of graphics card do you have?
and do you have the drivers for that card installed and enabled?

nVidia : http://wiki.archlinux.org/index.php/How … DIA_driver
ATI : http://wiki.archlinux.org/index.php/ATI

or in case you have Intel chipset

$ pacman -Sy xf86-video-i810

and in xorg.conf set to the correct driver " i810 "

does this help?

On the problem with the password I have no clue though.

codemac · 2007-01-24 15:36:36

Yea, this will go a lot quicker if you can tell us every detail about your video card.

ravisghosh · 2007-01-25 02:15:15

i have intel motherboard only and no Nvidia, etc., So, I did "pacman -Sy xf86-video-i810" now where to put what in xorg.conf???

ploxiln · 2007-01-25 03:21:28

I'm using xfce4.4.0, and I installed slim (simple login manager) as a lightweight alternative to gdm. After that the graphics performance was terrible. When I reverted back to gdm instead the problem was fixed.

On another note, "glx" isn't exactly direct rendering, it's for 3d rendering. "dri" is direct rendering, which accelerates 2d rendering. There isn't linux support for glx with my videocard (some unichrome integrated one) but that doesn't prevent me from getting decent 2d performance.

sokuban · 2007-01-25 10:34:05

I'm gonna hijack this thread a bit. Forgive me, but I have a similar problem.

lspci gives me this:

00:02.0 VGA compatible controller: Intel Corporation Mobile 945GM/GMS/940GML Express Integrated Graphics Controller (rev 03)
00:02.1 Display controller: Intel Corporation Mobile 945GM/GMS/940GML Express Integrated Graphics Controller (rev 03)

I am pretty sure that my card is actually the 945GM.

I have installed the i810 driver with pacman.

I added my user to the video group (just now) and restarted X.

I tried this command.

[sokuban@Arche ~]$ grep "(EE)|(WW)" /var/log/Xorg.0.log 
        (WW) warning, (EE) error, (NI) not implemented, (??) unknown.
(WW) `fonts.dir' not found (or not valid) in "/usr/share/fonts/75dpi".
(WW) `fonts.dir' not found (or not valid) in "/usr/share/fonts/100dpi".
(WW) Open ACPI failed (/var/run/acpid.socket) (No such file or directory)
(WW) I810: No matching Device section for instance (BusID PCI:0:2:1) found
(WW) I810(0): Bad V_BIOS checksum
(WW) I810(0): Bad V_BIOS checksum
(WW) I810(0): config file hsync range 30-92kHz not within DDC hsync ranges.
(WW) I810(0): config file vrefresh range 50-85Hz not within DDC vrefresh ranges.
(WW) I810(0): Bad V_BIOS checksum
(WW) AIGLX: 3D driver claims to not support visual 0x23
(WW) AIGLX: 3D driver claims to not support visual 0x24
(WW) AIGLX: 3D driver claims to not support visual 0x25
(WW) AIGLX: 3D driver claims to not support visual 0x26
(WW) AIGLX: 3D driver claims to not support visual 0x27
(WW) AIGLX: 3D driver claims to not support visual 0x28
(WW) AIGLX: 3D driver claims to not support visual 0x29
(WW) AIGLX: 3D driver claims to not support visual 0x2a
(WW) AIGLX: 3D driver claims to not support visual 0x2b
(WW) AIGLX: 3D driver claims to not support visual 0x2c
(WW) AIGLX: 3D driver claims to not support visual 0x2d
(WW) AIGLX: 3D driver claims to not support visual 0x2e
(WW) AIGLX: 3D driver claims to not support visual 0x2f
(WW) AIGLX: 3D driver claims to not support visual 0x30
(WW) AIGLX: 3D driver claims to not support visual 0x31
(WW) AIGLX: 3D driver claims to not support visual 0x32
[sokuban@Arche ~]$

And this command.

[sokuban@Arche ~]$ glxinfo | grep -i "direct rendering" 
libGL error: open DRM failed (Operation not permitted)
libGL error: reverting to (slow) indirect rendering
direct rendering: No
[sokuban@Arche ~]$

I've been trying to get direct rendering/openGL working for a long time but one day I gave up and came to the conclusion only Nvidia, ATI and a few expensive Intel cards (that I don't have) work with it. After seeing this I think I might have a chance.

My computer has a nice dual processor and all that so I can live life (and even play games) on pure processing power, but direct rendering would be a very nice thing indeed.

sh__ · 2007-01-25 15:12:15

sokuban wrote:

I have installed the i810 driver with pacman.
I added my user to the video group (just now) and restarted X.
(WW) I810: No matching Device section for instance (BusID PCI:0:2:1) found

Do you have a device section in xorg.conf for the Intel driver? I have an i855 chipset and it handles 3D stuff like beryl and (older) games quite decently. This is what I have in xorg.conf (things that are commented out should probably be adjusted to your system)

Section "Device"
        Identifier  "Card0"
        Driver      "i810"
        VendorName  "Intel Corp."
#        BoardName   "82852/855GM Integrated Graphics Device"
#        BusID       "PCI:0:2:0"
#        VideoRam    "32768"
EndSection

and in the screen section

Section "Screen"
.
.
       Device     "Card0"
.
.

sokuban · 2007-01-26 09:19:45

No go it seems, but I did notice I have two device sections, I commented out the entire section about the generic video card and X still starts up, but I have the same problems. So at least part of the i810 driver works.

ravisghosh · 2007-01-27 02:54:30

Here is my xorg.conf

# 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        "speedo"
    Load        "freetype"
#    Load        "xtt"

# This loads the GLX module
    Load       "glx"
# This loads the DRI module
#    Load       "dri"

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"
    FontPath   "/usr/share/fonts/75dpi"
    FontPath   "/usr/share/fonts/100dpi"
#    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"    "pc104"
    Option "XkbLayout"    "us"

EndSection


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

Section "InputDevice"

# Identifier and driver

    Identifier    "Mouse1"
    Driver    "mouse"
    Option "Protocol"    "Microsoft"    # Microsoft compatible (2-button protocol)
    Option "Device"      "/dev/ttyS0"

# 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  "Samsung Samtron 45Bn"

# 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   30-55

#    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 50-120

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  "Intel i810"
    Driver      "i810"
    #VideoRam    32768
    # Insert Clocks lines here if appropriate
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      "Intel i810"
    Monitor     "Samsung Samtron 45Bn"
    DefaultDepth 24

    Subsection "Display"
        Depth       8
        Modes       "1280x1024" "1024x768" "800x600" "640x480"
        ViewPort    0 0
    EndSubsection
    Subsection "Display"
        Depth       16
        Modes       "1280x1024" "1024x768" "800x600" "640x480"
        ViewPort    0 0
    EndSubsection
    Subsection "Display"
        Depth       24
        Modes       "1280x1024" "1024x768" "800x600" "640x480"
        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  "Simple Layout"

# 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"

EndSection

# Section "DRI"
#    Mode 0666
# EndSection

After installing xorg, I ran xorgconfig which asked me to put identifiers for my video card, etc., and I remember I had put i810 only even though I installed xf86-video-i810 recently and it was vesa (i guess) which was and is working.

Could anyone please suggest where shall i put what line to get direct rendering on and get better performance. Shall I remove vesa? Also, in kde, at times I'm getting vertical lines in kde menu. Is the probable reason like in xorg?

Also, the password problem while restarting or shutting down has solved on its own.

sh__ · 2007-01-27 16:30:54

You could try this: remove or comment out the vesa driver and uncomment the following lines:
In Section "Module":

    Load       "dri"

and in the end of file:

Section "DRI"
    Mode 0666
EndSection

ravisghosh · 2007-01-27 19:12:56

there is no "vesa" in my xorg. At the time of doing xorgconfig that asked me to put graphic card identifier and i guess i had put "i810." So, is "i810" reprsenting vesa or is it represent xf86-video-i810. I can easily remove xf86-video-i810 without any problem and xfce works well, but when i try to remove, xf86-video-vesa, it says xorg depends on it. Shall I comment out "load glx" if I'm doing what u have said above @sh_.

ploxiln · 2007-01-27 19:54:13

ravisghosh, notice that you have two (2) "Device" sections, the first one specifies "Driver 'vga'", I would suggest you try to comment out everything in that first section, as well as uncomment the dri stuff sh__ mentions.

sh__ · 2007-01-27 20:26:40

@ravisghosh: I meant remove the lines from xorg.conf, NOT the package with 'pacman -R'.

As ploxiln said, the first device section is for the vesa driver. So comment out this whole section:

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

ravisghosh · 2007-01-27 20:35:42

edit:

After rebooting, X was not working without xf86-video-i810 and hence, it seems my box is using xf86-video-i810 rather than vesa. Then i reinstalled xf86-video-i810.

I commented out the the following things:

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

Driver "vga"

but again, it did not work.
Again, i tried to comment out this section:

Section "Device"
Identifier "Intel i810"
Driver "i810"
#VideoRam 32768
# Insert Clocks lines here if appropriate
EndSection

but the same story, x would not start.

Last edited by ravisghosh (2007-01-27 20:56:32)

ravisghosh · 2007-01-28 04:01:24

is direct rendering anyway related to playing music online in sites like this.

http://ww.smashits.com/music/pop/songs/ … -sami.html
http://www.musicindiaonline.com/music/ut/s/ghazals/10/
http://www.raaga.com/channels/hindi/top10.asp

I had not been able to play music online even though i installed mplayer-plugin, etc. There was an indication that one needs direct rendering to play them.

deficite · 2007-01-28 05:20:00

ravisghosh wrote:

Recently, I have been finding that everything is somewhat slower than it used to be. I'm unable to pin point after which upgrade it is like this, but i guess it was after upgrading to voodo (but thats just a guess). Its overall slow performance rather than any particular program, thunar opens slow, changing tab in opera is slow and likewise. Any guess guys?

I know you have probably realized that it wasn't Voodoo that did it to you by now, but for future reference: in a rolling release system such as Arch, you never "upgrade" to a newer version of the distro. What reports to you when you start up is what the initscripts have in them to display. I'm just telling you this to prevent further confusion for you and anybody else that reads this thread that isn't aware of this.

ravisghosh · 2007-01-28 18:27:41

@deficiete, you u mean that one should install fresh whenever a new version is available....

deficite · 2007-01-28 19:45:15

No, I mean that the release names don't mean anything at all. Arch is a rolling release system and thus if you run a pacman -Syu every now and then you'll always be updated. Arch isn't like *buntu where software doesn't really update much until a new release of the whole system, which updates everything all at once.

Basically, ignore the whole Voodoo thing. Whenever we go to 8.1 ignore that as well. It doesn't mean anything at all in a rolling release system. Well, except the the installer may be updated a bit and some more updated packages may be on the install discs (but if you keep running pacman -Syu, you'll be updated beyond those anyway)

Last edited by deficite (2007-01-28 19:48:22)

ravisghosh · 2007-01-28 20:23:29

Thanks a lot for that info. however, unknowingly, i was doing the same, keeping myself updated.. Any idea about the direct rendering thing.

Arch Linux

#1 2007-01-22 11:25:53

In General Slow Performance

#2 2007-01-22 13:52:13

Re: In General Slow Performance

#3 2007-01-23 02:51:23

Re: In General Slow Performance

#4 2007-01-23 03:05:51

Re: In General Slow Performance

#5 2007-01-23 04:24:09

Re: In General Slow Performance

#6 2007-01-23 05:28:44

Re: In General Slow Performance

#7 2007-01-23 19:32:11

Re: In General Slow Performance

#8 2007-01-24 11:21:53

Re: In General Slow Performance

#9 2007-01-24 15:36:36

Re: In General Slow Performance

#10 2007-01-25 02:15:15

Re: In General Slow Performance

#11 2007-01-25 03:21:28

Re: In General Slow Performance

#12 2007-01-25 10:34:05

Re: In General Slow Performance

#13 2007-01-25 15:12:15

Re: In General Slow Performance

#14 2007-01-26 09:19:45

Re: In General Slow Performance

#15 2007-01-27 02:54:30

Re: In General Slow Performance

#16 2007-01-27 16:30:54

Re: In General Slow Performance

#17 2007-01-27 19:12:56

Re: In General Slow Performance

#18 2007-01-27 19:54:13

Re: In General Slow Performance

#19 2007-01-27 20:26:40

Re: In General Slow Performance

#20 2007-01-27 20:35:42

Re: In General Slow Performance

#21 2007-01-28 04:01:24

Re: In General Slow Performance

#22 2007-01-28 05:20:00

Re: In General Slow Performance

#23 2007-01-28 18:27:41

Re: In General Slow Performance

#24 2007-01-28 19:45:15

Re: In General Slow Performance

#25 2007-01-28 20:23:29

Re: In General Slow Performance

Board footer