The Latest Kernel Release.

gegechris99 · 10-19-2018, 12:45 PM

Quote:

Originally Posted by mralk3

The easiest way is to go to https://packages.slackware.com/ and search for the package you want. Download it from the links provided.

Then I suggest you use "installpkg" to install it, and update your lilo settings, reboot. If all looks good, use "removepkg" on the kernel package from Slackware stable.

You need the kernel-generic and kernel-modules packages from -current. I would suggest to keep the kernel from stable Slackware and make two entries in lilo.conf: one for the -current version and one for the stable Slackware version.

Lysander666 · 10-19-2018, 12:56 PM

Quote:

Originally Posted by gegechris99

You need the kernel-generic and kernel-modules packages from -current.

That's funny because I've never had to do that. And in that case why are all the necessary files inside the stable kernel folder[s]?

I'm getting confused now, and I bet overlock is too.

He asked for stable. In which case, he either needs 64bit stable kernel or 32bit.

What you're saying may indeed have some import, but I think at this point such advice risks confusing the poor chap. Nice to see you here though, gegechris99, I found your blog post on persistent naming absolutely invaluable.

mralk3 · 10-19-2018, 01:20 PM

The original request was asking how to install the generic kernel from Slackware-current on a Slackware 14.2 (stable) system. I think that is the confusion because overlock didn't word his question very well. Maybe I am wrong?

Lysander666 · 10-19-2018, 01:29 PM

Quote:

Originally Posted by mralk3

The original request was asking how to install the generic kernel from Slackware-current on a Slackware 14.2 (stable) system. I think that is the confusion because overlock didn't word his question very well. Maybe I am wrong?

Yes, it's an odd question, now I look at it again. He appears to want to install the 4.14 -current generic kernel on stable. Sounds like an odd request, but the question is worded poorly.

gegechris99 · 10-19-2018, 01:33 PM

Quote:

Originally Posted by mralk3

The original request was asking how to install the generic kernel from Slackware-current on a Slackware 14.2 (stable) system.

That was also my understanding. That's why I suggested to grab the kernel-generic and kernel-modules packages from -current. These are minimal -current packages you need to install if you want to run the -current generic kernel in Slackware 14.2. That's what I do on my system to take advantage of better scaling governor management for my CPU in 4.14 kernel (refer to this thread suggestion-use-performance-cpu-frequency-governor for more details)

Granted, I do not compile packages that depend on the kernel version.

Quote:

Originally Posted by Lysander666

Nice to see you here though, gegechris99, I found your blog post on persistent naming absolutely invaluable.

Thanks for the kind word.

overlock · 10-19-2018, 05:01 PM

Thanks for the personal help, this is exactly what I wanted to install version 4.14 of the kernel in my stable slackware and I was able to succeed with thanks.

cwizardone · 10-20-2018, 06:20 AM

Kernel updates 4.18.16, 4.14.78, 4.9.135 and 4.4.162 are now available at,

https://www.kernel.org/

The change logs,

https://cdn.kernel.org/pub/linux/ker...ngeLog-4.18.16

https://cdn.kernel.org/pub/linux/ker...ngeLog-4.14.78

https://cdn.kernel.org/pub/linux/ker...ngeLog-4.9.135

https://cdn.kernel.org/pub/linux/ker...ngeLog-4.4.162

Dave's Unofficial Slackbuilt Kernel updates for the 4.4.xxx and 4.18.xx series
can be found at, https://dusk.idlemoor.tk

The 4.19 Stable and LTS kernel should be released tomorrow, Sunday.

Edit in: The dusk-4.18.16 kernel is installed and running as advertised with -current (up to the moment) and the Nvidia-410.66 driver.
BTW, I was looking through the 4.18.16 change log and see Mr. Torvalds has returned.

mralk3 · 10-20-2018, 07:05 AM

Quote:

Originally Posted by cwizardone

The 4.19 Stable and LTS kernel should be released tomorrow, Sunday.

I do remember what happened with 4.14.0, but we can hope that our BDFL adds 4.19.0 to -current by the end of the day!

cwizardone · 10-20-2018, 09:02 AM

Quote:

Originally Posted by mralk3

I do remember what happened with 4.14.0......

Yes, remember that well.

But, FWIW, I built and installed the 4.19-rc6 and -rc7 kernels and didn't have any problems, so maybe we'll get lucky this time.

AlleyTrotter · 10-22-2018, 07:46 AM

building 4.19 now.
Somewhat disappointed as I expected 5.0 with Linus' return from exile
AlleyTrotter

mralk3 · 10-22-2018, 08:34 AM

I was about to build 4.19 and found https://dusk.idlemoor.tk/ to already contain a package for it. Thanks idlemoor!

cwizardone · 10-22-2018, 09:30 AM

Here is Greg K-H's announcement,
Note the last paragraph. I added the bold emphasis.

Quote:

Linux 4.19
Greg KH
Date: Mon Oct 22 2018 - 03:34:02 EST

Hi everyone!

It's been a long strange journey for this kernel release...

While it was not the largest kernel release every by number of commits,
it was larger than the last 3 releases, which is a non-trivial thing to
do. After the original -rc1 bumps, things settled down on the code side
and it looks like stuff came nicely together to make a solid kernel for
everyone to use for a while. And given that this is going to be one of
the "Long Term" kernels I end up maintaining for a few years, that's
good news for everyone.

A small trickle of good bugfixes came in this week, showing that waiting
an extra week was a wise choice. However odds are that linux-next is
just bursting so the next -rc1 merge window is going to be bigger than
"normal", if there is such a thing as "normal" for our rate of
development.

And speaking of development, there's that other thing that happened this
release cycle, that ended up making it such that I'm the one writing
this instead of Linus. Allow me the guilty pleasure of taking a few
minutes to talk about that....

I've been giving my "How the kernel is developed" talk all around the
world for over a decade now. After the first year or so, I was amazed
that it kept needing to be given as surely everyone knew how we did this
type of thing, right? But my wife, someone much smarter than I, then
told me, "Every year there is a new kindergarten class."

And we all need to remember that, every year new people enter our
community with the goal, or requirement, to get stuff done for their
job, their hobby, or just because they want to help contribute to the
tool that has taken over the world and enabled everyone to have a solid
operating system base on which to build their dreams.

And when they come into our community, they don't have the built-in
knowledge of years of experience that thousands of us already do.
Without that experience they make mistakes and fumble and have to learn
how this all works. Part of learning how things work is dealing with
the interaction between people, and trying to understand the basic
social norms and goals that we all share. By providing a document in
the kernel source tree that shows that all people, developers and
maintainers alike, will be treated with respect and dignity while
working together, we help to create a more welcome community to those
newcomers, which our very future depends on if we all wish to see this
project succeed at its goals.

And that goal we all share is the key here. We _ALL_ want to create the
best kernel that we possibly can. We can disagree on lots of different
things in other parts of our lives, but we do share this one thing. And
we should focus on that shared goal as it has pulled us all together in
a way that has enabled us to create something that no other company or
group of people has ever been able to accomplish.

We used to joke that our goal was "Total World Domination", but it
really wasn't a joke. We achieved that goal, Linux really does rule the
world. All companies use it, contribute to it, and it has ended up
making the world a much better place because of all of us working on it.

In these talks I give, I also say that "the only thing that can stop us
is ourselves, it is up to us to mess this up." And that's truer now
than when I first started saying that a decade ago. There is no other
operating system out there that competes against us at this time. It
would be nice to have something to compete against, as competition is
good, and that drives us to do better, but we can live with this
situation for the moment

These past few months has been a tough one for our community, as it is
our community that is fighting from within itself, with prodding from
others outside of it. Don't fall into the cycle of arguing about those
"others" in the "Judean People's Front" when we are the "We're the
People's Front of Judea!" That is the trap that countless communities
have fallen into over the centuries. We all share the same goal, let us
never loose sight of that.

So here is my plea to everyone out there. Let's take a day or two off,
rest, relax with friends by sharing a meal, recharge, and then get back
to work, to help continue to create a system that the world has never
seen the likes of, together.

Personally, I'm going to take my own advice. I'll be enjoying this week
in Edinburgh with many other kernel developers, drinking some good
whiskey, and taking some time off of reading email, by spending it with
the great friends I have made in this community.

And with that, Linus, I'm handing the kernel tree back to you. You can have the joy of dealing with the merge window

thanks,

greg k-h

P.S. Here's the shortlog from 4.19-rc8 to 4.19 for those that like
looking at those things:

http://lkml.iu.edu/hypermail/linux/k...0.2/05220.html

Edit in: The dusk-4.19.0 kernel has been installed and is running well with -current and the Nvidia-410.66 driver.

Jeebizz · 10-22-2018, 10:50 AM

Quote:

Originally Posted by cwizardone

Here is Greg K-H's announcement,
Note the last paragraph. I added the bold emphasis.

http://lkml.iu.edu/hypermail/linux/k...0.2/05220.html

Edit in: The dusk-4.19.0 kernel has been installed and is running well with -current and the Nvidia-410.66 driver.

Also reminder this is slated as LTS https://news.softpedia.com/news/it-s...s-522452.shtml - so I hope --Current updates to it.

cwizardone · 10-22-2018, 12:09 PM

3.16.60

The 3.16.xx kernel series has been updated to version 3.16.60, and is now available at,

https://www.kernel.org/

The change log,

https://cdn.kernel.org/pub/linux/ker...ngeLog-3.16.60

55020 · 10-22-2018, 02:03 PM

Just FYI folks, I tried building 4.19 for i686 in an up-to-date -current VM multiple times, but it died (repeatably) with the old gcc favourite: "internal compiler error: Segmentation fault". So there won't be a 32-bit 4.19 dusk kernel for the foreseeable future. Sorry!