The Latest Kernel Release.

PROBLEMCHYLD · 12-20-2020, 10:51 PM

I have the latest firmware.

PROBLEMCHYLD · 12-21-2020, 12:14 AM

All kernels above 5.5, 5.6, 5.7, 5.8, 5.9, 5.10 etc... breaks qBittorrent 3.3.16 on Slackware 14.2 64bit. 5.4.xx is the only one that still works.

denydias · 12-21-2020, 04:23 AM

Quote:

Originally Posted by cwizardone

See posts #2784 and #2790 in this thread.
Since post #2790, there have been three or four new releases. Currently, I have Test Build Linux 64-bit, 6.1.x revision 141968, installed and it works just fine.
We will probably see a new release within the next business day or two.

https://www.virtualbox.org/wiki/Testbuilds

Sure, @cwizardone! I forgot to check these VirtualBox test builds. Thanks for pointing that out.

Now that I've already applied the patch and the modules compiled fine with a release version, I'll wait for an official release including it.

cwizardone · 12-21-2020, 06:47 AM

Kernel updates 5.10.2, 5.9.16 and 5.4.85 are now available at

https://www.kernel.org/

The change logs,

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

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

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

chrisretusn · 12-21-2020, 07:08 AM

Quote:

Originally Posted by cwizardone

Currently, I have Test Build Linux 64-bit, 6.1.x revision 141968, installed and it works just fine.
https://www.virtualbox.org/wiki/Testbuilds

Same results.

andrew.46 · 12-21-2020, 07:41 PM

Quote:

Originally Posted by chrisretusn

Same results.

This version of VirtualBox (same as cwizardone):

Code:

andrew@ilium~$ vboxmanage --version
6.1.17r141968
andrew@ilium~$

is working fine with Kernel 5.10.1 on my 64bit -current system...

Daedra · 12-21-2020, 07:55 PM

Quote:

Originally Posted by Daedra

success! Only caveat is that simply adding "CONFIG_NVME_HWMON=y" does not work. I misread the depends line in the kernel config. For this to work it requires "NVME_CORE [=m]=y && HWMON [=m]=y || NVME_CORE [=m]=m && HWMON [=m]" in the kernel config. So either hardware monitoring support has to be static and not a module. Or NVME_CORE needs to be a module and not static. For my experiment I made hardware monitoring support a module instead of static. After I was done I got a interesting surprise, not only did I have nvme temperature support but it was also showing the temperature of my wifi adapter. That doesn't matter since I am about to disable it in the bios now that my Intel i225-V works properly.

Well I don't know what changed between kernel 5.10.1 and 5.10.2, but now hardware monitoring support needs to be static and not a module to get nvme hardware support. I ran "make xconfig" and the option for nvme hardware monitoring is visible but can't be enabled until hardware monitoring support is changed from a module to static. I made another request, hopefully Pat will enable this on the next kernel release.

cwizardone · 12-21-2020, 08:03 PM

The 5.9.y kernel series has been designated, End Of Life.

Quote:

Linux 5.9.16
From: Greg Kroah-Hartman
Date: Mon Dec 21 2020 - 08:25:14 EST

I'm announcing the release of the 5.9.16 kernel.

All users of the 5.9 kernel series must upgrade.

NOTE, this is the LAST 5.9.y kernel to be released unless something
really odd happens. Please move to 5.10.y at this point in time, the
5.9.y branch is now end-of-life...........

thanks,

greg k-h

------------

The full announcement can be found at, http://lkml.iu.edu/hypermail/linux/k...2.2/03659.html

andrew.46 · 12-21-2020, 08:48 PM

Quote:

Originally Posted by PROBLEMCHYLD

All kernels above 5.5, 5.6, 5.7, 5.8, 5.9, 5.10 etc... breaks qBittorrent 3.3.16 on Slackware 14.2 64bit. 5.4.xx is the only one that still works.

I use an AppImage of qBittorrent to stay clear from system turbulence on -current. Is this an option for you?

GazL · 12-22-2020, 04:05 AM

Quote:

Originally Posted by cwizardone

The 5.9.y kernel series has been designated, End Of Life.
The full announcement can be found at, http://lkml.iu.edu/hypermail/linux/k...2.2/03659.html

That kernel-branchicide seems sooner than usual.

PROBLEMCHYLD · 12-22-2020, 04:29 AM

Quote:

Originally Posted by andrew.46

I use an AppImage of qBittorrent to stay clear from system turbulence on -current. Is this an option for you?

Thanks, I just downgraded to 5.4.85 and everything is working. Since the newer kernels doesn't offer much unless using new hardware, I don't see the purpose. I like to test and tinker with new things but if stuff is gonna break, I'll stay on a stable release. Not sure if the Bluetooth was fixed in the 5.10.2 but I haven't tried it.

mario · 12-22-2020, 04:40 AM

https://www.kernel.org/category/releases.html

It looks like 5.4 will outlive 5.10, by a lot. I guess we will be seeing Slackware 15.1 fairly quickly if 5.10 gets picked for 15.0 :P

PROBLEMCHYLD · 12-22-2020, 04:42 AM

Wow!!! 3 years is a big difference...

LuckyCyborg · 12-22-2020, 05:04 AM

Quote:

Originally Posted by mario

https://www.kernel.org/category/releases.html

It looks like 5.4 will outlive 5.10, by a lot. I guess we will be seeing Slackware 15.1 fairly quickly if 5.10 gets picked for 15.0 :P

I do not think that the life of a LTS kernel matters.

In the experience, after no more than one year a LTS release becomes obsolete.

And also the experience demonstrated that 5.4.x works quite well with Slackware 14.2

So, if Mr. Volkerding wants to maintain the Slackware 15.0 kernel(s) for 8 years, all he have to do is to update them. Probably with the LTS kernels, waiting for 20 or something patch releases...

In the end, would be no differences, other that the stable release will get new hardware support. Which probably is better, because in 4 years the hardware evolves a lot.

cwizardone · 12-22-2020, 06:35 AM

Quote:

Originally Posted by mario

https://www.kernel.org/category/releases.html

It looks like 5.4 will outlive 5.10, by a lot. I guess we will be seeing Slackware 15.1 fairly quickly if 5.10 gets picked for 15.0 :P

See post #2786 in this thread.

Quote:

Originally Posted by bassmadrigal

It's always announced with a 2 year LTS support and then they usually extend it to 6 years about a year into the LTS cycle.