The Latest Kernel Release.

bassmadrigal · 10-10-2018, 05:13 PM

Quote:

Originally Posted by elcore

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.

I did mean LTS in general, not the 4.14 LTS specifically. In your case, it is likely that the problem won't be backported to the 4.14 LTS, but it is very possible the fix may not exist in the 4.19 kernel which is expected to be an LTS... although, this would depend on how they label patch (whenever it arrives) and whether they decide it is worth backporting into a stable release.

However, it should be mentioned that while there isn't a fix yet, there is a workaround that was suggested in the second message by Jani Nikula that seemed to work. They mentioned adding video=VGA-1:e to the command, which the OP replied that it does work, however, it keeps the VGA port enabled when not plugged in.

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

Quote:

Originally Posted by bassmadrigal

However, it should be mentioned that while there isn't a fix yet, there is a workaround that was suggested in the second message by Jani Nikula that seemed to work.

Maybe it works for the OP's case, but I already have "video=nouveaufb:VGA-1:1680x1050x24@60" that works fine on 4.14
So if I were to replace the command with 'e' I may as well replace it with 'nomodeset' or 'vesafb' (it'll do vesa standard res, not native res)

cwizardone · 10-11-2018, 01:23 PM

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

From the 4.18.13 change log:

Quote:

commit 386562cba8c2b5de706884158419da45f0213299
Author: Sean O'Brien <seobrien@chromium.org>
Date: Mon Aug 27 13:02:15 2018 -0700

HID: add support for Apple Magic Keyboards

[ Upstream commit ee345492437043a79db058a3d4f029ebcb52089a ]

USB device
Vendor 05ac (Apple)
Device 026c (Magic Keyboard with Numeric Keypad)

Bluetooth devices
Vendor 004c (Apple)
Device 0267 (Magic Keyboard)
Device 026c (Magic Keyboard with Numeric Keypad)

Support already exists for the Magic Keyboard over USB connection.
Add support for the Magic Keyboard over Bluetooth connection, and for
the Magic Keyboard with Numeric Keypad over Bluetooth and USB
connection.

Signed-off-by: Sean O'Brien <seobrien@chromium.org>
Reviewed-by: Benjamin Tissoires <benjamin.tissoires@redhat.com>
Signed-off-by: Jiri Kosina <jkosina@suse.cz>
Signed-off-by: Sasha Levin <alexander.levin@microsoft.com>
Signed-off-by: Greg Kroah-Hartman <gregkh@linuxfoundation.org>

brodo · 10-11-2018, 02:00 PM

Quote:

Originally Posted by ponce

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

I succesfully built generic-smp-4.18.13-smp using the 2 wget commands above; the 3rd latest line didn't worked.

I shorted it to:

Code:

 RECIPES="IA32_SMP" ./build-all-kernels.sh

and that worked well.

Thanks !

AlleyTrotter · 10-13-2018, 07:04 AM

Updated to 4.18.14 / 64 this very morning, all seems fine
AlleyTrotter

cwizardone · 10-13-2018, 07:29 AM

Kernel updates 4.18.14, 4.14.76, 4.9.133, 4.4.161 and 3.18.124 [EOL] are now available at,

https://www.kernel.org/

The change logs,

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

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

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

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

https://cdn.kernel.org/pub/linux/ker...geLog-3.18.124

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

Jeebizz · 10-14-2018, 12:04 AM

4.19 on 7th RC, hopefully the last - and then maybe -current can jump to that since that kernel is slated as "LTS".

cwizardone · 10-14-2018, 09:08 AM

Well, I hope you are correct, but last week Greg K-H said,

Quote:

......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.....

The entire message is quoted in post #906, above.

We will find out sometime over the next several hours.

cwizardone · 10-15-2018, 07:45 AM

4.19-rc8

The eighth, and last, release candidate of the mainline 4.19 series is now available for testing.

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

Greg KH's announcement,

Quote:

From: Greg KH
Date: Mon Oct 15 2018 - 02:49:21 EST

Hi all,

As mentioned last week, here's a -rc8 release as it seems needed.

There were a lot of "little" pull requests this week, semi-normal for
this late in the cycle, but a lot of them were "fix up the previous fix
I just sent" which implies that people are having a few issues still.

I also know of at least one "bad" bug that finally has a proposed fix,
so that should hopefully get merged this week. And there are some
outstanding USB fixes I know of that have not yet landed in the tree (I
blame me for that...)

Anyway, the full shortlog is below, lots of tiny things all over the
tree. Please go and test and ensure that all works well for you.
Hopefully this should be the last -rc release.

thanks,

greg k-h

http://lkml.iu.edu/hypermail/linux/k...0.1/06808.html

Jeebizz · 10-16-2018, 12:26 AM

Quote:

Originally Posted by cwizardone

4.19-rc8

The eighth, and last, release candidate of the mainline 4.19 series is now available for testing.

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

Greg KH's announcement,

http://lkml.iu.edu/hypermail/linux/k...0.1/06808.html

Lets hope it is the last.

cwizardone · 10-18-2018, 05:04 AM

Kernel updates 4.18.15, 4.14.77 and 4.9.134 are now available at,

https://www.kernel.org/

The change logs,

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

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

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

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

Edit in: The dusk-4.18.15 kernel has been installed and is running well with -current (minus the latest icu4c and related updates) and the new Nvidia 410.66 driver.

overlock · 10-19-2018, 11:07 AM

Hello, how do I install the generic slackware current 4.14 kernel in slackware stable?

orbea · 10-19-2018, 11:41 AM

Quote:

Originally Posted by overlock

Hello, how do I install the generic slackware current 4.14 kernel in slackware stable?

https://docs.slackware.com/slackware...generic_kernel

mralk3 · 10-19-2018, 12:02 PM

Quote:

Originally Posted by overlock

Hello, how do I install the generic slackware current 4.14 kernel in slackware stable?

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.

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

Quote:

Originally Posted by overlock

Hello, how do I install the generic slackware current 4.14 kernel in slackware stable?

I was going to make a blog-post about it to slim down the process, but here's my personal microwaveable-quick version. May contain allergens.

EDIT: I'm going to omit this for now and tidy it up so as not to confuse things. Go read orbea's link.