On Wed, May 17, 2017 at 3:35 PM, Kai Krakow <hurikha...@gmail.com> wrote: > Am Wed, 17 May 2017 12:14:18 -0700 > schrieb Jorge Almeida <jjalme...@gmail.com>:
>> Well, regardless of how well/badly it works, it does seem to have >> everything I don't want: hidden boot messages? logs sent to somewhere? >> No-thank-you. >> >> (Not to mention that newer versions seem to be systemd-only, according >> to the Wiki) > > Actually it's pretty much plug and play: Choose theme, enable, I hate plug and play. It means I must trust something not knowing what it does. Of course, plug and play would be great if it didn't usually come with zero documentation. (OK, plug and play for USB doesn't require documentation, but something like Plymouth would be quite different...) > BTW: Newer versions also seem to be KMS-only, so if your graphics > driver doesn't support KMS, plymouth wouldn't work there anyway. For > nvidia proprietary, there's a KMS module which you need to trick into > being loaded very early at boot. This is easy when integrated into > initrd. It also enables me to finally use UEFI and suspend to RAM again > with NVIDIA proprietary without a dead framebuffer after resume. ;-) IMO, KMS is great. I finally retired my Atom ION, and I will never again buy Nvidia. Ever. Never again. No more. > > But I think this is also everything you don't want. I just wanted to > take note of the pitfalls for completion reasons. > Your input is appreciated. Regards Jorge
