You are not logged in.

#1 2022-07-04 09:40:07

SimonJ
Member
Registered: 2021-05-11
Posts: 181

[SOLVED] Module error on upgrade

I did an upgrade this morning and during the process I get this error.

==> Generating module dependencies
depmod: WARNING: could not open modules.builtin.modinfo at /tmp/mkinitcpio.g7ZnEP/root/lib/modules/5.18.9-arch1-1: No such file or directory

So I re-ran the command and the output is the same. My system seems to be working OK but it is odd to get an error so I would like someone more experienced than I to explain it please.

mkinitcpio -P
==> Building image from preset: /etc/mkinitcpio.d/linux.preset: 'default'
  -> -k /boot/vmlinuz-linux -c /etc/mkinitcpio.conf -g /boot/initramfs-linux.img
==> Starting build: 5.18.9-arch1-1
  -> Running build hook: [base]
  -> Running build hook: [udev]
  -> Running build hook: [autodetect]
  -> Running build hook: [modconf]
  -> Running build hook: [block]
  -> Running build hook: [filesystems]
  -> Running build hook: [keyboard]
  -> Running build hook: [fsck]
==> Generating module dependencies
depmod: WARNING: could not open modules.builtin.modinfo at /tmp/mkinitcpio.2RebpN/root/lib/modules/5.18.9-arch1-1: No such file or directory
==> Creating zstd-compressed initcpio image: /boot/initramfs-linux.img
==> Image generation successful
==> Building image from preset: /etc/mkinitcpio.d/linux.preset: 'fallback'
  -> -k /boot/vmlinuz-linux -c /etc/mkinitcpio.conf -g /boot/initramfs-linux-fallback.img -S autodetect
==> Starting build: 5.18.9-arch1-1
  -> Running build hook: [base]
  -> Running build hook: [udev]
  -> Running build hook: [modconf]
  -> Running build hook: [block]
==> WARNING: Possibly missing firmware for module: wd719x
==> WARNING: Possibly missing firmware for module: aic94xx
==> WARNING: Possibly missing firmware for module: bfa
==> WARNING: Possibly missing firmware for module: qla1280
==> WARNING: Possibly missing firmware for module: qed
==> WARNING: Possibly missing firmware for module: qla2xxx
  -> Running build hook: [filesystems]
  -> Running build hook: [keyboard]
  -> Running build hook: [fsck]
==> Generating module dependencies
depmod: WARNING: could not open modules.builtin.modinfo at /tmp/mkinitcpio.g7ZnEP/root/lib/modules/5.18.9-arch1-1: No such file or directory
==> Creating zstd-compressed initcpio image: /boot/initramfs-linux-fallback.img
==> Image generation successful

Any help or explanation gratefully received.

Last edited by SimonJ (2022-07-04 10:34:43)

Online

#2 2022-07-04 10:30:11

Lone_Wolf
Administrator
From: Netherlands, Europe
Registered: 2005-10-04
Posts: 12,933

Re: [SOLVED] Module error on upgrade

Has to do with the update of kmod to v30, see https://bugs.archlinux.org/task/75218


Disliking systemd intensely, but not satisfied with alternatives so focusing on taming systemd.

clean chroot building not flexible enough ?
Try clean chroot manager by graysky

Online

#3 2022-07-04 10:34:26

SimonJ
Member
Registered: 2021-05-11
Posts: 181

Re: [SOLVED] Module error on upgrade

Lone_Wolf wrote:

Has to do with the update of kmod to v30, see https://bugs.archlinux.org/task/75218

Thank you, downgrade to kmod 29 and the error is gone.

Online

#4 2022-07-04 11:41:08

Scimmia
Fellow
Registered: 2012-09-01
Posts: 12,085

Re: [SOLVED] Module error on upgrade

There was no error, downgrading makes no sense.

Warning are not errors.

Offline

#5 2022-07-04 11:51:19

SimonJ
Member
Registered: 2021-05-11
Posts: 181

Re: [SOLVED] Module error on upgrade

Scimmia wrote:

There was no error, downgrading makes no sense.

Warning are not errors.

As I said I wanted input, if there is no problem with the warning I can live with that, I just needed someone with more knowledge to explain it.

Upgraded. Thank you.

Online

#6 2022-07-04 12:47:17

Bachsau
Member
Registered: 2016-12-09
Posts: 16

Re: [SOLVED] Module error on upgrade

Scimmia wrote:

Warning are not errors.

No, but they can have consequences. I'm also very careful when such things come up during updates of anything involved in booting. If the system does not come up again because some module is missing from the RAM disk, that would result in a lengthy fixing process which I don't want to go through.

Offline

Board footer

Powered by FluxBB