Kernel 4.19.x no more Tux in boot screen and led blinking on suspend.
 

For the led blinking on suspend, I'm not sure but IIRC, one of the leds, power or hd activity,
kept blinking indicating that the machine (signature desktop) was in suspend state,
just as a notebook, the power button blinks.

The Tux image at boot screen is missing but the kernel config option is set to yes.

I can confirm this after just restarting, Tux is missing. Sharp eyes Paulo2.....

I had noticed this also, but hadn't looked to see why it was missing.

Well I'll be a penguin's uncle. Been running 4.19.x since it first appeared in -current, never noticed those missing penguins. Just tested in my Acer Laptop. Will check this machine later as it's busy doing stuff aside from my typing this.

I've never used suspend on a desktop. May have to try. That seem likes a nice thing to have. <shrug>

I recall incorrectly. Running 14.2 right now and with 4.4.x kernel, leds don't blink on suspend.
I booted the last 4.18.20 dusk kernel and same result.
(I don't know where I saw the led blinking, maybe in Windows some months ago)


The Tux on boot appears with 4.18.20, so this is a 4.19.x thing.
Maybe some change on the early kernel video driver,
or Lilo (I didn't test with grub or eLilo).

Kernel 4.19.11 here and I still have them on boot.

:scratch: I tested with generic and huge kernels, with NVidia and nouveau drivers (but I think these
don't matter) and still they are missing (8 of them :)).

Which boot manager do you use? Maybe it's a Lilo issue or hardware.

Just updated to 4.19.12 and still missing.

same here , with grub.

Thats probably a kernel bug, or config issue.

GRUB on 14.2

4.19.8 here and elilo i configured myself.. settings:
CONFIG_LOGO=y
# CONFIG_LOGO_LINUX_MONO is not set
# CONFIG_LOGO_LINUX_VGA16 is not set
CONFIG_LOGO_LINUX_CLUT224=y

No penguins :(

Thanks, I wouldn't like to change the boot loader to test this (bad experiences in the past).

I searched again in Google changing some words and the results are the same,
half wants to get rid of the image and half wants to change the image.

here is my config attached if you want to see if one of you can narrow it down to a .config option.

Thanks Pixxt! I diff'd your file and found 2 things I thought might be what was causing the problem. My .config had these two options set to =y and I set them to =N

CONFIG_FRAMEBUFFER_CONSOLE_DEFERRED_TAKEOVER
CONFIG_EXPERT

They're now # not set
# CONFIG_FRAMEBUFFER_CONSOLE_DEFERRED_TAKEOVER is not set

And I have penguins !!! :)
I can successfully and effectively use Slackware again with Tux inspiration

I think it's the framebuffer_console setting because I read other places that framebuffer has a lot to do with what happens with TUX at boot...
Cheers mates!!

Also, https://bugs.archlinux.org/task/60404