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.

Is anyone else having trouble building the nvidia-driver SlackBuild on Slackware 14.0 multilib? It worked fine before I installed the multilib packages. Now, however, it fails with the following error.

I dind't try the slackbuilds yet, I used the NVIDIA-installer. But I had some problems with said version of the NVIDIA-driver in slackware64 14.0 multilib: Good old neverwinternights client (32 bit) yielded a segfault. It works perfect with the latest driver from the 295 series. The 32 bit version of driver 304.51 works too.

From READMEThis set of SlackBuilds should get Bumblebee up and running on a
Slackware based NVIDIA Optimus setup.
Slackware Docs:
A wiki page on the Slackware docs has been put to gether by another
slacker, TommyC. I recommend you follow the wiki page for a more
in-depth guide.
http://docs.slackware.com/howtos:har...nvidia_optimus
HowTo:
If you have never used a SlackBuild before, please refer to the HowTo
on SlackBuilds.org: http://slackbuilds.org/howto/
Note:
Several of these SlackBuilds support a COMPAT32 option which
allows 32-bit binaries to be build and packaged. This does
require that the system is multilibbed, otherwise the
SlackBuilds will fail.
For more information on multilibbing visit AlienBOB's wiki:
http://alien.slackbook.org/dokuwiki/...kware:multilib
1. Download the sources:
$ ./download.sh
2. Create group: bumblebee:
# groupadd bumblebee
Add users to the group:
# usermod -G bumblebee -a USERNAME
Note: you will need to re-login as the user for this to take effect
3. Build and install: libjpeg-turbo
If the system is x86_64 based, 32-bit compatible binaries and
libraries can be installed via:
# COMPAT32=yes ./libjpeg-turbo.SlackBuild
4. Build and install: VirtualGL
If the system is x86_64 based, 32-bit compatible binaries and
libraries can be installed via:
# COMPAT32=yes ./VirtualGL.SlackBuild
5. Build and install: nvidia-bumblebee (Optional, if using nouveau)
If the system is x86_64 based, 32-bit compatible binaries and
libraries can be installed via:
# COMPAT32=yes ./nvidia-bumblebee.SlackBuild
6. Build and install: nvidia-kernel (Optional, if using nouveau)
7. Build and install: bbswitch (Optional)
This in an optional requirement. If you do not need power management or
the ability to turn off the nVidia chip, you can skip this.
8. Build and install: libbsd
9. Build and install: bumblebeed
10. Run the rc.bumblebee script:
# chmod +x /etc/rc.d/rc.bumblebeed
# /etc/rc.d/rc.bumblebeed start
If you'd like to have bumblebee autostart with the system, you'll need
to add the following lines to: /etc/rc.d/rc.local:
if [ -x /etc/rc.d/rc.bumblebeed ]; then
/etc/rc.d/rc.bumblebeed start
fi
You can also go a step further by having bumblebeed start with your
system by adding the following lines to: /etc/rc.d/rc.local_shutdown:
if [ -x /etc/rc.d/rc.bumblebeed ]; then
/etc/rc.d/rc.bumblebeed stop
fi
Now an application can run with optirun:
$ optirun glxgears

I built this about three weeks ago with no issues. Not to sure that I will upgrade at this time

Dugan,
You could also email the slackbuild maintainer (me). In all the 14.0 RC excitement there were a few "typos" that showed up when installing/updating 304.xx and for the nvidia security bug from earlier version. Also, Upstream no longer advises stomping on the Mesa headers. But, if you don't correctly restore Mesa, THEN remove the old nvidia SBo package, THEN run the new SBo scripts, the wrong non-Mesa headers might still be still present. Anyway, from this point you should be ok for future upgrades without needing 'nvidia-switch --remove' and bug reports are welcome.

Speaking of bug reports: I travel quite a bit for work so beside posting here you might also consider dropping me an email (see .info) or on the SBo mailing list. I don't always have access to LQ (ie web) so may not notice people are having difficulties for many days.

Something weird I haven't seen in this thread, or anywhere else: I have to use the proprietary NVIDIA driver, rather than the new nouveau driver (or older "nv" driver). With either nv or nouveau, when power management puts my monitor to sleep, it will not wake up using the keyboard or mouse. The only way to wake it up is to turn the monitor off and back on (pressing the monitor's "menu" button works too). This is really strange, and was one of the main reasons I switched to the NVIDIA driver. I assume the problem is just some odd quirk between my video card (ASUS GeForce 7300GT) and monitor (HP S2331), which started when I switched from using the VGA to the DVI port. Using the NVIDIA driver fixed it (as well as other things).

The blue people/libvdpau problem has been fixed with the latest beta driver (310.14) from NVidia (fingers crossed). I've tried it on a few YouTube music videos with hardware acceleration enabled and it seems OK.

I noticed that recently (not sure if it was 304.51* that introduced this) but the nvidia driver seems to take a long time (a second or two) to restore the X11 desktop after exiting a fullscreen SDL based application. I hadn't noticed this behaviour on older drivers, and it doesn't happen with nouveau. Any one else seen this?

(* there were some SDL changes listed in 304.37 release notes, so they may be the trigger).

actually, the accellerated blue man group effect appears to be gone with nvidia-304.51 and libvdpau-0.5 under Slackware64 14.0 Firefox 16.0.1 and flash-11.2.202.238, for the vids I checked on youtube and tekzilla. Ok, I only checked 3 vids (480, 720, 1080) but thats a good enough trend for me.

I'll submit to SBo anon; but if you are anxious, the current libvdpau slackbuild works.

The blue people/libvdpau problem has been fixed with the latest beta driver (310.14) from NVidia (fingers crossed). I've tried it on a few YouTube music videos with hardware acceleration enabled and it seems OK.

This is not a bugfix, it is a workaround and works only in specific browsers (like Firefox). The workaround also breaks any accelerated Flash version, which doesn't have this bug (like 10.3). It will break also, if Adobe finally fixes this bug in 11.2.