I've been on 418.30 and 4.4.172 for about a week, and nothing out of the ordinary.

1 members found this post helpful.

I am using the new 418.30 with the latest update of 64-current and it works fine.
I typically run 3 monitors one of which is 4K sometimes and the performance has been satisfactory,
recognizing that I am pushing the envelope.

1 members found this post helpful.

Public Service Announcement
I finally worked out the glitch with nvidia-418.30-BETA. This was a weird one since other systems did not have any issues. Yes, I do these things so you don't have to (to paraphrase the late Jerry Pournelle). My main system:

• Slackwarew64 14.2 multilib kernel 4.4.172 (hnudred-add SBo and custom packages)
• i7-6850K CPU @ 3.60GHz, 32GB DDR4 RAM, 4TB HD over 5 drives
• Nvidia 418.30 via Slackbuilds.org (why, of course)
• EVGA GTX 1060, xscreen0, monitor0
• Gigabyte GTX 660, xscreen1, monitor1
• Xfce desktop, BOINC (distributed science processing)

Symptoms:

• After clean boot, system becomes unresponsive after several hours.
• Mouse cursor freezes (especially when moving from xscreen0 to xscreen1).
• applications launch slow, X.org random freezes, xscreensaver very slow to respond.
• X.org server pegs 1-3 physical processors for no apparent reason, X slow, slow to shut down, eventually X freezes completely.
• No issues in console (before startx) or via remote ssh.
• after X freezes, can ssh in and do the typical normal activities
• gkrellm randomly closes
• no log entries of note.

Solution: remove GTX 660, and configure GTX 1060 to run both monitors. System has been stable for 8+ hrs now.

I have not the foggiest idea, why after ages running 2 GPUs, each with it sown monitor, and the nvidia blob, the 418.30-BETA driver is unstable. I'm just going to throw this out there in the hopes that it does some good.

5 members found this post helpful.

I'm not holding much hope for us GT 610 users. The, apparently monthly, driver updates stopped in August of last year, with 390.87, and it doesn't look like they're doing beta drivers for that branch.

(I so wish there was an RSS/Atom feed for their releases…)

Update: Just noticed kingbeowolf's relevant post.

There is a patch to build Legacy 390 series drivers against kernel 4.19.

1 members found this post helpful.

If I may ask, when will that hit Slackbuilds?

I've been hit twice with the Nouveau fifo: LB_ERROR bug while using Blender.

Every Friday/Saturday or so. The fix is in!

1 members found this post helpful.

Apparently no chance here to have my GT210 working with this kernel. Has anyone a link to the previous kernel packages, please?

Honestly, I'd suggest just building your own.

https://docs.slackware.com/howtos:sl...kernelbuilding

Thank you, I know how to build the kernel by myself. My question was about a link, just to downgrade to the old kernel, because I don't have the time to build and test

1 members found this post helpful.

Here's a site with a lot of older packages; perhaps you'll find what you need here. Hope this helps!

1 members found this post helpful.

connection timeout :-(
thanks anyway

You're welcome. I don't know if there are any mirrors for this kind of stuff, but it was the only one I could find.

Something I am trying to get my head around - is this change not affecting other distros that run 4.4.169 upwards or 4.19.*? They all have to build their packages, right? I've found a number of hits on Google about it from last year, but I'd have expected it to be a broader problem.

I'm hoping there's a fix for the 390.* driver as I have a workstation with an NVS 315; it's only three years old but is already considered legacy.

2 members found this post helpful.

Many distros don't provide vanilla kernel packages, so they may modify their kernel to prevent this issue from showing. I know that Arch requires the 4.20.x kernel to run the 390 driver (that's what I usually check when I run into problems with SlackBuilds I maintain).