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.
Distribution: Slackware64 15.0 (started with 13.37). Testing -current in a spare partition.
Posts: 928
Rep:
Quote:
Originally Posted by garpu
Those are module options, not kernel ones. (I made the same mistake.) In /etc/modprobe.d, you need a file called nvidia_drm.conf with "options nvidia_drm modeset=1 fbdev=1" in it.
Added experimental support for framebuffer consoles provided bynvidia-drm.
On kernels that implement drm_fbdev_generic_setup anddrm_aperture_remove_conflicting_pci_framebuffers,
nvidia-drm will installa framebuffer console when loaded with both `modeset=1` and `fbdev=1`kernel module parameters.
This will replace the Linux boot console drivenby a system framebuffer driver such as efifb or vesafb.
Note that when an nvidia-drm framebuffer console is enabled, unloadingnvidia-drm will cause the screen to turn off.
But even passed as a kernel options (I pass them in the "append" line in lilo.conf, and they appear in the /proc/cmdline), they made
difference on how NVidia driver works for me. Now with them, suspend recovers OK.
Yeah, it's worded weirdly, and I made the same mistake. (It would probably be better if it were made explicit that the kernel module parameters are for the nvidia_drm module.) I don't think either do anything when called as kernel boot parameters.
The downside is, as the note says, that if you unload the nvidia_drm module, you'll get a black screen. This is an annoyance when upgrading drivers, for instance. (I had to comment out the "options" line, reboot (I'm always runlevel 3), uncomment the line once booted, then upgrade drivers. If anyone has a better way of doing this, I'm all ears.)
Distribution: Slackware64-current with "True Multilib" and KDE4Town.
Posts: 9,103
Original Poster
Rep:
Nvidia's "Production Branch" Driver, Version: 550.76, has been released.
The "release highlights," a list of supported products and a download link can be found at, https://www.nvidia.com/Download/driv.../224022/en-us/
Installation instructions can be found under the heading, "Additional Information" at the above link. Under that same heading you can find detailed installation instructions by clicking on "README."
Last edited by cwizardone; 04-17-2024 at 09:22 AM.
Distribution: Slackware64-current with "True Multilib" and KDE4Town.
Posts: 9,103
Original Poster
Rep:
Nvidia's "Production Branch" Driver, Version: 550.78, has been released.
The "release highlights," a list of supported products and a download link can be found at, https://www.nvidia.com/Download/driv.../224350/en-us/
Installation instructions can be found under the heading, "Additional Information" at the above link. Under that same heading you can find detailed installation instructions by clicking on "README."
LinuxQuestions.org is looking for people interested in writing
Editorials, Articles, Reviews, and more. If you'd like to contribute
content, let us know.
