Since the installation of the openSuse 11.3 months ago,I did no backup,
so I decided,to make a new installation.
All went fine,but what makes me a little insecure,is,that I now stick on the
NVIDEA 260.19.29.
In several posts here,I read about problems with the 260.x.x-version,so I thought,
I was on the right side with the 256.x.x-version.
I tried at once,to change back to the older version,but I did not find it anymore.
Are the problems solved,can I savely use this now with 11.3 and KDE 4.4 on 64 bit?
If not,from where can I get the 256.x.x-version ?
Most (if not all) of the problems reported about 260.x.x seem to be on 32-bit. (I do have some light probs with 260.x.x on 64-bit, but I am more and more doubtful that that is what what others experience).
use packages supplied by forum users. Please_try_again and Ypnose were so kind to upload 32-bit and 64-bit versions to file hosting sites. Check especially the latter pages of the thread NVIDIA 260.19 Issues for links.
I can attest that using openSUSE 11.3 64 bit does work with the nVIDIA 260.19.36 driver. I have not seen the problems that are supposed to occur with 32 bit, but I have not loaded any PC with 32 bit as they all support 64 bit OS installation. Now you can add the nVIDIA repository, search on nVIDIA in YaST Software Management and install just two files and get close to a recent nVIDIA driver and it will not need to be reloaded as long as you update the kernel only within a 2.6.34 version.
Or, you can install the nVIDIA driver the Hard Way, as it is called obtained from the following site:
The script is called lnvhw and message #12 has the most recent version of the script file. If you have not just updated your kernel, which you would need to reboot, you can enter runlevel 3, needed to load the driver, as follows. Open a terminal Session and type:
su -
password:
init 3
root
password:
lnvhw
You do not type the word password, but rather you type in the root password in response to the password prompt. You can only use that last command if you have got the lnvhw script file on your PC.
Thanks for your quick responses !
Tell me,how can I check,if there may be potential problems ?
Just tested with the Plasma-analogclock,it works.Are 3d-games
a good challenge,or what will bring the driver to its limit ?
Thanks for your quick responses !
Tell me,how can I check,if there may be potential problems ?
Just tested with the Plasma-analogclock,it works.Are 3d-games
a good challenge,or what will bring the driver to its limit ?
Greetings !
lostinspace
Normally, playing any sort of video full screen will tell you if it is working, though your multimedia setup also must be correct. Games also work, but openGL ones would be best. I would guess any Windows games you could play in Wine would be a way of checking, but I am not into games much myself.
We have 4 PCs at home with nVidia hardware and openSUSE-11.3.
One is so old (nVidia FX5200 graphics) it does not use the 260.x.x driver, but rather uses a legacy driver. It also runs LXDE and hence does not have the problems noted with nvidia graphic driver.
Of the other 3, they all use the 260.x.x driver on openSUSE-11.3 with KDE-4.4.4 :
Two are 64-bit openSUSE-11.3 (nVidia GTX260 and a G210 graphics) with the proprietary 260.x.x driver and being 64-bit they do not have this problem.
The last one is a 32-bit openSUSE-11.3 with the very latest 260.x.x driver and it does have some hiccups. It has a PCI (not PCI-e) GeForce 8400 GS and to start amarok I need to use the code “strace amarok” and I had to re-install VirtualBox to overcome a “floating point error”. There are also other minor hiccups with this driver. But none of them are thus far blocking for using this 32-bit PC with openSUSE-11.3. I note with the nVidia 260.x.x proprietary graphic driver with VDPAU and mplayer I can play HD videos of a very high resolution and bit rate, where such videos will bring a much faster Dual Core PC to its knees (assuming that Dual Core does not have HD Acceleration of videos).
So it is not all bad news with the 260.x.x driver. A lot depends on how you plan to use your PC.
Sorry for the blowed-up font !I had a new installation,and have to resize the
system/browser-fonts.But late at night,I didn’t get the consequence of enlarging
the font for the readability !
With the 256.x.x,I had an significant improvement in relation to the Nouveau
one,I had before !
So I think,the NVIDEA-drivers are the right choice for me.
Although my pc is humming along with old nvidia driver, I feel compelled to upgrade it! I tried the lnvhw script and it works nicely. Unfortunately, the 260.x.x driver does not. The good thing about the script was that it made it so easy to switch back to the working driver.
When I load the new driver, on reboot I get a plasma crash and the floating point error on krunner (? - the run dialog? which I assume is krunner) that comes so fast that I get dozens of error windows while I’m thinking about what to do (actually, I’m too slow to click them closed as fast as they open.) So should I/can I uninstall plasma and krunner and re-install? Do you do it before the installation of the new driver or afterward?
Even if you uninstall/reinstall plasma with the new driver it will not work.
Try to hit Alt-F2 and fire strace plasma-desktop. You can have that command in the kde4 autostart as a temporary measure.
I am unfamiliar with strace, so I probably did it the wrong way. I installed 260.x.36 and on reboot entered “nomodeset” on the boot line. Having forgotten to add strace plasma-desktop in autostart, I took a chance and typed that on the boot line too. No change in the results. I tried Alt-F2 and while the krunner crash notifications were flying in, I ran strace from the cli. Lots of code scrolled through the console but, to my surprise, the desktop came up! The floating point exceptions on krunner kept coming, so the desktop was not usable. In less than a minute, I had 24 of those bug-reporting boxes open. I rebooted and reinstalled the old nvidia driver. I searched for a log of strace but found only old ones from the summer. I’m guessing that the output was in the console only and not in a file. Sorry I have nothing to show.
