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.
Distribution: Slackware64-current with "True Multilib" and KDE4Town.
Posts: 9,094
Original Poster
Rep:
With all the changes being incorporated into the 5.7 kernel, it appears it will be a major release.
Among many other improvements,
Quote:
Open-Source NVIDIA "Nouveau" Driver Should Trip Less Often On Some GPUs With Linux 5.7
Written by Michael Larabel in Nouveau on 8 April 2020 at 07:17 AM EDT
Distribution: VM Host: Slackware-current, VM Guests: Artix, Venom, antiX, Gentoo, FreeBSD, OpenBSD, OpenIndiana
Posts: 1,008
Rep:
Quote:
Originally Posted by gdiazlo
Do you use sources/k SlackBuilds to try our new kernels? or download/install in /usr/src/linux and the usual stuff?
I use sources downloaded from kernel.org, installed in /usr/src and copy config from previous working kernel. I keep old working kernel until I am sure that new kernel works well.
I use sources downloaded from kernel.org, installed in /usr/src and copy config from previous working kernel. I keep old working kernel until I am sure that new kernel works well.
I pretty much do something similar, except I don't delete my old kernels out of sheer laziness. I currently have 18 kernels in there, ranging from 4.13.7 to 5.4.30. I must've deleted some at some point since I had a 4.4.x kernel installed when I first installed 14.2 and I know I ran the 4.8 and 4.9 kernels before moving on.
I just looked and I have almost 40GB used in my /usr/src/ folder. Maybe I should clear some up since I only have 13GB free on my root partition (but then I have 113GB in my /tmp/, so I have plenty of places I can slim down to clear up more space).
Do you use sources/k SlackBuilds to try our new kernels? or download/install in /usr/src/linux and the usual stuff?
I follow the latest 'stable' kernel from kernel.org but usually a few point upgrades in from a new version release and I also wait out any larger problems that surface. This is my working kernel, I install it manually and also remove it manually. This has always kept me out of trouble and I have the stock -current kernel upgrades as backup; I usually will load up one of these installed kernels to test before I upgrade the working kernel...
Thanks all for your feedback, I tried to use the sources/k slackbuilds to try the 5.6.3 kernel. It was a matter of generating good kernel configurations for generic and huge to my platform (x86_64) and the packages were generated correctly.
The migration from the 5.4.31 config to the 5.6.3 config was more or less strightforward. What I did was:
- uncompress the kernel sources,
- copy from sources/k/kernel-configs/generic-5.4.31-x64 config to /tmp/linux-5.6.3/.config
- run make oldconfig
- set the new changes (new modules mostly)
- copy the new generated .config file as a new sources/k/kernel-config/generic-5.6.3-x64
- repeat the process for config-huge configuration
- run the build all kernel scripts. If this script gets stuck, it might be trying to do a make oldconfig without a terminal, so it is waiting for user input, and the user can't see it. That would mean the generated configuration is incorrect, try to run the make oldconfig by hand and copying the generated config again.
Distribution: Slackware64-current with "True Multilib" and KDE4Town.
Posts: 9,094
Original Poster
Rep:
Year 2020, Round 24
Another batch of kernel updates has been scheduled for release Monday, 13 April 2020, at approximately 12:00, GMT.
If no problems are found while testing the release candidates, they might be available sometime on Sunday (depending on your time zone).
There will be 38 patches in the 5.6.4 update, 44 in 5.5.17, 41 in 5.4.32, 54 in 4.19.115, 38 in 4.14.176, 32 in 4.9.219 and, finally, 29 patches in the 4.4.219 update.
Here are a couple of articles about the new features to be found in the 5.7 kernel, [...]
Exciting for me will be the new and improved exFAT file-system implementation. I have a fancy high speed sdcard in my digital camera and I was excited enough when the original support landed in the kernel. Now I have an actual good reason to track the newest kernel
Distribution: Slackware64-current with "True Multilib" and KDE4Town.
Posts: 9,094
Original Poster
Rep:
Have you tried the 5.7-rc1 kernel? Were you able to boot?
Quote:
Linux 5.7 Git Restores The Ability To EFI Boot Following Fallout In 5.7-rc1
If you tried out Linux 5.7-rc1 at the start of the week you may have found your system unbootable if using EFI... Fortunately, those EFI fixes have now been merged several days later.
LinuxQuestions.org is looking for people interested in writing
Editorials, Articles, Reviews, and more. If you'd like to contribute
content, let us know.