[SOLVED] Google Earth Segfaults

chrisretusn · 05-07-2021, 09:31 PM

Quote:

Originally Posted by Paulo2

Did you try with nouveau? Here nouveau has that problem too, doesn't show the globe.

No, but I will give it a shot later.

One thing of note after I install the rebuilt google-earth-pro.SlackBuild on the first start of google-earth-pro I got a blanked out screen in section of google-eath-pro were the globe/map appears. Next time I started google-earth-pro all was well.

business_kid · 05-08-2021, 03:52 AM

Quote:

Originally Posted by Paulo2

Graphic card is Intel i915.

That really says nothing except that your graphics (Like mine) suck. the lspci video card tells us how badly they suck.

If you're running the intel driver, I think street view is out. Have you the modesetting driver?

chrisretusn · 05-08-2021, 10:35 AM

Quote:

Originally Posted by Paulo2

Did you try with nouveau? Here nouveau has that problem too, doesn't show the globe.

Just tried it, working here with the nouveau driver.

Paulo2 · 05-08-2021, 05:20 PM

Quote:

Originally Posted by chrisretusn

Just tried it, working here with the nouveau driver.

Thanks, it seems that is something here then.
Fortunately NVidia driver is running rock-solid here.
Thanks to NVidia devs for the --no-unified-memory option

Quote:

Originally Posted by business_kid

That really says nothing except that your graphics (Like mine) suck. the lspci video card tells us how badly they suck.

If you're running the intel driver, I think street view is out. Have you the modesetting driver?

Code:

inxi -G 
Graphics:
  Device-1: Intel Mobile 4 Series Integrated Graphics driver: i915 v: kernel 
  Display: server: X.Org 1.18.3 driver: intel resolution: 1280x800~60Hz 
  OpenGL: renderer: Mesa DRI Mobile Intel GM45 Express v: 2.1 Mesa 11.2.2

It really doesn't handle graphics heavy load. I can play with decent fps only "SuperTuxKart 0.8 class" graphics.
Google-earth is rendered decently with Mesa GL, but sometime ago street view stopped working, I think it is due to Google.

chrisretusn · 05-08-2021, 09:16 PM

[QUOTE=Paulo2;6249320]Thanks, it seems that is something here then.
Fortunately NVidia driver is running rock-solid here.
Thanks to NVidia devs for the --no-unified-memory option

What is the benefit of --no-unified-memory aside from not installing the NVIDIA Unified Memory kernel module. I know that CUDA needs this module and I don't have CUDA installed away. I've been installing the NVIDIA driver for years without this switch.

Code:

inxi -G -xx
Graphics:  Device-1: NVIDIA GF108 [GeForce GT 730] vendor: Palit Microsystems driver: nvidia 
           v: 390.143 bus-ID: 02:00.0 chip-ID: 10de:0f02 
           Display: server: X.Org 1.20.11 compositor: kwin_x11 driver: loaded: nvidia 
           unloaded: modesetting,nouveau,nv,vesa alternate: fbdev resolution: 1366x768~60Hz s-dpi: 84 
           OpenGL: renderer: GeForce GT 730/PCIe/SSE2 v: 4.6.0 NVIDIA 390.143 direct render: Yes

Paulo2 · 05-09-2021, 08:09 AM

Quote:

Originally Posted by chrisretusn

Quote:

Originally Posted by Paulo2

Thanks, it seems that is something here then.
Fortunately NVidia driver is running rock-solid here.
Thanks to NVidia devs for the --no-unified-memory option

What is the benefit of --no-unified-memory aside from not installing the NVIDIA Unified Memory kernel module. I know that CUDA needs this module and I don't have CUDA installed away. I've been installing the NVIDIA driver for years without this switch.

Code:

inxi -G -xx
Graphics:  Device-1: NVIDIA GF108 [GeForce GT 730] vendor: Palit Microsystems driver: nvidia 
           v: 390.143 bus-ID: 02:00.0 chip-ID: 10de:0f02 
           Display: server: X.Org 1.20.11 compositor: kwin_x11 driver: loaded: nvidia 
           unloaded: modesetting,nouveau,nv,vesa alternate: fbdev resolution: 1366x768~60Hz s-dpi: 84 
           OpenGL: renderer: GeForce GT 730/PCIe/SSE2 v: 4.6.0 NVIDIA 390.143 direct render: Yes

inxi output here

Code:

$ inxi -G -xx
Graphics:
  Device-1: NVIDIA GM206 [GeForce GTX 960] vendor: eVga.com. driver: nvidia 
  v: 465.27 bus-ID: 01:00.0 chip-ID: 10de:1401 
  Display: server: X.Org 1.20.11 driver: loaded: nvidia 
  resolution: 1680x1050~60Hz s-dpi: 87 
  OpenGL: renderer: NVIDIA GeForce GTX 960/PCIe/SSE2 v: 4.6.0 NVIDIA 465.27 
  direct render: Yes

About unified memory, if I understood right what I read, is a way to use the GPU processor in parallel with main CPU for general use,
not only graphics software. Also is a way to unify main RAM memory and GPU own memory.
https://en.wikipedia.org/wiki/CUDA
https://developer.nvidia.com/blog/un...ory-in-cuda-6/

NVidia driver was working rock-solid until mid-2017, then it started to freeze X session.
It seems that they changed something with the CUDA driver that my hardware cannot handle.
I don't see any downgrade in performance for not using CUDA driver, I think a software
must be specifically written to use it.

chrisretusn · 05-09-2021, 10:58 AM

Quote:

Originally Posted by Paulo2

About unified memory, if I understood right what I read, is a way to use the GPU processor in parallel with main CPU for general use,
not only graphics software. Also is a way to unify main RAM memory and GPU own memory.
https://en.wikipedia.org/wiki/CUDA
https://developer.nvidia.com/blog/un...ory-in-cuda-6/

NVidia driver was working rock-solid until mid-2017, then it started to freeze X session.
It seems that they changed something with the CUDA driver that my hardware cannot handle.
I don't see any downgrade in performance for not using CUDA driver, I think a software
must be specifically written to use it.

Thanks. That's the way I read it too. To use CUDA you need the driver from NVIDIA, which version needed of CUDA depends on your graphics card. Since I have no reason to use GPU processing or any programs installed that needed it, when I reinstalled the NVIDIA driver I used the --no-unified-memory switch.

I have an occasional freeze problem on logging out from X back to runlevel 3. Not really a hard freeze though, I could ssh in to this computer and restart or shutdown, pressing off/on switch also started a shutdown, though I couldn't see it progress until the shutdown occurred. Maybe this will be the solution, maybe not, time will tell.

business_kid · 05-09-2021, 12:21 PM

Quote:

Originally Posted by Paulo2

Thanks, it seems that is something here then.
Fortunately NVidia driver is running rock-solid here.
Thanks to NVidia devs for the --no-unified-memory option

Code:

inxi -G 
Graphics:
  Device-1: Intel Mobile 4 Series Integrated Graphics driver: i915 v: kernel 
  Display: server: X.Org 1.18.3 driver: intel resolution: 1280x800~60Hz 
  OpenGL: renderer: Mesa DRI Mobile Intel GM45 Express v: 2.1 Mesa 11.2.2

It really doesn't handle graphics heavy load. I can play with decent fps only "SuperTuxKart 0.8 class" graphics.
Google-earth is rendered decently with Mesa GL, but sometime ago street view stopped working, I think it is due to Google.

As a guide my HD4000 Ivy Bridge card was released in 2012. On the intel driver, you get no 3D at all, so street view goes. Your GM45 was released in Q3 of 2008, and probably bought in 2009. I would not tax it with 1280x800~60Hz if I could get away with a lower resolution. Use modesetting driver just in case 3D is usable. The intel driver has been deprecated for years.

chrisretusn · 05-10-2021, 04:25 AM

Quote:

Originally Posted by chrisretusn

I have an occasional freeze problem on logging out from X back to runlevel 3. Not really a hard freeze though, I could ssh in to this computer and restart or shutdown, pressing off/on switch also started a shutdown, though I couldn't see it progress until the shutdown occurred. Maybe this will be the solution, maybe not, time will tell.

Time did tell, I logged out, it froze, I ssh'd in a rebooted. Oh well. Did not thing it would work anyway, get the same sort of thing on my Intel chip set laptop.

business_kid · 05-10-2021, 09:17 AM

I gather you guys have hijack my solved thread to discuss graphics. Fine by me, I suppose, although you would get better exposure if you posted your own thread,.

What beats me is why on earth you are using such a crappy video card from 2008 in 2021? Heck, ATI (Radeon) had just been bought by AMD around then, and anything Intel were coming up with was only fit for giving away in breakfast cereal packets

. Why use it now?

chrisretusn · 05-10-2021, 09:46 AM

Hardly hijacked. What we have discussed it related to Google-Earth-Pro. Ya, okay not related to the segmentation fault specifically, but still Google-Earth-Pro working or not working based on graphic drivers used. This crappy old NVIDIA card works just fine for what I use it for. My computer is just as old, guess I should dump that too. This old computer works, I do not see a reason to buy a new one.

Google Earth Pro version 7.3.3.7786 is working here with the replacement libcrypto.so.1.0.0 from openssl10-solibs-1.0.2u-x86_64-2.txz. Happy now back on topic.

Guess you never, ever gone of topic before.

ponce · 05-10-2021, 01:25 PM

Quote:

Originally Posted by Lenard Spencer

NOTE TO PONCE: Matteo, you may want to grab the rest of the tarballs in that folder to merge into the -current repo as well.

Hi Lenard, I had a look at the tarball in the folder and read the note

Quote:

Lenard Spencer's SBo script updates for Slackware 15.0

Here is the list of updates to my SBo scripts for 15.0:
(If it is not listed here, it is already up-to-date in Ponce's repo.)

crispy-doom
update REQUIRES for -current/15.0

dvdbackup
remove CURRENT= switch

FlightGear
update for version 2020.3.8

FlightGear-data
update for version 2020.3.8

gnucash{,-docs}
update for version 4.5

gnucash-legacy{,-docs}
removed (gnucash 2.6.21 no longer starts)

google-earth
update for version 7.3.3, (64-bit only -
32-bit needs google-earth-legacy)
(needs openssl10-solibs from Tadgy's slackware.uk cumulative repo)

google-earth-legacy
rename from google-earth

k9copy-reloaded
remove CURRENT= switch

lives
update for version 3.2.0

nvidia-driver
update for version 460.73.01
patched nvidia-installer
removed CURRENT= switch
removed nvidia-switch ONCE AND FOR ALL

nvidia-kernel
update for version 460.73.01

nvidia-legacy390-driver
update for version 390.143
patched nvidia-installer
removed CURRENT= switch
added douninst.sh

nvidia-legacy390-kernel
update for version 390.143

OpenVSP
added to graphics (3D aircraft modeling tool from NASA)

python2-pillow
added to python (needed for gourmet recipe manager)

SimGear
update for version 2020.3.8
remove freealut from REQUIRES

vobsub2srt
minor script cleanup for 15.0

of the things there I pushed the ones in my branch, please have a look at the commits

https://git.slackbuilds.org/slackbuilds/log/?h=ponce

I haven't pushed a few things on that branch that will be merged on SBo's master branch:
- crispy-doom fixes are already there;
- gnucash-docs tarball seems to revert a lot of *correct* stuff;
- google-earth{,-legacy}: I don't have a clear sight of what's happening here (also there's no openssl10, listed in REQUIRES, on SBo) so maybe it's better to re-evaluate this later;
- OpenVSP is a new script that is not a mandatory dependency of anything else so it should go in when submission will reopen;
- python2-pillow has been already added to SBo's master branch.