How to Install kernel 419

Hello,

I’ve just installed EndeavourOS and I would like to know how to install the (old) Kernel 419.
It is the latest kernel that works well with my laptop (I have a Lenovo Yoga C930, which is known to be quite unfriendly to our Linux, anyway…).

I had a look on the AKM program of Endeavouros to manage kernels but the kernel 4.19 is not referenced.
I tried installing it via yay, more precisely I tried to install these two packages:

2 aur/linux-lts419-headers 4.19.251-1 (+13 0.44) 
    Headers and scripts for building modules for the LTS 4.19 Linux kernel
1 aur/linux-lts419 4.19.251-1 (+13 0.44) 
    The LTS 4.19 Linux kernel and modules

but the build was about to destroy my laptop (the process was very long and temperatures were reaching critical levels), so I had to kill it.

Any idea?
Thanks.

it is only “officially” available in the AUR.

It is normal that it takes some time and produces heat. AUR-Kernels are compiled when installing - when set up correctly, it uses all threads.

To get you a rough estimate: Building the mainline Kernel (https://archlinux.org/packages/core/x86_64/linux/) on my Ryzen 7 2700X 8C/16T CPU takes about 20 minutes while using all 16 Threads.

1 Like

You can get it from the kernel-lts repo which is unoffical.

https://wiki.archlinux.org/title/unofficial_user_repositories#kernel-lts

3 Likes

Great! I will have a look at it. Seems what I need! Thanks.

1 Like

didn’t remember it in time. The repo is maintained by someone that is active in the forum:

2 Likes

Keep in mind that you’ll also have to configure your initramfs to use something other than zstd compression (in /etc/mkinitcpio.conf) - anything earlier than 5.4 doesn’t support zstd compression, which is now the Arch default.

“Someone” :stuck_out_tongue:

7 Likes

It’s that guy! :point_up:

Thanks for the tip!

Oh, also, you’ll want the uncompressed firmware variant from the kernel-lts repo too:

https://archlinux.org/news/linux-firmware-202201190c6a7b3-2-requires-kernel-53-and-package-splitting/

So linux-firmware-uncompressed to replace the standard linux-firmware (and any others your system has).

Hi,
Thanks a lot for the help!
I’ve finally installed the kernel 419 from the AUR. It took me more than 1 hour (and a lot of ice) but ended. However I got a few warnings and errors (see below).
Then:

  1. I’ve substituted linux-framware by linux-framware-uncompressed

  2. I’ve replaced the zstd compression system in /etc/mkinitcpio.conf by another one (I chose gzip, not knowing which one would be better).

  3. Rebooted. But it does not start, I got a kernel panic, first line is:
    Initframs unpacking failed: junk in compressed archive

Should I’ve done step 1 and 2 before building the kernel from yay? (Well, as you can see I don’t really understand what I’m doing).

From pacman.log (I don’t know where is yay’s log file):

 [2022-07-30T12:28:14+0200] [PACMAN] Running 'pacman -U --noconfirm --config /etc/pacman.conf -- /home/alex/.cache/yay/linux-lts419/linux-lts419-headers-4.19.251-1-x86_64.pkg.tar.zst /home/alex/.cache/yay/linux-lts419/linux-lts419-4.19.251-1-x86_64.pkg.tar.zst'
[2022-07-30T12:28:14+0200] [ALPM] transaction started
[2022-07-30T12:28:15+0200] [ALPM] installed linux-lts419-headers (4.19.251-1)
[2022-07-30T12:28:16+0200] [ALPM] installed linux-lts419 (4.19.251-1)
[2022-07-30T12:28:16+0200] [ALPM] transaction completed
[2022-07-30T12:28:16+0200] [ALPM] running '30-systemd-update.hook'...
[2022-07-30T12:28:16+0200] [ALPM] running '60-depmod.hook'...
[2022-07-30T12:28:22+0200] [ALPM-SCRIPTLET] depmod: WARNING: could not open modules.builtin.modinfo at /lib/modules/4.19.251-1-lts419: No such file or directory
[2022-07-30T12:28:22+0200] [ALPM] running '90-mkinitcpio-install.hook'...
[2022-07-30T12:28:22+0200] [ALPM-SCRIPTLET] ==> Building image from preset: /etc/mkinitcpio.d/linux-lts419.preset: 'default'
[2022-07-30T12:28:22+0200] [ALPM-SCRIPTLET]   -> -k /boot/vmlinuz-linux-lts419 -c /etc/mkinitcpio.conf -g /boot/initramfs-linux-lts419.img
[2022-07-30T12:28:22+0200] [ALPM-SCRIPTLET] ==> Starting build: 4.19.251-1-lts419
[2022-07-30T12:28:22+0200] [ALPM-SCRIPTLET]   -> Running build hook: [base]
[2022-07-30T12:28:22+0200] [ALPM-SCRIPTLET]   -> Running build hook: [udev]
[2022-07-30T12:28:22+0200] [ALPM-SCRIPTLET]   -> Running build hook: [autodetect]
[2022-07-30T12:28:22+0200] [ALPM-SCRIPTLET]   -> Running build hook: [modconf]
[2022-07-30T12:28:22+0200] [ALPM-SCRIPTLET]   -> Running build hook: [block]
[2022-07-30T12:28:24+0200] [ALPM-SCRIPTLET]   -> Running build hook: [keyboard]
[2022-07-30T12:28:24+0200] [ALPM-SCRIPTLET]   -> Running build hook: [keymap]
[2022-07-30T12:28:24+0200] [ALPM-SCRIPTLET]   -> Running build hook: [consolefont]
[2022-07-30T12:28:24+0200] [ALPM-SCRIPTLET] ==> WARNING: consolefont: no font found in configuration
[2022-07-30T12:28:24+0200] [ALPM-SCRIPTLET]   -> Running build hook: [filesystems]
[2022-07-30T12:28:24+0200] [ALPM-SCRIPTLET]   -> Running build hook: [fsck]
[2022-07-30T12:28:24+0200] [ALPM-SCRIPTLET] ==> Generating module dependencies
[2022-07-30T12:28:24+0200] [ALPM-SCRIPTLET] install: cannot stat '/lib/modules/4.19.251-1-lts419/modules.builtin.modinfo': No such file or directory
[2022-07-30T12:28:24+0200] [ALPM-SCRIPTLET] depmod: WARNING: could not open modules.builtin.modinfo at /tmp/mkinitcpio.tinOEa/root/lib/modules/4.19.251-1-lts419: No such file or directory
[2022-07-30T12:28:24+0200] [ALPM-SCRIPTLET] ==> Creating zstd-compressed initcpio image: /boot/initramfs-linux-lts419.img
[2022-07-30T12:28:25+0200] [ALPM-SCRIPTLET] ==> WARNING: errors were encountered during the build. The image may not be complete.
[2022-07-30T12:28:25+0200] [ALPM-SCRIPTLET] ==> Building image from preset: /etc/mkinitcpio.d/linux-lts419.preset: 'fallback'
[2022-07-30T12:28:25+0200] [ALPM-SCRIPTLET]   -> -k /boot/vmlinuz-linux-lts419 -c /etc/mkinitcpio.conf -g /boot/initramfs-linux-lts419-fallback.img -S autodetect
[2022-07-30T12:28:25+0200] [ALPM-SCRIPTLET] ==> Starting build: 4.19.251-1-lts419
[2022-07-30T12:28:25+0200] [ALPM-SCRIPTLET]   -> Running build hook: [base]
[2022-07-30T12:28:25+0200] [ALPM-SCRIPTLET]   -> Running build hook: [udev]
[2022-07-30T12:28:25+0200] [ALPM-SCRIPTLET]   -> Running build hook: [modconf]
[2022-07-30T12:28:25+0200] [ALPM-SCRIPTLET]   -> Running build hook: [block]
[2022-07-30T12:28:25+0200] [ALPM-SCRIPTLET] ==> WARNING: Possibly missing firmware for module: qed
[2022-07-30T12:28:26+0200] [ALPM-SCRIPTLET] ==> WARNING: Possibly missing firmware for module: qla2xxx
[2022-07-30T12:28:26+0200] [ALPM-SCRIPTLET] ==> WARNING: Possibly missing firmware for module: qla1280
[2022-07-30T12:28:26+0200] [ALPM-SCRIPTLET] ==> WARNING: Possibly missing firmware for module: aic94xx
[2022-07-30T12:28:26+0200] [ALPM-SCRIPTLET] ==> WARNING: Possibly missing firmware for module: bfa
[2022-07-30T12:28:26+0200] [ALPM-SCRIPTLET] ==> WARNING: Possibly missing firmware for module: wd719x
[2022-07-30T12:28:29+0200] [ALPM-SCRIPTLET]   -> Running build hook: [keyboard]
[2022-07-30T12:28:30+0200] [ALPM-SCRIPTLET]   -> Running build hook: [keymap]
[2022-07-30T12:28:30+0200] [ALPM-SCRIPTLET]   -> Running build hook: [consolefont]
[2022-07-30T12:28:30+0200] [ALPM-SCRIPTLET] ==> WARNING: consolefont: no font found in configuration
[2022-07-30T12:28:30+0200] [ALPM-SCRIPTLET]   -> Running build hook: [filesystems]
[2022-07-30T12:28:31+0200] [ALPM-SCRIPTLET]   -> Running build hook: [fsck]
[2022-07-30T12:28:33+0200] [ALPM-SCRIPTLET] ==> Generating module dependencies
[2022-07-30T12:28:33+0200] [ALPM-SCRIPTLET] install: cannot stat '/lib/modules/4.19.251-1-lts419/modules.builtin.modinfo': No such file or directory
[2022-07-30T12:28:33+0200] [ALPM-SCRIPTLET] depmod: WARNING: could not open modules.builtin.modinfo at /tmp/mkinitcpio.FlCR3O/root/lib/modules/4.19.251-1-lts419: No such file or directory
[2022-07-30T12:28:33+0200] [ALPM-SCRIPTLET] ==> Creating zstd-compressed initcpio image: /boot/initramfs-linux-lts419-fallback.img
[2022-07-30T12:28:33+0200] [ALPM-SCRIPTLET] ==> WARNING: errors were encountered during the build. The image may not be complete.
[2022-07-30T12:28:33+0200] [ALPM] running 'eos-grub-update-after-kernel.hook'...
[2022-07-30T12:28:34+0200] [ALPM-SCRIPTLET] Generating grub configuration file ...
[2022-07-30T12:28:34+0200] [ALPM-SCRIPTLET] Found theme: /boot/grub/themes/EndeavourOS/theme.txt
[2022-07-30T12:28:34+0200] [ALPM-SCRIPTLET] Found linux image: /boot/vmlinuz-linux-zen
[2022-07-30T12:28:34+0200] [ALPM-SCRIPTLET] Found initrd image: /boot/intel-ucode.img /boot/initramfs-linux-zen.img
[2022-07-30T12:28:34+0200] [ALPM-SCRIPTLET] Found fallback initrd image(s) in /boot:  intel-ucode.img initramfs-linux-zen-fallback.img
[2022-07-30T12:28:34+0200] [ALPM-SCRIPTLET] Found linux image: /boot/vmlinuz-linux-lts419
[2022-07-30T12:28:34+0200] [ALPM-SCRIPTLET] Found initrd image: /boot/intel-ucode.img /boot/initramfs-linux-lts419.img
[2022-07-30T12:28:34+0200] [ALPM-SCRIPTLET] Found fallback initrd image(s) in /boot:  intel-ucode.img initramfs-linux-lts419-fallback.img
[2022-07-30T12:28:35+0200] [ALPM-SCRIPTLET] Found linux image: /boot/vmlinuz-linux
[2022-07-30T12:28:35+0200] [ALPM-SCRIPTLET] Found initrd image: /boot/intel-ucode.img /boot/initramfs-linux.img
[2022-07-30T12:28:35+0200] [ALPM-SCRIPTLET] Found fallback initrd image(s) in /boot:  intel-ucode.img initramfs-linux-fallback.img
[2022-07-30T12:28:35+0200] [ALPM-SCRIPTLET] Warning: os-prober will be executed to detect other bootable partitions.
[2022-07-30T12:28:35+0200] [ALPM-SCRIPTLET] Its output will be used to detect bootable binaries on them and create new boot entries.
[2022-07-30T12:28:35+0200] [ALPM-SCRIPTLET] Adding boot menu entry for UEFI Firmware Settings ...
[2022-07-30T12:28:35+0200] [ALPM-SCRIPTLET] done

Please use code tags <> instead of quote tags " to format the posted output.

Also, after making changes to your mkinitcpio.conf, did you rebuild your initramfs?

sudo mkinitcpio -P

I have one of these. It’s possible to get Endeavour mostly working with the current Zen kernel, everything but the subwoofer and fingerprint reader (and some odd and inconsitent webcam issues.

Here’s what I did, I’ve got a full howto on Reddit.

Anyway, to get the audio working on the hinge speakers (bottom speakers still dont work):

  1. Add options snd-hda-intel dmic_detect=0 to /etc/modprobe.d/alsa-base.conf(Courtesy of the Arch Wiki)
  2. Add options snd_intel_dspcfg dsp=driver=1 to /etc/modprobe.d/dsp.conf (Forgot where I found this)
  3. Install alsa-utils from the community repo specifically.
  4. Run hdajackretask from alsa-utils (Courtesy of This page)
  5. Make sure you have the internal audio selected
  6. Select (show unconnected pins)
  7. Find pin 0x17 and override it to “Dock headphone”
  8. Click “Install boot override”
  9. Reboot
1 Like

Sorry, I changed the format.

Oh, I didn’t do that. Let me try.

1 Like

Hi,
Do you know if this makes the audio jack input/output working? All I really need is to have both my headphones working and the camera. In this case that could be a good workaround for me.

I don’t have any alsa-base.conf in /etc/modprobe.d/

you have to create the file. And I ran into a gotcha where the camera only works with non-Chrome-based stuff while undocked. So firefox and OBS work, but Chrome, Chromium, Edge, and anything Electron based wouldn’t. So if you’re not using Firefox or something, you might still have an issue. But the audio jack worked fine.

Those Lenovo C930 machines are really evil to Linux in general.

It works like a charm!
In fact I tried a long time ago to do this hacking but I hadn’t seen the first two steps you mentioned! So, no codecs were appearing.
Thanks!!

I

It works! (Well, I have no wifi but this is another story). :grinning:

Thank you!

1 Like

Please check the solution box under the post that gave you the solution for you issue for this thread to close.

You could open a new thread about your WiFi and post some hardware info etc.
Please have a look here:

https://discovery.endeavouros.com/forum-log-tool-options/how-to-include-systemlogs-in-your-post/2021/03/

Ok, done.
But I have a question. Actually, @npaladin2000 gave an alternative that works for me, which is not about how to install the kernel 419.
Is it possible to open a new topic, like “How to solve some hardware issues for Lenovo yoga C930?” and link @npaladin2000’s answer as a solution?

1 Like

Sure, feel free to do so.
And good luck!