The Latest Kernel Release.

cwizardone · 10-01-2018, 10:43 PM

Quote:

Originally Posted by cwizardone

It has been many years since I "rolled my own," but I have just built and installed the 4.19.0-rc6 kernel.

So far, so good. All the usual applications are running without any problems.

However, there was a problem with both the 390.87 and 396.54.05 Nvidia drivers. Both returned an error and suggested the installation be re-started using the "--no-drm" option. That worked, but to get xorg to behave properly it was necessary to pull my old xorg.conf file out of retirement and copy it to /etc/X11/xorg.conf.d/

So far... so good...

Well, it has been running just about 24 hours now and there have been no coughs, hiccups or seizures with the 4.19.0-rc6 kernel.

elcore · 10-02-2018, 05:14 AM

I've introduced the recent NUMA changes from -current into 14.2 kernel 4.4.157 with no apparent downside.
It's running for about a week, no problem. But I'm looking to bump the version to 4.14 on all my systems soon.

55020 · 10-02-2018, 04:52 PM

individual · 10-02-2018, 04:56 PM

Quote:

Originally Posted by 55020

Attachment 28706

Thanks for the trip down memory lane.

cwizardone · 10-03-2018, 08:15 PM

Kernel updates 4.18.12, 4.14.74, 4.9.131 and 3.16.59 are now available at,

https://www.kernel.org/

The change logs,

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

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

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

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

Dave's Unofficial Slackbuilt Kernel-4.18.12 update can be found at, https://dusk.idlemoor.tk
__________________

cwizardone · 10-07-2018, 11:03 AM

4.19-rc7

The seventh release candidate of the mainline 4.19 series is now available for testing.

The tarball, https://git.kernel.org/torvalds/t/linux-4.19-rc7.tar.gz

Greg K-H's announcement,

Quote:

Linux 4.19-rc7
From: Greg KH
Date: Sun Oct 07 2018 - 11:54:28 EST

Hi all,

Yet again, it's time for a kernel -rc release. This one is bigger than
-rc6 was, for a variety of unrelated reasons it seems. Lots of
different trees being merged this week, much more so than the previous
one. Highlights include two sets of networking fixes, lots of different
driver subsystem fixes, arm and arm64 and x86 and riscv and powerpc64
fixes, as well as scheduler, iommu, and vfs fixes. Not a huge quantity
overall, just overall a lot of different things.

Given the current rate of change, and looking at the travel/conference
schedule happening this month, it seems like we will be having a -rc8
just to be sure 4.19 is solid as well as not having to be in the middle
of a merge window during a conference week. Please go test and make
sure any remaining problems are sent in in time.

thanks,

greg k-h

http://lkml.iu.edu/hypermail/linux/k...0.0/05765.html

cwizardone · 10-07-2018, 12:20 PM

The 4.19-rc7 kernel has been built and installed and...... so far, so good

with -current and the Nvidia-396.54.05 driver.

abga · 10-09-2018, 11:45 AM

4.19 will definitely have some interesting updates from security POV, hope they'll get backported into the branches Slackware uses.

- kernel boot parameter to disable the (controversial) HW RNG, finally
https://git.kernel.org/pub/scm/linux...53cab15f596ee0
- proper Meltdown mitigation for 32 bit X86 CPUs, I wasn't aware that it was broken
https://git.kernel.org/pub/scm/linux...b0210b9c5d8b70
https://git.kernel.org/pub/scm/linux...79c88d299267af
(and a recommendation-warning to switch to a 64bit kernel on 64bit CPUs)
https://git.kernel.org/pub/scm/linux...05020ee4eda31a
- Spectre v4 - l1tf - got an update
https://git.kernel.org/pub/scm/linux...6adf9c1e17aa2d
- some updates for Spectre V2
https://git.kernel.org/pub/scm/linux...ec3b803e45ed4d

cwizardone · 10-10-2018, 08:12 AM

Kernel updates 4.18.13, 4.14.75, 4.9.132 and 4.4.160 are now available at,

https://www.kernel.org/

The change logs,

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

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

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

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

AlleyTrotter · 10-10-2018, 09:13 AM

4.18.13 is a runner here on 64-14.2
john

brodo · 10-10-2018, 09:32 AM

Sorry for a lame question - may I build 4.18.13 on my 32-bit current Slackware using directly scripts from:

http://ftp.slackware.com/pub/slackwa...rent/source/k/

Of course I'll remember about changing kernel version where it must be changed.
What about specific config settings, etc ?

ponce · 10-10-2018, 09:55 AM

Quote:

Originally Posted by brodo

Sorry for a lame question - may I build 4.18.13 on my 32-bit current Slackware using directly scripts from:

http://ftp.slackware.com/pub/slackwa...rent/source/k/

Of course I'll remember about changing kernel version where it must be changed.
What about specific config settings, etc ?

I never tried (I usually built them with my own script) but I think downloading a compatible config should be enough: try, from that directory, something like

Code:

rm linux-4.14.74.tar.*
wget https://cdn.kernel.org/pub/linux/kernel/v4.x/linux-4.18.13.tar.xz https://cdn.kernel.org/pub/linux/kernel/v4.x/linux-4.18.13.tar.sign
wget -O kernel-configs/config-generic-smp-4.18.13-smp https://dusk.idlemoor.tk/config/config-generic-smp-4.18.12-smp
RECIPES="IA32_SMP" KERNEL_CONFIG=./kernel-configs/config-generic-smp-4.18.13-smp ./build-all-kernels.sh

elcore · 10-10-2018, 11:37 AM

https://lkml.org/lkml/2018/8/15/147

Any kernel since 4.15 is not loading the samsung edid block on my AMD machine (loads the edid block fine on 4.14).
Seriously guys? Deprecated by intel? Bonus typo in deprecation notification? Parameter change for the sake of change?

Stuff like that, is why I stick to LTS. Not enough lifetime to work around, I could maybe fix one or two.. but kernel has no end.

bassmadrigal · 10-10-2018, 12:03 PM

Quote:

Originally Posted by elcore

Stuff like that, is why I stick to LTS. Not enough lifetime to work around, I could maybe fix one or two.. but kernel has no end.

Unfortunately, I don't think the solution is as easy as sticking to LTS.

This problem isn't guaranteed to be fixed in future LTS versions... According to the DRM bug report linked on that lkml message, it still wasn't fixed by the end of September, so who knows if it'll make it into the 4.19 kernel, which is expected to be the next LTS kernel.

There's still this Ryzen bug that has yet to be fixed even though it was first reported in 2017 back with the 4.12 kernel. We're getting ready to have the 4.19 kernel released, which still has the issue, so that means we will have gone through 2 LTS kernels without a fix.

elcore · 10-10-2018, 04:11 PM

Quote:

Originally Posted by bassmadrigal

Unfortunately, I don't think the solution is as easy as sticking to LTS.

Right, I checked if that was a security fix thinking they might backport it, and it's not. It's regression, so even if it persists in next LTS, it'll probably still work on 4.14.x until EOL.
It's kind of a big deal, because samsung specs have different timings for lcd panel, and it was designed for 1680x1050@60 but kernel sets 1024x768@75 (stretched, or cut on the sides)
That's standard resolution so it probably won't damage the display, even though it's possible with wrong timings.