Puppy Linux Discussion Forum Forum Index Puppy Linux Discussion Forum
Puppy HOME page : puppylinux.com
"THE" alternative forum : puppylinux.info
 
 FAQFAQ   SearchSearch   MemberlistMemberlist   UsergroupsUsergroups   RegisterRegister 
 ProfileProfile   Log in to check your private messagesLog in to check your private messages   Log inLog in 

The time now is Sun 24 Mar 2019, 00:57
All times are UTC - 4
 Forum index » Advanced Topics » Additional Software (PETs, n' stuff) » REQUESTS
Request google-earth sfs for Fatdog64-800b (Solved)
Post new topic   Reply to topic View previous topic :: View next topic
Page 1 of 1 [11 Posts]  
Author Message
superchook

Joined: 13 Mar 2006
Posts: 110
Location: Sydney, Australia

PostPosted: Sun 27 Jan 2019, 20:26    Post subject:  Request google-earth sfs for Fatdog64-800b (Solved)  

Either Google Earth Pro 7.3.x or 7.1.8.3036
Google Earth 7.1.8.3036 runs under xenialpup64 but i do not recall where I found it Sad

Hints on how to roll my own would also be welcome.

Last edited by superchook on Fri 22 Feb 2019, 04:39; edited 1 time in total
Back to top
View user's profile Send private message 
Mike Walsh


Joined: 28 Jun 2014
Posts: 4739
Location: King's Lynn, UK.

PostPosted: Sun 27 Jan 2019, 21:05    Post subject:  

@ superchook:-

The G.Earth 7.1.8.3036 package for Xenialpup64 can be found here at Ibiblio:-

http://distro.ibiblio.org/puppylinux/pet_packages-xenial64/google-earth-pro-stable_7.1.8.3036-r0_amd64.pet

I also have a G.Earth Pro 7.3.0.3830 .pet package at my GoogleDrive a/c:-

https://drive.google.com/file/d/1MYuh61c1ocEyucXq4mHG8U8wpHGq6GVk/view?usp=sharing

I don't use FatDog myself, but from what I understand you may need to convert these to the .txz package format that FatDog employs, before installing either of them. Let us know if either of those work for you, please.


Mike. Wink

_________________
My 'Puppy' Packages
--------------------------------------

Back to top
View user's profile Send private message Visit poster's website 
superchook

Joined: 13 Mar 2006
Posts: 110
Location: Sydney, Australia

PostPosted: Mon 28 Jan 2019, 05:29    Post subject: Request google-earth sfs for Fatdog64-800b  

Many thanks for your quick response Mike.
I already had google-earth 7.1.8.3036 working in my "every day" puppy i.e. xenialpup647.5frugal so now I have to remove traces of my bungled attempts to install it in Fatdog64-800b then make a working sfs package from one of your pets.
I will make a post in a new thread after (or if?) I succeed.

Ken
Back to top
View user's profile Send private message 
Mike Walsh


Joined: 28 Jun 2014
Posts: 4739
Location: King's Lynn, UK.

PostPosted: Mon 28 Jan 2019, 14:23    Post subject:  

@ Ken:-

I used to think converting .pets to SFSs, and vice versa, was really complicated.....but once you understand the basic principles, it is so simple you'll feel like kicking yourself..!

Now; you want to convert those .pets into SFS packages, yes? Right. First step; extract the .pet package. There is one, and only one tool for this job.

SFR's UExtract.

http://www.murga-linux.com/puppy/viewtopic.php?t=87864

Doesn't matter what archive format you throw at it, it'll unpack it (assuming the archive has been formed correctly. I've had it refuse to unpack .debs before, but it's always turned out to be a boo-boo on the part of the original packager; you'll get the term 'malformed package' somewhere in the error read-out. I've usually ended up using the .rpm format version of the same package; I've never had any trouble with those! Rolling Eyes)

Anyway; download that, and use it to unpack either of the .pet packages. UExtract will ask where you want the unpacked archive to be; you'll need to specify a location. Once you've unpacked it, look in the extracted directory (unless you specify a location, it will unpack in the same directory.) I usually do this in /root, but then I use pretty big save-files; typically 10-12 GB in size. I may be using a 14-yr old box, but I am not short on room to maneuver..!

I use two directories for this stuff. One called 'make-pet' (this works with Trio's 'PetMaker'), and the other is labelled 'MAKE-SFS'.

Look inside the extracted directory until you come to the file-system stuff (usr, root, etc, bin.....all that stuff.) This is the 'top-level' of the package contents.

If you don't have plenty of 'Puppy-space' to play with, I suggest moving this to somewhere you do have plenty of space. And it's always an idea to contain all this within a 'working' directory; saves it getting spread out all over the place. Which can easily happen.....

-----------------------------------------------------

Using my own set-up as an example, I extract/create .pets within the 'make-pet' directory, and like wise for SFSs within the 'MAKE-SFS' one. Having extracted the .pet, leave that ROX-window open.

Opening the 'MAKE-SFS' directory, I now create a new directory; in this case, we'll give it the same name as the .pet you've just extracted. (Whichever one that is.) Say

Code:
Google_Earth_Pro-7.3.0.3830-amd64


We now open this one you've just created. (At this point, you've got 2 ROX windows open. One on the extracted contents of the .pet (A), and one on the empty SFS directory (B)). Highlight the contents of (A), then drag & drop into (B). Click 'Copy'. Then, delete the pet.specs file you've copied along with it. SFS packages don't use this.

You should now have the named SFS directory, with the contents of the .pet copied into it. With me so far?

Good! That's the easy bit.... Now then:-

--------------------------------------------------

Using my own example, of a directory called 'MAKE-SFS' within /root, you now open a terminal, and issue the following command. Watch the syntax carefully. (If you get it wrong, it won't run, and usually tells you what you've done wrong anyway):-

Code:
mksquashfs /root/MAKE-SFS/Google_Earth_Pro-7.3.0.3830-amd64 /root/MAKE-SFS/Google_Earth_Pro-7.3.0-3830-amd64.sfs


The first 'stanza' tells it where to find the data. The second 'stanza' (remember to leave a space between them) tells it where to create the package. (I do all this in the same directory for tidiness). Remember to add the .sfs extension at the end of the second stanza. If you don't, it'll create a binary package.....and that is not what you want.

Assuming all goes well, you'll end up with an SFS package with the name you've given it......


Mike. Wink

_________________
My 'Puppy' Packages
--------------------------------------

Back to top
View user's profile Send private message Visit poster's website 
step

Joined: 04 May 2012
Posts: 1168

PostPosted: Mon 28 Jan 2019, 17:21    Post subject:  

I like uextract too, I always add it to my Fatdog.
Some Fatdog specific tips:

- if you're converting a large package stay out of /tmp to maximize the memory made available for the conversion process (best is to mount a hard disk and work in there)

- once you've got your constituent files inside a directory as Mike explained, you can compress the directory into an sfs by running the following command in a terminal:
dir2sfs name_of_the_directory

_________________
Fatdog64-800|+Packages|Kodi|Findnrun|+forum|gtkmenuplus
Back to top
View user's profile Send private message 
step

Joined: 04 May 2012
Posts: 1168

PostPosted: Mon 28 Jan 2019, 17:21    Post subject:  

double post deleted
_________________
Fatdog64-800|+Packages|Kodi|Findnrun|+forum|gtkmenuplus
Back to top
View user's profile Send private message 
jamesbond

Joined: 26 Feb 2007
Posts: 3284
Location: The Blue Marble

PostPosted: Thu 07 Feb 2019, 12:12    Post subject:  

I'm uploading it here: http://distro.ibiblio.org/fatdog/sfs/800/google-earth-2019.02.sfs
I haven't finished uploading it yet. Wait until you can see the md5sum file: http://distro.ibiblio.org/fatdog/sfs/800/google-earth-2019.02.sfs.md5sum.txt or wait until you can see it in SFS Manager.

This is a straight convert from G's rpm package, no icons, etc - you need to open terminal and type "google-earth-pro" to run it.

In order to run it, you need to install libproxy from the repo (using the package manager).

Notes: Many G's products don't like nouveau. If you're on nouveau and you see corrupted screen, type this on terminal before starting google-earth-pro: "export LIBGL_ALWAYS_SOFTWARE=yes"

It means what it says, and software rendering will be slower than hardware-assisted rendering, but at least it will work.

_________________
Fatdog64, Slacko and Puppeee user. Puppy user since 2.13.
Contributed Fatdog64 packages thread.
Back to top
View user's profile Send private message 
superchook

Joined: 13 Mar 2006
Posts: 110
Location: Sydney, Australia

PostPosted: Fri 08 Feb 2019, 09:13    Post subject:  

Hi James,
I have returned home after a few days away. While away I experimented with a laptop and succeeded,with help, in getting google-earth 7.1.8.3036 running on that machine.(see: Forum index » Advanced Topics » Puppy Projects
How to make Google-Earth SFS for Fatdog64-800b? _SOLVED_ )
This evening I tried your new google-earth-2019.02.sfs on my main computer but without much luck.
This computer has:
Summary
-------

-Computer-
Processor : 2x AMD Athlon(tm) 64 X2 Dual Core Processor 6000+
Memory : 8176MB (1004MB used)
Machine Type : Physical machine
Operating System : Puppy Linux
User Name : root (root)
Date/Time : Fri Feb 8 23:13:49 2019
-Display-
Resolution : 1920x1080 pixels
OpenGL Renderer : Gallium 0.4 on NV96
X11 Vendor : The X.Org Foundation
-Audio Devices-
Audio Adapter : HDA-Intel - HDA NVidia
Audio Adapter : PC-Speaker - pcsp
-Input Devices-
Power Button
Power Button
AT Translated Set 2 keyboard
Microsoft Microsoft 3-Button Mouse with IntelliEye(TM)
PC Speaker
HDA NVidia Rear Mic
HDA NVidia Front Mic
HDA NVidia Line
HDA NVidia Line Out Front
HDA NVidia Line Out Surround
HDA NVidia Line Out CLFE
HDA NVidia Line Out Side
HDA NVidia Front Headphone
-Printers (CUPS)-
CUPS-PDF : <i>Default</i>
HP_LaserJet_P3010_Series
-SCSI Disks-
ATA WDC WD10EZEX-00B
ATAPI iHAS324 E

Operating System
----------------

-Version-
Kernel : Linux 4.9.58 (x86_64)
Version : #1 SMP PREEMPT Mon Nov 13 15:54:01 GMT 2017
C Library : GNU C Library version 2.23 (stable)
Distribution : Puppy Linux
-Current Session-
Computer Name : Deep_Thought
User Name : root (root)
Home Directory : /root
Desktop Environment : Unknown (Window Manager: JWM)
-Misc-
Uptime : 1 hour, 13 minutes
Load Average : 0.51, 0.57, 0.49

Kernel Modules
--------------

-Loaded Modules-
xt_pkttype : Xtables: link layer packet type match
xt_conntrack : Xtables: connection tracking state match
iptable_mangle : iptables mangle table
iptable_nat
nf_nat_ipv4
iptable_filter : iptables filter table
nf_conntrack_irc : IRC (DCC) connection tracking helper
nf_nat_ftp : ftp NAT helper
nf_conntrack_ftp : ftp connection tracking helper
nf_nat
nf_conntrack_ipv4
nf_defrag_ipv4
nf_conntrack
ip_tables : IPv4 packet filter
cfg80211 : wireless configuration support
rfkill : RF switch support
nouveau : nVidia Riva/TNT/GeForce/Quadro/Tesla
mxm_wmi : MXM WMI Driver
input_leds : Input -&gt; LEDs Bridge
ttm : TTM memory manager subsystem (for DRM device)
drm_kms_helper : DRM KMS helper
drm : DRM shared core routines
snd_pcsp : PC-Speaker driver
i2c_algo_bit : I2C-Bus bit-banging algorithm
k8temp : AMD K8 core temperature monitor
snd_hda_codec_via : VIA HD-audio codec
snd_hda_codec_generic : Generic HD-audio codec parser
shpchp : Standard Hot Plug PCI Controller Driver
snd_hda_intel : Intel HDA driver
snd_hda_codec : HDA codec core
snd_hda_core : HD-audio bus
snd_hwdep : Hardware dependent layer
snd_pcm_oss : PCM OSS emulation for ALSA.
snd_mixer_oss : Mixer OSS emulation for ALSA.
forcedeth : Reverse Engineered nForce ethernet driver
snd_pcm : Midlevel PCM code for ALSA.
snd_seq_dummy : ALSA sequencer MIDI-through client
snd_seq_oss : OSS-compatible sequencer module
snd_seq_midi : Advanced Linux Sound Architecture sequencer MIDI synth.
snd_seq_midi_event : MIDI byte &lt;-&gt; sequencer event coder
snd_rawmidi : Midlevel RawMidi code for ALSA.
snd_seq : Advanced Linux Sound Architecture sequencer.
snd_seq_device : ALSA sequencer device management
snd_timer : ALSA timer interface
snd : Advanced Linux Sound Architecture driver for soundcards.
soundcore : Core sound module
i2c_nforce2 : nForce2/3/4/5xx SMBus driver
wmi : ACPI-WMI Mapping Driver
fjes : FUJITSU Extended Socket Network Device Driver
floppy
parport_pc : PC-style parallel port driver
parport
asus_atk0110
hwmon : hardware monitoring sysfs/class support
tpm_tis : TPM Driver
tpm_tis_core : TPM Driver
tpm : TPM Driver

Boots
-----

-Boots-

Languages
---------

-Available Languages-
en_AU.utf8 : English locale for Australia
en_US : English locale for the USA
en_US.utf8 : English locale for the USA

Filesystems
-----------

-Mounted File Systems-
/dev/sda2 /initrd/mnt/dev_save 71.22 % (204.4 GiB of 710.1 GiB)
tmpfs /initrd/mnt/tmpfs 15.99 % (3.5 GiB of 4.2 GiB)
unionfs / 71.22 % (204.4 GiB of 710.1 GiB)
/dev/loop0 /initrd/pup_ro2 100.00 % (0.0 B of 240.0 MiB)
/dev/loop1 /initrd/pup_z 100.00 % (0.0 B of 78.0 MiB)
devtmpfs /dev 0.00 % (3.9 GiB of 3.9 GiB)
shmfs /dev/shm 1.49 % (1.8 GiB of 1.8 GiB)
/dev/loop2 /initrd/pup_ro3 100.00 % (0.0 B of 189.8 MiB)
/dev/loop3 /initrd/pup_ro4 100.00 % (0.0 B of 70.6 MiB)
/dev/loop4 /initrd/pup_ro5 100.00 % (0.0 B of 51.6 MiB)

Display
-------

-Display-
Resolution : 1920x1080 pixels
Vendor : The X.Org Foundation
Version : 1.18.4
-Monitors-
Monitor 0 : 1920x1080 pixels
-Extensions-
BIG-REQUESTS
Composite
DAMAGE
DOUBLE-BUFFER
DPMS
DRI2
GLX
Generic Event Extension
MIT-SCREEN-SAVER
MIT-SHM
Present
RANDR
RECORD
RENDER
SECURITY
SGI-GLX
SHAPE
SYNC
X-Resource
XC-MISC
XFIXES
XFree86-DGA
XFree86-VidModeExtension
XINERAMA
XInputExtension
XKEYBOARD
XTEST
XVideo
XVideo-MotionCompensation
-OpenGL-
Vendor : nouveau
Renderer : Gallium 0.4 on NV96
Version : 3.0 Mesa 17.0.7
Direct Rendering : Y_es

Environment Variables
---------------------

-Environment Variables-
HOSTNAME : Deep_Thought
XDG_DATA_HOME : /root/.local/share
SHELL : /bin/bash
TERM : xterm
HISTSIZE : 1000
GTK2_RC_FILES : /root/.gtkrc-2.0
QT_XFT : true
DEFAULTDRAW : libreoffice6.1
XLIB_SKIP_ARGB_VISUALS : 1
HISTFILESIZE : 2000
USER : root
LS_COLORS : bd=33:cd=33
LD_LIBRARY_PATH : /lib64:/usr/lib64:/usr/X11R7/lib:/root/my-applications/lib:/usr/local/lib
GDK_USE_XFT : 1
RGBDEF : /usr/share/X11/rgb.txt
DEFAULTIMAGEVIEWER : viewnior
OOO_FORCE_DESKTOP : gnome
DEFAULTPAINT : mtpaint
MOZ_DISABLE_PANGO : 1
MOZ_PLUGIN_PATH : /usr/lib64/mozilla/plugins
XDG_CONFIG_DIRS : /etc/xdg
DEFAULTBROWSER : /home/spot/chrome.sh
PATH : /bin:/usr/bin:/sbin:/usr/sbin:/usr/local/bin:/usr/X11R7/bin:/root/my-applications/bin:/usr/games
DEFAULTMEDIAPLAYER : /usr/bin/mpv
DEFAULTIMAGEEDITOR : mtpaint
INPUTRC : /etc/inputrc
PWD : /root
EDITOR : mp
LANG : en_AU.UTF-8
XFINANSDIR : /root/.xfinans
HISTCONTROL : ignoredups
DEFAULTSPREADSHEET : libreoffice6.1
DEFAULTHTMLEDITOR : mozedit
SHLVL : 3
HOME : /root
XDG_CONFIG_HOME : /root/.config
TERMINFO : /usr/share/terminfo
KODI_HOME : /usr/share/kodi/
XDG_CACHE_HOME : /root/.cache
G_FILENAME_ENCODING : @locale
LOGNAME : root
PREFIX : /usr
XDG_DATA_DIRS : /usr/share:/usr/local/share
TEXTDOMAIN : xwin
WINDOWPATH : 4
DISPLAY : :0
MM_RUNASROOT : 1
NO_AT_BRIDGE : 1
DEFAULTWORDPROCESSOR : libreoffice6.1
DEFAULTTEXTEDITOR : geany
OUTPUT_CHARSET : UTF-8
_ : /usr/bin/hardinfo

Development
-----------

-Scripting Languages-
CPython : 2.7.12
Perl : 5.22.1
PHP : Not found
Ruby : Not found
Bash : 4.3.42(1)-release
-Compilers-
C (GCC) : Not found
C (Clang) : Not found
D (dmd) : Not found
Java : Not found
CSharp (Mono, old) : Not found
CSharp (Mono) : Not found
Vala : Not found
Haskell (GHC) : Not found
FreePascal : Not found
-Tools-
make : Not found
GDB : Not found
strace : Not found
valgrind : Not found
QMake : Not found

Users
-----

-Users-
root : root
daemon
nobody
spot : Linux User
bin : bin
messagebus : Linux User
ftp : Linux User
haldaemon : Hardware abstraction layer
uucp : uucp
sshd : sshd
webuser : Linux User
fido : Linux User
man

Groups
------

-Groups-
root : 0
daemon : 1
tty : 109
ppp : 200
users : 500
nobody : 65534
guest : 501
spot : 502
bin : 2
503 : 503
ftp : 1000
dip : 30
uucp : 10
lpadmin : 112
netdev : 113
haldaemon : 119
sshd : 33
webgroup : 504
disk : 100
audio : 101
lp : 102
dialout : 103
kmem : 104
video : 105
floppy : 106
cdrom : 107
tape : 108
tty : 109
plugdev : 110

Devices
*******


Processor
---------

-Processors-
AMD Athlon(tm) 64 X2 Dual Core Processor 6000+ : 2400.00MHz
AMD Athlon(tm) 64 X2 Dual Core Processor 6000+ : 2400.00MHz

Memory
------

-Memory-
Total Memory : 8176044 kB
Free Memory : 5352840 kB
MemAvailable : 6268328 kB
Buffers : 196852 kB
Cached : 1819616 kB
Cached Swap : 0 kB
Active : 1518584 kB
Inactive : 1085468 kB
Active(anon) : 1021156 kB
Inactive(anon) : 317352 kB
Active(file) : 497428 kB
Inactive(file) : 768116 kB
Unevictable : 0 kB
Mlocked : 0 kB
Virtual Memory : 8188 kB
Free Virtual Memory : 8188 kB
Dirty : 256 kB
Writeback : 0 kB
AnonPages : 587608 kB
Mapped : 256888 kB
Shmem : 750932 kB
Slab : 149188 kB
SReclaimable : 114208 kB
SUnreclaim : 34980 kB
KernelStack : 5024 kB
PageTables : 18416 kB
NFS_Unstable : 0 kB
Bounce : 0 kB
WritebackTmp : 0 kB
CommitLimit : 4096208 kB
Committed_AS : 2994732 kB
VmallocTotal : 34359738367 kB
VmallocUsed : 0 kB
VmallocChunk : 0 kB
AnonHugePages : 0 kB
ShmemHugePages : 0 kB
ShmemPmdMapped : 0 kB
DirectMap4k : 16000 kB
DirectMap2M : 8372224 kB

PCI Devices
-----------

-PCI Devices-
RAM memory : NVIDIA Corporation MCP67 Memory Controller (rev a2)
ISA bridge : NVIDIA Corporation MCP67 ISA Bridge (rev a2)
SMBus : NVIDIA Corporation MCP67 SMBus (rev a2)
USB controller : NVIDIA Corporation MCP67 OHCI USB 1.1 Controller (rev a2) (prog-if 10 [OHCI])
USB controller : NVIDIA Corporation MCP67 EHCI USB 2.0 Controller (rev a2) (prog-if 20 [EHCI])
USB controller : NVIDIA Corporation MCP67 OHCI USB 1.1 Controller (rev a2) (prog-if 10 [OHCI])
USB controller : NVIDIA Corporation MCP67 EHCI USB 2.0 Controller (rev a2) (prog-if 20 [EHCI])
IDE interface : NVIDIA Corporation MCP67 IDE Controller (rev a1) (prog-if 8a [Master SecP PriP])
Audio device : NVIDIA Corporation MCP67 High Definition Audio (rev a1)
PCI bridge : NVIDIA Corporation MCP67 PCI Bridge (rev a2) (prog-if 01 [Subtractive decode])
IDE interface : NVIDIA Corporation MCP67 AHCI Controller (rev a2) (prog-if 85 [Master SecO PriO])
Ethernet controller : NVIDIA Corporation MCP67 Ethernet (rev a2)
PCI bridge : NVIDIA Corporation MCP67 PCI Express Bridge (rev a2) (prog-if 00 [Normal decode])
PCI bridge : NVIDIA Corporation MCP67 PCI Express Bridge (rev a2) (prog-if 00 [Normal decode])
PCI bridge : NVIDIA Corporation MCP67 PCI Express Bridge (rev a2) (prog-if 00 [Normal decode])
PCI bridge : NVIDIA Corporation MCP67 PCI Express Bridge (rev a2) (prog-if 00 [Normal decode])
PCI bridge : NVIDIA Corporation MCP67 PCI Express Bridge (rev a2) (prog-if 00 [Normal decode])
PCI bridge : NVIDIA Corporation MCP67 PCI Express Bridge (rev a2) (prog-if 00 [Normal decode])
PCI bridge : NVIDIA Corporation MCP67 PCI Express Bridge (rev a2) (prog-if 00 [Normal decode])
Host bridge : Advanced Micro Devices, Inc. [AMD] K8 [Athlon64/Opteron] HyperTransport Technology Configuration
Host bridge : Advanced Micro Devices, Inc. [AMD] K8 [Athlon64/Opteron] Address Map
Host bridge : Advanced Micro Devices, Inc. [AMD] K8 [Athlon64/Opteron] DRAM Controller
Host bridge : Advanced Micro Devices, Inc. [AMD] K8 [Athlon64/Opteron] Miscellaneous Control
VGA compatible controller : NVIDIA Corporation G96 [GeForce 9500 GT] (rev a1) (prog-if 00 [VGA controller])

Sensors
-------

-Temperature-
temp1 (k8temp) : 34.00°C
temp2 (k8temp) : 37.00°C
temp3 (k8temp) : 37.00°C
temp4 (k8temp) : 38.00°C
temp1 (ATK0110) : 45.00°C
temp2 (ATK0110) : 41.00°C
temp1 (nouveau) : 50.00°C
-Cooling Fans-
fan1 (ATK0110) : 2800RPM
fan2 (ATK0110) : 0RPM
fan3 (ATK0110) : 0RPM
fan1 (nouveau) : 0RPM
-Voltage Values-
in0 (ATK0110) : 1.136V
in1 (ATK0110) : 3.328V
in2 (ATK0110) : 5.017V
in3 (ATK0110) : 11.734V

Input Devices
-------------

-Input Devices-
Power Button
Power Button
AT Translated Set 2 keyboard
Microsoft Microsoft 3-Button Mouse with IntelliEye(TM)
PC Speaker
HDA NVidia Rear Mic
HDA NVidia Front Mic
HDA NVidia Line
HDA NVidia Line Out Front
HDA NVidia Line Out Surround
HDA NVidia Line Out CLFE
HDA NVidia Line Out Side
HDA NVidia Front Headphone

Storage
-------

-SCSI Disks-
ATA WDC WD10EZEX-00B
ATAPI iHAS324 E

DMI
---

-BIOS-
Date : 08/27/2008
Vendor : American Megatrends Inc. (www.ami.com)
Version : 0317
-Board-
Name : M2N68-CM
Vendor : ASUSTeK Computer INC. (SEAGATE, www.seagate.com)

The computer is set up to multi boot several Puppies but for these experiments I tried only xenialpup647.5frugal and fatdog64_800bfrugal

Running under xenialpup64 I get satisfactory performance using my
google-earth-pro-stable_7.1.8.3036-r0_amd64.sfs
but
google-earth-2019.02.sfs will only display the opening screen showing half of the globe if you disable hardware acceleration as you describe. the rendering is very slow as you try to zoom in and the application crashes before you can display an area of, say, 4 km East-West x 2.25 km North-South.
When running under fatdog64_800b it is necessary to disable hardware acceleration on both versions of google-earth to even display the opening screen but the rendering is so slow as to be useless. Both packages crash when you attempt to zoom in.

The puzzling thing is why is the rendering so much slower under fatdog on the same hardware? Is it just a function of the different nouveau drivers or does the kernel play a role?

As it stands I can run google-earth under fatdog on a rather anaemic laptop with radeon graphics but not if I have something with Nvidia. (unless perhaps Nvidia have drivers for the kernel in question.
Back to top
View user's profile Send private message 
jamesbond

Joined: 26 Feb 2007
Posts: 3284
Location: The Blue Marble

PostPosted: Fri 08 Feb 2019, 11:20    Post subject:  

TL;DR:

If you want acceleration on your desktop you need to install proprietary NVIDIA driver. Or use older copy of G earth.

__________________________________________

Longer story:

I'm not sure how "new" is the xenialpup version of google earth.
Mine, I just fished it yesterday from G website.

G has always had problems with nouveau driver. See for example: https://www.phoronix.com/scan.php?page=news_item&px=Chrome-Blacklisting-Nouveau. This is new, Jan 2019's decision for Chrome 71 onwards, but let me say that Chrome has always had partial blacklisting for nouveau (as in, it blacklist nouveau based on certain nvidia cards, or based on certain version of the drivers, etc) - the post linked above just said that G has decided to make the blacklist complete - everything nouveau will now be ignored and no acceleration used, which, as we know it, slow.

While the decision sounds harsh, the reality is nouveau driver does have a long outstanding problem that has plagued it for years that the nouveau drivers can't (or won't fix - I don't know which one, although I'd go with "can't"). Reason? Nouveau driver is based on reverse-engineering. NVIDIA doesn't help at all with nouveau, it doesn't provide any documetation, support, manpower, or anything at all. The devs spent countless hours just to figure out a certain feature, and then more hours to figure out how it works. And they have to figure out and test how and whether this particular feature works with other features (e.g. antialiasing combined with filtering - how does it work? Or if it works at all?). Then once they think they've figured it out, they spend more countless hours to really combine the new feature into a working nouveau feature. And they have to do this for every card out there. With so many possible card combinations and feature combinations you can expect lots of bugs. To minimise the bugs the devs stick to features or methods that they know to work; dropping less-often-bur-arcane features. The final result: as a display driver, nouveau is not too bad, but when it comes to the 3D acceleration features ... you know what I mean.

So that's why G decided to disable acceleration; they think it is better to be slow but at least showing it properly, rather than fast but showing garbage (black rectangles, wrong images at wrong location, wrong sizes, etc).

That being said G is not exactly innocent either. With every new iteration of their software, aligned with their ambition to stay no #1, they tend to use the latest and greatest feature offered by the graphics card. This means it often pushes the card (and its driver) to the limit, exposing bugs that otherwise are rarely encountered. And with nouveau they have encountered many issues over and over again - hence the decision. This decision isn't new, they have been blacklisting and de-blacklisting nouveau many times in the past (I can't find the link right now).

Well that's about Chrome, but I'm quite sure the same problem plagues G earth too because they exploit the GPU in a similar way. Perhaps, only that G earth doesn't blacklist nouveau (yet).
My own desktop, for example, that has nouveau, will not display G earth properly either, unless I disable acceleration (hence my initial note - it came from first hand experience).

But all is not lost. If you really can't live without acceleration, then your way out is to install proprietary NVIDIA driver. Or else, use an older version of G earth, where it is not as taxing as the newer ones (and probably the bugs exposed by the older G earth have already been fixed by the newer nouveau driver).

EDIT: I see that you said that even with xenialpup's version of G earth, it doesn't work well with Fatdog. Then my only explanation is this: the quality of the nouveau driver varies from release to release (we're talking about kernel version + Xorg version). Back in the day, I had a desktop (also with nvidia) who had problems from release to release; sometimes it worked well and sometimes it didn't. Perhaps the particular combination of kernel version + Xorg version + your card model results in a bad nouveau.

In this case the only thing to do is to install NVIDIA driver. We won't be releasing nvidia driver for 800beta because we're close to making 800 final; we might release nvidia driver not too long after that.

_________________
Fatdog64, Slacko and Puppeee user. Puppy user since 2.13.
Contributed Fatdog64 packages thread.
Back to top
View user's profile Send private message 
Mike Walsh


Joined: 28 Jun 2014
Posts: 4739
Location: King's Lynn, UK.

PostPosted: Fri 08 Feb 2019, 12:26    Post subject:  

@ jamesbond:-

James:-

I'll just add my two-penn'orth here. While I concur that using an older version of G.Earth will work for a while, always remember that G.Earth is a double-ended process; client & server software have to work together. And periodically, Google decide to switch the servers off for older versions - they've done this just recently for the older 6-series. I've had to 'upgrade' all my Pups to 7-series versions to keep 'em working.

I'm just waiting for the day when they decide to drop the desktop client altogether in favour of the new web-based one. That'll be a sad day for us, because Google are well-known for refusing to implement hardware-based acceleration in the Linux iteration of the Chrome/Chromium code (here, citing the huge number of different distros they would have to support).....so even installing proprietary drivers will no longer do the trick.

They like Windows, of course; very few versions to keep code updated for. Pretty much everybody running Windows is now singing from the exact same hymn-sheet.


Mike. Wink

_________________
My 'Puppy' Packages
--------------------------------------

Back to top
View user's profile Send private message Visit poster's website 
superchook

Joined: 13 Mar 2006
Posts: 110
Location: Sydney, Australia

PostPosted: Fri 22 Feb 2019, 04:51    Post subject: Request google-earth sfs for Fatdog64-800b (Solved)  

On the box with built in NVIDIA graphics I had to compile an NVIDIA driver and add a symbolic link /lib64/ld-lsb-x86-64.so.3 -> ld-2.27.so
I used the google earth 7.1.8 SFS that I made for my laptop.
James' google-earth2019.02.sfs crashed on this computer but that may reflect on the capabilities of this box rather than on the package.
Back to top
View user's profile Send private message 
Display posts from previous:   Sort by:   
Page 1 of 1 [11 Posts]  
Post new topic   Reply to topic View previous topic :: View next topic
 Forum index » Advanced Topics » Additional Software (PETs, n' stuff) » REQUESTS
Jump to:  

You cannot post new topics in this forum
You cannot reply to topics in this forum
You cannot edit your posts in this forum
You cannot delete your posts in this forum
You cannot vote in polls in this forum
You cannot attach files in this forum
You can download files in this forum


Powered by phpBB © 2001, 2005 phpBB Group
[ Time: 0.0580s ][ Queries: 12 (0.0041s) ][ GZIP on ]