Welcome!
Important information
-- Spectre and Meltdown vulnerabilities
-- Change in MX sources

News
-- MX Linux on social media: here
-- Mepis support still here

Current releases
-- MX-17.1 Final release info here
-- antiX-17 release info here

New users
-- Please read this first, and don't forget to add system and hardware information to posts!
-- Here are the Forum Rules

MX 17 Repository: The Backported Debian Kernel Thread

Message
Author
User avatar
Stevo
Forum Veteran
Forum Veteran
Posts: 15979
Joined: Fri Dec 15, 2006 8:07 pm

MX 17 Repository: The Backported Debian Kernel Thread

#1 Post by Stevo » Wed Mar 28, 2018 1:13 pm

We now have a newer backported Debian 4.15.11 kernel in the test repository for those that wish to test the latest version. As usual, it presents two version numbers:

Code: Select all

$ uname -a
Linux mx1 4.15.0-2-amd64 #1 SMP Debian 4.15.11-1~mx17+1 (2018-03-27) x86_64 GNU/Linux
It will not automatically upgrade over or replace any other kernels. This is by design. Changes from the Debian version include bumping the kernel context switch frequency from 250 to 1000 Hz, adding libelf-dev as a build-dependency for the headers, and other changes to make it work with our gcc-6 instead of gcc-7.

dr-kart
Forum Regular
Forum Regular
Posts: 124
Joined: Sun Oct 22, 2017 8:12 pm

Re: MX 17 Repository: The Backported Debian Kernel Thread

#2 Post by dr-kart » Wed Mar 28, 2018 2:24 pm

thumbs up

User avatar
Stevo
Forum Veteran
Forum Veteran
Posts: 15979
Joined: Fri Dec 15, 2006 8:07 pm

Re: MX 17 Repository: The Backported Debian Kernel Thread

#3 Post by Stevo » Sat May 05, 2018 5:03 pm

We now have a 4.15.0-1 (4.15.17) backported kernel that will upgrade in place over the stock 4.15.4 version in MX 17.1, plus a new 4.16.0-1 (4.16.5) backported kernel, both in the test repo. The easiest way to upgrade or install the new kernel is to use the test repo feature in the MX package installer and search for 4.15.0-1 or 4.16.0-1, and install the image and the headers package for your flavor. 32-bit users most likely will be using the pae kernel.

Users of the proprietary nvidia-driver package need to update that from the test repo for the 4.16 kernel, also, otherwise it won't work and you'll get no GUI when booting that kernel.

User avatar
Stevo
Forum Veteran
Forum Veteran
Posts: 15979
Joined: Fri Dec 15, 2006 8:07 pm

Re: MX 17 Repository: The Backported Debian Kernel Thread

#4 Post by Stevo » Mon Jun 04, 2018 3:02 pm

The 4.16 backported kernel has been updated to 4.16.0-2 (4.16.12), backported from the Sid sources. This will not be seen as an upgrade to any installed kernel, and must be installed manually. One way is to add the test repo in Synaptic, and search for "4.16.0-2", then install the linux-image and linux-headers packages for your architecture. Note that 64-bit users will also see the two 32-bit kernels, as well as an extra "rt" realtime kernel; 32-bit users will see pae and nonpae versions, so make like Indiana Jones and choose wisely.

User avatar
Stevo
Forum Veteran
Forum Veteran
Posts: 15979
Joined: Fri Dec 15, 2006 8:07 pm

Re: MX 17 Repository: The Backported Debian Kernel Thread

#5 Post by Stevo » Sun Jun 10, 2018 3:20 pm

We now have added the 4.17.0 kernel to the test repo, built using upstream's rc7 version as a template. Included are amd64, i386-pae, and i386 versions, but the realtime "rt" versions were disabled for this build. The kernel timer frequency is also bumped from 250 to 1000 Hz.

The major dkms driver packages will build with this new kernel as long as you have those updated from the test repo. However, virtualbox-guest-dkms builds will fail, so that puts a crimp to any plans to test the kernel in Virtualbox guests.

User avatar
stsoh
Forum Regular
Forum Regular
Posts: 375
Joined: Sun Aug 20, 2017 10:11 am

Re: MX 17 Repository: The Backported Debian Kernel Thread

#6 Post by stsoh » Mon Jun 11, 2018 12:40 am

can someone check nftables with kernel 4.17.0?

Code: Select all

lsmod | grep '^nf'
edit:
ps:
reason i ask is because nftables are missing from kernel 4.17.0 at config.
may not be critical, iptables may preferred by dev(s) to drop nftables.
MX-17.1_x64 Horizon, G41M-P33 Combo(MS-7592), Pentium E5400 (min/max: 1203/2700 MHz), 8Gb RAM (800 MT/s),
Intel 4 Series Integrated Graphics, Realtek PCIe Fast RTL8101/2/6E, PCI Gigabit RTL8169 Ethernets.

User avatar
Stevo
Forum Veteran
Forum Veteran
Posts: 15979
Joined: Fri Dec 15, 2006 8:07 pm

Re: MX 17 Repository: The Backported Debian Kernel Thread

#7 Post by Stevo » Tue Jun 12, 2018 8:50 pm

This is what shows up.

Code: Select all

lsmod | grep '^nf'
nfsd                  413696  2
nfs_acl                16384  1 nfsd
nfs                   311296  0
It also appears that the Debian kernel does not enable the new built-in Virtual Box guest support, though the Liquorix 4.16 kernel does. That might have been a way to work around the guest dkms failures. Maybe I'll copy over the config and rebuild it again.

User avatar
stsoh
Forum Regular
Forum Regular
Posts: 375
Joined: Sun Aug 20, 2017 10:11 am

Re: MX 17 Repository: The Backported Debian Kernel Thread

#8 Post by stsoh » Wed Jun 13, 2018 4:25 am

ok, thanks.
tried compile kernel 4.17.1, nftables still are missing from source, seem plausible dev(s) did something.
compiled latest kernel 4.16.15, no error(s) or missing module(s).
(except for dkms vb-guest, need to remove n reinstall with option --force)

Code: Select all

$ uname -a
Linux mx 4.16.15 #1 SMP PREEMPT Tue Jun 12 17:16:52 +08 2018 x86_64 GNU/Linux

Code: Select all

$ dkms status
broadcom-sta, 6.30.223.271, 4.16.15, x86_64: installed
ndiswrapper, 1.61, 4.16.15, x86_64: installed
virtualbox, 5.2.12, 4.16.15, x86_64: installed
virtualbox-guest, 5.2.12, 4.16.15, x86_64: installed (original_module exists)

Code: Select all

$ lsmod | grep '^nf'
nfsd                  352256  2
nfs_acl                16384  1 nfsd
nfs                   282624  0
nf_reject_ipv6         16384  1 ip6t_REJECT
nf_conntrack_ipv6      16384  7
nf_defrag_ipv6         32768  1 nf_conntrack_ipv6
nf_reject_ipv4         16384  1 ipt_REJECT
nf_conntrack_ipv4      16384  7
nf_defrag_ipv4         16384  1 nf_conntrack_ipv4
nf_conntrack_netbios_ns    16384  0
nf_conntrack_broadcast    16384  1 nf_conntrack_netbios_ns
nf_nat_ftp             16384  0
nf_nat                 32768  1 nf_nat_ftp
nf_conntrack_ftp       16384  1 nf_nat_ftp
nf_conntrack          131072  8 nf_conntrack_ipv6,nf_conntrack_ftp,nf_conntrack_ipv4,nf_conntrack_broadcast,nf_nat_ftp,nf_conntrack_netbios_ns,xt_conntrack,nf_nat
MX-17.1_x64 Horizon, G41M-P33 Combo(MS-7592), Pentium E5400 (min/max: 1203/2700 MHz), 8Gb RAM (800 MT/s),
Intel 4 Series Integrated Graphics, Realtek PCIe Fast RTL8101/2/6E, PCI Gigabit RTL8169 Ethernets.

User avatar
sacules
Forum Novice
Forum  Novice
Posts: 14
Joined: Fri Mar 09, 2018 4:15 pm

Re: MX 17 Repository: The Backported Debian Kernel Thread

#9 Post by sacules » Wed Jun 13, 2018 5:17 pm

Stevo wrote:
Sun Jun 10, 2018 3:20 pm
We now have added the 4.17.0 kernel to the test repo, built using upstream's rc7 version as a template.
I've been using it for the last day or two and everything's working fine - finally the AMDGPU drivers allow me to have HDMI audio!

User avatar
Stevo
Forum Veteran
Forum Veteran
Posts: 15979
Joined: Fri Dec 15, 2006 8:07 pm

Re: MX 17 Repository: The Backported Debian Kernel Thread

#10 Post by Stevo » Wed Jun 13, 2018 5:49 pm

sacules wrote:
Wed Jun 13, 2018 5:17 pm
Stevo wrote:
Sun Jun 10, 2018 3:20 pm
We now have added the 4.17.0 kernel to the test repo, built using upstream's rc7 version as a template.
I've been using it for the last day or two and everything's working fine - finally the AMDGPU drivers allow me to have HDMI audio!
Much improved amdgpu drivers were advertised for the 4.17 kernels, for sure!

Post Reply

Return to “Package Requests/Status - MX 17”