On Sunday, April 05, 2015 01:15:48 PM Cristian Rodríguez wrote:
then running mkinitrd will recreate your initrd, tell Dracut to load
your driver, and Plymouth will use it
Nope.. nope. nope.. do not recommend people to do this.. dracut has to
include the needed modules in the initrd automatically.. if it does
not.. then there is a bug..
Actually the issue is not with Dracut :) If you run a dracut -H and have a
new initrd file generated, then dracut will recognize the video driver
required and included it into the initrd file.
However as with many things, due to the sake of compatibility with other
programs the mkinitrd wrapper seems to be the culprit. I haven't checked, but
I guess that it calls dracut in such a way that it no longer checks which
video driver is required. I wonder when we can actually switch to just calling
dracut with the right parameters and drop these type of wrappers.
On Sun, Apr 5, 2015 at 8:51 PM, Cristian Rodríguez email@example.com wrote:
On Sun, Apr 5, 2015 at 9:46 AM, Sumit Bhardwaj firstname.lastname@example.org wrote:
But can there be an issue if I do what is suggested by Richard? Or is it just about good practice? Right now, this issue is irritating me a little.
Something like that just continues the long standing tradition of papering over bugs somewhere else, if we need drm devices drivers in the initrd and dracut does not pull them in when plymouth is installed then there is a bug that needs fixing. -- To unsubscribe, e-mail: email@example.com To contact the owner, e-mail: firstname.lastname@example.org