LinuxQuestions.org
Download your favorite Linux distribution at LQ ISO.
Home Forums Tutorials Articles Register
Go Back   LinuxQuestions.org > Forums > Linux Forums > Linux - Distributions > Slackware
User Name
Password
Slackware This Forum is for the discussion of Slackware Linux.

Notices


Reply
  Search this Thread
Old 06-07-2023, 02:46 PM   #46
lonestar_italy
Member
 
Registered: Nov 2010
Location: Italy
Distribution: Slackware64-current
Posts: 175

Rep: Reputation: 70

A feedback:
I compiled kernel 6.1.32 with
Code:
CONFIG_DRM_SIMPLEDRM=y
(I found Arch and other distributions have it enabled) ,

removed
Code:
nvidia-drm.modeset=1
from kernel boot options (which I've been having for very long time), and installed NVIDIA drivers 525.116.04 and it seems to be working fine.

No weirdness during boot and before the start up of X. Sddm displays normally, and Plasma opens and works.
 
2 members found this post helpful.
Old 06-07-2023, 04:46 PM   #47
enorbet
Senior Member
 
Registered: Jun 2003
Location: Virginia
Distribution: Slackware = Main OpSys
Posts: 4,811

Rep: Reputation: 4447Reputation: 4447Reputation: 4447Reputation: 4447Reputation: 4447Reputation: 4447Reputation: 4447Reputation: 4447Reputation: 4447Reputation: 4447Reputation: 4447
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.

Last edited by enorbet; 06-08-2023 at 12:54 AM.
 
1 members found this post helpful.
Old 06-08-2023, 04:32 AM   #48
lonestar_italy
Member
 
Registered: Nov 2010
Location: Italy
Distribution: Slackware64-current
Posts: 175

Rep: Reputation: 70
Quote:
Originally Posted by enorbet View Post
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.

Let's see how it goes for you with time.
 
Old 06-08-2023, 01:20 PM   #49
jkh2cpu
Member
 
Registered: Feb 2014
Location: Michigan, USA
Distribution: slackware
Posts: 287

Rep: Reputation: 63
My machine runs current with multilib.

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.

No joy here.
 
Old 06-08-2023, 10:24 PM   #50
enorbet
Senior Member
 
Registered: Jun 2003
Location: Virginia
Distribution: Slackware = Main OpSys
Posts: 4,811

Rep: Reputation: 4447Reputation: 4447Reputation: 4447Reputation: 4447Reputation: 4447Reputation: 4447Reputation: 4447Reputation: 4447Reputation: 4447Reputation: 4447Reputation: 4447
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.

Last edited by enorbet; 06-08-2023 at 10:26 PM.
 
1 members found this post helpful.
Old 06-08-2023, 10:30 PM   #51
chrisretusn
Senior Member
 
Registered: Dec 2005
Location: Philippines
Distribution: Slackware64-current
Posts: 2,987

Rep: Reputation: 1556Reputation: 1556Reputation: 1556Reputation: 1556Reputation: 1556Reputation: 1556Reputation: 1556Reputation: 1556Reputation: 1556Reputation: 1556Reputation: 1556
Booting to runlevel 3, using startx to start the GUI does not put you in runlevel 4, you are still in runlevel 3.
 
2 members found this post helpful.
Old 06-09-2023, 06:19 AM   #52
lonestar_italy
Member
 
Registered: Nov 2010
Location: Italy
Distribution: Slackware64-current
Posts: 175

Rep: Reputation: 70
Quote:
Originally Posted by jkh2cpu View Post
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.
 
1 members found this post helpful.
Old 06-09-2023, 07:49 AM   #53
jkh2cpu
Member
 
Registered: Feb 2014
Location: Michigan, USA
Distribution: slackware
Posts: 287

Rep: Reputation: 63
Quote:
Originally Posted by enorbet View Post
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 start in runlevel 3, just for grins ;-)

This is for Nvidia to fix.
 
Old 02-23-2024, 12:39 PM   #54
garpu
Senior Member
 
Registered: Oct 2009
Distribution: Slackware
Posts: 1,610

Rep: Reputation: 929Reputation: 929Reputation: 929Reputation: 929Reputation: 929Reputation: 929Reputation: 929Reputation: 929
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.
 
Old 02-23-2024, 05:12 PM   #55
jkh2cpu
Member
 
Registered: Feb 2014
Location: Michigan, USA
Distribution: slackware
Posts: 287

Rep: Reputation: 63
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.

HTH.
 
Old 02-24-2024, 09:56 AM   #56
garpu
Senior Member
 
Registered: Oct 2009
Distribution: Slackware
Posts: 1,610

Rep: Reputation: 929Reputation: 929Reputation: 929Reputation: 929Reputation: 929Reputation: 929Reputation: 929Reputation: 929
Quote:
Originally Posted by jkh2cpu View Post
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.
Hrm. What boot parameters are you using?
 
Old 02-24-2024, 10:10 AM   #57
jkh2cpu
Member
 
Registered: Feb 2014
Location: Michigan, USA
Distribution: slackware
Posts: 287

Rep: Reputation: 63
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.
 
Old 02-24-2024, 11:06 AM   #58
garpu
Senior Member
 
Registered: Oct 2009
Distribution: Slackware
Posts: 1,610

Rep: Reputation: 929Reputation: 929Reputation: 929Reputation: 929Reputation: 929Reputation: 929Reputation: 929Reputation: 929
Oh my god. I'm a complete idiot. I was setting modeset=1 and fbdev=1 as kernel boot parameters, not kernel module parameters.
 
Old 02-24-2024, 11:08 AM   #59
jkh2cpu
Member
 
Registered: Feb 2014
Location: Michigan, USA
Distribution: slackware
Posts: 287

Rep: Reputation: 63
You cannot be an idiot because you figured it out!

Is it working better for you now?
 
Old 02-24-2024, 11:30 AM   #60
garpu
Senior Member
 
Registered: Oct 2009
Distribution: Slackware
Posts: 1,610

Rep: Reputation: 929Reputation: 929Reputation: 929Reputation: 929Reputation: 929Reputation: 929Reputation: 929Reputation: 929
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...
 
1 members found this post helpful.
  


Reply



Posting Rules
You may not post new threads
You may not post replies
You may not post attachments
You may not edit your posts

BB code is On
Smilies are On
[IMG] code is Off
HTML code is Off



Similar Threads
Thread Thread Starter Forum Replies Last Post
NVIDIA problems (NVIDIA-SMI has failed..., NVIDIA driver is not loaded....) CrimsonEvenfall Linux - General 1 04-16-2022 02:33 AM
nvidia-driver SBo The symbolic link '/usr/lib/libGL.so.1' does not point to 'tmp/SBo/package-nvidia-driver/usr/lib64/libGL.so.1' Gerardo Zamudio Slackware 5 07-30-2017 10:44 PM
kernel source and nvidia driver installation issues - have searched timsch75 Slackware 7 11-12-2005 06:36 PM
nvidia fx5600 loads vesa driver instead of nvidia driver saburo62 Linux - Hardware 3 05-04-2004 03:59 PM
kernel 2.6.3--bk8 and NVIDIA-Linux-x86-1.0-5336 video driver from Nvidia zdenkod Linux - Hardware 2 03-09-2004 05:38 AM

LinuxQuestions.org > Forums > Linux Forums > Linux - Distributions > Slackware

All times are GMT -5. The time now is 02:47 AM.

Main Menu
Advertisement
My LQ
Write for LQ
LinuxQuestions.org is looking for people interested in writing Editorials, Articles, Reviews, and more. If you'd like to contribute content, let us know.
Main Menu
Syndicate
RSS1  Latest Threads
RSS1  LQ News
Twitter: @linuxquestions
Open Source Consulting | Domain Registration