Description of problem:
plymouth doesn't fall back to text mode if DRM/FB devices exist but don't work as expected (e.g. nvidia binary driver).

There is a defect in Plymouth's logic. It uses udev of course to look for devices, and if it finds a DRM device or a FB device it uses them, and if not, it falls back to text mode. It does not cope with a scenario where a DRM or FB device exists but doesn't work, in that scenario it does not fall back to text mode. It /should/.

Version-Release number of selected component (if applicable):
Red Hat Enterprise Linux 7.3
plymouth-0.8.9-0.26.20140113.el7.x86_64

How reproducible:
Always

Steps to Reproduce:
It happens when you use the NVIDIA binary/third party drivers. The nvidia driver provides a DRM device (although it doesn't provide an fbdev device) and plymouth sees that and tries to use it, of course, it doesn't work because the nvidia driver doesn't support proper kernel mode setting or fbdev. So plymouth simply fails, and the user doesn't see anything during boot up until X starts. 

Actual results:
Plymouth does not cope with a scenario where a DRM or FB device exists but doesn't work, in that scenario it does not fall back to text mode.

This is a huge problem on RHEL7 if you use the PackageKit/systemd offline updates because the system starts, it begins an automatic update, and plymouth has failed so you see nothing at all, not even a text output! There is no visual indication that the system is working at all even though underneath its doing a yum update! This has led to our users rebooting systems which are mid-update, and then breaking horribly.

Expected results:
This bug thus requests that a patch be written and applied to Plymouth to cope with this scenario.
It should fall back to text mode in scenario of where DRM/FB devices exist but don't work as expected. eg (NVIDIA or any third party display driver)

Additional info:
Most people, in fact nearly all info on the internet, suggest setting the vga=<mode> flag on the kernel command line to set up a vesafb framebuffer which plymouth will then use, but this is a bad idea for many reasons (NVIDIA don't support it, the mode depends on what the card and/or monitor support, etc.). We can't do this, and don't want to.