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.
Ditto for 5.15.12. The screen still goes blank for 6 - 7 seconds after the BIOS check.
FWIW, I haven't experienced this on my two -current installations (on an old P4 desktop and Core 2 Duo laptop) using any of the 5.{12,13,14,15}.x kernels built by Pat since I started trying -current out. I suppose this issue somehow depends on the system running it. I'm not sure whether this helps much, but it seems relevant.
Distribution: Slackware64-current with "True Multilib" and KDE4Town.
Posts: 9,139
Original Poster
Rep:
The blank screen on boot up has been reported on both AMD and Intel hardware, and systems using grub or lilo. I guess it is not consider a "problem" as there have been seven 5.15.rc releases, thirteen 5.15.x stable releases and seven 5.16-release candidates and nothing has been done.
The blank screen on boot up has been reported on both AMD and Intel hardware, and systems using grub or lilo. I guess it is not consider a "problem" as there have been seven 5.15.rc releases, thirteen 5.15.x stable releases and seven 5.16-release candidates and nothing has been done.
I've got 5.15.10 running on 2 Laptops with Intel 7-6820HQ CPU's and 1 server/PC with an AMD FX-6300
No black screens though I did have 1 desktop responsiveness issue (no keyboard/mouse action) on 1 of the Intel's and the AMD
Services were still responding, but for the most part they were frozen desktop wise
Distribution: Slackware64-current with "True Multilib" and KDE4Town.
Posts: 9,139
Original Poster
Rep:
FWIW: Twice since installing the 5.15.12 kernel and while streaming video in Firefox, I've been thrown back to the prompt (init 3). Just booted the 5.16-rc7 kernel and we'll see how it goes.
On my pinebook pro I get a black screen that is clearly powered on after a fresh installation. The boot loader loads a bunch of output, but once the kernel starts booting, the screen goes off. The serial console is still accessible and so is a remote shell. I am building a 5.15.10 kernel to see if rolling back from 5.15.12 fixes this. None of my other arm machines have this problem. There are a few other things it could be though.
EDIT: It turned out to be something entirely different with the same result, black screen.
The blank screen on boot up has been reported on both AMD and Intel hardware, and systems using grub or lilo. I guess it is not consider a "problem" as there have been seven 5.15.rc releases, thirteen 5.15.x stable releases and seven 5.16-release candidates and nothing has been done.
Only one of my machines (the only non-efi one) exhibited this. I got around it by adding a line to /etc/default/grub:
That last line tells grub to use the same graphics resolution for the initial (penguin) screen as it does for the grub menu screen. Efi machines (at least, mine) don't seem to need this, but my only remaining non-efi one did.
This is "interesting", but how are you going to keep the
kernel/sched/per_task_area_struct_defs.h and struct task_struct_per_task
definition in sync? It seems that you manually created this (which is
great for testing), but over the long-term, trying to manually determine
what needs to be done here to keep everything lined up properly is going
to be a major pain.
That issue aside, I took a glance at the tree, and overall it looks like
a lot of nice cleanups. Most of these can probably go through the
various subsystem trees, after you split them out, for the "major" .h
cleanups. Is that something you are going to be planning on doing?
That last line tells grub to use the same graphics resolution for the initial (penguin) screen as it does for the grub menu screen. Efi machines (at least, mine) don't seem to need this, but my only remaining non-efi one did.
I have no idea why this works, but it did!
--
Pete
Is there similar for that option in Lilo?
I think the blank screen is due to some change in the VESA framebuffer, or something,
because if I boot in VGA mode (80x25), the kernel messages appear right after Lilo loads the kernel.
Any VESA resolution causes the blank screen delay.
I realized that, before the "long" blank screen delay, with the older kernels there was a delay too but it was something less than 2 seconds,
so before one starts thinking "hey, what is this blank screen delay?" kernel messages were showing already.
edit- long blank screen delay still happens with 5.16-rc8
LinuxQuestions.org is looking for people interested in writing
Editorials, Articles, Reviews, and more. If you'd like to contribute
content, let us know.
