Re: xorg update clobbers Nvidia GL
On Sat, 2008-08-16 at 13:56 -0500, Jordi Gutiérrez Hermoso wrote: > 2008/8/16 Patrick Wiseman <[EMAIL PROTECTED]>: > > If I use nvidia-installer to UNinstall the drivers, > > Btw, the installer from nvidia's website doesn't play nicely with > Debian's packaging system, as you have seen. The Debian way to do it > is something like this: Actually, the list is even shorter than you think: a-i does quite a lot. > update-pciids > m-a a-i nvidia > depmod -a > modprobe nvidia > dpkg-reconfigure xserver-xorg -- Paul Johnson [EMAIL PROTECTED] signature.asc Description: This is a digitally signed message part
Re: xorg update clobbers Nvidia GL
On 08/17/08 15:59, Hugo Vanwoerkom wrote: Ron Johnson wrote: On 08/16/08 12:57, Patrick Wiseman wrote: Hello: It seems every time xorg is updated it clobbers my Nvidia driver and, all of a sudden, those cool GLX screen savers, not to mention Google Earth (a mission-critical application!) don't work. If I use nvidia-installer to UNinstall the drivers, it tells me '/usr/lib/xorg/modules/extensions/libglx.so is not a symbolic link', whereas, right after installing the nvidia drivers, it IS. So, what I'm wondering is whether there's any way to protect a symbolic link from being overwritten. Ordinarily, if I want to protect a file, I'll make it read- or read-and-execute-only, but a symbolic link is always 'lrwxrwxrwx' and 'chmod 555 link' just changes the permissions on the underlying file. Perhaps that will protect the link from being replaced with a file, but I'm not confident! A hack solution would be simply to rename the underlying file to the link name and make THAT unwritable, but I think that might confuse the nvidia installer. Any suggestions will be welcome. After any xorg update, I go into /usr/lib/xorg/modules/extensions and manually symlink the nvidia libglx.so.XXX.YY.ZZ to libglx.so. Good point. But you have stated this at least 6 times in the last couple of years. People must forget. People use so many different terms and ways of phrasing the same problem that Googling can sometimes be a futile exercise. Especially if you are a n00b or casual user. -- Ron Johnson, Jr. Jefferson LA USA "Do not bite at the bait of pleasure till you know there is no hook beneath it." -- Thomas Jefferson -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
Re: xorg update clobbers Nvidia GL
Ron Johnson wrote: On 08/16/08 12:57, Patrick Wiseman wrote: Hello: It seems every time xorg is updated it clobbers my Nvidia driver and, all of a sudden, those cool GLX screen savers, not to mention Google Earth (a mission-critical application!) don't work. If I use nvidia-installer to UNinstall the drivers, it tells me '/usr/lib/xorg/modules/extensions/libglx.so is not a symbolic link', whereas, right after installing the nvidia drivers, it IS. So, what I'm wondering is whether there's any way to protect a symbolic link from being overwritten. Ordinarily, if I want to protect a file, I'll make it read- or read-and-execute-only, but a symbolic link is always 'lrwxrwxrwx' and 'chmod 555 link' just changes the permissions on the underlying file. Perhaps that will protect the link from being replaced with a file, but I'm not confident! A hack solution would be simply to rename the underlying file to the link name and make THAT unwritable, but I think that might confuse the nvidia installer. Any suggestions will be welcome. After any xorg update, I go into /usr/lib/xorg/modules/extensions and manually symlink the nvidia libglx.so.XXX.YY.ZZ to libglx.so. Good point. But you have stated this at least 6 times in the last couple of years. People must forget. Hugo -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
Re: xorg update clobbers Nvidia GL
Jordi Gutiérrez Hermoso wrote: > 2008/8/16 Patrick Wiseman <[EMAIL PROTECTED]>: >> If I use nvidia-installer to UNinstall the drivers, > > Btw, the installer from nvidia's website doesn't play nicely with > Debian's packaging system, as you have seen. The Debian way to do it > is something like this: > > update-pciids > apt-get install module-assistant nvidia-kernel-source > m-a prepare > m-a a-i nvidia > apt-get install nvidia-glx > depmod -a > modprobe nvidia > dpkg-reconfigure xserver-xorg I don't think the last command will work anymore. It will just ask a small set of questions about the keyboard and the mouse, I think, and that is it. It has stopped asking about display altogether. I have had to actually delete the xorg.conf file to let xorg generate a new file by itself. It appears that xorg.conf does a better job of display detection and the xserver-xorg is thus not dealing with it anymore. So, I have had to manually insert the "nvidia" string to make xorg use nvidia in the recent past. I hope I am not waaay wrong about this. Let me know if I am ->HS > HTH, > - Jordi G. H. > > -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
Re: xorg update clobbers Nvidia GL
On 08/16/08 13:51, Jordi Gutiérrez Hermoso wrote: 2008/8/16 Patrick Wiseman <[EMAIL PROTECTED]>: It seems every time xorg is updated it clobbers my Nvidia driver Of course it clobbers it; it's a blob. The only fix is to reinstall the latest nvidia driver each time you update Xorg. No. Just recreate the necessary symlink. The real solution, though, is to get nvidia to free up their blob, but nvidia has stated on repeated occasions that it won't do so. Maybe the nouveau project will be usable one of these days. -- Ron Johnson, Jr. Jefferson LA USA "Do not bite at the bait of pleasure till you know there is no hook beneath it." -- Thomas Jefferson -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
Re: xorg update clobbers Nvidia GL
On 08/16/08 14:24, Jack Schneider wrote: On Sat, 16 Aug 2008 13:57:51 -0500 Ron Johnson <[EMAIL PROTECTED]> wrote: On 08/16/08 12:57, Patrick Wiseman wrote: Hello: It seems every time xorg is updated it clobbers my Nvidia driver and, all of a sudden, those cool GLX screen savers, not to mention Google Earth (a mission-critical application!) don't work. If I use nvidia-installer to UNinstall the drivers, it tells me '/usr/lib/xorg/modules/extensions/libglx.so is not a symbolic link', whereas, right after installing the nvidia drivers, it IS. So, what I'm wondering is whether there's any way to protect a symbolic link from being overwritten. Ordinarily, if I want to protect a file, I'll make it read- or read-and-execute-only, but a symbolic link is always 'lrwxrwxrwx' and 'chmod 555 link' just changes the permissions on the underlying file. Perhaps that will protect the link from being replaced with a file, but I'm not confident! A hack solution would be simply to rename the underlying file to the link name and make THAT unwritable, but I think that might confuse the nvidia installer. Any suggestions will be welcome. After any xorg update, I go into /usr/lib/xorg/modules/extensions and manually symlink the nvidia libglx.so.XXX.YY.ZZ to libglx.so. Hey, Ron Does yours look like this??? lrwxrwxrwx 1 root root 19 2008-07-13 16:25 libglx.so -> libglx.so.173.14.09 Yuppers... Sorry about the highjack!!! You're still on-topic, and you haven't changed the Subject line. Thus, no hijack. -- Ron Johnson, Jr. Jefferson LA USA "Do not bite at the bait of pleasure till you know there is no hook beneath it." -- Thomas Jefferson -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
Re: xorg update clobbers Nvidia GL
On Saturday 16 August 2008 22:12:14 debian-user-digest- [EMAIL PROTECTED] wrote: > It seems every time xorg is updated it clobbers my Nvidia driver and, > all of a sudden, those cool GLX screen savers, not to mention Google > Earth (a mission-critical application!) don't work. If I use > nvidia-installer to UNinstall the drivers, it tells me > '/usr/lib/xorg/modules/extensions/libglx.so is not a symbolic link', > whereas, right after installing the nvidia drivers, it IS. So, what > I'm wondering is whether there's any way to protect a symbolic link > from being overwritten. Ordinarily, if I want to protect a file, I'll > make it read- or read-and-execute-only, but a symbolic link is always > 'lrwxrwxrwx' and 'chmod 555 link' just changes the permissions on the > underlying file. Perhaps that will protect the link from being > replaced with a file, but I'm not confident! A hack solution would be > simply to rename the underlying file to the link name and make THAT > unwritable, but I think that might confuse the nvidia installer. > > Any suggestions will be welcome. Alternatives are: After any xorg upgrade go to /usr/lib/xorg/modules/extensions and (as root), make libglx.so a symlink to the libglx.so.### that is nvidia's. Xorg upgrades place there own libglx.so file. OR. There is a way to have nivida put their stuff elsewhere. Look at the --help for their installer OR Use Debian's versions (note that in the past, I had gotten a lower framerate with these but on the otherhand, they might install in cases where the proprietary ones do not). -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
Re: xorg update clobbers Nvidia GL
On Sat, 16 Aug 2008 13:57:51 -0500 Ron Johnson <[EMAIL PROTECTED]> wrote: > On 08/16/08 12:57, Patrick Wiseman wrote: > > Hello: > > > > It seems every time xorg is updated it clobbers my Nvidia driver > > and, all of a sudden, those cool GLX screen savers, not to mention > > Google Earth (a mission-critical application!) don't work. If I use > > nvidia-installer to UNinstall the drivers, it tells me > > '/usr/lib/xorg/modules/extensions/libglx.so is not a symbolic link', > > whereas, right after installing the nvidia drivers, it IS. So, what > > I'm wondering is whether there's any way to protect a symbolic link > > from being overwritten. Ordinarily, if I want to protect a file, > > I'll make it read- or read-and-execute-only, but a symbolic link is > > always 'lrwxrwxrwx' and 'chmod 555 link' just changes the > > permissions on the underlying file. Perhaps that will protect the > > link from being replaced with a file, but I'm not confident! A > > hack solution would be simply to rename the underlying file to the > > link name and make THAT unwritable, but I think that might confuse > > the nvidia installer. > > > > Any suggestions will be welcome. > > After any xorg update, I go into /usr/lib/xorg/modules/extensions > and manually symlink the nvidia libglx.so.XXX.YY.ZZ to libglx.so. > Hey, Ron Does yours look like this??? lrwxrwxrwx 1 root root 19 2008-07-13 16:25 libglx.so -> libglx.so.173.14.09 Sorry about the highjack!!! Jack -- -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
Re: xorg update clobbers Nvidia GL
2008/8/16 Patrick Wiseman <[EMAIL PROTECTED]>: > It seems every time xorg is updated it clobbers my Nvidia driver Of course it clobbers it; it's a blob. The only fix is to reinstall the latest nvidia driver each time you update Xorg. The real solution, though, is to get nvidia to free up their blob, but nvidia has stated on repeated occasions that it won't do so. Maybe the nouveau project will be usable one of these days. - Jordi G. H. -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
Re: xorg update clobbers Nvidia GL
2008/8/16 Patrick Wiseman <[EMAIL PROTECTED]>: > If I use nvidia-installer to UNinstall the drivers, Btw, the installer from nvidia's website doesn't play nicely with Debian's packaging system, as you have seen. The Debian way to do it is something like this: update-pciids apt-get install module-assistant nvidia-kernel-source m-a prepare m-a a-i nvidia apt-get install nvidia-glx depmod -a modprobe nvidia dpkg-reconfigure xserver-xorg HTH, - Jordi G. H. -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
Re: xorg update clobbers Nvidia GL
On 08/16/08 12:57, Patrick Wiseman wrote: Hello: It seems every time xorg is updated it clobbers my Nvidia driver and, all of a sudden, those cool GLX screen savers, not to mention Google Earth (a mission-critical application!) don't work. If I use nvidia-installer to UNinstall the drivers, it tells me '/usr/lib/xorg/modules/extensions/libglx.so is not a symbolic link', whereas, right after installing the nvidia drivers, it IS. So, what I'm wondering is whether there's any way to protect a symbolic link from being overwritten. Ordinarily, if I want to protect a file, I'll make it read- or read-and-execute-only, but a symbolic link is always 'lrwxrwxrwx' and 'chmod 555 link' just changes the permissions on the underlying file. Perhaps that will protect the link from being replaced with a file, but I'm not confident! A hack solution would be simply to rename the underlying file to the link name and make THAT unwritable, but I think that might confuse the nvidia installer. Any suggestions will be welcome. After any xorg update, I go into /usr/lib/xorg/modules/extensions and manually symlink the nvidia libglx.so.XXX.YY.ZZ to libglx.so. -- Ron Johnson, Jr. Jefferson LA USA "Do not bite at the bait of pleasure till you know there is no hook beneath it." -- Thomas Jefferson -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
xorg update clobbers Nvidia GL
Hello: It seems every time xorg is updated it clobbers my Nvidia driver and, all of a sudden, those cool GLX screen savers, not to mention Google Earth (a mission-critical application!) don't work. If I use nvidia-installer to UNinstall the drivers, it tells me '/usr/lib/xorg/modules/extensions/libglx.so is not a symbolic link', whereas, right after installing the nvidia drivers, it IS. So, what I'm wondering is whether there's any way to protect a symbolic link from being overwritten. Ordinarily, if I want to protect a file, I'll make it read- or read-and-execute-only, but a symbolic link is always 'lrwxrwxrwx' and 'chmod 555 link' just changes the permissions on the underlying file. Perhaps that will protect the link from being replaced with a file, but I'm not confident! A hack solution would be simply to rename the underlying file to the link name and make THAT unwritable, but I think that might confuse the nvidia installer. Any suggestions will be welcome. Patrick -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
