On 17.04.2014 03:14, Adam Williamson wrote:
On Thu, 2014-04-17 at 02:28 +0200, poma wrote:
>> Hum, actually - it looks like on my tablet, dropping 'rhgb quiet' from
>> the cmdline helps (no 'enforcing=0' needed). Does that apply to others?
>>
>
> # systemctl stop plymouth-halt plymouth-kexec plymouth-poweroff
> plymouth-quit-wait plymouth-quit plymouth-read-write plymouth-reboot
> plymouth-start plymouth-switch-root systemd-ask-password-plymouth
>
> # systemctl mask plymouth-halt plymouth-kexec plymouth-poweroff
> plymouth-quit-wait plymouth-quit plymouth-read-write plymouth-reboot
> plymouth-start plymouth-switch-root systemd-ask-password-plymouth
>
> # ll /etc/systemd/system/*plymouth*
>
> # vi /etc/dracut.conf.d/omit_dracut-module-plymouth.conf
> omit_dracutmodules+=" plymouth "
>
> # dracut -f -v
>
> Will set you free.
That's, um, massively more drastic and difficult to reverse than just
leaving 'rhgb' out of the cmdline, and doesn't tell us any more in terms
of fixing the actual bug.
Tt's just removing one variable from the equation, really nothing
drastically.
poma