You are not logged in.

#1 2009-06-29 09:53:10

SoleSoul
Member
From: Israel
Registered: 2009-06-29
Posts: 319

New to arch, Intel graphics, can't set direct rendering

Greetings everybody.
As you can see this is my first time here.
I used Zenwalk for the last year or so with great success, but since the OS was "too working" it started to get boring.
I wanted to set up my os as I want so I came here.

I chose not to go with a DE but install each program separately.
I installed compiz and cairo-dock (svn from AUR) and it works nicely.

The problem is I think that graphics acceleration does not work.
There are some indicators:
1) When I type startx it complains:
(EE) Failed to load module "i810" (module does not exist, 0)
(EE) Failed to load module "fbdev" (module does not exist, 0)

2) "glxinfo | grep direct" outputs "direct rendering: No (LIBGL_ALWAYS_INDIRECT set)"

3) fusion-icon starts compiz with --indirect-rendering tag.

I use hal with no xorg.conf.
System fully upgraded with kernel ver 2.26.30
Everything else works ok.

Specs:
Lenovo T1 8898-6DG
00:02.0 VGA compatible controller: Intel Corporation Mobile GM965/GL960 Integrated Graphics Controller (rev 0c)
00:02.1 Display controller: Intel Corporation Mobile GM965/GL960 Integrated Graphics Controller (rev 0c)

I consulted the wiki and google for 4 days now and I couldn't solve it myself.
Thank you.

Offline

#2 2009-06-29 12:35:54

panosk
Member
From: Athens, Greece
Registered: 2008-10-29
Posts: 241

Re: New to arch, Intel graphics, can't set direct rendering

Hello and welcome to Arch,

I use KDE so maybe I won't be much useful, but anyways. When I was using gnome+compiz, glxinfo was always giving me "direct rendering: No (LIBGL_ALWAYS_INDIRECT set)". However, system was very responsive and compiz ran flawlessly.
Now, in my KDE installation (intel graphics, no xorg.conf), grepping xorg log reveals the same errors (EE), but graphics performance is very good (Kwin effects run very smoothly, World of Padman runs very fast with high visual effects). However, glxinfo shows direct rendering.

Anyways, is your graphics performance OK? If it is, I think you shouldn't worry about glxinfo's output. I remember I was searching a lot too about this issue when I was in gnome+compiz, and had read that indirect rendering was necessary for compiz to run smoothly (in intel graphics). Then again, things may have changed so maybe you can get direct rendering with compiz, in which case other archers may be able to help more.

Cheers

Offline

#3 2009-06-29 13:36:46

blasse
Member
From: Poland
Registered: 2008-04-24
Posts: 303

Re: New to arch, Intel graphics, can't set direct rendering

SoleSoul wrote:

I use hal with no xorg.conf.
System fully upgraded with kernel ver 2.26.30
Everything else works ok.

Fully upgraded with core/extra or with testing enabled?

What version of intel driver is used? (post pacman -Qs xf86-video-intel output)


Proud ex-maintainer of firefox-pgo

Offline

#4 2009-06-29 13:42:31

eldragon
Member
From: Buenos Aires
Registered: 2008-11-18
Posts: 1,029

Re: New to arch, Intel graphics, can't set direct rendering

more useful debug info if you post /var/log/Xorg.0.log to see what display driver is being loaded...
i asume  you dont have KMS enabled yet

EDIT: failing to load those modules is ok, if you plan to use xf86-video-intel

Last edited by eldragon (2009-06-29 13:43:16)

Offline

#5 2009-06-29 14:30:29

SoleSoul
Member
From: Israel
Registered: 2009-06-29
Posts: 319

Re: New to arch, Intel graphics, can't set direct rendering

Thank you for your answers.

Anyways, is your graphics performance OK?

Well, the computer is fast so it's working quite well, but I think that it's not using the graphics card accelertion.

Fully upgraded with core/extra or with testing enabled?

No, I didn't enable testing in pacman.conf so I think it's disabled.

What version of intel driver is used? (post pacman -Qs xf86-video-intel output)

local/xf86-video-intel 2.7.1-1 (xorg-video-drivers)

more useful debug info if you post /var/log/Xorg.0.log to see what display driver is being loaded...

I'll post it below.

i asume  you dont have KMS enabled yet

I didn't do it manually so

return (is it enabled by default in 2.26.30?)

big_smile

failing to load those modules is ok, if you plan to use xf86-video-intel

I thought that the big question here is why xorg tries to load them. AFAIK i810 is not the right driver at all...


Keep in mind that I may be missing something elementary because I'm new to arch.
BTW, direct rendering works with other linuxes on this computer so I assume the problem is not setting it up properly.

Here is the Xorg.0.log: (...It's so long...)

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-ARCH i686 
Current Operating System: Linux blackpearl 2.6.30-ARCH #1 SMP PREEMPT Fri Jun 19 21:25:17 UTC 2009 i686
Build Date: 28 May 2009  10:40:05PM
 
    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: Mon Jun 29 17:11:21 2009
(II) Loader magic: 0x1a40
(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) Intel Corporation Mobile GM965/GL960 Integrated Graphics Controller rev 12, Mem @ 0xf8100000/1048576, 0xe0000000/268435456, I/O @ 0x00001800/8
(--) PCI: (0@0:2:1) Intel Corporation Mobile GM965/GL960 Integrated Graphics Controller rev 12, Mem @ 0xf8200000/1048576
(==) Using default built-in configuration (39 lines)
(==) --- Start of built-in configuration ---
    Section "Device"
        Identifier    "Builtin Default intel Device 0"
        Driver    "intel"
    EndSection
    Section "Screen"
        Identifier    "Builtin Default intel Screen 0"
        Device    "Builtin Default intel Device 0"
    EndSection
    Section "Device"
        Identifier    "Builtin Default i810 Device 0"
        Driver    "i810"
    EndSection
    Section "Screen"
        Identifier    "Builtin Default i810 Screen 0"
        Device    "Builtin Default i810 Device 0"
    EndSection
    Section "Device"
        Identifier    "Builtin Default vesa Device 0"
        Driver    "vesa"
    EndSection
    Section "Screen"
        Identifier    "Builtin Default vesa Screen 0"
        Device    "Builtin Default vesa Device 0"
    EndSection
    Section "Device"
        Identifier    "Builtin Default fbdev Device 0"
        Driver    "fbdev"
    EndSection
    Section "Screen"
        Identifier    "Builtin Default fbdev Screen 0"
        Device    "Builtin Default fbdev Device 0"
    EndSection
    Section "ServerLayout"
        Identifier    "Builtin Default Layout"
        Screen    "Builtin Default intel Screen 0"
        Screen    "Builtin Default i810 Screen 0"
        Screen    "Builtin Default vesa Screen 0"
        Screen    "Builtin Default fbdev Screen 0"
    EndSection
(==) --- End of built-in configuration ---
(==) ServerLayout "Builtin Default Layout"
(**) |-->Screen "Builtin Default intel Screen 0" (0)
(**) |   |-->Monitor "<default monitor>"
(**) |   |-->Device "Builtin Default intel Device 0"
(==) No monitor specified for screen "Builtin Default intel Screen 0".
    Using a default monitor configuration.
(**) |-->Screen "Builtin Default i810 Screen 0" (1)
(**) |   |-->Monitor "<default monitor>"
(**) |   |-->Device "Builtin Default i810 Device 0"
(==) No monitor specified for screen "Builtin Default i810 Screen 0".
    Using a default monitor configuration.
(**) |-->Screen "Builtin Default vesa Screen 0" (2)
(**) |   |-->Monitor "<default monitor>"
(**) |   |-->Device "Builtin Default vesa Device 0"
(==) No monitor specified for screen "Builtin Default vesa Screen 0".
    Using a default monitor configuration.
(**) |-->Screen "Builtin Default fbdev Screen 0" (3)
(**) |   |-->Monitor "<default monitor>"
(**) |   |-->Device "Builtin Default fbdev Device 0"
(==) No monitor specified for screen "Builtin Default fbdev Screen 0".
    Using a default monitor configuration.
(==) Automatically adding devices
(==) Automatically enabling devices
(WW) The directory "/usr/share/fonts/TTF" does not exist.
    Entry deleted from font path.
(WW) The directory "/usr/share/fonts/Type1" does not exist.
    Entry deleted from font path.
(==) FontPath set to:
    /usr/share/fonts/misc,
    /usr/share/fonts/100dpi:unscaled,
    /usr/share/fonts/75dpi:unscaled,
    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.
(WW) Open ACPI failed (/var/run/acpid.socket) (No such file or directory)
(II) No APM support in BIOS or kernel
(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) 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: "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: "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: "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: "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: "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.0.0
    ABI class: X.Org Server Extension, version 2.0
(II) Loading extension DRI2
(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, module version = 2.7.1
    Module class: X.Org Video Driver
    ABI class: X.Org Video Driver, version 5.0
(II) LoadModule: "i810"
(WW) Warning, couldn't open module i810
(II) UnloadModule: "i810"
(EE) Failed to load module "i810" (module does not exist, 0)
(II) LoadModule: "vesa"
(II) Loading /usr/lib/xorg/modules/drivers//vesa_drv.so
(II) Module vesa: vendor="X.Org Foundation"
    compiled for 1.6.0, module version = 2.2.0
    Module class: X.Org Video Driver
    ABI class: X.Org Video Driver, version 5.0
(II) LoadModule: "fbdev"
(WW) Warning, couldn't open module fbdev
(II) UnloadModule: "fbdev"
(EE) Failed to load module "fbdev" (module does not exist, 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
(II) VESA: driver for VESA chipsets: vesa
(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]
(WW) Falling back to old probe method for vesa
(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]
(II) Loading sub module "vgahw"
(II) LoadModule: "vgahw"
(II) Loading /usr/lib/xorg/modules//libvgahw.so
(II) Module vgahw: vendor="X.Org Foundation"
    compiled for 1.6.1.901, module version = 0.1.0
    ABI class: X.Org Video Driver, version 5.0
(II) Loading sub module "ramdac"
(II) LoadModule: "ramdac"
(II) Module "ramdac" already built-in
(II) intel(0): Creating default Display subsection in Screen section
    "Builtin Default intel Screen 0" for depth/fbbpp 24/32
(==) intel(0): Depth 24, (--) framebuffer bpp 32
(==) intel(0): RGB weight 888
(==) intel(0): Default visual is TrueColor
(II) intel(0): Integrated Graphics Chipset: Intel(R) 965GM
(--) intel(0): Chipset: "965GM"
(--) intel(0): Linear framebuffer at 0xE0000000
(--) intel(0): IO registers at addr 0xF8100000
(WW) intel(0): libpciaccess reported 0 rom size, guessing 64kB
(==) intel(0): Using EXA for acceleration
(II) intel(0): 2 display pipes available.
(II) Loading sub module "ddc"
(II) LoadModule: "ddc"
(II) Module "ddc" already built-in
(II) Loading sub module "i2c"
(II) LoadModule: "i2c"
(II) Module "i2c" already built-in
(II) intel(0): Output VGA has no monitor section
(II) intel(0): Output LVDS has no monitor section
(II) intel(0): I2C bus "LVDSDDC_C" initialized.
(II) intel(0): Attempting to determine panel fixed mode.
(II) intel(0): I2C device "LVDSDDC_C:E-EDID segment register" registered at address 0x60.
(II) intel(0): I2C device "LVDSDDC_C:ddc2" registered at address 0xA0.
(II) intel(0): EDID vendor "LEN", prod id 16416
(II) intel(0): I2C bus "SDVOCTRL_E for SDVOB" initialized.
(II) intel(0): I2C device "SDVOCTRL_E for SDVOB:SDVO Controller B" registered at address 0x70.
(II) intel(0): I2C bus "SDVOB DDC Bus" initialized.
(II) intel(0): Output TMDS-1 has no monitor section
(II) intel(0): SDVOB: device VID/DID: 02:3C.06, clock range 25.0MHz - 200.0MHz
(II) intel(0): SDVOB: 1 input channel
(II) intel(0): SDVOB: TMDS0 output reported
(II) intel(0): I2C bus "SDVOCTRL_E for SDVOC" initialized.
(II) intel(0): I2C device "SDVOCTRL_E for SDVOC:SDVO Controller C" registered at address 0x72.
(II) intel(0): No SDVO device found on SDVOC
(II) intel(0): I2C device "SDVOCTRL_E for SDVOC:SDVO Controller C" removed.
(II) intel(0): I2C bus "SDVOCTRL_E for SDVOC" removed.
(II) intel(0): Current clock rate multiplier: 1
(II) intel(0): Resizable framebuffer: not available (1 3)
(II) intel(0): EDID vendor "LEN", prod id 16416
(II) intel(0): Output VGA disconnected
(II) intel(0): Output LVDS connected
(II) intel(0): Output TMDS-1 disconnected
(II) intel(0): Using exact sizes for initial modes
(II) intel(0): Output LVDS using initial mode 1024x768
(II) intel(0): detected 512 kB GTT.
(II) intel(0): detected 7676 kB stolen memory.
(==) intel(0): video overlay key set to 0x101fe
(==) intel(0): Using gamma correction (1.0, 1.0, 1.0)
(==) intel(0): DPI set to (96, 96)
(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 "exa"
(II) LoadModule: "exa"
(II) Loading /usr/lib/xorg/modules//libexa.so
(II) Module exa: vendor="X.Org Foundation"
    compiled for 1.6.1.901, module version = 2.4.0
    ABI class: X.Org Video Driver, version 5.0
(II) intel(0): Comparing regs from server start up to After PreInit
(WW) intel(0): Register 0x61200 (PP_STATUS) changed from 0xc0000008 to 0xd0000009
(WW) intel(0): PP_STATUS before: on, ready, sequencing idle
(WW) intel(0): PP_STATUS after: on, ready, sequencing on
(II) UnloadModule: "vesa"
(II) Unloading /usr/lib/xorg/modules/drivers//vesa_drv.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](OprD)
    [5] 0    0    0x000b0000 - 0x000b7fff (0x8000) MS[b](OprD)
    [6] 0    0    0x000b8000 - 0x000bffff (0x8000) MS[b](OprD)
    [7] -1    0    0x0000ffff - 0x0000ffff (0x1) IX[b]
    [8] -1    0    0x00000000 - 0x00000000 (0x1) IX[b]
    [9] 0    0    0x000003b0 - 0x000003bb (0xc) IS[b](OprU)
    [10] 0    0    0x000003c0 - 0x000003df (0x20) IS[b](OprU)
(II) intel(0): Kernel reported 481024 total, 1 used
(II) intel(0): I830CheckAvailableMemory: 1924092 kB available
(WW) intel(0): DRI2 requires UXA
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
drmOpenByBusid: Searching for BusID pci:0000:00:02.0
drmOpenDevice: node name is /dev/dri/card0
drmOpenDevice: open result is 10, (OK)
drmOpenByBusid: drmOpenMinor returns 10
drmOpenByBusid: drmGetBusid reports pci:0000:00:02.0
(II) [drm] loaded kernel module for "i915" driver.
(II) [drm] DRM interface version 1.3
(II) [drm] DRM open master succeeded.
(II) intel(0): [drm] Using the DRM lock SAREA also for drawables.
(II) intel(0): [drm] framebuffer mapped by ddx driver
(II) intel(0): [drm] added 1 reserved context for kernel
(II) intel(0): X context handle = 0x1
(II) intel(0): [drm] installed DRM signal handler
(**) intel(0): Framebuffer compression disabled
(**) intel(0): Tiling enabled
(==) intel(0): VideoRam: 262144 KB
(II) intel(0): Attempting memory allocation with tiled buffers.
(II) intel(0): Tiled allocation successful.
(II) intel(0): [drm] Registers = 0xf8100000
(II) intel(0): [dri] visual configs initialized
(II) intel(0): vgaHWGetIOBase: hwp->IOBase is 0x03d0, hwp->PIOOffset is 0x0000
(II) EXA(0): Offscreen pixmap area of 12582912 bytes
(II) EXA(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): [DRI] installation complete
(II) intel(0): Current clock rate multiplier: 1
(II) intel(0): xf86BindGARTMemory: bind key 0 at 0x0f400000 (pgoffset 62464)
(II) intel(0): Fixed memory allocation layout:
(II) intel(0): 0x00000000-0x00000fff: power context (4 kB)
(II) intel(0): 0x0077f000:            end of stolen memory
(II) intel(0): 0x0077f000-0x0f3fffff: DRI memory manager (242180 kB)
(II) intel(0): 0x0f400000-0x0fffffff: exa offscreen (12288 kB)
(II) intel(0): 0x10000000:            end of aperture
(II) intel(0): BO memory allocation layout:
(II) intel(0): 0x0077f000:            start of memory manager
(II) intel(0): 0x0079f000-0x00b9efff: depth buffer (4096 kB) Y tiled
(II) intel(0): 0x00b9f000-0x00f9efff: back buffer (4096 kB) X tiled
(II) intel(0): 0x00f9f000-0x0139efff: front buffer (4096 kB) X tiled
(II) intel(0): 0x0139f000-0x0139ffff: overlay registers (4 kB)
(II) intel(0): 0x013a0000-0x013a9fff: HW cursors (40 kB)
(II) intel(0): 0x0f400000:            end of memory manager
(II) intel(0): using SSC reference clock of 100 MHz
(II) intel(0): Selecting standard 18 bit TMDS pixel format.
(II) intel(0): [drm] mapped front buffer at 0xe0f9f000, handle = 0xe0f9f000
(II) intel(0): [drm] mapped back buffer at 0xe0b9f000, handle = 0xe0b9f000
(II) intel(0): [drm] mapped depth buffer at 0xe079f000, handle = 0xe079f000
(II) intel(0): Output configuration:
(II) intel(0):   Pipe A is off
(II) intel(0):   Display plane A is now disabled and connected to pipe A.
(II) intel(0):   Pipe B is on
(II) intel(0):   Display plane B is now enabled and connected to pipe B.
(II) intel(0):   Output VGA is connected to pipe none
(II) intel(0):   Output LVDS is connected to pipe B
(II) intel(0):   Output TMDS-1 is connected to pipe none
(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): Set up overlay video
(II) intel(0): direct rendering: XF86DRI Enabled
(--) 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 SECURITY
(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
drmOpenDevice: node name is /dev/dri/card0
drmOpenDevice: open result is 11, (OK)
drmOpenByBusid: Searching for BusID pci:0000:00:02.0
drmOpenDevice: node name is /dev/dri/card0
drmOpenDevice: open result is 11, (OK)
drmOpenByBusid: drmOpenMinor returns 11
drmOpenByBusid: drmGetBusid reports pci:0000:00:02.0
(II) AIGLX: enabled GLX_SGI_make_current_read
(II) AIGLX: enabled GLX_MESA_copy_sub_buffer
(II) AIGLX: enabled GLX_SGI_swap_control and GLX_MESA_swap_control
(II) AIGLX: enabled GLX_texture_from_pixmap with driver support
(II) AIGLX: Loaded and initialized /usr/lib/xorg/modules/dri/i965_dri.so
(II) GLX: Initialized DRI GL provider for screen 0
(II) intel(0): Setting screen physical size to 286 x 214
(II) config/hal: Adding input device Video Bus
(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, module version = 2.2.2
    Module class: X.Org XInput Driver
    ABI class: X.Org XInput driver, version 4.0
(**) Video Bus: always reports core events
(**) Video Bus: Device: "/dev/input/event10"
(II) Video Bus: Found keys
(II) Video Bus: Configuring as keyboard
(II) XINPUT: Adding extended input device "Video Bus" (type: KEYBOARD)
(**) Option "xkb_rules" "evdev"
(**) Option "xkb_model" "evdev"
(**) Option "xkb_layout" "us"
(II) config/hal: Adding input device TPPS/2 IBM TrackPoint
(**) TPPS/2 IBM TrackPoint: always reports core events
(**) TPPS/2 IBM TrackPoint: Device: "/dev/input/event9"
(II) TPPS/2 IBM TrackPoint: Found 3 mouse buttons
(II) TPPS/2 IBM TrackPoint: Found x and y relative axes
(II) TPPS/2 IBM TrackPoint: Configuring as mouse
(**) TPPS/2 IBM TrackPoint: YAxisMapping: buttons 4 and 5
(**) TPPS/2 IBM TrackPoint: EmulateWheelButton: 4, EmulateWheelInertia: 10, EmulateWheelTimeout: 200
(II) XINPUT: Adding extended input device "TPPS/2 IBM TrackPoint" (type: MOUSE)
(**) TPPS/2 IBM TrackPoint: (accel) keeping acceleration scheme 1
(**) TPPS/2 IBM TrackPoint: (accel) filter chain progression: 2.00
(**) TPPS/2 IBM TrackPoint: (accel) filter stage 0: 20.00 ms
(**) TPPS/2 IBM TrackPoint: (accel) set acceleration profile 0
(II) config/hal: Adding input device ThinkPad Extra Buttons
(**) ThinkPad Extra Buttons: always reports core events
(**) ThinkPad Extra Buttons: Device: "/dev/input/event7"
(II) ThinkPad Extra Buttons: Found keys
(II) ThinkPad Extra Buttons: Configuring as keyboard
(II) XINPUT: Adding extended input device "ThinkPad Extra Buttons" (type: KEYBOARD)
(**) Option "xkb_rules" "evdev"
(**) Option "xkb_model" "evdev"
(**) Option "xkb_layout" "us"
(II) config/hal: Adding input device Macintosh mouse button emulation
(**) Macintosh mouse button emulation: always reports core events
(**) Macintosh mouse button emulation: Device: "/dev/input/event0"
(II) Macintosh mouse button emulation: Found 3 mouse buttons
(II) Macintosh mouse button emulation: Found x and y relative axes
(II) Macintosh mouse button emulation: Configuring as mouse
(**) Macintosh mouse button emulation: YAxisMapping: buttons 4 and 5
(**) Macintosh mouse button emulation: EmulateWheelButton: 4, EmulateWheelInertia: 10, EmulateWheelTimeout: 200
(II) XINPUT: Adding extended input device "Macintosh mouse button emulation" (type: MOUSE)
(**) Macintosh mouse button emulation: (accel) keeping acceleration scheme 1
(**) Macintosh mouse button emulation: (accel) filter chain progression: 2.00
(**) Macintosh mouse button emulation: (accel) filter stage 0: 20.00 ms
(**) Macintosh mouse button emulation: (accel) set acceleration profile 0
(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, 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/event6"
(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
(**) Option "HorizTwoFingerScroll" "true"
(**) Option "TapButton1" "1"
(**) Option "TapButton2" "3"
(**) Option "TapButton3" "2"
(--) 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
(**) AT Translated Set 2 keyboard: always reports core events
(**) AT Translated Set 2 keyboard: Device: "/dev/input/event1"
(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" "us"
(II) AIGLX: Suspending AIGLX clients for VT switch
(II) intel(0): xf86UnbindGARTMemory: unbind key 0
(WW) Open ACPI failed (/var/run/acpid.socket) (No such file or directory)
(II) No APM support in BIOS or kernel
(II) AIGLX: Resuming AIGLX clients after VT switch
(II) intel(0): xf86BindGARTMemory: bind key 0 at 0x0f400000 (pgoffset 62464)
(II) intel(0): Fixed memory allocation layout:
(II) intel(0): 0x00000000-0x00000fff: power context (4 kB)
(II) intel(0): 0x0077f000:            end of stolen memory
(II) intel(0): 0x0077f000-0x0f3fffff: DRI memory manager (242180 kB)
(II) intel(0): 0x0f400000-0x0fffffff: exa offscreen (12288 kB)
(II) intel(0): 0x10000000:            end of aperture
(II) intel(0): BO memory allocation layout:
(II) intel(0): 0x0077f000:            start of memory manager
(II) intel(0): 0x0079f000-0x00b9efff: depth buffer (4096 kB) Y tiled
(II) intel(0): 0x00b9f000-0x00f9efff: back buffer (4096 kB) X tiled
(II) intel(0): 0x00f9f000-0x0139efff: front buffer (4096 kB) X tiled
(II) intel(0): 0x0139f000-0x0139ffff: overlay registers (4 kB)
(II) intel(0): 0x013a0000-0x013a9fff: HW cursors (40 kB)
(II) intel(0): 0x0f400000:            end of memory manager
(II) intel(0): using SSC reference clock of 100 MHz
(II) intel(0): Selecting standard 18 bit TMDS pixel format.
(II) intel(0): [drm] mapped front buffer at 0xe0f9f000, handle = 0x1e1f3000
(II) intel(0): Output configuration:
(II) intel(0):   Pipe A is off
(II) intel(0):   Display plane A is now disabled and connected to pipe A.
(II) intel(0):   Pipe B is on
(II) intel(0):   Display plane B is now enabled and connected to pipe B.
(II) intel(0):   Output VGA is connected to pipe none
(II) intel(0):   Output LVDS is connected to pipe B
(II) intel(0):   Output TMDS-1 is connected to pipe none
(--) SynPS/2 Synaptics TouchPad: touchpad found
(II) intel(0): EDID vendor "LEN", prod id 16416
(II) intel(0): Using EDID range info for horizontal sync
(II) intel(0): Using EDID range info for vertical refresh
(II) intel(0): Printing DDC gathered Modelines:
(II) intel(0): Modeline "1024x768"x0.0   65.00  1024 1048 1184 1344  768 771 777 806 -hsync -vsync (48.4 kHz)
(II) intel(0): Modeline "1024x768"x0.0   54.16  1024 1048 1184 1344  768 771 777 806 -hsync -vsync (40.3 kHz)
(II) intel(0): EDID vendor "LEN", prod id 16416
(II) Video Bus: Device reopened after 1 attempts.
(II) TPPS/2 IBM TrackPoint: Device reopened after 1 attempts.
(II) ThinkPad Extra Buttons: Device reopened after 1 attempts.
(II) Macintosh mouse button emulation: Device reopened after 1 attempts.
(II) AT Translated Set 2 keyboard: Device reopened after 1 attempts.

Offline

#6 2009-06-29 14:35:50

eldragon
Member
From: Buenos Aires
Registered: 2008-11-18
Posts: 1,029

Re: New to arch, Intel graphics, can't set direct rendering

your xorg looks ok to me.....

i found it odd that i810 and fbdev are being tried prior to intel, its the same case here...

do you have an xorg.conf? you might need to use one.... try generating one, and then adding to it:

Section "Extensions"
    Option "Composite" "Enable"
EndSection

Section "DRI"
    Mode 0666
EndSection

Offline

#7 2009-06-29 16:23:29

patroclo7
Member
From: Bassano del Grappa, ITALY
Registered: 2006-01-11
Posts: 915

Re: New to arch, Intel graphics, can't set direct rendering

The log shows that dri is activated (after an initial failure). Odd


Mortuus in anima, curam gero cutis

Offline

#8 2009-06-29 16:30:21

eldragon
Member
From: Buenos Aires
Registered: 2008-11-18
Posts: 1,029

Re: New to arch, Intel graphics, can't set direct rendering

patroclo7 wrote:

The log shows that dri is activated (after an initial failure). Odd

where do you get that from?
it fails to load dri2 cause you are using EXA, thats expected.

if you wish to use UXA, add to your device section:

Option "Accelmethod" "UXA"

then dri2 will load instead of dri

Offline

#9 2009-06-29 17:47:27

SoleSoul
Member
From: Israel
Registered: 2009-06-29
Posts: 319

Re: New to arch, Intel graphics, can't set direct rendering

Thank you for your help.
I didn't try your suggestions yet because I don't want to create a xorg.conf file if I don't have to.
I added horizontal scrolling to synaptics through fdi policy, is there a way to do the changes you suggested in the "new way", without xorg.conf?

Offline

#10 2009-06-29 17:52:41

eldragon
Member
From: Buenos Aires
Registered: 2008-11-18
Posts: 1,029

Re: New to arch, Intel graphics, can't set direct rendering

SoleSoul wrote:

Thank you for your help.
I didn't try your suggestions yet because I don't want to create a xorg.conf file if I don't have to.
I added horizontal scrolling to synaptics through fdi policy, is there a way to do the changes you suggested in the "new way", without xorg.conf?

i dont think we are there yet... you could still have an xorg.conf and hotplug your inputs (just remove everything, and leave the device section (which is what you need) and of course the pieces i posted which should go below the device section.

thats what ive done.

Last edited by eldragon (2009-06-29 17:53:00)

Offline

#11 2009-06-29 19:32:51

SoleSoul
Member
From: Israel
Registered: 2009-06-29
Posts: 319

Re: New to arch, Intel graphics, can't set direct rendering

There is some progress here.
This is my xorg.conf:

Section "Extensions"
        Option "Composite" "Enable"
EndSection

Section "Device"
    Identifier     "Videocard1"
    VendorName  "Intel Corporation"
    BoardName   "Mobile GM965/GL960 Integrated Graphics Controller"
    Driver     "intel"
    BusID       "PCI:0:2:0"
    Option "RenderAccel" "true"
    Option "XaaNoOffscreenPixmaps" "on"
    Option "Accelmethod" "UXA"
EndSection

Section "dri"
# Access to OpenGL ICD is allowed for all users:
    Mode        0666
# Access to OpenGL ICD is restricted to a specific user group:
#    Group        100    # users
EndSection

It's taken from my Zenwalk installation and stripped according to your advice.
The addition of the line Option "Accelmethod" "UXA" allowed cairo-dock to use opengl for the first time. The effects are totally different!
Until now if I tried to use opengl X would crash.
Thank you for that!

There are still problems though...
Firefox scrolls slowly if the page is heavy, and it is OS related because when I use other OS's on the same computer it works better.

Compiz still starts with indirect rendering. glxinfo says that direct rendering is disabled and I think I agree with it neutral

I'm sure that there is a way to operate this Intel card better. It's driver is open source and developed by Intel after all...

Offline

#12 2009-06-29 19:41:50

eldragon
Member
From: Buenos Aires
Registered: 2008-11-18
Posts: 1,029

Re: New to arch, Intel graphics, can't set direct rendering

SoleSoul wrote:

There is some progress here.
This is my xorg.conf:

Section "Extensions"
        Option "Composite" "Enable"
EndSection

Section "Device"
    Identifier     "Videocard1"
    VendorName  "Intel Corporation"
    BoardName   "Mobile GM965/GL960 Integrated Graphics Controller"
    Driver     "intel"
    BusID       "PCI:0:2:0"
    Option "RenderAccel" "true"
    Option "XaaNoOffscreenPixmaps" "on"
    Option "Accelmethod" "UXA"
EndSection

Section "dri"
# Access to OpenGL ICD is allowed for all users:
    Mode        0666
# Access to OpenGL ICD is restricted to a specific user group:
#    Group        100    # users
EndSection

It's taken from my Zenwalk installation and stripped according to your advice.
The addition of the line Option "Accelmethod" "UXA" allowed cairo-dock to use opengl for the first time. The effects are totally different!
Until now if I tried to use opengl X would crash.
Thank you for that!

There are still problems though...
Firefox scrolls slowly if the page is heavy, and it is OS related because when I use other OS's on the same computer it works better.

Compiz still starts with indirect rendering. glxinfo says that direct rendering is disabled and I think I agree with it neutral

I'm sure that there is a way to operate this Intel card better. It's driver is open source and developed by Intel after all...

compiz using indirect-rendering just depends on how you are starting it...read the wiki on how to start it with your DE.

again, i advice you read the wiki on how to generate a clean xorg.conf straight for arch. although yours looks ok. some options in the device section might not be needed.

Offline

#13 2009-06-29 22:33:13

.:B:.
Forum Fellow
Registered: 2006-11-26
Posts: 5,819
Website

Re: New to arch, Intel graphics, can't set direct rendering

Just wipe your configuration alltogether, start out without one, add stuff as needed. That's how you keep it clean and minimal smile.


Got Leenucks? :: Arch: Power in simplicity :: Get Counted! Registered Linux User #392717 :: Blog thingy

Offline

#14 2009-07-02 22:07:56

SoleSoul
Member
From: Israel
Registered: 2009-06-29
Posts: 319

Re: New to arch, Intel graphics, can't set direct rendering

Thank you for your help.
I ended up using uxa and dri2.
After the last update glxgeras shows similar framerate as exa and only with uxa cairo-dock works with opengl.
compiz still runs with indirect rendering. it detects an Intel video card and disables direct rendering. without doing any change, if I check glxinfo before starting compiz I see direct rendering: yes and after starting compiz it says direct rendering : no.
I tried to manually start compiz with direct rendering and with exa it didn't work. With uxa it worked in about 1/3 fps!! one frame in three seconds.
For now it's enough for me. I'll just wait for the driver to get better.

Offline

#15 2009-07-02 22:09:57

SoleSoul
Member
From: Israel
Registered: 2009-06-29
Posts: 319

Re: New to arch, Intel graphics, can't set direct rendering

BTW, this is my xorg.conf:

Section "Module"
    Load  "dri2"
EndSection

Section "Extensions"
        Option "Composite" "Enable"
EndSection

Section "Device"
    Identifier     "Videocard1"
    Option "Accelmethod" "uxa"
EndSection

Offline

#16 2009-07-02 22:13:59

eldragon
Member
From: Buenos Aires
Registered: 2008-11-18
Posts: 1,029

Re: New to arch, Intel graphics, can't set direct rendering

SoleSoul wrote:

BTW, this is my xorg.conf:

Section "Module"
    Load  "dri2"
EndSection

Section "Extensions"
        Option "Composite" "Enable"
EndSection

Section "Device"
    Identifier     "Videocard1"
    Option "Accelmethod" "uxa"
EndSection

have you checked the wiki on how to enable compiz? as far as i know, nothing is automagically set up here in arch, so compiz shouldnt be any different.

for example, im using the method which DOES NOT load metacity (whats the point if its going to get killed anyway wink ) its here: http://wiki.archlinux.org/index.php/Com … on.22.29_2

Offline

#17 2009-07-03 01:47:28

SoleSoul
Member
From: Israel
Registered: 2009-06-29
Posts: 319

Re: New to arch, Intel graphics, can't set direct rendering

Hey, thanks for your worrying about me but if I get you right, you assume that I use gnome. Well, it's not right. I use no desktop environment. I start compiz with fusion icon. It is the only program that I start with xorg.

Thank you!

Offline

#18 2009-07-03 01:49:07

eldragon
Member
From: Buenos Aires
Registered: 2008-11-18
Posts: 1,029

Re: New to arch, Intel graphics, can't set direct rendering

well, then its even simpler, you can set it to direct rendering right there. the setting should stick (it did here)

Offline

#19 2009-07-03 01:54:12

SoleSoul
Member
From: Israel
Registered: 2009-06-29
Posts: 319

Re: New to arch, Intel graphics, can't set direct rendering

ehm.. I tried it:

SoleSoul wrote:

I tried to manually start compiz with direct rendering and with exa it didn't work. With uxa it worked in about 1/3 fps!! one frame in three seconds.

Offline

#20 2009-07-03 01:58:26

eldragon
Member
From: Buenos Aires
Registered: 2008-11-18
Posts: 1,029

Re: New to arch, Intel graphics, can't set direct rendering

SoleSoul wrote:

ehm.. I tried it:

SoleSoul wrote:

I tried to manually start compiz with direct rendering and with exa it didn't work. With uxa it worked in about 1/3 fps!! one frame in three seconds.

after doing so....switch to a VT, wait 10 secs, and switch back. see if that restores the refresh rate

ohh, and i forgot, check if /var/log/kernel.log is being filled with:

 kernel: [drm:drm_wait_vblank] *ERROR* failed to acquire vblank counter, -22

EDIT: one final thought: check this: https://bugs.freedesktop.org/show_bug.cgi?id=22492 and this https://bugs.freedesktop.org/show_bug.cgi?id=22166

Last edited by eldragon (2009-07-03 02:05:37)

Offline

#21 2009-07-03 02:14:26

SoleSoul
Member
From: Israel
Registered: 2009-06-29
Posts: 319

Re: New to arch, Intel graphics, can't set direct rendering

after doing so....switch to a VT, wait 10 secs, and switch back. see if that restores the refresh rate

No, sorry. It doesn't change anything.

BUT this:

Jun 29 18:38:39 blackpearl kernel: [drm:i915_get_vblank_counter] *ERROR* trying to get vblank count for 
disabled pipe 0

is indeed spread across the kernel log. Now googling it.. What is it?

And about the bug report, the description fits, but if I didn't miss something there is still no solution for it right?

Offline

#22 2009-07-03 02:20:19

eldragon
Member
From: Buenos Aires
Registered: 2008-11-18
Posts: 1,029

Re: New to arch, Intel graphics, can't set direct rendering

no, there is no solution, i only get this when i switch from a bigger screen to a smaller screen, and switching to a VT and back fixes it. maybe try switching resolutions back and forth with xrandr...that could help compiz pick the correct rendering pipe.

Offline

#23 2009-07-03 02:21:57

SoleSoul
Member
From: Israel
Registered: 2009-06-29
Posts: 319

Re: New to arch, Intel graphics, can't set direct rendering

I really must get some sleep so I'll continue the research tomorrow. For now it works quite well.
Thank you!

Offline

#24 2009-07-03 10:14:08

SoleSoul
Member
From: Israel
Registered: 2009-06-29
Posts: 319

Re: New to arch, Intel graphics, can't set direct rendering

Ok, I'm back.
I found a partial solution.
I enabled kms, and now I can run compiz with direct rendering and I can now drop my xorg.conf entirely.
The are two problems though:
1) FPS of glxgears drop from 950~ to 750~. but I don't really care.
2) cairo-dock works only after I start compiz with --indirect-rendering. otherwise it crashes.

I learned a lot from this discussion!

EDIT: the only way I found to run both compiz with direct-rendering and cairo-dock with opengl is:
1) start compiz with --indirect-rendering
2) start cairo-dock -o
3) kill compiz
4) start compiz with direct rendering.

It's weird but it works. Surely I'm not gonna do it each time I startx..

Last edited by SoleSoul (2009-07-03 10:24:57)

Offline

#25 2009-07-03 12:42:19

eldragon
Member
From: Buenos Aires
Registered: 2008-11-18
Posts: 1,029

Re: New to arch, Intel graphics, can't set direct rendering

check cairo dock bugs upstream...they might already be aware of the situation, otherwise, file a bug there..

Offline

Board footer

Powered by FluxBB