Latest Testing Update - Kernel Extramodules missed?


#1

No announcement thread so I’ll post this question in a new thread.

4.14 and 4.9 kernel updates but no extramodules … is this right?

Packages (7) atom-1.34.0-1  linux414-4.14.98-1  linux419-4.19.20-1  linux419-bbswitch-0.8-16
             linux419-nvidia-1:415.27-5  linux419-virtualbox-host-modules-6.0.4-3  linux49-4.9.155-1

[Testing Update] 2019-01-27 - Kernels, Browsers, CertBot, Deepin, Wine
#2

When I had asked the same question some time ago, Phil said it is not always necessary.
But a confirmation would be nice…


#3

I was thinking the same thing.

But the more intriguing part for me is having Virtual Box host module for Linux 4.19 at 6.0.4 while we still have Virtual Box 6.0.2 in Testing. I wonder if Virtual Box will work correctly after applying updates.

If you leave me a moment, I’ll sacrifice myself (or my system, rather) for science.

EDIT: Welp, at first glance, it seems to work perfectly fine on my side. The update went flawlessly with Pamac GUI. I can boot both on 4.19 and 4.14 and run VMs with Virtual Box on 4.19 and 4.14 too. The rest seems to be OK too.

Huh. Well, I’ll take it I guess.

I saw no one reporting problems with it too. Maybe it’s a good sign? Or no one dared to update and are waiting or an official post? :grinning:

Version of each packages before
[awesome@i56400 ~]$ pacman -Q | grep linux
archlinux-appstream-data 20181222-2
archlinux-keyring 20190123-1
lib32-util-linux 2.33-1
libutil-linux 2.33.1-2
linux-api-headers 4.17.11-1
linux-firmware 20190118.a8b75ca-1
linux414 4.14.96-1
linux414-nvidia 1:415.27-4
linux414-virtualbox-host-modules 6.0.2-4
linux419 4.19.18-1
linux419-nvidia 1:415.27-3
linux419-virtualbox-host-modules 6.0.2-3
util-linux 2.33.1-2
[awesome@i56400 ~]$
Version of each packages after
[awesome@i56400 ~]$ pacman -Q | grep linux
archlinux-appstream-data 20181222-2
archlinux-keyring 20190123-1
lib32-util-linux 2.33-1
libutil-linux 2.33.1-2
linux-api-headers 4.17.11-1
linux-firmware 20190118.a8b75ca-1
linux414 4.14.98-1
linux414-nvidia 1:415.27-4
linux414-virtualbox-host-modules 6.0.2-4
linux419 4.19.20-1
linux419-nvidia 1:415.27-5
linux419-virtualbox-host-modules 6.0.4-3
util-linux 2.33.1-2
[awesome@i56400 ~]$
Pamac details
Synchronizing package databases...
Refreshing DEB_Arch_Extra.db...
Starting full system upgrade...
Resolving dependencies...
Checking inter-conflicts...
Downloading linux414 (4.14.98-1-x86_64)...
Downloading linux419 (4.19.20-1-x86_64)...
Downloading linux419-nvidia (1:415.27-5-x86_64)...
Downloading linux419-virtualbox-host-modules (6.0.4-3-x86_64)...
Checking keyring...
Checking integrity...
Loading packages files...
Checking file conflicts...
Checking available disk space...
Upgrading linux414 (4.14.96-1 -> 4.14.98-1)...
Upgrading linux419 (4.19.18-1 -> 4.19.20-1)...
Upgrading linux419-nvidia (1:415.27-3 -> 1:415.27-5)...
Upgrading linux419-virtualbox-host-modules (6.0.2-3 -> 6.0.4-3)...
Configuring linux419-virtualbox-host-modules...
In order to use the new version, reload all virtualbox modules manually.
Running post-transaction hooks...
Updating linux414 module dependencies...
Updating linux419 module dependencies...
Updating linux414 initcpios...
==> Building image from preset: /etc/mkinitcpio.d/linux414.preset: 'default'
  -> -k /boot/vmlinuz-4.14-x86_64 -c /etc/mkinitcpio.conf -g /boot/initramfs-4.14-x86_64.img
==> Starting build: 4.14.98-1-MANJARO
  -> Running build hook: [base]
  -> Running build hook: [udev]
  -> Running build hook: [autodetect]
  -> Running build hook: [modconf]
  -> Running build hook: [block]
  -> Running build hook: [keyboard]
  -> Running build hook: [keymap]
  -> Running build hook: [resume]
  -> Running build hook: [filesystems]
  -> Running build hook: [fsck]
==> Generating module dependencies
==> Creating gzip-compressed initcpio image: /boot/initramfs-4.14-x86_64.img
==> Image generation successful
==> Building image from preset: /etc/mkinitcpio.d/linux414.preset: 'fallback'
  -> -k /boot/vmlinuz-4.14-x86_64 -c /etc/mkinitcpio.conf -g /boot/initramfs-4.14-x86_64-fallback.img -S autodetect
==> Starting build: 4.14.98-1-MANJARO
  -> Running build hook: [base]
  -> Running build hook: [udev]
  -> Running build hook: [modconf]
  -> Running build hook: [block]
  -> Running build hook: [keyboard]
  -> Running build hook: [keymap]
  -> Running build hook: [resume]
  -> Running build hook: [filesystems]
  -> Running build hook: [fsck]
==> Generating module dependencies
==> Creating gzip-compressed initcpio image: /boot/initramfs-4.14-x86_64-fallback.img
==> Image generation successful
Updating linux419 initcpios...
==> Building image from preset: /etc/mkinitcpio.d/linux419.preset: 'default'
  -> -k /boot/vmlinuz-4.19-x86_64 -c /etc/mkinitcpio.conf -g /boot/initramfs-4.19-x86_64.img
==> Starting build: 4.19.20-1-MANJARO
  -> Running build hook: [base]
  -> Running build hook: [udev]
  -> Running build hook: [autodetect]
  -> Running build hook: [modconf]
  -> Running build hook: [block]
  -> Running build hook: [keyboard]
  -> Running build hook: [keymap]
  -> Running build hook: [resume]
  -> Running build hook: [filesystems]
  -> Running build hook: [fsck]
==> Generating module dependencies
==> Creating gzip-compressed initcpio image: /boot/initramfs-4.19-x86_64.img
==> Image generation successful
==> Building image from preset: /etc/mkinitcpio.d/linux419.preset: 'fallback'
  -> -k /boot/vmlinuz-4.19-x86_64 -c /etc/mkinitcpio.conf -g /boot/initramfs-4.19-x86_64-fallback.img -S autodetect
==> Starting build: 4.19.20-1-MANJARO
  -> Running build hook: [base]
  -> Running build hook: [udev]
  -> Running build hook: [modconf]
  -> Running build hook: [block]
  -> Running build hook: [keyboard]
  -> Running build hook: [keymap]
  -> Running build hook: [resume]
  -> Running build hook: [filesystems]
  -> Running build hook: [fsck]
==> Generating module dependencies
==> Creating gzip-compressed initcpio image: /boot/initramfs-4.19-x86_64-fallback.img
==> Image generation successful
Updating Grub-Bootmenu
Generating grub configuration file ...
Found background: /usr/share/grub/background.png
Found linux image: /boot/vmlinuz-4.19-x86_64
Found initrd image: /boot/intel-ucode.img /boot/initramfs-4.19-x86_64.img
Found initrd fallback image: /boot/initramfs-4.19-x86_64-fallback.img
Found linux image: /boot/vmlinuz-4.14-x86_64
Found initrd image: /boot/intel-ucode.img /boot/initramfs-4.14-x86_64.img
Found initrd fallback image: /boot/initramfs-4.14-x86_64-fallback.img
Found Windows Boot Manager on /dev/sda2@/EFI/Microsoft/Boot/bootmgfw.efi
Found memtest86+ image: /boot/memtest86+/memtest.bin
done
Arming ConditionNeedsUpdate...
Transaction successfully finished.
Partial inxi
System:
  Host: i56400 Kernel: 4.19.20-1-MANJARO x86_64 bits: 64 compiler: gcc 
  v: 8.2.1 Desktop: Cinnamon 4.0.9 dm: LightDM Distro: Manjaro Linux 
Machine:
  Type: Desktop Mobo: ASUSTeK model: H170 PRO GAMING v: Rev X.0x 
  serial: <root required> UEFI: American Megatrends v: 0224 date: 07/17/2015 
CPU:
  Topology: Quad Core model: Intel Core i5-6400 bits: 64 type: MCP 
  arch: Skylake-S rev: 3 L2 cache: 6144 KiB 
  flags: lm nx pae sse sse2 sse3 sse4_1 sse4_2 ssse3 vmx bogomips: 21704 
  Speed: 800 MHz min/max: 800/3300 MHz Core speeds (MHz): 1: 800 2: 800 
  3: 800 4: 800 
Graphics:
  Device-1: NVIDIA GM204 [GeForce GTX 970] vendor: ASUSTeK driver: nvidia 
  v: 415.27 bus ID: 01:00.0 chip ID: 10de:13c2 
  Display: x11 server: X.Org 1.20.3 driver: nvidia tty: N/A 
  OpenGL: renderer: GeForce GTX 970/PCIe/SSE2 v: 4.6.0 NVIDIA 415.27 
  direct render: Yes

#4

I’ve updated to 4.19.20 and it works okay but I’m not using any of the extra modules on either system. as for Virtualbox it should work okay still as you found with an incrementally higher release of host modules than the Virtualbox build but not lower


#5

Here is the last ABI change for the kernels:

--- kernel-modules-2019-02-01-17:41:31-x86_64.sum	2019-02-01 17:41:31.488409310 +0100
+++ kernel-modules-x86_64.sum	2019-02-07 00:01:47.641746096 +0100
@@ -1,11 +1,11 @@
 a2bed609107c82ee49a971f0eb2c9f94  Kernel: 3.16.62-1-MANJARO
-01ee090ba5bab7d13412a34d96361e39  Kernel: 3.18.133-1-MANJARO
+01ee090ba5bab7d13412a34d96361e39  Kernel: 3.18.134-1-MANJARO
 08a24dbb1ab0372cabc3c5096269ead5  Kernel: 4.14.93-rt53-MANJARO
-f9119aab63592892b77da38a55bd901a  Kernel: 4.14.97-1-MANJARO
+f9119aab63592892b77da38a55bd901a  Kernel: 4.14.98-1-MANJARO
 02eec08680a0c59a003b4627aa83e021  Kernel: 4.16.18-rt12-MANJARO
 b3ddf6d413b44f231d0eab86b0ff99d8  Kernel: 4.18.16-rt9-MANJARO
-36d738e2e7cb88013cd5919484e14e7e  Kernel: 4.19.19-1-MANJARO
-ce81dfb08c8a81e3a2552aa651633eca  Kernel: 4.20.6-1-MANJARO
+cc80dc02f9862236c74261ad19c57c6b  Kernel: 4.19.20-1-MANJARO
+510448e870a40c848861ec08a7ab9f82  Kernel: 4.20.7-1-MANJARO
 c4bf288ca524c8ba52a863a20eed89f9  Kernel: 4.4.167-1-MANJARO
-548a50af43e3ef6f83c429a5576fc96c  Kernel: 4.9.154-1-MANJARO
+548a50af43e3ef6f83c429a5576fc96c  Kernel: 4.9.155-1-MANJARO
 43cdead525396383bdafff24b6cb7556  Kernel: 5.0.0-1-MANJARO

Therefore not always needed my friends to build new extramodules, only when the shasums change.


#6

Update Kernel okay.
OS: Manjaro 18.0.3-pre2 Illyria
Kernel: x86_64 Linux 4.20.7-1-MANJARO
Uptime: 5m
Packages: 1147
Shell: bash 5.0.0
Resolution: 1920x1080
DE: Xfce4
WM: Xfwm4
WM Theme: Agua
GTK Theme: Clearlooks [GTK2]
Icon Theme: gnome
Font: Noto Sans 11
CPU: Intel Core i5-4460 @ 4x 3.4GHz [45.0°C]
GPU: GeForce GT 720
RAM: 737MiB / 7908MiB