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-current with "True Multilib" and KDE4Town.
Posts: 9,137
Original Poster
Rep:
Quote:
Nouveau Patches Posted For Running On NVIDIA GSP-RM Firmware, Initial RTX 40 Ada Support
By Michael Larabel. 18 September 2023.
The long-awaited patches for allowing the open-source NVIDIA "Nouveau" upstream Linux kernel driver to leverage NVIDIA's GPU System Processor "GSP" firmware for handling GPU re-clocking and other hardware tasks with RTX 20 GPUs and newer have been posted. With this set of 44 patches also comes the initial GPU hardware accelerated support for the GeForce RTX 40 "Ada Lovelace" GPUs that is built upon this new GSP driver code path..........
The Maintainer Of The NVIDIA Open-Source "Nouveau" Linux Kernel Driver Resigns
Code:
Hours after posting a large patch series for enabling the Nouveau kernel driver to use NVIDIA's GSP
for improving the support for RTX 20/30 series hardware and finally enabling accelerated graphics support
on RTX 40 "Ada Lovelace" GPUs, the Red Hat maintainer has resigned from his duties.
Distribution: Slackware64-current with "True Multilib" and KDE4Town.
Posts: 9,137
Original Poster
Rep:
Nvidia's "Production Branch" Driver, Version: 535.113.01, 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.../211711/en-us/
Quote:
Fixed a bug that could cause GPU memory utilization to be reported incorrectly for Multi-Instance GPU (MIG) partitions on Grace Hopper systems.
Fixed a bug that intermittently caused the display to freeze when resuming from suspend on some Ada GPUs.
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."
Distribution: Slackware64 15.0 (started with 13.37). Testing -current in a spare partition.
Posts: 932
Rep:
Off-topic: the font they use is nice, I found it for download (or at least very similar) https://en.bestfonts.pro/font/nvidia-sans.
Too bad there isn't a monospace font.
I'm still using RTX 4090 on Slackware64-current and SBo's latest nvidia-driver (all up-to-date as of minutes ago). A few days ago I found out I have no framebuffer device, as shown below (I guess that's why the text looks more like size & rows & columns for '1080p' on 4K?).
Code:
root@cosmos:~# fbv image.jpg
open /dev/fb0: No such file or directory
root@cosmos:~# fbi *.jpg
using "Liberation Mono-16", pixelsize=16.67 file=/usr/share/fonts/TTF/LiberationMono-Regular.ttf
trying drm: /dev/dri/card0 ...
drm: no dumb buffer support
trying fbdev: /dev/fb0 ...
open /dev/fb0: No such file or directory
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."
Added experimental support for framebuffer consoles provided by nvidia-drm. On kernels that implement drm_fbdev_generic_setup and drm_aperture_remove_conflicting_pci_framebuffers, nvidia-drm will install a framebuffer console when loaded with both `modeset=1` and `fbdev=1` kernel module parameters. This will replace the Linux boot console driven by a system framebuffer driver such as efifb or vesafb.
Note that when an nvidia-drm framebuffer console is enabled, unloading nvidia-drm will cause the screen to turn off.
Updated nvidia-installer to allow installing the driver while an existing NVIDIA driver is already loaded.
Distribution: Slackware64 15.0 (started with 13.37). Testing -current in a spare partition.
Posts: 932
Rep:
The new beta driver 545.23.06 didn't work for me in Slackware 15.0.
It starts the X session, but if I change to tty2 console and then go back
to the X session in tty1, I get a black screen with only the mouse pointer.
I can exit with ctrl+alt+backspace.
I tried to boot with kernel options modeset=1 and fbdev=1 to no avail.
Now I'm running the good old stable 535.113.01
It's not working for me, either, and yes my card is on the A-OK list. This is nothing new for me. It's been going on since maybe last January.
Same problem: once X is started, there is no returning to a visible terminal. The keyboard does work, which is good. To upgrade slackware-current, I'll log out of KDE to a blank screen. I then start an SSH session into machine with no working terminal screen, and do my upgrades from there. I'll reboot, if necessary, otherwise I go back to the machine with no terminal screen, type startx, and I'm back in KDE land.
Distribution: Slackware64 15.0 (started with 13.37). Testing -current in a spare partition.
Posts: 932
Rep:
Quote:
Originally Posted by jkh2cpu
It's not working for me, either, and yes my card is on the A-OK list. This is nothing new for me. It's been going on since maybe last January.
Same problem: once X is started, there is no returning to a visible terminal. The keyboard does work, which is good. To upgrade slackware-current, I'll log out of KDE to a blank screen. I then start an SSH session into machine with no working terminal screen, and do my upgrades from there. I'll reboot, if necessary, otherwise I go back to the machine with no terminal screen, type startx, and I'm back in KDE land.
I will try later in -current, but in Slackware 15.0 I can change to another console (eg tty2-6), and
exit the X session (Xfce) goes to tty1 without problems (with 535.113.01 driver).
IIRC, in -current with the 535.113.01 driver all that works too. I don't boot too often in -current.
Distribution: Slackware64 15.0 (started with 13.37). Testing -current in a spare partition.
Posts: 932
Rep:
Quote:
Originally Posted by cwizardone
Some of the 700 series have already gone "legacy," but the GTX-745 and above have not (yet).
Yes, they split the 700 series. I'm afraid they will do the same with 900 series,
supporting 980 Ti and 980 (and maybe 970), and throwing 9[65]0 at the "pit of legacy".
Well, at some point we are going to build a new machine anyway
I tested the beta 545.23.06 in -current up to date (with 6.5.1 kernel), and it seems that
the problem changing to a console and back to X session gives a black screen, is related to the DE.
It happens with Xfce but not with KDE.
In KDE, Kwin is reloaded when coming back from a console, maybe this is the difference, I don't know.
Distribution: Slackware64-current with "True Multilib" and KDE4Town.
Posts: 9,137
Original Poster
Rep:
Quote:
Originally Posted by Paulo2
Yes, they split the 700 series. I'm afraid they will do the same with 900 series,
supporting 980 Ti and 980 (and maybe 970), and throwing 9[65]0 at the "pit of legacy".......
It is based on the GPU microarchitecture. Most of the 700 series used the Kepler architecture. The top three were based on the newer Maxwell architecture. So, you are safe until they decide to "legacy" Maxwell. https://en.wikipedia.org/wiki/Kepler_(microarchitecture)
LinuxQuestions.org is looking for people interested in writing
Editorials, Articles, Reviews, and more. If you'd like to contribute
content, let us know.