Bug 16451 - direct rendering "yes" but not working for a intel 865G
Summary: direct rendering "yes" but not working for a intel 865G
Status: RESOLVED INVALID
Alias: None
Product: xorg
Classification: Unclassified
Component: Driver/intel (show other bugs)
Version: 7.3 (2007.09)
Hardware: x86 (IA32) Linux (All)
: medium normal
Assignee: Chris Wilson
QA Contact: Xorg Project Team
URL:
Whiteboard:
Keywords: NEEDINFO
Depends on:
Blocks:
 
Reported: 2008-06-21 01:47 UTC by Xavier
Modified: 2011-01-14 10:59 UTC (History)
0 users

See Also:
i915 platform:
i915 features:


Attachments
Xorg.0.log (31.69 KB, text/plain)
2008-06-21 01:47 UTC, Xavier
no flags Details

Description Xavier 2008-06-21 01:47:03 UTC
Created attachment 17278 [details]
Xorg.0.log

Hi all,

I've a integrated chipset that claims to support direct rendering but it is not running (all gets very slow and xorg is at 99% cpu when charging a flash video). I've the following warnings in my log file :

~$ grep -i aigl /var/log/Xorg.0.log
(==) AIGLX enabled
(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 0x31
(WW) AIGLX: 3D driver claims to not support visual 0x32
(II) AIGLX: Loaded and initialized /usr/lib/dri/i915_dri.so

I've tested my computer with a Ubuntu and a Knoppix live-CD and I've the same problem.

Thanks,
Xavier

-- additional informations --
CPU: Intel(R) Pentium(R) 4 CPU 3.06GHz
Mem: 1 Go
Xorg version : 7.3
OS : Debian Lenny

xorg.conf :

Section "InputDevice"
        Identifier      "Generic Keyboard"
        Driver          "kbd"
        Option          "XkbRules"      "xorg"
        Option          "XkbModel"      "pc105"
        Option          "XkbLayout"     "fr"
        Option          "XkbVariant"    "latin9"
EndSection

Section "InputDevice"
        Identifier      "Configured Mouse"
        Driver          "mouse"
EndSection

Section "Device"
        Identifier      "Configured Video Device"
        Driver          "i810"
        #Driver         "intel"
        BusID           "PCI:0:2:0"
        Option          "NoAccel"       "false"
        Option          "DRI"           "true"
EndSection

Section "Monitor"
        Identifier      "Configured Monitor"
        HorizSync       28-80
        VertRefresh     48-75
        VendorName      "Sony"
        ModelName       "SDM-S75A"
EndSection

Section "Screen"
        Identifier      "Default Screen"
        Monitor         "Configured Monitor"
        Device          "Configured Video Device"
EndSection

Section "Module"
    Load           "glx"
    Load           "GLcore"
    Load           "dri"
    Load           "v4l"
    Load           "i2c"
    Load           "bitmap"
    Load           "ddc"
    Load           "dbe"
    Load           "extmod"
    Load           "freetype"
    Load           "int10"
    Load           "record"
    Load           "type1"
    Load           "xtrap"
EndSection
Comment 1 Matt Turner 2010-12-02 18:56:33 UTC
This was filed under the wrong component. Is this bug still present?
Comment 2 Chris Wilson 2011-01-14 10:59:39 UTC
Presuming that it works today with the "intel" driver and i915_dri.so. At least I know it works for a variety of other gen2 testers.


Use of freedesktop.org services, including Bugzilla, is subject to our Code of Conduct. How we collect and use information is described in our Privacy Policy.