SlackwareThis Forum is for the discussion of Slackware Linux.
Notices
Welcome to LinuxQuestions.org, a friendly and active Linux Community.
You are currently viewing LQ as a guest. By joining our community you will have the ability to post topics, receive our newsletter, use the advanced search, subscribe to threads and access many other special features. Registration is quick, simple and absolutely free. Join our community today!
Note that registered members see fewer ads, and ContentLink is completely disabled once you log in.
If you have any problems with the registration process or your account login, please contact us. If you need to reset your password, click here.
Having a problem logging in? Please visit this page to clear all LQ-related cookies.
Get a virtual cloud desktop with the Linux distro that you want in less than five minutes with Shells! With over 10 pre-installed distros to choose from, the worry-free installation life is here! Whether you are a digital nomad or just looking for flexibility, Shells can put your Linux machine on the device that you want to use.
Exclusive for LQ members, get up to 45% off per month. Click here for more info.
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?
I've checked that Arch post and it doesn't seem to apply to me.
Quote:
Originally Posted by config-generic-5.4.25.x64
CONFIG_LOGO=y
#CONFIG_FRAMEBUFFER_CONSOLE_DEFERRED_TAKEOVER is not set.
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.
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.
Do:
Code:
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).
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!
That's very interesting but I do have a framebuffer.
Code:
# 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.
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.
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.
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.
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.
LinuxQuestions.org is looking for people interested in writing
Editorials, Articles, Reviews, and more. If you'd like to contribute
content, let us know.