[wellylug] Google Earth

[Alex Thomson]

Rob Collins wrote:
> Jon / Alex, (and any others that may know about getting dri for savage 
> S3 vt8375 chipset graphics card working)
> 
> Tried all the bits that have gleaned from you guys last couple of days 
> with some success.  DRI is at least partially working and this is the 
> return I get at Konsole:
> 
> admins at Kubuntu:~$ cat /var/log/Xorg.0.log | grep DRI
> (II) Loading extension XFree86-DRI
> (**) SAVAGE(0): DRI is disabled by default on this chipset as it is 
> experimental and unstable.
> (II) SAVAGE(0): [drm] Enabling ShadowStatus for DRI.
> (**) SAVAGE(0): DRI is enabled
> (II) SAVAGE(0): [DRI] installation complete
> (II) SAVAGE(0): [junkers]pSAVAGEDRIServer:
> (II) SAVAGE(0): [junkers]pSAVAGEDRI:
> (II) GLX: Initialized DRI GL provider for screen 0
> admins at Kubuntu:~$ glxgears >> -printfps
> libGL warning: 3D driver claims to not support visual 0x4c
> 
> The gears seem to spin pretty smoothly except occasionally (every 15 
> seconds or so) they stall for a fraction of a second (almost unnoticeable).
> 
> Google Earth works at lightening speed compared to what I was getting 
> under software emulation.  However, when zooming in close enough to the 
> planet to just see sommes island and wellington airport runway, the app 
> crashes spectacularly (the pc freezes) can't even alt-ctrl-bkspace out 
> of KDE or alt-ctrl-del to stop google e.  Is there anything obvious in 
> the returned text above that would indicate what's wrong?  My xorg.conf 
> follows:
> 
> # /etc/X11/xorg.conf (xorg X Window System server configuration file)
> #
> # This file was generated by dexconf, the Debian X Configuration tool, using
> # values from the debconf database.
> #
> # Edit this file with caution, and see the /etc/X11/xorg.conf manual page.
> # (Type "man /etc/X11/xorg.conf" at the shell prompt.)
> #
> # This file is automatically updated on xserver-xorg package upgrades *only*
> # if it has not been modified since the last upgrade of the xserver-xorg
> # package.
> #
> # If you have edited this file but would like it to be automatically updated
> # again, run the following command:
> #   sudo dpkg-reconfigure -phigh xserver-xorg
> 
> Section "Files"
>   FontPath "/usr/share/X11/fonts/misc"
>   FontPath "/usr/share/X11/fonts/cyrillic"
>   FontPath "/usr/share/X11/fonts/100dpi/:unscaled"
>   FontPath "/usr/share/X11/fonts/75dpi/:unscaled"
>   FontPath "/usr/share/X11/fonts/Type1"
>   FontPath "/usr/share/X11/fonts/100dpi"
>   FontPath "/usr/share/X11/fonts/75dpi"
>   FontPath "/usr/share/fonts/X11/misc"
>   # path to defoma fonts
>   FontPath "/var/lib/defoma/x-ttcidfont-conf.d/dirs/TrueType"
> EndSection
> 
> Section "Module"
>   Load "i2c"
>   Load "bitmap"
>   Load "ddc"
>   Load "extmod"
>   Load "freetype"
>   Load "int10"
>   Load "type1"
>   Load "vbe"
>   load "glx"
>   load "GLcore"
>   load "v4l"
>   load "dri"
> EndSection
> 
> Section "InputDevice"
>   Identifier "Generic Keyboard"
>   Driver "kbd"
>   option "CoreKeyboard"
>   option "XkbRules" "xorg"
>   option "XkbModel" "pc105"
>   option "XkbLayout" "us"
>   option "XkbVariant" "intl"
>   option "XkbOptions" "lv3:ralt_switch"
> EndSection
> 
> Section "InputDevice"
>   Identifier "Configured Mouse"
>   Driver "mouse"
>   option "CorePointer"
>   option "Device" "/dev/input/mice"
>   option "Protocol" "ExplorerPS/2"
>   option "ZAxisMapping" "4 5"
>   option "Emulate3Buttons" "true"
> EndSection
> 
> Section "InputDevice"
>   Driver "wacom"
>   Identifier "stylus"
>   option "Device" "/dev/wacom"# Change to
>   option "Type" "stylus"
>   option "ForceDevice" "ISDV4"# Tablet PC ONLY
>   # /dev/input/event
>   # for USB
> EndSection
> 
> Section "InputDevice"
>   Driver "wacom"
>   Identifier "eraser"
>   option "Device" "/dev/wacom"# Change to
>   option "Type" "eraser"
>   option "ForceDevice" "ISDV4"# Tablet PC ONLY
>   # /dev/input/event
>   # for USB
> EndSection
> 
> Section "InputDevice"
>   Driver "wacom"
>   Identifier "cursor"
>   option "Device" "/dev/wacom"# Change to
>   option "Type" "cursor"
>   option "ForceDevice" "ISDV4"# Tablet PC ONLY
>   # /dev/input/event
>   # for USB
> EndSection
> 
> Section "Device"
>   identifier "S3 Inc. VT8375 [ProSavage8 KM266/KL266]"
>   boardname "S3 Savage (generic, sw_cursor)"
>   busid "PCI:1:0:0"
>   driver "savage"
>   screen 0
>   vendorname "S3"
>   videoram 65536
>   option "sw_cursor"
>   option "ForceInit"
>   option "AGPSize"    "16"
>   option "AGPMode"    "4"
>   option "DmaType"    "AGP"
>   option "DmaMode"    "None"
>   option "BusType"    "PCI"
> EndSection
> 
> Section "Monitor"
>   identifier "Monitor Generico"
>   vendorname "Plug 'n' Play"
>   modelname "Plug 'n' Play"
>   modeline  "640x480 at 60" 25.2 640 656 752 800 480 490 492 525 -vsync -hsync
>   modeline  "640x480 at 72" 31.5 640 664 704 832 480 489 491 520 -vsync -hsync
>   modeline  "640x480 at 75" 31.5 640 656 720 840 480 481 484 500 -vsync -hsync
>   modeline  "800x600 at 56" 36.0 800 824 896 1024 600 601 603 625 +hsync +vsync
>   modeline  "800x600 at 72" 50.0 800 856 976 1040 600 637 643 666 +hsync +vsync
>   modeline  "800x600 at 75" 49.5 800 816 896 1056 600 601 604 625 +hsync +vsync
>   modeline  "800x600 at 60" 40.0 800 840 968 1056 600 601 605 628 +hsync +vsync
>   modeline  "832x624 at 75" 57.284 832 864 928 1152 624 625 628 667 -vsync 
> -hsync
>   modeline  "1024x768 at 75" 78.8 1024 1040 1136 1312 768 769 772 800 
> +hsync +vsync
>   modeline  "1024x768 at 70" 75.0 1024 1048 1184 1328 768 771 777 806 
> -vsync -hsync
>   modeline  "1024x768 at 60" 65.0 1024 1048 1184 1344 768 771 777 806 
> -vsync -hsync
>   modeline  "1280x960 at 60" 102.1 1280 1360 1496 1712 960 961 964 994 
> -hsync +vsync
>   gamma 1.0
> EndSection
> 
> Section "Screen"
>   Identifier "Default Screen"
>   Device "S3 Inc. VT8375 [ProSavage8 KM266/KL266]"
>   Monitor "Monitor Generico"
>   DefaultDepth 24
>   SubSection "Display"
>     depth 24
>     virtual 1024 768
>     modes "1024x768 at 60" "1280x960 at 60" "1024x768 at 70" "1024x768 at 75" 
> "832x624 at 75" "800x600 at 60" "800x600 at 75" "800x600 at 72" "800x600 at 56" 
> "640x480 at 75" "640x480 at 72" "640x480 at 60"
>   EndSubSection
> EndSection
> 
> Section "DRI"
>   Mode 0666
> EndSection
> 
> Section "ServerLayout"
>   Identifier "Default Layout"
>   screen 0 "Default Screen" 0 0
>   InputDevice "Generic Keyboard"
>   InputDevice "Configured Mouse"
>   InputDevice "stylus" "SendCoreEvents"
>   InputDevice "cursor" "SendCoreEvents"
>   InputDevice "eraser" "SendCoreEvents"
> EndSection
> 
> Section "DRI"
>   Mode 0666
> EndSection
> Section "ServerFlags"
> EndSection
> 
> 
> jon at jon.geek.nz wrote:
>> Rob Collins wrote:
>>   
>>> Jon,
>>>
>>> Seems you know a lot about specific graphics hardware problems and thank
>>> you for the advice.  Will forcing the card into PCI mode automatically
>>> enable DRI or do I have to do additionally what Alex suggested:
>>>
>>> "(In the "Module" section)
>>>      Load "dri"
>>>
>>> (...and at the end of the file...)
>>> Section "dri"
>>>     Mode 0666
>>> EndSection "
>>>
>>> Also, without using software cursors, my card seems to throw up a square
>>> block of static instead of a mouse pointer to do I need to also add:
>>>
>>> option "HWcursor"   "false"
>>>     
>>
>> You need to tell xorg about DRI, so yes you will need the Load "dri"
>> bit, and the Section "dri" as well (to tell xorg that non-root users can
>> also use DRI)
>>
>> People have varying success with turning hardware tiling on and off.
>> Searching the interwebs for "vt8375 xorg dri" or similar gets the best
>> stuff, mostly forum threads with people saying "how the heck do I get
>> DRI to work?!"  :-)
>>
>> It's all about fiddling with xorg.conf, as most modern distros should
>> have the S3 savage stuff in the kernel. Which distro are you using?
>>
>> Without the hardware to play with myself, I can't really say much beyond
>> what's already out there except try it and see. Make a backup of a
>> working /etc/X11/xorg.conf so that if it all goes horribly wrong you can
>> reboot into a console and copy it back:
>>
>>   cp  /etc/X11/xorg.conf  /home/rob/xorg.conf.backup
>>
>> (or wherever.)
>>
>> J
>>
>>   
> 
> ------------------------------------------------------------------------
> 
> 

Hi,

Hmmm, I am inclined to think that your card is working fine, and this is 
a potential problem with GoogleEarth (from the G.E. faq:)

"Via S3 SuperSavage and ProSavage DDR when used with OpenGL renders 
incorrectly and/or crashes due to driver problems."

However, the site does suggest a few things to try, ie. reducing the 
screen-size, detail area, and maybe dropping the pixel depth to 16.  If 
you run googleearth from a console, does it display any errors or warnings?

It's good you managed to at least get DRI going tho! :)

BTW- I see in your xorg.conf the Section "dri" part was already there, 
so you didn't need to add it again after all, and also, the command for 
glxgears was:
glxgears -printfps
not...
glxgears >> -printfps
Which is why it wasn't displaying the framerate and pausing every 5 seconds.

Cheers,
Alex

Attention:
This email may contain information intended for the sole use of
the original recipient. Please respect this when sharing or
disclosing this email's contents with any third party. If you
believe you have received this email in error, please delete it
and notify the sender or postmaster at solnetsolutions.co.nz as
soon as possible. The content of this email does not necessarily
reflect the views of SolNet Solutions Ltd.