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.
Apologies for the delay. Went out before sunrise for some exercise, tripped on a curb and landed on my face. Nothing broken, but I do have a seriously bruised ego.
Last edited by cwizardone; 10-13-2021 at 03:08 PM.
[QUOTE=cwizardone;6291741} tripped on a curb and landed on my face. Nothing broken, but I do have a seriously bruised ego.
[/QUOTE]
I will wager the first thing you did was look to see if anyone was watching LOL
Seriously hope all is well.
john
Distribution: Slackware64-current with "True Multilib" and KDE4Town.
Posts: 9,107
Original Poster
Rep:
Quote:
Originally Posted by AlleyTrotter
I will wager the first thing you did was look to see if anyone was watching.....
Thanks for asking.
Nah. No one around at that time of the morning. Somehow managed to scrap the knuckles on one hand and now a couple of ribs are starting to complain. I've been waiting for the left side of my face to turn black and blue and then I'll really start to look like I was in fight..... Nah, not at my age.... Haven't participated in a good old fashion bar brawl since I was in the Service.
Edit in: Built, installed and so far, so good. It still blanks the screen for 7-8 seconds on boot up, as previously mentioned, but everything else is just fine.
While upgrading from 5.14.11 to 5.14.12, I noticed a new addition to the config file -
Code:
# CONFIG_FB_SIMPLE is not set
I notice this was previously introduced in the 5.15-rc series. Wonder if thats what has been causing your blank screens, the associated menu help text states -
Code:
Say Y if you want support for a simple frame-buffer.
This driver assumes that the display hardware has been initialized before the kernel boots, and the kernel will simply render to the pre-allocated frame buffer surface.
Configuration re: surface address, size, and format must be provided through device tree, or plain old platform data.
While upgrading from 5.14.11 to 5.14.12, I noticed a new addition to the config file -
Code:
# CONFIG_FB_SIMPLE is not set
Strange; that's not what I see:
Code:
$ grep FB_SIMPLE config*
config-generic-5.14.10.x64:# CONFIG_FB_SIMPLE is not set
config-generic-5.14.11.x64:# CONFIG_FB_SIMPLE is not set
config-generic-5.14.12.x64:# CONFIG_FB_SIMPLE is not set
config-generic-5.14.2.x64:# CONFIG_FB_SIMPLE is not set
config-generic-5.14.3.x64:# CONFIG_FB_SIMPLE is not set
config-generic-5.14.4.x64:# CONFIG_FB_SIMPLE is not set
config-generic-5.14.5.x64:# CONFIG_FB_SIMPLE is not set
config-generic-5.14.6.x64:# CONFIG_FB_SIMPLE is not set
config-generic-5.14.7.x64:# CONFIG_FB_SIMPLE is not set
config-generic-5.14.8.x64:# CONFIG_FB_SIMPLE is not set
config-generic-5.14.9.x64:# CONFIG_FB_SIMPLE is not set
$ grep FB_SIMPLE config*
config-generic-5.14.10.x64:# CONFIG_FB_SIMPLE is not set
config-generic-5.14.11.x64:# CONFIG_FB_SIMPLE is not set
config-generic-5.14.12.x64:# CONFIG_FB_SIMPLE is not set
config-generic-5.14.2.x64:# CONFIG_FB_SIMPLE is not set
config-generic-5.14.3.x64:# CONFIG_FB_SIMPLE is not set
config-generic-5.14.4.x64:# CONFIG_FB_SIMPLE is not set
config-generic-5.14.5.x64:# CONFIG_FB_SIMPLE is not set
config-generic-5.14.6.x64:# CONFIG_FB_SIMPLE is not set
config-generic-5.14.7.x64:# CONFIG_FB_SIMPLE is not set
config-generic-5.14.8.x64:# CONFIG_FB_SIMPLE is not set
config-generic-5.14.9.x64:# CONFIG_FB_SIMPLE is not set
Oh weird, I saw it by doing a diff between the old and new config when upgrading kernels.
Code:
< # Linux/x86 5.14.12 Kernel Configuration
---
> # Linux/x86 5.14.11 Kernel Configuration
3228d3227
< # CONFIG_FB_SIMPLE is not set
I guess my config file through out the years just never had it manfest since this last make menuconfig.
But you are right, looking on catee it says - found in Linux kernels: 3.15–3.19, 4.0–4.20, 5.0–5.14, 5.15-rc+HEAD.
Distribution: Slackware64-current with "True Multilib" and KDE4Town.
Posts: 9,107
Original Poster
Rep:
Year 2021, Round 71
Another batch of updates has been scheduled for release on Saturday, 16 October 2021, at approximately 14:00, GMT. If no problems are found while testing the release candidates, they might be available sometime on Friday (depending on your time zone).
I always get nervous when I see too many rc's in the stable branch: on the one hand, it shows that they're doing their due-diligence, but on the other, it plants that seed of doubt: "why are they changing their minds about what to include... don't they know?!". Human psychology is a funny thing.
My thoughts exactly:
Either you know what you are doing but you try too much and too soon (=bad)
Or, You assume and then assume wrongly - resulting in broken builds (=bad)
Either way i want our quick and simple releases back.
the 5.15.y won't sadly be stable until later (crystal_ball_voyance) and will possibly have a short life time too, let's hope i'm proven all wrong
LinuxQuestions.org is looking for people interested in writing
Editorials, Articles, Reviews, and more. If you'd like to contribute
content, let us know.