Comment # 24 on bug 1183839 from Bruno Friedmann

(In reply to Takashi Iwai from comment #23)
> I guess it's either some dracut config or the installation of an extra
> modules in /lib/modules/*/{updates,weak-updates,extra}/*?  Usually the
> latter happens when a KMP is installed and it puts in the update path.  Then
> dracut enforces the modules to be loaded in initrd, no matter whether it's
> needed or not.

Hi, I would like to thank you firt for the advises given along the thread.

I've checked what I have and it's nothing really unusual (those drivers are
there since years) vbox and nvidia. Unfortunately for me both are mandatory
around.

-rw-r--r-- 1 root root   770659 avr  8 22:29
/lib/modules/5.11.11-1-default/extra/vboxdrv.ko
-rw-r--r-- 1 root root    21163 avr  8 22:29
/lib/modules/5.11.11-1-default/extra/vboxnetadp.ko
-rw-r--r-- 1 root root    62963 avr  8 22:29
/lib/modules/5.11.11-1-default/extra/vboxnetflt.ko
-rw-r--r-- 1 root root  3762824 avr 11 15:53
/lib/modules/5.11.11-1-default/updates/nvidia-drm.ko
-rw-r--r-- 1 root root 49579768 avr 11 15:53
/lib/modules/5.11.11-1-default/updates/nvidia.ko
-rw-r--r-- 1 root root  2203400 avr 11 15:53
/lib/modules/5.11.11-1-default/updates/nvidia-modeset.ko
-rw-r--r-- 1 root root 40843928 avr 11 15:53
/lib/modules/5.11.11-1-default/updates/nvidia-uvm.ko

I would exclude nvidia since I have it on other machines and didn't get that
trouble. I should be able in the next week to remove temporalily vbox to
recheck if that one is causing the trouble.

Have a good day