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

dr.s · 12-23-2018, 08:14 AM

Quote:

Originally Posted by Pixxt

Kernel 4.19.11 here and I still have them on boot.

Penguins missing since 4.19.12

Pixxt · 12-23-2018, 09:09 AM

Quote:

Originally Posted by tramtrist

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!!

Cool Beans!

Markus Wiesner · 12-23-2018, 10:04 AM

Quote:

Originally Posted by https://wiki.archlinux.org/index.php/silent_boot#Disabling_deferred_takeover

Disabling deferred takeover

If the new behavior leads to issues, you can disable deferred takeover by using the fbcon=nodefer kernel parameter.

This solves the "issue" ;-) with the missing penguins without recompiling the kernel (at least here, still with kernel 4.19.8).

For grub, set this in /etc/default/grub (and then update grub.cfg):

Code:

GRUB_CMDLINE_LINUX_DEFAULT="fbcon=nodefer"

For lilo, add this in /etc/lilo.conf (and then reinstall lilo):

Code:

append = "fbcon=nodefer"

cwizardone · 12-23-2018, 10:34 AM

Quote:

Originally Posted by Markus Wiesner

This solves the "issue" ;-) with the missing penguins without recompiling the kernel (at least here, still with kernel 4.19.8).

For grub, set this in /etc/default/grub (and then update grub.cfg):

Code:

GRUB_CMDLINE_LINUX_DEFAULT="fbcon=nodefer"

For lilo, add this in /etc/lilo.conf (and then reinstall lilo):

Code:

append = "fbcon=nodefer"

That works!
Many Thanks!

Paulo2 · 12-23-2018, 10:35 AM

Quote:

Originally Posted by Markus Wiesner

For lilo, add this in /etc/lilo.conf (and then reinstall lilo):

Code:

append = "fbcon=nodefer"

It works with lilo

penguins are back.

Thanks to all for tracking this, I will mark this as solved.

Aeterna · 12-27-2018, 04:53 PM

Intersting, because this option is not enabled by default if one runs config editor even when creating new .config file

Poprocks · 12-27-2018, 05:14 PM

I just wanted to mark this as a high priority bug. Having the penguins appear is VERY important. It's literally the only time my wife takes interest while I'm booting my Slack laptop...

mlangdn · 12-27-2018, 05:18 PM

Thanks for finding that Markus Wiesner!

bassmadrigal · 12-27-2018, 05:50 PM

Quote:

Originally Posted by tramtrist

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!!

I made this change earlier this week when I compiled my 4.19.12 kernel and disabling that actually knocked out my screen throughout the whole boot process. It didn't come up until KDE started (I have runlevel 4 as default and kdm is set to auto login for my user). I'll just live without the tux for now... I really don't reboot my computer much, so I'm not too worried.

1337_powerslacker · 12-27-2018, 10:44 PM

Quote:

Originally Posted by tramtrist

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!!

I'm happy to report that I also have my penguins back. There's just something so comforting about seeing an array of penguins displayed across the top of my screen...

Lysander666 · 12-28-2018, 03:26 AM

Where are these fabled penguins? Is it a line in LILO?

rkelsen · 12-28-2018, 03:40 AM

Do you use the frame buffer Lysander?

If not, then you won't see the penguins.

You can fix it with a "vga = xxx" line in your lilo.conf.

Look in the sample lilo config file for some suggestions.

Lysander666 · 12-28-2018, 03:58 AM

Quote:

Originally Posted by rkelsen

Do you use the frame buffer Lysander?

If not, then you won't see the penguins.

You can fix it with a "vga = xxx" line in your lilo.conf.

Look in the sample lilo config file for some suggestions.

Hmm so maybe the second line here needs to be uncommented on my desktop:

Code:

# VESA framebuffer console @ 1024x768x64k
#vga=791

Now, my netbook uses a 1024x600 screen, so according to allend it may be useful to use

Code:

video=inteldrmfb:mode=1024x600

in the "append= " string, in addition to using

Code:

# VESA framebuffer console @ 640x480x256
#vga=769

or similar.

Is there any technical purpose to these penguins other than their looking nice?

Paulo2 · 12-28-2018, 06:09 AM

Quote:

Originally Posted by Lysander666

Hmm so maybe the second line here needs to be uncommented on my desktop:

Code:

# VESA framebuffer console @ 1024x768x64k
#vga=791

Now, my netbook uses a 1024x600 screen, so according to allend it may be useful to use

Code:

video=inteldrmfb:mode=1024x600

in the "append= " string, in addition to using

Code:

# VESA framebuffer console @ 640x480x256
#vga=769

or similar.

Is there any technical purpose to these penguins other than their looking nice?

You could uncomment the line '#vga = ask', lilo will display a menu with (probably) supported screen resolutions.
I have a notebook with Intel video and it uses i915, but lilo doesn't support native resolution 1280x800.

On my desktop lilo supports native 1680x1050 and, with the NVidia driver, penguins always stay on top of the
screen, even if I login. Only with a screen reset they disapear.
(with nouveau the screen resets when it is loaded).

The penguin can be changed to some company logo, and there is one penguin for cpu or cpu core.
It is realy easy to change the logo, but I think there is some trick to make it with so smooth edges.
I tried some edits but it ends with rough edges.

Aeterna · 12-28-2018, 09:00 AM

Quote:

Originally Posted by Paulo2

You could uncomment the line '#vga = ask', lilo will display a menu with (probably) supported screen resolutions.
I have a notebook with Intel video and it uses i915, but lilo doesn't support native resolution 1280x800.

On my desktop lilo supports native 1680x1050 and, with the NVidia driver, penguins always stay on top of the
screen, even if I login. Only with a screen reset they disapear.
(with nouveau the screen resets when it is loaded).

The penguin can be changed to some company logo, and there is one penguin for cpu or cpu core.
It is realy easy to change the logo, but I think there is some trick to make it with so smooth edges.
I tried some edits but it ends with rough edges.

I replaced penguins with Slackware logo. It works even in virtual machine (with enabled 4 processors equals to four Slackware logos. If I would add more, then more penguins, if I removed processosrs, then less penguins). This is on laptop with Haswell

I never had an issue with the logo during boot. If someone had logo visible before 4.19.x, it still should be there unless default Slackware kernel was modified now to run in quiet mode and no penguins. The options added do nothing more than helps quiet boot.

Quote:

CONFIG_FRAMEBUFFER_CONSOLE_DEFERRED_TAKEOVER:

If enabled this defers the framebuffer console taking over the
console from the dummy console until the first text is displayed on
the console. This is useful in combination with the "quiet" kernel
commandline option to keep the framebuffer contents initially put up
by the firmware in place, rather then replacing the contents with a
black screen as soon as fbcon loads.