[SOLVED] Split: Other kernels to use in place of End of Life Kernels

[Member LikkMii]

Helpful

Up

0

::

Just put liquorix on it and roll

[Moderator Brian Masinick]

Helpful

Up

0

::

LikkMii wrote:

Just put liquorix on it and roll

For anyone interested in that approach, there are “patches” available for the Liquorix kernel sources going WAY back to the Version 3 series, so the 4.4 patches are out there.

Here’s a link to them: https://liquorix.net/sources/

https://liquorix.net/ has the main information and the commands to bring in the Liquorix repository, including the security key.

curl ‘https://liquorix.net/add-liquorix-repo.sh’ | sudo bash
will create the initial entry into the /etc/apt/ directory tree.

sudo apt-get install linux-image-liquorix-amd64 linux-headers-liquorix-amd64
installs the current liquorix kernel image and headers (this will install version 5.15/16 kernel binaries at the present time)

--
Brian Masinick

[Forum Admin rokytnji]

Helpful

Up

0

::

are you sure you want a deb package. The names below are the kernel maintainers. The end date is projected EOL. The middle date is the release date.

“4.14 Greg Kroah-Hartman & Sasha Levin 2017-11-12 Jan, 2024

anyways. search term should be for kernel version for long term support like I listed above is: 4.14.267

Now the hard part is finding a .deb compatible with antix version of libs.

https://www.linuxcompatible.org/story/linux-kernel-414267-released/

Maybe put a request in at the MX forum is all I can think of presently.

https://forum.mxlinux.org/viewforum.php?f=55&sid=2c712ad5c90cc72555b9bade50b91fcb

Good Luck.

Sometimes I drive a crooked road to get my mind straight.
Not all who Wander are Lost.
I'm not outa place. I'm from outer space.

Linux Registered User # 475019
How to Search for AntiX solutions to your problems

[Member andfree]

Helpful

Up

0

::

LikkMii wrote:

Just put liquorix on it and roll

Could not download all repository indexes

The repository may no longer be available or could not be contacted because of network problems. If available an older version of the failed index will be used. Otherwise the repository will be ignored. Check your network connection and ensure the repository address in the preferences is correct.

GPG error: https://liquorix.net/debian sid InRelease: The following signatures couldn’t be verified because the public key is not available: NO_PUBKEY 9AE4078033F8024DThe repository ‘http://liquorix.net/debian sid InRelease’ is not signed.

• This reply was modified 1 year, 2 months ago by andfree.

[Member andfree]

Helpful

Up

0

::

rokytnji wrote:

are you sure you want a deb package.

I’m not, I’m just sure I want to keep alive two old but functional machines. It seems that I misunderstood this post and thought that installing 4.14 is something simple:

oops wrote:

FI: I had the same issue with a old PC (PACKARD BELL BV) … and only kernels 4.4 and 4.14 worked correctly.
inxi:
System: Host: mx19 Kernel: 4.14.14-antix.1-486-smp i686 bits: 32 compiler: gcc v: 7.2.0
Machine: Type: Desktop System: PACKARD BELL BV product: ### v: N/A serial: ### Chassis: type: 3 serial: 50424E

Now, judging by the name of the kernel in that case (4.14.14-antix.1-486-smp), I suppose that once upon a time 4.14 was supported by antiX, so its installation must have been really simple (but it’s not anymore).

• This reply was modified 1 year, 2 months ago by andfree.

[Member oops]

Helpful

Up

0

::

Hi,
It seems than the kernel “4.14.14-antix.1-486-smp i686 bits: 32 compiler: gcc v: 7.2.0” is no more available.

But if you want to try an old 4.14 kernel, just to see if it works for your old PC, maybe you can try the old MX kernel 4.14 (.deb common + header + image)

http://mxrepo.com/mx/repo/pool/main/l/linux/

linux-headers-4.14.0-3-common_4.14.13-1~bpo9+1mx17+2_all.deb 2018-01-27 16:01 7.5M
linux-image-4.14.0-3-686_4.14.13-1~bpo9+1mx17+2_i386.deb 2018-01-27 16:03 37M
linux-headers-4.14.0-3-686_4.14.13-1~bpo9+1mx17+2_i386.deb 2018-01-27 16:02 451K

or

linux-headers-4.14.0-3-common_4.14.13-1~bpo9+1mx17+2_all.deb 2018-01-27 16:01 7.5M
linux-image-4.14.0-3-686-pae_4.14.13-1~bpo9+1mx17+2_i386.deb 2018-01-27 15:59 37M
linux-headers-4.14.0-3-686-pae_4.14.13-1~bpo9+1mx17+2_i386.deb 2018-01-27 16:02 452K

… And you will see the result.

[Moderator Brian Masinick]

Helpful

Up

0

::

andfree wrote:

LikkMii wrote:

Just put liquorix on it and roll

Could not download all repository indexes

The repository may no longer be available or could not be contacted because of network problems. If available an older version of the failed index will be used. Otherwise the repository will be ignored. Check your network connection and ensure the repository address in the preferences is correct.

GPG error: https://liquorix.net/debian sid InRelease: The following signatures couldn’t be verified because the public key is not available: NO_PUBKEY 9AE4078033F8024DThe repository ‘http://liquorix.net/debian sid InRelease’ is not signed.

If you go to the Liquorix site, they have a set of procedures you can run to add the repository and the public key to the gpg trust. There is a shell script that will do it; moreover, if you look over the script and you are able to read it, you may see what they do. The site isn’t gone and it’s not broken either; I’ve used it within the past 24 hours or less.

• This reply was modified 1 year, 2 months ago by Brian Masinick.

--
Brian Masinick

[Member andfree]

Helpful

Up

0

::

oops wrote:

But if you want to try an old 4.14 kernel, just to see if it works for your old PC, maybe you can try the old MX kernel 4.14 (.deb common + header + image)

Thanks a lot. I installed only the image (I never install headers):

$ sudo dpkg -i linux-image-4.14.0-3-686_4.14.13-1~bpo9+1mx17+2_i386.deb

“md5sum” command seems to work without any problem (as I have wrote, this was a serious problem as regards 4.9 kernel).

If I reboot while I’m connected to the net (wired or wireless), there is a noticeable delay until the “sign-in” fields of slim appear, but finally they do. No such a delay if I disconnect before rebooting.

System:
  Kernel: 4.14.0-3-686 i686 bits: 32 compiler: gcc v: 6.3.0 
  Desktop: IceWM 2.9.4 
  Distro: antiX-19_386-full Marielle Franco 16 October 2019 
  base: Debian GNU/Linux 10 (buster) 
Machine:
  Type: Laptop System: TOSHIBA product: Satellite 2450 v: PS245E-03TE0-GK 
  serial: <filter> 
  Mobo: TOSHIBA model: Portable PC v: Version A0 serial: <filter> 
  BIOS: TOSHIBA v: Version 1.30 date: 03/20/2003 
CPU:
  Info: Single Core model: Intel Pentium 4 bits: 32 type: MCP 
  arch: Netburst Northwood rev: 7 cache: L2: 512 KiB 
  flags: pae sse sse2 bogomips: 5585 
  Speed: 2793 MHz min/max: N/A Core speed (MHz): 1: 2793 
Graphics:
  Device-1: NVIDIA NV17M [GeForce4 420 Go] 
  vendor: Toshiba America Info Systems driver: nouveau v: kernel 
  bus-ID: 01:00.0 
  Display: x11 server: X.Org 1.20.4 driver: loaded: nouveau 
  unloaded: fbdev,modesetting,vesa resolution: 1024x768~60Hz 
  OpenGL: renderer: Mesa DRI nv17 x86/MMX/SSE2 v: 1.2 Mesa 18.3.6 
  direct render: Yes 
Audio:
  Device-1: Intel 82801DB/DBL/DBM AC97 Audio 
  vendor: Toshiba America Info Systems driver: snd_intel8x0 v: kernel 
  bus-ID: 00:1f.5 
  Sound Server-1: ALSA v: k4.14.0-3-686 running: yes 
Network:
  Device-1: Realtek RTL-8100/8101L/8139 PCI Fast Ethernet Adapter 
  vendor: Toshiba America Info Systems driver: 8139too v: 0.9.28 port: ce00 
  bus-ID: 02:09.0 
  IF: eth0 state: up speed: 100 Mbps duplex: full mac: <filter> 
Drives:
  Local Storage: total: 93.16 GiB used: 83.16 GiB (89.3%) 
  ID-1: /dev/sda vendor: Toshiba model: MK1032GAX size: 93.16 GiB 
Partition:
  ID-1: / size: 89.19 GiB used: 83.16 GiB (93.2%) fs: ext4 dev: /dev/sda1 
Swap:
  ID-1: swap-1 type: partition size: 2 GiB used: 0 KiB (0.0%) dev: /dev/sda2 
Sensors:
  System Temperatures: cpu: 71.0 C mobo: N/A 
  Fan Speeds (RPM): N/A 
Info:
  Processes: 97 Uptime: 32m Memory: 1004.6 MiB used: 496.8 MiB (49.5%) 
  Init: SysVinit runlevel: 5 Compilers: gcc: 8.3.0 Packages: 1901 
  Shell: Bash v: 5.0.3 inxi: 3.3.06

[Forum Admin anticapitalista]

Helpful

Up

0

::

You do realise that the 4.14 kernel you installed has less security upgrades than the present 4.4 one?
You should also know that the 4.14 kernel is no longer supported by MX Linux (where you got it from.
Finally why are you installing a stretch-based kernel(17) and not a buster-based one (19)?

Philosophers have interpreted the world in many ways; the point is to change it.

antiX with runit - leaner and meaner.

[Member andfree]

Helpful

Up

0

::

Really thanks for your comments. Unfortunately, I don’t know where to find a buster-based kernel. I just installed the kernel that oops kindly suggested to me, while I could not find any 4.14 kernel at all.

[Forum Admin anticapitalista]

Helpful

Up

0

::

Why don’t you stick with the 4.4 one?

Philosophers have interpreted the world in many ways; the point is to change it.

antiX with runit - leaner and meaner.

[Moderator Brian Masinick]

Helpful

Up

0

::

The recommendation is NOT to use the 4.14 kernel at all.

If you want a supported kernel use 4.4, (though it’s also at end of life); otherwise use one of the kernels that we DO continue to support, e.g. 4.9, 4.19 or for systems under 10 years old, see if a version 5 kernel in our repository works.

You may, if you insist, use whatever you want, but in that case we are unable to help further; we’ve already pointed out the available software,

If you at least try kernels in our repository we can help with any issues that may arise.

Do you understand what we have been sharing and attempting to explain?

--
Brian Masinick

[Moderator Brian Masinick]

Helpful

Up

0

::

One final thought: I noticed earlier that you have or had the 4.4 kernel installed and it was working fine.

If that continues to be the case, stick with it on really old hardware.

The next version with longer support is 4.9. From previous information, end of life is in 2023. If 4.19 works that’ll be supported longer.

If you are curious you can try one of those or revert to the 4.4 kernel and use it.

--
Brian Masinick

[Member oops]

Helpful

Up

0

::

Hello,
The old 4.14 kernel try was just to know if the K4.14 is OK into his old PC (It is just a test to see).
Of course this old kernel 4.14.13 is old (today it is 4.14.267) but 4.14 is not EOL and will be updated until Jan, 2024. So it is possible to compile this kernel by himself if he wants at the latest subversion.

https://www.kernel.org/releases.html
Longterm release kernels Version Maintainer Released Projected EOL
5.15 Greg Kroah-Hartman & Sasha Levin 2021-10-31 Oct, 2023
5.10 Greg Kroah-Hartman & Sasha Levin 2020-12-13 Dec, 2026
5.4 Greg Kroah-Hartman & Sasha Levin 2019-11-24 Dec, 2025
4.19 Greg Kroah-Hartman & Sasha Levin 2018-10-22 Dec, 2024
4.14 Greg Kroah-Hartman & Sasha Levin 2017-11-12 Jan, 2024
4.9 Greg Kroah-Hartman & Sasha Levin 2016-12-11 Jan, 2023

4.4 Already EOL (the last one is: 4.4.302 )

• This reply was modified 1 year, 2 months ago by oops.
• This reply was modified 1 year, 2 months ago by oops.

[Member andfree]

Helpful

Up

0

::

oops wrote:

The old 4.14 kernel try was just to know if the K4.14 is OK into his old PC (It is just a test to see).

Exactly. This is the answer to the questions & comments above. I haven’t uninstalled the 4.4 kernel and I won’t do so, if it continues to work. Even more once it is an SLTS kernel, although I haven’t yet understood how this helps me practically.

I hope that there are no serious security exploits from now on, but I don’t think that the wishes are the only thing I should do.

As regards the other supported versions of 4 (or 5) kernel, there are serious problems or they don’t work at all.

• This reply was modified 1 year, 2 months ago by andfree.

[Author]

Posts