| View previous topic :: View next topic |
| Author |
Message |
olger901
l33t
Joined: 17 Mar 2005
Posts: 625
|
 Posted: Thu May 25, 2006 10:00 am Post subject: ati-drivers-8.25.18 are in portage! |
 |
|
Hi all,
I wanted to let you guys know that the ati-drivers-8.25.18 are in portage and that they seem to be alot more stable then any previous ati-drivers. I also noticed a very slight fps increase when using glxgears (I know it's not a benchmark tool, but it does give an indication) with the new drivers btw 
Now I would like to know: What are your experiences with the ati-drivers?? |
|
| Back to top |
|
 |
Cryssli
Apprentice
Joined: 16 Sep 2003
Posts: 213
Location: Regensburg - Germany
|
| Posted: Thu May 25, 2006 11:35 am Post subject: |
|
|
Hi,
still black screen when starting X. Maybe the backtrace at the end of Xorg.0.log is helpful for somebody who can 'read' it.
| Code: | uname -a
Linux athlon 2.6.16-gentoo-r7 #2 SMP Mon May 8 18:12:54 CEST 2006 x86_64 AMD Athlon(tm) 64 X2 Dual Core Processor 4200+ GNU/Linux
|
xorg.conf
| Code: |
# 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(5x) 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:
# **********************************************************************
# 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/share/fonts/TTF"
# 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/75dpi"
FontPath "/usr/share/fonts/100dpi"
FontPath "/usr/share/fonts/Type1"
FontPath "usr/share/fonts/corefonts/"
FontPath "/usr/share/fonts/freefont/"
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"
# Load "speedo"
# This loads the GLX module
# Load "glx"
# This loads the DRI module
# Load "dri"
# Load "dga"
Load "dbe" # Double buffer extension
SubSection "extmod"
Option "omit xfree86-dga" # don't initialise the DGA extension
EndSubSection
Load "freetype"
# Load "xtt"
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"
# 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"
# 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 "XkbVariant" "nodeadkeys"
#
Option "XkbRules" "xorg"
Option "XkbModel" "pc105"
Option "XkbLayout" "de"
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" "IMPS/2" # PS/2 Mouse
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 "NEC"
HorizSync 31.5 - 64.3
VertRefresh 50.0 - 70.0
EndSection
Section "Monitor"
Identifier "aticonfig Monitor 0"
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 "vesa"
# 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:05:0"
# VideoRam 256
# Clocks 25.2 28.3
Identifier "permedia"
Driver "vesa"
VendorName "Unknown"
BoardName "Unknown"
EndSection
Section "Device"
Identifier "ATI Graphics Adapter 0"
Driver "fglrx"
BusID "PCI:5:0:0"
EndSection
Section "Screen"
# DefaultDepth 16
#
# Subsection "Display"
# Depth 8
# Modes "1280x1024" "1024x768" "800x600" "640x480"
# ViewPort 0 0
# EndSubsection
# Subsection "Display"
# Depth 16
# Modes "1024x768" "800x600" "640x480"
# ViewPort 0 0
# EndSubsection
# Subsection "Display"
# Depth 24
# Modes "800x600" "640x480"
# ViewPort 0 0
# EndSubsection
Identifier "Screen 1"
Device "permedia"
Monitor "NEC"
EndSection
Section "Screen"
Identifier "aticonfig Screen 0"
Device "ATI Graphics Adapter 0"
Monitor "aticonfig Monitor 0"
DefaultDepth 24
SubSection "Display"
Viewport 0 0
Depth 24
EndSubSection
EndSection
|
[code]
Supported Future Video Modes
X Window System Version 7.0.0
Release Date: 21 December 2005
X Protocol Version 11, Revision 0, Release 7.0
Build Operating System:Linux 2.6.16-gentoo-r7 x86_64
Current Operating System: Linux athlon 2.6.16-gentoo-r7 #2 SMP Mon May 8 18:12:54 CEST 2006 x86_64
Build Date: 08 May 2006
Before reporting problems, check http://wiki.x.org
to make sure that you have the latest version.
Module Loader present
Markers: (--) probed, (**) from config file, (==) default setting,
(++) from command line, (!!) notice, (II) informational,
(WW) warning, (EE) error, (NI) not implemented, (??) unknown.
(==) Log file: "/var/log/Xorg.0.log", Time: Thu May 25 13:24:39 2006
(==) Using config file: "/etc/X11/xorg.conf"
(==) ServerLayout "Simple Layout"
(**) |-->Screen "aticonfig Screen 0" (0)
(**) | |-->Monitor "aticonfig Monitor 0"
(**) | |-->Device "ATI Graphics Adapter 0"
(**) |-->Input Device "Mouse1"
(**) |-->Input Device "Keyboard1"
(WW) The directory "/usr/share/fonts/freefont/" does not exist.
Entry deleted from font path.
(**) FontPath set to "/usr/share/fonts/misc,/usr/share/fonts/75dpi,/usr/share/fonts/100dpi,/usr/share/fonts/Type1,usr/share/fonts/corefonts/"
(==) RgbPath set to "/usr/share/X11/rgb"
(==) ModulePath set to "/usr/lib64/xorg/modules"
(II) Module ABI versions:
X.Org ANSI C Emulation: 0.2
X.Org Video Driver: 0.8
X.Org XInput driver : 0.5
X.Org Server Extension : 0.2
X.Org Font Renderer : 0.4
(II) Loader running on linux
(II) LoadModule: "bitmap"
(II) Loading /usr/lib64/xorg/modules/fonts/libbitmap.so
(II) Module bitmap: vendor="X.Org Foundation"
compiled for 7.0.0, module version = 1.0.0
Module class: X.Org Font Renderer
ABI class: X.Org Font Renderer, version 0.4
(II) Loading font Bitmap
(II) LoadModule: "pcidata"
(II) Loading /usr/lib64/xorg/modules/libpcidata.so
(II) Module pcidata: vendor="X.Org Foundation"
compiled for 7.0.0, module version = 1.0.0
ABI class: X.Org Video Driver, version 0.8
(--) using VT number 7
...
Xorg.0.log:
[code]
(II) fglrx(0): [drm] DRM interface version 1.0
(II) fglrx(0): [drm] created "fglrx" driver at busid "PCI:5:0:0"
(II) fglrx(0): [drm] added 8192 byte SAREA at 0x2000
(II) fglrx(0): [drm] mapped SAREA 0x2000 to 0x2ba6f9335000
(II) fglrx(0): [drm] framebuffer handle = 0x3000
(II) fglrx(0): [drm] added 1 reserved context for kernel
(II) fglrx(0): DRIScreenInit done
(II) fglrx(0): Kernel Module Version Information:
(II) fglrx(0): Name: fglrx
(II) fglrx(0): Version: 8.25.18
(II) fglrx(0): Date: May 18 2006
(II) fglrx(0): Desc: ATI FireGL DRM kernel module
(II) fglrx(0): Kernel Module version matches driver.
(II) fglrx(0): Kernel Module Build Time Information:
(II) fglrx(0): Build-Kernel UTS_RELEASE: 2.6.16-gentoo-r7
(II) fglrx(0): Build-Kernel MODVERSIONS: no
(II) fglrx(0): Build-Kernel __SMP__: no
(II) fglrx(0): Build-Kernel PAGE_SIZE: 0x1000
(II) fglrx(0): [drm] register handle = 0x00004000
(II) fglrx(0): [pcie] 65536 kB allocated with handle 0xdeadbeef
(II) fglrx(0): [drm] ringbuffer size = 0x00100000 bytes
(II) fglrx(0): [drm] DRM buffer queue setup: nbufs = 100 bufsize = 65536
(II) fglrx(0): [drm] texture shared area handle = 0x00008000
(II) fglrx(0): shared FSAAScale=1
(II) fglrx(0): DRI initialization successfull!
(II) fglrx(0): FBADPhys: 0xc0000000 FBMappedSize: 0x008f7000
(II) fglrx(0): FBMM initialized for area (0,0)-(1728,1360)
(II) fglrx(0): FBMM auto alloc for area (0,0)-(1728,1050) (front color buffer - assumption)
(==) fglrx(0): Backing store disabled
(==) fglrx(0): Silken mouse enabled
(II) fglrx(0): Using XFree86 Acceleration Architecture (XAA)
Screen to screen bit blits
Solid filled rectangles
8x8 mono pattern filled rectangles
Solid Lines
Dashed Lines
Offscreen Pixmaps
Setting up tile and stipple cache:
26 128x128 slots
(II) fglrx(0): Acceleration enabled
(II) fglrx(0): X context handle = 0x1
(II) fglrx(0): [DRI] installation complete
(II) fglrx(0): Direct rendering enabled
(==) fglrx(0): Using hardware cursor
(II) fglrx(0): Largest offscreen area available: 1728 x 304
*** If unresolved symbols were reported above, they might not
*** be the reason for the server aborting.
Backtrace:
0: X(xf86SigHandler+0x94) [0x4789b4]
1: /lib/libc.so.6 [0x2ba6f6c43840]
2: /lib/libc.so.6(strlen+0x55) [0x2ba6f6c844d5]
3: X(xf86XVScreenInit+0x81f) [0x4892ff]
4: /usr/lib64/xorg/modules/drivers/fglrx_drv.so(KaleidoscopeInitVideo+0x8a) [0x2ba6f7c7a3ca]
5: /usr/lib64/xorg/modules/drivers/fglrx_drv.so(R200ScreenInit+0xc51) [0x2ba6f7c4dec1]
6: X(AddScreen+0x1fe) [0x432f4e]
7: X(InitOutput+0x218) [0x4619d8]
8: X(main+0x293) [0x432893]
9: /lib/libc.so.6(__libc_start_main+0xf6) [0x2ba6f6c31136]
10: X(FontFileCompleteXLFD+0xa1) [0x432059]
Fatal server error:
Caught signal 11. Server aborting
[/code]
_________________
----------------------------------------------------------
JabberID: Jabberwocky AT amessage.de
GPG-Key: http://www.cryss.net/pubkey.gpg.asc
----------------------------------------------------------
Last edited by Cryssli on Thu May 25, 2006 1:14 pm; edited 3 times in total |
|
| Back to top |
|
|
Skrot
Tux's lil' helper
Joined: 06 Oct 2003
Posts: 141
Location: Adelaide, Australia
|
| Posted: Thu May 25, 2006 12:04 pm Post subject: |
|
|
My girlfriend has a 9600Pro in her computer, and these drivers seem much better! The system feels far more solid than it did with the old drivers.
I'm still having strange lag with my SDL/OpenGL thingy I'm working on. I'm guessing it's got to do with the vertex buffer objects, but who knows. I haven't tried to debug that yet.
Doom 3 seems to work pretty nicely! Similar sort of FPS to my 5900XT. Looking forward to future ATI driver releases
_________________
You will release your mind. |
|
| Back to top |
|
|
bandreabis
Advocate
Joined: 18 Feb 2005
Posts: 2490
Location: イタリアのロディで
|
| Posted: Thu May 25, 2006 7:36 pm Post subject: |
|
|
NO! Drivers horrible with my Radeon 200M
Andrea
_________________
Il numero di post non fa di me un esperto! Anzi! |
|
| Back to top |
|
|
rang3r
n00b
Joined: 09 Jun 2004
Posts: 25
|
| Posted: Thu May 25, 2006 8:20 pm Post subject: |
|
|
With my X600 these drivers give about 20+ more FPS over the previous version. This version seems to be much more stable overall.
_________________
rang3r |
|
| Back to top |
|
|
justus
n00b
Joined: 16 Apr 2002
Posts: 48
|
| Posted: Thu May 25, 2006 11:14 pm Post subject: Try this... |
|
|
| Cryssli wrote: | Hi,
still black screen when starting X. Maybe the backtrace at the end of Xorg.0.log is helpful for somebody who can 'read' it.
|
If you try editing your /etc/X11/xorg.conf to include the following, then you should be able to start up X without problems (well except the missing XVideo... but at least it will start.)
| Code: |
SubSection "extmod"
Option "omit XVideo"
EndSubSection
|
If it still doesn't work (or you get a black screen and can see some strange white lines when moving the mouse) then you can also try adding a:
| Code: | | Option "no_accel" "no" |
to your graphic cards device section (by the Driver "fglrx").
Hope that helps out! |
|
| Back to top |
|
|
Flintz
n00b
Joined: 29 Sep 2004
Posts: 48
|
| Posted: Fri May 26, 2006 12:03 am Post subject: |
|
|
I got the drivers installed, but somehow they're not working correctly. Xorg starts and 3D acceleration works completely, XV output however doesn't work. As soon as I start any mediaplayer (mplayer, gxine, totem ....) Xorg crashes with some weird references to /usr/lib64/modules/drivers/fglrx_drv.so
anyone else has this problem? |
|
| Back to top |
|
|
widremann
Veteran
Joined: 14 Mar 2005
Posts: 1314
|
| Posted: Fri May 26, 2006 12:15 am Post subject: |
|
|
They finally support 7.0, but I just upgraded to 7.1, so the drivers don't work  . I may downgrade just to see how things are. Has anybody tried these drivers with composite? |
|
| Back to top |
|
|
paszczi
Tux's lil' helper
Joined: 23 Sep 2005
Posts: 117
Location: Poznan, Poland
|
| Posted: Fri May 26, 2006 7:37 am Post subject: |
|
|
| I must admit that they indeed work more stable. |
|
| Back to top |
|
|
anz
Apprentice
Joined: 05 Feb 2003
Posts: 279
Location: Vienna
|
| Posted: Fri May 26, 2006 8:35 am Post subject: |
|
|
I have updated the ati-drivers on a S270 (sempron 3000+, ATI radeon XPRESS 200M) with xorg-x11-6.8.2-r7.
fglrx is working,
but whenever I login, f.e. su - in konsole or bash when X server is NOT running,
I get following message:
| Code: | | -bash: [: :/usr/lib//modules.dri:/usr/X11R6/lib/modules/dri/: unary operator expected |
modprobe fglrx works without any errors ...
This message did not appear under ati-drivers-8.24.8
--- update start ---
after a shut down/restarting (not a reboot), the message above has gone ... 
--- update end ---
... but I am very glad, that fglrx is working s t a b l e ... and it seems to be faster (fgl_glxgears: 135 fps instead of 110 fps)
What I 've never got working is hibernate under kde:
i have to enlarge pageset with a
| Code: | | ProcSetting extra_pages_allowance 5000 |
in the /etc/hibernate/hibernate.conf. Without that, the pagset is too small for hibernating under kde and the system reboots (without kde freeze).
With that change, hibernating shuts down the computer,
but the system freezes after starting kde
... but this is another story ...
_________________
Greetings from Vienna
Last edited by anz on Fri May 26, 2006 12:41 pm; edited 3 times in total |
|
| Back to top |
|
|
rncwnd
n00b
Joined: 13 Jun 2003
Posts: 69
Location: Germany
|
| Posted: Fri May 26, 2006 10:14 am Post subject: |
|
|
Sadly there is still no xorg 7.0/7.1 support with these drivers:
| Code: | (II) LoadModule: "fglrx"
(II) Loading /usr/lib/xorg/modules/drivers/fglrx_drv.so
(II) Module fglrx: vendor="FireGL - ATI Technologies Inc."
compiled for 6.8.99.8, module version = 8.25.18
Module class: X.Org Video Driver
ABI class: X.Org Video Driver, version 0.7
(EE) module ABI major version (0) doesn't match the server's version (1)
(II) UnloadModule: "fglrx"
(II) Unloading /usr/lib/xorg/modules/drivers/fglrx_drv.so
(EE) Failed to load module "fglrx" (module requirement mismatch, 0) |
|
|
| Back to top |
|
|
happen
n00b
Joined: 16 Aug 2004
Posts: 14
Location: Germany
|
| Posted: Fri May 26, 2006 10:44 am Post subject: |
|
|
i did an emerge --sync today but still an emerge ati-drivers -pv gives me
| Code: |
Calculating dependencies ...done!
[ebuild R ] x11-drivers/ati-drivers-8.24.8 +opengl 0 kB
Total size of downloads: 0 kB
|
How do i tell emerge to install the new drivers?
Thanks! |
|
| Back to top |
|
|
happen
n00b
Joined: 16 Aug 2004
Posts: 14
Location: Germany
|
| Posted: Fri May 26, 2006 11:09 am Post subject: |
|
|
Ok got it:
| Code: |
nano /etc/portage/package.keywords
|
| Code: |
x11-driver/ati-drivers ~x86
~x11-drivers/ati-drivers-8.25.18 -*
|
| Code: |
emerge =ati-drivers-8.25.18
|
that did it for me |
|
| Back to top |
|
|
Snoozz
Tux's lil' helper
Joined: 01 Feb 2006
Posts: 76
|
| Posted: Fri May 26, 2006 1:33 pm Post subject: |
|
|
I can't get the new driver running without begin root :s:s:s:s
Everything is OK, fglrx loaded, dmesg looks perfect.
But still I only get DRI when root (I tried everything, I changed the modes of dri, I added Group "video", etc...)
The 8.24.8 version works perfect when beging a user, the 8.25.18 doesn't :'(
I als get this message when going form root to user (aka su - <user name>)
bash: [: :/usr/lib//modules.dri:/usr/X11R6/lib/modules/dri/: unary operator expected |
|
| Back to top |
|
|
Cryssli
Apprentice
Joined: 16 Sep 2003
Posts: 213
Location: Regensburg - Germany
|
| Posted: Fri May 26, 2006 4:35 pm Post subject: |
|
|
Works for me (see xv workaround some posts above).
Thank you VERY MUCH!!
Well, whats the problem with xv?
What is xv, at all?
Chris
_________________
----------------------------------------------------------
JabberID: Jabberwocky AT amessage.de
GPG-Key: http://www.cryss.net/pubkey.gpg.asc
---------------------------------------------------------- |
|
| Back to top |
|
|
yinkoshaumer
Tux's lil' helper
Joined: 25 Oct 2005
Posts: 139
|
| Posted: Fri May 26, 2006 7:55 pm Post subject: |
|
|
the checksums seem to fail for me at the pci_name.patch
| Code: | >>> checking ebuild checksums ;-)
>>> checking auxfile checksums
!!! Digest verification failed:
!!! /usr/portage/x11-drivers/ati-drivers/files/fglrx-2.6.12-pci_name.patch
!!! Reason: Failed on SHA256 verification
!!! Got: 8dc2a7d9cdf449fd040ed9bb6b7f891f3885cf33a35a39e858b8072eb505f67a
!!! Expected: 80300e0810a35f42e6d1323c6aef1cd1a4d6c40ebf8d508269c5d06f3cc79817 |
I've cleared out the file listed above and grabbed it from another sync i did on my laptop. Still the same issue. Any thoughts?
Thanks,
Yinko |
|
| Back to top |
|
|
zietbukuel
l33t
Joined: 30 Dec 2005
Posts: 607
|
| Posted: Fri May 26, 2006 8:34 pm Post subject: |
|
|
| They are garbage... I have 600 less fps using glxgears, I know that is not a benchmark utility but I seems everything is slower with these drivers... (I'm using XGL) |
|
| Back to top |
|
|
zietbukuel
l33t
Joined: 30 Dec 2005
Posts: 607
|
| Posted: Fri May 26, 2006 8:35 pm Post subject: |
|
|
| yinkoshaumer wrote: | the checksums seem to fail for me at the pci_name.patch
| Code: | >>> checking ebuild checksums ;-)
>>> checking auxfile checksums
!!! Digest verification failed:
!!! /usr/portage/x11-drivers/ati-drivers/files/fglrx-2.6.12-pci_name.patch
!!! Reason: Failed on SHA256 verification
!!! Got: 8dc2a7d9cdf449fd040ed9bb6b7f891f3885cf33a35a39e858b8072eb505f67a
!!! Expected: 80300e0810a35f42e6d1323c6aef1cd1a4d6c40ebf8d508269c5d06f3cc79817 |
I've cleared out the file listed above and grabbed it from another sync i did on my laptop. Still the same issue. Any thoughts?
Thanks,
Yinko |
emerge --digest =ati-drivers-8.25.18 |
|
| Back to top |
|
|
yinkoshaumer
Tux's lil' helper
Joined: 25 Oct 2005
Posts: 139
|
| Posted: Fri May 26, 2006 9:27 pm Post subject: |
|
|
Thanks, that fixed it. I also noticed a drop in fps in glxgears (about 60).
Thanks again,
Yinko |
|
| Back to top |
|
|
Cryssli
Apprentice
Joined: 16 Sep 2003
Posts: 213
Location: Regensburg - Germany
|
| Posted: Sat May 27, 2006 8:31 am Post subject: |
|
|
glx_gears tells me about 2200 fps (Radeon X1800XT 512MB). Is this ok?
_________________
----------------------------------------------------------
JabberID: Jabberwocky AT amessage.de
GPG-Key: http://www.cryss.net/pubkey.gpg.asc
---------------------------------------------------------- |
|
| Back to top |
|
|
spielc
Guru
Joined: 20 Apr 2004
Posts: 452
|
| Posted: Sat May 27, 2006 10:30 am Post subject: |
|
|
| Cryssli wrote: | | glx_gears tells me about 2200 fps (Radeon X1800XT 512MB). Is this ok? |
Seems a bit low to me: I get 3182.633 FPS (still nothing spectacular but okey...) with two Firefox-Windows and Thunderbird open on my X1600Pro/512 MB vidram...
I hope they fix this problem soon... |
|
| Back to top |
|
|
Flintz
n00b
Joined: 29 Sep 2004
Posts: 48
|
| Posted: Sat May 27, 2006 11:11 am Post subject: |
|
|
guys, please stop using glxgears as a reference for performance. The only thing you can say from glxgears is whether 3d acceleration is generally working or not.
I have a X1300 Pro and get over 3300 fps, which is clearly not possible against your cards 
Use any real-world application such as DOOM3 demo oder UT2004 demo for benchmarking (I think both have an integrated benchmark option)
Sadly I had to downgrad to 8.24.8 because of my XV problems |
|
| Back to top |
|
|
spielc
Guru
Joined: 20 Apr 2004
Posts: 452
|
| Posted: Sat May 27, 2006 11:19 am Post subject: |
|
|
| Flintz wrote: | guys, please stop using glxgears as a reference for performance. The only thing you can say from glxgears is whether 3d acceleration is generally working or not.
I have a X1300 Pro and get over 3300 fps, which is clearly not possible against your cards
Use any real-world application such as DOOM3 demo oder UT2004 demo for benchmarking (I think both have an integrated benchmark option)
Sadly I had to downgrad to 8.24.8 because of my XV problems |
I would if i would be able to run games but without XV it doesn't seem to be possible... (e.g. if i want to run Quake 3 i have a small centered window with the game itself and the rest of the screen is black border... i don't think that this would get umm reasonable results Btw. Quake 3 worked great with my old 9600 Pro but since i've build in my X 1600 Pro it's behaving weird so i guess it's connected to missing XV)
But another question: XV works for you with the old driver?!??! |
|
| Back to top |
|
|
adrin
n00b
Joined: 27 May 2006
Posts: 41
|
| Posted: Sat May 27, 2006 11:29 am Post subject: |
|
|
those new drivers dont work for me... module loads, Xorg starts, but when i run any opengl program or fglrxinfo i receive a lot of fglrx API errors... so unfortunately i had to return to 8.24
_________________
*a* |
|
| Back to top |
|
|
Flintz
n00b
Joined: 29 Sep 2004
Posts: 48
|
| Posted: Sat May 27, 2006 2:26 pm Post subject: |
|
|
| @spielc: yes, XV works with 8.24.8, not flawless ( I cannot open any tv-program) but it works, xvinfo and fglrxinfo both show correct information and mplayer, gxine etc. work with XV output. |
|
| Back to top |
|
|
|
Desktop Environments
