14.1 - some questions about errors at startup - and yes some programs now don't work
SlackwareThis Forum is for the discussion of Slackware Linux.
Welcome to LinuxQuestions.org, a friendly and active Linux Community.
You are currently viewing LQ as a guest. By joining our community you will have the ability to post topics, receive our newsletter, use the advanced search, subscribe to threads and access many other special features. Registration is quick, simple and absolutely free. Join our community today!
Note that registered members see fewer ads, and ContentLink is completely disabled once you log in.
If you have any problems with the registration process or your account login, please contact us. If you need to reset your password, click here.
Having a problem logging in? Please visit this page to clear all LQ-related cookies.
Introduction to Linux - A Hands on Guide
This guide was created as an overview of the Linux Operating System, geared toward new users as an exploration tour and getting started guide, with exercises at the end of each chapter.
For more advanced trainees it can be a desktop reference, and a collection of the base knowledge needed to proceed with system and network administration. This book contains many real life examples derived from the author's experience as a Linux system and network administrator, trainer and consultant. They hope these examples will help you to get a better understanding of the Linux system and that you feel encouraged to try out things on your own.
Click Here to receive this Complete Guide absolutely free.
Got skype to work, just edited the slackbuild and changed the version from 188.8.131.52 to 184.108.40.206 after downloading the 220.127.116.11.tar.bz2 from skype.com, ran the slackbuild again, and it works *shrug* , still can't figure out google-earth though...
Newer Google-Earth requires you to have OpenGL rendering, meaning if you are using Intel GPU, then you are out-of-luck
about the error message, it seems that you are using dual GPU and the kernel is detecting both of them.
I see. I am using NVIDIA card, and yes I am just using the binary blob. After the upgrade Google-Earth broke, so I downloaded the latest NVIDIA binaries, 331.28, but I kept getting errors when trying to install it - so I reverted to 319.72 , and installed fine, and I did make sure to install compa32 as well as OpenGL , still no luck
I had to go back and try to setup the 331.28 NVIDIA binaries again to get the errors - it only happens during the compat32 phase , and these are the errors:
unable to determine the architecture of the files '/usr/X11R6/lib/libEGL.la', which has an architecture specific conflict
unable to determine the architecture of the files '/usr/X11R6/lib64/libEGL.la', which has an architecture specificconflict
unable to determine the architecture of the files '/usr/lib/libEGL.la' which has an architecture specific conflict
unable to determine the architecture of the files '/usr/lib64/libEGL.la' which has an architecture specific conflict
I can still boot X and get DRI - but I don't get these errors when using 319 , so I am still using that, either way Google-Earth still gives me the error:
./googleearth-bin: error while loading shared libraries: libGLU.so.1: cannot open shared object file: No such file or directory
I did make sure to also install OpenGL too... so., I dunno
Issue with later drivers, good info but did not solve anything - I attempted to rebuild an install of Google-earth, still no luck, I did download 325 nivida binaries, installed perfectly , no errors, but did not help Google Earth. I don't know, I am guessing I probably just have to wait until a new Google-Earth slackbuild and version of Google Earth is released.. Still a shame that no 64bit Google-Earth... Overall though I am happy with my new sys., Google Earth is not an urgent matter, but I will be following the NVIDIA issue thing a little more closely since others are having the same issues with later versions of the drivers. 325 is working ok, so I am staying with that now.
4) GoogleEarth is a 32bit application only. You need to have the 32bit
compatibility packages installed to have this work on a 64bit system.
Otherwise you'll just see "no such file or directory" errors. I am aware
that Google puts a 64bits debian package out, but this is a 32bits package
with a 64bit wrapper for debian that installs multilib