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're diving way too much into a topic that doesn't need this type of detail. We don't need to understand the intricacies of X drivers as long as we understand what we need to do on our end (either use the open source nouveau kernel driver or the binary Nvidia driver).
If OP wants proprietary drivers, they need to disable the nouveau kernel driver and install the binary Nvidia drivers. They don't need to worry about everything else as it should handle everything automatically.
In another thread, "denydias" says, "That totally did the trick to me! Running 5.10.4 with functional dual screens. System freeze is gone." --- "denydias" was talking about creating (as suggested by Petri Kaukasoina) a file with this name "/etc/modprobe.d/snd_hda.conf", and putting this in it
Yes, there is a kernel option CONFIG_SND_HDA_INTEL_HDMI_SILENT_STREAM, with help text "Intel hardware has a feature called 'silent stream', that keeps external HDMI receiver's analog circuitry powered on avoiding 2-3 sec silence during playback start. This mechanism relies on setting channel_id as 0xf, sending info packet and preventing codec D3 entry (increasing platform static power consumption when HDMI receiver is plugged-in). 2-3 sec silence at the playback start is expected whenever there is format change. (default is 2 channel format). Say Y to enable Silent Stream feature."
That feature is buggy now in kernel 5.10.4, and that modprobe module option line turns it off.
In another thread, "denydias" says, "That totally did the trick to me! Running 5.10.4 with functional dual screens. System freeze is gone." --- "denydias" was talking about creating (as suggested by Petri Kaukasoina) a file with this name "/etc/modprobe.d/snd_hda.conf", and putting this in it
bassmadrigal
You're diving way too much into a topic that doesn't need this type of detail. We don't need to understand the intricacies of X drivers as long as we understand what we need to do on our end (either use the open source nouveau kernel driver or the binary Nvidia driver).
If OP wants proprietary drivers, they need to disable the nouveau kernel driver and install the binary Nvidia drivers. They don't need to worry about everything else as it should handle everything automatically.
Gee! THANK YOU! Someone finally spelled it!
I know it's all done with good heart and intention but, going to the mechanic because your car doesn't start and having to hear all the engineering details on how a combustion engine works can sometime be very frustrating!
Quote:
Petri Kaukasoina
That feature is buggy now in kernel 5.10.4, and that modprobe module option line turns it off.
Just tried, very excitedly as I read it in the other thread currently going on about dual screens stopping with the kernel 5.10.X
No luck for me
however, did going back to the 5.4.XX Linux kernel fix your issue?
(sounds silly but) I have to be honest; i havent tried yet because i am terrified of a terrible no-return system crash and lose all my work (I know this 100% from previous experience on compiling and/or installing kernel).
Back up you say!
Yet still, if things go wrong, i will have to reinstall slackware -current then countless packages, dependencies and adjust all the settings to get things back to normal; and, since I haven't had a couple of days off work yet, I am still hoping that someone will find a solution to this issue or, maybe, gets fixed at the next kernel patch.
If kernel 5.11.X (i read in RC2) will not solve this then I will take my chances.
Just to keep up with my own thread (i have been posting more on other similar threads): latest patch, kernel 5.10.6, has not resolved the glitching/system freeze issue for me.
Still working well with Xrender as Rendering backend Compositor
kernel 5.10.7 does not fix the issue.
Same problem as I change Settings>System Settings>Compositor>Rendering backend to OpenGL. Immediate glitching (didn't wait for system crash and switched back to Xrender straight away). Identical issue on laptop
Hoping for next patch update
I upgraded to the latest kernel 5.10.12 and the problem still persisted so a famous phrase by a famous guy came to mind: "insanity is defined as repeating the same thing over and over expecting different results".
So, i tried something i didn't try before: i tried to install the nVidia legacy driver (NVIDIA-Linux-x86_64-390.141.run). I was led to understand, by searching&reading other posts, that the nVidia legacy driver was designed for older nVidia cards and considering that my card is relatively recent i never gave it too much notice.
Now, guess what happened? not only it installed flawlessly, it also solved the glitching/system freeze that happened before with the Nouveau drivers.
Nevertheless, the problem is not fully resolved. I have double screen on both my laptop and my desktop working well, with no glitching and great image resolution but after a cpl of hours there was a system stall that lasted only a few seconds and then it went back to "normal"; (even though the system didn't crash completely to hard-reset, it automatically disabled the OpenGL drivers and i lost all the desktop effects).
Investigating this further, on Setting>System Settings>Display and Monitor>Compositor this message appeared (screenshot attached).
I tried to look up for more recent version of OpenGL as suggested in the message but, there are aren't any for nVidia.
replying to RadicalDreamer's 1-21-21 post, I am experiencing the same freeze, unrelated to multiple screens or any other "fancy stuff". I started a new thread about it (which I will update in a few minutes). My system uses a VGA cable hookup to my HDMI monitor because an HDMI hookup causes the nouveau kernel driver to seize my audio and I've never spent the time to figure out how to fix that. I have a fully-installed backup partition running the 5.4.40 Slackware kernel from last May and it has always worked fine. So did all the later 5.4.x kernels, but they got lost with the December upgrade to 5.10.x This is the sketchiest Slackware -current I've ever dealt with since the 13.37 days, Many things changed all at once - mesa, xfce4, nouveau, and they seem to all have "issues". You can't run a 1920x1080 monitor without the nouveau kernel driver, and you can't turn off it's acceleration (noaccel=1 nofbaccel=1) without breaking other things, so I too am hoping for better times ahead. My system slows, them freezes entirely about once a day. At one point I thought it was repeatable and tied to mp4 video acceleration, but I was wrong, and will post a retraction on the other thread...
If this goes on, I'll shift to booting the 5.4 kernel and system, and symlink my home directory into the partition containing my current data - since I'd like to get some work done without random freezes all the time. "however" sent me a link to this thread, which boiled down to "try the proprietary driver". From what I've read, switching back and forth opens a whole new can of worms and flames, and I'm not willing to go through that. So much for Patrick's comment in December: "Linus says this is not a scary upgrade" LOL!
replying to RadicalDreamer's 1-21-21 post, I am experiencing the same freeze, unrelated to multiple screens or any other "fancy stuff". I started a new thread about it (which I will update in a few minutes). My system uses a VGA cable hookup to my HDMI monitor because an HDMI hookup causes the nouveau kernel driver to seize my audio and I've never spent the time to figure out how to fix that. I have a fully-installed backup partition running the 5.4.40 Slackware kernel from last May and it has always worked fine. So did all the later 5.4.x kernels, but they got lost with the December upgrade to 5.10.x This is the sketchiest Slackware -current I've ever dealt with since the 13.37 days, Many things changed all at once - mesa, xfce4, nouveau, and they seem to all have "issues". You can't run a 1920x1080 monitor without the nouveau kernel driver, and you can't turn off it's acceleration (noaccel=1 nofbaccel=1) without breaking other things, so I too am hoping for better times ahead. My system slows, them freezes entirely about once a day. At one point I thought it was repeatable and tied to mp4 video acceleration, but I was wrong, and will post a retraction on the other thread...
If this goes on, I'll shift to booting the 5.4 kernel and system, and symlink my home directory into the partition containing my current data - since I'd like to get some work done without random freezes all the time. "however" sent me a link to this thread, which boiled down to "try the proprietary driver". From what I've read, switching back and forth opens a whole new can of worms and flames, and I'm not willing to go through that. So much for Patrick's comment in December: "Linus says this is not a scary upgrade" LOL!
unfortunately, in the case of most "modern" laptops, nVidia comes with it and not much of a specific card choice. Perhaps, if it is a custom built desktop I could see the point (price to pay) for choosing nVidia, even though this issue has been reported with AMD cards and Intel graphics as well as other distros (after kernel update)
unfortunately, in the case of most "modern" laptops, nVidia comes with it and not much of a specific card choice. Perhaps, if it is a custom built desktop I could see the point (price to pay) for choosing nVidia, even though this issue has been reported with AMD cards and Intel graphics as well as other distros (after kernel update)
I attached another screenshot (OpenGL3.1) but it doesn't give any bug-crash option to report.
The Nouveau driver is mostly created from reverse engineering. With NVIDIA people are paying for their temporary binary driver support. Have you tried the latest 460.39 NVIDIA driver? https://www.nvidia.com/en-us/drivers/unix/
The Nouveau driver is mostly created from reverse engineering. With NVIDIA people are paying for their temporary binary driver support. Have you tried the latest 460.39 NVIDIA driver? https://www.nvidia.com/en-us/drivers/unix/
I tried with previous and current kernel from 5.10.4 to 5.10.12. The ./drvr.run from init3 would stop and give 'unable to build nvidia kernel' error. This was reported in several linux forums, not just on slackware distro and with other graphic cards too.
The legacy version of nVidia (also available on the page you linked) solved that problem and completed installation.
Now, perhaps, i could try installing again the nvidia.driver.460.tgz that I compiled and built from alien's repo on top of the legacy kernel&driver but, I am afraid that I will open a "can of worms" as mentioned by someone else.
Quote:
Originally Posted by Rod3775
... switching back and forth opens a whole new can of worms and flames, and I'm not willing to go through that.
if a PhD in computer science with 2 decades of experience with linux wants to avoid that, i certainly copy them
I tried with previous and current kernel from 5.10.4 to 5.10.12. The ./drvr.run from init3 would stop and give 'unable to build nvidia kernel' error. This was reported in several linux forums, not just on slackware distro and with other graphic cards too.
The legacy version of nVidia (also available on the page you linked) solved that problem and completed installation.
Now, perhaps, i could try installing again the nvidia.driver.460.tgz that I compiled and built from alien's repo on top of the legacy kernel&driver but, I am afraid that I will open a "can of worms" as mentioned by someone else.
if a PhD in computer science with 2 decades of experience with linux wants to avoid that, i certainly copy them
To be honest the sbo slackbuilds for the NVIDIA binary stuff scares me. It overwhelms me. If it were me I'd install the 5.4.XX Linux kernel to see if things work with it. If not I'd reinstall and update Slackware64 Current using Slackware Live. Eric does a great job and the Slackware Live I installed for a relative a few years ago was tricked out with slackpkg+ and his alien repository. https://slackware.nl/slackware-live/latest/
Then I'd uninstall nouveau, install nouveau blacklist, and then install the nvidia driver using the .run file. I'm so paranoid after creating symbolic link spaghetti a few years ago that I uninstall the nvidia driver with --uninstall before updating xorg and mesa.
LinuxQuestions.org is looking for people interested in writing
Editorials, Articles, Reviews, and more. If you'd like to contribute
content, let us know.
