The Latest Kernel Release.

tauon · 01-06-2022, 06:40 AM

Quote:

Originally Posted by Ilgar

5.15.12 has been a good update for me. With earlier 5.15 kernels my netbook's screen was going black uopn resume from suspend. You could ssh into the machine but the screen would not wake up. This was fixed in 5.15.12.

Same with mine R50p, but only in an X11 session, in fb console everything was fine.

cwizardone · 01-08-2022, 11:31 AM

Quote:

Originally Posted by cwizardone

Quote:

Originally Posted by Jan K. View Post
"25,288 files changed, 178,024 insertions(+), 74,720 deletions(-)"

Quite breathtaking... https://lore.kernel.org/lkml/YdIfz+L...gmail.com/T/#u

See posts #4121 and #4123, above.

Patches for this are starting to show up at the "Linux-Kernel Archive by Thread."
If and when they are incorporated into the kernel.... is another matter.

Edit in: Just found this news story on the project, https://www.phoronix.com/scan.php?pa...nel-Headers-v2

cwizardone · 01-09-2022, 05:17 PM

5.16.0

The newest stable kernel, version 5.16.0, has been released.

The tarball, https://git.kernel.org/pub/scm/linux...ux-5.16.tar.gz

Mr. Torvalds' announcement, http://lkml.iu.edu/hypermail/linux/k...1.1/00613.html

marav · 01-09-2022, 05:43 PM

Quote:

Originally Posted by cwizardone

5.16.0

The newest stable kernel, version 5.16.0, has been released.

The tarball, https://git.kernel.org/pub/scm/linux...ux-5.16.tar.gz

Mr. Torvalds' announcement, http://lkml.iu.edu/hypermail/linux/k...1.1/00613.html

Build & running pretty well here!

Code:

blackstar :: ~ » uname -srvm
Linux 5.16.0 #1 SMP PREEMPT Mon Jan 10 00:24:38 CET 2022 x86_64

cwizardone · 01-09-2022, 09:23 PM

Quote:

Originally Posted by marav

Build & running pretty well here!........

Ditto.
Other than the 7 second blank screen after the BIOS check, the 5.16.0 kernel is working as it should with the Nvidia-470.94 driver and VirtualBox-6.1.30.

3rensho · 01-10-2022, 12:28 AM

Running as expected. Nothing untoward in the logs

cwizardone · 01-10-2022, 05:12 AM

Year 2022, Round 02.

Another batch of updates has been scheduled for release on Wednesday, 12 January 2022, at approximately 07:00, GMT. If no problems are found while testing the release candidates, they might be available sometime on Tuesday (depending on your time zone).

The details:

5.15.14-rc1, with 72 patches, http://lkml.iu.edu/hypermail/linux/k...1.1/00963.html
Contains 9 drm/amd patches and 1 drm/amd revert.

5.10.91-rc1, with 43 patches, http://lkml.iu.edu/hypermail/linux/k...1.1/00916.html

5.4.171-rc1, with 34 patches, http://lkml.iu.edu/hypermail/linux/k...1.1/00893.html

4.19.225-rc1, with 21 patches, http://lkml.iu.edu/hypermail/linux/k...1.1/00888.html

4.14.262-rc1, with 22 patches, http://lkml.iu.edu/hypermail/linux/k...1.1/00865.html

4.9.297-rc1, with 21 patches, http://lkml.iu.edu/hypermail/linux/k...1.1/00850.html

4.4.299-rc1, with 14 patches, http://lkml.iu.edu/hypermail/linux/k...1.1/00813.html

AlleyTrotter · 01-10-2022, 09:13 AM

5.16.0 compiled and running without issue on Slackware64-14.2.
HTH
john

cwizardone · 01-11-2022, 06:50 AM

Kernel updates 4.19.225, 4.14.262, 4.9.297 and 4.4.299 are now available at, https://www.kernel.org/

The change logs,

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

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

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

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

cwizardone · 01-11-2022, 08:29 AM

Kernel updates 5.15.14, 5.10.91 and 5.4.171 are now available at, https://www.kernel.org/

The change logs,

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

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

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

kjhambrick · 01-11-2022, 09:41 AM

This commit to 5.15.14 looks interesting:

Code:

commit 19070d812e130c035eca07b9af9ed7867cd9df96
Author: Len Brown <len.brown@intel.com>
Date:   Sun Jan 9 13:11:37 2022 -0500

    Revert "drm/amdgpu: stop scheduler when calling hw_fini (v2)"
    
    commit df5bc0aa7ff6e2e14cb75182b4eda20253c711d4 upstream.
    
    This reverts commit f7d6779df642720e22bffd449e683bb8690bd3bf.
    
    This bisected regression has impacted suspend-resume stability
    since 5.15-rc1. It regressed -stable via 5.14.10.
    
    Link: https://bugzilla.kernel.org/show_bug.cgi?id=215315
    Fixes: f7d6779df64 ("drm/amdgpu: stop scheduler when calling hw_fini (v2)")
    Cc: Guchun Chen <guchun.chen@amd.com>
    Cc: Andrey Grodzovsky <andrey.grodzovsky@amd.com>
    Cc: Christian Koenig <christian.koenig@amd.com>
    Cc: Alex Deucher <alexander.deucher@amd.com>
    Cc: <stable@vger.kernel.org> # 5.14+
    Signed-off-by: Len Brown <len.brown@intel.com>
    Signed-off-by: Linus Torvalds <torvalds@linux-foundation.org>
    Signed-off-by: Greg Kroah-Hartman <gregkh@linuxfoundation.org>

JayByrd · 01-11-2022, 03:48 PM

5.16.0 compiled and running fine on Slackware64-current w/ nvidia-legacy304. (After squaring away the "5.16" vs. "5.16.0" conflict, that is.

)

Aeterna · 01-12-2022, 08:48 AM

Quote:

Originally Posted by JayByrd

5.16.0 compiled and running fine on Slackware64-current w/ nvidia-legacy304. (After squaring away the "5.16" vs. "5.16.0" conflict, that is.

)

What is the issue between 5.16 vs 5.16.0

Toutatis · 01-12-2022, 10:33 AM

Quote:

Ditto.
Other than the 7 second blank screen after the BIOS check, the 5.16.0 kernel is working as it should with the Nvidia-470.94 driver and VirtualBox-6.1.30.

I have this also, with 5.15.4 (about 6 seconds), but the display of time also begins later (with [ 6.something]). but 'dmesg' begins with [ 0.000000] Linux version 5.15.4....

JayByrd · 01-12-2022, 10:59 AM

Quote:

Originally Posted by Aeterna

What is the issue between 5.16 vs 5.16.0

Merely an annoyance of naming conventions--it happens at every "point-zero" release.

The kernel-source is installed to "/usr/src/linux-5.16" while the modules are installed to "/lib/modules/5.16.0".

The "conflict" I referred to in my post was merely my forgetting about that when I went to build the nVidia kernel module. I passed KERNEL=5.16 to the SlackBuild and it built successfully. However, when I rebooted: "nvidia module not found"! That's because the system was looking in "/lib/modules/5.16.0".

I suppose I could alter the SlackBuild to test for a "point-zero" release, and then have it create two different strings for the kernel-source directory and the modules directory. But that seems like way too much work for something that happens only rarely.

One can either rename the source directory or just create a symlink in /usr/src/: linux-5.16.0 -> linux-5.16, and then call the nvidia SlackBuild w/ KERNEL=5.16.0