[SOLVED] kmod-30 bug causes mkinitrd warning after kernel upgrade

kgha · 07-08-2022, 01:39 AM

When running

Code:

mkinitrd -c -k 5.18.10 -m ext4

after today's kernel upgrade I get the following warning:

Code:

depmod: WARNING: could not open modules.builtin.modinfo at /boot/initrd-tree/lib/modules/5.18.10: No such file or directory

Probably negligible since reboot was uneventful and everything seems to run as it should?

EDIT: checked the package and the modules.builtin.modinfo is there, but for some reason it's not transferred to my ssd during install.

3rensho · 07-08-2022, 01:59 AM

I see exactly the same thing but as you say doesn't seem to cause a problem

rkelsen · 07-08-2022, 07:19 AM

Quote:

Originally Posted by kgha

When running

Code:

mkinitrd -c -k 5.18.9 -m ext4

after today's kernel upgrade I get the following warning:

Dunno if that's a typo, but you seem to have typed the wrong kernel version there.

kgha · 07-08-2022, 08:09 AM

Quote:

Originally Posted by rkelsen

Dunno if that's a typo, but you seem to have typed the wrong kernel version there.

Yes it was a typo when posting, my first post now duly edited. Thanks for pointing it out.

kgha · 07-08-2022, 09:35 AM

Seems to be a bug in kmod-30 causing this:
https://bugs.archlinux.org/task/75218

teoberi · 07-08-2022, 11:32 AM

http://slackware.osuosl.org/slackwar...nitrd/mkinitrd

Code:

  cp /lib/modules/$kver/modules.{builtin,order} \

->

Code:

  cp /lib/modules/$kver/modules.{builtin,builtin.modinfo,order} \

Or directly in /sbin/mkinitrd

LuckyCyborg · 07-08-2022, 12:03 PM

Quote:

Originally Posted by teoberi

http://slackware.osuosl.org/slackwar...nitrd/mkinitrd

Code:

  cp /lib/modules/$kver/modules.{builtin,order} \

->

Code:

  cp /lib/modules/$kver/modules.{builtin,builtin.modinfo,order} \

Or directly in /sbin/mkinitrd

Yes, I tested this and it fixes the error subject of this thread, and probably the built initrd works better.

BUT, what about the backward compatibility? There is nothing for us to care regarding it?

kgha · 07-08-2022, 12:22 PM

Thanks, teoberi, your suggested change fixed the error for me. I'll mark the thread as solved, even if LuckyCyborg's point regarding backward compatibility might be valid.

teoberi · 07-08-2022, 12:30 PM

We will see in the next period if the solution is correct.

Arch Linux uses it.

amikoyan · 07-08-2022, 12:51 PM

I am very lazy and just run the geninitrd command after updating:
From the Slackware 15.0 release notes:

Quote:

Slackware 15.0 release notes. Wed Feb 2 18:39:59 CST 2022

Good hello folks, nice to see you here again. :-
I'd strongly recommend using a generic kernel for the best kernel module
compatibility as well. It's easier to do that than in previous releases - the
installer now makes an initrd for you, and the new geninitrd utility will
rebuild the initrd automatically for the latest kernel packages you've
installed on the system.

There is no error message when I rebuilt the initrd using geninitrd after Thursday's upgrade