Kernel updates 5.5.15, 5.4.30, 4.19.114, 4.14.175 and 4.9.218 are now available at,

https://www.kernel.org/

The change logs,

https://cdn.kernel.org/pub/linux/ker...angeLog-5.5.15

https://cdn.kernel.org/pub/linux/ker...angeLog-5.4.30

https://cdn.kernel.org/pub/linux/ker...geLog-4.19.114

https://cdn.kernel.org/pub/linux/ker...geLog-4.14.175

https://cdn.kernel.org/pub/linux/ker...ngeLog-4.9.218

It's already pretty crazy what's going on!

1 members found this post helpful.

Kernel update 4.4.218 is now available at,

https://www.kernel.org/

The change logs,

https://cdn.kernel.org/pub/linux/ker...ngeLog-4.4.218

It doesn't seem to be available yet as a DUSK kernel (32-bit only!).

1 members found this post helpful.

I've not looked at the script so I don't know how often it searches for updates. If the script still works, it will pick up the changes and generate a new kernel... eventually.

Here you go,
The 32-bit version of Dave's Unofficial Slackbuilt Kernel update for the 4.4.y series can be found at, https://dusk.idlemoor.tk/linux-4.4/i686/

So I was just a little bit too early, it came to be available about an hour later.

1 members found this post helpful.

5.4.30 seems to be working well on 14.2.

1 members found this post helpful.

Year 2020, Round 23

Another batch of kernel updates has been scheduled for release Thursday, 09 April 2020, at approximately 10:00, GMT.

If no problems are found while testing the release candidates, they might be available sometime Wednesday (depending on your time zone).

There will be 29 patches in the 5.6.3 update, 46 in 5.5.16 and 36 in the 5.4.31 update.

The details:

5.6.3-rc1, http://lkml.iu.edu/hypermail/linux/k...4.0/06509.html

5.5.16-rc1, http://lkml.iu.edu/hypermail/linux/k...4.0/06474.html

5.4.31-rc1, http://lkml.iu.edu/hypermail/linux/k...4.0/06537.html

Nvidia has released a new long term driver to fix compatibility problems with the 5.6 kernel.
Please see this post, https://www.linuxquestions.org/quest...ml#post6108762

A second round of release candidates has been announced.

There will be 30 patches in the 5.6.3 update, 48 in 5.5.16 and 38 patches in the 5.4.31 update.

5.6.3-rc2, http://lkml.iu.edu/hypermail/linux/k...4.0/06938.html

5.5.16-rc2, http://lkml.iu.edu/hypermail/linux/k...4.0/06936.html

5.4.31-rc2, http://lkml.iu.edu/hypermail/linux/k...4.0/06929.html

Kernel 5.6.2 running fine on Slackware -current with NVidia 440.82. However VirtualBox 6.1.4 barfs on the new kernel, a known problem noted here with a fix in the pipeline...

1 members found this post helpful.

download 6.1.5 from testing

outstanding issue is with the choice between having the ability of working clipboard between host and clients or client to client and vboxsf:

5.6.x adds support for vboxsf. If you compile it, you have to remove VirtualBoxGuestAddtions otherwise vboxsf module will not work at all and then you will loose clipboard support. Removing VirtualBoxGuestAddtions will keep vboxsf kernel functionality.

On the other hand, if you do not compile kernel vboxsf then you will loose support for vboxsf kernel and Oracle (VBox module will not compile generating an error) but clipboard will work.
Personally I opted for this option as I also have enabled smb and nfs so file transfer between vm host and client works and clipboard functionality is preserved

3 members found this post helpful.

Thanks, that did the trick! All now working fine: Kernel 5.6.2, NVidia blob 440.82 and VirtualBox 6.1.5r136807

2 members found this post helpful.

I was unhappy with how long Virtualbox is taking to resolve this (they've only known about it all month before the Linux 5.6 release) so I switched to Qemu and I'm not looking back. That's much more sustainable in the long run, not needing third party, out of tree kernel modules. I'm using Qemu with the Spice libraries and I even have decent drivers in my Windows 7 guest. (spice guest tools...qxl video driver, virtio storage, accelerated virtio-net-pci etc.)

Not at all onerous to compile Qemu either. (I don't compile the VirtualBox application, build needs too much crap that I don't want to have)

P.S. Must be new build of VirtualBox 6.1.5 because it didn't work at the time I tried. Nor did 6.1.97 dev snapshot.

3 members found this post helpful.