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.
I will try this today! Thank you, lonestar_italy!.. at the very least for this glimmer of hope. Toes and fingers crossed but I think I can manage one key at a time typing .
UPDATE: That seems to work for now at least on logging out from KDE but I will have to keep an eye on it since in the past before the DRM change KDE would sometimes logout properly a few times and then, I know not why, fail every time after. Hopefully this time it sticks.
However I am a bit dismayed because some time ago I began having minor issues with 500x drivers so dropped back to a 490x driver which worked as expected. I tried newer drivers from time to time and at some point a 525x driver no longer exhibited such issues so I stayed with newer ones. Lately though I've been noticing some behaviours akin to tearing but instead of full screen tearing it only seems to affect graphics and does so in textures and details. I can't help but wonder if this is, whether forced or by accident, due to nvidia going all in on ray tracing or just having little or no concern with my old GTX 1070 era GPU.
After building a 6.1.32 kernel I tried installing a 495X driver and it failed. I may work on that.
However I am a bit dismayed because some time ago I began having minor issues with 500x drivers so dropped back to a 490x driver which worked as expected. I tried newer drivers from time to time and at some point a 525x driver no longer exhibited such issues so I stayed with newer ones.
Support for simpledrm has been added at some point in the way of 525x drivers , and I'm not sure if it's present in any other version. That's also why I used that instead of 530x.
I just tried CONFIG_DRM_SIMPLEDRM=y with the NVIDIA-Linux-x86_64-525.116.04.run driver. When I exit kde back to runlevel 3, I still get a blank screen, and the keyboard still works.
Just for grins, jkh2cpu, if you commonly use "startx" to get to Runlevel 4, maybe try "sddm" instead just to see if that helps. Both "KDE leave" and "Ctrl-Alt-Backspace" will cycle through restarting X to get you back to the sddm "Chooser" but then "Ctrl-Alt-F1" will drop you to Runlevel 3. It would be interesting to find out if that triggers something in nvidia modeset.
If you try this watch out for any entries in Chooser for wayland. It's beginning to work with nvidia but it is horribly slow, at least on my machines.
I just tried CONFIG_DRM_SIMPLEDRM=y with the NVIDIA-Linux-x86_64-525.116.04.run driver. When I exit kde back to runlevel 3, I still get a blank screen, and the keyboard still works.
My problem was actually different from that. I had the text console reducing to a smaller square part of the screen as soon as the driver was loaded, and then when it reached to load X11 in runlevel 4, everything would turn to black with some stripes of color here and there.
Now with the changes I reported, my text console remains normal until the moment when X11 starts and then the Gui is displayed normally.
I do have a black screen with colored stripes and artifacts if I should switch from X to console with alt-F1 or similar. That has a minor relevance to me.
I will try to recompile the kernel with the patch for fbdev and see if that fixes this part.
Just for grins, jkh2cpu, if you commonly use "startx" to get to Runlevel 4, maybe try "sddm" instead just to see if that helps. Both "KDE leave" and "Ctrl-Alt-Backspace" will cycle through restarting X to get you back to the sddm "Chooser" but then "Ctrl-Alt-F1" will drop you to Runlevel 3. It would be interesting to find out if that triggers something in nvidia modeset.
If you try this watch out for any entries in Chooser for wayland. It's beginning to work with nvidia but it is horribly slow, at least on my machines.
I just tried with the new stable 550 driver (with modeset=1 and fbdev=1), and console never comes back after exiting X in init 3. :/ (535 and 545, I'd at least get a console.) Did the fix not make it to the 10 series cards? (I've got an nvidia 1050ti.) Keyboard works, so it's the same issue as jkh2cpu was having.
I'm no longer having trouble with logout funkyness. When I exit to run level 3, I get a screen and a keyboard. I'm running a GTX 1060, and I just startx, no wayland yet... too unstable.
I'm running the latest kernel in -current, and I just downloaded the new 550 driver. A few weeks ago, I needed to patch the nvidia source before building. I've not done that since 6.6.16 or so.
I'm no longer having trouble with logout funkyness. When I exit to run level 3, I get a screen and a keyboard. I'm running a GTX 1060, and I just startx, no wayland yet... too unstable.
Nothing special... except that I now use grub as elilo will loose the terminal screen on exit to run level 3. Grub is really easy to install in slackware these days. Grub-install and grub-mkconfig -o /boot/grub/grub.cfg should do it, with a repeat grub-mkconfig routine every time that you change the kernel. You might have to adjust the boot order in your machine's bios settings.
Oh yes! Perfectly! I even get console fonts again!
So the secret is to add "modeset=1" and "fbdev=1" to nvidia_drm's parameters in /etc/modprobe.d. (I had these as kernel boot parameters, which...doesn't work.)
So in /etc/modprobe.d I have a file "nvidia_drm.conf":
Code:
options nvidia_drm modeset=1 fbdev=1
Reboot, and it works with 550. Huzzah. I can exit X, no change in boot loader needed. 32-bit OpenGL doesn't work right yet, but that's another bug for another thread...
LinuxQuestions.org is looking for people interested in writing
Editorials, Articles, Reviews, and more. If you'd like to contribute
content, let us know.