LinuxQuestions.org - ati-driver-installer-8-4

- Slackware (https://www.linuxquestions.org/questions/slackware-14/)

- - ati-driver-installer-8-4 (https://www.linuxquestions.org/questions/slackware-14/ati-driver-installer-8-4-a-641698/)

ati-driver-installer-8-4

Sorry to bother with such a newbie question, but i need some help with installing the latest fglrx ati drivers.

I downloaded the installer and after running the installer script like this

root@darkstar:/ati# sh ati-driver-installer-8-4-x86.x86_64.run --buildpkg Slackware/All

what i get is:

Code:



Created directory fglrx-install.KSzujc

Verifying archive integrity... All good.

Uncompressing ATI Proprietary Linux Driver-8.476.....................................................................................................................................................................................................................................................................................................................................................................................................................................................................................................................................................................................................................

==================================================

 ATI Technologies Linux Driver Installer/Packager

==================================================

Generating package: Slackware/All



ATI SlackBuild Ver. 1.2.0

--------------------------------------------

by: Emanuele Tomasi <tomasiATcli.di.unipi.it>

    Ezio Ghibaudo<ekxiusATgmail.com>

    Federico Rota<federico.rota01ATgmail.com>



ATI module generator V 2.0

==========================

initializing...

cleaning...

patching 'highmem.h'...

assuming new VMA API since we do have kernel 2.6.x...

 Assuming default VMAP API

 Assuming default munmap API

doing Makefile based build for kernel 2.6.x and higher

make -C /lib/modules/2.6.24/build SUBDIRS=/ati/fglrx-install.KSzujc/common/lib/modules/fglrx/build_mod/2.6.x modules

make[1]: Entering directory `/usr/src/linux-2.6.24'

  CC [M]  /ati/fglrx-install.KSzujc/common/lib/modules/fglrx/build_mod/2.6.x/firegl_public.o

/ati/fglrx-install.KSzujc/common/lib/modules/fglrx/build_mod/2.6.x/firegl_public.c: In function '__ke_check_pci':

/ati/fglrx-install.KSzujc/common/lib/modules/fglrx/build_mod/2.6.x/firegl_public.c:1951: error: implicit declaration of function 'pci_find_slot'

/ati/fglrx-install.KSzujc/common/lib/modules/fglrx/build_mod/2.6.x/firegl_public.c:1951: warning: assignment makes pointer from integer without a cast

make[2]: *** [/ati/fglrx-install.KSzujc/common/lib/modules/fglrx/build_mod/2.6.x/firegl_public.o] Error 1

make[1]: *** [_module_/ati/fglrx-install.KSzujc/common/lib/modules/fglrx/build_mod/2.6.x] Error 2

make[1]: Leaving directory `/usr/src/linux-2.6.24'

make: *** [kmod_build] Error 2

build failed with return value 2

Error -> I don't have make module

Removing temporary directory: fglrx-install.KSzujc

root@darkstar:/ati#

Code:

root@darkstar:/ati# uname -a

Linux darkstar 2.6.24 #4 PREEMPT Sun Apr 20 14:29:03 CEST 2008 i686 AMD Athlon(tm) 64 Processor 3500+ AuthenticAMD GNU/Linux

I guess i need to patch the firegl_public.c file, but i'm not sure which patch exactly to apply and how, so step by step instructions for this would be really appreciated, thank you.

I've gotten it to work just by:

Code:

$ chmod +x ati*.run

$ sudo ./ati*.run

I have never attempted to build a package from it - do you consider it completely necessary to do so?

I'm guessing you switched to a non-smp kernel, and may need the non-smp kernel headers.
See here:
http://slackware.osuosl.org/slackwar...4.5-nosmp-sdk/

Even those with single-core processors should be running the smp kernel - if they are able.
You will avoid many problems.

You are doing the right thing by building fglrx packages for Slackware.
Much easier to upgrade/uninstall later.

you had to chmod the file because of your usage.

sh ati...etc the files needs to be +x

if you
sh ./ati...etc the file will work without having to chmod -/+

Just for reference.

could also be an issue with your custom kernel...

Your kernel was configured with CONFIG_PCI_LEGACY=n.

Did you build it yourself? In kernel-generic-2.6.24.5-i486-2 it is enabled.

Thanks for the comments, yes i built my own custom kernel and after a bit of googling i've seen that i need to enable PCI_CONFIG_LEGACY, so after recompiling the kernel, the driver module, and xorg module compile just fine ..

after that i restarted the x-server, rebooted, ran aticonfig --initial, but so far couldn't get 3d acceleration working :\ .. here's the output of Xorg.0.log :

Code:

root@darkstar:/dev/dri# cat /var/log/Xorg.0.log | grep '(EE)'

        (WW) warning, (EE) error, (NI) not implemented, (??) unknown.

(EE) fglrx(0): atiddxDriScreenInit failed, GPS not been initialized.

(EE) AIGLX: Screen 0 is not DRI capable

Code:

root@darkstar:/home/orion# glxinfo | grep direct

direct rendering: No

OpenGL renderer string: Mesa GLX Indirect

root@darkstar:/home/orion# dmesg | grep fglrx

fglrx: module license 'Proprietary. (C) 2002 - ATI Technologies, Starnberg, GERMANY' taints kernel.

[fglrx] Maximum main memory to use for locked dma buffers: 927 MBytes.

[fglrx] ASYNCIO init succeed!

[fglrx] PAT is enabled successfully!

[fglrx:firegl_init_module] *ERROR* firegl_stub_register failed

[fglrx] Maximum main memory to use for locked dma buffers: 927 MBytes.

[fglrx] ASYNCIO init succeed!

[fglrx:KCL_enable_pat] *ERROR* Pat entry 2 is already configured

[fglrx] PAT is disabled!

[fglrx:firegl_init_module] *ERROR* firegl_stub_register failed

[fglrx] Maximum main memory to use for locked dma buffers: 927 MBytes.

[fglrx] ASYNCIO init succeed!

[fglrx:KCL_enable_pat] *ERROR* Pat entry 2 is already configured

[fglrx] PAT is disabled!

[fglrx:firegl_init_module] *ERROR* firegl_stub_register failed

root@darkstar:/home/orion#

After googling a bit more, i read there was no common solution to this issue, so didn't get much further ..

@wadsworth
I installed the non-smp kernel headers just in case now, thx :)

Also, there was no card0 in /dev/dri for some reason .. any ideas ?

ok, here's my xorg.conf file:

Code:



# File generated by xf86config.

#

# Copyright (c) 1999 by The XFree86 Project, Inc.

#

# 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 XFREE86 PROJECT 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 XFree86 Project 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

# XFree86 Project.

#

# **********************************************************************

# Refer to the XF86Config(4/5) man page for details about the format of 

# this file.

# **********************************************************************

# NOTE:  This is a NEW IMPROVED version of XF86Config-fbdev that uses the vesa

# driver instead of the fbdev driver.  Thanks to Kenneth Fanyo who pointed

# this out to me. :)

# This XF86Config file is designed for use with the VESA framebuffer.

# This generic interface should work with nearly all video cards

# (although not every card will support every resolution).

# With the new driver, it should no longer be required to have frame buffer

# support in the kernel, or to run it on the console.

#

# Enjoy! :)

# -- volkerdi@slackware.com

#

# **********************************************************************

# 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

# **********************************************************************

# Some examples of extended input devices

# 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

# **********************************************************************

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

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

# 

# If you don't have a floating point coprocessor and emacs, Mosaic or other

# programs take long to start up, try moving the Type1 and Speedo directory

# to the end of this list (or comment them out).

# 

# ModulePath can be used to set a search path for the X server modules.

# The default path is shown here.

#    ModulePath "/usr/lib/xorg/modules"

        RgbPath      "/usr/share/X11/rgb"

        FontPath    "/usr/share/fonts/local/"

        FontPath    "/usr/share/fonts/misc/"

        FontPath    "/usr/share/fonts/OTF/"

        FontPath    "/usr/share/fonts/TTF/"

        FontPath    "/usr/share/fonts/Type1/"

        FontPath    "/usr/share/fonts/CID/"

        FontPath    "/usr/share/fonts/Speedo/"

        FontPath    "/usr/share/fonts/75dpi/:unscaled"

        FontPath    "/usr/share/fonts/100dpi/:unscaled"

        FontPath    "/usr/share/fonts/75dpi/"

        FontPath    "/usr/share/fonts/100dpi/"

        FontPath    "/usr/share/fonts/cyrillic/"

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

# This loads the GLX module

        Load  "dbe"          # Double buffer extension

        SubSection "extmod"

                Option            "omit xfree86-dga"  # don't initialise the DGA extension

        EndSubSection

        Load  "type1"

        Load  "freetype"

    #Load        "speedo"

        Load    "dri"

        Load    "glx"

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"

# Set the keyboard auto repeat parameters.  Not all platforms implement

# this.

#    Option    "AutoRepeat"    "500 5"

# Specifiy which keyboard LEDs can be user-controlled (eg, with xset(1)).

#    Option    "Xleds" "1 2 3"

# To disable the XKEYBOARD extension, uncomment XkbDisable.

#    Option    "XkbDisable"

# To customise the XKB settings to suit your keyboard, modify the

# lines below (which are the defaults).  For example, for a European

# keyboard, you will probably want to use one of:

#

#    Option    "XkbModel"      "pc102"

#    Option    "XkbModel"      "pc105"

#

# If you have a Microsoft Natural keyboard, you can use:

#

#    Option    "XkbModel"      "microsoft"

#

# If you have a US "windows" keyboard you will want:

#

#    Option    "XkbModel"      "pc104"

#

# 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 X.Org

#

#    Option    "XkbRules"      "xorg"

#    Option    "XkbModel"      "pc105"

#    Option    "XkbLayout"    "us"

#    Option    "XkbVariant"    ""

#    Option    "XkbOptions"    ""

        Identifier  "Keyboard1"

        Driver      "kbd"

EndSection



Section "InputDevice"



# Identifier and driver

# On platforms where PnP mouse detection is supported the following

# protocol setting can be used when using a newer PnP mouse:

#    Option    "Protocol"      "Auto"

# The available mouse protocols types that you can set below are:

#    Auto BusMouse GlidePoint GlidePointPS/2 IntelliMouse IMPS/2

#    Logitech Microsoft MMHitTab MMSeries Mouseman MouseManPlusPS/2

#    MouseSystems NetMousePS/2 NetScrollPS/2 OSMouse PS/2 SysMouse

#    ThinkingMouse ThinkingMousePS/2 Xqueue

# which is usually a symbolic link to the real device.

#  Option "Device"      "/dev/ttyS0"

#  Option "Device"      "/dev/ttyS1"

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

# the following line.

#    Option "Protocol"        "Xqueue"

# Baudrate and SampleRate are only for some Logitech mice. In

# almost every case these lines should be omitted.

#    Option "BaudRate"                "9600"

#    Option "SampleRate"        "150"

# Emulate3Buttons is an option for 2-button Microsoft 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"

        Identifier  "Mouse1"

        Driver      "mouse"

        Option            "Protocol" "PS/2"

# The mouse device.  The device is normally set to /dev/mouse,

        Option            "Device" "/dev/mouse"

#  Option "Device"      "/dev/psaux"

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 - 50.0

        VertRefresh  40.0 - 90.0

EndSection



Section "Monitor"

        Identifier  "aticonfig-Monitor[0]"

        Option            "VendorName" "ATI Proprietary Driver"

        Option            "ModelName" "Generic Autodetecting Monitor"

        Option            "DPMS" "true"

EndSection



Section "Device"



    #VideoRam    4096

    # Insert Clocks lines here if appropriate

        Identifier  "VESA Framebuffer"

        Driver      "vesa"

EndSection



Section "Device"

        Identifier  "aticonfig-Device[0]"

        Driver      "fglrx"

EndSection



Section "Screen"



# If your card can handle it, a higher default color depth (like 24 or 32)

# is highly recommended.

#  DefaultDepth 8

#  DefaultDepth 16

#  DefaultDepth 32

# "1024x768" is also a conservative usable default resolution.  If you

# have a better monitor, feel free to try resolutions such as

# "1152x864", "1280x1024", "1600x1200", and "1800x1400" (or whatever your

# card/monitor can produce)

        Identifier "Screen 1"

        Device    "VESA Framebuffer"

        Monitor    "My Monitor"

        DefaultDepth    24

        SubSection "Display"

                Depth    8

                Modes    "1024x768" "800x600" "640x480"

        EndSubSection

        SubSection "Display"

                Depth    16

                Modes    "1024x768" "800x600" "640x480"

        EndSubSection

        SubSection "Display"

                Depth    24

                Modes    "1024x768" "800x600" "640x480"

        EndSubSection

        SubSection "Display"

                Depth    32

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



Section "DRI"

      Group  0

      Mode    0666

EndSection

I've done the liberty and replaced your xorg.conf with the following. Please try this out to see if direct rendering works now.

Code:



Section "ServerLayout"

        Identifier    "Simple Layout"

        Screen      0  "aticonfig-Screen[0]" 0 0

        InputDevice    "Mouse1" "CorePointer"

        InputDevice    "Keyboard1" "CoreKeyboard"

EndSection



Section "ServerFlags"

        Option “IgnoreABI” “on”

        Option “AIGLX” “true”

EndSection



Section "Files"

        RgbPath      "/usr/share/X11/rgb"

        FontPath    "/usr/share/fonts/local/"

        FontPath    "/usr/share/fonts/misc/"

        FontPath    "/usr/share/fonts/OTF/"

        FontPath    "/usr/share/fonts/TTF/"

        FontPath    "/usr/share/fonts/Type1/"

        FontPath    "/usr/share/fonts/CID/"

        FontPath    "/usr/share/fonts/Speedo/"

        FontPath    "/usr/share/fonts/75dpi/:unscaled"

        FontPath    "/usr/share/fonts/100dpi/:unscaled"

        FontPath    "/usr/share/fonts/75dpi/"

        FontPath    "/usr/share/fonts/100dpi/"

        FontPath    "/usr/share/fonts/cyrillic/"

EndSection



Section "Module"

        Load  "dbe"          # Double buffer extension

        SubSection "extmod"

                Option            "omit xfree86-dga"  # don't initialise the DGA extension

        EndSubSection

        Load  "type1"

        Load  "freetype"

        Load    "dri"

        Load    "glx"

EndSection



Section "InputDevice"

        Identifier  "Keyboard1"

        Driver      "kbd"

EndSection



Section "InputDevice"

        Identifier  "Mouse1"

        Driver      "mouse"

        Option            "Protocol" "PS/2"

        Option            "Device" "/dev/mouse"

EndSection



Section "Monitor"

        Identifier  "My Monitor"

        HorizSync    31.5 - 50.0

        VertRefresh  40.0 - 90.0

EndSection



Section "Monitor"

        Identifier  "aticonfig-Monitor[0]"

        Option            "VendorName" "ATI Proprietary Driver"

        Option            "ModelName" "Generic Autodetecting Monitor"

        Option            "DPMS" "true"

EndSection



Section "Device"

        Identifier  "aticonfig-Device[0]"

        Driver      "fglrx"

        Option “VideoOverlay” “on”

        Option “OpenGLOverlay” “off”

        Option “XAANoOffscreenPixmaps” “true”

        Option “AllowGLXWithComposite” “true”

        Option “RenderAccel” “true”

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

Thank you for your effort, but, unfortunately, i still haven't managed to get 3d acceleration running.

dmesg | grep fglrx still returns :
[fglrx:firegl_init_module] *ERROR* firegl_stub_register failed

Here's the output of Xorg.0.log file:

http://pastebin.ca/1017982

Trying to load fglrx kernel module manually gives:

Code:

root@darkstar:/ati# modprobe fglrx

FATAL: Error inserting fglrx (/lib/modules/2.6.24/external/fglrx.ko.gz): Operation not permitted

It has to do wih your custom kernel. Found this on another website

Quote:

Make sure that "Direct Rendering Manager" and anything ati/radeon (and other graphic cards) are set to module, not built in (drm is in device drivers/character devices).

Don't forget to copy your kernel to /boot and re-run lilo :P small mistakes like this can happen.

EDIT: you can just check the .config file in your kernel sources tree for CONFIG_DRM and the like (ex: grep CONFIG_DRM /usr/src/linux/.config). It should be set to m not y.

Btw, there are ATI slackBuilds out now at slackBuilds.org.

Quote:

Originally Posted by symatic (Post 3153143)

It has to do wih your custom kernel. Found this on another website

Setting CONFIG_DRM to "m" did the trick ! The module loads just fine now. Thanks :)

But, the problem now i have is getting black screen after 'startx' with my own xorg.conf aswell with the one kindly provided by agentc0re .. both used to work just fine before.
I tried disabling composite extensions in xorg, as suggested somewhere, but that didn't solve the problem, hmm.. what could be wrong now ? :D

Quote:

Btw, there are ATI slackBuilds out now at slackBuilds.org.

Very nice, i like the fact they change the amdcccle in the build to allow users to use it. Stock slackware kernels people, saves alot of time. Different topic.

Quote:

But, the problem now i have is getting black screen after 'startx' with my own xorg.conf aswell with the one kindly provided by agentc0re .. both used to work just fine before.
I tried disabling composite extensions in xorg, as suggested somewhere, but that didn't solve the problem, hmm.. what could be wrong now ?

What I do after I install the fglrx pkgs is run 'xorgsetup'. I know it is like beating a dead horse but it will display all the options for the fglrx driver. Also check in /var/log/Xorg.0.log it will tell you whats going on.

Tried it, same thing happens unfortunately :\ .. Xorg.0.log only gave 1 warning, but that was related to the other device on my card (no screens found for bus : pci:1:0:1, something like that), but i have no intentions in making dualhead confguration anyway.

Seems that enabling "dri" module results in a black screen because i am able to starx with a generic xorg-vesa config, while fglrx is loaded, expect from not having 3d support, and AIGLX beeing disabled.