[SOLVED] A new kernel for the stable branch and for -current!
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.
Anyone tried 4.9 yet? I've just run through make oldconfig and got my local config file ready for a build. Surprisingly there weren't that many new options to set given how large a changeset 4.9 is.
update:
Code:
test@ws1:~$ uname -a
Linux ws1 4.9.0-local #1 SMP Tue Dec 13 14:25:08 GMT 2016 x86_64 Intel(R) Core(TM) i3-5157U CPU @ 2.50GHz GenuineIntel GNU/Linux
Well, if nothing else. It still boots. Nothing obviously untoward in the kernel log.
Awesome. I've been planning on giving 4.9 a try. I would love to be able to take a Pat config from testing/ but if there aren't that many new options I might just try myself
Supposedly skylake power management has been getting some love which might be good news on my laptop.
If I remember rightly, I started with a fresh "make defconfig" around 4.7 and built on it from there. I'd share it, but it's a heavily trimmed down one so probably more harm then help to anyone else.
Just to be clear, when I said not many new options, I meant from 4.8 to 4.9. If you're starting with a config file earlier than that you'll probably have quite a few options to ponder.
Maybe the missing 4.4.29 files were due to upgrading the kernel files ( which does a removepkg on the old kernel ) ?
Specifically, `upgradepkg kernel-modules` will delete the kernel modules on your running kernel !
As a rule, I apply all the kernel-related packages manually, some via upgradepkg but importantly, some via installpkg.
These packages are upgraded:
Code:
#
# these kernel updates are applied via `upgradepkg`
#
kernel-headers
kernel-firmware
These packages are installed
Code:
#
# these kernel updates are applied via `installpkg`
#
kernel-generic
kernel-huge
kernel-modules
kernel-source
Applying the second set of packages via `installpkg` leaves behind the previous version(s).
After applying the new kernel Packages, I ( usually but not always ) make a new initrd file and fix lilo.conf for the new kernel(s) ( I include the full vmlinuz file name in my lilo.conf file so that I can have multiple versions ) and reboot.
Note that for the Generic Kernels, I also generate versioned initrd files. Once again, so that I can keep an old one 'just in case'.
See the -a and -o options on /usr/share/mkinitrd/mkinitrd_command_generator.sh
Code:
#
# in lilo.conf, my image = lines look like this:
#
image = /boot/vmlinuz-huge-4.4.29
#
# instead of referencing the symlinks:
#
# NOT THIS: image = /boot/vmlinuz-huge
#
# AND ESPECIALLY NOT THIS: image = /boot/vmlinuz
#
# this way I can be sure of which kernel I am booting and I can always boot an 'old one'
#
After all this, once I see that the new version is a keeper, I eventually go back and `removepkg` the older version(s) in the `installpkg` list and remove any old initrd files 'by hand'.
Location: Northeastern Michigan, where Carhartt is a Designer Label
Distribution: Slackware 32- & 64-bit Stable
Posts: 3,541
Rep:
Quote:
Originally Posted by kjhambrick
tronayne --
Maybe the missing 4.4.29 files were due to upgrading the kernel files ( which does a removepkg on the old kernel ) ?
I kind of figured that, just didn't know what it was and it was only on the system that has VirtualBox on it (so, I rebuilt VirtualBox just for the heck of it). I also rebuild some SBo packages (I have a shell program that does that) just to take advantage of kernel updates that might be handy.
I learned a long time ago to trust Pat and the developers; I don't mess with initrd, just lilo on un-fooled-around-with Slackware stable; when I install a new release I do a full install (everything), accept the default kernel and do some editing in [I]/etc/I] from a backup of the entire /etc directory, either merging or editing as I deem necessary. Everything works as expected.
Doing the kernel updates (two of 'em so far in 14.2) is pretty much the same -- upgradepkg and be done with it (I do not fiddle with the kernel, quit doing that about 10 years ago). I have to spread the kernel (and other) updates across multiple servers and, because every system is configured identically, it's a simple scp from the main system to the others and ssh into them and run upgradepkg.
It works for me, no troubles, no tweaking, no nothing.
Thanks for the input -- one of these days I might just have to fiddle and it's nice to know how.
How did you get your sleep/hibernation to work? I have been struggling with it.
Sleep (suspend to ram) works out of the box on the laptop used, ditto for hibernate but you need to set the resume kernel parameter as needed in Grub/Lilo config (resume=/dev/sdax, replace sdax with your resume partition).
I kind of figured that, just didn't know what it was and it was only on the system that has VirtualBox on it (so, I rebuilt VirtualBox just for the heck of it). I also rebuild some SBo packages (I have a shell program that does that) just to take advantage of kernel updates that might be handy.
I learned a long time ago to trust Pat and the developers; I don't mess with initrd, just lilo on un-fooled-around-with Slackware stable; when I install a new release I do a full install (everything), accept the default kernel and do some editing in [I]/etc/I] from a backup of the entire /etc directory, either merging or editing as I deem necessary. Everything works as expected.
Doing the kernel updates (two of 'em so far in 14.2) is pretty much the same -- upgradepkg and be done with it (I do not fiddle with the kernel, quit doing that about 10 years ago). I have to spread the kernel (and other) updates across multiple servers and, because every system is configured identically, it's a simple scp from the main system to the others and ssh into them and run upgradepkg.
It works for me, no troubles, no tweaking, no nothing.
Thanks for the input -- one of these days I might just have to fiddle and it's nice to know how.
You're welcome tronayne.
I agree with you about the HUGE Kernel and not fooling with an initrd, especially lately with the unusual Kernel churn the past few months.
This is kind of random, but I didn't want to start a new thread on it.
In case someone is using the 4.8 series kernel and VirtualBox from SBo, you may have noticed that virtualbox-kernel does not compile. I made a SlackBuild with some patches to fix that, which you can get here. Other than applying the patches, only minor things like the tag and build number have been changed from the SBo version. Of course, I'm aware that there are other ways to run VirtualBox without resorting to this fix, but I thought I'd mention it just in case someone else ran into the same issue. It may work with 4.9 too, but I haven't tried.
Distribution: Slackware64-current on Thinkpad Carbon X1
Posts: 264
Rep:
Quote:
Originally Posted by kjhambrick
tronayne --
Maybe the missing 4.4.29 files were due to upgrading the kernel files ( which does a removepkg on the old kernel ) ?
Specifically, `upgradepkg kernel-modules` will delete the kernel modules on your running kernel !
As a rule, I apply all the kernel-related packages manually, some via upgradepkg but importantly, some via installpkg.
These packages are upgraded:
Code:
#
# these kernel updates are applied via `upgradepkg`
#
kernel-headers
kernel-firmware
These packages are installed
Code:
#
# these kernel updates are applied via `installpkg`
#
kernel-generic
kernel-huge
kernel-modules
kernel-source
Applying the second set of packages via `installpkg` leaves behind the previous version(s).
After applying the new kernel Packages, I ( usually but not always ) make a new initrd file and fix lilo.conf for the new kernel(s) ( I include the full vmlinuz file name in my lilo.conf file so that I can have multiple versions ) and reboot.
Note that for the Generic Kernels, I also generate versioned initrd files. Once again, so that I can keep an old one 'just in case'.
See the -a and -o options on /usr/share/mkinitrd/mkinitrd_command_generator.sh
Code:
#
# in lilo.conf, my image = lines look like this:
#
image = /boot/vmlinuz-huge-4.4.29
#
# instead of referencing the symlinks:
#
# NOT THIS: image = /boot/vmlinuz-huge
#
# AND ESPECIALLY NOT THIS: image = /boot/vmlinuz
#
# this way I can be sure of which kernel I am booting and I can always boot an 'old one'
#
After all this, once I see that the new version is a keeper, I eventually go back and `removepkg` the older version(s) in the `installpkg` list and remove any old initrd files 'by hand'.
Clear as mudd ?
-- kjh
With a bit of polishing this should be a sticky. Pretty much the same way I do it after needing to read countless threads to figure it out.
LinuxQuestions.org is looking for people interested in writing
Editorials, Articles, Reviews, and more. If you'd like to contribute
content, let us know.