LinuxQuestions.org - The Latest Kernel Release.

- Slackware (https://www.linuxquestions.org/questions/slackware-14/)

- - The Latest Kernel Release. (https://www.linuxquestions.org/questions/slackware-14/the-latest-kernel-release-4175597503/)

Quote:

Originally Posted by GazL (Post 5657820)

.....Anyway, fwiw, 4.9.5 running ok here.

Some of the changes in the 4.9.5 kernel:

Quote:

......Linux kernel 4.9.5 appears to be a big milestone that changes a total of 132 files, with 1515 insertions and 821 deletions. There are numerous improvements implemented in this fifth Linux 4.9 maintenance update, but first we'd like to remind you that Greg Kroah-Hartman recently marked this kernel branch as long-term supported (LTS)............

"Radeon SMC firmware selection updated for Southern Islands family"

From the appended shortlog, we can notice that the biggest part of the Linux kernel 4.9.5 patch includes updated drivers. This time, the developers managed to improve the support for open-source Radeon, Intel i915, Tegra, and VC4 graphics drivers, but there are also updated I2C, CPUFreq, ACPI, DMA, InfiniBand, Ethernet (Mellanox MLX5), wireless (Intersil), NVM Express (NVMe), PINCTRL, USB, TTY, and remoteproc drivers.

Other than that, Linux kernel 4.9.5 includes various PowerPC (PPC), x86 (KVM changes mostly), ARM64/AArch64, Btrfs, NFS, OCFS2, and XFS improvements, along with the usual mm and core kernel noise, tooling fixes, and an updated networking stack with a fix for the new 802.11 netlink interface public header.....

http://news.softpedia.com/news/linux...s-512050.shtml

4.9.5 work perfectly here, now ;)

Quote:

Originally Posted by gmgf (Post 5658626)

4.9.5 work perfectly here, now ;)

Ditto, been using 4.9.x for a while now on a laptop with Slackware 14.2, no issues so far.

I've been running 4.9.5 for a few days now and the Intel graphics support is great.

The 4.10-rc5 mainline kernel is available for testing,
https://www.kernel.org/

Is the unofficial Kernel built as if it was done by Slackware Devs? What I mean, do you use the same commands/flags etc...? Are they equivalent to each other? I normally don't play around with the kernel.

Quote:

Originally Posted by PROBLEMCHYLD (Post 5659084)

The commands are really all the same.

Code:

cp /location/to/kernel/config .config

make menuconfig  # If you want to make any changes to the default config

make modules bzImage  # Build the kernel and modules

make modules_install  # Install the modules

cp arch/x86/boot/bzImage /boot/vmlinuz-generic-4.9.5  # Copy the kernel to the boot directory

# Edit bootloader (lilo, grub, etc) to support new kernel

There is some wiggle room with that and additional things you can do, but those are the basic commands to build a kernel.

David (55020) has automated this process and instead of installing kernels manually, he generates Slackware packages for them. As with normal kernel packages, it is generally recommended to installpkg the new kernels rather than upgradepkg so if the new kernels don't work, you can boot into your old one. You'll still need to edit your bootloader configs with these packages.

The main difference would be in the configs used to build the kernel as each major series can see substantial changes to the options in the config. For these, David took the 4.6 kernel config that Pat provided in testing/ and modified it the best he could to 4.9's options. It is likely what he thinks is similar to what Pat would/will provide if/when he provides configs for 4.9 (whether that is just configs in testing/ or actually new kernels in -current, we'll need to wait and see). However, it seems he is only providing generic configs, so you'll be on your own if you don't want an initrd. (Pat highly suggests running generic kernels over huge and only provides huge as a starting point.)

bassmadrigal, Thanks!!!!!

I'm going to download and install them. I'll report back any errors or not. Thanks again.
I wish more was as helpful and polite as you. You seem to be a meek individual. Off to test and thanks to David (55020).

P.S

I don't see the kernel firmware package. Is it needed?

That's a good question. The linux-firmware package isn't really part of the kernel (note the name). It isn't tied to a particular version of the kernel, it doesn't even have releases. Patrick puts out a new snapshot in -current occasionally, which you might have a specific need for if you have new hardware. Otherwise it's easy to forget it's even there, which is just the way I like it.

Thanks for trying my unofficial kernel packages, but let's not forget that the official kernel packages are curated by the best man in the business.

The 4.4.45 kernel has been released.
The change log, https://cdn.kernel.org/pub/linux/ker...angeLog-4.4.45

And, a new version of the newest LTS kernel, 4.9.6.
The change log, https://cdn.kernel.org/pub/linux/ker...hangeLog-4.9.6

Quote:

Originally Posted by cwizardone (Post 5660380)

The 4.4.45 kernel has been released.
The change log, https://cdn.kernel.org/pub/linux/ker...angeLog-4.4.45
And, a new version of the newest LTS kernel, 4.9.6.
The change log, https://cdn.kernel.org/pub/linux/ker...hangeLog-4.9.6

These kernels fixes CVE-2016-7097:

Quote:

tmpfs: clear S_ISGID when setting posix ACLs

commit 497de07d89c1410d76a15bec2bb41f24a2a89f31 upstream.

This change was missed the tmpfs modification in In CVE-2016-7097
commit 073931017b49 ("posix_acl: Clear SGID bit when setting
file permissions")
It can test by xfstest generic/375, which failed to clear
setgid bit in the following test case on tmpfs:

touch $testfile
chown 100:100 $testfile
chmod 2755 $testfile
_runas -u 100 -g 101 -- setfacl -m u::rwx,g::rwx,o::rwx $testfile"

If you care about security you mount your user-writable filesystems with "nosuid,nodev" anyway. Given how problematic non-root owned SUID/SGID executables are in general I'm not convinced the existence of this vulnerability makes them any worse.

55020 --

Thanks for sharing your .config files !

Building 4.9.6.kjh now and will try it out this weekend.

-- kjh

followup ...

Linux 4.9.6 built and booted fine using 55020's .config

I ran NVIDIA-Linux-x86_64-375.26.run and it built and installed fine and KDE ran and looked great.

However, I use VMWare Workstation 12.5.x, mostly so I can read Outlook Email on a Win7 VM for work.

VMWare won't compile the necessary Kernel Modules without the 4.9.6 Kernel Headers.

I suppose I could install the Kernel Headers and rebuild the dependencies ( :) ? just about everything ? :) ) but that dog won't hunt on my main Laptop for Work :(

I suppose I am 'stuck' with 4.4.x for now ...

Thanks again for sharing those .configs 55020 !

-- kjh

I've no experience of VMware but I was under the impression that the correct approach for out of tree modules is to compile them against /lib/modules/$kernel-release/build/include rather than the headers in /usr/include.