Is there going to be official MX Linux 4.19 kernel?

[Osminymus]

Thanks for the explanation I will check it out when it comes in repos. Currently, I can't get either of kernels from MX or antiX get to work, I install it from repos, MX Package Installer mainly, but I tried with Synaptic too but with no luck. System can't boot it stops at nvidiapcie or smt, I couldn't fix it and I've tried and googled a lot.

[Stevo]

The latest kernels need the Nvidia proprietary drivers from stretch-backports or our test repository, if you're using those.

[KoO]

I updated my nvidia drivers yesterday with sgfxi now have 410.73 and I like them too..

Ditto for AntiX 4.19 mainline

[Osminymus]

I tried antiX 4.18.7 kernel with proprietary 390.77 or 390.87 from MX repos, but it didn't work, maybe cuz I disabled nouveau Idk. Actually IIRC sometimes it manages to boot but it takes 10 mins or more, that's why I am asking about 4.19 kernel.

[Gerson]

Using the kernel 4.18.0-14.1-liquorix-amd64 on a Compaq Presario-21-Verk machine and the performance is impressive, it improves a lot for continuous work and several open applications; It is faster and improves the battery life time.
They find it in MX Repo Test; They are two files:
- linux-image-liquorix-amd64
- linux-headers-liquorix-amd64

[Stevo]

Using the kernel 4.18.0-14.1-liquorix-amd64 on a Compaq Presario-21-Verk machine and the performance is impressive, it improves a lot for continuous work and several open applications; It is faster and improves the battery life time.
They find it in MX Repo Test; They are two files:
- linux-image-liquorix-amd64
- linux-headers-liquorix-amd64

You can also install the latest Liquorix kernel we have in the Package Installer, but then won't get that kernel automatically upgraded when we add a newer one like with the metapackages above. However, using "liquorix" as a search keyword in Synaptic helps manage them quite a bit.

[marlowe221]

This thread leads me to a couple of new user-ish questions related to the kernel and upgrades, etc.

If everything is working correctly for me on my machine, does upgrading the kernel do anything for me?

Do the kernel packages with the AntiX label work for MX?

MX includes Synaptic but also includes the MX Package Installer - which one of those should I be using, or are they the same?

[chrispop99]

This thread leads me to a couple of new user-ish questions related to the kernel and upgrades, etc.

If everything is working correctly for me on my machine, does upgrading the kernel do anything for me?

Do the kernel packages with the AntiX label work for MX?

MX includes Synaptic but also includes the MX Package Installer - which one of those should I be using, or are they the same?

The only time I would advise upgrading the kernel when everything is working properly is when it was needed for security. If that was the case, there would be plenty of information available to let you know. Otherwise, leave well alone!

All the kernels in the Package Installer will work with MX.

The Package Installer has several advantages. The Popular Applications tab makes it easy to find something for a specific purpose, as items are arranged in categories.

Selecting one of the other tabs enables the appropriate repo just whilst you are installing. When you exit, that repo is disabled. That is actually a really clever idea, as it prevents a repo that might cause problems with updates in the future from being left enabled, either accidentally, or through ignorance.

Chris

[marlowe221]

Thanks Chris. That is very helpful!

I was a bit confused about the existence of the MXPI along side Synaptic. So let's say I install some application from the MX Testing repo. Will it auto-notify me of updates with the applet in the panel? Or are those updates different?

[asqwerth]

The auto-notification only checks the permanently enabled repos, ie the Stable Repo and any other repo you might manually enable on a permanent basis.

You aren't actually meant to keep regularly updating from the Test Repo. Remember that things found there are at a "Test" or "trial" level because someone asked for a newer version of a package or because the Packaging team felt a particular package not found in the Debian stable repo was worth packaging. It's placed in Test Repo to be tried by the requester and whomever's interested. If the users report that it's working fine (on rare occasions, there might be a bug, or some dependency overlooked, which are then reported and hopefully fixed), the package gets moved into the Stable Repo. And if there are subsequent updates to that package also pushed to the Stable Repo, you will see the update auto-reported by the notifier.

That's why Test Repo is advised to be kept disabled and only turned on temporarily in MXPI to install test packages on request.