Nvidia drivers installed through Slackbuilds but glxinfo error.

Monk Tea · 09-21-2014, 09:38 AM

Hi.

I installed Nvidia kernel first and then the Nvidia driver. I had already installed the nouveau blacklist package from extra at that point and rebooted. I can see that I have Nvidia settings under settings in xfce. But when I types glxinfo, it gives error:

Code:

bash-4.2$ glxinfo
name of display: :0.0
X Error of failed request:  BadWindow (invalid Window parameter)
  Major opcode of failed request:  153 (NV-GLX)
  Minor opcode of failed request:  4 ()
  Resource id in failed request:  0x2c00003
  Serial number of failed request:  33
  Current serial number in output stream:  33

glxgears gives:

Code:

bash-4.2$ glxgears
X Error of failed request:  BadWindow (invalid Window parameter)
  Major opcode of failed request:  153 (NV-GLX)
  Minor opcode of failed request:  4 ()
  Resource id in failed request:  0x2c00002
  Serial number of failed request:  38
  Current serial number in output stream:  38

I checked the /etc/X11/xorg.conf and its like this:

Code:

# nvidia-xconfig: X configuration file generated by nvidia-xconfig
# nvidia-xconfig:  version 340.24  (root@her)  Sun Sep 21 18:32:59 IST 2014

Section "ServerLayout"
    Identifier     "Layout0"
    Screen      0  "Screen0"
    InputDevice    "Keyboard0" "CoreKeyboard"
    InputDevice    "Mouse0" "CorePointer"
EndSection

Section "Files"
    FontPath        "/usr/lib64/X11/fonts/misc/:unscaled"
    FontPath        "/usr/lib64/X11/fonts/100dpi/:unscaled"
    FontPath        "/usr/lib64/X11/fonts/75dpi/:unscaled"
    FontPath        "/usr/lib64/X11/fonts/misc/"
    FontPath        "/usr/lib64/X11/fonts/Type1/"
    FontPath        "/usr/lib64/X11/fonts/Speedo/"
    FontPath        "/usr/lib64/X11/fonts/100dpi/"
    FontPath        "/usr/lib64/X11/fonts/75dpi/"
    FontPath        "/usr/lib64/X11/fonts/cyrillic/"
    FontPath        "/usr/lib64/X11/fonts/TTF/"
EndSection

Section "InputDevice"
    # generated from default
    Identifier     "Mouse0"
    Driver         "mouse"
    Option         "Protocol" "auto"
    Option         "Device" "/dev/psaux"
    Option         "Emulate3Buttons" "no"
    Option         "ZAxisMapping" "4 5"
EndSection

Section "InputDevice"
    # generated from default
    Identifier     "Keyboard0"
    Driver         "kbd"
EndSection

Section "Monitor"
    Identifier     "Monitor0"
    VendorName     "Unknown"
    ModelName      "Unknown"
    HorizSync       28.0 - 33.0
    VertRefresh     43.0 - 72.0
    Option         "DPMS"
EndSection

Section "Device"
    Identifier     "Device0"
    Driver         "nvidia"
    VendorName     "NVIDIA Corporation"
EndSection

Section "Screen"
    Identifier     "Screen0"
    Device         "Device0"
    Monitor        "Monitor0"
    DefaultDepth    24
    SubSection     "Display"
        Depth       24
    EndSubSection
EndSection

Drakeo · 09-21-2014, 10:19 AM

open a terminal and type nvidia-settings if it runs ok then the driver is loaded. The Nvidia proprietary blob actually uses parts of mesa. I would go to run level 3 and then sh NVIDIA-Linux-arch-version-run --uninstall then reinstall mesa.
if using slackbuilds i have no clue I tried it once just to complicated for me. That is what your missing. parts of mesa.
then reboot go to run level 3 and run sh NVIDIA-Linux-arch-version-run then startx or telinit 4 or kdm what ever you want.
http://www.nvidia.com/Download/index.aspx
as part of slackbuilds they use the nvidia switch to go back and forth again that is far from KISS.
I use the KISS method build it like the manufacture want's it built in a root environment in run level three. it then uses the mesa and takes two files and stashes them till you run the uninstall script.
Slackbuilds does the same thing they just have the driver build and the driver loader split up with a switch script.
Like i said either you want to use the driver or not.

I been using Slackware as my main system since 2004 and down loading the driver to /root then in runlevel three run the sh NVIDIA-Linux-arch-version-run then startx. it has never let me down with a stable version of slackware and the driver for that time and era.
Not only that if you are running the opensource driver it will ask to blacklist it and then you rebbot and then at run level 3 you can then run the build script.
I am sure.
the day they create a build script like puppy linux that just down loads the driver from nvidia and then builds the driver and installer and installs it and creats a package then I will use it.
but till then Do it the slackware way install it vanilla.

kingbeowulf · 09-25-2014, 09:39 PM

This is essentially what the Slackbuilds (SBo) package does - it replicates the nivida installer in a Slackware compliant manner. Also, anything peculiar to Slackware are fixed (or I should say, weird glitches nvidia copies from those other distros). There's an additional script to flip back to Mesa and GLX libs without having to run the nivdia-*.run --uninstall script. In fact, BEFORE you uninstall the the nvidia packages you MUST

Code:

# nvidia-switch --remove

to properly restore Xorg.

Monk Tea, definitely run 'nvidia-settings' from the command line. If you get the same error, then your X is not using/can't find the nvidia GLX extensions and your opensource GLX extension are hosed. You will need to correct that issue. With Nvidia packages properly installed:

Code:

$ ls -l /usr/lib64/xorg/modules/extensions/
total 11152
-rwxr-xr-x 1 root root      932 Oct  9  2013 libglx.la-xorg
lrwxrwxrwx 1 root root       16 Jul 18 15:59 libglx.so -> libglx.so.340.24
-rwxr-xr-x 1 root root   419880 Oct  9  2013 libglx.so-xorg
lrwxrwxrwx 1 root root       23 Jul 18 15:59 libglx.so.340.24 -> libglx.so.340.24-nvidia
-rwxr-xr-x 1 root root 10989992 Jul 18 15:44 libglx.so.340.24-nvidia
$ ls -l /usr/lib64/libGL.*
-rwxr-xr-x 1 root root     646 Jul 18 15:45 /usr/lib64/libGL.la
lrwxrwxrwx 1 root root      10 Jul 18 15:59 /usr/lib64/libGL.so -> libGL.so.1
lrwxrwxrwx 1 root root      15 Jul 18 15:59 /usr/lib64/libGL.so.1 -> libGL.so.340.24
-rwxr-xr-x 1 root root  511032 Oct 21  2013 /usr/lib64/libGL.so.1.2.0-xorg
lrwxrwxrwx 1 root root      22 Jul 18 15:59 /usr/lib64/libGL.so.340.24 -> libGL.so.340.24-nvidia
-rwxr-xr-x 1 root root 1267768 Jul 18 15:44 /usr/lib64/libGL.so.340.24-nvidia

To use the SBo scripts, you must

exit X and make sure that the original Slackware mesa (opengl) and xorg-server (glx) packages are (re)istalled
blacklist and remove nouveau from memory (modprobe -r or preferably reboot)
log in as root at the command line DO NOT RUN X.
run SBo script; install the libvdpau package
run SBo script; install the kernel package
run SBo script; install the nvidia-driver package
reboot

What you cannot do, is just install all the packages and then just type "startx" - you MUST reboot. Also, if you have converted to multilib from x86_64, you should

Code:

$ COMPAT32-yes ./nvidia-driver.SlackBuild

to enable 32-bit opengl.

The SBo packages install /usr/share/X11/xorg.conf.d/10-nvidia-conf for the "automagical" people; you may delete this to use your own /etc/X11/xorg.conf.d/xorg.conf

Correct your ServerLayout section:

Code:

Section "ServerLayout"
    Identifier     "Layout0"
    Screen      0  "Screen0" 0 0
    InputDevice    "Keyboard0" "CoreKeyboard"
    InputDevice    "Mouse0" "CorePointer"
    Option         "Xinerama" "0"
EndSection

Your monitor

Code:

    HorizSync       28.0 - 33.0
    VertRefresh     43.0 - 72.0

look weird. Are you sure they are correct? CRT or LCD?

Drakeo · 09-25-2014, 10:21 PM

yes I know that but why would you want to switch make no since to me. If it works for you ok good. you still have to rebuild it after a kernel upgrade so what is the big deal the switch does not load the nouveau driver you still have to reboot so I guess it is a vesa thing. Really what is the switch good for so you have to remember to switch back before upgrading a kernel.
But if it works for you fine.
2 does the average user really need a switch for his or her graphics card I mean they installed the blob for a reason.
3 it takes two packages to maintain one driver.
4 what is the real benefit.
question is no glxgears and that means a parts of mesa is missing and if you have a full install and the nvidia run
from nvidia and you install it via sh NVidia you will not have this issue. this issue will arise from the Slackbuild.
this is not KISS.

kingbeowulf · 09-25-2014, 11:27 PM

I am sorry, Drakeo, but you have no idea what K.I.S.S. really means. Nor do you understand the design considerations of the SBo nvidia driver slackbuild. The nvidia script can get very cranky and cause serious stability issues for some. Also, there are many who wish to be able to do a clean switch back the F/OSS Mesa drivers.

Monk Tea · 09-30-2014, 04:55 PM

Hi.

Been a while.

I checked it out and uninstalling Nvidia driver from the official Nvidia site did something to libeegl.la. I can't exactly remember but I found this upon search:http://http://www.linuxquestions.org...rs-4175493420/

I dunno how to solve this. I do have Nvidia drivers installed from the Nvidia site and not the slackbuilds. Any help would be appreciated because that error is not letting me compile many applications from Slackbuilds.

Thanks,
Laxman

---------- Post added 01-10-14 at 03:25 ----------

Hi.

Been a while.

I checked it out and uninstalling Nvidia driver from the official Nvidia site did something to libeegl.la. I can't exactly remember but I found this upon search:http://http://www.linuxquestions.org...rs-4175493420/

I dunno how to solve this. I do have Nvidia drivers installed from the Nvidia site and not the slackbuilds. Any help would be appreciated because that error is not letting me compile many applications from Slackbuilds.

Thanks,
Laxman

Monk Tea · 09-30-2014, 04:57 PM

Hi.

Been a while.

I checked it out and uninstalling Nvidia driver from the official Nvidia site did something to libeegl.la. I can't exactly remember but I found this upon search:http://http://www.linuxquestions.org...rs-4175493420/

I dunno how to solve this. I do have Nvidia drivers installed from the Nvidia site and not the slackbuilds. Any help would be appreciated because that error is not letting me compile many applications from Slackbuilds.

Thanks,
Laxman

Monk Tea · 10-01-2014, 05:24 AM

Sorry for the multiple posts there. I am gonna uninstall the official Nvidia drivers and install it the way Slackbuilds suggest. I will report back here.

Thanks.