SlackwareThis Forum is for the discussion of Slackware Linux.
Notices
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.
Get a virtual cloud desktop with the Linux distro that you want in less than five minutes with Shells! With over 10 pre-installed distros to choose from, the worry-free installation life is here! Whether you are a digital nomad or just looking for flexibility, Shells can put your Linux machine on the device that you want to use.
Exclusive for LQ members, get up to 45% off per month. Click here for more info.
Hi all I just switched over to the nouveau driver because my nvidia one was tainting the kernel and making software installs impossible!
I been running nvidia a long time and you know the software problem you describe is a very simple fix there are two libraries that a moved to /var/lib/nvidia/
and they are renamed 100 and 101. those two files are. libGL.la libEGL.la
those libraries have code in them help compile stuff. and link them. Do conflict with the build of the nvidia driver. They have to be moved.
my work around for years now is to grab the mesa Slackware package and make a folder mesa /root/mesa/ and paste it there then extract it. if in kde desktop right click the package and autodetect subfolder there you will see the exploded package of mesa /usr/lib or /usr/lib64 then when I need those two folders I just link them to my /usr/lib64 or /usr/lib .
now when you need run into the problem of building stuff it will build. when your done just unlink them
because the worst nvidia driver is far superior to nouveau. same thing if you need libGL.so. don't give up the fun.
I keep a download of nvida in /root/ I do not use the Slackbuilds build. if you run current you may need to have stable and beta depending on how the system is changing.
grab the mesa Slackware package and make a folder mesa /root/mesa/ and paste it there then extract it. if in kde desktop right click the package and autodetect subfolder there you will see the exploded package of mesa /usr/lib or /usr/lib64 then when I need those two folders I just link them to my /usr/lib64 or /usr/lib .
now when you need run into the problem of building stuff it will build. when your done just unlink them
because the worst nvidia driver is far superior to nouveau. same thing if you need libGL.so. don't give up the fun.
I keep a download of nvida in /root/ I do not use the Slackbuilds build. if you run current you may need to have stable and beta depending on how the system is changing.
Drakeo,
I looked for that package on the internet and couldnt find what I needed. Can you provide a link pls? also, I am a tad bit confused as to EXACTLY name which file to what and auto detecting in kde is a no go as I do not even have it installed. I can link them no problem. --scarrz
second way is to open dolphin up in as root and drag them and drop them and make it a link.
third way is to reinstall mesa over the top of nvidia and when done . uninstall nvidia and reinstall it.
the Slackbuiuld's switch handles much of thi of this but i never did care for the build. it is in two parts.
and far from kiss.
I rather keep nvidia and build from there nvidia-run.
it pretty simple to say .
Quote:
slackpkg reinstall mesa then do your build then log out to run level 3 and rebuild nvidia
tell you the truth i have left mine linked for months. no real problems
in linux the dot .la files use for telling the program your compiling where everything is.
right click one open it with kwrite you will see.
the link just sends it to your new home for the build.
if you need other parts of mesa another way is to do a -root install
Quote:
installpkg -root /tmp/mesa mesa-9.1.7-i486-1.txz
now you have the package with all the links in /tmp/mesa and no it is not installed on your system.
then you can link what ever you need to your /usr/lib.
I will try this soon and mark the thread [SOLVED] if I can install software after I have done all that; thanks. I have a Slackware section in my blog so I will be sure to add these instructions to the blog so I have them for future reference and so others can fix the same problem.
I'm still using the nouveau driver at them moment and I had forgot to mention that I also have dropline GNOME installed (3.10) and I believe the install process added those files we have been discussing in those proper directories. or: is it because I have the nouveau driver installed and it provides those files?
At any rate... I'll uninstall the nouveau driver today and follow those instructions and de-install "Clementine" and re- install it and see if it passed the build process.
Well dropline gnome is a nice project and it really does not change the fact nvidia grabs them libraries and has to hide them and use there own in order to handle the chip.
how to install
Quote:
Optional dependencies:
gst-plugins-bad (for http support) <--you really do need it
gst-plugins-ugly (for mp3 support) <<--you really do need it
libimobiledevice (for iPod support)
libusbmuxd (for iPod support)
libspotify and libqca (for Spotify support) (not on SBo)
libvlc (not available on slackbuilds.org but AlienBob has vlc packages
and slackbuilds at http://connie.slackware.com/~alien/slackbuilds/vlc/ )
This requires: protobuf
you really want to build that for your system get with me I will do up a build script for you.
but if you really want most of that. read here and you will have a serious media center. https://forum.kde.org/viewtopic.php?...303965#p303965
you need to install openjdk and reboot then start your build. I used SBOPKG
Well dropline gnome is a nice project and it really does not change the fact nvidia grabs them libraries and has to hide them and use there own in order to handle the chip.
how to install
you really want to build that for your system get with me I will do up a build script for you.
but if you really want most of that. read here and you will have a serious media center. https://forum.kde.org/viewtopic.php?...303965#p303965
you need to install openjdk and reboot then start your build. I used SBOPKG
PS: I just went ahead with your FIRST set of instructions and installed the nvidia driver and dis a re-install of clementine and it compiled just fine so everything looks good so far
can't wait to hear back on this because I'm having display problems with dropline (mostly with IRC clients) but we all do a bunch of that so it needs to be fixed.
everyone of those programs contribute to several things. one is your building audacity one of the finest audio manipulation tools. Two your building ffmpeg that is the base to to everything. three your build libquick time this lets you play about every format out there. then your building kdenlive and that is the next best thing to adobe for video manipulation.
did you ever look at all the programs that have to be built for "clementine" it requires vlan and that is 85 percent of what we have there.
everyone of those programs contribute to several things. one is your building audacity one of the finest audio manipulation tools. Two your building ffmpeg that is the base to to everything. three your build libquick time this lets you play about every format out there. then your building kdenlive and that is the next best thing to adobe for video manipulation. did you ever look at all the programs that have to be built for "clementine" it requires vlan and that is 85 percent of what we have there.
okay... I am having problems with audio so I uninstalled the pulseaudio package that came with dropline GNOME because the Slackbuild is an updated version and:
Code:
sboinstall pulseaudio
and the build failed looking for those files libEGL.la or whatever (I forget atm)
so I:
Code:
slackpkg reinstall mesa
Code:
sboinstall pulseaudio
and everything built properly so I am partly happy.
looks like reinstalling that package will make software compiling work (yay) but I am not marking this thread as [SOLVED] because however, I can run dropline GNOME; but rendering is VERY poor and I am experiencing things like text disappearing from the bottom line of xchat whenever anyone types a new message. (the userlist also behaves the same way whenever a user joins or parts) Also, I have noticed parts of my webpage (Google) like the user information app (top right when logged into google.com or google.ca) also disappearing when I hover over it with the mouse or even doing nothing at all! So it looks like my xorg.conf is going to need a little tweaking for dropline GNOME to function properly. And I really want this to happen. here is a section of my xorg.conf that I am using for opengl and composite:
I can run all my ccsm effects and emerald without any problems except a bit of memory usage in XFCE just fine so I was assuming that what I had found on Google to tweak my xorg.conf was working, but I guess I am missing something. Think you can help?
and I understand about installing and linking with:
Quote:
after extracting the package thats all slackware packages are are tar ball so assume your in root. open a terminal type mkdir mesa then cd mesa . type ls and you will see etc, install, usr cd /usr/lib for 32 bit for 64 bit it would be /usr/lib64
I don't have dolphin (or KDE for that matter) installed so I can't make a link that way, but oh well... I am smart enough to do it from the terminal. so I think that is probably the best way to do it and am going to do it that way in a bit here. I would REALLY appreciate your help on tweaking the nVIDIA driver to work properly with GNOME. I's a pet install, and I am really happy with it (except for my audio problem). (here)
RSVP
Last edited by scarrz; 08-30-2014 at 02:31 PM.
Reason: because
unfortunately dropline GNOME won't start now. was doing some Googling to tweak my xorg.conf to get rid of the odd rendering problems I was having and things are running smoothly in XFCE... but from runlevel 3 when I run startx to GNOME, GNOME starts, and I get a grey screen with "oops" something has gone wrong and a window pops up to unlock my keyring; then x locks up. here is my current xorg.conf that works just fine with XFCE:
LinuxQuestions.org is looking for people interested in writing
Editorials, Articles, Reviews, and more. If you'd like to contribute
content, let us know.