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 15.0 (started with 13.37). Testing -current in a spare partition.
Posts: 934
Rep:
Running 5.15 here too, NVidia 470.82.00 and VBox 6.1.28 drivers built OK, vhba module did not.
There is a blank screen about six seconds after lilo loads the kernel.
Code:
uname -a
Linux paulo.bfw 5.15.0 #1 SMP PREEMPT Sun Oct 31 18:50:25 -03 2021 x86_64 AMD FX-8320E Eight-Core Processor AuthenticAMD GNU/Linux
edit- There is a new version of vhba module (20211023) that builds OK.
Distribution: Slackware64-current with "True Multilib" and KDE4Town.
Posts: 9,152
Original Poster
Rep:
Year 2021, Round 74
Another batch of updates has been scheduled for release on Wednesday, 03 November 2021, at approximately 08:00, GMT. If no problems are found while testing the release candidates, they might be available sometime on Tuesday (depending on your time zone).
Distribution: Slackware64 {15.0,-current}, FreeBSD, stuff on QEMU
Posts: 459
Rep:
5.15 is looking OK here. I thought I might've gotten the "black screen" issue that was mentioned earlier in the thread, but I think it was just the new "simple framebuffer" setting. The screen went blank once initrd was loaded, and then it came back on about half-way through the rest of the boot process (basically, the part where the penguins show up onscreen didn't get displayed).
No big deal at the moment, but I'll turn "CONFIG_SYSFB_SIMPLEFB" off next release and see what happens.
That was fast!
Good news!
There should be a 5.15.1 released soon if I'm reading this correctly, http://lkml.iu.edu/hypermail/linux/k...0.3/07773.html
Plus one or two other problems that were reported after 5.15.0 was released.
That was fast!
Good news!
There should be a 5.15.1 released soon if I'm reading this correctly, http://lkml.iu.edu/hypermail/linux/k...0.3/07773.html
Plus one or two other problems that were reported after 5.15.0 was released.
I believe that the (future) packages of 5.15.x kernels should stay on /testing for some iterations, let's say until 5.14.x kernels goes EOL.
Because those LTS kernels are (in)famous of having lots of things pushed within, even they still have an uh-oh quality - see our past adventures with the initial releases of them.
Last edited by LuckyCyborg; 11-01-2021 at 08:51 AM.
Distribution: Slackware64 15.0 (started with 13.37). Testing -current in a spare partition.
Posts: 934
Rep:
Quote:
Originally Posted by pghvlaans
5.15 is looking OK here. I thought I might've gotten the "black screen" issue that was mentioned earlier in the thread, but I think it was just the new "simple framebuffer" setting. The screen went blank once initrd was loaded, and then it came back on about half-way through the rest of the boot process (basically, the part where the penguins show up onscreen didn't get displayed).
No big deal at the moment, but I'll turn "CONFIG_SYSFB_SIMPLEFB" off next release and see what happens.
That's what I have, should it explicitly set to off?
Code:
grep SYSFB_SIMPLEFB /usr/src/linux-5.15/.config
# CONFIG_SYSFB_SIMPLEFB is not set
I have not been seeing the black screen mentioned earlier. Using grub and an Nvidia card. Normal grub prompt comes up, I choose 5.15 and then I get a text line about loading the initrd and after a couple of seconds it boots as normal.
I've been using the "legacy" EFIFB until now, but with this option showing up in 5.15 I decided to give the simplefb a shot.
If you do set CONFIG_SYSFB_SIMPLEFB=y, make sure you also select its driver (CONFIG_DRM_SIMPLEDRM=y), otherwise you might end up without a framebuffer at all.
I haven't decided whether I'll stick with this or go back to using EFIFB. inteldrm takes over when it loads anyway, so it likely makes little difference either way.
Distribution: Slackware64 {15.0,-current}, FreeBSD, stuff on QEMU
Posts: 459
Rep:
Quote:
Originally Posted by GazL
If you do set CONFIG_SYSFB_SIMPLEFB=y, make sure you also select its driver (CONFIG_DRM_SIMPLEDRM=y), otherwise you might end up without a framebuffer at all.
Interesting. I have SYSFB_SIMPLEFB=y, and DRM_SIMPLEDRM=m was carried over from my 5.14 config. That probably explains it. Thanks for the tip!
LinuxQuestions.org is looking for people interested in writing
Editorials, Articles, Reviews, and more. If you'd like to contribute
content, let us know.
