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.