[opensuse-factory] Nvidia blobs, Kwin Desktop Effects, and 12.1 M1
Greetings all:
I had been stymied in upgrading my 11.4 system to 12.1 M1. The upgrade would
proceed as normal, but the Nvidia drivers versions 270.xx.xx and 275.xx xx
(all the proprietary xxxx.run file downloaded from Nvidia) would be
required for use. The kernel module would not build for 260.19.44 under 12.1
M1.
The 260.19.44 driver is the last one for which desktop effects worked
correctly for me. With the 270.xx.xx and 275.xx.xx I had to disable desktop
effects due to various problems. Even then, there was still a problem with
the titlebar blacking out in the middle when hovered over in some window
decorations. So I wanted to figure out how to get the 260.19.44 driver to
build the kernel module under 12.1 M1.
Turns out it was simple. Extract the NVIDIA-Linux-x86_64-260.19.44.run with
the -x switch. Change into the NVIDIA-Linux-x86_64-260.19.44/kernel
directory and open file nv-linux.h and change line 90 from #include
Hi, this time it may not be the fault of nvidia (i am on nvidia too)... as I heard similar reports for ati and intel... and someone was blaming mesa... I suspect you are using oxygen... if you change to something else do you still have issues? Alin On Thu 16 Jun 2011 06:19:47 Michael Powell wrote:
Greetings all:
I had been stymied in upgrading my 11.4 system to 12.1 M1. The upgrade would proceed as normal, but the Nvidia drivers versions 270.xx.xx and 275.xx xx (all the proprietary xxxx.run file downloaded from Nvidia) would be required for use. The kernel module would not build for 260.19.44 under 12.1 M1.
The 260.19.44 driver is the last one for which desktop effects worked correctly for me. With the 270.xx.xx and 275.xx.xx I had to disable desktop effects due to various problems. Even then, there was still a problem with the titlebar blacking out in the middle when hovered over in some window decorations. So I wanted to figure out how to get the 260.19.44 driver to build the kernel module under 12.1 M1.
Turns out it was simple. Extract the NVIDIA-Linux-x86_64-260.19.44.run with the -x switch. Change into the NVIDIA-Linux-x86_64-260.19.44/kernel directory and open file nv-linux.h and change line 90 from #include
to #include . Logout from KDE, login to console as root, init 3, cd to wherever the above directory was extracted and run the nvidia-installer as you normally would. Driver installs, reboot, and now you can turn the KDE/KWin Desktop Effects on again and everything is running the way it did under my old 11.4. As far as any deeper stuff is concerned, such as the classic NVIDIA vs KWin devs back and forth I can't address (way out of my league). I believe this problem is triggered with the move to the 2.6.39-2-desktop kernel. Unclear as to very specific details, but I seem to recall some mention of kernel locks removal. All I can say is I am happily running the 260.19.44 driver under 12.1 M1 and Kwin Desktop Effects are once again running fine.
As to why others have not seen this I do not know. I do hope this may help anyone who may encounter what I did. This is not the correct approach for a long term fix, but it is maybe a good interim solution for now. My hardware is nothing special - it's only a Nvidia GTS 450. It would really be nice if NVIDIA would fix their drivers, which is what I was initially waiting for - but when 275.09.07 dropped and they had not I went looking for this work around.
-Mike -- Without Questions there are no Answers!
Alin Marin ELENA Advanced Molecular Simulation Research Laboratory School of Physics, University College Dublin ---- Ardionsamblú Móilíneach Saotharlann Taighde Scoil na Fisice, An Coláiste Ollscoile, Baile Átha Cliath ----------------------------------------------------------------------------------- http://alin.elenaworld.net ______________________________________________________________________
Alin Marin Elena wrote:
Hi,
this time it may not be the fault of nvidia (i am on nvidia too)... as I heard similar reports for ati and intel... and someone was blaming mesa...
Lot of Mesa changes lately, I think Intel is pushing some of it so as to get improvements for their Linux support. Been seeing a lot on Phoronix about this.
I suspect you are using oxygen... if you change to something else do you still have issues?
Not using Oxygen but rather QtCurve with Sonar icon theme. I did try a couple of other styles and it made no difference - still had to disable KWin desktop effects. It isn't that the desktop would not come up, it was more an extreme sluggishness. Examples would include typing in Konsole - type one character and it would be 6 seconds before it displayed kind of thing. You had to click a menu item on the menu bar as it would not highlight on hover. When the popup displayed it was dark but would eventually get the right background at some point after the mouse got over it. Start Firefox and it was only a big black box. And even disabling desktop effects didn't fix the Firefox situation. None of this happens with version 260.19.44. I think I've seen a couple of comments somewhere about regressions in latest NVIDIA code but I don't really know enough about that. I also have a hand-coded xorg.conf for configuring Twinview for use with two monitors. For testing I tried removing it and allowing Xorg to auto-configure itself. I would only get one monitor this way, but the problem remained present. I even tried nomodeset with corresponding change in sysconfig. Nothing I tried, short of going back to 260.19.44 made any difference. I have seen very similar occurrences in the past - and not just with Nvidia but also with Catalyst drivers I had been using before I bought the Nvidia card. I believe what I recall is a tendency of driver code writers to always say something to the affect of: "we've made changes x, y, z, etc to make stuff better, faster, etc, and any breakages in things like KWin as a result of changes we made need to be followed/fixed by said KWin people, etc...". Don't know if this is exactly what has happened this time, or not, it just 'feels' eerily similar to these past occurrences. -Mike [snip] -- To unsubscribe, e-mail: opensuse-factory+unsubscribe@opensuse.org For additional commands, e-mail: opensuse-factory+help@opensuse.org
ok... so it seems we speak about different bugs... that still have to hit me...
Alin
On 16 June 2011 12:43, Michael Powell
Alin Marin Elena wrote:
Hi,
this time it may not be the fault of nvidia (i am on nvidia too)... as I heard similar reports for ati and intel... and someone was blaming mesa...
Lot of Mesa changes lately, I think Intel is pushing some of it so as to get improvements for their Linux support. Been seeing a lot on Phoronix about this.
I suspect you are using oxygen... if you change to something else do you still have issues?
Not using Oxygen but rather QtCurve with Sonar icon theme. I did try a couple of other styles and it made no difference - still had to disable KWin desktop effects. It isn't that the desktop would not come up, it was more an extreme sluggishness. Examples would include typing in Konsole - type one character and it would be 6 seconds before it displayed kind of thing. You had to click a menu item on the menu bar as it would not highlight on hover. When the popup displayed it was dark but would eventually get the right background at some point after the mouse got over it. Start Firefox and it was only a big black box. And even disabling desktop effects didn't fix the Firefox situation.
None of this happens with version 260.19.44. I think I've seen a couple of comments somewhere about regressions in latest NVIDIA code but I don't really know enough about that. I also have a hand-coded xorg.conf for configuring Twinview for use with two monitors. For testing I tried removing it and allowing Xorg to auto-configure itself. I would only get one monitor this way, but the problem remained present. I even tried nomodeset with corresponding change in sysconfig. Nothing I tried, short of going back to 260.19.44 made any difference.
I have seen very similar occurrences in the past - and not just with Nvidia but also with Catalyst drivers I had been using before I bought the Nvidia card. I believe what I recall is a tendency of driver code writers to always say something to the affect of: "we've made changes x, y, z, etc to make stuff better, faster, etc, and any breakages in things like KWin as a result of changes we made need to be followed/fixed by said KWin people, etc...". Don't know if this is exactly what has happened this time, or not, it just 'feels' eerily similar to these past occurrences.
-Mike
[snip]
-- To unsubscribe, e-mail: opensuse-factory+unsubscribe@opensuse.org For additional commands, e-mail: opensuse-factory+help@opensuse.org
-- To unsubscribe, e-mail: opensuse-factory+unsubscribe@opensuse.org For additional commands, e-mail: opensuse-factory+help@opensuse.org
participants (2)
-
Alin Marin Elena -
Michael Powell