Intel GPU kernel driver
Andrey Kosachenko
andrey.kosachenko at gmail.com
Tue Jul 12 11:00:50 UTC 2011
On 12.07.2011 11:17, Kostik Belousov wrote:
>>>> - switching between vts (Ctrl+Alt+F[1-9]) doesn't work over here,
>>>> attempt to switch to consoles within range [1-8] leads to garbled screen
>>>> (https://lh4.googleusercontent.com/-WmDhn1X-Ze0/Thn-O5dfeiI/AAAAAAAAABM/WIX3co3DQaM/s720/20110710_003-1.jpeg)
>>>> though 9-th (occupied by X) is always displayed properly;
> Yes, VT switch handling is not implemented.
Okay, got it (just expressed my observations)
>> Also not sure that X actually operates w/o acceleration: the following
>> output makes me think so:
>>
>> # env LIBGL_DEBUG=verbose sh -c 'glxinfo 2>&1' | egrep '(render|Driver)'
>> direct rendering: Yes
>> OpenGL renderer string: Mesa DRI Intel(R) Ironlake Mobile
>> GL_EXT_vertex_array_bgra, GL_NV_conditional_render,
> If OpenGL apps work, and not cause the X server to die with SIGBUS,
> then yes, most likely acceleration works.
Yeap, agree. Unfortunately I hadn't appropriate apps at my hand at that
very moment. Though freaking artificial glxgears ran w/o issues (sorry
for my ignorance... I'm not a fan of games, GL neat features/effects and
stuff like that, so if you can recommend smth. to test it thoroughly
I'll do it and report the results)
>>
>> Additional information:
>> - pciconf -lvb: http://pastebin.com/YT8wUBiZ
> So this is another Ironlake.
Hm... not sure if I got this properly. In the first post I mentioned
that there is a laptop "with integrated Intel graphics card (Ironlake,
0x00468086)". pciconf -lvb output also reports "chip=0x00468086". AFAIK
there are two types of chips: 0x00428086 (a.k.a. "D" (desktop?)) and
0x00468086 (a.k.a. "M" (mobile?)). And I've got exactly the second one.
>>
>> - dmesg output (with DE effects enabled, leads to garbled screen):
>> http://pastebin.com/DU3RvzTi
>>
>> - dmesg output (failsafe DE session): http://pastebin.com/f4gghA6E
> No useful information there.
yeap, the second dmesg's output (failsafe) is clean and mentioned just
for comparison. However the first one (http://pastebin.com/DU3RvzTi)
contains suspicious entries (for instance line #333, #340, #367 and so
forth). So I thought it could be helpful (though you considered it
useless... let me know if you want to acquire more info)
>>
>> - and just in case X logs (with ModeDebug="true"):
>> http://pastebin.com/iEPxm8ib
> When did the X server segfaulted ?
X segfaulted on attempt to enable desktop effects (presumes usage of
composite extension). Both aforementioned logs (Xorg.log
(http://pastebin.com/iEPxm8ib) and first dmesg output
(http://pastebin.com/DU3RvzTi) were collected within 2-5 seconds right
after X segfaulted.
Also, forgot to mention that hw.dri.0.info.i915_error_state didn't
contain any errors.
--
WBR,
Andrey Kosachenko.
More information about the freebsd-x11
mailing list