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: 925
Rep:
The last two kernels 5.8 (.9 and .10) seem problematic with my wired network interface, Realtek RTL8168.
It doesn't connect when coming back from suspend, I have to unload the module and load it again to fix.
With the stock -current kernels 5.4.x that don't happen, they are working OK.
I was just looking at the specs. Very nice! Congrats!
While waiting for the 5.9.y kernel, you might consider the 5.8.y series.
The 5.8.10 kernel is installed here using "up to the minute" -current,
f2fs on the SSD,
ext4 on the HD,
removed ConsoleKit2,
installed elogind-243.7-x86_64.
upgraded to upower-0.99.11-x86_64,
using wine-5.6-x86_64-1alien.txz
and
VirtualBox-6.1.14-140239-Linux_amd64.run.
It has been running for the last 24 hours hours with no hiccups, coughs or sneezes.
Nice and thanks... I think. I'm actually having problems with Z490s that I've never encountered in hundreds of builds with older chipsets. I have owned and worked on dozens of SuperMicro server systems and got really excited to discover several years ago that they were entering the "Enthusiast" market (with absolute Linux support) while keeping that extreme server quality, but I've had deal breaker problems with -- C9Z490-PGW -- The debugging BIOS/UEFI is incredible but I have to wonder how much all those automated features may affect reliability. Its' likely going to be awhile before I find out. RMA is slow.
In the meantime I bought another Z490 for a "known good" just to make certain the faults have been in the mobo and not my doing. I had to spend $100 more with Asus (Maximus Hero) to get the same quality albeit with more features. It booted like a scalded cat today but is now having some POST problem driving me nuts. Tomorrow I pare down and troubleshoot.
Yunhai Zhang recently fixed a VGA software scrollback bug in commit
ebfdfeeae8c0 ("vgacon: Fix for missing check in scrollback handling"), but that then made people look more closely at some of this code, and there were more problems on the vgacon side, but also the fbcon software scrollback.
We don't really have anybody who maintains this code - probably because nobody actually _uses_ it any more. Sure, people still use both VGA and the framebuffer consoles, but they are no longer the main user interfaces to the kernel, and haven't been for decades, so these kinds of extra features end up bitrotting and not really being used.
So rather than try to maintain a likely unused set of code, I'll just aggressively remove it, and see if anybody even notices. Maybe there are people who haven't jumped on the whole GUI badnwagon yet, and think it's just a fad. And maybe those people use the scrollback code.
If that turns out to be the case, we can resurrect this again, once we've found the sucker^Wmaintainer for it who actually uses it.
I noticed, so thanks for that Linus!
I guess I'll just have to adapt to it's absence and start using screen/tmux on the consoles from now. Scrollback wasn't maintained over a console swap anyway, so it always had its limitations, but I did use it a lot. Can't believe I'm the only one.
Distribution: Slackware64-current with "True Multilib" and KDE4Town.
Posts: 9,045
Original Poster
Rep:
Quote:
Originally Posted by GazL
Just a heads up, looks like 5.8.10 Got rid of console scrollback:
I noticed, so thanks for that Linus!
I guess I'll just have to adapt to it's absence and start using screen/tmux on the consoles from now. Scrollback wasn't maintained over a console swap anyway, so it always had its limitations, but I did use it a lot. Can't believe I'm the only one.
Can you post a message expressing your opinion to a message board where it might get Mr. Torvalds' attention? If enough people let him know they use the feature, he might be persuaded to change his mind.
Last edited by cwizardone; 09-19-2020 at 10:09 AM.
This appears to have been a "it's already broken in several ways, so lets just remove it" decision, and I don't necessarily disagree with that choice. I can adapt, and if it makes the console code cleaner, then so be it.
Mostly I was just posting so that others wouldn't suddenly go "Hey, why is shift-pageup not working!" and have to dig around to find out... like I just had to.
.....The one thing that does show up in the diffstat is the softscroll
removal (both fbcon and vgacon), and there are people who want to save
that, but we'll see if some maintainer steps up. I'm not willing to
resurrect it in the broken form it was in, so I doubt that will happen
in 5.9, but we'll see what happens.....
Last edited by cwizardone; 09-20-2020 at 07:12 PM.
We have a more serious trouble at kernel with time and date, to 100 year's at BIOS and age dimension.
Ex: ISO 8601; date --rfc-3339=ns; and much more. BIOS date diapason.
Did you mean: You satellite work at space with Linux many years ?
But i use scrollback but not regular but every day.
Last edited by Roman Dyaba; 09-21-2020 at 03:33 AM.
Reason: i leak word
We have a more serious trouble at kernel with time and date, to 100 year's at BIOS and age dimension.
Ex: ISO 8601; date --rfc-3339=ns; and much more. BIOS date diapason.
Did you mean: You satellite work at space with Linux many years ?
But i use scrollback but not regular but every day.
I don't understand at all what you mean. English is a second language for me but this time deepl.com didn't help.
Distribution: Slackware64-current with "True Multilib" and KDE4Town.
Posts: 9,045
Original Poster
Rep:
Year 2020, Round 59.
Another batch of kernel updates has been scheduled for release on Wednesday, 23 September 2020, at approximately 16:00, GMT. If no problems are found while testing the release candidates, they might be available sometime on Tuesday (depending on your time zone).
Seems fine here (just tested on slackware64-14.2) not much to report, skipped a few 4.14.x releases this year, bumped it to 4.14.199 now and nothing broke.
Distribution: VM Host: Slackware-current, VM Guests: Artix, Venom, antiX, Gentoo, FreeBSD, OpenBSD, OpenIndiana
Posts: 1,001
Rep:
Quote:
Originally Posted by cwizardone
5.8.11 aborted about 2/3 of the way through the process with the following error,
Maybe there is a problem with your config or added drivers?
I don't remember issues with kernel compilation for very long time. 5.8.11 compiled just fine on Slackware-current and Gentoo (so far)
LinuxQuestions.org is looking for people interested in writing
Editorials, Articles, Reviews, and more. If you'd like to contribute
content, let us know.