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.
You mean the nouveau.modset=0 parameter? It's not relevant because I had removed the nouveau*.ko when doing the test, so I did not need bother to remove the parameter as well.
I can't be certain of what the behaviour should be in this specific instance but it seems to me that when one specifies a specific choice and it cannot be found an error should be generated and I didn't see one. As I also said, I'm grasping at straws so I notice any anomalies and try to systematically remove any room for doubt so that I'm left with certainty. That's just how I troubleshoot the less than obvious.
Yes, you need it with a Intel/nvidia setup if you want to use the nvidia card for rendering. You also should specify the BusID for both cards and the drivers to use, i.e. "nvidia" and "modesetting" respectively. I have Slackware64-14.2, intelHD and GTX1060. I had to get the latest kernel (4.16.10 at the time), because the older one woudn't recognize the intel card, but otherwise it runs OK. For the record, my xorg.conf:
That is assuming you have the nvidia driver enabled. I've had 3 or 4 laptops with this setting and the id was always NVIDIA-0 so there's a good chance it will be the same in your case.
@millgates, Another question is, I saw you have two Screen section in your config, one use intel the other use nvidia, what does it mean?
To be honest, I don't really know. I think both cards need to have a screen associated with them. Some xorg.conf examples for optimus such as this one have those so I put it there. Usually, the nvidia card has no physical output and can only be connected to the screen through the intel card, so the Option "UseDisplayDevice" "None" is there to tell the X server to not expect a monitor connected to it. As for the intel device section, I'm not sure whether or not it needs to be explicitly specified, but it doesn't seem to hurt.
Last edited by millgates; 06-27-2018 at 09:07 AM.
Reason: fixing the link
To be honest, I don't really know. I think both cards need to have a screen associated with them. Some xorg.conf examples for optimus such as this one have those so I put it there. Usually, the nvidia card has no physical output and can only be connected to the screen through the intel card, so the Option "UseDisplayDevice" "None" is there to tell the X server to not expect a monitor connected to it. As for the intel device section, I'm not sure whether or not it needs to be explicitly specified, but it doesn't seem to hurt.
I basically copied your xorg.conf and the xrandr command lines, still cannot start X with the nvidia driver, the screen simply halt with a white cursor stay in the upper left corner forever. Attached is the log.
Can you give the output of xrandr --listproviders while the X server is running?
(you can either swith to a tty with ctrl+alt+F1 and run
Code:
DISPLAY=:0.0 xrandr --listproviders
or put the command in the .xinitrc startup script. You are using runlevel 3 and startx, right? Did you put the commands I mentioned earlier to your .xinitrc? They should go right before the window manager is started. Which WM/DE are you using?
Distribution: Slackware64-current with "True Multilib" and KDE4Town.
Posts: 9,095
Rep:
Quote:
Originally Posted by enorbet
.....makes me suspect 4.17.1 or even Xorg's reaction to the kernel........
The OP's setup may introduce different problems, but, FWIW, I have not had any problems with the DUSK-4.17.1, 4.17.2 and 4.17.3 kernels, xorg-1.20.0, and the Nvidia-390.67 driver.
Last edited by cwizardone; 06-27-2018 at 10:48 AM.
Looking at your Xorg.0.log, it seems that your xserver loads module intel for your intel card while it should be loading modesetting instead. Are you sure your kernel is built with KMS suppport?
Looking at your Xorg.0.log, it seems that your xserver loads module intel for your intel card while it should be loading modesetting instead. Are you sure your kernel is built with KMS suppport?
My X server can only use intel driver for the i915 intel card. Days before I tested and found if I use modesetting driver, the X cannot started. How can I know whether my kernel already with KMS enabled? (I guess it is, because when the system boot up, the font at some stage getting very small and the console resolution switched to a higher one)
Can you give the output of xrandr --listproviders while the X server is running?
(you can either swith to a tty with ctrl+alt+F1 and run
Code:
DISPLAY=:0.0 xrandr --listproviders
or put the command in the .xinitrc startup script. You are using runlevel 3 and startx, right? Did you put the commands I mentioned earlier to your .xinitrc? They should go right before the window manager is started. Which WM/DE are you using?
My X server can only use intel driver for the i915 intel card.
If you want to use the nvidia card, ithink you need to use modesetting driver for intel.
Quote:
Originally Posted by narke
Days before I tested and found if I use modesetting driver, the X cannot started.
Yes, but back then you probably didn't have the required commands in your .xinitrc. I suggest you try again now, and if it fails, post the xorg.0.log again.
LinuxQuestions.org is looking for people interested in writing
Editorials, Articles, Reviews, and more. If you'd like to contribute
content, let us know.