Forums

Skip to content

Advanced search
  • Quick links
    • Unanswered topics
    • Active topics
    • Search
  • FAQ
  • Login
  • Register
  • Board index Assistance Desktop Environments
  • Search

Current Status of Intel GEM, UXA Acceleration, KMS, and PAE?

Problems with GUI applications? Questions about X, KDE, Gnome, Fluxbox, etc.? Come on in. NOTE: For multimedia, go up one forum
Post Reply
Advanced search
34 posts
  • 1
  • 2
  • Next
Author
Message
0000000000000
Apprentice
Apprentice
Posts: 163
Joined: Fri Mar 21, 2008 11:21 pm

Current Status of Intel GEM, UXA Acceleration, KMS, and PAE?

  • Quote

Post by 0000000000000 » Thu Jun 04, 2009 7:15 pm

I have not been keeping up with the latest developments, and I am trying to gather information across the internets in regards to this, but there is quite a breadth of differences.

From what I have gathered though, in order to use GEM on an intel card (gma4500hd) and UXA acceleration, the kernel needs KMS enabled and PAE disabled although I have read reports of KMS not being needed and I have seen the patch for GEM+PAE but have yet to apply it.

As of now, my configuration is xorg-server-1.6.0, intel driver 2.6.3, and mesa-7.3 along with libdrm-2.4.5 and dri2proto-2.0. I have PAE enabled, KMS disabled, and I am running 2.6.30-rc3 from Linus Torvalds off of git. With this, I can not enable AccelMethod UXA or I get an entirely black screen (no backlight even), and with EXA I get "failed to initialize GEM"

Anyone more knowledgeable on this who has inclination to point me towards what is needed, or knows the current state of these technologies is implored to reply.

Thanks.
Top
pappy_mcfae
Watchman
Watchman
User avatar
Posts: 5999
Joined: Thu Dec 27, 2007 10:51 pm
Location: Pomona, California.
Contact:
Contact pappy_mcfae
Website

  • Quote

Post by pappy_mcfae » Fri Jun 05, 2009 4:45 am

You might want to wait on KMS. Put simply, it sucks. I know that statement will probably upset some folk. Oh well.

I gave it a go last night after deciding I could risk pappy-lap's stability to further the purposes of Linux. You know what, KMS was a mess. It was unstable; very unstable. I couldn't get it to automatically use "vga=" statements. Once X started, I had mouse tails and other irritations on the screen.

Thanks but no thanks. As of yet, I have no reason to move from using the standard intelfb. It works just fine. I can swap between X and CLI sessions, and not miss a beat.

As for PAE, if it's working, it's working.

Blessed be!
Pappy
This space left intentionally blank, except for these ASCII symbols.
Top
0000000000000
Apprentice
Apprentice
Posts: 163
Joined: Fri Mar 21, 2008 11:21 pm

  • Quote

Post by 0000000000000 » Fri Jun 05, 2009 5:18 pm

Thanks Pappy,

I decided to just give it a go and went ahead and enabled KMS last night, disabled PAE, upgraded xorg to 1.6.1 and updated intel driver to 2.7.0. GEM and UXA are now working, I can switch between X and console without any graphical glitches or hangs and nothing seems to be broken at the moment. Last time I used KMS my resolution would get messed up if restarting X or when trying to run mplayer full screen. That is not happening this time around. My glxgears FPS are much lower now though, but when I try to play Portal, instead of the window locking up my entire system, it just goes white and I can still hear the game's sound, and if I click around on the screen it makes noises as though I am clicking on the buttons that would otherwise be visible. I don't know if this can really be considered an improvement, but it's not as sloppy and unusable as the last time I experimented with KMS.

Going to see if I can figure out what "Intel XvMC decoder disabled" means, if it's a bad thing, and how to enable it, as Option "XvMC" "true" is "not used"
Top
Havin_it
Veteran
Veteran
Posts: 1343
Joined: Sun Jul 17, 2005 10:26 am
Location: Edinburgh, UK
Contact:
Contact Havin_it
Website

  • Quote

Post by Havin_it » Fri Jun 19, 2009 1:18 pm

0000000000000 wrote: Going to see if I can figure out what "Intel XvMC decoder disabled" means, if it's a bad thing, and how to enable it, as Option "XvMC" "true" is "not used"
I wondered about this too. I notice there is an eselect module for xvmc, where you can choose intel or xorg, but I've yet to see what difference it makes. If anyone has any background on this, I'd be interested.
Top
alex.blackbit
Advocate
Advocate
Posts: 2397
Joined: Tue Jul 26, 2005 8:04 pm

  • Quote

Post by alex.blackbit » Fri Jun 19, 2009 1:49 pm

KMS and UXA works fine for me, for quite some time now.
the console itself, X, console switching, all are quick and stable.
xorg-server-1.6.1.901-r3, xf86-video-intel-2.7.1, gentoo-sources-2.6.30-r1.
the only regressions i am facing at the moment are: mplayer fullscreen in smaller than full, and quitting google-earth crashes the x server.
Top
pdw_hu
Apprentice
Apprentice
Posts: 200
Joined: Mon Jun 02, 2008 6:56 pm
Location: Budapest, Hungary

  • Quote

Post by pdw_hu » Fri Jun 19, 2009 2:32 pm

All of these work great for me, with the exception of KMS + kdm. I cannot log out of KDE4, because the screen will just stay black. But otherwise, it's alright.
Top
Havin_it
Veteran
Veteran
Posts: 1343
Joined: Sun Jul 17, 2005 10:26 am
Location: Edinburgh, UK
Contact:
Contact Havin_it
Website

  • Quote

Post by Havin_it » Fri Jun 19, 2009 9:35 pm

pappy_mcfae wrote:You might want to wait on KMS. Put simply, it sucks. I know that statement will probably upset some folk. Oh well.

I gave it a go last night after deciding I could risk pappy-lap's stability to further the purposes of Linux. You know what, KMS was a mess. It was unstable; very unstable. I couldn't get it to automatically use "vga=" statements. Once X started, I had mouse tails and other irritations on the screen.

Thanks but no thanks. As of yet, I have no reason to move from using the standard intelfb. It works just fine. I can swap between X and CLI sessions, and not miss a beat.

As for PAE, if it's working, it's working.

Blessed be!
Pappy
I have the two extremes: KMS works nicely on my NC10 (with 945GMA) but X won't even start on my older lappy (855GM). Well, it starts enough to give me a blank screen with a frozen cursor and a hard lock :S

By the way Pappy, what's the spec on your newer machine?

Oh and what's PAE? Just when I thought I knew all the acronyms...
Top
alex.blackbit
Advocate
Advocate
Posts: 2397
Joined: Tue Jul 26, 2005 8:04 pm

  • Quote

Post by alex.blackbit » Fri Jun 19, 2009 11:29 pm

well, wikipedia knows what PAE means.
basically it's the ability to use more than 4G on a 32bit system.
Top
Havin_it
Veteran
Veteran
Posts: 1343
Joined: Sun Jul 17, 2005 10:26 am
Location: Edinburgh, UK
Contact:
Contact Havin_it
Website

  • Quote

Post by Havin_it » Sat Jun 20, 2009 1:56 am

alex.blackbit wrote:well, wikipedia knows what PAE means.
basically it's the ability to use more than 4G on a 32bit system.
Oh, thanks. I did look it up, but I didn't think that was what was being discussed here because (a) I didn't think it was all that related to the graphics situation and (b) I assumed we'd had this capability for some time. Thanks for putting me straight.
Top
Elv13
Guru
Guru
User avatar
Posts: 388
Joined: Sun Nov 13, 2005 8:42 pm
Location: Socialist land of North America

  • Quote

Post by Elv13 » Sat Jun 20, 2009 2:41 am

XxMC is the video acceleration interface of Intel. It use less CPU when it is working, that's all. It is visible when playing HD video (10% cpu instead of 50%) according to phoronix, but NVIDIA VDPAU is better (50% cpu to 1%).
Top
alex.blackbit
Advocate
Advocate
Posts: 2397
Joined: Tue Jul 26, 2005 8:04 pm

  • Quote

Post by alex.blackbit » Sat Jun 20, 2009 2:45 am

Havin_it, you are right, PAE exists for quite some time now, but nonetheless it is still useful and needed in a 32bit environment.
Top
pappy_mcfae
Watchman
Watchman
User avatar
Posts: 5999
Joined: Thu Dec 27, 2007 10:51 pm
Location: Pomona, California.
Contact:
Contact pappy_mcfae
Website

  • Quote

Post by pappy_mcfae » Sat Jun 20, 2009 6:38 am

Havin_it wrote:By the way Pappy, what's the spec on your newer machine?
It's a Compaq C504US with the i945 video chipset. It doesn't mind the old-fashioned fb, so I really don't see a need to change, especially when what I'd change too is unstable to the extreme. I'll check every now and again to see if the problems I see in that setup have been fixed, and modify my system if the need arises.

Blessed be!
Pappy
This space left intentionally blank, except for these ASCII symbols.
Top
marcelser
Tux's lil' helper
Tux's lil' helper
Posts: 106
Joined: Thu Sep 30, 2004 9:53 pm

opengl only software rasterizer

  • Quote

Post by marcelser » Thu Jun 25, 2009 5:31 pm

Hi,

I just installed kernel-2.6.29-r3 xorg-server-1.6.1 and intel-video-9999, libdrm-9999 and set AccelMethod to "UXA". X starts fine, but when I run glxinfo it always says that for opengl rendering I only have software rasterizer. What am I doing wrong and can I somehow check if UXA is enabled?

I also have another problem. KMS only gives me a black screen when kernel starts, I think it has something to do with the vga=792 statement but I'm not sure.

Can anyone tell me how I check if UXA is working properly, and how I get opengl to use the intel driver instead of software rasterizer and is there some solution to KMS with VGA statements?

Thanks for every help I on this.
Top
PaulBredbury
Watchman
Watchman
User avatar
Posts: 7310
Joined: Thu Jul 14, 2005 3:47 pm

Re: opengl only software rasterizer

  • Quote

Post by PaulBredbury » Thu Jun 25, 2009 7:11 pm

marcelser wrote:when I run glxinfo it always says that for opengl rendering I only have software rasterizer.
Check /var/log/Xorg.0.log for a better error message.
Top
alex.blackbit
Advocate
Advocate
Posts: 2397
Joined: Tue Jul 26, 2005 8:04 pm

Re: opengl only software rasterizer

  • Quote

Post by alex.blackbit » Thu Jun 25, 2009 7:29 pm

PaulBredbury wrote:
marcelser wrote:when I run glxinfo it always says that for opengl rendering I only have software rasterizer.
Check /var/log/Xorg.0.log for a better error message.
very true.
try this to parse the log file for your convenience:

Code: Select all

grep -E "^\((WW|EE|NI|\?\?)\)" /var/log/Xorg.0.log
i have an alias with that on all my machines. it's needed from time to time.
Top
asturm
Developer
Developer
Posts: 9496
Joined: Thu Apr 05, 2007 4:07 pm

  • Quote

Post by asturm » Thu Jun 25, 2009 9:34 pm

KMS works extremely well for me and my i915.
Top
baeksu
l33t
l33t
User avatar
Posts: 609
Joined: Sun Sep 26, 2004 11:03 am
Location: Seoul, Korea

Re: opengl only software rasterizer

  • Quote

Post by baeksu » Fri Jun 26, 2009 8:40 am

marcelser wrote:I also have another problem. KMS only gives me a black screen when kernel starts, I think it has something to do with the vga=792 statement but I'm not sure.
If you enable KMS, you should remove any 'vga=' or 'video=' parameters, as the kernel will (try to) automatically figure out the appropriate resolution. Having both (KMS and vga) will result in the black screen you saw.
Gnome:
1. A legendary being.
2. A never ending quest to make unix friendly to people who don't want unix and excruciating for those that do.
Top
vh4x0r
n00b
n00b
User avatar
Posts: 37
Joined: Mon May 11, 2009 4:36 pm
Contact:
Contact vh4x0r
Website

  • Quote

Post by vh4x0r » Fri Jun 26, 2009 7:32 pm

I have tested KMS on vanilla 2.6.30, with xorg-server-1.6.1 and intel drivers-2.7.1 on an intel 845. No problems with console switching, no graphical glitches, but no xvideo!!! Adding nomodeset=1 brings up xvideo again! Also there is the invisible mouse cursor problem with 2.6.29-gentoo-r5!
Top
toralf
Developer
Developer
User avatar
Posts: 3944
Joined: Sun Feb 01, 2004 2:58 pm
Location: Hamburg
Contact:
Contact toralf
Website

  • Quote

Post by toralf » Fri Jun 26, 2009 7:48 pm

genstorm wrote:KMS works extremely well for me and my i915.
Trying KMS with 2.6.29.5 at my ThinkPad T400 messed it up in a way, that I had to boot into windows to get X11 up and running again with the native resolution of 1440x900...
Top
Hupf
Tux's lil' helper
Tux's lil' helper
User avatar
Posts: 112
Joined: Sun Sep 11, 2005 3:01 pm
Location: Germany

  • Quote

Post by Hupf » Sat Jun 27, 2009 7:00 am

On my X4500HD, the 29 line of kernels was broken too. With the 2.6.30 kernel, KMS+UXA work fine though. XVideo or OpenGL weren't tested yet and I get some very strange keyboard stuttering when switching to a console (making it impossible to type in a password), but the basic GUI is up quick and clean :)
Top
asturm
Developer
Developer
Posts: 9496
Joined: Thu Apr 05, 2007 4:07 pm

  • Quote

Post by asturm » Sat Jun 27, 2009 12:08 pm

Yes, unpatched 2.6.29 is a bad idea for KMS. Go for 2.6.30 instead.

FYI I'm also using xorg-server-1.6.1.901-r4 and xf86-video-intel-9999. Bleeding edge really is an advantage here.
Top
marcelser
Tux's lil' helper
Tux's lil' helper
Posts: 106
Joined: Thu Sep 30, 2004 9:53 pm

Re: opengl only software rasterizer

  • Quote

Post by marcelser » Thu Jul 02, 2009 7:39 am

First of all, removing vga= make the kernel mode working, although kdm does not come back when I log out of kde (it works when I disable kms in the kernel, don't know why. But I still have problems to get UXA working.
alex.blackbit wrote:
PaulBredbury wrote:
marcelser wrote:when I run glxinfo it always says that for opengl rendering I only have software rasterizer.
Check /var/log/Xorg.0.log for a better error message.
very true.
try this to parse the log file for your convenience:

Code: Select all

grep -E "^\((WW|EE|NI|\?\?)\)" /var/log/Xorg.0.log
i have an alias with that on all my machines. it's needed from time to time.
I have tried this, but I only get the following output:

Code: Select all

(WW) intel(0): libpciaccess reported 0 rom size, guessing 64kB
(WW) intel(0): Option "DDC" is not used
But I found other interesting stuff in Xorg.0.log:

Code: Select all

(**) intel(0): Framebuffer compression disabled
(**) intel(0): Tiling disabled
(**) intel(0): SwapBuffers wait enabled
(==) intel(0): VideoRam: 262144 KB
(II) intel(0): Attempting memory allocation with untiled buffers.
(II) intel(0): Untiled allocation successful.
(II) UXA(0): Driver registered support for the following operations:
(II)         solid
(II)         copy
(II)         composite (RENDER acceleration)
(==) intel(0): Backing store disabled
(==) intel(0): Silken mouse enabled
(II) intel(0): Initializing HW Cursor
(II) intel(0): No memory allocations
(II) intel(0): RandR 1.2 enabled, ignore the following RandR disabled message.
(II) intel(0): DPMS enabled
(==) intel(0): Intel XvMC decoder disabled
(II) intel(0): Set up textured video
(II) intel(0): direct rendering: Failed
(WW) intel(0): Option "DDC" is not used
As you can see on the second last line "direct rendering: failed", but I have absolutely no clue why. And further down in the Xorg.0.log I also found the lines:

Code: Select all

(II) AIGLX: Screen 0 is not DRI2 capable
(II) AIGLX: Screen 0 is not DRI capable
(II) AIGLX: Loaded and initialized /usr/lib/dri/swrast_dri.so
(II) GLX: Initialized DRISWRAST GL provider for screen 0
(II) intel(0): Setting screen physical size to 270 x 203
I don't know if these last lines are the cause that direct rendering fails, or if these lines are caused by the failed direct rendering.

Any help?

Here's my Xorg.conf

Code: Select all

Section "ServerLayout"
        Identifier     "X.org Configured"
        Screen      0  "Screen0" 0 0
        Option         "DRI2" "on"
EndSection

Section "Files"
        FontPath     "/usr/share/fonts/misc:unscaled"
        FontPath     "/usr/share/fonts/Type1/"
        FontPath     "/usr/share/fonts/TTF/"
        ### FontPath     "/usr/share/fonts/OTF"
        FontPath     "/usr/share/fonts/corefonts"
        FontPath     "/usr/share/fonts/freefonts"
        FontPath     "/usr/share/fonts/terminus"
        FontPath     "/usr/share/fonts/ttf-bitstream-vera"
        FontPath     "/usr/share/fonts/unifont"
        FontPath     "/usr/share/fonts/100dpi:unscaled"
        FontPath     "/usr/share/fonts/75dpi:unscaled"
        FontPath     "/usr/share/fonts/artwiz-aleczapka-en:unscaled"
EndSection

Section "Module"
        Load  "glx"
        Load  "extmod"
#       Load  "xtrap"
        Load  "record"
        Load  "GLcore"
#       Load  "ddc"
        Load  "dbe"
        Load  "dri2"
#       Load  "freetype"
EndSection

Section "Monitor"
        DisplaySize       304   228     # mm
        Identifier   "Monitor0"
        VendorName   "AUO"
        ModelName    "f07"
EndSection

Section "Device"
        Identifier  "Card0"
        Driver      "intel"
        VendorName  "Intel Corporation"
        BoardName   "Mobile 915GM/GMS/910GML Express Graphics Controller"
        BusID       "PCI:0:2:0"
#       Option      "AccelMethod" "UXA"
        Option      "Tiling" "false"
        Option      "DRI" "true"
        Option      "DDC" "true"
        Option      "ModeDebug" "on"
EndSection

Section "Screen"
        Identifier "Screen0"
        Device     "Card0"
        Monitor    "Monitor0"
        DefaultDepth 24
        SubSection "Display"
                Viewport   0 0
                Depth     24
                Modes     "1024x768"
        EndSubSection
EndSection

Section "ServerFlags"
        #Option  "AIGLX" "off"
EndSection
and here's the complete Xorg.0.log:

Code: Select all

This is a pre-release version of the X server from The X.Org Foundation.
It is not supported in any way.
Bugs may be filed in the bugzilla at http://bugs.freedesktop.org/.
Select the "xorg" product for bugs you find in this release.
Before reporting bugs in pre-release versions please check the
latest version in the X.Org Foundation git repository.
See http://wiki.x.org/wiki/GitPage for git access instructions.

X.Org X Server 1.6.1.901 (1.6.2 RC 1)
Release Date: 2009-5-8
X Protocol Version 11, Revision 0
Build Operating System: Linux 2.6.29-tuxonice-r3 i686
Current Operating System: Linux shadowstux 2.6.29-tuxonice-r3 #4 Thu Jun 25 19:23:02 CEST 2009 i686
Build Date: 29 June 2009  06:11:37PM

        Before reporting problems, check http://wiki.x.org
        to make sure that you have the latest version.
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 Jul  2 09:18:42 2009
(==) Using config file: "/etc/X11/xorg.conf"
(==) ServerLayout "X.org Configured"
(**) |-->Screen "Screen0" (0)
(**) |   |-->Monitor "Monitor0"
(**) |   |-->Device "Card0"
(**) Option "DRI2" "on"
(==) Automatically adding devices
(==) Automatically enabling devices
(**) FontPath set to:
        /usr/share/fonts/misc:unscaled,
        /usr/share/fonts/Type1/,
        /usr/share/fonts/TTF/,
        /usr/share/fonts/corefonts,
        /usr/share/fonts/freefonts,
        /usr/share/fonts/terminus,
        /usr/share/fonts/ttf-bitstream-vera,
        /usr/share/fonts/unifont,
        /usr/share/fonts/100dpi:unscaled,
        /usr/share/fonts/75dpi:unscaled,
        /usr/share/fonts/artwiz-aleczapka-en:unscaled,
        /usr/share/fonts/misc/,
        /usr/share/fonts/TTF/,
        /usr/share/fonts/OTF,
        /usr/share/fonts/Type1/,
        /usr/share/fonts/100dpi/,
        /usr/share/fonts/75dpi/,
        built-ins
(==) ModulePath set to "/usr/lib/xorg/modules"
(II) Cannot locate a core pointer device.
(II) Cannot locate a core keyboard device.
(II) The server relies on HAL to provide the list of input devices.
        If no devices become available, reconfigure HAL or disable AllowEmptyInput.
(II) Loader magic: 0x3ae0
(II) Module ABI versions:
        X.Org ANSI C Emulation: 0.4
        X.Org Video Driver: 5.0
        X.Org XInput driver : 4.0
        X.Org Server Extension : 2.0
(II) Loader running on linux
(++) using VT number 7

(--) PCI:*(0:0:2:0) 8086:2592:1028:01a4 Intel Corporation Mobile 915GM/GMS/910GML Express Graphics Controller rev 3, Mem @ 0xdff00000/524288, 0xc0000000/268435456, 0xdfec0000/262144, I/O @ 0x0000ec38/8
(--) PCI: (0:0:2:1) 8086:2792:1028:01a4 Intel Corporation Mobile 915GM/GMS/910GML Express Graphics Controller rev 3, Mem @ 0xdff80000/524288
(II) Open ACPI successful (/var/run/acpid.socket)
(II) System resource ranges:
        [0] -1  0       0xffffffff - 0xffffffff (0x1) MX[B]
        [1] -1  0       0x000f0000 - 0x000fffff (0x10000) MX[B]
        [2] -1  0       0x000c0000 - 0x000effff (0x30000) MX[B]
        [3] -1  0       0x00000000 - 0x0009ffff (0xa0000) MX[B]
        [4] -1  0       0x0000ffff - 0x0000ffff (0x1) IX[B]
        [5] -1  0       0x00000000 - 0x00000000 (0x1) IX[B]
(II) "extmod" will be loaded. This was enabled by default and also specified in the config file.
(II) "dbe" will be loaded. This was enabled by default and also specified in the config file.
(II) "glx" will be loaded. This was enabled by default and also specified in the config file.
(II) "record" will be loaded. This was enabled by default and also specified in the config file.
(II) "dri" will be loaded by default.
(II) "dri2" will be loaded. This was enabled by default and also specified in the config file.
(II) LoadModule: "glx"
(II) Loading /usr/lib/xorg/modules/extensions//libglx.so
(II) Module glx: vendor="X.Org Foundation"
        compiled for 1.6.1.901, module version = 1.0.0
        ABI class: X.Org Server Extension, version 2.0
(==) AIGLX enabled
(II) Loading extension GLX
(II) LoadModule: "extmod"
(II) Loading /usr/lib/xorg/modules/extensions//libextmod.so
(II) Module extmod: vendor="X.Org Foundation"
        compiled for 1.6.1.901, module version = 1.0.0
        Module class: X.Org Server Extension
        ABI class: X.Org Server Extension, version 2.0
(II) Loading extension MIT-SCREEN-SAVER
(II) Loading extension XFree86-VidModeExtension
(II) Loading extension XFree86-DGA
(II) Loading extension DPMS
(II) Loading extension XVideo
(II) Loading extension XVideo-MotionCompensation
(II) Loading extension X-Resource
(II) LoadModule: "record"
(II) Loading /usr/lib/xorg/modules/extensions//librecord.so
(II) Module record: vendor="X.Org Foundation"
        compiled for 1.6.1.901, module version = 1.13.0
        Module class: X.Org Server Extension
        ABI class: X.Org Server Extension, version 2.0
(II) Loading extension RECORD
(II) LoadModule: "dbe"
(II) Loading /usr/lib/xorg/modules/extensions//libdbe.so
(II) Module dbe: vendor="X.Org Foundation"
        compiled for 1.6.1.901, module version = 1.0.0
        Module class: X.Org Server Extension
        ABI class: X.Org Server Extension, version 2.0
(II) Loading extension DOUBLE-BUFFER
(II) LoadModule: "dri2"
(II) Loading /usr/lib/xorg/modules/extensions//libdri2.so
(II) Module dri2: vendor="X.Org Foundation"
        compiled for 1.6.1.901, module version = 1.1.0
        ABI class: X.Org Server Extension, version 2.0
(II) Loading extension DRI2
(II) LoadModule: "dri"
(II) Loading /usr/lib/xorg/modules/extensions//libdri.so
(II) Module dri: vendor="X.Org Foundation"
        compiled for 1.6.1.901, module version = 1.0.0
        ABI class: X.Org Server Extension, version 2.0
(II) Loading extension XFree86-DRI
(II) LoadModule: "intel"
(II) Loading /usr/lib/xorg/modules/drivers//intel_drv.so
(II) Module intel: vendor="X.Org Foundation"
        compiled for 1.6.1.901, module version = 2.7.99
        Module class: X.Org Video Driver
        ABI class: X.Org Video Driver, version 5.0
(II) intel: Driver for Intel Integrated Graphics Chipsets: i810,
        i810-dc100, i810e, i815, i830M, 845G, 852GM/855GM, 865G, 915G,
        E7221 (i915), 915GM, 945G, 945GM, 945GME, IGD_GM, IGD_G, 965G, G35,
        965Q, 946GZ, 965GM, 965GME/GLE, G33, Q35, Q33,
        Mobile Intel® GM45 Express Chipset,
        Intel Integrated Graphics Device, G45/G43, Q45/Q43, G41, IGDNG_D,
        IGDNG_M
(II) Primary Device is: PCI 00@00:02:0
(II) resource ranges after xf86ClaimFixedResources() call:
        [0] -1  0       0xffffffff - 0xffffffff (0x1) MX[B]
        [1] -1  0       0x000f0000 - 0x000fffff (0x10000) MX[B]
        [2] -1  0       0x000c0000 - 0x000effff (0x30000) MX[B]
        [3] -1  0       0x00000000 - 0x0009ffff (0xa0000) MX[B]
        [4] -1  0       0x0000ffff - 0x0000ffff (0x1) IX[B]
        [5] -1  0       0x00000000 - 0x00000000 (0x1) IX[B]
(II) resource ranges after probing:
        [0] -1  0       0xffffffff - 0xffffffff (0x1) MX[B]
        [1] -1  0       0x000f0000 - 0x000fffff (0x10000) MX[B]
        [2] -1  0       0x000c0000 - 0x000effff (0x30000) MX[B]
        [3] -1  0       0x00000000 - 0x0009ffff (0xa0000) MX[B]
        [4] 0   0       0x000a0000 - 0x000affff (0x10000) MS[B]
        [5] 0   0       0x000b0000 - 0x000b7fff (0x8000) MS[B]
        [6] 0   0       0x000b8000 - 0x000bffff (0x8000) MS[B]
        [7] -1  0       0x0000ffff - 0x0000ffff (0x1) IX[B]
        [8] -1  0       0x00000000 - 0x00000000 (0x1) IX[B]
        [9] 0   0       0x000003b0 - 0x000003bb (0xc) IS[B]
        [10] 0  0       0x000003c0 - 0x000003df (0x20) IS[B]
drmOpenDevice: node name is /dev/dri/card0
drmOpenDevice: open result is 8, (OK)
drmOpenByBusid: Searching for BusID pci:0000:00:02.0
drmOpenDevice: node name is /dev/dri/card0
drmOpenDevice: open result is 8, (OK)
drmOpenByBusid: drmOpenMinor returns 8
drmOpenByBusid: drmGetBusid reports pci:0000:00:02.0
(**) intel(0): Depth 24, (--) framebuffer bpp 32
(==) intel(0): RGB weight 888
(==) intel(0): Default visual is TrueColor
(**) intel(0): Option "DRI" "true"
(**) intel(0): Option "ModeDebug" "on"
(**) intel(0): Option "Tiling" "false"
(II) intel(0): Integrated Graphics Chipset: Intel(R) 915GM
(--) intel(0): Chipset: "915GM"
(WW) intel(0): libpciaccess reported 0 rom size, guessing 64kB
(II) intel(0): No SDVO device is found in VBT
(II) intel(0): Output VGA1 using monitor section Monitor0
(II) intel(0): Output LVDS1 has no monitor section
(II) intel(0): Output TV1 has no monitor section
(II) intel(0): EDID for output VGA1
(II) intel(0): Not using default mode "640x350" (vrefresh out of range)
(II) intel(0): Not using default mode "640x400" (vrefresh out of range)
(II) intel(0): Not using default mode "720x400" (vrefresh out of range)
(II) intel(0): Not using default mode "640x480" (vrefresh out of range)
(II) intel(0): Not using default mode "640x480" (vrefresh out of range)
(II) intel(0): Not using default mode "640x480" (vrefresh out of range)
(II) intel(0): Not using default mode "800x600" (vrefresh out of range)
(II) intel(0): Not using default mode "800x600" (vrefresh out of range)
(II) intel(0): Not using default mode "800x600" (vrefresh out of range)
(II) intel(0): Not using default mode "800x600" (vrefresh out of range)
(II) intel(0): Not using default mode "1024x768" (vrefresh out of range)
(II) intel(0): Not using default mode "1024x768" (vrefresh out of range)
(II) intel(0): Not using default mode "1024x768" (vrefresh out of range)
(II) intel(0): Not using default mode "1152x864" (vrefresh out of range)
(II) intel(0): Not using default mode "1280x960" (hsync out of range)
(II) intel(0): Not using default mode "1280x960" (vrefresh out of range)
(II) intel(0): Not using default mode "1280x1024" (hsync out of range)
(II) intel(0): Not using default mode "1280x1024" (vrefresh out of range)
(II) intel(0): Not using default mode "1280x1024" (vrefresh out of range)
(II) intel(0): Not using default mode "1600x1200" (hsync out of range)
(II) intel(0): Not using default mode "1600x1200" (vrefresh out of range)
(II) intel(0): Not using default mode "1600x1200" (vrefresh out of range)
(II) intel(0): Not using default mode "1600x1200" (vrefresh out of range)
(II) intel(0): Not using default mode "1600x1200" (vrefresh out of range)
(II) intel(0): Not using default mode "1792x1344" (hsync out of range)
(II) intel(0): Not using default mode "1792x1344" (vrefresh out of range)
(II) intel(0): Not using default mode "1856x1392" (hsync out of range)
(II) intel(0): Not using default mode "1856x1392" (vrefresh out of range)
(II) intel(0): Not using default mode "1920x1440" (hsync out of range)
(II) intel(0): Not using default mode "1920x1440" (vrefresh out of range)
(II) intel(0): Not using default mode "832x624" (vrefresh out of range)
(II) intel(0): Not using default mode "1400x1050" (hsync out of range)
(II) intel(0): Not using default mode "1400x1050" (vrefresh out of range)
(II) intel(0): Not using default mode "1920x1440" (vrefresh out of range)
(II) intel(0): Not using default mode "2048x1536" (hsync out of range)
(II) intel(0): Not using default mode "2048x1536" (vrefresh out of range)
(II) intel(0): Not using default mode "2048x1536" (vrefresh out of range)
(II) intel(0): Printing probed modes for output VGA1
(II) intel(0): Modeline "1024x768"x60.0   65.00  1024 1048 1184 1344  768 771 777 806 -hsync -vsync (48.4 kHz)
(II) intel(0): Modeline "800x600"x60.3   40.00  800 840 968 1056  600 601 605 628 +hsync +vsync (37.9 kHz)
(II) intel(0): Modeline "640x480"x59.9   25.18  640 656 752 800  480 490 492 525 -hsync -vsync (31.5 kHz)
(II) intel(0): EDID for output LVDS1
(II) intel(0): Manufacturer: AUO  Model: f07  Serial#: 16843009
(II) intel(0): Year: 2004  Week: 1
(II) intel(0): EDID Version: 1.3
(II) intel(0): Digital Display Input
(II) intel(0): Max Image Size [cm]: horiz.: 30  vert.: 23
(II) intel(0): Gamma: 2.20
(II) intel(0): No DPMS capabilities specified
(II) intel(0): Supported color encodings: RGB 4:4:4 YCrCb 4:4:4
(II) intel(0): First detailed timing is preferred mode
(II) intel(0): redX: 0.580 redY: 0.340   greenX: 0.310 greenY: 0.550
(II) intel(0): blueX: 0.155 blueY: 0.155   whiteX: 0.313 whiteY: 0.329
(II) intel(0): Manufacturer's mask: 0
(II) intel(0): Supported additional Video Mode:
(II) intel(0): clock: 65.0 MHz   Image Size:  304 x 228 mm
(II) intel(0): h_active: 1024  h_sync: 1048  h_sync_end 1184 h_blank_end 1344 h_border: 0
(II) intel(0): v_active: 768  v_sync: 771  v_sync_end 777 v_blanking: 806 v_border: 0
(II) intel(0):  D8381
(II) intel(0):  ����`@
(II) intel(0): EDID (in hex):
(II) intel(0):  00ffffffffffff0006af070f01010101
(II) intel(0):  010e0103801e17780a87f594574f8c27
(II) intel(0):  27505400000001010101010101010101
(II) intel(0):  01010101010164190040410026301888
(II) intel(0):  360030e4100000180000000000000000
(II) intel(0):  00000000000000000000000000fe0044
(II) intel(0):  383338310042313530584732000000fe
(II) intel(0):  00d0c0b0a88860400001010a2020002a
(II) intel(0): Not using default mode "640x350" (vrefresh out of range)
(II) intel(0): Not using default mode "640x400" (vrefresh out of range)
(II) intel(0): Not using default mode "720x400" (vrefresh out of range)
(II) intel(0): Not using default mode "640x480" (vrefresh out of range)
(II) intel(0): Not using default mode "640x480" (vrefresh out of range)
(II) intel(0): Not using default mode "640x480" (vrefresh out of range)
(II) intel(0): Not using default mode "800x600" (vrefresh out of range)
(II) intel(0): Not using default mode "800x600" (vrefresh out of range)
(II) intel(0): Not using default mode "800x600" (vrefresh out of range)
(II) intel(0): Not using default mode "800x600" (vrefresh out of range)
(II) intel(0): Not using default mode "1024x768" (vrefresh out of range)
(II) intel(0): Not using default mode "1024x768" (vrefresh out of range)
(II) intel(0): Not using default mode "1024x768" (vrefresh out of range)
(II) intel(0): Not using default mode "1152x864" (vrefresh out of range)
(II) intel(0): Not using default mode "1280x960" (hsync out of range)
(II) intel(0): Not using default mode "1280x960" (vrefresh out of range)
(II) intel(0): Not using default mode "1280x1024" (hsync out of range)
(II) intel(0): Not using default mode "1280x1024" (vrefresh out of range)
(II) intel(0): Not using default mode "1280x1024" (vrefresh out of range)
(II) intel(0): Not using default mode "1600x1200" (hsync out of range)
(II) intel(0): Not using default mode "1600x1200" (vrefresh out of range)
(II) intel(0): Not using default mode "1600x1200" (vrefresh out of range)
(II) intel(0): Not using default mode "1600x1200" (vrefresh out of range)
(II) intel(0): Not using default mode "1600x1200" (vrefresh out of range)
(II) intel(0): Not using default mode "1792x1344" (hsync out of range)
(II) intel(0): Not using default mode "1792x1344" (vrefresh out of range)
(II) intel(0): Not using default mode "1856x1392" (hsync out of range)
(II) intel(0): Not using default mode "1856x1392" (vrefresh out of range)
(II) intel(0): Not using default mode "1920x1440" (hsync out of range)
(II) intel(0): Not using default mode "1920x1440" (vrefresh out of range)
(II) intel(0): Not using default mode "832x624" (vrefresh out of range)
(II) intel(0): Not using default mode "1400x1050" (hsync out of range)
(II) intel(0): Not using default mode "1400x1050" (vrefresh out of range)
(II) intel(0): Not using default mode "1920x1440" (vrefresh out of range)
(II) intel(0): Not using default mode "2048x1536" (hsync out of range)
(II) intel(0): Not using default mode "2048x1536" (vrefresh out of range)
(II) intel(0): Not using default mode "2048x1536" (vrefresh out of range)
(II) intel(0): Printing probed modes for output LVDS1
(II) intel(0): Modeline "1024x768"x60.0   65.00  1024 1048 1184 1344  768 771 777 806 -hsync -vsync (48.4 kHz)
(II) intel(0): Modeline "800x600"x60.3   40.00  800 840 968 1056  600 601 605 628 +hsync +vsync (37.9 kHz)
(II) intel(0): Modeline "640x480"x59.9   25.18  640 656 752 800  480 490 492 525 -hsync -vsync (31.5 kHz)
(II) intel(0): EDID for output TV1
(II) intel(0): Not using default mode "640x350" (vrefresh out of range)
(II) intel(0): Not using default mode "640x400" (vrefresh out of range)
(II) intel(0): Not using default mode "720x400" (vrefresh out of range)
(II) intel(0): Not using default mode "640x480" (vrefresh out of range)
(II) intel(0): Not using default mode "640x480" (vrefresh out of range)
(II) intel(0): Not using default mode "640x480" (vrefresh out of range)
(II) intel(0): Not using default mode "800x600" (vrefresh out of range)
(II) intel(0): Not using default mode "800x600" (vrefresh out of range)
(II) intel(0): Not using default mode "800x600" (vrefresh out of range)
(II) intel(0): Not using default mode "800x600" (vrefresh out of range)
(II) intel(0): Not using default mode "1024x768" (vrefresh out of range)
(II) intel(0): Not using default mode "1024x768" (vrefresh out of range)
(II) intel(0): Not using default mode "1024x768" (vrefresh out of range)
(II) intel(0): Not using default mode "1152x864" (vrefresh out of range)
(II) intel(0): Not using default mode "1280x960" (hsync out of range)
(II) intel(0): Not using default mode "1280x960" (vrefresh out of range)
(II) intel(0): Not using default mode "1280x1024" (hsync out of range)
(II) intel(0): Not using default mode "1280x1024" (vrefresh out of range)
(II) intel(0): Not using default mode "1280x1024" (vrefresh out of range)
(II) intel(0): Not using default mode "1600x1200" (hsync out of range)
(II) intel(0): Not using default mode "1600x1200" (vrefresh out of range)
(II) intel(0): Not using default mode "1600x1200" (vrefresh out of range)
(II) intel(0): Not using default mode "1600x1200" (vrefresh out of range)
(II) intel(0): Not using default mode "1600x1200" (vrefresh out of range)
(II) intel(0): Not using default mode "1792x1344" (hsync out of range)
(II) intel(0): Not using default mode "1792x1344" (vrefresh out of range)
(II) intel(0): Not using default mode "1856x1392" (hsync out of range)
(II) intel(0): Not using default mode "1856x1392" (vrefresh out of range)
(II) intel(0): Not using default mode "1920x1440" (hsync out of range)
(II) intel(0): Not using default mode "1920x1440" (vrefresh out of range)
(II) intel(0): Not using default mode "832x624" (vrefresh out of range)
(II) intel(0): Not using default mode "1400x1050" (hsync out of range)
(II) intel(0): Not using default mode "1400x1050" (vrefresh out of range)
(II) intel(0): Not using default mode "1920x1440" (vrefresh out of range)
(II) intel(0): Not using default mode "2048x1536" (hsync out of range)
(II) intel(0): Not using default mode "2048x1536" (vrefresh out of range)
(II) intel(0): Not using default mode "2048x1536" (vrefresh out of range)
(II) intel(0): Printing probed modes for output TV1
(II) intel(0): Modeline "1024x768"x60.0   65.00  1024 1048 1184 1344  768 771 777 806 -hsync -vsync (48.4 kHz)
(II) intel(0): Modeline "800x600"x60.3   40.00  800 840 968 1056  600 601 605 628 +hsync +vsync (37.9 kHz)
(II) intel(0): Modeline "640x480"x59.9   25.18  640 656 752 800  480 490 492 525 -hsync -vsync (31.5 kHz)
(II) intel(0): Output VGA1 disconnected
(II) intel(0): Output LVDS1 connected
(II) intel(0): Output TV1 connected
(II) intel(0): Using user preference for initial modes
(II) intel(0): Output LVDS1 using initial mode 1024x768
(II) intel(0): Output TV1 using initial mode 1024x768
(==) intel(0): video overlay key set to 0x101fe
(==) intel(0): Using gamma correction (1.0, 1.0, 1.0)
(**) intel(0): Display dimensions: (304, 228) mm
(**) intel(0): DPI set to (85, 85)
(II) Loading sub module "fb"
(II) LoadModule: "fb"
(II) Loading /usr/lib/xorg/modules//libfb.so
(II) Module fb: vendor="X.Org Foundation"
        compiled for 1.6.1.901, module version = 1.0.0
        ABI class: X.Org ANSI C Emulation, version 0.4
(II) Loading sub module "dri2"
(II) LoadModule: "dri2"
(II) Reloading /usr/lib/xorg/modules/extensions//libdri2.so
(==) Depth 24 pixmap format is 32 bpp
(II) do I need RAC?  No, I don't.
(II) resource ranges after preInit:
        [0] -1  0       0xffffffff - 0xffffffff (0x1) MX[B]
        [1] -1  0       0x000f0000 - 0x000fffff (0x10000) MX[B]
        [2] -1  0       0x000c0000 - 0x000effff (0x30000) MX[B]
        [3] -1  0       0x00000000 - 0x0009ffff (0xa0000) MX[B]
        [4] 0   0       0x000a0000 - 0x000affff (0x10000) MS[B]
        [5] 0   0       0x000b0000 - 0x000b7fff (0x8000) MS[B]
        [6] 0   0       0x000b8000 - 0x000bffff (0x8000) MS[B]
        [7] -1  0       0x0000ffff - 0x0000ffff (0x1) IX[B]
        [8] -1  0       0x00000000 - 0x00000000 (0x1) IX[B]
        [9] 0   0       0x000003b0 - 0x000003bb (0xc) IS[B]
        [10] 0  0       0x000003c0 - 0x000003df (0x20) IS[B]
(**) intel(0): Framebuffer compression disabled
(**) intel(0): Tiling disabled
(**) intel(0): SwapBuffers wait enabled
(==) intel(0): VideoRam: 262144 KB
(II) intel(0): Attempting memory allocation with untiled buffers.
(II) intel(0): Untiled allocation successful.
(II) UXA(0): Driver registered support for the following operations:
(II)         solid
(II)         copy
(II)         composite (RENDER acceleration)
(==) intel(0): Backing store disabled
(==) intel(0): Silken mouse enabled
(II) intel(0): Initializing HW Cursor
(II) intel(0): No memory allocations
(II) intel(0): RandR 1.2 enabled, ignore the following RandR disabled message.
(II) intel(0): DPMS enabled
(==) intel(0): Intel XvMC decoder disabled
(II) intel(0): Set up textured video
(II) intel(0): direct rendering: Failed
(WW) intel(0): Option "DDC" is not used
(--) RandR disabled
(II) Initializing built-in extension Generic Event Extension
(II) Initializing built-in extension SHAPE
(II) Initializing built-in extension MIT-SHM
(II) Initializing built-in extension XInputExtension
(II) Initializing built-in extension XTEST
(II) Initializing built-in extension BIG-REQUESTS
(II) Initializing built-in extension SYNC
(II) Initializing built-in extension XKEYBOARD
(II) Initializing built-in extension XC-MISC
(II) Initializing built-in extension XINERAMA
(II) Initializing built-in extension XFIXES
(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) AIGLX: Screen 0 is not DRI2 capable
(II) AIGLX: Screen 0 is not DRI capable
(II) AIGLX: Loaded and initialized /usr/lib/dri/swrast_dri.so
(II) GLX: Initialized DRISWRAST GL provider for screen 0
(II) intel(0): Setting screen physical size to 270 x 203
(II) config/hal: Adding input device SynPS/2 Synaptics TouchPad
(II) LoadModule: "synaptics"
(II) Loading /usr/lib/xorg/modules/input//synaptics_drv.so
(II) Module synaptics: vendor="X.Org Foundation"
        compiled for 1.6.1.901, module version = 1.1.2
        Module class: X.Org XInput Driver
        ABI class: X.Org XInput driver, version 4.0
(II) Synaptics touchpad driver version 1.1.2
(**) Option "Device" "/dev/input/event5"
(II) SynPS/2 Synaptics TouchPad: x-axis range 1472 - 5472
(II) SynPS/2 Synaptics TouchPad: y-axis range 1408 - 4448
(II) SynPS/2 Synaptics TouchPad: pressure range 0 - 255
(II) SynPS/2 Synaptics TouchPad: finger width range 0 - 0
(II) SynPS/2 Synaptics TouchPad: buttons: left right middle double triple
(--) SynPS/2 Synaptics TouchPad: touchpad found
(**) SynPS/2 Synaptics TouchPad: always reports core events
(II) XINPUT: Adding extended input device "SynPS/2 Synaptics TouchPad" (type: TOUCHPAD)
(**) SynPS/2 Synaptics TouchPad: (accel) keeping acceleration scheme 1
(**) SynPS/2 Synaptics TouchPad: (accel) filter chain progression: 2.00
(**) SynPS/2 Synaptics TouchPad: (accel) filter stage 0: 20.00 ms
(**) SynPS/2 Synaptics TouchPad: (accel) set acceleration profile 0
(--) SynPS/2 Synaptics TouchPad: touchpad found
(II) config/hal: Adding input device AT Translated Set 2 keyboard
(II) LoadModule: "evdev"
(II) Loading /usr/lib/xorg/modules/input//evdev_drv.so
(II) Module evdev: vendor="X.Org Foundation"
        compiled for 1.6.1.901, module version = 2.2.2
        Module class: X.Org XInput Driver
        ABI class: X.Org XInput driver, version 4.0
(**) AT Translated Set 2 keyboard: always reports core events
(**) AT Translated Set 2 keyboard: Device: "/dev/input/event4"
(II) AT Translated Set 2 keyboard: Found keys
(II) AT Translated Set 2 keyboard: Configuring as keyboard
(II) XINPUT: Adding extended input device "AT Translated Set 2 keyboard" (type: KEYBOARD)
(**) Option "xkb_rules" "evdev"
(**) Option "xkb_model" "evdev"
(**) Option "xkb_layout" "ch"
(**) Option "xkb_variant" "de,winkeys"
Thanks for any help on this.

I'm using xf86-video-intel-9999, libdrm-9999, xorg-server-1.6.1.901-r5 and mesa-9999. Should I downgrade to get UXA working?
Top
Havin_it
Veteran
Veteran
Posts: 1343
Joined: Sun Jul 17, 2005 10:26 am
Location: Edinburgh, UK
Contact:
Contact Havin_it
Website

  • Quote

Post by Havin_it » Thu Jul 02, 2009 11:29 am

@marcelser, the first thing I'd recommend is to downgrade to the previous revision of xorg-server. The -r5 revision caused the DRI failure you're observing for me and a number of others - the issue has its own thread on here.
Top
marcelser
Tux's lil' helper
Tux's lil' helper
Posts: 106
Joined: Thu Sep 30, 2004 9:53 pm

downgrading seems to work but still no opengl

  • Quote

Post by marcelser » Fri Jul 03, 2009 7:26 am

Havin_it wrote:@marcelser, the first thing I'd recommend is to downgrade to the previous revision of xorg-server. The -r5 revision caused the DRI failure you're observing for me and a number of others - the issue has its own thread on here.
Hi, I just downgraded to xorg-server -r4 and now the xorg log-file looks very promising like this:

Code: Select all

(II) intel(0): Tiled allocation successful.
(II) UXA(0): Driver registered support for the following operations:
(II)         solid
(II)         copy
(II)         composite (RENDER acceleration)
(==) intel(0): Backing store disabled
(==) intel(0): Silken mouse enabled
(II) intel(0): Initializing HW Cursor
(II) intel(0): Fixed memory allocation layout:
(II) intel(0): 0x00000000-0x0fff4fff: DRI memory manager (262100 kB)
(II) intel(0): 0x00000000:            end of aperture
(II) intel(0): BO memory allocation layout:
(II) intel(0): 0x00000000:            start of memory manager
(II) intel(0): unpinned          : front buffer (4096 kB) X tiled
(II) intel(0): unpinned          : HW cursors (40 kB)
(II) intel(0): 0x0fff5000:            end of memory manager
(II) intel(0): RandR 1.2 enabled, ignore the following RandR disabled message.
(II) intel(0): DPMS enabled
(==) intel(0): Intel XvMC decoder disabled
(II) intel(0): Set up textured video
(II) intel(0): direct rendering: DRI2 Enabled
and nearly at the end of the logfile, it also seems that AIGLX and GLX are initialised:

Code: Select all

(II) AIGLX: enabled GLX_MESA_copy_sub_buffer
(II) AIGLX: enabled GLX_SGI_swap_control and GLX_MESA_swap_control
(II) AIGLX: GLX_EXT_texture_from_pixmap backed by buffer objects
(II) AIGLX: Loaded and initialized /usr/lib/dri/i915_dri.so
(II) GLX: Initialized DRI2 GL provider for screen 0
(II) intel(0): Setting screen physical size to 304 x 228
What I don't understand is, when I run glxinfo it still says that it's using "software rasterizer" and my opengl screen savers look more like a slideshow as a screen-saver.

What do I have to do, to make opengl working, because it seems dri2/uxa is now loaded but not used as far as I can tell.

Thanks for any help.

Marc
Top
asturm
Developer
Developer
Posts: 9496
Joined: Thu Apr 05, 2007 4:07 pm

  • Quote

Post by asturm » Fri Jul 03, 2009 12:00 pm

Just to rule it out: rename your xorg.conf to xorg.conf.old

You shouldn't need it anymore, everything including DRI runs ootb.

EDIT: Of course assuming you have already migrated to hal and evdev for configuring your input devices.

Do you ACCEPT_KEYWORDS="~arch" or are you maintaining a stable system with xorg.conf keywords file?
Top
Post Reply

34 posts
  • 1
  • 2
  • Next

Return to “Desktop Environments”

Jump to
  • Assistance
  • ↳   News & Announcements
  • ↳   Frequently Asked Questions
  • ↳   Installing Gentoo
  • ↳   Multimedia
  • ↳   Desktop Environments
  • ↳   Networking & Security
  • ↳   Kernel & Hardware
  • ↳   Portage & Programming
  • ↳   Gamers & Players
  • ↳   Other Things Gentoo
  • ↳   Unsupported Software
  • Discussion & Documentation
  • ↳   Documentation, Tips & Tricks
  • ↳   Gentoo Chat
  • ↳   Gentoo Forums Feedback
  • ↳   Duplicate Threads
  • International Gentoo Users
  • ↳   中文 (Chinese)
  • ↳   Dutch
  • ↳   Finnish
  • ↳   French
  • ↳   Deutsches Forum (German)
  • ↳   Diskussionsforum
  • ↳   Deutsche Dokumentation
  • ↳   Greek
  • ↳   Forum italiano (Italian)
  • ↳   Forum di discussione italiano
  • ↳   Risorse italiane (documentazione e tools)
  • ↳   Polskie forum (Polish)
  • ↳   Instalacja i sprzęt
  • ↳   Polish OTW
  • ↳   Portuguese
  • ↳   Documentação, Ferramentas e Dicas
  • ↳   Russian
  • ↳   Scandinavian
  • ↳   Spanish
  • ↳   Other Languages
  • Architectures & Platforms
  • ↳   Gentoo on ARM
  • ↳   Gentoo on PPC
  • ↳   Gentoo on Sparc
  • ↳   Gentoo on Alternative Architectures
  • ↳   Gentoo on AMD64
  • ↳   Gentoo for Mac OS X (Portage for Mac OS X)
  • Board index
  • All times are UTC
  • Delete cookies

© 2001–2026 Gentoo Foundation, Inc.

Powered by phpBB® Forum Software © phpBB Limited

Privacy Policy

 

 

magic