Joined: 24 Apr 2002
|Posted: Fri Apr 18, 2003 4:39 pm Post subject: Unmerging nvidia drivers => Difficult to diagnose problem
|So, I can think of three scenarios where you might unmerge your nvidia drivers and not realize that there is a problem:
1) you copied a list of packages from one machine (presumably with a nvidia card in it) to another machine (that doesn't have an nvidia card) and did a
or some such and then realized your mistake and unmerged the nvidia packages
|cat pkg.list | xargs emerge |
2) you upgraded your hardware and no longer have an nvidia card so you unmerged the nvidia packages
3) you were flailing around and for a random reason emerged the nvidia packages and then unmerged them.
Now, you'll note that the post install portion of the nvidia ebuilds will automatically switch the openGL libraries that you are using to the nvidia libs. However, unmerging the nvidia drivers will not automatically revert to the standard X openGL libraries and include files.
Among other things, this cause me the following problems:
1) Trying to run X would result in libraries not being loaded and startx would fail
2) Trying to run X would succeed but various libraries (dri, glx, etc.) would fail to load.
3) PyQT emerge failed.
4) Wine emerge failed (this may or may not related).
The first two problems appeared to me to be issues with my i845G chipset software: DRM kernel module (830) / X Server driver (810). Of course, since they were not the problem, this took an awful long time to diagnose.
The solution is to run
which should take care of manipulating the necessary symbolic links between libraries and between headers. Note, using opengl-update is much easier than doing it by hand (the route I went, since I didn't think about it until now).
|opengl-update xfree |
In short, if you unmerge the nvidia drivers, make sure to run opengl-update. This of course begs the question, "Why isn't it done automatically?" Seems like a good question to me .