Felix Miata composed on 2018-01-02 04:30 (UTC-0500):
Andrei Borzenkov composed on 2018-01-02 08:08 (UTC+0300):
Felix Miata composed:
I'm noticing these failures during boot on many TW installations, maybe more than half. Below are from the journals of two installations. In recent days, I've seen these messages on at least 4 of 7 installations. # TW20171230 4.14.8 p5bse systemd-modules-load[134]: Failed to find module 'no' ... # TW20171231 4.13.12 & 4.14.9 fi965 systemd-modules-load[144]: Failed to find module 'no' ... How do I find what causes these?
You read "man modules-load.d" and find file that contains "no" as module name.
Do other see them too?
No.
Is this a problem that needs fixing?
Of course, any false noise distracts from real errors.
On four installations checked so far, /etc/modules-load.d/MODULES_LOADED_ON_BOOT.conf timestamped 2013 existed and contained various strings not corresponding to any module existing in current kernel.
One (host gx27c) producing such errors had /etc/modules-load.d/yast.conf dated Dec. 2013, containing pciehp Wouldn't that have been something that became obsolete and should have been removed by some yast module update? rpm -qf reports that file not owned by any package. -- "Wisdom is supreme; therefore get wisdom. Whatever else you get, get wisdom." Proverbs 4:7 (New Living Translation) Team OS/2 ** Reg. Linux User #211409 ** a11y rocks! Felix Miata *** http://fm.no-ip.com/ -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse+owner@opensuse.org