LinuxQuestions.org - Which NVIDIA driver do you use, Nouveau or the proprietary blob?

- Slackware (https://www.linuxquestions.org/questions/slackware-14/)

- - Which NVIDIA driver do you use, Nouveau or the proprietary blob? (https://www.linuxquestions.org/questions/slackware-14/which-nvidia-driver-do-you-use-nouveau-or-the-proprietary-blob-4175428692/)

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.

Yes, I'm using the SlackBuild to build version 304.51.

Code:

CC          mkprecompiled.c

  LINK        _out/Linux_x86_64/mkprecompiled

  STRIP        _out/Linux_x86_64/mkprecompiled

  HOST_CC      makeself-help-script.c

  HOST_CC      common-utils/common-utils.c

  HOST_CC      common-utils/nvgetopt.c

  HOST_LINK    _out/Linux_x86_64/makeself-help-script

_out/Linux_x86_64/makeself-help-script --advanced-options-args-only >> _out/Linux_x86_64/makeself-help-script.sh

_out/Linux_x86_64/makeself-help-script --help-args-only >> _out/Linux_x86_64/makeself-help-script.sh

chmod u+x _out/Linux_x86_64/makeself-help-script.sh

  HOST_CC      gen-manpage-opts.c

  HOST_CC      common-utils/gen-manpage-opts-helper.c

  HOST_LINK    _out/Linux_x86_64/gen-manpage-opts

  M4          nvidia-installer.1.m4

/tmp/SBo/NVIDIA-Linux-x86_64-304.51

rm -f libXNVCtrl.a *.o

cc -O2 -fPIC -fPIC  -c -o NVCtrl.o NVCtrl.c

ar rv libXNVCtrl.a NVCtrl.o

ar: creating libXNVCtrl.a

a - NVCtrl.o

ranlib libXNVCtrl.a

rm NVCtrl.o

make[1]: Entering directory `/tmp/SBo/nvidia-settings-304.51/src'

  CC          command-line.c

In file included from command-line.c:32:0:

glxinfo.h:23:20: fatal error: GL/glx.h: No such file or directory

compilation terminated.

make[1]: *** [_out/Linux_x86_64/command-line.o] Error 1

make[1]: Leaving directory `/tmp/SBo/nvidia-settings-304.51/src'

make: *** [all] Error 2

EDIT: It's the same problem reported in this thread:

http://www.linuxquestions.org/questi...pkg-4175430166

EDIT 2: Apparently, the procedure is:

Code:

nvidia-switch --remove

Then rebuild both nvidia-kernel and nvidia-driver.

Hello,

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.

I used the SlackBuild for a non-multilib 64-bit only system and it worked for me.

I recommend using the SlackBuild rather than using the Nvidia-Installer.

Hi,

If you happen to have 'optimus' then I suggest that you look at: https://github.com/jgeboski/Bumblebee-SlackBuilds/tree/

Code:

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

Quote:

Originally Posted by ponce (Post 4800453)

FYI, the "smurf effect" on youtube is fixed with the release of libvdpau-0.5.

But not in Opera, because it searches for "libflashplayer" in "/proc/self/cmdline".

The bug should be fixed where it actually is: in the flash player binary.

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.

Also, for bleeding edge: https://git.gitorious.org/kingbeowul...lackbuilds.git
Branch 'master' is what is planned for SBo and might be a bit 'newer'
Branch '14.0' is WIP

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.

http://www.geforce.com/drivers/results/50148

Praise "Bob"!

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).

I might be mistaken (happens too often :) ), but I think I saw blue people with 304.51 and 304.60. Dunno...

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.

Quote:

Originally Posted by brianL (Post 4813804)

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.