Daniel Feiglin wrote:
Rajko M. wrote:
On Saturday 23 June 2007 15:15, Daniel Feiglin wrote:
Daniel Feiglin wrote:
Situation Summary:
Kernel: 2.6.18.8-0.3-default (latest patch)
KDE: 3.5.5 "release 45.4"
Video card: nVidia, GeForce MX 4000
Driver - from openSUSE (yast installed) fully patched, 1.0-9631
GoogleEarth version: 4.0.2735.0 Same problem with latest, 4.1.7076.4458
When running from a command line, it comes up, shows the logo graphic and then a SIGSEGV -
Google Earth has caught signal 11.
Another crash happened while handling crash!
For what it's worth, i ran the unistall, got rid of ~/.googleearth and re-installed. The problem persists.
If I do the export LD_ASSUME_KERNEL=2.4.10 hack, and then run from the command line I get this:
You have kernel 2.6 and 2.4 kernel hack seems out of place. Though, I didn't looked for information what it means.
/bin/sh: error while loading shared libraries: libdl.so.2: cannot open shared object file: No such file or directory
For the record, this item does exist, in /lib as libdl-2.5.so with libdl.so.2 symlinks from /lib and /usr/lib.
Can't think of anything else.
Google Earth crashes are usually sign of graphic driver problems, and last time I got crashes that was the case. I had GeForce4 MX 4000 AGP card in computer when it happened.
After downloading latest driver and compiling on my own problem disappeared.
The latest driver is: ftp://download.nvidia.com/XFree86/Linux-x86/1.0-9639/
Here in README you can find complete list of supported chipsets, look in section for legacy 1.0-96xx driver series: ftp://download.nvidia.com/XFree86/Linux-x86/1.0-9639/README/appendix-a.html
I believe this to be the right answer - but there is still a fly in the ointment.
Nvidia drivers version 1.0-9639 as available through Yast. Something odd about the rpm's aroused my suspicion. It appears that the rpm's are not clean. They contain 9639 modules and 9631 GL libs. As things stand, I will try to delete the rpm's and replace the drivers from the nvidia supplied bin package (which I used to do before the rpm's became available).
That is also a bit problematic: The good old sh NVIDIA-... .run thing is failing on the "sanity check" - cc not there (Rubbish!)
I'll summarize again as soon as I get a clean 9639 install.
GoogleEarth problem solved - Nvidia driver install problem still open 1. From init level 3, I completely uninstalled the 9631 files, and using text mode yast, uninstalled what ever drivers were there. So at his point we were "clean". 2. Again under text mode yast I re-installed the 9639 drivers (latest release, as "seen" by yast, at least for my installation sources), and a bit more, as in 5. below. 3. I would have preferred to use the nvidia package, but I could not persuade it to believe that gcc/libc were really there where they should be. 4. Run up KDE and test googleearth. It works fine. But why? What's changed? 5. In the various target directories mostly under /usr/lib, yast had insisted on restoring 9631 libs. However, during stage 2, I extracted the files from the nvidia run package. I then did a careful comparison of each of the run package files with the installed files. Nvidia very thoughtfully includes the version number in the filename. I was quickly able to ascertain that all of the installed module files were 9639 and all the libs were 9631. It was a simple matter to copy the 9639 lib files to their correct places and manually adjust relevant symlinks. All of this still leaves open the Nvidia run file install failure - which can go to another list or another thread if anyone's interested. The integrity of the openSUSE Nvidia RPM's is an issue that should be addressed here. Thanks to everyone who contributed to this thread.