current updating and kernel

dubiousa · 01-18-2021, 02:44 AM

Hi guys,
i have a simple question. I really wanna keep my current system new, so i run the update process regulary.
Question - do i have to update all kernels or is it ok to upgrade everything and leave the kernel/module/header version be?

today, i do have kernel 5.10.7
https://slackware.pkgs.org/current/slackware-x86_64/

but my mirror already has kernel-headers 5.10.8

so i realised better leave that 3 packages be and wait till the same version is available. Is this viable?

How often do you update your current system?

Do you update the new kernel every time?
-
EDIT: updated, restarted on kernel/modules/headers 5.10.6 with all new updated packages - seems to work fine.
Thanks!

kgha · 01-18-2021, 02:55 AM

No, you don't have to upgrade the kernel every time a new version is available - at least not in my experience.
I can theoretically imagine some very rare instance where upgrades of other packages are dependent on the latest kernel, but can't remember that it has happened during the five years I've been running current. And should that happen I'm sure it would be stated in the changelog, which should always be checked before upgrading in order to avoid surprises.
I usually upgrade the kernel every fifth release, unless an upgrade solves an important security or stability issue in which case I upgrade immediately.

chrisretusn · 01-18-2021, 09:31 AM

Quote:

Originally Posted by dubiousa

Hi guys,
i have a simple question. I really wanna keep my current system new, so i run the update process regulary.
Question - do i have to update all kernels or is it ok to upgrade everything and leave the kernel/module/header version be?

You don't have to BUT, you should. When you decided to start using -current, you also decide to start using a pre-release version of stable Slackware. In other words you are now a tester.

Quote:

today, i do have kernel 5.10.7
https://slackware.pkgs.org/current/slackware-x86_64/

but my mirror already has kernel-headers 5.10.8

I just finished upgrade to Sun Jan 17 23:48:59 UTC 2021 which includes 5.10.8, I was at 5.10.7

That link you posted is not an official mirror. You should be referencing ChangeLog.txt, not that site.
http://www.slackware.com/changelog/c...php?cpu=x86_64

As for kernel-headers, not sure what you mean, I see all of the 5.10.8 kernel packages listed there.

How to you update? slackpkg?

I use slackpkg with slackpkg+. I also use a local mirror, so updates on my other computers that use -current can be done across my LAN.

Quote:

How often do you update your current system?

On this system, my daily use computer I update anytime there is an update available; unless I am in the middle of a process that can't be interrupted. I have other systems as well I general update right away also. I have one laptop I use for "work", that is updated less frequently but I never let it go to long.

Quote:

Do you update the new kernel every time?

On this system, yes. Just completed the Sun Jan 17 23:48:59 UTC 2021 update. All of my system that have -current installed, I actually don't "upgrade" the kernel (except for huge). I keep two kernels installed. For example before I did my upgrade I had 5.10.6 and 5.10.7 installed. The 5.10.7 kernel was the running kernel, the 5.10.6 was the last working kernel, a fall back kernel. Now the 5.10.7 is the last working kernel and 5.10.8 is the running kernel. The 5.10.6 kernel has been removed. When I boot I have three selections; Slackware64 (default), LastWorking and HugeKernel. Sometimes there is a fourth, TestKernel. I wrote a script that handles the kernel updates for me. Until recently I did that manually.

hitest · 01-18-2021, 10:25 AM

Quote:

Originally Posted by dubiousa

How often do you update your current system?

Do you update the new kernel every time?
-

I update my -current systems as new updates arrive. I apply all updates. I don't think it's a good idea to have a partially up to date version of -current. You're now a beta tester.

dubiousa · 01-19-2021, 01:35 AM

Quote:

Originally Posted by chrisretusn

That link you posted is not an official mirror. You should be referencing ChangeLog.txt, not that site.
http://www.slackware.com/changelog/c...php?cpu=x86_64

Can u please post me the link to official fresh kernel/kernel modules?
Normally i am installing these with installpkg then lilo -v, and i am keeping 3 kernels as of now.

Quote:

Originally Posted by chrisretusn

How to you update? slackpkg?

Yes apart from kernel/modules i am using slackpkg and slackpkg+ with blacklisted kernel/modules.

I have now successfully updated to 5.10.8 and also run a full slackpkg update from "local" mirror in germany - tu-chemnitz.de, as the austrian mirror is not working at all.

Everything seems to work fine, ethernet, Wifi working, BUT the SIM-Data is sadly not working at all since the update. Can u point me to the right package?
I am on a lenovo thinkpad x250 with SIM Card port here.
This is the SIM Module: Sierra Wireless, Inc. Sierra Wireless EM7345 4G LTE

Thanks a lot for extensive answer!

EDIT: OK SIM working now. I took out the sim, tried it in a phone, sticked it back, restarted - works now.. very dubious... BUT it works

Problems will be software unrelated - probably some network problem with the SIM or something as i have never made a call with it..

chrisretusn · 01-19-2021, 03:37 AM

Quote:

Originally Posted by dubiousa

Can u please post me the link to official fresh kernel/kernel modules?
Normally i am installing these with installpkg then lilo -v, and i am keeping 3 kernels as of now.

Awesome on the three kernels. I'd only go with two though, one being the last working kernel, and the new one. If your going to have multiple kernels installed then your /etc/slackpkg/blacklist should include kernel-headers since they are also part of the kernel set of packages. Mostly for consistency. There are not a lot of changes in kernel-header, but it is paired with the kernel.

Code:

kernel-generic
kernel-huge
kernel-modules
kernel-source
kernel-headers

You can pick from a list of official mirrors here.
https://mirrors.slackware.com/mirrorlist/

Quote:

Yes apart from kernel/modules i am using slackpkg and slackpkg+ with blacklisted kernel/modules.

Since you are using slackpkg and slackpkg+, did you know you can use this to get the kernels from your selected mirror defined in /etc/slackpkg/mirrors.

Code:

USEBL=off slackpkg download kernel

OR

Code:

USEBL=off slackpkg download kernel-generic kernel-huge kernel-modules kernel-source kernel-headers

This assumes you have USEBL=on (default) in slackpkgplus.conf. The USEBL=off tells tells slackpkg/slackpkg+ to not use the blacklist. If you use the first one above, you can just unselect kernel-firmware from the dialog list presented. The second will just populate the list with the given kernel packages.

Quote:

Everything seems to work fine, ethernet, Wifi working, BUT the SIM-Data is sadly not working at all since the update. Can u point me to the right package?

I am on a lenovo thinkpad x250 with SIM Card port here.
This is the SIM Module: Sierra Wireless, Inc. Sierra Wireless EM7345 4G LTE

What kernel do you normally run? Huge or generic?

If generic, have you tried using /usr/share/mkinitrd/mkinitrd_command_generator.sh to give you a list of options to use for mkinitrd? This is what /usr/share/mkinitrd/mkinitrd_command_generator.sh -c gives me on my Acer Laptop. I don't have a SIM port though. It may provide the correct module.

Code:

# /usr/share/mkinitrd/mkinitrd_command_generator.sh -c
SOURCE_TREE="/boot/initrd-tree"
CLEAR_TREE="1"
OUTPUT_IMAGE="/boot/initrd.gz"
KERNEL_VERSION="5.10.8"
KEYMAP="us"
MODULE_LIST="xhci-pci:ohci-pci:ehci-pci:xhci-hcd:uhci-hcd:ehci-hcd:hid:usbhid:i2c-hid:hid_generic:hid-asus:hid-cherry:hid-logitech:hid-logitech-dj:hid-logitech-hidpp:hid-lenovo:hid-microsoft:hid_multitouch:jbd2:mbcache:ext4"
LUKSDEV=""
ROOTDEV="/dev/sda2"
ROOTFS="ext4"
RESUMEDEV=""
RAID=""
LVM=""
UDEV="1"
WAIT="1"

I found this thread that might be of interest. http://linux-thinkpad.10952.n7.nabbl...E-td21273.html

Toutatis · 01-19-2021, 04:21 AM

The kernels (huge or generic) may have been installed in special partitions, or changes modify the MBR (when lilo is used, no UEFI). On a SSD it is necessary to use fstrim regularly. How this can be done on special partitions or MBR ?

chrisretusn · 01-19-2021, 05:22 AM

I forgot to mention above.

When using 'slackpkg download' the files are downloaded to their respective /var/cache/packages/slackware64/ package series directory. In the case of kernels 'a', 'd' and 'k'. When done using them to upgrade or install you will have to manually remove them. 'rm /var/cache/packages/slackware64/*/*' will do the job.