I am running Compiz on SUSE 10.1. I had it working fine. Then, an update (a month or two ago) destroyed it. I have now installed the current version, and all I can say is that it is 10 times slower. Really bad. This is with an NVIDIA GeForce 6400. I an using Xgl as the server. I run it under KDE. I suspect the settings are all funny. I have whatever the defaults are. Anyone else have this happen? I have these packages: kicker-compiz-060918-3.1 gset-compiz-0.3.4-20.3 compiz-manager-060917-3.8 compiz-quinncvs_060920-4.2 xorg-x11-driver-video-nvidia-6.9.0-46.15 nvidia-gfx-kmp-default-1.0.8762_2.6.16.21_0.8-1 tiny-nvidia-installer-1.0.7-14 x11-video-nvidia-1.0.8762-1 xgl-cvs_060729-23.3 Re the nvidia driver, I have, of course, specified 'nvidia' in the X configuration. But, I see that the nvidia_drv.so module is a pointer to the nv_drv.so driver. Perhaps this is the way it is now? So, my X log in /var/log no longer says vendor="NVIDIA Corporation" when the driver (/usr/X11R6/lib/modules/drivers/nvidia_drv.so) is loaded. It now says vendor="X.Org Foundation". This seems wrong. Finally, when I run Xgl, it always seems to be a child process of Xorg. I did not expect Xorg to run at all. I have followed the Xgl installation instructions and made /var/X11R6/bin/X a pointer to Xgl instead of Xorg. And I changed it in /etc/sysconfig/desktopmanager. Did I miss something? -- Roger Oberholtzer
On 10/19/06, Roger Oberholtzer <roger@opq.se> wrote:
I am running Compiz on SUSE 10.1. I had it working fine. Then, an update (a month or two ago) destroyed it. I have now installed the current version, and all I can say is that it is 10 times slower. Really bad. This is with an NVIDIA GeForce 6400. I an using Xgl as the server. I run it under KDE. I suspect the settings are all funny. I have whatever the defaults are. Anyone else have this happen?
I have these packages:
kicker-compiz-060918-3.1 gset-compiz-0.3.4-20.3 compiz-manager-060917-3.8 compiz-quinncvs_060920-4.2
compiz-quinn is no longer maintained, you should use compiz-git or beryl packages or the 'official' compiz-cvs packages. You can install beryl and compiz togather and use beryl-manager to switch between those. There is more information on that here: http://wiki.beryl-project.org/index.php/Install/SuSE http://en.opensuse.org/Additional_YaST_Package_Repositories#Alternate_Compiz... and http://forum.beryl-project.org/topic-4853-beryl-suse-packages Cheers! -J
On Thu, 2006-10-19 at 09:58 +0530, Jigish Gohil wrote:
On 10/19/06, Roger Oberholtzer <roger@opq.se> wrote:
I am running Compiz on SUSE 10.1. I had it working fine. Then, an update (a month or two ago) destroyed it. I have now installed the current version, and all I can say is that it is 10 times slower. Really bad. This is with an NVIDIA GeForce 6400. I an using Xgl as the server. I run it under KDE. I suspect the settings are all funny. I have whatever the defaults are. Anyone else have this happen?
I have these packages:
kicker-compiz-060918-3.1 gset-compiz-0.3.4-20.3 compiz-manager-060917-3.8 compiz-quinncvs_060920-4.2
compiz-quinn is no longer maintained, you should use compiz-git or beryl packages or the 'official' compiz-cvs packages. You can install beryl and compiz togather and use beryl-manager to switch between those.
I have been doing the installs via smart. I have held off going to beryl until I sorted out my current issues and also sorted out the best way to transition from compiz to beryl. As to my original post, seems that if you install the nvidia driver via smart, the link from nvidia_drv.so to nv_drv.so is made. Effectively removing the NVIDIA supplied driver, but still letting you specify 'nvidia' in the X config without generating an error. Don't know why. When I installed the driver direct, all became happy again. Compiz and all parts are running smoothly again.
On Sunday 22 October 2006 05:27, Roger Oberholtzer wrote:
On Thu, 2006-10-19 at 09:58 +0530, Jigish Gohil wrote:
On 10/19/06, Roger Oberholtzer <roger@opq.se> wrote:
I am running Compiz on SUSE 10.1. I had it working fine. Then, an update (a month or two ago) destroyed it. I have now installed the current version, and all I can say is that it is 10 times slower. Really bad. This is with an NVIDIA GeForce 6400. I an using Xgl as the server. I run it under KDE. I suspect the settings are all funny. I have whatever the defaults are. Anyone else have this happen?
I have these packages:
kicker-compiz-060918-3.1 gset-compiz-0.3.4-20.3 compiz-manager-060917-3.8 compiz-quinncvs_060920-4.2
compiz-quinn is no longer maintained, you should use compiz-git or beryl packages or the 'official' compiz-cvs packages. You can install beryl and compiz togather and use beryl-manager to switch between those.
I have been doing the installs via smart. I have held off going to beryl until I sorted out my current issues and also sorted out the best way to transition from compiz to beryl.
As to my original post, seems that if you install the nvidia driver via smart, the link from nvidia_drv.so to nv_drv.so is made. Effectively removing the NVIDIA supplied driver, but still letting you specify 'nvidia' in the X config without generating an error. Don't know why.
Trying to be "smart", but who is at fault. The configuration program (sax) or postinstall script in the rpm that you tried to install. Do you have any reference to location of package that you tried to install with smart?
When I installed the driver direct, all became happy again. Compiz and all parts are running smoothly again.
-- Regards, Rajko M.
On Sun, 2006-10-22 at 09:46 -0500, Rajko M wrote:
On Sunday 22 October 2006 05:27, Roger Oberholtzer wrote:
As to my original post, seems that if you install the nvidia driver via smart, the link from nvidia_drv.so to nv_drv.so is made. Effectively removing the NVIDIA supplied driver, but still letting you specify 'nvidia' in the X config without generating an error. Don't know why.
Trying to be "smart", but who is at fault. The configuration program (sax) or postinstall script in the rpm that you tried to install. Do you have any reference to location of package that you tried to install with smart?
ftp://download.nvidia.com/novell, which can be added as an rpm-md repository. I think it can also be used from yast. But I am pretty sure when used from smart, the odd link appeared. I do not recall which version of the driver was installed this way. It would be whatever one was available late September. It could also be some non-NVIDIA wrapper that did this. -- Roger Oberholtzer
On Sunday 22 October 2006 12:42, Roger Oberholtzer wrote:
On Sun, 2006-10-22 at 09:46 -0500, Rajko M wrote:
On Sunday 22 October 2006 05:27, Roger Oberholtzer wrote:
As to my original post, seems that if you install the nvidia driver via smart, the link from nvidia_drv.so to nv_drv.so is made. Effectively removing the NVIDIA supplied driver, but still letting you specify 'nvidia' in the X config without generating an error. Don't know why.
Trying to be "smart", but who is at fault. The configuration program (sax) or postinstall script in the rpm that you tried to install. Do you have any reference to location of package that you tried to install with smart?
ftp://download.nvidia.com/novell, which can be added as an rpm-md repository. I think it can also be used from yast. But I am pretty sure when used from smart, the odd link appeared. I do not recall which version of the driver was installed this way. It would be whatever one was available late September. It could also be some non-NVIDIA wrapper that did this.
I just looked in nvidia-gfx-kmp-default-1.0.8762_2.6.16.21_0.8-1.i586.rpm postinstall scripts and it has nothing that will perform linking to nv driver. Even post uninstall will not do that, which might sound logical if previous driver was nv. Maybe, it is possible to find something on http://bugzilla.novell.com that will explain this. I'll see tomorrow. -- Regards, Rajko M.
On Sun, 2006-10-22 at 23:14 -0500, Rajko M wrote:
On Sunday 22 October 2006 12:42, Roger Oberholtzer wrote:
On Sun, 2006-10-22 at 09:46 -0500, Rajko M wrote:
On Sunday 22 October 2006 05:27, Roger Oberholtzer wrote:
As to my original post, seems that if you install the nvidia driver via smart, the link from nvidia_drv.so to nv_drv.so is made. Effectively removing the NVIDIA supplied driver, but still letting you specify 'nvidia' in the X config without generating an error. Don't know why.
Trying to be "smart", but who is at fault. The configuration program (sax) or postinstall script in the rpm that you tried to install. Do you have any reference to location of package that you tried to install with smart?
ftp://download.nvidia.com/novell, which can be added as an rpm-md repository. I think it can also be used from yast. But I am pretty sure when used from smart, the odd link appeared. I do not recall which version of the driver was installed this way. It would be whatever one was available late September. It could also be some non-NVIDIA wrapper that did this.
I just looked in nvidia-gfx-kmp-default-1.0.8762_2.6.16.21_0.8-1.i586.rpm postinstall scripts and it has nothing that will perform linking to nv driver. Even post uninstall will not do that, which might sound logical if previous driver was nv.
Is the X server part in the same RPM as the kernel modules? -- Roger Oberholtzer OPQ Systems AB Ramböll Sverige AB Kapellgränd 7 P.O. Box 4205 SE-102 65 Stockholm, Sweden Tel: Int +46 8-615 60 20 Fax: Int +46 8-31 42 23
On Monday 23 October 2006 01:23, Roger Oberholtzer wrote: .....
ftp://download.nvidia.com/novell, which can be added as an rpm-md repository. I think it can also be used from yast. But I am pretty sure when used from smart, the odd link appeared. I do not recall which version of the driver was installed this way. It would be whatever one was available late September. It could also be some non-NVIDIA wrapper that did this.
I just looked in nvidia-gfx-kmp-default-1.0.8762_2.6.16.21_0.8-1.i586.rpm postinstall scripts and it has nothing that will perform linking to nv driver. Even post uninstall will not do that, which might sound logical if previous driver was nv.
Is the X server part in the same RPM as the kernel modules?
X server part is not in the same package. The only files that you can find in above rpm are /lib/modules/2.6.16.21-0.8-default/updates/nvidia.ko and 3 scripts POSTIN, POSTUN, PREUN. The package x11-video-nvidia-1.0.8762-1.i586.rpm has X server part including this 2 scripts. #postinstall scriptlet (through /bin/sh): #/sbin/ldconfig #test -x usr/bin/switch2nvidia && usr/bin/switch2nvidia #if ls var/lib/hardware/ids/* &> /dev/null; then # > var/lib/hardware/hd.ids # for i in var/lib/hardware/ids/*; do # cat $i >> var/lib/hardware/hd.ids # done #fi #exit 0 Where switch2nvidia is simple script that will replace any "nv" with "nvidia" in xorg.conf. #postuninstall scriptlet (through /bin/sh): #/sbin/ldconfig #if [ "$1" -eq 0 ]; then # test -x usr/bin/switch2nv && usr/bin/switch2nv # if ls var/lib/hardware/ids/* &> /dev/null; then # > var/lib/hardware/hd.ids # for i in var/lib/hardware/ids/*; do # cat $i >> var/lib/hardware/hd.ids # done # else # rm -f var/lib/hardware/hd.ids # fi #fi #exit 0 The switch2nv is calling tiny-nvidia-installer --uninstall -s to remove nvidia driver silently, before change any "nvidia" to "nv" in xorg.conf. Now is again late. It would be interesting to see the file that you downloaded, but I don't know where Smart can keep copies. If you find something, let me know. -- Regards, Rajko M.
On Mon, 2006-10-23 at 23:29 -0500, Rajko M wrote:
On Monday 23 October 2006 01:23, Roger Oberholtzer wrote: .....
ftp://download.nvidia.com/novell, which can be added as an rpm-md repository. I think it can also be used from yast. But I am pretty sure when used from smart, the odd link appeared. I do not recall which version of the driver was installed this way. It would be whatever one was available late September. It could also be some non-NVIDIA wrapper that did this.
I just looked in nvidia-gfx-kmp-default-1.0.8762_2.6.16.21_0.8-1.i586.rpm postinstall scripts and it has nothing that will perform linking to nv driver. Even post uninstall will not do that, which might sound logical if previous driver was nv.
Is the X server part in the same RPM as the kernel modules?
X server part is not in the same package.
The only files that you can find in above rpm are /lib/modules/2.6.16.21-0.8-default/updates/nvidia.ko and 3 scripts POSTIN, POSTUN, PREUN.
The package x11-video-nvidia-1.0.8762-1.i586.rpm has X server part including this 2 scripts.
#postinstall scriptlet (through /bin/sh): #/sbin/ldconfig #test -x usr/bin/switch2nvidia && usr/bin/switch2nvidia #if ls var/lib/hardware/ids/* &> /dev/null; then # > var/lib/hardware/hd.ids # for i in var/lib/hardware/ids/*; do # cat $i >> var/lib/hardware/hd.ids # done #fi #exit 0
Where switch2nvidia is simple script that will replace any "nv" with "nvidia" in xorg.conf.
#postuninstall scriptlet (through /bin/sh): #/sbin/ldconfig #if [ "$1" -eq 0 ]; then # test -x usr/bin/switch2nv && usr/bin/switch2nv # if ls var/lib/hardware/ids/* &> /dev/null; then # > var/lib/hardware/hd.ids # for i in var/lib/hardware/ids/*; do # cat $i >> var/lib/hardware/hd.ids # done # else # rm -f var/lib/hardware/hd.ids # fi #fi #exit 0
The switch2nv is calling tiny-nvidia-installer --uninstall -s to remove nvidia driver silently, before change any "nvidia" to "nv" in xorg.conf.
Now is again late. It would be interesting to see the file that you downloaded, but I don't know where Smart can keep copies.
If you find something, let me know.
Not much. I may very well have cleaned the smart cache as well. I did see that tiny-nvidia-installer has some symbolic linking stuff in it: (assuming it uses a system() call to do this): strings /usr/bin/tiny-nvidia-installer | grep "ln -s" produced: The symbolic link '%s' does not exist. This is necessary for correct operation of the %s. You can create this symbolic link manually by executing `ln -sf %s %s`. The symbolic link '%s' does not point to '%s' as is necessary for correct operation of the %s. It is possible that `ldconfig` has created this incorrect symbolic link because %s's "soname" conflicts with that of %s. It is recommended that you remove or rename the file '%s' and create the necessary symbolic link by running `ln -sf %s %s`. Of course, that does not mean it made the symbolic link. Unless it failed on install and tried to undo whatever it had done by placing the link so modified config files where it replaced nv with nvidia would still work. All speculation. Here in is one problem with closed source code... -- Roger Oberholtzer OPQ Systems AB Ramböll Sverige AB Kapellgränd 7 P.O. Box 4205 SE-102 65 Stockholm, Sweden Tel: Int +46 8-615 60 20 Fax: Int +46 8-31 42 23
On Tuesday 24 October 2006 01:11, Roger Oberholtzer wrote:
On Mon, 2006-10-23 at 23:29 -0500, Rajko M wrote:
On Monday 23 October 2006 01:23, Roger Oberholtzer wrote: ....... The package x11-video-nvidia-1.0.8762-1.i586.rpm has X server part including this 2 scripts.
"Morning is smarter than evening" is old saying. This is driver file location in above package /usr/X11R6/lib/modules/updates/drivers/nvidia_drv.so and this is on a system /usr/X11R6/lib/modules/drivers/nvidia_drv.so It is the same for 10.0 and 10.1. The 10.1 is the same as SLED 10. So your update was probably installed in directory that is listed in rpm file. .......
Of course, that does not mean it made the symbolic link. Unless it failed on install and tried to undo whatever it had done by placing the link so modified config files where it replaced nv with nvidia would still work.
That might be one possible reason to create the link, but it means that you tried to uninstall the nvidia driver, because that is the only way to run post-uninstall script that will call tiny-nvidia-installer. Post-install script just replaces string "nv" with "nvidia" in section "Drivers" of xorg.conf. That is the case in 10.1 and 10.2 alpha. In version 10.0 script replaces any "nv" with "nvidia". The search and replacement strings include both "". I had few problems with nvidia-installer that was downloaded with tiny-nvidia-installer --update it changed xorg.conf for both displays to "nvidia". Second needs "ati" driver :-) BTW, the nvidia-installer is not really comfortable. For instance: I missed to prepare kernel sources before running installer and it offered to download kernel without telling the download source and version. That can end with kernel that is not compatible with the rest of the system, so I refused offer, and than it ran preparation for me, compiled driver and installed it. Strange that it didn't offered to prepare existing kernel sources first. ..... It can be that Smart did just what is programmed to do, install rpm, run post-install script and that is all. New driver was in wrong place that only original SLED 10 software management can find. -- Regards, Rajko M.
On Tuesday 24 October 2006 20:26, Rajko M wrote: .....
It can be that Smart did just what is programmed to do, install rpm, run post-install script and that is all. New driver was in wrong place that only original SLED 10 software management can find.
The link nvidia_drv.so -> nv_drv.so is a part of default Xorg installation. It is the only thing in package: xorg-x11-driver-video-nvidia-6.9.0-46.i586.rpm that belongs to 10.1 GM and you can find it in suse/i586 directory on CD1. The nv_drv.so is in xorg-x11-driver-video-6.9.0-46.i586.rpm. So, symlink is part of default 10.1 installation. Smart did installation of nVidia rpm in a proper way, including running post-install script, but something is missing in that script than would place nvidia_drv.so in a right place. Missing part might be included in SLED 10. -- Regards, Rajko M.
On Tue, 2006-10-24 at 23:16 -0500, Rajko M wrote:
On Tuesday 24 October 2006 20:26, Rajko M wrote: .....
It can be that Smart did just what is programmed to do, install rpm, run post-install script and that is all. New driver was in wrong place that only original SLED 10 software management can find.
The link nvidia_drv.so -> nv_drv.so is a part of default Xorg installation. It is the only thing in package: xorg-x11-driver-video-nvidia-6.9.0-46.i586.rpm that belongs to 10.1 GM and you can find it in suse/i586 directory on CD1. The nv_drv.so is in xorg-x11-driver-video-6.9.0-46.i586.rpm.
So, symlink is part of default 10.1 installation.
Smart did installation of nVidia rpm in a proper way, including running post-install script, but something is missing in that script than would place nvidia_drv.so in a right place. Missing part might be included in SLED 10.
At least we can see where the link came from. I am not loosing my mind. I wonder why this link would be done? Is X.org wanting to 'hide' the nvidia corp driver? I would think no one would have 'nvidia' in their X config unless they DID want the nvidia corp driver. Xorg should restrict itself to its own driver: nv. The xorg-x11-driver-video-nvidia rpm should only fiddle with Xorg's .'nv' driver. NOT nvidia corps' 'nvidia' driver. And, I think it does this destructively: The nvidia corp driver and kernel modules were already installed when this link was made. It effectively erased the nvidia corp driver and replaced it with a link to the Xorg driver. Thanks for your help. -- Roger Oberholtzer OPQ Systems AB Ramböll Sverige AB Kapellgränd 7 P.O. Box 4205 SE-102 65 Stockholm, Sweden Tel: Int +46 8-615 60 20 Fax: Int +46 8-31 42 23
On Wednesday 25 October 2006 01:43, Roger Oberholtzer wrote:
I wonder why this link would be done? Is X.org wanting to 'hide' the nvidia corp driver? I would think no one would have 'nvidia' in their X config unless they DID want the nvidia corp driver. Xorg should restrict itself to its own driver: nv. The xorg-x11-driver-video-nvidia rpm should only fiddle with Xorg's .'nv' driver. NOT nvidia corps' 'nvidia' driver. And, I think it does this destructively: The nvidia corp driver and kernel modules were already installed when this link was made. It effectively erased the nvidia corp driver and replaced it with a link to the Xorg driver.
Note that Xorg --> SUSE --> your computer, not Xorg --> your computer. If you compile and install original xorg 6.9.0 it will mess SUSE installation, as it is different that xorg defaults. Not every file marked as xorg-x11.... belongs to X.org, and this one seems to be quick fix when Novell decided not to include proprietary drivers in openSUSE. Otherwise how to explain that whole rpm contains only one symlink, and uninstall script for existing driver. For particular file, is not clear how it was installed as nvidia (from ftp) rpm doesn't require it. It is possible trough indirect dependency, or Smart used the package with bigger version number as both are listed to provide the same nvidia driver :-) Anyhow, dust is cleared, and now you know that Smart shouldn't be used for sensitive (read system) updates. -- Regards, Rajko M.
On Tue, 2006-10-24 at 20:26 -0500, Rajko M wrote:
On Tuesday 24 October 2006 01:11, Roger Oberholtzer wrote:
On Mon, 2006-10-23 at 23:29 -0500, Rajko M wrote:
On Monday 23 October 2006 01:23, Roger Oberholtzer wrote: ....... The package x11-video-nvidia-1.0.8762-1.i586.rpm has X server part including this 2 scripts.
"Morning is smarter than evening" is old saying.
This is driver file location in above package /usr/X11R6/lib/modules/updates/drivers/nvidia_drv.so and this is on a system /usr/X11R6/lib/modules/drivers/nvidia_drv.so
It is the same for 10.0 and 10.1. The 10.1 is the same as SLED 10.
So your update was probably installed in directory that is listed in rpm file.
.......
Of course, that does not mean it made the symbolic link. Unless it failed on install and tried to undo whatever it had done by placing the link so modified config files where it replaced nv with nvidia would still work.
That might be one possible reason to create the link, but it means that you tried to uninstall the nvidia driver, because that is the only way to run post-uninstall script that will call tiny-nvidia-installer.
Or, smart did the uninstall. I have been curious how smart (and You/Yast for that matter) can install the nvidia driver as the driver install always wants a run level without the X server running. Perhaps this is the problem. -- Roger Oberholtzer OPQ Systems AB Ramböll Sverige AB Kapellgränd 7 P.O. Box 4205 SE-102 65 Stockholm, Sweden Tel: Int +46 8-615 60 20 Fax: Int +46 8-31 42 23
participants (3)
-
Jigish Gohil -
Rajko M -
Roger Oberholtzer