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.
Our xorg-server was built to the defaults Enorbet. That's why we have the error in the xorg logs.
Patrick probably didn't know about the switch when he was importing that version of xorg-server. Yes, it needs to be disabled in the standard Slackware release. If primus and bumblebee both detect that stray setting and cause a foul up when launching 3D applications, then it is a problem, but normally it should work without any issues.
It requires (or greatly prefers) the Intel driver be installed before the nvidia driver.
Well, what is a intel driver? Integrated videocard runs out of the box, doesn't in? Is it libva-intel-driver that I must install?
Quote:
Additionally it is recommended that you create and add user to the bumblebee group
Done that from the beginning.
Quote:
Plus you need to enable the bumblebeed.service
It is enabled in my rc.local
Quote:
GLX errors should be solved by letting nvidia install mesa et al.
Could you please more thoroughly explain how to do that? I have no idea.
>>>I am still experiencing GLX errors, can't run steam and most of the games.
And to ReaperX7,
Quote:
You can try to reinstall the Nvidia-driver and see if it does help, but if Steam is checking for Xorg, it won't matter what driver you install, as this is not a driver issue, but an issue with the xorg-server directly.
I can walk you through fixing this if you're interested.
Now go back to the root directory of the x11 directory you copied and run:
Code:
./x11.SlackBuild xorg-server xorg-server
This will rebuild xorg-server according and drop some packages in /tmp when completed. Just use 'upgradepkg --reinstall' on them. Now restart the X server and check the log. You should NOT have any (EE) entries which means systemd-logind support is now gone.
Try running primusrun with your applications and see if it helps. Hopefully it will.
The tty0 node should be created by the system during the boot phase, namely during the /dev mount and starting of udev. It should also be activated for agetty by the entry in /etc/inittab.
Are you logged in as root to test it, or a user account?
Actually good news!!!
If startx initiated as root, there is no problem with GLX extensions! Glxinfo works perfectly. Now all remains is to do startx as normal user.
Thanks.
I've also recompiled xorg-server, but not with the stock slackbuild. I had to set both Xorg.bin and Xorg.wrap (found in /usr/libexec) suid root. Although the --enable-suid-wrapper option would have me believe that only Xorg.wrap ought to need to be set suid. But I never bothered to dig deeper.
Although I intend to continue watching this thread and offer suggestions if and when I see something of which I feel certain, but given that I don't have Optimus and still install nVidia proprietary driver generically from runlevel 3 (not a slackpack nor slackbuild) I think I should hang back to avoid confusion with steps and actions that don't apply or miss extras I don't have to contend with.
Example - nvidia's installer searches for conflicting libraries and installs GLX and Mesa that it knows works with that version driver and hardware. It is not known to me if the SBs behave in this manner. I've been installing nvidia's driver this way for over 10 years and excepting choosing newer drivers on old hardware that would not install (and told me why and what to get) I have never had any problems with nvidia drivers and I don't have to wait for someone to build a SlackBuild nor create one myself for nvidia anyway.
LinuxQuestions.org is looking for people interested in writing
Editorials, Articles, Reviews, and more. If you'd like to contribute
content, let us know.