| View previous topic :: View next topic |
| Author |
Message |
dlublink
Tux's lil' helper
Joined: 30 Sep 2006
Posts: 146
|
 Posted: Wed Mar 07, 2007 5:02 pm Post subject: DRI device exists, but doesn't work |
 |
|
Hello,
So, last week all of a sudden glxinfo started reporting 'Direct Rendering: Yes'. PPRacer, GoogleEarth all worked beautifully. GLXGears was spinning smoothly and beautifully.
So yesterday I decided to install beryl to impress my friends. One of the steps in Beryl was to change the X display to 1 and set 0 as inactive. I think this may have ruined by GLX experience.
Now when I run ppRacer or googleearth it's as if I don't have a 3d card, glxinfo now reports direct rendering as 'no' and glxgears stutters when it actually moves.
I looked through the log and found this:
| Code: |
(II) RADEON(0): Detected Radeon Mobility M6, disabling multimedia i2c
(II) Loading sub module "theatre_detect"
(II) LoadModule: "theatre_detect"
(II) Loading /usr/lib/xorg/modules/multimedia/theatre_detect_drv.so
(II) Module theatre_detect: vendor="X.Org Foundation"
compiled for 7.1.1, module version = 1.0.0
ABI class: X.Org Video Driver, version 1.0
(II) RADEON(0): no multimedia table present, disabling Rage Theatre.
(WW) RADEON(0): Option "VendorName" is not used
(WW) RADEON(0): Option "ModelName" is not used
(**) RADEON(0): RADEONScreenInit finished
(==) RandR enabled
(II) Initializing built-in extension MIT-SHM
(II) Initializing built-in extension XInputExtension
(II) Initializing built-in extension XTEST
(II) Initializing built-in extension XKEYBOARD
(II) Initializing built-in extension XC-APPGROUP
(II) Initializing built-in extension SECURITY
(II) Initializing built-in extension XINERAMA
(II) Initializing built-in extension XFIXES
(II) Initializing built-in extension XFree86-Bigfont
(II) Initializing built-in extension RENDER
(II) Initializing built-in extension RANDR
(II) Initializing built-in extension COMPOSITE
(II) Initializing built-in extension DAMAGE
(II) Initializing built-in extension XEVIE
drmOpenDevice: node name is /dev/dri/card0
drmOpenDevice: open result is 9, (OK)
drmOpenByBusid: Searching for BusID pci:0000:01:00.0
drmOpenDevice: node name is /dev/dri/card0
drmOpenDevice: open result is 9, (OK)
drmOpenByBusid: drmOpenMinor returns 9
drmOpenByBusid: drmGetBusid reports pci:0000:01:00.0
(WW) AIGLX: 3D driver claims to not support visual 0x23
(WW) AIGLX: 3D driver claims to not support visual 0x24
(WW) AIGLX: 3D driver claims to not support visual 0x25
(WW) AIGLX: 3D driver claims to not support visual 0x26
(WW) AIGLX: 3D driver claims to not support visual 0x27
(WW) AIGLX: 3D driver claims to not support visual 0x28
(WW) AIGLX: 3D driver claims to not support visual 0x29
(WW) AIGLX: 3D driver claims to not support visual 0x2a
(WW) AIGLX: 3D driver claims to not support visual 0x2b
(WW) AIGLX: 3D driver claims to not support visual 0x2c
(WW) AIGLX: 3D driver claims to not support visual 0x2d
(WW) AIGLX: 3D driver claims to not support visual 0x2e
(WW) AIGLX: 3D driver claims to not support visual 0x2f
(WW) AIGLX: 3D driver claims to not support visual 0x30
(WW) AIGLX: 3D driver claims to not support visual 0x32
(II) AIGLX: Loaded and initialized /usr/lib/dri/radeon_dri.so
(II) GLX: Initialized DRI GL provider for screen 0
(II) AIGLX: Loaded and initialized /usr/lib/dri/radeon_dri.so
(II) GLX: Initialized DRI GL provider for screen 0
(**) Option "CoreKeyboard"
(**) Keyboard1: Core Keyboard
(**) Option "Protocol" "standard"
(**) Keyboard1: Protocol: standard
(**) Option "XkbRules" "xorg"
(**) Keyboard1: XkbRules: "xorg"
(**) Option "XkbModel" "pc105"
(**) Keyboard1: XkbModel: "pc105"
(**) Option "XkbLayout" "us"
(**) Keyboard1: XkbLayout: "us"
(**) Option "CustomKeycodes" "off"
(**) Keyboard1: CustomKeycodes disabled
(WW) <default pointer>: No Device specified, looking for one...
(II) <default pointer>: Setting Device option to "/dev/input/mice"
(--) <default pointer>: Device: "/dev/input/mice"
(==) <default pointer>: Protocol: "Auto"
(**) Option "CorePointer"
(**) <default pointer>: Core Pointer
(==) <default pointer>: Emulate3Buttons, Emulate3Timeout: 50
(**) <default pointer>: ZAxisMapping: buttons 4 and 5
(**) <default pointer>: Buttons: 9
(II) XINPUT: Adding extended input device "<default pointer>" (type: MOUSE)
(II) XINPUT: Adding extended input device "Keyboard1" (type: KEYBOARD)
xkb_keycodes { include "xfree86+aliases(qwerty)" };
xkb_types { include "complete" };
xkb_compatibility { include "complete" };
xkb_symbols { include "pc(pc105)+us" };
xkb_geometry { include "pc(pc105)" };
(--) <default pointer>: PnP-detected protocol: "ExplorerPS/2"
(II) <default pointer>: ps2EnableDataReporting: succeeded
(**) RADEON(0): RADEONSaveScreen(2)
(**) RADEON(0): RADEONDisplayPowerManagementSet(0,0x0)
(**) RADEON(0): RADEONSaveScreen(2)
xkb_types { include "%" };
xkb_compatibility { include "%" };
xkb_symbols { include "%" };
xkb_geometry { include "%" };
(EE) Error loading keymap /usr/share/X11/xkb/compiled/server-94.xkm
|
Permissions and timestamp are fine on the device:
| Code: |
david@compaq /var/log $ ls /dev/dri/ -l
total 0
crw-rw-rw- 1 root root 226, 0 2007-03-07 11:49 card0
david@compaq /var/log $
|
Here are some highlights from xorg.conf:
| Code: |
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 "radeon"
Option "RenderAccel" "true"
Option "AGPMode" "4"
# Option "AGPFastWrite" "true" #Faster than default (off)
Option "SWcursor" "false" #Faster than default (on)
Option "EnablePageFlip" "true" #Faster than default (off)
Option "AccelMethod" "EXA" # or XAA, EXA, XAA more stable, XAA is deafult
Option "DynamicClocks" "true"
Option "BIOSHotkeys" "true"
Option "AGPSize" "32" # default: 8
Option "EnableDepthMoves" "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
|
I don't know what the problem is, but wonder if it has to do with XGL using screen 1 and my ATI on screen 0 which is now inactive in GDM. I removed the modifications to GDM.conf and set 0=Standard and commented out 0=inactive and 1=Xgl. Now glxgears runs smoothly, ppracer and googleearth work fine, glxinfo says direct rendering is on.
So it looks like if I have Beryl, I loose my GLX.
Any ideas?
Thanks,
David |
|
| Back to top |
|
 |
dlublink
Tux's lil' helper
Joined: 30 Sep 2006
Posts: 146
|
| Posted: Wed Mar 07, 2007 5:20 pm Post subject: |
|
|
I did some research and came across the opensuse website : [url]http://en.opensuse.org/Xgl[/url].
From what I understand, I can have cool effects in X without non-functionning applications, or have fully functional applications with no effects?
Even gnome-tetris is laggy running in the XGL screen.
How do I get 3d acceleration in my applications within XGL?
Thanks,,
David |
|
| Back to top |
|
|
dlublink
Tux's lil' helper
Joined: 30 Sep 2006
Posts: 146
|
| Posted: Wed Mar 07, 2007 5:38 pm Post subject: |
|
|
I found a thread that addresses part of this issue:
https://forums.gentoo.org/viewtopic-t-483004.html
But it doesn't seem to cover the issue entirely.
I noticed that when scrolling (firefox, terminal etc...) it is *really* slow in XGL. Do I have to run all my applications using the script he wrote??
David |
|
| Back to top |
|
|
|
|
You cannot post new topics in this forum
You cannot reply to topics in this forum
You cannot edit your posts in this forum
You cannot delete your posts in this forum
You cannot vote in polls in this forum
|
|
Desktop Environments
