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.
So things have been pretty calm, and rc8 is fairly small. I'm still
waiting for a networking pull with some fixes, so it's not like I
could have made a final 5.9 release even if I had wanted to, but there
was nothing scary going on this past week, and it all feels ready for
a final 5.9 next weekend........
Last edited by cwizardone; 10-04-2020 at 06:21 PM.
Distribution: Slackware64-current with "True Multilib" and KDE4Town.
Posts: 9,136
Original Poster
Rep:
Year 2020, Round 62.
Another batch of kernel updates has been scheduled for release on Wednesday, 07 October 2020, at approximately 14:00, GMT. If no problems are found while testing the release candidates, they might be available sometime on Tuesday (depending on your time zone).
Linux 5.9
From: Linus Torvalds
Date: Sun Oct 11 2020 - 17:30:29 EST
Ok, so I'll be honest - I had hoped for quite a bit fewer changes this
last week, but at the same time there doesn't really seem to be
anything particularly scary in here. It's just more commits and more
lines changed than I would have wished for.
The bulk of this is the networking fixes that I already mentioned as
being pending in the rc8 release notes last weekend. In fact, about
half the patch (and probably more of the number of commits) is from
the networking stuff (both drivers and elsewhere).
Outside of that, the most visible thing is a reinstatement of the
fbdev amba-clcd driver - that's a noticeable patch, but it's basically
just mainly a revert.
The rest is really really tiny (mostly some other minor driver
updates, but some filesystem and architecture fixes too). There's just
a bit more of those kinds of tiny details than there should be fo this
kind of last delayed week. But since nothing in there gives me any
particular reason to delay another week, here we are.
That obviously means that the merge window for 5.10 is open, and I'll
start doing those pulls tomorrow. I already have a couple of pulls
pending, but I hope people take the time to just do one last test of
the final 5.9 release.
So go get it.
Linus
---
Last edited by cwizardone; 10-12-2020 at 08:01 AM.
5.9 has dropped. I built it and it boots fine (gcc-10.2.0). Tried building nvidia module but that failed with NVIDIA-Linux-x86_64-450.80.02.run and NVIDIA-Linux-x86_64-455.28.run. Back to running 5.8.14.
With both drivers the build crashed with the error message that there was a version mismatch between the gcc version that the kernel was built with and the version that I built the driver with. I have been using only gcc-10.2.0 to build everything since it was released so me thinks some tweak is needed.
Edit: Did some further reading and it sounds like there is a dust-up between the kernel people and Nvidia. I guess the nouveau driver option is available but have never used it and will have to see how to set it up.
Distribution: Slackware64-current with "True Multilib" and KDE4Town.
Posts: 9,136
Original Poster
Rep:
The 5.9 tarball from https://git.kernel.org/pub/scm/linux...able/linux.git
compiled properly and is running well with the nouveau driver. No virtualbox, yet,
of course. So far, everything I do on the computer (except virtualbox) works as it
should.
The tarball from https://cdn.kernel.org/pub/linux/ker...nux-5.9.tar.xz
did not build. It stopped, just short of finishing, without an error. When
I tried to run "make modules_install" it returned the, "no file or directory
by that name" error.
Distribution: Slackware64-current with "True Multilib" and KDE4Town.
Posts: 9,136
Original Poster
Rep:
Year 2020, Round 63.
Another batch of kernel updates has been scheduled for release on Wednesday, 14 October 2020, at approximately 13: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-current with "True Multilib" and KDE4Town.
Posts: 9,136
Original Poster
Rep:
Quote:
Originally Posted by cwizardone
The 5.9 tarball from https://git.kernel.org/pub/scm/linux...able/linux.git
compiled properly and is running well with the nouveau driver. No virtualbox, yet,
of course. So far, everything I do on the computer (except virtualbox) works as it
should............
Development snapshot, VirtualBox-6.1.97-140861-Linux_amd64.run works with the 5.9 kernel.
Distribution: VM Host: Slackware-current, VM Guests: Artix, Venom, antiX, Gentoo, FreeBSD, OpenBSD, OpenIndiana
Posts: 1,011
Rep:
Quote:
Originally Posted by cwizardone
The 5.9 tarball from https://git.kernel.org/pub/scm/linux...able/linux.git
compiled properly and is running well with the nouveau driver. No virtualbox, yet,
of course. So far, everything I do on the computer (except virtualbox) works as it
should.
The tarball from https://cdn.kernel.org/pub/linux/ker...nux-5.9.tar.xz
did not build. It stopped, just short of finishing, without an error. When
I tried to run "make modules_install" it returned the, "no file or directory
by that name" error.
That is the second time I've had trouble compiling a kernel in a terminal. Both times it was in Konsole in KDE4.
Never a problem when compiling from the prompt (out of X).
FWIW, the 5.9 kernel has been running for 24 hours now without a cough, hiccup or sneeze.
Last edited by cwizardone; 10-13-2020 at 08:57 AM.
Distribution: Slackware64 15.0 (started with 13.37). Testing -current in a spare partition.
Posts: 932
Rep:
Quote:
Originally Posted by cwizardone
Both times it was in Konsole in KDE4.
Never a problem when compiling from the prompt (out of X).
Could it be that $TERM problem?
In konsole mine is TERM=xterm and the kernel builds ok. (though for slackpkg
I have to run with TERM=konsole)
Compiling in other terminal (XFCE or xterm) it crashes too?
Distribution: Slackware64-current with "True Multilib" and KDE4Town.
Posts: 9,136
Original Poster
Rep:
Quote:
Originally Posted by Paulo2
Could it be that $TERM problem?
In konsole mine is TERM=xterm and the kernel builds ok. (though for slackpkg
I have to run with TERM=konsole)
Compiling in other terminal (XFCE or xterm) it crashes too?
LinuxQuestions.org is looking for people interested in writing
Editorials, Articles, Reviews, and more. If you'd like to contribute
content, let us know.
Could it be that $TERM problem?
