The Latest Kernel Release.

enorbet · 02-05-2021, 07:46 PM

I'm very much liking 5.10.x kernels and presently using 5.10.12 on latest Current. It's so good I tried installing it on 14.2 but it won't compile with the older gcc on 14.2. So I copied /usr/src/linux-5.10.12, lib/modules/5.10.12 (and firmware) and all the /boot files and it runs great BUT because of the wide variation in gcc I can't either rebuild 5.10.12 or install the nvidia driver. I may just have to resort to nouveau since older kernels and firmware don't recognize the new wifi hardware and a few other items on my Z490 board.

AlleyTrotter · 02-05-2021, 09:32 PM

Quote:

Originally Posted by enorbet

I'm very much liking 5.10. kernels and presently using 5.10.12 on latest Current. It's so good I tried installing it on 14.2 but it won't compile with the older gcc on 14.2. So I copied /usr/src/linux-5.10.12, lib/modules/5.10.12 (and firmware) and all the /boot files and it runs great BUT because of the wide variation in gcc I can't either rebuild 5.10.12 or install the nvidia driver. I may just have to resort to nouveau since older kernels and firmware don't recognize the new wifi hardware and a few other items on my Z490 board.

compiles and runs fine using the kernel config in Slackware64-current iso
slackware64/source/k/config-huge-5.10.13x64. ( I use huge kernel)
This has worked with the entire 5.10 series on Slackware64-14.2
I can't offer any more help than:
Make any backups or copy any kernels you wish to save

Code:

cp -pv slackware64/source/k/kernel-huge-5.10.?.x64 /usr/src/linux-5.10/.config
make oldconfig
make
make modules_install
cp -pv .config /boot/config-5.10.13
cp -pv System.map /boot/System.map-5.10.13
cp -pv arch/x86/boot/bzimage /boot/vmlinuz-5.10.13
# include next line if you use UEFI
cp -pv arch/x86/boot/bzimage /boot/efi/EFI/SLACKWARE/vmlinuz-5.10.13

adjust lilo or elilo.conf as you always do
reboot into your new kernel

HTH
john

Aeterna · 02-06-2021, 10:36 AM

Quote:

Originally Posted by enorbet

I'm very much liking 5.10.x kernels and presently using 5.10.12 on latest Current. It's so good I tried installing it on 14.2 but it won't compile with the older gcc on 14.2. So I copied /usr/src/linux-5.10.12, lib/modules/5.10.12 (and firmware) and all the /boot files and it runs great BUT because of the wide variation in gcc I can't either rebuild 5.10.12 or install the nvidia driver. I may just have to resort to nouveau since older kernels and firmware don't recognize the new wifi hardware and a few other items on my Z490 board.

I wonder if you tried to install 5.10.x Slackware-current kernels (download packages and install?).
Your problem with nvidia will not be alleviated because you will have still different gcc versions used for kernel and nvidia modules of course but this may be easier to mantain if you decide to use nouveau for your nvidia video.
I use nouveau module and it works pretty well (I am not a gamer).

Quote:

make oldconfig

will not work because (as you mentioned) latest kernels refuse to compile with older versions of gcc and oldconfig is just a way to copy previous version of config file.
personally I don't see a point of recompiling default Slackware kernels.

AlleyTrotter · 02-06-2021, 11:41 AM

Quote:

Originally Posted by Aeterna

latest kernels refuse to compile with older versions of gcc and oldconfig is just a way to copy previous version of config file.
personally.

First copy the new (current) config to .config then make oldconfig. Probably should have included that in my answer. I think i did say which kernel config you should use.
You are wrong about older versions of GCC.

Code:

/usr/bin/gcc --version
gcc (GCC) 5.5.0
Copyright (C) 2015 Free Software Foundation, Inc.
This is free software; see the source for copying conditions.  There is NO
warranty; not even for MERCHANTABILITY or FITNESS FOR A PARTICULAR PURPOSE.

head /usr/src/linux-5.10/.config
#
# Automatically generated file; DO NOT EDIT.
# Linux/x86_64 5.10.13 Kernel Configuration
#
CONFIG_CC_VERSION_TEXT="gcc (GCC) 5.5.0"
CONFIG_CC_IS_GCC=y
CONFIG_GCC_VERSION=50500
CONFIG_LD_VERSION=201827250000
CONFIG_CLANG_VERSION=0
CONFIG_LLD_VERSION=0

Slackware64-14.2 compiles and runs the 5.10 series just fine no problems.
I have compiled every one of them without problems on 14.2
HTH
john

enorbet · 02-06-2021, 05:15 PM

Perhaps my problems stem from never using generic config (I dislike initrd) and using huge for a few minutes only before I custom build my own config. This rebuilding is important to me for my main system because I use it as a DAW and also game, so top performance in realtime is essential. 14.2 always booted and installed proprietary nvidia drivers just fine on drop in kernels from Current up until 5.10.2 and beyond. I'm coming to terms with the fact that Current has become my Main and I don't require extreme performance from 14.2 anymore. I'll work with this (thanks for the feedback guys) but it's not a top priority. I just like to keep order on my boxen.

PROBLEMCHYLD · 02-06-2021, 05:18 PM

I use the configs from current and constantly get the error when using build-all-kernels.sh on 14.2.

Code:

  LD [M]  fs/xfs/xfs.o
  CC      fs/locks.o
  CC      fs/binfmt_script.o
  CC      fs/binfmt_elf.o
  CC      fs/compat_binfmt_elf.o
  CC      fs/posix_acl.o
  CC      fs/coredump.o
  CC      fs/drop_caches.o
  CC      fs/fhandle.o
  CC      fs/dcookies.o
  CC [M]  fs/binfmt_misc.o
  CC [M]  fs/mbcache.o
  AR      fs/built-in.a
mv: cannot stat '/tmp/kernel-source-5.10.13-noarch-1.txz': No such file or directory

karlmag · 02-06-2021, 05:55 PM

Quote:

Originally Posted by PROBLEMCHYLD

I use the configs from current and constantly get the error when using build-all-kernels.sh on 14.2.

Code:

mv: cannot stat '/tmp/kernel-source-5.10.13-noarch-1.txz': No such file or directory

If you look at line 98 in build-all-kernels.sh it says;

Code:

mv ${TMP}/${KERNEL_SOURCE_PACKAGE_NAME} $OUTPUT || exit 1

Which - if it fails - will give an error message like the one you get.

So why does this happen?

On line 96 in the same script;

Code:

KERNEL_CONFIG="config-generic${LOCALVERSION}-${VERSION}${LOCALVERSION}
${CONFIG_SUFFIX}" VERSION=$VERSION BUILD=$BUILD ./kernel-source.SlackBuild

The important part and clue, I am guessing, is the running of kernel-source.SlackBuild.
If that is run, I would assume the kernel source txz would be built and put into /tmp (or ${TMP}).
So in build-all-kernels.sh it is assumed that the source txz exists and is trying to move it around.
Why it actually fails for you I cannot say anything too useful about, but it not existing for whatever reason would be the reason it does fail. If it is built, or at least tried to build, is perhaps /tmp running out of disk space?

Thanks
--
KarlMag

AlleyTrotter · 02-06-2021, 07:06 PM

Anyone wanting to build a linux kernel let me highly recommend starting here :

Code:

/usr/src/linux-$VERSION/Documentation/admin-guide/README.rst

been using this and other help files to build kernels since 1998
I guess the SlackBuild from current may work on 14.2, but I prefer following the above guide.
I believe the original was written by Linus himself.
HTH
john

PS taint easy until you do it about hundred times, then it becomes second nature.

Aeterna · 02-07-2021, 12:27 AM

Quote:

Originally Posted by AlleyTrotter

First copy the new (current) config to .config then make oldconfig. Probably should have included that in my answer. I think i did say which kernel config you should use.
You are wrong about older versions of GCC.

Code:

/usr/bin/gcc --version
gcc (GCC) 5.5.0
Copyright (C) 2015 Free Software Foundation, Inc.
This is free software; see the source for copying conditions.  There is NO
warranty; not even for MERCHANTABILITY or FITNESS FOR A PARTICULAR PURPOSE.

head /usr/src/linux-5.10/.config
#
# Automatically generated file; DO NOT EDIT.
# Linux/x86_64 5.10.13 Kernel Configuration
#
CONFIG_CC_VERSION_TEXT="gcc (GCC) 5.5.0"
CONFIG_CC_IS_GCC=y
CONFIG_GCC_VERSION=50500
CONFIG_LD_VERSION=201827250000
CONFIG_CLANG_VERSION=0
CONFIG_LLD_VERSION=0

Slackware64-14.2 compiles and runs the 5.10 series just fine no problems.
I have compiled every one of them without problems on 14.2
HTH
john

this is the most convoluted way of building kernel that I have recently seen:

cp -pv slackware64/source/k/kernel-huge-5.10.?.x64 /usr/src/linux-5.10/.config
make oldconfig - not needed
make
make modules_install
cp -pv .config /boot/config-5.10.13 not needed
cp -pv System.map /boot/System.map-5.10.13 not needed
cp -pv arch/x86/boot/bzimage /boot/vmlinuz-5.10.13
# include next line if you use UEFI
cp -pv arch/x86/boot/bzimage /boot/efi/EFI/SLACKWARE/vmlinuz-5.10.13

just copy .config from the last kernel to the new kernel sources and build (although why re-compile huge, I am not sure really). Then copy bzImage to /boot or /boot/efi/EFI/Slackware

you did suggest also to use localmodconfig
unless you know what you do, you will end up without all the modules that are loaded on demand.
localmodconfig scans for loaded modules and includes these in the .config. If module is not loaded, it will not be added to the new .config file

@enorbet
I don't use initrd for Slackware. I did use in past nvidia, but too much trouble, so now I am happy with nouveau

Didier Spaier · 02-07-2021, 03:00 AM

FWIW. I have slightly modified build_all_kernels.sh as I don't need huge kernels. Also I only build for x86_64.

PROBLEMCHYLD · 02-07-2021, 07:44 AM

Quote:

Originally Posted by karlmag

If you look at line 98 in build-all-kernels.sh it says;

Code:

mv ${TMP}/${KERNEL_SOURCE_PACKAGE_NAME} $OUTPUT || exit 1

Which - if it fails - will give an error message like the one you get.

So why does this happen?

On line 96 in the same script;

Code:

KERNEL_CONFIG="config-generic${LOCALVERSION}-${VERSION}${LOCALVERSION}
${CONFIG_SUFFIX}" VERSION=$VERSION BUILD=$BUILD ./kernel-source.SlackBuild

The important part and clue, I am guessing, is the running of kernel-source.SlackBuild.
If that is run, I would assume the kernel source txz would be built and put into /tmp (or ${TMP}).
So in build-all-kernels.sh it is assumed that the source txz exists and is trying to move it around.
Why it actually fails for you I cannot say anything too useful about, but it not existing for whatever reason would be the reason it does fail. If it is built, or at least tried to build, is perhaps /tmp running out of disk space?

Thanks
--
KarlMag

Thanks, but I'm not running out of disk space. Its something in the config files because if I use the older configs from 5.4 everything compiles. Once I use the 5.10 configs I'm presented with the error message. So I added all the changes from 5.10 to 5.4 and things compile. I can't use the 5.10 configs without error.

AlleyTrotter · 02-07-2021, 08:11 AM

Quote:

Originally Posted by Aeterna

this is the most convoluted way of building kernel that I have recently seen:

cp -pv slackware64/source/k/kernel-huge-5.10.?.x64 /usr/src/linux-5.10/.config
make oldconfig - not needed
make
make modules_install
cp -pv .config /boot/config-5.10.13 not needed
cp -pv System.map /boot/System.map-5.10.13 not needed
cp -pv arch/x86/boot/bzimage /boot/vmlinuz-5.10.13
# include next line if you use UEFI
cp -pv arch/x86/boot/bzimage /boot/efi/EFI/SLACKWARE/vmlinuz-5.10.13

just copy .config from the last kernel to the new kernel sources and build (although why re-compile huge, I am not sure really). Then copy bzImage to /boot or /boot/efi/EFI/Slackware

you did suggest also to use localmodconfig
unless you know what you do, you will end up without all the modules that are loaded on demand.
localmodconfig scans for loaded modules and includes these in the .config. If module is not loaded, it will not be added to the new .config file

@enorbet
I don't use initrd for Slackware. I did use in past nvidia, but too much trouble, so now I am happy with nouveau

You may not like my method which is patterned after the Kernel documentation But
You are still wrong about older GCC
You obviously have little experience building kernel

Code:

ls /boot/*4.4.240*
/boot/System.map-generic-4.4.240  /boot/config-generic-4.4.240.x64  /boot/vmlinuz-generic-4.4.240
/boot/System.map-huge-4.4.240     /boot/config-huge-4.4.240.x64     /boot/vmlinuz-huge-4.4.240

The above "not needed" is also installed by the SlackBuild.

3rensho · 02-07-2021, 09:42 AM

5.10.14 and three others have dropped

cwizardone · 02-07-2021, 09:56 AM

As 3resho has pointed out, kernel updates 5.10.14, 5.4.96, 4.19.174 and 4.14.220 are now available at,

https://www.kernel.org/

The change logs,

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

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

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

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

enorbet · 02-07-2021, 10:12 AM

I'm not sure if you were including me, AlleyTrotter, in kernel stuff beyond nvidia modules, but just to be sure I have to mention I always build a custom kernel NOT merely a Huge rehash and I've built hundreds in 20+ years. My 14.2 install could very well have some other quirky issues because as soon as "Pure Alsa" became available on Current, I adapted it to 14.2 and partly because my stem is multilib, there were sacrifices to dump pulse. It was a worthwhile tradeoff back then (not so much now) and I still have the older working 5.5.12 kernel option on it.

Current is considerably snappier than 14.2, so much so that I replaced my 14.2 install on an ancient laptop with Current and Plasma5. I no longer need 14.2 to game or do recording/editing work so nouveau is OK until I get around to either fixing 14.2 or upgrading it to Current... either that or just wipe the system and keep the partition as storage.

Anyway I agree that nouveau is more than adequate for 2D and moderate acceleration, but since my stroke I depend on games for a strenuous eye/hand workout and nouveau will not cut it there.