This forum has been archived. All content is frozen. Please use KDE Discuss instead.

[solved]composite fail to load after kernel update to 2.6.30

Tags: kwin, compositing kwin, compositing kwin, compositing
(comma "," separated)
broch
Registered Member
Posts
11
Karma
0
OS
Hello,
I have small problem with kde 4.2.4.
Thank you for any help. Below is description of my system and the problem that I have.

My system:
laptop HP Pavillion dv5000 (Intel dualcore T2500)
video card:
nvidia Go 7400
RAM 2GB
OS:
Arch Linux (current)
running kernels:
2.6.29.4
2.6.29.5
2.6.30-Arch
2.6.30-zen2
2.6.31-rc1-zen1
nvidia driver 185.18.14 (patched to install on 2.6.31-rc1)
all kernels are installed with nvidia modules, so I don't need to reinstall nvidia driver when booting to another kernel.
KDE: Kdemod 4.2.4
problem:
after booting to any of the 2.6.30 I am loosing desktop effects (e.g. transparency, Expose)
when I boot to 2.6.29.x effects are restored, without any modification of kde settings.

Enable desktop effects is checked
Compositing type: OpenGL
OpenGL mode is set to Texture from Pixmap

Desktop effects work when booting to 2.6.29. Desktop effects do not work when booting to 2.6.30 series or 2.6.31-rc1

I tried different options settings in Desktop Settings configuration panel with no effect.
Moreover it seems that after upgrading to 2.6.30 more users have this problem.

I also have this exact problem when I had installed nvidia driver version 180.53 and 180.60 on all kernels (with exception of 2.6.31-rc1 as there are no patches for earlier drivers to be installed on 2.6.31-rc1)

When booting to 2.6.30 and trying to re-enable desktop efects: I am getting the following error:
Failed to activate desktop effects using the given configuration options. Settings will be reverted to their previous values.
Check your X configuration. You may also consider changing advanced options, especially changing the compositing type.


this is the error appended to
~/.xsessions-error
kwin(2891) KWin::CompositingPrefs::detectDriverAndVersion: GL vendor is "NVIDIA Corporation"
kwin(2891) KWin::CompositingPrefs::detectDriverAndVersion: GL renderer is "GeForce Go 7400/PCI/SSE2"
kwin(2891) KWin::CompositingPrefs::detectDriverAndVersion: GL version is "2.1.2 NVIDIA 185.18.14"
kwin(2891) KWin::CompositingPrefs::detectDriverAndVersion: XGL: no
kwin(2891) KWin::CompositingPrefs::detectDriverAndVersion: Detected driver "nvidia" , version "185.18.14"
kwin(2891) KWin::CompositingPrefs::applyDriverSpecificOptions: nvidia >= 173.14.12, enabling compositing
kwin(2891) KWin::x11ErrorHandler: kwin: X Error ( "error: GLXBadDrawable[GLX+2], request: X_GLXMakeContextCurrent[GLX+26], resource: 0x3a0a765" )
kwin(2891) KWin::Extensions::init: Extensions: shape: 0x "11" composite: 0x "4" render: 0x "a" fixes: 0x "40"
kwin(2891) KWin::Workspace::setupCompositing: OpenGL compositing
kwin(2891) KWin::SceneOpenGL::initBufferConfigs: Drawable visual (depth 24 ): 0x "59"
kwin(2891) KWin::SceneOpenGL::initBufferConfigs: Drawable visual (depth 32 ): 0x "80"
kwin(2891) KWin::SceneOpenGL::initBuffer: Buffer visual (depth 24 ): 0x "57"
kwin(2891): Compositing self-check failed, disabling compositing.
kwin(2891): Failed to initialize compositing, compositing disabled

Last edited by broch on Sun Jul 05, 2009 9:31 pm, edited 2 times in total.
jokerwww
Registered Member
Posts
12
Karma
0
Did you check if the nvidia driver is actually loaded in the 2.6.30 kernel? If not run "lsmod" and check.
Do other 3D applications work?
I'm using KDE 4.2.4 on gentoo with kernel 2.6.30 and compositing effects work just fine for me...
broch
Registered Member
Posts
11
Karma
0
OS
yes, module is loaded:
glxinfo | grep OpenGL
OpenGL vendor string: NVIDIA Corporation
OpenGL renderer string: GeForce Go 7400/PCI/SSE2
OpenGL version string: 2.1.2 NVIDIA 185.18.14
OpenGL shading language version string: 1.20 NVIDIA via Cg compiler

also ~/.xsession-errors shows nvidia module loaded and driver version.

This is not common problem, but I have seen kde users complaining about similar issue (upgraded kernel to 2.6.30 and lost compositing)
User avatar
bcooksley
Administrator
Posts
19765
Karma
87
OS
That is the Xorg driver, which is not related to the Kernel. The command below lists the loaded kernel modules.
Code: Select all
lsmod


KDE Sysadmin
[img]content/bcooksley_sig.png[/img]
broch
Registered Member
Posts
11
Karma
0
OS
Are you saying that
OpenGL version string: 2.1.2 NVIDIA 185.18.14 <- (this is nvidia driver version listed)
is X driver?
glxinfo lists current driver status as well as lsmod | grep nvidia
also kwin is detecting nvidia driver too:
kwin(2891) KWin::CompositingPrefs::detectDriverAndVersion: Detected driver "nvidia" , version "185.18.14"


anyway
lsmod | grep nvidia
nvidia 8890024 40
i2c_core 12692 2 nvidia,i2c_i801

this is status of nvidia driver irrelevant of kernel loaded with exception of default Arch linux kernel which additionally loads intel_agp module
User avatar
bcooksley
Administrator
Posts
19765
Karma
87
OS
I have never encountered this. However it is possible that the Kernel is not the graphics related module, since it is being used by i2c_core.

Can you verify direct rendering is available?
Code: Select all
glxinfo | grep -i direct
coques
Registered Member
Posts
6
Karma
0
Hi,
I guess, I've got the same problem as broch.
Rendering is on.

Code: Select all
direct rendering: Yes
    GL_EXT_direct_state_access, GL_EXT_draw_range_elements, GL_EXT_fog_coord,
User avatar
bcooksley
Administrator
Posts
19765
Karma
87
OS
Is KDE being logged in using safe mode? ( Check in KDM it is in the list of sessions ?)
coques
Registered Member
Posts
6
Karma
0
No, it's not in safe mode.

I also tried this, but without success.

Code: Select all
KWIN_COMPOSE=O kwin --replace &


I moved .kde4 directory somewhere else and created a new KDE profile, which didn't help.
broch
Registered Member
Posts
11
Karma
0
OS
$ glxinfo | grep -i direct
direct rendering: Yes
GL_EXT_direct_state_access, GL_EXT_draw_range_elements, GL_EXT_fog_coord


In my opinion there are changes in the new kernel that affect compositing.
e.g. PAT (in some cases users suffer slowdown in compiz if PAT is enabled)
KMS is another issue.
These may not affect compositing per se but may introduce bugs that cause compositing to fail irrelevant of PAT and/or KMS/any video releted changes to the kernel.

Because, as I mentioned before I have at the same time several kernels installed all of them with nvidia driver, and all kernels of 2.6.29.x allow compositing to load while all kernels of 2.6.30 will cause compositing to fail, I think that this is related to the changes in the kernel. These changes however may be permanent so compositing would have to be adjusted somehow to work with whatever kernel changes.


building kernel without i2c did not help, still getting the same error with compositing failed to load
broch
Registered Member
Posts
11
Karma
0
OS
It is possible that I have found kernel bug causing compositing to fail.
It seems that bug is related to PAT.

I have two kernels with PAT disabled.
.config file for 2.6.29.5:
cat .config | grep X86_PAT
# CONFIG_X86_PAT is not set
messages.log for this kernel does not show any entry for PAT

.config file for 2.6.30 (custom)
cat .config | grep X86_PAT
# CONFIG_X86_PAT is not set

however messages.log for this kernel still generates entry for PAT:
NVRM: CPU does not support the PAT, falling back to MTRRs.

so in spite of PAT being disabled, kernel 2.6.30 still recognizes this option

in view of
this finding:
http://www.nvnews.net/vbulletin/showthr ... 112&page=2
post #23
it seems that kernels 2.6.30 and up bear a bug will cause PAT try to load even if PAT is disabled.

It does not affect all nvidia cards but it looks like has some impact on 7400 (at least)

To confirm this I will build 2.6.29.5 with PAT enabled to see if compositing will fail.
broch
Registered Member
Posts
11
Karma
0
OS
problem fixed by the patch provided by nvidia (zander)

thank you


Bookmarks



Who is online

Registered users: Bing [Bot], Evergrowing, Google [Bot], rblackwell