Arch Linux

harry

Member

Registered: 2007-06-25

Posts: 24

xorg issue with ati x700 mobility

hello

i have just installed arch on my laptop and it works fine so far except one thing...install and configure xorg right

first, my hardware:

samsung x20 with ati x700 mobilty card

i´ve read a lot in the forum and in the wiki about similar issues but nothing really works for me
i deleted my xorg.conf and generated a "blank" new one with hwd -xa to start at 0

first, there is the question about the right driver.which one should i use for the above-named graphic-card?
the open source one or the fglrx?later i´d like to try beryl and because of that - as far as i know - i have to make the decision about the driver as soon as possible...well the more i read the more i get confused and disoriented :S

so i know the issue with xorg very well from a previous try to get arch running a year ago :>
i can´t manage it by myself but i want to learn, it´d be nice if someone can take me by the hand so i learn it once and for all

any help appreciated

thanks

calvinthomas

Member

Registered: 2007-06-24

Posts: 15

Re: xorg issue with ati x700 mobility

Hi harry, I have the same card as you, I chose to use the fglrx driver as I find the open source driver difficult to setup, to get everything working correctly (for beryl and accelerated graphics etc) I had to do some minor editing of my /etc/X11/xorg.conf file. I'm pretty sure my settings aren't perfect but they're working well enough for me:

Here is my /etc/X11/xorg.conf file so you can use it as a reference (I would assume if you copied it identically and used the wiki to install fglrx, xgl, beryl etc it should work for you as the card is identical).

# 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.
# **********************************************************************
#
# **********************************************************************
# Files section.  This allows default font and rgb paths to be set
# **********************************************************************
# **********************************************************************
# Server flags section.
# **********************************************************************
# **********************************************************************
# Input devices
# **********************************************************************
# **********************************************************************
# Core keyboard's InputDevice section
# **********************************************************************
# **********************************************************************
# Core Pointer's InputDevice section
# **********************************************************************
# **********************************************************************
# 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
# **********************************************************************
# Graphics device section
# **********************************************************************
# Any number of graphics device sections may be present
# Standard VGA Device:
# Device configured by xorgconfig:
# **********************************************************************
# 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.
# **********************************************************************
# 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 "DRI"
    Mode 0666
 EndSection

Section "ServerLayout"

# The Identifier line must be present
# 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.
# 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".
    Identifier     "Simple Layout"
    Screen      0  "aticonfig-Screen[0]" 0 0
    InputDevice    "Mouse1" "CorePointer"
    InputDevice    "Keyboard1" "CoreKeyboard"
EndSection

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/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"
    FontPath     "/usr/share/fonts/misc"
    FontPath     "/usr/share/fonts/100dpi:unscaled"
    FontPath     "/usr/share/fonts/75dpi:unscaled"
    FontPath     "/usr/share/fonts/TTF"
    FontPath     "/usr/share/fonts/Type1"
EndSection

Section "Module"

# This loads the DBE extension module.
# This loads the miscellaneous extensions module, and disables
# initialisation of the XFree86-DGA extension within that module.
# This loads the font modules
#    Load        "type1"
# This loads the GLX module
#    Load       "glx"
# This loads the DRI module
    Load       "dri"
    Load  "dbe"      # Double buffer extension
    SubSection "extmod"
        Option        "omit xfree86-dga"   # don't initialise the DGA extension
    EndSubSection
    Load  "freetype"
#    Load        "xtt"
EndSection

Section "InputDevice"

# 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    "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"
    Identifier  "Keyboard1"
    Driver      "kbd"
    Option        "AutoRepeat" "500 30"
# Specify which keyboard LEDs can be user-controlled (eg, with xset(1))
    Option        "XkbRules" "xorg"
    Option        "XkbModel" "pc101"
    Option        "XkbLayout" "gb"
EndSection

Section "InputDevice"

# Identifier and driver
# 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.
# 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"
    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
    Option        "ZAxisMapping" "4 5 6 7"
# Emulate3Buttons is an option for 2-button mice
EndSection

Section "Monitor"

# 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-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.
    Identifier   "My Monitor"
    HorizSync    31.5 - 48.5
    VertRefresh  50.0 - 70.0
EndSection

Section "Monitor"
    Identifier   "aticonfig-Monitor[0]"
    Option        "VendorName" "ATI Proprietary Driver"
    Option        "ModelName" "Generic Autodetecting Monitor"
    Option        "DPMS" "true"
EndSection

Section "Device"

# 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.
# 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
    Identifier  "Standard VGA"
    Driver      "vga"
    VendorName  "Unknown"
    BoardName   "Unknown"
EndSection

Section "Device"

    # unsupported card
    #VideoRam    131072
    # Insert Clocks lines here if appropriate
    Identifier  "My Video Card"
    Driver      "vga"
EndSection

Section "Device"
    Identifier  "aticonfig-Device[0]"
    Driver      "fglrx"
EndSection

Section "Screen"
    Identifier "Screen 1"
    Device     "My Video Card"
    Monitor    "My Monitor"
    DefaultDepth     24
    SubSection "Display"
        Viewport   0 0
        Depth     8
        Modes    "1280x1024" "1024x768" "800x600" "640x480"
    EndSubSection
    SubSection "Display"
        Viewport   0 0
        Depth     16
        Modes    "1280x1024" "1024x768" "800x600" "640x480"
    EndSubSection
    SubSection "Display"
        Viewport   0 0
        Depth     24
        Modes    "1280x1024" "1024x768" "800x600" "640x480"
    EndSubSection
EndSection

Section "Screen"
    Identifier "aticonfig-Screen[0]"
    Device     "aticonfig-Device[0]"
    Monitor    "aticonfig-Monitor[0]"
    DefaultDepth     24
    SubSection "Display"
        Viewport   0 0
        Depth     24
    EndSubSection
EndSection

P.S. I set my horizontal sync and vertical refresh semi-manually, please check they are not too high for your system before using this xorg file.

Last edited by calvinthomas (2007-06-26 11:29:49)

thayer

Fellow

From: Vancouver, BC

Registered: 2007-05-20

Posts: 1,560

Website

Re: xorg issue with ati x700 mobility

If you're still looking for advice, I would say go with the fglrx driver as it's the easiest.  If you want Beryl+XGL, then you might need the proprietary drivers straight from ATI--I'm not sure because I don't bother with Beryl.  If all you want is native resolution (e.g. 1680x1050) and 3d gaming, then the fglrx driver is perfect:

# pacman -S fglrx
# hwd -xa
# aticonfig --initial

Then simply add "fglrx" to the modules section of /etc/rc.conf.  Restart X and away you go.  The aticonfig sets the proper values for your xorg.conf (if you want to see what its doing, simply compare the new xorg.conf with the backup it creates.)

---

thayer williams ~ thayerwilliams.ca

harry

Member

Registered: 2007-06-25

Posts: 24

Re: xorg issue with ati x700 mobility

hi again

thx for your answers

@calvinthomas

i´ve tried your xorg and it works immediately, thx for that
(uhh just copy and paste, don´t think that i learned much out of this :>, will examine in more detail later)

at the moment i try to get beryl running, just installed beryl and xgl according to the wiki (i skipped the section for configuring gdm because a friend told me that it is just "fine tuning").

as i use your xorg.conf i naively typed beryl-manager atfer the install and hoped it would work out of the box

in fact i became:

**************
* Beryl system compatiblity check                            *
**************************************************************

Detected xserver                                : AIGLX

Checking Display :1.0 ...

Checking for XComposite extension               : failed

No composite extension
beryl: No composite extension

oaky i added

Section "Extensions"
    Option "Composite" "Enabled"
EndSection

to my xorg.conf but i got even more strange errors... :

**************
* Beryl system compatiblity check                            *
**************************************************************

Detected xserver                                : AIGLX

Checking Display :1.0 ...

Checking for XComposite extension               : passed (v0.3)
Checking for XDamage extension                  : passed
Checking for RandR extension                    : passed
Checking for XSync extension                    : passed

Checking Screen 0 ...

Checking for GLX_SGIX_fbconfig                  : passed
Checking for GLX_EXT_texture_from_pixmap        : passed
Checking for non power of two texture support   : failed

Support for non power of two textures missing
beryl: Support for non power of two textures missing
beryl: Failed to manage screen: 0
beryl: No manageable screens found on display :1.0

what can i do to solve the problem?

thx in advance

harry

Last edited by harry (2007-06-25 17:23:21)

thayer

Fellow

From: Vancouver, BC

Registered: 2007-05-20

Posts: 1,560

Website

Re: xorg issue with ati x700 mobility

harry, I could be wrong about this, but I don't think the fglrx drivers currently work with Beryl because they don't support Composite.  Referring to the Beryl Wiki it states (towards the bottom) that you must remove the fglrx drivers and install the open source version (e.g. xf86-video-ati).

Last edited by thayer.w (2007-06-25 17:45:28)

---

thayer williams ~ thayerwilliams.ca

billy

Member

From: Slovenia

Registered: 2006-09-13

Posts: 164

Re: xorg issue with ati x700 mobility

harry, I could be wrong about this, but I don't think the fglrx drivers currently work with Beryl because they don't support Composite.  Referring to the Beryl Wiki it states (towards the bottom) that you must remove the fglrx drivers and install the open source version (e.g. xf86-video-ati).

beryl runs on fglrx but yoou need xgl

harry

Member

Registered: 2007-06-25

Posts: 24

Re: xorg issue with ati x700 mobility

hi

@thayer.w
yes i´ve read that too, but calvinthomas said that it is possible with him too
i found that wiki entry very confusing...

beryl runs on fglrx but yoou need xgl

i´ve already done that, just typed

pacman -S xgl

as i said above

at the moment i try to get beryl running, just installed beryl and xgl according to the wiki (i skipped the section for configuring gdm because a friend told me that it is just "fine tuning").

thx harry

billy

Member

From: Slovenia

Registered: 2006-09-13

Posts: 164

Re: xorg issue with ati x700 mobility

at the moment i try to get beryl running, just installed beryl and xgl according to the wiki (i skipped the section for configuring gdm because a friend told me that it is just "fine tuning").

do you use gdm to log into X session? because if you didn't modify gdm, then gdm still starts a normal X session and not Xgl.

calvinthomas

Member

Registered: 2007-06-24

Posts: 15

Re: xorg issue with ati x700 mobility

You must use an XGL session to get Beryl to work (with fglrx anyway) installing it puts it on your system but doesn't actually run it, to get it running take a look at this:

http://wiki.archlinux.org/index.php/Xgl If you are using gnome, I personally would use gdm method 2, if KDE kdm method 2 but you can use method 1 if you want to, when you have set that up correctly (just follow the guide) then make sure you've done this:

pacman -Sy beryl-gnome

(for Gnome)

pacman -Sy beryl-kde

(for KDE)

pacman -Sy beryl

(I think for platform independent?)

Finally your probably (although its not essential) are going to want to do:

pacman -S emerald emerald-themes

HTH

Calv

P.S as for the Xorg file, most of it is completely as standard following an xorgconfig and aticonfig --initial, the only things I did was uncomment a couple of things I think, the section on dri and dri being diabled and possibly something else but I can't remember for sure, I didn't do very much at all. Finally since I used xorgconfig, I set my horizontal sync and vertical resolution for my monitor semi-manually, I didn't set them particularly high but you MUST check they aren't too high for your system, I really should have mentioned that much earlier, it was late last night though, so I apologise, I'll update my first post incase anyone else uses it.

P.P.S You can check if you card is set up correctly by doing:

fglrxinfo

If it mentions ATI Radeon X700 your good, if it mentions mesa its not set-up quite right and beryl won't work!

Last edited by calvinthomas (2007-06-26 11:30:28)

harry

Member

Registered: 2007-06-25

Posts: 24

Re: xorg issue with ati x700 mobility

hi again.

thx guys everything works fine now

do you use gdm to log into X session? because if you didn't modify gdm, then gdm still starts a normal X session and not Xgl.

yes i but as i said i thought thatś just "fine tuning"....as said by sb.

Finally since I used xorgconfig, I set my horizontal sync and vertical resolution for my monitor semi-manually, I didn't set them particularly high but you MUST check they aren't too high for your system, I really should have mentioned that much earlier, it was late last night though, so I apologise, I'll update my first post incase anyone else uses it.

i will check that immediately, thanks for that notation. btw no need to make an excuse

thank you for your efforts! especially yours calvinthomas

harry