[gobolinux-users] Trying to install nVIDIA - script may need update

[Jonas Karlsson]

On Sun, 01 Apr 2007 19:20:09 +0200, teique <teique at gmail.com> wrote:

> Nick Matteo wrote:
>> On 3/31/07, teique <teique at gmail.com> wrote:
>>
>>> !! /lib/libGL.so.1 -> libGL.so.1.5.060500
>>> *mmm*, the beggining of my Konsole history is lost by now :/
>>> as I remember, I did
>>> $ link -sf libGL.so.1.0.9755 /lib/libGL.so.1
>>> so it was towards nvidia,
>>> and then, by curiosity and to let ldconfig happen thru SymlinkProgram,
>>> I run
>>> $ SymlinkProgram nvidia
>>> and it symlinked back again to mesa one...
>>> $ /lib/libGL.so.1 -> libGL.so.1.5.060500
>>> (offtopic: I wonder if there is a way to default Konsole to unlimited
>>> history on new sessions...)
>>>
>>
>> There certainly is, just set the history to unlimited, then choose
>> "settings->save as default"
>>
>> SymlinkProgram nvidia shouldn't point anything towards mesa, unless
>> the libGL.so.1 in the nvidia directory is pointing at
>> libGL.so.1.5.060500?
>>
> no, well usually after I fix something I keep it quiet ^^
> but to make it sure I did:
> $ SymlinkProgram mesa
> and I got this symlink back up
> $ libGL.so.1.5.060500 -> /Programs/Mesa/6.5/lib/libGL.so.1.5.060500
> so this one was also restored:
> $ libGL.so.1 -> libGL.so.1.5.060500
>
> then I did this manually, at /lib
> $ ln -sf libGL.so.1.0.9755 libGL.so.1
> so I get this in a fixed way
> $ libGL.so.1 -> libGL.so.1.0.9755
>
> then to test, I run this
> $ SymlinkProgram -c overwrite nvidia
> and I get this pointing again to mesa one,
> $ libGL.so.1 -> libGL.so.1.5.060500
> I mean, I see it points to the latest available library,
> what is a good thing in my point of view,
> so system keeps always updated to the latest available lib,
>
> cuz of that I suggest (if proper, I dunno...), not to change -c overwrite
> but to create a new option like -c forceoverwriteall,
> just to be used in these specific cases
>
> btw, if now I perform
> $ SymlinkProgram firefox
> it doesnt plays with libGL*
> but if I do
> $ SymlinkProgram wine
> it does change libGL.so.1 back to mesa
> so -c forceoverwriteall may prove useless,
> unless there is some way to configure priority on conflicting libs,
> lets say, nvidia libs take priority over other packages libs...
> and this would be setup when -c forceoverwriteall was run...
> anyway these are speculative, as I dunno how symlink idea works
> internally here :)
>
> so the only way I can fix it, is to
> $ rm /lib/libGL.so.1.5.060500
> so after
> $ SymlinkProgram nvidia
> it keeps/is fixed again
>
> I see the mesa one will be missing then at /lib
> I dunno, what limitation it can cause as I dunno to what Mesa is used at
> all :),
> considering nvidia is available instead,
> I mean I believe I could remove mesa package w/o n problems...
> despite I am not willing to do it any soon :)
>
This was a tricky "bug" to reproduce but after some experimenting I found  
out how to do it, and it was just as you did it.
You shouldn't create any relative links inside the /System/Links/Libraries  
(/lib) directory, that's what making this happen, not that the subversions  
of the library differs. As I said, SymlinkProgram takes no heed to what  
subversion of a library exist. Instead the problem is with how readlink  
works, and now I'm not saying that there's a bug in readlink, instead  
there are situations that is impossible to take into account, with how  
symlinks point.

What you should to is to remove the libGL.so.1 link in  
/System/Links/Libraries and instead cd into /Programs/Nvidia/1.0_9755/lib/  
and do 'ln -sf libGL.so.1.0.9755 libGL.so.1'. Then you can try to  
resymlink the Nvidia lib again.

-- 
/Jonas

Using Opera's revolutionary e-mail client: http://www.opera.com/mail/