-   Slackware (
-   -   Where have my penguins gone? (

hazel 03-27-2020 05:59 AM

Where have my penguins gone?
I switched to the Current kernel (5.4.24) to test out a program that was misbehaving (more info here if you're interested). I'm too lazy to go through all the palaver of switching back again. But I miss the four penguins that used to appear after the kernel had loaded.

What happened to them? Did Pat decide they were too frivolous?

cwizardone 03-27-2020 06:45 AM

I just rebooted to double check and they are still there.

hazel 03-27-2020 06:48 AM

So where have mine gone? Apart from that everything seems to function normally.

Paulo2 03-27-2020 06:49 AM

I can see them here too. I'm running 5.4.28 now but they were there with 5.4.24 (IIRC).
Take a look at this, but it is old from 2018.

Maybe it is something with the early video driver, they disappear with screen refresh.

cwizardone 03-27-2020 06:55 AM

Thanks for that. I had forgotten all about it, but, then, these days I'm lucky I remember my own name. :scratch:

hazel 03-27-2020 06:58 AM

I've checked that Arch post and it doesn't seem to apply to me.

Originally Posted by config-generic-5.4.25.x64

I must check next time what actually is the first thing that appears. It used to be the cpu penguins and then the names of the modules loaded from the initrd.

mrclisdue 03-27-2020 08:10 AM


Originally Posted by hazel (Post 6104898)

I'm at the age (and mindset) that, try as I may, I don't learn something new everyday.

Today I did, thank you.


pchristy 03-27-2020 10:12 AM

Hazel: Are you running a recent UEFI machine and using ELILO? If so the problem may be related to this.

Some newer machines use 64-bit addressing for the efifb, and this can cause problems. Basically, it means you have no framebuffer until KMS kicks in.


dmesg | grep efifb
and see what you get.

If you get an error message (invalid address, or similar) you will need to switch to grub as a bootloader. Grub supports 64-bit efifb. elilo doesn't. I'm not sure what the position is with lilo, as all my UEFI machines use either elilo (for older graphics chips) or grub (for newer ones).

This bug can also cause the installer to hang if you are running recent Intel graphics. It took me a long time to find the cause!

That link will show you how to get the installer to work. I've only just managed to get grub working the way I want on my laptop (Intel 620 graphics), so I'm not in a position to write up a "HowTo" on that! Slackware's grub implementation seems to be somewhat different to the way a Google search implies (no grub-update), but is otherwise not too bad to grapple with. Just different! ;)


hazel 03-27-2020 10:22 AM

That's very interesting but I do have a framebuffer.

# dmesg|grep efifb
[    0.603008] pci 0000:00:02.0: BAR 2: assigned to efifb
[    1.452864] efifb: probing for efifb
[    1.452886] efifb: framebuffer at 0xa0000000, using 3072k, total 3072k
[    1.452888] efifb: mode is 1024x768x32, linelength=4096, pages=1
[    1.452889] efifb: scrolling: redraw
[    1.452891] efifb: Truecolor: size=8:8:8:8, shift=24:16:8:0

If I didn't, presumably I wouldn't have seen any penguins with the old kernel either. This is an old machine btw. I'm neither a gamer nor a media fiend so I don't see why I should fork out money on new hardware with capacities that I don't need.

I haven't looked at the Slackware GRUB but, given the Slack philosophy, I'd be surprised if it came festooned with all those automated scripts that make GRUB so complicated in other distros.

pchristy 03-27-2020 10:31 AM

Ah! OK, if you have a framebuffer, its not the same problem then!

Usually, its the framebuffer that kicks in before kms that puts the penguins up. I wasn't getting any penguins or the first part of the boot messages. I only started seeing stuff when kms kicked in. And when trying to install, it froze solid as soon as the initrd had loaded - again, presumably due to the absence of a framebuffer.

Are you seeing the initial part of the boot screen? The messages where you would normally see the penguins? And does the resolution change once kms arrives? That may give you a clue.

Also I note you say you are using the -current kernel, but not -current? That may have something to do with it. It might be worth compiling the kernel yourself using the config from -current. -current has diverged a *long* way from 14.2 now, and you may be missing something that the -current kernel expects.


hazel 03-27-2020 10:35 AM

Or I could just go back to the old kernel. There's no longer any particular reason to use this one.

All the same, I do want to try and see if I can identify the first output from this kernel at boot.

pchristy 03-27-2020 10:40 AM

Yes, I lived without the penguins and initial boot screen on my laptop, because it still worked. But with Slackware-15 on the horizon, I wanted to get the installer to work, as I had to install via LiveSlack to get it on this laptop.

Once I discovered the problem and got it sorted, the current "self isolation" has given me the opportuntiy to play with grub and get it to work as I want on the offending laptop.

Its an ill-wind.....! ;)


hazel 03-28-2020 08:53 AM

I carefully checked my boot messages this morning. The first thing to come up was the modules loading from the initrd. That used to be the first thing that came up after the cpu count and display. So it's not a whole stash of stuff that has vanished, just the 4 penguins.

tramtrist 03-28-2020 09:15 AM

My penguins always disappear after i915 loads from initrd. If I re-compile i915 into the kernel with the framebuffer flag it loads all the way from boot til I start X.

Richard Cranium 03-28-2020 05:50 PM

Nobody responded with "Antarctica"?

All times are GMT -5. The time now is 04:17 AM.