<br><br><div class="gmail_quote">On Mon, Nov 22, 2010 at 10:54 AM, <span dir="ltr"><<a href="mailto:chris.abela@maltats.com">chris.abela@maltats.com</a>></span> wrote:<br><blockquote class="gmail_quote" style="margin: 0pt 0pt 0pt 0.8ex; border-left: 1px solid rgb(204, 204, 204); padding-left: 1ex;">
Hi,<br>
<br>
My reply was based on my experience of the googleearth and nvidia Slackbuilds. I did not try the Amaya application and I never installed the nvidia from the source script so I cannot reply.<br>
<br>
Chris<br>
<br>
Powered by BlackBerry® from Vodafone<br>
<div><div></div><div class="h5"><br>
-----Original Message-----<br>
From: Martin Pagnan <<a href="mailto:mpagnan@acanac.net">mpagnan@acanac.net</a>><br>
Sender: <a href="mailto:slackbuilds-users-bounces@slackbuilds.org">slackbuilds-users-bounces@slackbuilds.org</a><br>
Date: Mon, 22 Nov 2010 11:24:57<br>
To: SlackBuilds.org Users List<<a href="mailto:slackbuilds-users@slackbuilds.org">slackbuilds-users@slackbuilds.org</a>><br>
Reply-To: "SlackBuilds.org Users List" <<a href="mailto:slackbuilds-users@slackbuilds.org">slackbuilds-users@slackbuilds.org</a>><br>
Subject: Re: [Slackbuilds-users] Nvidia driver update - for GoogleEarth and<br>
Amaya Builds, perhaps others<br>
<br>
Chris,<br>
This is interesting. The GoogleEarth.SlackBuild that I used has the arch<br>
set as 486 and does a binary install. The Amaya.Slackbuild tests the<br>
architecture (and in my case chose 64bit) and compiles from source. The<br>
new Nvidia driver that I installed is apparently, from its name, for<br>
64bit (like my old one). But now both Amaya and GoogleEarth work great<br>
and I did not install the 32bit Nvidia driver.<br>
<br>
I have installed multilib and read the recommendations. Could it be that<br>
Nvidia's new 64bit driver has a 32bit thunk built in?<br>
<br>
On 11/22/2010 05:14 AM, Chris Abela wrote:<br>
> On the other hand, if you originally only installed the 64bit driver<br>
> libraries for your Nvidia/Ati card, it is recommended after installation of<br>
> the multilib packages, to re-install the binary driver package. This time,<br>
> choose to install the 32bit driver files as well.<br>
><br>
> The graphical 32bit applications that you are going to run on your multilib<br>
> installation will require these 32bit driver libraries. Crashes are likely<br>
> to occur if you fail to install the correct files."<br>
><br>
><br>
><br>
> -----Original Message-----<br>
> From: <a href="mailto:slackbuilds-users-bounces@slackbuilds.org">slackbuilds-users-bounces@slackbuilds.org</a><br>
> [mailto:<a href="mailto:slackbuilds-users-bounces@slackbuilds.org">slackbuilds-users-bounces@slackbuilds.org</a>] On Behalf Of Martin<br>
> Pagnan<br>
> Sent: 22 November 2010 04:35<br>
> To: <a href="mailto:SlackBuilds-users@slackbuilds.org">SlackBuilds-users@slackbuilds.org</a><br>
> Subject: [Slackbuilds-users] Nvidia driver update - for GoogleEarth and<br>
> Amaya Builds, perhaps others<br>
><br>
> Both GoogleEarth.Slackbuild and Amaya.Slackbuild failed for me in that<br>
> they both crashed KDE. After a long painstaking search I found a<br>
> recommendation to reinstall the Nvidia driver. Reinstalling my old<br>
> driver (version x86_64-256) did not fix the problem. The error log<br>
> indicated that the GLX module was not loaded - even though it was<br>
> specified in the xorg.conf file and the GLXmodules were installed. Then<br>
> I looked to the Nvidia site for a new driver and downloaded and<br>
> installed the latest version - NVIDIA-Linux-x86_64-260.19.21.run. This<br>
> fixed both problems. KDE no longer crashes. The GLX module now loads.<br>
> The release notes for this new version state that it fixes a problem<br>
> where "multi-threaded applications" would sometimes crash. I have<br>
> notified the maintainers of the GoogleEarth and Amaya Slackbuilds on<br>
> this, but I thought that others may be experiencing similar problems<br>
> with other builds so I am posting this here.<br>
> _______________________________________________<br>
> SlackBuilds-users mailing list<br>
> <a href="mailto:SlackBuilds-users@slackbuilds.org">SlackBuilds-users@slackbuilds.org</a><br>
> <a href="http://lists.slackbuilds.org/mailman/listinfo/slackbuilds-users" target="_blank">http://lists.slackbuilds.org/mailman/listinfo/slackbuilds-users</a><br>
> Archives - <a href="http://lists.slackbuilds.org/pipermail/slackbuilds-users/" target="_blank">http://lists.slackbuilds.org/pipermail/slackbuilds-users/</a><br>
> FAQ - <a href="http://slackbuilds.org/faq/" target="_blank">http://slackbuilds.org/faq/</a><br>
><br>
><br>
> _______________________________________________<br>
> SlackBuilds-users mailing list<br>
> <a href="mailto:SlackBuilds-users@slackbuilds.org">SlackBuilds-users@slackbuilds.org</a><br>
> <a href="http://lists.slackbuilds.org/mailman/listinfo/slackbuilds-users" target="_blank">http://lists.slackbuilds.org/mailman/listinfo/slackbuilds-users</a><br>
> Archives - <a href="http://lists.slackbuilds.org/pipermail/slackbuilds-users/" target="_blank">http://lists.slackbuilds.org/pipermail/slackbuilds-users/</a><br>
> FAQ - <a href="http://slackbuilds.org/faq/" target="_blank">http://slackbuilds.org/faq/</a><br>
><br>
><br>
><br>
_______________________________________________<br>
SlackBuilds-users mailing list<br>
<a href="mailto:SlackBuilds-users@slackbuilds.org">SlackBuilds-users@slackbuilds.org</a><br>
<a href="http://lists.slackbuilds.org/mailman/listinfo/slackbuilds-users" target="_blank">http://lists.slackbuilds.org/mailman/listinfo/slackbuilds-users</a><br>
Archives - <a href="http://lists.slackbuilds.org/pipermail/slackbuilds-users/" target="_blank">http://lists.slackbuilds.org/pipermail/slackbuilds-users/</a><br>
FAQ - <a href="http://slackbuilds.org/faq/" target="_blank">http://slackbuilds.org/faq/</a><br>
<br>
_______________________________________________<br>
SlackBuilds-users mailing list<br>
<a href="mailto:SlackBuilds-users@slackbuilds.org">SlackBuilds-users@slackbuilds.org</a><br>
<a href="http://lists.slackbuilds.org/mailman/listinfo/slackbuilds-users" target="_blank">http://lists.slackbuilds.org/mailman/listinfo/slackbuilds-users</a><br>
Archives - <a href="http://lists.slackbuilds.org/pipermail/slackbuilds-users/" target="_blank">http://lists.slackbuilds.org/pipermail/slackbuilds-users/</a><br>
FAQ - <a href="http://slackbuilds.org/faq/" target="_blank">http://slackbuilds.org/faq/</a><br>
<br>
</div></div></blockquote></div><br><br>The 64-bit Nvidia driver comes with the option to install 32-bit compatibility libraries. There are actually two different packages available, one with and one without the compatibility libs.<br>
<a href="ftp://download.nvidia.com/XFree86/Linux-x86_64/260.19.21/NVIDIA-Linux-x86_64-260.19.21-no-compat32.run">ftp://download.nvidia.com/XFree86/Linux-x86_64/260.19.21/NVIDIA-Linux-x86_64-260.19.21-no-compat32.run</a><br>
<a href="ftp://download.nvidia.com/XFree86/Linux-x86_64/260.19.21/NVIDIA-Linux-x86_64-260.19.21.run">ftp://download.nvidia.com/XFree86/Linux-x86_64/260.19.21/NVIDIA-Linux-x86_64-260.19.21.run</a><br><br>The no-compat32 is 20 megs smaller, and I'd imagine that would be the one used for the Slackbuild, since SBo doesn't officially support multilib. Alternatively, it's possible that it's running the driver installation script and answering "No" to the compat32 question. In any case, I suspect that's what's going on here.<br>
<br>--JK<br>