In "Workaround 1" we use add_drivers in /etc/dracut.conf to add the driver.  This is done in the kmodtool file.  We do this along with a "dracut --force" command to force a rebuild of the initrd image.

To be clear, "Workaround 1" does update the initrd image however it generates the error messages associated with our driver that I mentioned.

Andre/Dracut team,

We're are forced to move forward with deploying workaround 1 which will result in customer visible Dracut errors logged to the command line prompt and the console every single time any initrd change is made by the user whether it is related to BRCFCOE drive or not!

This is likely result in Customer Support Calls to both our company's unless some other solution can be identified by RH.  This is very unfortunate, please help to prevent these Customer Support Calls.

thank you
Laurie

$ man depmod.d

       search subdirectory...
           This allows you to specify the order in which /lib/modules (or
           other configured module location) subdirectories will be
           processed by depmod. 

       override modulename kernelversion modulesubdirectory
           This command allows you to override which version of a
           specific module will be used when more than one module sharing
           the same name is processed by the depmod command. It is
           possible to specify one kernel or all kernels using the *
           wildcard.  modulesubdirectory is the name of the subdirectory
           under /lib/modules (or other module location) where the target
           module is installed.

Greetings, Harold,

I apologize if I am missing something but, how does this help install a new driver to initrd?  I see how this can be helpful in that we can use depmod to make sure that lpfc loads before brcmfcoe or vice versa.  I.E. and alternative to blacklisting.  However, as far as I can tell, it does not address the issue of cleanly(without errors) installing the drivers onto initrd and rebuilding initrd during the driver's rpm installation.

-For example, is there a flag that can be set in kmodtool?
-Is there a directive that can be added to the spec file?

As I mentioned earlier, using dracut's "add_driver" does not work cleanly since it produces failure messages.

Please provide any further feedback relating to cleanly installing the driver onto initrd.  As mentioned, using add_driver in kmodtool produces side effects when the driver is uninstalled or upgraded.

I don't understand the problem. Works for me without any error messages. Did you forget "depmnod <kernel-version>" in the rpm install script?

# rpm -qf /etc/depmod.d/dist.conf 
kmod-20-21.el7.x86_64

# cat /etc/depmod.d/dist.conf 
#
# depmod.conf
#

# override default search ordering for kmod packaging
search updates extra built-in weak-updates

# ls -l /lib/modules/$(uname -r)/extra/hello.ko
-rw-r--r--. 1 root root 104448 13. Feb 12:01 /lib/modules/3.10.0-850.el7.x86_64/extra/hello.ko

# depmod -a

# grep hello /lib/modules/$(uname -r)/modules.dep

# cat /etc/dracut.conf.d/hello.conf 
add_drivers+=" hello "

# dracut --force test.img

# lsinitrd test.img /usr/lib/modules/3.10.0-850.el7.x86_64/modules.dep | grep hello
extra/hello.ko:

# lsinitrd test.img | grep hello.ko
-rw-r--r--   1 root     root         4840 Feb 13 12:49 usr/lib/modules/3.10.0-850.el7.x86_64/extra/hello.ko

also note the spaces in add_drivers