As promised, I will do a comparative test between Intel video driver, version 2.14.0 and 2.15.0.
The 'victim' for tests:
Motherboard: G31TM-P35
CPU: 'Intel Pentium Dual E2180@2.00GHz
Memory: 2GB DDR2 800MHz
Harddrive: WD3200AAKS, 320GB
Current configuration:
Slackware current, kernel-2.6.38.3-smp, AlienBob's KDE-4.6.2, Mesa-7.10.2, libdrm-2.4.25 and a custom xf86-video-intel-2.15.0, compiled against libdrm-2.4.25.
Notable Configurations:
In
/etc/kde/kdm/kdmrc a line is added:
Code:
[X-:*-Core]
AllowNullPasswd=true
AllowShutdown=All
NoPassEnable=false
NoPassUsers=
ServerArgsLocal=-nolisten tcp
ServerCmd=/usr/bin/X -br -novtswitch -quiet
ServerTimeout=45
TerminateServer=true
[X-:*-Greeter]
AllowClose=false
Last night, very late, I forgot to mention that we use this option. I know, I know, in a Perfect World you do not need it, but the graphics stack is not perfect.
However, now I know that 'something strange will happen' without it.
Let me continue...
Another change, which is somewhat strange, is in
/usr/bin/startkde:
Code:
#!/bin/sh
#
# DEFAULT KDE STARTUP SCRIPT ( 4.6.2 (4.6.2) )
#
# KWIN workaround
export KWIN_DIRECT_GL=1
if test "x$1" = x--failsafe; then
KDE_FAILSAFE=1 # General failsafe flag
KWIN_COMPOSE=N # Disable KWin's compositing
export KWIN_COMPOSE KDE_FAILSAFE
fi
# When the X server dies we get a HUP signal from xinit. We must ignore it
A rational explanation:
KWin uses OpenGL renderer string to get some information. But these happy lads from Mesa have decided to change the structure of this information.
With this parameter, we say to KWin, as it has direct rendering.
KWin with KWIN_DIRECT_GL parameter:
Code:
OpenGL vendor string: Tungsten Graphics, Inc
OpenGL renderer string: Mesa DRI Intel(R) G33 x86/MMX/SSE2
OpenGL version string: 1.4 Mesa 7.10.2
Driver: Intel
GPU class: i915/i945
OpenGL version: 1.4
Mesa version: 7.10.2
X server version: 1.9.5
Linux kernel version: 2.6.38
Direct rendering: yes
Requires strict binding: yes
GLSL shaders: no
Texture NPOT support: yes
KWin without KWIN_DIRECT_GL parameter:
Code:
OpenGL vendor string: Tungsten Graphics, Inc
OpenGL renderer string: Mesa DRI Intel(R) G33 x86/MMX/SSE2
OpenGL version string: 1.4 Mesa 7.10.2
Driver: Intel
GPU class: i915/i945
OpenGL version: 1.4
Mesa version: 7.10.2
X server version: 1.9.5
Linux kernel version: 2.6.38
Direct rendering: no
Requires strict binding: yes
GLSL shaders: no
Texture NPOT support: limited
Why do we need to properly inform KWin? For proper management of crisis situations. Read: crash.
And, mysteriously, the blur effect works again.
The third important element of our configuration is:
System Settings -> Desktop Effects -> Advanced -> Scale method: Smooth.
Then, no Lanczos filter for you, if you have a G31 'video-card'!
So,
Scale method: Accurate is glorious about transforming your G31 system into something slooooooow, and, anyways, will not work ...
And last but not least, we have
flashplayer 10.3 Beta, version 10.3.180.65.
---------------
Finally, the system looks responsive, everything works. Let's try to ruin it!
We use three methods to break the system:
1. We watch
a clip on Youtube in 720p HD format. Full-screen and back, is efficient enough 'to see the console'.
2. The glorious OpenGL screensaver. You can be sure that something bad will happen. Here, our favorite will be
Atlantis.
3. Logout into KDM screen. But here we already know, 'we have problems'.
Phase 1.
Initial system.
1. The video runs smoothly, full screen and back.
2. We test Atlantis. The first test works, then, KWin crack, and he comes back, without 3D effects. The system is still perfectly functional, but KWin's effects are not enabled.
3. Logout works.
This is exactly the behavior you expect. KWin has to disable the OpenGL effects of a crash.
Phase 2.
We install the stock 2.15.0 video driver, and we comment
TerminateServer. Reboot.
1. The video runs smoothly, full screen and back. But it has moments of stuttering when we get into full-screen.
2. No major changes on Atlantis. KWin crash on first shoot and it comes back without effects.
3. Logout fails and we see the console. Goodbye, KDM!
Overall, the system feels a bit slower.
Phase 3.
We install Mesa-7.9.2 and libdrm-2.4.23. Reboot.
1. No major changes.
2. No major changes.
3. No major changes.
Overall, the system feels yet slower.
Phase 4.
We install the stock 2.14.0 video driver. Reboot.
1. No major changes.
2. X server freeze! But console switching works. We go on first virtual console and we comment the KWIN_DIRECT_GL, then reboot.
3. Can not be tested.
Phase 5.
No changes after reboot.
1. No major changes.
3. Logout into KDM screen works again. Login again.
2. X server crash. We see the console.
Overall, the system not feels slower or faster.
Phase 6.
We activate
the default Scale method: Accurate.
1. The clip sees framed.
2. No changes.
3. No changes.
Overall, the system feels slooooooow.
--------------
That's it. It's time to repair this system.
