Hi @philm @oberon
Do you know by any chance the reason behind this change on the kernels? See below:
- patch: 0104 removed
- patch: 0104 removed
Apparently that’s causing the warnings reported in the unstable announcement thread. It seems to be harmless to me though …
While update of
...
Package (8) Old Version New Version Net Change Download Size
core/linux514 5.14.rc2.d0718.g2734d6c-1 5.14.rc3.d0725.gff11764-1 0.02 MiB 96.45 MiB
...
I got the new warning I never saw before:
...
-> Running build hook: [modconf]
-> Running build hook: [block]
==> WARNING: Possibly missing firmware for module: xhci_pci
-> Running build hook: [keyboard]
...
Full log of the update ...
:: Synchronising p…
Same behaviour with latest 5.13 and 5.10.
Sorry, can’t post further info. I’m on mobile right now.
Your insights are highly appreciated. Thanks!
alven
8 August 2021 00:14
3
I have
$ mhwd-kernel -li
Currently running: 5.14.0-1-MANJARO (linux514)
The following kernels are installed in your system:
* linux514
$
$ pacman -Qi linux514
Name : linux514
Version : 5.14.rc4.d0805.g902e7f3-1
Description : The Linux514 kernel and modules
Architecture : x86_64
...
$ pacman -Qi linux-firmware
Name : linux-firmware
Version : 20210719.r1990.168452e-1
Description : Firmware files for Linux (Manjaro Overlay Package)
Architecture : any
...
and right before the package installation I tried:
$ sudo mkinitcpio -P
==> Building image from preset: /etc/mkinitcpio.d/linux514.preset: 'default'
-> -k /boot/vmlinuz-5.14-x86_64 -c /etc/mkinitcpio.conf -g /boot/initramfs-5.14-x86_64.img
==> Starting build: 5.14.0-1-MANJARO
-> Running build hook: [base]
-> Running build hook: [udev]
-> Running build hook: [autodetect]
-> Running build hook: [modconf]
-> Running build hook: [block]
==> WARNING: Possibly missing firmware for module: xhci_pci
-> Running build hook: [keyboard]
-> Running build hook: [keymap]
-> Running build hook: [encrypt]
==> WARNING: Possibly missing firmware for module: qat_4xxx
-> Running build hook: [openswap]
-> Running build hook: [filesystems]
==> Generating module dependencies
==> Creating gzip-compressed initcpio image: /boot/initramfs-5.14-x86_64.img
==> Image generation successful
==> Building image from preset: /etc/mkinitcpio.d/linux514.preset: 'fallback'
-> -k /boot/vmlinuz-5.14-x86_64 -c /etc/mkinitcpio.conf -g /boot/initramfs-5.14-x86_64-fallback.img -S autodetect
==> Starting build: 5.14.0-1-MANJARO
-> Running build hook: [base]
-> Running build hook: [udev]
-> Running build hook: [modconf]
-> Running build hook: [block]
==> WARNING: Possibly missing firmware for module: xhci_pci
-> Running build hook: [keyboard]
-> Running build hook: [keymap]
-> Running build hook: [encrypt]
==> WARNING: Possibly missing firmware for module: qat_4xxx
-> Running build hook: [openswap]
-> Running build hook: [filesystems]
==> Generating module dependencies
==> Creating gzip-compressed initcpio image: /boot/initramfs-5.14-x86_64-fallback.img
==> Image generation successful
$
I tried the AUR (en) - upd72020x-fw package (Renesas uPD720201 / uPD720202 USB 3.0 chipsets firmware):
Submitter: redchenjs
Maintainer: redchenjs
Last Packager: redchenjs
Votes: 38
Popularity: 4.97
First Submitted: 2020-08-21 15:45
Last Updated: 2020-11-25 07:32
Installed and w/o reboot tried again:
$ sudo mkinitcpio -P
==> Building image from preset: /etc/mkinitcpio.d/linux514.preset: 'default'
-> -k /boot/vmlinuz-5.14-x86_64 -c /etc/mkinitcpio.conf -g /boot/initramfs-5.14-x86_64.img
==> Starting build: 5.14.0-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: [encrypt]
==> WARNING: Possibly missing firmware for module: qat_4xxx
-> Running build hook: [openswap]
-> Running build hook: [filesystems]
==> Generating module dependencies
==> Creating gzip-compressed initcpio image: /boot/initramfs-5.14-x86_64.img
==> Image generation successful
==> Building image from preset: /etc/mkinitcpio.d/linux514.preset: 'fallback'
-> -k /boot/vmlinuz-5.14-x86_64 -c /etc/mkinitcpio.conf -g /boot/initramfs-5.14-x86_64-fallback.img -S autodetect
==> Starting build: 5.14.0-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: [encrypt]
==> WARNING: Possibly missing firmware for module: qat_4xxx
-> Running build hook: [openswap]
-> Running build hook: [filesystems]
==> Generating module dependencies
==> Creating gzip-compressed initcpio image: /boot/initramfs-5.14-x86_64-fallback.img
==> Image generation successful
$
Hm, like magic!
Thank you, @steanne !
How did you know about that package? Why exactly that package with that strange name of 2020
like it was for 2020 year as temp patch and now outdated?
PS
Why so old version? 1 year ago was the first submit and 9 months ago last update. Are there more modern?
the 2020 is part of the name of the chip.
1 Like
Yep, I confirm that I’ve got a flawless initramfs generation after the patch was re-added.
==> Building image from preset: /etc/mkinitcpio.d/linux510.preset: 'default'
-> -k /boot/vmlinuz-5.10-x86_64 -c /etc/mkinitcpio.conf -g /boot/initramfs-5.10-x86_64.img
==> Starting build: 5.10.58-1-MANJARO
-> Running build hook: [base]
-> Running build hook: [udev]
-> Running build hook: [usr]
-> Running build hook: [autodetect]
-> Running build hook: [modconf]
-> Running build hook: [block]
-> Running build hook: [keyboard]
-> Running build hook: [keymap]
-> Running build hook: [consolefont]
-> Running build hook: [plymouth]
-> Running build hook: [lvm2]
-> Running build hook: [filesystems]
-> Running build hook: [shutdown]
==> Generating module dependencies
==> Creating zstd-compressed initcpio image: /boot/initramfs-5.10-x86_64.img
==> Image generation successful
==> Building image from preset: /etc/mkinitcpio.d/linux510.preset: 'fallback'
-> -k /boot/vmlinuz-5.10-x86_64 -c /etc/mkinitcpio.conf -g /boot/initramfs-5.10-x86_64-fallback.img -S autodetect
==> Starting build: 5.10.58-1-MANJARO
-> Running build hook: [base]
-> Running build hook: [udev]
-> Running build hook: [usr]
-> Running build hook: [modconf]
-> Running build hook: [block]
-> Running build hook: [keyboard]
-> Running build hook: [keymap]
-> Running build hook: [consolefont]
-> Running build hook: [plymouth]
-> Running build hook: [lvm2]
-> Running build hook: [filesystems]
-> Running build hook: [shutdown]
This issue should be resolved for the other branches once the newer kernel updates are rolled out.
Thanks @philm for looking after this.
1 Like
This topic was automatically closed 24 hours after the last reply. New replies are no longer allowed.