[gentoo-user] Re: [OT] Tux AWOL

2017-05-17 Thread Kai Krakow 
Am Wed, 17 May 2017 12:14:18 -0700
schrieb Jorge Almeida :

> On Wed, May 17, 2017 at 11:01 AM, Nikos Chantziaras
>  wrote:
> > On 05/14/2017 01:47 PM, Jorge Almeida wrote:  
> >>
> >> It's the first time I hear about plymouth. Visiting
> >> https://cgit.freedesktop.org/plymouth/ I found zilch
> >> documentation.  
> >  
> 
> Actually, I replied too soon: there is a README in the tree.
> >
> > It's... complicated:
> >
> >   https://wiki.gentoo.org/wiki/Plymouth
> >
> >  
> 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,
reboot... The kernel configuration part should be on par with other
boot screen themers. Of course, yes: Newer versions need seat support
which OpenRC doesn't have. Mask newer versions.

I don't remember if there are themes available that can show boot
messages, themes can also be handcrafted. A static image should be
really easy. I prefer uncluttered boot screens without boot messages,
so I never tried. I remember that plymouth was hiding itself back when
I was still working with OpenRC and a fatal error occurred (read:
booting stopped and failed) but since switching to systemd, I never had
such problems so it's no issue for me. In systemd, plymouth would be
hidden, when systemd falls back to emergency mode. This only happens to
me when I mess up dracut. I need and initramfs due to multi-dev btrfs.

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. ;-)

But I think this is also everything you don't want. I just wanted to
take note of the pitfalls for completion reasons.


-- 
Regards,
Kai

Replies to list-only preferred.

Re: [gentoo-user] Re: [OT] Tux AWOL

2017-05-17 Thread Jorge Almeida 
On Wed, May 17, 2017 at 11:01 AM, Nikos Chantziaras  wrote:
> On 05/14/2017 01:47 PM, Jorge Almeida wrote:
>>
>> It's the first time I hear about plymouth. Visiting
>> https://cgit.freedesktop.org/plymouth/ I found zilch documentation.
>

Actually, I replied too soon: there is a README in the tree.
>
> It's... complicated:
>
>   https://wiki.gentoo.org/wiki/Plymouth
>
>
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)

Cheers

Jorge

[gentoo-user] Re: [OT] Tux AWOL

2017-05-17 Thread Nikos Chantziaras 

On 05/14/2017 01:47 PM, Jorge Almeida wrote:

It's the first time I hear about plymouth. Visiting
https://cgit.freedesktop.org/plymouth/ I found zilch documentation.


It's... complicated:

  https://wiki.gentoo.org/wiki/Plymouth

[gentoo-user] Re: [OT] Tux AWOL

2017-05-17 Thread Kai Krakow 
Am Wed, 17 May 2017 19:38:41 +0300
schrieb Arthur Țițeică :

> În ziua de duminică, 14 mai 2017, la 12:50:43 EEST, Alan Mackenzie a
> scris:
> > Something strange happened when I installed the 4.11.0 sources -
> > all the options were initialised to what they were in my 4.9.16
> > running kernel. This saved me a lot of time.  
> 
> I've seen it gets the defaults from /boot/config* files if it can't
> find a local .config.
> 
> I had the opposite problem the other day... I wanted to start with a
> fresh .config and had to find out how it gets the current config
> automatically.

Run "make help", find "make defconfig" ;-)

-- 
Regards,
Kai

Replies to list-only preferred.

Re: [gentoo-user] [OT] Tux AWOL

2017-05-17 Thread Arthur Țițeică 
În ziua de duminică, 14 mai 2017, la 12:50:43 EEST, Alan Mackenzie a scris:
> Something strange happened when I installed the 4.11.0 sources - all the
> options were initialised to what they were in my 4.9.16 running kernel.
> This saved me a lot of time.

I've seen it gets the defaults from /boot/config* files if it can't find a 
local .config.

I had the opposite problem the other day... I wanted to start with a fresh 
.config and had to find out how it gets the current config automatically.