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.
Distribution: Slackware64-current with "True Multilib" and KDE4Town.
Posts: 9,105
Original Poster
Rep:
Quote:
Originally Posted by 3rensho
Kernel-5.15.7 built and running with Nvidia-470.86. No problems so far.
Ditto, plus VirtualBox-6.1.30-148432.
After 7 release candidates and 8 stable releases the 6-8 second blank screen after the BIOS check is still with us. Ditto with 5.16-rc1 through 4.
Other than that, everything I do on the computer works as it should.
Kernel-5.15.7 built and running with Nvidia-470.86. No problems so far.
Same here with nvidia-304.137.
Quote:
Originally Posted by cwizardone
... After 7 release candidates and 8 stable releases the 6-8 second blank screen after the BIOS check is still with us. Ditto with 5.16-rc1 through 4.
Other than that, everything I do on the computer works as it should.
I've seen some mention of this phenomenon, but have yet to see it myself.
When you say "BIOS check," I take it you are referring to the messages that appear at the top of the screen after LILO:
Code:
Loading vmlinuz-generic.. ...
BIOS data check successful
?
If so, then I can confirm that I have yet to experience the blank-screen problem after any of the kernel updates, including the latest.
This would lead me to surmise that this behavior is somehow hardware (GPU?) specific. At any rate, it would appear that it's not universal. I have two -current installs--one on metal and one VM--and neither of them go blank after the BIOS check.
Distribution: Slackware64-current with "True Multilib" and KDE4Town.
Posts: 9,105
Original Poster
Rep:
Quote:
Originally Posted by JayByrd
......I've seen some mention of this phenomenon, but have yet to see it myself.
Quote:
Originally Posted by cwizardone View Post
... After 7 release candidates and 8 stable releases the 6-8 second blank screen after the BIOS check is still with us. Ditto with 5.16-rc1 through 4.
When you say "BIOS check," I take it you are referring to the messages that appear at the top of the screen after LILO:
Code:
Loading vmlinuz-generic.. ...
BIOS data check successful
Correct.
At first I thought it might have something to do with LILO, but, then, someone reported the same problem with Grub2.
This box has a Ryzen CPU and a Nvidia GPU.
Edit in: I just rebooted to double check and it simply says,
Then 3 lines, screen wide of dots (periods), then the BIOS check message and then 6 seconds or so of a blank screen.
If we eliminate the kernel and lilo
There remains nvidia
Did you try only with the stock kernel driver "nouveau" ?
The behavior is the same with or without the Nvidia driver.
Well, this answers preemptively what was going to be my next question!
For the record, I was going to ask if you include the nvidia module in your initrd. (I don't, I just allow the system to load it normally during boot-up.)
Given that it behaves the same with or without nvidia, I'm at a loss. I guess the only other avenue I can think of to explore would be to try to find out if other users who are experiencing the blank-screen problem are also on Ryzen hardware...
FWIW I had to revert to building 5.4.164 on my ancient Thinkpad T61p in order to get nvidia .run proprietary installer to complete. 5.15.x kernels boot just fine but v304 (and a sketchy 340) drivers (needed for the old Quadro FX570 chip) won't build for me on 5.15.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.
