View Full Version : ATI fglrx 8.31.5 Display Drivers
Michael
11-15-2006, 12:55 PM
No new features are in this release, but there is a chunk of resolved issues:
# Setting the display resolution to 400x300 or less no longer results in the mouse pointer not being able to move across the entire desktop. Further details can be found in topic number 733-23732
# The graphics driver no longer hangs the system shortly after the X Server is started on Red Hat enterprise Linux 3 system running Uniprocessor kernels. Further details can be found in topic number 733-23731
# Playing a media file under any distribution with X Server 6.9 or greater no longer results in a brief pause or video tearing when resizing the video window or running the mouse pointer over the video player window. Further details can be found in topic number 733-23730
# Using aticonfig to set the TV format to PAL-COMB-N no longer fails to update the X Server configuration file. Further details can be found in topic number 733-23729
Release Notes: https://a248.e.akamai.net/f/674/9206/0/www2.ati.com/drivers/linux/linux_8.31.5.html (Note they are now the AMD Proprietary Display Drivers)
Phoronix Review: http://www.phoronix.com/vr.php?view=7876
crash_override
11-16-2006, 07:11 AM
Hi, I'm aThinkpad T60 user;
I've succesfullyy installed 8.29.6 drivers with you script on my FC6;
Now I'm trying to update to 8.31.5 but I receive some errors.
Which is the way do you used to install this driver on T60?
Thanks
Crash_Override
Linux Registered User #353811
---------------------------------
" I Shall Be Free "
The Freewheelin' Bob Dylan, 1963
Michael
11-16-2006, 07:44 AM
I just use ./ati-831-driver-name.run --buildpkg Fedora/FC6
What errors are you running into?
crash_override
11-16-2006, 08:56 AM
Hi,
with ./ati-831-driver-name.run --buildpkg Fedora/FC6 I've built rpms.
After I've installed *.rpm without errors.
I've rebooted the pc, then I've run aticonfig --initial without errors; but direct rendering is disabled.
[root@hal9000 X11]# fglrxinfo
Xlib: extension "XFree86-DRI" missing on display ":0.0".
display: :0.0 screen: 0
OpenGL vendor string: Mesa project: www.mesa3d.org
OpenGL renderer string: Mesa GLX Indirect
OpenGL version string: 1.2 (1.5 Mesa 6.5.1)
this is my xorg.conf
# Xorg configuration created by system-config-display
Section "ServerLayout"
Identifier "Default Layout"
Screen 0 "aticonfig-Screen[0]" 0 0
InputDevice "Keyboard0" "CoreKeyboard"
EndSection
Section "Files"
EndSection
Section "Module"
Load "glx"
Load "dri"
EndSection
Section "InputDevice"
Identifier "Keyboard0"
Driver "kbd"
Option "XkbModel" "pc105"
Option "XkbLayout" "it"
EndSection
Section "Monitor"
Identifier "aticonfig-Monitor[0]"
Option "VendorName" "ATI Proprietary Driver"
Option "ModelName" "Generic Autodetecting Monitor"
Option "DPMS" "true"
EndSection
Section "Device"
Identifier "Videocard0"
Driver "vesa"
EndSection
Section "Device"
Identifier "aticonfig-Device[0]"
Driver "fglrx"
EndSection
Section "Screen"
Identifier "Screen0"
Device "Videocard0"
DefaultDepth 24
SubSection "Display"
Viewport 0 0
Depth 24
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
Michael
11-16-2006, 09:04 AM
What errors are in your Xorg.0.log?
I have no problems with the T60 and the 8.31 drivers.
crash_override
11-16-2006, 09:14 AM
this is my log
http://www.difficile.it/xorg.0.log.txt
Michael
11-16-2006, 09:23 AM
Oops I just noticed from your above xorg.conf that it doesn't look like Composite is disabled. Here is a working conf from a T60.
Section "ServerLayout"
Identifier "Default Layout"
Screen 0 "aticonfig-Screen[0]" 0 0
InputDevice "Keyboard0" "CoreKeyboard"
InputDevice "Synaptics" "CorePointer"
EndSection
Section "Files"
EndSection
Section "Module"
Load "dbe"
Load "v4l"
Load "extmod"
Load "type1"
Load "freetype"
Load "dri"
Load "glx"
EndSection
Section "InputDevice"
Identifier "Keyboard0"
Driver "kbd"
Option "XkbModel" "pc105"
Option "XkbLayout" "us"
EndSection
Section "InputDevice"
Identifier "Synaptics"
Driver "synaptics"
Option "Device" "/dev/input/mice"
Option "Protocol" "auto-dev"
Option "Emulate3Buttons" "yes"
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"
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 "Extensions"
Option "Composite" "disable"
EndSection
crash_override
11-16-2006, 09:31 AM
But with
Section "Extensions"
Option "Composite" "disable"
EndSection
I can't run AIGLX...It's true?
Michael
11-16-2006, 09:44 AM
The fglrx drivers do not support AIGLX.
crash_override
11-16-2006, 09:49 AM
:eek:
oh no..... I've tryed with DRI drivers, but (I dont knw why) I can't build them; only may I hope for support in future releases....
Thank you very much for help.
Michael
11-16-2006, 09:51 AM
So is your drivers working with Composite disabled?
AIGLX support will eventually come, it's just a matter of when. non-X1000 users are able to use the open-source Radeon drivers for support.
crash_override
11-16-2006, 10:12 AM
No... I've disabled composite extension, then rebooted but the result is the same...
this is the new log http://www.difficile.it/Xorg.0.log
foxtseng
11-16-2006, 03:39 PM
Could anyone give me a hint that how can I download a 8.31.5 ati driver? What I can only find on ATI official website is the old 8.29.6 Thanks!
Michael
11-16-2006, 03:48 PM
ATI.com has 8.31.5 listed...
https://a248.e.akamai.net/f/674/9206/0/www2.ati.com/drivers/linux/ati-driver-installer-8.31.5-x86.x86_64.run
foxtseng
11-16-2006, 03:58 PM
ATI.com has 8.31.5 listed...
https://a248.e.akamai.net/f/674/9206/0/www2.ati.com/drivers/linux/ati-driver-installer-8.31.5-x86.x86_64.run
Thank you Michael! It should be a 32-bit and 64-bit compatible bin code, right? I could not find any news about 8.31.5 on http://ati.amd.com
Is that the ati's official website? I am just a little bit confused, since seems everyone here can find it and I am in another world...
Michael
11-16-2006, 04:00 PM
Yes, works with both x86 and x86_64 architectures.
http://ati.amd.com/support/drivers/linux/linux-radeon.html Is the page, accessed from ati.com and clicking on drivers.
foxtseng
11-16-2006, 06:06 PM
Yes, works with both x86 and x86_64 architectures.
http://ati.amd.com/support/drivers/linux/linux-radeon.html Is the page, accessed from ati.com and clicking on drivers.
Ah, I see. Because my card is a mobility and the demo is a mobility. And the driver for mobilities on the site is not updated. =.=
But I still cannot compile the control panel, it complaints that cannot find my qt-3.3 lib files, which has been installed.
Current release is FC6. Maybe it would be helpful to reinstall a clean system, or try some other release instead of fc6?
Details was posted here,
http://phoronix.net/forums/showthread.php?t=375
Michael
11-16-2006, 06:14 PM
See http://phoronix.net/forums/showthread.php?t=318 for fireglcontrolpanel build problems on FC6.
FrogPR
11-17-2006, 03:02 AM
Well, subject says it all. Suspend-to-RAM was working fine with the 8.30.3 drivers but now it stopped working on my mobility radeon X700 :mad:
I don't really know what introduced the bug but I'm getting even more angry with the ATI... erm ... AMD support. They seem to focus on bugs nobody cares about (resolutions of 400x300 or even less???) and apparently accidently remove feature that were once supported. Ok, I cannot really complain as the new drviers seem to be meant for non-mobile users only (for the mobility display drivers, they still point you to 8.29.6 while the non-mobility drivers have been updated)
As I'm not a big gamer, i'm not really interested in 3D performance, even though it's probably the most important thing. What is far more important to me is the POWERplay support that was only implemented partially in the linux drivers. The power you save is ridiculously small compared to windows. I took a power meter and noticed that under windows you save almost 7 watt, while under linux you're struggeling to save 2 watts. This does not only mean a highly reduced batgtery life but also a noisy laptop. Checking Xorg.0.log reveals, that POWERplay 3 is supported, a years-old technology. My X700 (also at least 1 year old alreaedy) has 5.0 as far as I know...
Anyway, I think ATI or AMD or whatever has to make up with its linux customers. Right know, I would not consider to buy a laptop with a radeom card again... Intel and NVIDIAs drivers are leaps ahead...
Let's hope for better drivers in the future...
afterburntdw
11-17-2006, 09:25 AM
To FrogPR:
Definitely feel your pain. ATI drivers are a joke compared to the support from Nvidia. If I had it to do over again, I would definitely get an Nvidia. Truth be told, I'm thinking about selling my ATI. I only got it because the ASUS P5W DH has Crossfire support. But getting that to work in Linux....I don't think I even want to try.
Michael
11-17-2006, 09:29 AM
I only got it because the ASUS P5W DH has Crossfire support. But getting that to work in Linux....I don't think I even want to try.
The fglrx drivers do not support CrossFire nor will they anytime in the near future.
afterburntdw
11-17-2006, 12:15 PM
Thank you for that information. It helps me to make my decision about video cards.
Just out of curiosity, where do you find the detailed information about the changes in each driver release?
presdec
11-18-2006, 11:36 AM
I firstly installed the drivers from livna through yum with no problems, it was not untill i ran ATI Control that i realized i was still using MESA, i googled my problem and came across your instructions. I followeed them to the letter but no matter what i did it always failed. THe most recent problem was the firecontrol. odly enough without knowing what exactly it was i did that fixed it that is know gone and the ATI control panel works fine detecting my ATI Radeon 9600 without problems but the Vendor for the driver is still Mesa 1.2(1.5 Mesa 6.5.1)
fglrxinfo give me the following
Xlib: extension "XFree86-DRI" missing on display ":0.0".
display: :0.0 screen: 0
OpenGL vendor string: Mesa project: www.mesa3d.org
OpenGL renderer string: Mesa GLX Indirect
OpenGL version string: 1.2 (1.5 Mesa 6.5.1)
My Xorg reads as follows
# Xorg configuration created by system-config-display
Section "ServerLayout"
Identifier "single head configuration"
Screen 0 "Screen0" 0 0
InputDevice "Keyboard0" "CoreKeyboard"
InputDevice "Synaptics" "CorePointer"
EndSection
Section "InputDevice"
Identifier "Keyboard0"
Driver "kbd"
Option "XkbModel" "pc105"
Option "XkbLayout" "us"
EndSection
Section "InputDevice"
Identifier "Synaptics"
Driver "synaptics"
Option "Device" "/dev/input/mice"
Option "Protocol" "auto-dev"
Option "Emulate3Buttons" "yes"
EndSection
Section "Monitor"
Identifier "Monitor0"
ModelName "LCD Panel 1600x1200"
### Comment all HorizSync and VertSync values to use DDC:
HorizSync 31.5 - 90.0
VertRefresh 59.9 - 60.1
Option "dpms"
EndSection
Section "Device"
Identifier "Videocard0"
Driver "fglrx"
EndSection
Section "Screen"
Identifier "Screen0"
Device "Videocard0"
Monitor "Monitor0"
DefaultDepth 24
SubSection "Display"
Viewport 0 0
Depth 24
Modes "1400x1050" "1280x1024" "1280x960" "1280x800" "1152x864" "1024x768" "800x600" "640x480"
EndSubSection
EndSection
Section "Extensions"
Option "Composite" "Disable"
EndSection
Is there a way of completely uninstalling the fglrx drivers from yum and also the onse i installed from your instructions under the hope that a fresh start might work better? Or a way to remove mesa or at least pass over control to ATI instead of MESA?
I've already looked through the various posts and have found none of the sollutions to suit me.
Any ideas would be much apreciated.
philip@gmail.com
Michael
11-18-2006, 01:13 PM
yum remove <package names> is able to uninstall the RPMs for you. After that try to run the installer manually.
Does your X log show any relevant information to this problem?
presdec
11-18-2006, 01:31 PM
(II) LoadModule: "GLcore"
(II) Loading /usr/lib/xorg/modules/extensions/libGLcore.so
(II) Module GLcore: vendor="X.Org Foundation"
compiled for 7.1.1, module version = 1.0.0
ABI class: X.Org Server Extension, version 0.3
(II) GLX: Initialized MESA-PROXY GL provider for screen 0
presdec
11-18-2006, 01:32 PM
(II) fglrx(0): driver needs X.org 7.1.x.y with x.y >= 0.0
(II) fglrx(0): detected X.org 7.1.1.0
(II) Loading extension ATIFGLRXDRI
(II) fglrx(0): doing DRIScreenInit
drmOpenDevice: node name is /dev/dri/card0
drmOpenDevice: open result is 7, (OK)
drmOpenDevice: node name is /dev/dri/card0
drmOpenDevice: open result is 7, (OK)
drmOpenByBusid: Searching for BusID PCI:1:0:0
drmOpenDevice: node name is /dev/dri/card0
drmOpenDevice: open result is 7, (OK)
drmOpenByBusid: drmOpenMinor returns 7
drmOpenByBusid: drmGetBusid reports
drmOpenDevice: node name is /dev/dri/card1
drmOpenDevice: open result is -1, (No such device)
drmOpenDevice: open result is -1, (No such device)
drmOpenDevice: Open failed
presdec
11-18-2006, 01:36 PM
hope these help...
Michael
11-18-2006, 01:43 PM
Were there any errors? (EE)
presdec
11-18-2006, 03:47 PM
(EE) AIGLX error: dlsym for __driCreateNewScreen_20050727 failed (/usr/lib/dri/fglrx_dri.so: undefined symbol: __driCreateNewScreen_20050727)
(EE) AIGLX: reverting to software rendering
also
(WW) warning, (EE) error, (NI) not implemented, (??) unknown.
glussier
11-18-2006, 07:26 PM
(EE) AIGLX error: dlsym for __driCreateNewScreen_20050727 failed (/usr/lib/dri/fglrx_dri.so: undefined symbol: __driCreateNewScreen_20050727)
(EE) AIGLX: reverting to software rendering
also
(WW) warning, (EE) error, (NI) not implemented, (??) unknown.
Add the following in /etc/X11/xorg.conf:
Section "ServerFlags"
Option "AIGLX" "off"
EndSection
presdec
11-18-2006, 11:56 PM
Did not work. Ati control centre reports the same MESA and fglrxinfo now gives
ERROR: DDX driver fingerprint mismatch: got 0x7A3E2CF0, but expected 0x84220BA7
libGL error: InitDriver failed
presdec
11-19-2006, 01:22 AM
Got it working by uninstalling the preexisting yum version. Then installing the ATI drivers from ATI (8.31.5). At this point i had the firecontrol problem so i installed via yum the kmod and xorg fgrlx did a aticonfig --initial and everythings dandy. Thank you Michael for your time and patience. And many thanks to all!
niniendowarrior
11-24-2006, 10:23 PM
Just updated to 8.31... and I lost all my 3D acceleration. Just great. Not only that... my root account seems suddenly haywired now... okay, minor glitches... it's gone now but still no 3d acceleration. Way to go AMD.
Michael
11-24-2006, 10:32 PM
What's your Xorg.0.log show? Did your xorg.conf by chance get altered?
niniendowarrior
11-24-2006, 10:33 PM
Okay... I'll calm down.
I'm going to post my logs in a sec.
niniendowarrior
11-24-2006, 10:47 PM
Michael, we could use a file attachment instead of posting log files like this.
Xorg.0.log
X Window System Version 6.8.2
Release Date: 9 February 2005
X Protocol Version 11, Revision 0, Release 6.8.2
Build Operating System: Linux 2.4.21-27.0.2.ELsmp i686 [ELF]
Current Operating System: Linux gaimcube.niniendoworld 2.6.11-1.1369_FC4smp #1 SMP Thu Jun 2 23:08:39 EDT 2005 i686
Build Date: 13 May 2005
Build Host: decompose.build.redhat.com
<snip>
MOBILITY RADEON X1700 (M66-P 71D5), RADEON Xpress 1200 (RS600 7941),
RADEON Xpress 1200 (RS600 7942)
(II) Primary Device is: PCI 01:00:0
(II) ATI Proprietary Linux Driver Version Identifier:8.31.5
(II) ATI Proprietary Linux Driver Release Identifier: LGDr8.31g1
(II) ATI Proprietary Linux Driver Build Date: Nov 9 2006 18:34:57
(II) ATI Proprietary Linux Driver Build Information: autobuild-rel-r6-8.31.2.1.2.3-driver-lnx-x86-x86_64-305837
(WW) fglrx: No matching Device section for instance (BusID PCI:1:0:1) found
(--) Chipset RADEON X800 PRO (R420 4A49) found
(II) resource ranges after xf86ClaimFixedResources() call:
[0] -1 0 0xffe00000 - 0xffffffff (0x200000) MX[B](B)
[1] -1 0 0x00100000 - 0x3fffffff (0x3ff00000) MX[B]E(B)
<snip>
(II) Setting vga for screen 0.
(II) fglrx(0): === [atiddxPreInit] === begin, [s]
<snip>
(**) fglrx(0): Gamma Correction for I is 0x06419064
(**) fglrx(0): Gamma Correction for II is 0x06419064
(==) fglrx(0): Buffer Tiling is ON
(II) Loading sub module "int10"
(II) LoadModule: "int10"
(II) Loading /usr/X11R6/lib/modules/linux/libint10.a
(II) Module int10: vendor="X.Org Foundation"
compiled for 6.8.2, module version = 1.0.0
ABI class: X.Org Video Driver, version 0.7
(II) fglrx(0): Primary V_BIOS segment is: 0xc000
(**) fglrx(0): Option "mtrr" "off"
(--) fglrx(0): Chipset: "RADEON X800 PRO (R420 4A49)" (Chipset = 0x4a49)
(--) fglrx(0): (PciSubVendor = 0x1002, PciSubDevice = 0x0002)
(--) fglrx(0): board vendor info: original ATI graphics adapter
(--) fglrx(0): Linear framebuffer (phys) at 0xe8000000
(--) fglrx(0): MMIO registers at 0xfe9f0000
(==) fglrx(0): ROM-BIOS at 0x000c0000
(II) Loading sub module "vbe"
(II) LoadModule: "vbe"
(II) Loading /usr/X11R6/lib/modules/libvbe.a
(II) Module vbe: vendor="X.Org Foundation"
compiled for 6.8.2, module version = 1.1.0
ABI class: X.Org Video Driver, version 0.7
(II) fglrx(0): VESA BIOS detected
(II) fglrx(0): VESA VBE Version 3.0
(II) fglrx(0): VESA VBE Total Mem: 16384 kB
<snip>
(II) Loading sub module "fglrxdrm"
(II) LoadModule: "fglrxdrm"
(II) Loading /usr/X11R6/lib/modules/linux/libfglrxdrm.a
(II) Module fglrxdrm: vendor="FireGL - ATI Technologies Inc."
compiled for 6.8.0, module version = 8.31.5
ABI class: X.Org Server Extension, version 0.2
(II) fglrx(0): ATI Video BIOS revision 9 or later detected
(--) fglrx(0): VideoRAM: 131072 kByte, Type: DDR3
(II) fglrx(0): AGP card detected
(II) fglrx(0): board/chipset is supported by this driver (original ATI board)
(II) Loading sub module "ddc"
(II) LoadModule: "ddc"
(II) Loading /usr/X11R6/lib/modules/libddc.a
(II) Module ddc: vendor="X.Org Foundation"
compiled for 6.8.2, module version = 1.0.0
ABI class: X.Org Video Driver, version 0.7
(II) fglrx(0): Connected Display1: CRT on primary DAC [crt1]
(II) fglrx(0): Display1 EDID data ---------------------------
(II) fglrx(0): Manufacturer: GSM Model: 4a4c Serial#: 16843009
(II) fglrx(0): Year: 2001 Week: 0
<snip>
(II) fglrx(0): 1280x1024@75Hz
(II) fglrx(0): 1152x870@75Hz
(II) fglrx(0): Manufacturer's mask: 0
(II) fglrx(0): Supported Future Video Modes:
(II) fglrx(0): #0: hsize: 640 vsize 480 refresh: 85 vid: 22833
(II) fglrx(0): #1: hsize: 800 vsize 600 refresh: 85 vid: 22853
(II) fglrx(0): #2: hsize: 1024 vsize 768 refresh: 85 vid: 22881
(II) fglrx(0): #3: hsize: 1280 vsize 1024 refresh: 85 vid: 39297
(II) fglrx(0): #4: hsize: 1600 vsize 1200 refresh: 75 vid: 20393
<snip>
(II) fglrx(0): Modeline "320x200" 13.10 320 352 368 416 200 406 407 417 doublescan
(**) fglrx(0): Default mode "320x200": 12.6 MHz (scaled from 0.0 MHz), 31.5 kHz, 60.0 Hz (D)
(II) fglrx(0): Modeline "320x200" 12.59 320 336 384 400 200 457 459 524 doublescan
(II) Loading sub module "fb"
(II) LoadModule: "fb"
(II) Loading /usr/X11R6/lib/modules/libfb.a
(II) Module fb: vendor="X.Org Foundation"
compiled for 6.8.2, module version = 1.0.0
ABI class: X.Org ANSI C Emulation, version 0.2
(II) Loading sub module "ramdac"
(II) LoadModule: "ramdac"
(II) Loading /usr/X11R6/lib/modules/libramdac.a
(II) Module ramdac: vendor="X.Org Foundation"
compiled for 6.8.2, module version = 0.1.0
ABI class: X.Org Video Driver, version 0.7
(**) fglrx(0): NoAccel = NO
(II) Loading sub module "xaa"
(II) LoadModule: "xaa"
(II) Loading /usr/X11R6/lib/modules/libxaa.a
(II) Module xaa: vendor="X.Org Foundation"
compiled for 6.8.2, module version = 1.2.0
ABI class: X.Org Video Driver, version 0.7
(==) fglrx(0): HPV inactive
(==) fglrx(0): FSAA enabled: NO
(**) fglrx(0): FSAA Gamma enabled
(**) fglrx(0): FSAA Multisample Position is fix
(**) fglrx(0): NoDRI = NO
(II) Loading sub module "fglrxdrm"
(II) LoadModule: "fglrxdrm"
(II) Reloading /usr/X11R6/lib/modules/linux/libfglrxdrm.a
(II) fglrx(0): Depth moves disabled by default
<snip>
(==) fglrx(0): EnablePrivateBackZ = NO
(--) Depth 24 pixmap format is 32 bpp
(II) do I need RAC? No, I don't.
(II) resource ranges after preInit:
[0] 0 0 0xfe9f0000 - 0xfe9fffff (0x10000) MX[B]
<snip>
(II) fglrx(0): UMM Bus area: 0xe8701000 (size=0x078ff000)
(II) fglrx(0): UMM area: 0xe0701000 (size=0x078ff000)
(II) fglrx(0): driver needs X.org 6.8.x.y with x.y >= 0.0
(II) fglrx(0): detected X.org 6.8.2.0
(II) Loading extension ATIFGLRXDRI
(II) fglrx(0): doing DRIScreenInit
drmOpenDevice: node name is /dev/dri/card0
drmOpenDevice: open result is 7, (OK)
drmOpenDevice: node name is /dev/dri/card0
drmOpenDevice: open result is 7, (OK)
drmOpenByBusid: Searching for BusID PCI:1:0:0
drmOpenDevice: node name is /dev/dri/card0
drmOpenDevice: open result is 7, (OK)
drmOpenByBusid: drmOpenMinor returns 7
drmOpenByBusid: drmGetBusid reports
drmOpenDevice: node name is /dev/dri/card1
drmOpenDevice: open result is -1, (No such device)
drmOpenDevice: open result is -1, (No such device)
drmOpenDevice: Open failed
<snip - redundant entries to different /dev/dri/cardX>
drmOpenByBusid: drmOpenMinor returns -1023
drmOpenDevice: node name is /dev/dri/card0
drmOpenDevice: open result is 7, (OK)
drmOpenDevice: node name is /dev/dri/card0
drmOpenDevice: open result is 7, (OK)
drmGetBusid returned ''
(II) fglrx(0): [drm] DRM interface version 1.0
(II) fglrx(0): [drm] created "fglrx" driver at busid "PCI:1:0:0"
(II) fglrx(0): [drm] added 8192 byte SAREA at 0x00002000
(II) fglrx(0): [drm] mapped SAREA 0x00002000 to 0xb7c24000
(II) fglrx(0): [drm] framebuffer handle = 0x00003000
(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.31.5
(II) fglrx(0): Date: Nov 9 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.11-1.1369_FC4smp
(II) fglrx(0): Build-Kernel MODVERSIONS: yes
(II) fglrx(0): Build-Kernel __SMP__: yes
(II) fglrx(0): Build-Kernel PAGE_SIZE: 0x1000
(II) fglrx(0): [drm] register handle = 0x00004000
(EE) fglrx(0): [agp] unable to acquire AGP, error "xf86_ENODEV"
(EE) fglrx(0): cannot init AGP
(II) fglrx(0): [drm] removed 1 reserved context for kernel
(II) fglrx(0): [drm] unmapping 8192 bytes of SAREA 0x00002000 at 0xb7c24000
(WW) fglrx(0): ***********************************************
(WW) fglrx(0): * DRI initialization failed! *
(WW) fglrx(0): * (maybe driver kernel module missing or bad) *
(WW) fglrx(0): * 2D acceleraton available (MMIO) *
(WW) fglrx(0): * no 3D acceleration available *
(WW) fglrx(0): ********************************************* *
(II) fglrx(0): FBADPhys: 0xe0000000 FBMappedSize: 0x08000000
(II) fglrx(0): FBMM initialized for area (0,0)-(1280,8191)
(II) fglrx(0): FBMM auto alloc for area (0,0)-(1280,1024) (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
Solid Horizontal and Vertical Lines
Offscreen Pixmaps
Setting up tile and stipple cache:
32 128x128 slots
32 256x256 slots
16 512x512 slots
(II) fglrx(0): Acceleration enabled
(II) fglrx(0): Direct rendering disabled
(==) fglrx(0): Using hardware cursor
(II) fglrx(0): Largest offscreen area available: 1280 x 7163
(**) fglrx(0): Video overlay enabled on CRTC1
(II) Loading extension FGLRXEXTENSION
(II) Loading extension ATITVOUT
(==) RandR enabled
Symbol atiddxVideoKaleidoscopeSetSync from module /usr/X11R6/lib/modules/drivers/fglrx_drv.o is unresolved!
<snip>
niniendowarrior
11-24-2006, 10:53 PM
I've tried to downgrade to 8.30.3. I'll see if I can get that one working instead.
Michael
11-24-2006, 10:54 PM
I don't actively use any AGP machines any longer, but did you encounter those two AGP related errors before with 8.30? I know some others had AGP problems with the 8.31 release so I don't know if it's related. Do you have (/tried altering) any AGP related options in your xorg.conf?
niniendowarrior
11-24-2006, 10:58 PM
The xorg.conf is from my previous driver. I didn't use 8.30.3 before... I think it may have been something like 8.25.
Is AMD cutting out AGP? By the way, 8.30.3 doesn't work too.
Michael
11-24-2006, 11:00 PM
What card are you using? If it's R200 series it was removed in driver 8.28.8.
Support for the Radeon 9500 to 9800 remain, along with any of the X series that has AGP versions, but anything up to and including the Radeon 9250 has been removed from the main development branch.
niniendowarrior
11-24-2006, 11:05 PM
Radeon X800 Pro.
I've downgraded to 8.25. My 3D acceleration is all lost. I regret ever having to have thought of installing this... this has caused me more problems that I've not asked for.
EDIT:
Now I can't find the uninstaller for this 8.25. Oh god, what have I done?
Michael
11-24-2006, 11:25 PM
What distribution are you using? If you aren't using distribution-specific packages, if you extract the driver installer found inside the fglrx-install directory should be something like a fglrx-uninstall.sh.
Have you considered using the open-source Radeon drivers or are you in it for performance.
niniendowarrior
11-24-2006, 11:25 PM
I've tried the Livna Yum rpms for 8.26. Nothing. *sigh* I think I'll go look for an R200 gpu next time.
EDIT:
I appreciate your effort Michael. Here's my specs:
Fedora Core 4.
ATi Radeon X800 Pro 256
P4 3.2 GHz.
Asus P4P800-E Deluxe.
1 GB RAM
Michael, I play on my Linux box. Remember Vdrift?
Michael
11-24-2006, 11:33 PM
Have you tried generating your own Fedora RPMs instead of using Livna? Or since you're using FC4, even if you run the graphical fglrx installer it should install fine for Stentz.
Michael, I play on my Linux box. Remember Vdrift?
Ah yes, wasn't sure if you had multiple Linux boxes or not :o
niniendowarrior
11-24-2006, 11:38 PM
I've used the graphical installer. The only packages I saw I could generate where RHEL so I didn't bother. It seems that the livna packages aren't very useful because even after running fglrx-uninstall on 8.25... the Xorg log still insists on using it.
Normally, I'd overlap driver installations of ATi cards and they didn't cause any problems. Now it seems that 8.31 has caused some problems and now I can't get anything right.
Michael
11-24-2006, 11:42 PM
I've used the graphical installer. The only packages I saw I could generate where RHEL so I didn't bother.
Package Maintainer(s): Niko Mirthes <nmirthes@gmail.com> and Michael Larabel <michael@phoronix.com>
Status: *UNVERIFIED*
Fedora Packages:
Fedora/FC3
Fedora/FC4
Fedora/FC5
Fedora/FC6
Fedora/RHEL3
Fedora/RHEL4
./ati-driver-installer-8.31.5-x86.x86_64.run --buildpkg Fedora/FC4 should generate the RPMs for you.
niniendowarrior
11-24-2006, 11:47 PM
I've generated the rpms.
I'm still concerned about remnants on 8.25. I'm going to remove the livna rpms now.
What do I get from installing the devel rpm? I'm going to install the control panel rpm and the driver.
niniendowarrior
11-24-2006, 11:55 PM
Hi Michael,
Your driver installed. No 3d acceleration just the same. If you need more info, tell me.
Michael
11-24-2006, 11:57 PM
The devel RPM provides glATI.h, glxATI.h, fglrx_gamma.h, libGL.so, and other library files.
Michael
11-24-2006, 11:58 PM
Hi Michael,
Your driver installed. No 3d acceleration just the same. If you need more info, tell me.
Are you able to post your xorg.conf?
niniendowarrior
11-24-2006, 11:59 PM
Do I need to install the devel rpms? Because I'm still getting nothing here. I'll just e-mail you my conf files because it's just a pain to post here.
Michael
11-25-2006, 12:00 AM
For the purpose of being complete, install all the RPMs. Yes, feel free to email the config files to me.
niniendowarrior
11-25-2006, 12:06 AM
No such luck, Michael. :( No 3d.
Michael
11-25-2006, 12:09 AM
Your problem looks to be due to AGP. Have you tried upgrading your kernel or rebuilding agpgart?
For a bit more detailed answer, see: http://www2.ati.com/drivers/linux/linux_8.12.10.html#175058
niniendowarrior
11-25-2006, 12:11 AM
This kernel is out of the box. Do you think I need to upgrade the kernel?
I'm checking yum right now... seems it's difficult to find one.
EDIT:
I did yum -y update kernel according to this site...
http://www.brandonhutchinson.com/Upgrading_Red_Hat_Linux_with_yum.html
And I lost my ethernet adapter. So now I'm back to my old kernel. Another day perhaps... or I'm contemplating on getting rid of Fedora and replacing it with something else.
Michael
11-25-2006, 09:24 AM
Have you considered upgrading to Fedora 6? Core 4 is getting pretty out of date these days for desktop usage -- GNOME 2.10, GCC 4.0, etc...
Your problem with updating the kernel might be as Fedora Core 4 is no longer supported by the Fedora Project. Core 4 is part of the Legacy project now, so you may have to enable that repo.
What is your network adapter?
niniendowarrior
11-25-2006, 12:29 PM
Are you serious? I've never had to upgrade my distributions. The changes here keep piling up.
If I attempt to upgrade to Fedora Core 6 by yum, that does not guarantee fixing my system. And... if I'm reinstalling, I'm thinking of going with Ubuntu. Do I have other options here or I'm just totally screwed? My 3d acceleration USED TO WORK until that blasted 8.31.8 ruined my driver.
Michael
11-25-2006, 12:41 PM
From what it sounds there might be a problem with your agpgart or the agp kernel module for your specific chipset, based upon the information available. You might be able to fix the issue by rebuilding your kernel.
niniendowarrior
11-26-2006, 02:25 AM
I'm thinking about doing that, Michael. Any thoughts on what kernel options you want specifically done for this build because I can't think of anything else I can do to fix this driver issue apart from reinstalling Fedora or just installing Ubuntu (and probably upgrade to Xubuntu).
By the way, the ethernet adapter is an sk98lin.
Michael
11-26-2006, 09:17 AM
I can't think of any extra options off hand to specify, but I don't deal with AGP much anymore.
exobg
12-04-2006, 06:24 PM
Hello, I've installed all generated packages by ati installer in my x86_64 FC6, but now seems to run into some problems (again :o ) Here they are:
glxinfo |grep rendering
Xlib: extension "XFree86-DRI" missing on display ":0.0".
direct rendering: No
Here's part of my xorg.0.log:
II) Loading extension X-Resource
(II) LoadModule: "glx"
(II) Loading /usr/lib64/xorg/modules/extensions/libglx.so
(II) Module glx: vendor="X.Org Foundation"
compiled for 7.1.1, module version = 1.0.0
ABI class: X.Org Server Extension, version 0.3
(==) AIGLX enabled
(II) Loading extension GLX
(II) LoadModule: "dri"
(II) Loading /usr/lib64/xorg/modules/extensions/libdri.so
(II) Module dri: vendor="X.Org Foundation"
compiled for 7.1.1, module version = 1.0.0
ABI class: X.Org Server Extension, version 0.3
(II) Loading sub module "drm"
(II) LoadModule: "drm"
(II) Loading /usr/lib64/xorg/modules/linux/libdrm.so
(II) Module drm: vendor="X.Org Foundation"
compiled for 7.1.1, module version = 1.0.0
ABI class: X.Org Server Extension, version 0.3
(II) Loading extension XFree86-DRI
(II) LoadModule: "fglrx"
(II) Loading /usr/lib64/xorg/modules/drivers/fglrx_drv.so
(II) Module fglrx: vendor="FireGL - ATI Technologies Inc."
compiled for 7.1.0, module version = 8.31.5
Module class: X.Org Video Driver
ABI class: X.Org Video Driver, version 1.0
...
(II) fglrx(0): Composite extension enabled, disabling direct rendering
(WW) fglrx(0): ***********************************************
(WW) fglrx(0): * DRI initialization failed! *
(WW) fglrx(0): * (maybe driver kernel module missing or bad) *
(WW) fglrx(0): * 2D acceleraton available (MMIO) *
(WW) fglrx(0): * no 3D acceleration available *
(WW) fglrx(0): ********************************************* *
If I try to run something that requires 3D it is either say "Warring Frame Rate Very low (2 to 3 fps)" or simply get "No 3D support" or something like that. IN the end it doesn't work like it should.
What could be the problem ... ?
Michael
12-04-2006, 06:30 PM
Hmm... Can you post your xorg.conf? I see no errors in that section of the X log.
exobg
12-04-2006, 06:43 PM
Section "ServerLayout"
Identifier "Layout[all]"
Screen "Screen[0]" 0 0
InputDevice "Keyboard[0]" "CoreKeyboard"
InputDevice "Mouse[1]" "CorePointer"
Option "Clone" "off"
Option "Xinerama" "off"
EndSection
Section "Files"
EndSection
Section "Module"
Load "dbe"
Load "type1"
Load "freetype"
Load "extmod"
Load "glx"
Load "dri"
EndSection
Section "ServerFlags"
Option "AllowMouseOpenFail"
EndSection
Section "InputDevice"
Identifier "Keyboard[0]"
Driver "kbd"
Option "Protocol" "Standard"
Option "XkbLayout" "us"
Option "XkbModel" "pc104"
Option "XkbRules" "xfree86"
EndSection
Section "InputDevice"
Identifier "Mouse[1]"
Driver "mouse"
Option "Buttons" "5"
Option "Device" "/dev/input/mice"
Option "Name" "ImPS/2 Generic Wheel Mouse"
Option "Protocol" "explorerps/2"
Option "Vendor" "Sysp"
Option "ZAxisMapping" "4 5"
EndSection
Section "Modes"
Identifier "Modes[0]"
EndSection
Section "Monitor"
Identifier "Monitor[0]"
VendorName "COMPAQ"
ModelName "P50 COLOR MONITOR"
UseModes "Modes[0]"
DisplaySize 260 200
HorizSync 30.0 - 69.0
VertRefresh 50.0 - 125.0
Option "CalcAlgorithm" "XServerPool"
Option "DPMS"
EndSection
Section "Device"
Identifier "Device[0]"
Driver "fglrx"
VendorName "VESA"
BoardName "Framebuffer Graphics"
Option "FSAADisableGamma" "no"
Option "TVHPosAdj" "0"
Option "Stereo" "off"
Option "FSAAMSPosX3" "0.000000"
Option "CenterMode" "off"
Option "FSAAMSPosY0" "0.000000"
Option "ScreenOverlap" "0"
Option "mtrr" "off"
Option "FSAAMSPosX4" "0.000000"
Option "FSAAMSPosY1" "0.000000"
Option "IgnoreEDID" "off"
Option "ForceGenericCPU" "no"
Option "NoTV" "yes"
Option "FSAAScale" "1"
Option "FSAAMSPosX5" "0.000000"
Option "FSAAMSPosY2" "0.000000"
Option "FSAAMSPosY3" "0.000000"
Option "GammaCorrectionI" "0x06419064"
Option "no_accel" "no"
Option "FSAAMSPosY4" "0.000000"
Option "FSAACustomizeMSPos" "no"
Option "UseFastTLS" "0"
Option "FSAAMSPosY5" "0.000000"
Option "TVVSizeAdj" "0"
Option "BlockSignalsOnLock" "on"
Option "FSAAEnable" "no"
Option "GammaCorrectionII" "0x06419064"
Option "TVHSizeAdj" "0"
Option "VideoOverlay" "on"
Option "TVVPosAdj" "0"
Option "no_dri" "no"
Option "TVColorAdj" "0"
Option "StereoSyncEnable" "1"
Option "UseInternalAGPGART" "no"
Option "FSAAMSPosX0" "0.000000"
Option "TVHStartAdj" "0"
Option "PseudoColorVisuals" "off"
Option "Capabilities" "0x00000000"
Option "FSAAMSPosX1" "0.000000"
Option "TVStandard" "PAL-B"
Option "FSAAMSPosX2" "0.000000"
Option "OpenGLOverlay" "off"
Option "DesktopSetup" "single"
BusID "1:0:0"
EndSection
Section "Screen"
Identifier "Screen[0]"
Device "Device[0]"
Monitor "Monitor[0]"
DefaultDepth 24
SubSection "Display"
Depth 15
Modes "1024x768" "800x600" "768x576" "640x480"
EndSubSection
SubSection "Display"
Depth 16
Modes "1024x768" "800x600" "768x576" "640x480"
EndSubSection
SubSection "Display"
Depth 24
Modes "1024x768" "800x600" "768x576" "640x480"
EndSubSection
SubSection "Display"
Depth 32
Modes "1024x768" "800x600" "768x576" "640x480"
EndSubSection
SubSection "Display"
Depth 8
Modes "1024x768" "800x600" "768x576" "640x480"
EndSubSection
EndSection
Section "DRI"
Group "video"
Mode 0660
EndSection
Michael
12-04-2006, 06:47 PM
Will it load if you make a "simple" xorg.conf? i.e. a fresh xorg.conf and just running aticonfig --initial
exobg
12-04-2006, 06:52 PM
Will it load if you make a "simple" xorg.conf? i.e. a fresh xorg.conf and just running aticonfig --initial
No, ... same result ...
EDIT:
heres xorg.conf from aticonfig --initial:
# Xorg configuration created by pyxf86config
Section "ServerLayout"
Identifier "Default Layout"
Screen 0 "aticonfig-Screen[0]" 0 0
InputDevice "Keyboard0" "CoreKeyboard"
EndSection
Section "Files"
EndSection
Section "Module"
Load "dri"
Load "glx"
EndSection
Section "InputDevice"
Identifier "Keyboard0"
Driver "kbd"
Option "XkbModel" "pc105"
Option "XkbLayout" "us,bg"
Option "XkbOptions" "grp:shifts_toggle,grp_led:scroll"
EndSection
Section "Monitor"
Identifier "aticonfig-Monitor[0]"
Option "VendorName" "ATI Proprietary Driver"
Option "ModelName" "Generic Autodetecting Monitor"
Option "DPMS" "true"
EndSection
Section "Device"
Identifier "Videocard0"
Driver "radeon"
EndSection
Section "Device"
Identifier "aticonfig-Device[0]"
Driver "fglrx"
EndSection
Section "Screen"
Identifier "Screen0"
Device "Videocard0"
DefaultDepth 24
SubSection "Display"
Viewport 0 0
Depth 24
Modes "1024x768" "800x600" "768x576" "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
Now I even have strange desktop efects, you know the jumping program icon in the mouse cursor at KDE,when you start program, well when start jumping it is "drawning" black spots on my Desktop ...
Michael
12-04-2006, 06:55 PM
What graphics card are you using?
exobg
12-04-2006, 06:58 PM
What graphics card are you using?
Radeon X550
glussier
12-04-2006, 07:19 PM
Add the following at the bottom of you /etc/X11/xorg.conf file:
Section "ServerFlags"
Option "AIGLX" "off"
EndSection
Section "DRI"
Group 0
Mode 0666
EndSection
Section "Extensions"
Option "Composite" "Disable"
EndSection
exobg
12-05-2006, 05:15 AM
Add the following at the bottom of you /etc/X11/xorg.conf file:
Section "ServerFlags"
Option "AIGLX" "off"
EndSection
Section "DRI"
Group 0
Mode 0666
EndSection
Section "Extensions"
Option "Composite" "Disable"
EndSection
Thanks :D Now everything is fine :) I guess now I can't use xgl, right ? Even so it's not such big deal for me :)
Michael
12-05-2006, 08:39 AM
You should be able to use XGL, just not AIGLX or Compiz/Beryl (w/o XGL).
ryeancoke
12-05-2006, 09:52 PM
I am struggling with this driver on FC6 x86_64. Here is my xorg.conf and my log. Any suggestions?
(--) Assigning device section with no busID to primary device
(WW) fglrx: No matching Device section for instance (BusID PCI:1:0:1) found
(--) Chipset RADEON 9600 (RV350 4150) found
...
(II) fglrx(0): doing DRIScreenInit
drmOpenDevice: node name is /dev/dri/card0
drmOpenDevice: open result is -1, (No such device or address)
drmOpenDevice: open result is -1, (No such device or address)
drmOpenDevice: Open failed
drmOpenDevice: node name is /dev/dri/card0
drmOpenDevice: open result is -1, (No such device or address)
drmOpenDevice: open result is -1, (No such device or address)
drmOpenDevice: Open failed
[drm] failed to load kernel module "fglrx"
(II) fglrx(0): [drm] drmOpen failed
(EE) fglrx(0): DRIScreenInit failed!
(WW) fglrx(0): ***********************************************
(WW) fglrx(0): * DRI initialization failed! *
(WW) fglrx(0): * (maybe driver kernel module missing or bad) *
(WW) fglrx(0): * 2D acceleraton available (MMIO) *
(WW) fglrx(0): * no 3D acceleration available *
(WW) fglrx(0): ********************************************* *
# Working /etc/X11/xorg.conf for ATI fglrx 8.29.6 and Fedora Core 6
# Created by Michael Larabel / Phoronix
# See: http://www.phoronix.com/redblog/index.php?p=blog&i=NTU1MA
Section "ServerLayout"
Identifier "Default Layout"
Screen 0 "aticonfig-Screen[0]" 0 0
InputDevice "Keyboard0" "CoreKeyboard"
EndSection
Section "Files"
EndSection
Section "Module"
Load "dri"
Load "glx"
EndSection
Section "InputDevice"
Identifier "Keyboard0"
Driver "kbd"
Option "XkbModel" "pc105"
Option "XkbLayout" "us"
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 "TVFormat" "NTSC-M"
Option "TVOverscan" "off"
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 "ServerFlags"
Option "AIGLX" "off"
EndSection
Section "DRI"
Group 0
Mode 0666
EndSection
Section "Extensions"
Option "Composite" "Disable"
EndSection
ryeancoke
12-05-2006, 10:47 PM
Ok, got it working. Here is what I did:
1. Follow the instructions here to stop the fireglcontrol panel from compiling, and not generate the rpm files: http://www.phoronix.net/forums/showthread.php?t=405&page=2#post2501
Once I did the above successfully, I had the following rpm files:
-rw-r--r-- 1 root root 10488424 Dec 5 21:25 ATI-fglrx-8.31.5-1.fc6.x86_64.rpm
-rw-r--r-- 1 root root 7312 Dec 5 21:25 ATI-fglrx-control-panel-8.31.5-1.fc6.x86_64.rpm
-rw-r--r-- 1 root root 121791 Dec 5 21:25 ATI-fglrx-devel-8.31.5-1.fc6.x86_64.rpm
-rw-r--r-- 1 root root 5803223 Dec 5 21:25 ATI-fglrx-IA32-libs-8.31.5-1.fc6.x86_64.rpm
-rw-r--r-- 1 root root 310360 Dec 5 21:25 kernel-module-ATI-fglrx-2.6.18-1.2849.fc6-8.31.5-1.fc6.x86_64.rpm
2. Removed all the fglrx rpms from the system (I used Add/Remove Software GUI)
3. Installed kernel-module-ATI-fglrx-2.6.18-1.2849.fc6-8.31.5-1.fc6.x86_64.rpm, ATI-fglrx-8.31.5-1.fc6.x86_64.rpm and ATI-fglrx-control-panel-8.31.5-1.fc6.x86_64.rpm
4. Used this xorg.conf file:
# Xorg configuration created by system-config-display
Section "ServerLayout"
Identifier "single head configuration"
Screen 0 "aticonfig-Screen[0]" 0 0
InputDevice "Keyboard0" "CoreKeyboard"
EndSection
Section "Files"
EndSection
Section "Module"
Load "glx"
Load "dri"
EndSection
Section "InputDevice"
Identifier "Keyboard0"
Driver "kbd"
Option "XkbModel" "pc105"
Option "XkbLayout" "us"
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 "TVFormat" "NTSC-M"
Option "TVOverscan" "off"
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"
Mode 0666
EndSection
Section "Extensions"
Option "Composite" "Disable"
EndSection
Section "ServerFlags"
Option "AIGLX" "off"
EndSection
5. Restart X and viola!! :D
Hope that helps some of you.
Hi guys,
I have read this whole thread and saw that some people are having problems similar to my ones. I am running FC6 and am having problem to get 3D acceleration working with my card. I have a X600 PCIX with two channels and to 24" Dell monitors, everything works fine but just not as fast as I would like it to be.
I have bilt RPMs using the ati-driver-installer-8.31.5-x86.x86_64.run, drivers installed and working but when I run fglrxinfo I get the below output.
Xlib: extension "XFree86-DRI" missing on display ":0.0".
display: :0.0 screen: 0
OpenGL vendor string: Mesa project: www.mesa3d.org
OpenGL renderer string: Mesa GLX Indirect
OpenGL version string: 1.2 (1.5 Mesa 6.5.1)
This is my config:
# Xorg configuration created by system-config-display
Section "ServerLayout"
Identifier "Multihead layout"
Screen 0 "Screen0" LeftOf "Screen1"
Screen 1 "Screen1" 0 0
InputDevice "Mouse0" "CorePointer"
InputDevice "Keyboard0" "CoreKeyboard"
Option "Xinerama" "on"
Option "Clone" "off"
EndSection
Section "Module"
Load "glx"
Load "dri"
EndSection
Section "ServerFlags"
Option "AIGLX" "off"
EndSection
Section "InputDevice"
Identifier "Keyboard0"
Driver "kbd"
Option "XkbModel" "pc105"
Option "XkbLayout" "us"
Option "XkbVariant" "intl"
EndSection
Section "InputDevice"
Identifier "Mouse0"
Driver "mouse"
Option "Protocol" "IMPS/2"
Option "Device" "/dev/input/mice"
Option "ZAxisMapping" "4 5"
Option "Emulate3Buttons" "yes"
EndSection
Section "Monitor"
### Comment all HorizSync and VertSync values to use DDC:
Identifier "Monitor0"
VendorName "Monitor Vendor"
ModelName "DELL 2407WFP"
Option "dpms"
EndSection
Section "Monitor"
### Comment all HorizSync and VertSync values to use DDC:
Identifier "Monitor1"
VendorName "Monitor Vendor"
ModelName "Dell 2407FPW"
Option "dpms"
EndSection
Section "Device"
Identifier "Videocard0"
Driver "fglrx"
VendorName "Videocard vendor"
BoardName "ATI Technologies Inc RV370 5B62 [Radeon X600 (PCIE)]"
Option "MonitorLayout" "TDMS, TDMS"
BusID "PCI:1:0:0"
EndSection
Section "Device"
Identifier "Videocard1"
Driver "fglrx"
VendorName "Videocard Vendor"
BoardName "ATI Technologies Inc RV370 5B62 [Radeon X600 (PCIE)]"
# Option "SWcursor" "On"
BusID "PCI:1:0:0"
Screen 1
EndSection
Section "Screen"
Identifier "Screen0"
Device "Videocard0"
Monitor "Monitor0"
DefaultDepth 24
SubSection "Display"
Viewport 0 0
Depth 24
Modes "1920x1200" "1680x1050"
EndSubSection
EndSection
Section "Screen"
Identifier "Screen1"
Device "Videocard1"
Monitor "Monitor1"
DefaultDepth 24
SubSection "Display"
Viewport 0 0
Depth 24
Modes "1920x1200" "1680x1050"
EndSubSection
EndSection
Section "DRI"
Group 0
Mode 0666
EndSection
Section "Extensions"
Option "Composite" "Disable"
EndSection
And this is my log file. If anyone knows what is going on here and could give a hand it would be very much appreciated. Thanks a lot in advance
Vini :)
Sorry the log seems to be too long and the website is crashing everytime when I post it.
(WW) warning, (EE) error, (NI) not implemented, (??) unknown.
(WW) No FontPath specified. Using compiled-in default.
(WW) fglrx(0): MonitorLayout is no longer supported.
(WW) fglrx(0): ***********************************
(WW) fglrx(0): * DRI initialization disabled! *
(WW) fglrx(0): * 2D acceleraton available (MMIO) *
(WW) fglrx(0): * no 3D acceleration available *
(WW) fglrx(0): ***********************************
(WW) fglrx(1): ***********************************
(WW) fglrx(1): * DRI initialization disabled! *
(WW) fglrx(1): * 2D acceleraton available (MMIO) *
(WW) fglrx(1): * no 3D acceleration available *
(WW) fglrx(1): ***********************************
(WW) warning, (EE) error, (NI) not implemented, (??) unknown.
Michael
12-08-2006, 09:04 AM
vini,
Do the drivers work if you use a simple xorg.conf with only a single head?
Had you tried using aticonfig with an ATI Big Desktop to run both of your screens? If not, you may want to try that as it should work better in most situations.
2. Setting up big desktop to horizontal and set overlay on secondary display.
aticonfig --dtop=horizontal --overlay-on=1
Hi Michael,
I think the only test that I didn't do was with a single head. I don't think it would work though, I know it worked before with dual head. I used to have FC5 and it was just fine but the ATI driver was a little older.
I think I tried the big desktop sometime ago, it was a bit strange I think because I was as if the screen was one long screen. This is not quite what I want as I need the windows to behave based on the screen they are on.
It is really strange as I have done everything that you recommended to people and some other things that I read on the net. The configuration looks good but it doesn't work at all with DRI. One question though, do I have to have the DRM module loaded to be able to use DRI?
Thanks
Vini
vini,
Do the drivers work if you use a simple xorg.conf with only a single head?
Had you tried using aticonfig with an ATI Big Desktop to run both of your screens? If not, you may want to try that as it should work better in most situations.
Michael
12-08-2006, 09:55 AM
Trying a single head xorg.conf (backup your current config and then run aticonfig --initial) would be worth trying.
Big Desktop with GNOME 2.16 or KDE 3.5.4 shouldn't cause issues with "long screens". I had used Big Desktop earlier this year for a few months.
You shouldn't need to mess with DRM and the DRI setup for the drivers to work, or did you build the kernel yourself?
Ok I will try with single head to see what happens.
Do you think a Big desktop would be the same as far as the window manager goes? I my windows don't go crazy I think there is no problem in using it. Also, I was going to post this here as well but forgot, I haven't managed to get my card working with 1920x1200, it works only with 1600x1050. The screens do support the 1920x1200 but it falls back to 1600x1050. Any ideas why it isn't working with this resolution?
I haven't built the kernel myself, I it is the default (but latest) FC6 kernel. It was updated by yum. The reason why I asked that question about DRM is that the drm kernel modules is not being loaded and when I try to load it I get a message saying that "cannot allocate memory (or something like that)" does this modules have to be loaded? The fglxr modules is being loaded just in case you wondered.
THnaks
Vini
Trying a single head xorg.conf (backup your current config and then run aticonfig --initial) would be worth trying.
Big Desktop with GNOME 2.16 or KDE 3.5.4 shouldn't cause issues with "long screens". I had used Big Desktop earlier this year for a few months.
You shouldn't need to mess with DRM and the DRI setup for the drivers to work, or did you build the kernel yourself?
fc6_try_production
12-08-2006, 11:38 AM
Hello Vini,
it seems quite a few people are trying to get this solved. Here is what I did (After a few days of lots of linking and then starting from scratch):
When trying to build the ati.com ATI driver on FC6 , one MUST have installed:
1. development libraries packages
2. development tools packages
3. GNOME development packages
4. X development packages
5. Old Software development -> compat-libdistc++-33-*
6. qt-devel
7. rpm-build
Then it compiles fine, no problems with "cannot stat firecontrolxyz . ." etc. I do not know exactly what is being installed to prevent the "cannot stat ... " problem, but this way you can solve it. Afterwards, you remove 1.-4.,6. and 7.
Solution to persistent MESA GL renderer when installing the 8.31.5 driver from livna (as you apparently did)
yum install xorg-X11-drv-fglrx.i386
The corresponding libGL.so.1.2 from this package will be installed in /usr/lib/ati-fglrx/ . Of course, the existing ligGL.so.1.2 provided by MESA, which resides in /usr/lib, will be found in the path first. So rename /usr/lib/libGL.so.1.2 to /usr/lib/ligGL.so.1.2.MESA and copy /usr/lib/ati-fglrx/ligGL.so.1.2 to /usr/lib. It did the trick. After rebooting (NOT only restarting X, funny, that . . ) I got the following on fglrxinfo:
display: :0.0 screen: 0
OpenGL vendor string: ATI Technologies Inc.
OpenGL renderer string: MOBILITY RADEON X300 Generic
OpenGL version string: 2.0.6174 (8.31.5)
So there you are :cool:
Regards,
J.
Michael
12-08-2006, 11:59 AM
Big Desktop shouldn't give window manager problems.
In regards to your resolution issues, you could manually specify the higher resolution in your xorg.conf. The drivers likely aren't pulling all of the EDID information.
Hey ya,
It works, I have got rid of the libGL.so.1.2 in /usr/lib and created a symbolic to the fglrx GL libs. It looks much better but there are still some weirdness, for example when I run glxgears it doesn't show up if its windown is small (default size). If I make the window bigger it shows up but the gears stop moving if I move the window across to the right half of the right screen. There appears to be a line that when crossed the gears stop moving.
Apart from this everything looks good.
Thanks for your help,
Vini
Hello Vini,
it seems quite a few people are trying to get this solved. Here is what I did (After a few days of lots of linking and then starting from scratch):
When trying to build the ati.com ATI driver on FC6 , one MUST have installed:
1. development libraries packages
2. development tools packages
3. GNOME development packages
4. X development packages
5. Old Software development -> compat-libdistc++-33-*
6. qt-devel
7. rpm-build
Then it compiles fine, no problems with "cannot stat firecontrolxyz . ." etc. I do not know exactly what is being installed to prevent the "cannot stat ... " problem, but this way you can solve it. Afterwards, you remove 1.-4.,6. and 7.
Solution to persistent MESA GL renderer when installing the 8.31.5 driver from livna (as you apparently did)
yum install xorg-X11-drv-fglrx.i386
The corresponding libGL.so.1.2 from this package will be installed in /usr/lib/ati-fglrx/ . Of course, the existing ligGL.so.1.2 provided by MESA, which resides in /usr/lib, will be found in the path first. So rename /usr/lib/libGL.so.1.2 to /usr/lib/ligGL.so.1.2.MESA and copy /usr/lib/ati-fglrx/ligGL.so.1.2 to /usr/lib. It did the trick. After rebooting (NOT only restarting X, funny, that . . ) I got the following on fglrxinfo:
display: :0.0 screen: 0
OpenGL vendor string: ATI Technologies Inc.
OpenGL renderer string: MOBILITY RADEON X300 Generic
OpenGL version string: 2.0.6174 (8.31.5)
So there you are :cool:
Regards,
J.
Hi Michael,
I have managed to fix my GL problem, it all seems to work well now. Please see my last post for more information on how I did it. I have also managed to configure my card to work with Big Desktop, it looks fine and works the same way as xinerama. My KDE hasn't complained yet and it is behaving the same way as before.
The Big Desktop also fixed an annoying problem that I used to have, the cursor wouldn't changed when moved across to the second screen. Like if you were typing a text and had a text cursor on the left screen and then suddenly moved it across to the right screen, it then would stay a text cursor while on the right screen. This no longer happens... :)
As for the resolution, I am not sure what to do. My xorg.conf explicitly states the resolution I want (1920x1200) but when the X server starts it resolution is always 1680x1050. Any ideas why this is happening?
Thanks a lot for your help so far!
Vini
Big Desktop shouldn't give window manager problems.
In regards to your resolution issues, you could manually specify the higher resolution in your xorg.conf. The drivers likely aren't pulling all of the EDID information.
Michael
12-10-2006, 09:03 PM
I don't think there are any limitations with the fglrx drivers for the resolution. Just to check, but your monitor can support the resolution? Is there anything regarding the resolution in your Xorg.0.log?
Hi Michael,
This is the section when I specify the resoltion.
Section "Screen"
Identifier "Screen0"
Device "Videocard0"
Monitor "Monitor0"
DefaultDepth 24
SubSection "Display"
Viewport 0 0
Depth 24
Modes "1920x1200" "1680x1050"
EndSubSection
EndSection
I have another similar entry for Screen1. Wiich I think is no longer needed as I am using Big Desktops, is it correct?
This is a link to the screen, it does support the resolution I want.
http://www1.ap.dell.com/content/products/productdetails.aspx/2407wfp?c=au&cs=aubsd1&l=en&s=bsd
Thanks
Vini
I don't think there are any limitations with the fglrx drivers for the resolution. Just to check, but your monitor can support the resolution? Is there anything regarding the resolution in your Xorg.0.log?
Michael
12-10-2006, 09:25 PM
Correct, for Big Desktop you should only need one screen entry.
You could try the next fglrx display driver when it's released to see if it by chance fixes your resolution problem.
I am also able to check with ATI as to any limitations that the fglrx drivers may have when running at 1900 x as well as being in a Big Desktop mode.
Hi Michael,
If you could check that with ATI that would be great. Do you know when a nover version of this driver may be released?
After a configured my machine to use Big Desktop there is something that is looking a bit strange. The round outer corners of every windows hava a black sharp square corner underneath, it is a bit hard to explain but it seems that the window manager (KDE) is not understanding something properly. Also the waiting cursors are no longer transparent, when the cursor turns into a waiting cursor and starts bouncing it has a blackbox around it.
I am using "OverlayOnCRTC2" "1" - I am not even sure why I have that in mu config file. Would that have anything todo with it?
Thanks
Vini
Correct, for Big Desktop you should only need one screen entry.
You could try the next fglrx display driver when it's released to see if it by chance fixes your resolution problem.
I am also able to check with ATI as to any limitations that the fglrx drivers may have when running at 1900 x as well as being in a Big Desktop mode.
Michael
12-11-2006, 07:42 AM
Hi Michael,
If you could check that with ATI that would be great. Do you know when a nover version of this driver may be released?
After a configured my machine to use Big Desktop there is something that is looking a bit strange. The round outer corners of every windows hava a black sharp square corner underneath, it is a bit hard to explain but it seems that the window manager (KDE) is not understanding something properly. Also the waiting cursors are no longer transparent, when the cursor turns into a waiting cursor and starts bouncing it has a blackbox around it.
I am using "OverlayOnCRTC2" "1" - I am not even sure why I have that in mu config file. Would that have anything todo with it?
Thanks
Vini
For transparency see -- http://phoronix.net/forums/showthread.php?t=367
Unfortunately, I cannot state when the new drivers will be coming... But keep in mind they are usually about the middle of the month.
I'll check with ATI in the next couple of days about the problem.
Sorry for asking but I am curious about this, do you work for ATI?
For transparency see -- http://phoronix.net/forums/showthread.php?t=367
Unfortunately, I cannot state when the new drivers will be coming... But keep in mind they are usually about the middle of the month.
I'll check with ATI in the next couple of days about the problem.
Michael
12-11-2006, 10:18 AM
Sorry for asking but I am curious about this, do you work for ATI?
No, I am not a paid employee of ATI Technologies or Advanced Micro Devices. I am a Fedora package maintainer for the fglrx drivers (after Niko's departure, prior to that I ran all the tests to ensured the scripts had worked). I also cover the ATI drivers at Phoronix thus I have other contacts at ATI, as well as NVIDIA.
No, I am not a paid employee of ATI Technologies or Advanced Micro Devices. I am a Fedora package maintainer for the fglrx drivers (after Niko's departure, prior to that I ran all the tests to ensured the scripts had worked). I also cover the ATI drivers at Phoronix thus I have other contacts at ATI, as well as NVIDIA.
Michael and everyone else,
Everything work perfectly on my machine now, transparency is back and the Big Desktop configuration solved many other problems that I was having. The only thing I haven't managed to fix yet is the resolution, but I can live with this for a while as 1680x1050 is not too bad.
Thank you all for your help!
Regards,
Vini
Michael
12-12-2006, 07:47 PM
Michael and everyone else,
Everything work perfectly on my machine now, transparency is back and the Big Desktop configuration solved many other problems that I was having. The only thing I haven't managed to fix yet is the resolution, but I can live with this for a while as 1680x1050 is not too bad.
Thank you all for your help!
Regards,
Vini
Tomorrow I can check with ATI about your resolution problem, if needed.
Tomorrow I can check with ATI about your resolution problem, if needed.
If you could that would be great!
Thanks
Michael
12-12-2006, 10:52 PM
If you could that would be great!
Thanks
Okay, ATI said that there are some OpenGL limitations with some hardware. After letting them know it was an X600 with two Dell LCDs, below is the response.
Although i can't make any commitments, get him to log a bugzilla on ati.cchtml.com, it gives us something to work with.
vBulletin® v3.7.4, Copyright ©2000-2009, Jelsoft Enterprises Ltd.