MX Linux Forum

Posted: **Tue Nov 07, 2017 2:34 pm**

We now have the latest 4.13-5 ( 4.13.0-11.1) release of the Liquorix kernel in the test repository. The builds from the developer's repository now need gcc-7 for the header packages, making those incompatible with MX 17 or Debian/Stretch, so that's why we have this solution.

Code: Select all

Liquorix is a distro kernel replacement built using the best configuration and kernel sources for desktop, multimedia, and gaming workloads.

[/i]

There are PAE and non-PAE versions available for the 32-bit platform. There are also kernel and header metapackages that will pull in any new versions automatically. If you just install the actual kernel and header packages, those don't get automatic updates, since every new version is going to be seen by apt as a different package.

There is a Liquorix kernel option in the MX Package Installer, and that also needs testing. Also note that you may need to update firmware, ndiswrapper, or the broadcom-sta-dkms driver packages from the test repo to get them to build with this kernel and you need them. Currently, the standard 375.82 Nvidia proprietary driver in the Debian repositories will build and work with the 4.13 kernel.

Posted: **Tue Nov 07, 2017 3:39 pm**

There is a Liquorix kernel option in the MX Package Installer

it's not working by now. So I had to manually pick those headers and image kernels from testing repo tab. Alongside ndiswrapper to be updated. And there's no any 'broadcom-sta-dkms' in testing tab (but I probably don't need it).

And what's annoying is that Liquorix Kernel has non zero cpu load while idle. AFAIK it's a well known "feature". (Same for Arch linux repo-ck kernels)

Posted: **Tue Nov 07, 2017 3:42 pm**

dr-kart wrote:
There is a Liquorix kernel option in the MX Package Installer
it's not working by now. So I had to manually pick those headers and image kernels from testing repo tab. Alongside ndiswrapper to be updated. And there's no any 'broadcom-sta-dkms' in testing tab (but I probably don't need it).

And what's annoying is that Liquorix Kernel has non zero cpu load while idle. AFAIK it's a well known "feature". (Same for Arch linux repo-ck kernels)

thanks. that pi pm file has a bad repo in it...will fix.

Posted: **Tue Nov 07, 2017 7:07 pm**

dr-kart wrote:
There is a Liquorix kernel option in the MX Package Installer
it's not working by now. So I had to manually pick those headers and image kernels from testing repo tab. Alongside ndiswrapper to be updated. And there's no any 'broadcom-sta-dkms' in testing tab (but I probably don't need it).

And what's annoying is that Liquorix Kernel has non zero cpu load while idle. AFAIK it's a well known "feature". (Same for Arch linux repo-ck kernels)

Well, yes, it's known to emphasize responsiveness over power savings. Currently it also uses cpufreq power governors instead of p-state like Debian for modern Intel CPUS.

Posted: **Tue Nov 28, 2017 1:54 pm**

Now up to the 4.13-10 (-16.1) version in the test repo, incorporates 4.13.16 vanilla kernel changes.

Posted: **Thu Dec 07, 2017 5:57 pm**

We now have 4.14-4 (4.14.0-3.1) in the test repository. Some proprietary drivers will need to be pulled in from the test repo to build against this kernel. If you have an Optimus system, it may not work after the upgrade, so hold off on this kernel unless you want to test it.

Posted: **Mon Dec 11, 2017 9:52 pm**

Updated to 14.4-7 (14.4-4.3) which builds upon the vanilla kernel 4.14.5rc base release. The changelog since 14.4-4:

linux-liquorix (4.14-7) unstable; urgency=medium

* merge 4.14.5-rc for 2017-12-09
* add patch to workaround nvidia build bug:
- locking/refcounts: Do not force refcount_t usage as GPL-only export
* update version to 4.3

-- Steven Barrett <steven@liquorix.net> Sat, 09 Dec 2017 19:59:19 -0600

linux-liquorix (4.14-6) unstable; urgency=medium

* revert 4.14.5-rc patches, breaks nvidia kernel support:
- https://techpatterns.com/forums/about2631.html
* merge zen-kernel master changes
* refresh configuration due to changes
* update version to 4.2

-- Steven Barrett <steven@liquorix.net> Fri, 08 Dec 2017 20:37:40 -0600

linux-liquorix (4.14-5) unstable; urgency=medium

* merge 4.14.4
* merge 4.14.5-rc for 2017-12-06
* update version to 4.1

-- Steven Barrett <steven@liquorix.net> Wed, 06 Dec 2017 20:22:48 -0600

The header packages also now depend on libelf-dev to fix Virtual Box 5.2.X builds, thanks to the bug report on this forum.

Posted: **Tue Dec 12, 2017 7:21 am**

will u be updating linux-image-4.14.0-5.1-liquorix-amd64_4.14-8_amd64.deb?

Posted: **Tue Dec 12, 2017 12:11 pm**

Is there something that is requiring you to need that kernel or just shiny new syndrome? Looks like they are keeping up with the kernel releases quite well. It takes hours to compile each new kernel release so it doesn't pay to package every single one.

Posted: **Tue Dec 12, 2017 12:48 pm**

I am really waiting for 4.15.

There are supposedly lots of Ryzen AMD code added, including CPU temperature monitoring.
The 4.13 is unstable (maybe) on this hardware, and 4.14 might be better.

But I am testing the antix 4.10 kernel on MX-17 RC1 for stability currently. If that is stable, I can stay on that for quite a while.

Posted: **Tue Dec 12, 2017 1:53 pm**

v3g4n wrote:Is there something that is requiring you to need that kernel or just shiny new syndrome? Looks like they are keeping up with the kernel releases quite well. It takes hours to compile each new kernel release so it doesn't pay to package every single one.

it's an update tat fix a few bugs, why not.
kernel update r more critical than apps.
i'm using the latest update liquorix-amd64_4.14-8.
not able to install header due to gcc-7 dependencies.
it run a lot better/smoother/faster than 4.13.13(eol) like new engine powerup my old pc.

Posted: **Tue Dec 12, 2017 4:14 pm**

entropyfoe wrote:I am really waiting for 4.15.

There are supposedly lots of Ryzen AMD code added, including CPU temperature monitoring.
The 4.13 is unstable (maybe) on this hardware, and 4.14 might be better.

But I am testing the antix 4.10 kernel on MX-17 RC1 for stability currently. If that is stable, I can stay on that for quite a while.

antiX 4.14.5 kernel should hit the repos very soon.

Edit - Whoops, I misread - ignore.

Posted: **Tue Dec 12, 2017 5:42 pm**

stsoh wrote: it's an update tat fix a few bugs, why not.
kernel update r more critical than apps.
i'm using the latest update liquorix-amd64_4.14-8.
not able to install header due to gcc-7 dependencies.
it run a lot better/smoother/faster than 4.13.13(eol) like new engine powerup my old pc.

So install 14.4-7 (14.4-4.3) from the test repo then, don't need to be using 4.13. You will also be able to install the headers then since Stevo recompiles them using Stretches gcc-6 so there will not be the dependency on gcc-7.

Posted: **Tue Dec 12, 2017 5:54 pm**

Kinda busy helping get MX 17 out now, but there's always my Liquorix openSUSE build service repo that builds the kernels much, much faster on their farm than I can on my laptop. I'll get 5.1 loaded it into it right now.

See https://techpatterns.com/forums/about2615.html

Though I now only do Debian 8, 9, and Ubuntu 14.04 versions now that Liquorix does the other Ubuntus in a PPA. Also I make much fewer changes to the files when backporting them than we used to...makes it much easier on my part.

Edit: Loaded, you can check on build progress here: https://build.opensuse.org/package/show ... uorix-4.14 You have to refresh the page to keep up to date on the progress.

Posted: **Wed Dec 13, 2017 3:16 am**

v3g4n wrote: So install 14.4-7 (14.4-4.3) from the test repo then, don't need to be using 4.13. You will also be able to install the headers then since Stevo recompiles them using Stretches gcc-6 so there will not be the dependency on gcc-7.

u r not helping at all, i did all b4 u even tot about it.
i managed to upgrade gcc-7 and cpp-7 from buster repo.
installed both linux-headers/image-4.14.0-5.1-liquorix-amd64_4.14-8_amd64.
uninstalled kernel 4.13.13 and all related after upgrade to latest liquorix.
the best.

Posted: **Wed Dec 13, 2017 3:41 am**

Stevo wrote:Kinda busy helping get MX 17 out now, but there's always my Liquorix openSUSE build service repo that builds the kernels much, much faster on their farm than I can on my laptop. I'll get 5.1 loaded it into it right now.
.......

thanks stevo, i know u r busy ...... i somehow managed to upgrade, the trick is getting gcc and cpp upgraded.
i got liquorix latest deb from here:
https://liquorix.net/debian/pool/main/l/linux-liquorix/

Code: Select all

$ inxi -S
System:    Host: mx1 Kernel: 4.14.0-5.1-liquorix-amd64 x86_64 bits: 64 Desktop: Xfce 4.12.3
           Distro: MX-17.RC1_x64 Horizon December 10, 2017

Posted: **Wed Dec 13, 2017 4:09 pm**

"Upgrading" those two critical system libraries very probably means your system is now broken and insane, and you will have trouble installing applications in the future. That's why we go to all the trouble of backporting and making sure our builds won't do that. Why didn't you follow that simple recipe in the thread I linked to add my OBS repo?

Good reading: http://forums.debian.net/viewtopic.php?&t=114130

Posted: **Wed Dec 13, 2017 4:44 pm**

Gonna be fun to see how this one pans out...

Posted: **Wed Dec 13, 2017 7:35 pm**

Just restore from the system backup...right?

At least MX is a lot faster to do a full reinstall than Debian, too.

Posted: **Wed Dec 13, 2017 10:38 pm**

....System restore from backup and reinstalling speed....

Yup, MX 17 is great. I just did a snapshot this afternoon, second time I used this feature, I love seeing top showing 1180% CPU !
And the apttik utility makes it easy to keep your installed applications.

Yes, installing from usb is very fast, for me three or four minutes. I used to burn DVDs, no more.

I never saw a big problem with a reinstall if you structure your data right. I have one disk with partitions for two OS versions, and I have a separate larger disk for data, the videos, music, pictures, documents, etc. With the data separate, changing the OS or programs is an easy task. I like a MX and an antix installation, with the antix one available to test new versions, like the next antix, maybe a different kernel when 4.15 comes out. And the new snapshot iso which goes on the data drive makes it easy.

Posted: **Wed Dec 13, 2017 11:42 pm**

Stevo wrote: "Upgrading" those two critical system libraries very probably means your system is now broken and insane, and you will have trouble installing applications in the future. That's why we go to all the trouble of backporting and making sure our builds won't do that. Why didn't you follow that simple recipe in the thread I linked to add my OBS repo?

Good reading: http://forums.debian.net/viewtopic.php?&t=114130

The main thing I took away from that thread is that stackexchange contains some really dodgy advice!

@stsoh, I appreciate some people love to tinker, but if so, always have backups handy, keep all your data and media in a separate data drive/partition, or do your experiments in a virtual machine install or a partition that you don't mind messing up. I suppose that since MX17 has not gone Final yet, you are just trying stuff because you can. If so, that's fine.

But if you intend to keep this partition long term, you will run into issues and it will be hard to support on this forum. You've changed some basic building blocks that other packages may depend on, and further updates of your system may lead to all sort of problems.

There is always the questionable lure of the latest and shiniest kernel, but it's not always true that the newest = the best.

You have an older pc, like you said in viewtopic.php?p=429087#p429087 . Your signature indicates it's an Intel Dual core E5400, which Google search says is an old Pentium. Will you really benefit from the latest kernel?

Posted: **Thu Dec 14, 2017 2:40 am**

asqwerth wrote:.......
@stsoh, I appreciate some people love to tinker, but if so, always have backups handy, keep all your data and media in a separate data drive/partition, or do your experiments in a virtual machine install or a partition that you don't mind messing up. I suppose that since MX17 has not gone Final yet, you are just trying stuff because you can. If so, that's fine.

But if you intend to keep this partition long term, you will run into issues and it will be hard to support on this forum. You've changed some basic building blocks that other packages may depend on, and further updates of your system may lead to all sort of problems.

There is always the questionable lure of the latest and shiniest kernel, but it's not always true that the newest = the best.

You have an older pc, like you said in viewtopic.php?p=429087#p429087 . Your signature indicates it's an Intel Dual core E5400, which Google search says is an old Pentium. Will you really benefit from the latest kernel?

it does benefit my old pc, run smoother and faster, tat's the way liquorix design to be. try it. anyway i use minimal space for mxlinux (16gb of my 120gb ssd), freshly install with every beta/new release. fiber broadband take only a few minutes to download, upgrading with deb files takes about a couple of minutes instead of two hours for make install from kernel tar files. liquorix update within a day from kernel releases update.

Code: Select all

$ inxi -F
System:    Host: mx1 Kernel: 4.14.0-5.1-liquorix-amd64 x86_64 bits: 64 Desktop: Xfce 4.12.3
           Distro: MX-17.RC1_x64 Horizon December 10, 2017
Machine:   Device: desktop Mobo: MSI model: G41M-P33 Combo(MS-7592) v: 7.0 serial: N/A
           BIOS: American Megatrends v: V32.13 date: 11/06/2014
CPU:       Dual core Pentium E5400 (-MCP-) cache: 2048 KB
           clock speeds: max: 3145 MHz 1: 3145 MHz 2: 3145 MHz
Graphics:  Card: Intel 4 Series Integrated Graphics Controller
           Display Server: x11 (X.Org 1.19.2 ) drivers: modesetting (unloaded: fbdev,vesa)
           Resolution: 1920x1080@60.00hz
           OpenGL: renderer: Mesa DRI Intel G41 version: 2.1 Mesa 13.0.6
Audio:     Card-1 Intel NM10/ICH7 Family High Def. Audio Controller driver: snd_hda_intel
           Card-2 GYROCOM C&C driver: USB Audio
           Sound: Advanced Linux Sound Architecture v: k4.14.0-5.1-liquorix-amd64
Network:   Card-1: Realtek RTL8101/2/6E PCIE Fast/Gigabit Ethernet controller driver: r8169
           IF: eth0 state: down
           Card-2: Realtek RTL8169 PCI Gigabit Ethernet Controller driver: r8169
           IF: eth1 state: up speed: 1000 Mbps duplex: full
Drives:    HDD Total Size: 4120.8GB (73.0% used)
           ID-1: /dev/sdc model: TOSHIBA_DT01ACA2 size: 2000.4GB
           ID-2: /dev/sda model: TOSHIBA_Q300 size: 120.0GB
           ID-3: /dev/sdb model: TOSHIBA_DT01ACA2 size: 2000.4GB
Partition: ID-1: / size: 16G used: 5.4G (37%) fs: ext4 dev: /dev/sda2
           ID-2: swap-1 size: 0.42GB used: 0.00GB (0%) fs: swap dev: /dev/zram0
           ID-3: swap-2 size: 0.42GB used: 0.00GB (0%) fs: swap dev: /dev/zram1
Sensors:   System Temperatures: cpu: 55.0C mobo: N/A
           Fan Speeds (in rpm): cpu: N/A
Info:      Processes: 159 Uptime: 1:07 Memory: 1177.4/7948.2MB Client: Shell (bash) inxi: 2.3.53

Posted: **Thu Dec 14, 2017 2:47 am**

Stevo wrote:......
"Upgrading" those two critical system libraries very probably means your system is now broken and insane, and you will have trouble installing applications in the future. That's why we go to all the trouble of backporting and making sure our builds won't do that. Why didn't you follow that simple recipe in the thread I linked to add my OBS repo?

Good reading: http://forums.debian.net/viewtopic.php?&t=114130

i understand, still i like mxlinux very much compared to other linux distributions........only the kernel.

Posted: **Thu Dec 14, 2017 8:14 am**

kernel update 4.14.6 is up, liquorix will update in a day.

Posted: **Thu Dec 14, 2017 11:23 am**

stsoh wrote: it does benefit my old pc, run smoother and faster

Do you happen to have any benchmarks that show this or just think so? Would be very curious to see them if you do. I've never noticed a difference when using the liquorix kernel. Wish I had though.

Posted: **Thu Dec 14, 2017 11:36 am**

Because of the way Liquorix tunes the scheduler & VMS, on a system running under heavy load a Liquorix kernel can make the desktop a bit more responsive. But on older hardware a new Liquorix kernel generally won't run any better than an older one.

If you have newer hardware where support is still in development, like Ryzen or a video chipset running the AMDGPU driver, then there are certain kernel updates that can improve performance.

Posted: **Thu Dec 14, 2017 12:28 pm**

v3g4n wrote:
stsoh wrote: it does benefit my old pc, run smoother and faster
Do you happen to have any benchmarks that show this or just think so? Would be very curious to see them if you do. I've never noticed a difference when using the liquorix kernel. Wish I had though.

run with the benchmark profiler, this is my current result. didn't any b4 kernel upgrade.

Posted: **Thu Dec 14, 2017 1:18 pm**

but even with performance benefits, updates may still bork other parts of your system because of your

...upgrade gcc-7 and cpp-7 from buster repo

Does that mean every time it breaks, you will reinstall your system and then install the latest and greatest kernel from a .deb file again, with the necessary importing of gcc and cpp from buster repo?

That's my understanding of your comments:

...anyway i use minimal space for mxlinux (16gb of my 120gb ssd), freshly install with every beta/new release. fiber broadband take only a few minutes to download, upgrading with deb files takes about a couple of minutes instead of two hours for make install from kernel tar files

Posted: **Thu Dec 14, 2017 1:36 pm**

stsoh wrote:run with the benchmark profiler, this is my current result. didn't any b4 kernel upgrade.

Cool, thanks! Unfortunately doesn't help a whole lot without the other for a comparison.

Posted: **Thu Dec 14, 2017 1:45 pm**

benchmark one from 4.13.0, another from 4.14.5.

Posted: **Thu Dec 14, 2017 1:55 pm**

asqwerth wrote:but even with performance benefits, updates may still bork other parts of your system because of your

...upgrade gcc-7 and cpp-7 from buster repo
Does that mean every time it breaks, you will reinstall your system and then install the latest and greatest kernel from a .deb file again, with the necessary importing of gcc and cpp from buster repo?

That's my understanding of your comments:

...anyway i use minimal space for mxlinux (16gb of my 120gb ssd), freshly install with every beta/new release. fiber broadband take only a few minutes to download, upgrading with deb files takes about a couple of minutes instead of two hours for make install from kernel tar files

no, does not break. no problems at all, even update r normal. i do fresh installation because it is much easier and fast than iso.zsync.

Posted: **Thu Dec 14, 2017 1:55 pm**

Those results are essentially identical - certainly within the margin of error for the tests.

Posted: **Thu Dec 14, 2017 2:00 pm**

benchmark r marginally close, in real life usage, it is better.

Posted: **Fri Dec 15, 2017 12:58 am**

updated liquorix 4.14.6, benchmark still as close as to 4.13.13. no breakage as everyone excepted to have, synaptic packages update as per norm.

Code: Select all

$ inxi -F
System:    Host: mx1 Kernel: 4.14.0-6.1-liquorix-amd64 x86_64 bits: 64 Desktop: Xfce 4.12.3
           Distro: MX-17.RC1_x64 Horizon December 10, 2017
Machine:   Device: desktop Mobo: MSI model: G41M-P33 Combo(MS-7592) v: 7.0 serial: N/A
           BIOS: American Megatrends v: V32.13 date: 11/06/2014
CPU:       Dual core Pentium E5400 (-MCP-) cache: 2048 KB
           clock speeds: max: 3145 MHz 1: 3145 MHz 2: 3145 MHz
Graphics:  Card: Intel 4 Series Integrated Graphics Controller
           Display Server: x11 (X.Org 1.19.2 ) drivers: modesetting (unloaded: fbdev,vesa)
           Resolution: 1920x1080@60.00hz
           OpenGL: renderer: Mesa DRI Intel G41 version: 2.1 Mesa 17.2.5
Audio:     Card-1 Intel NM10/ICH7 Family High Def. Audio Controller driver: snd_hda_intel
           Card-2 GYROCOM C&C driver: USB Audio
           Sound: Advanced Linux Sound Architecture v: k4.14.0-6.1-liquorix-amd64
Network:   Card-1: Realtek RTL8101/2/6E PCIE Fast/Gigabit Ethernet controller driver: r8169
           IF: eth0 state: down mac: 44:8a:5b:91:69:6c
           Card-2: Realtek RTL8169 PCI Gigabit Ethernet Controller driver: r8169
           IF: eth1 state: up speed: 1000 Mbps duplex: full mac: 64:70:02:00:71:f9
Drives:    HDD Total Size: 4120.8GB (73.1% used)
           ID-1: /dev/sda model: TOSHIBA_Q300 size: 120.0GB
           ID-2: /dev/sdb model: TOSHIBA_DT01ACA2 size: 2000.4GB
           ID-3: /dev/sdc model: TOSHIBA_DT01ACA2 size: 2000.4GB
Partition: ID-1: / size: 16G used: 5.5G (38%) fs: ext4 dev: /dev/sda2
           ID-2: swap-1 size: 0.42GB used: 0.00GB (0%) fs: swap dev: /dev/zram0
           ID-3: swap-2 size: 0.42GB used: 0.00GB (0%) fs: swap dev: /dev/zram1
Sensors:   System Temperatures: cpu: 43.0C mobo: N/A
           Fan Speeds (in rpm): cpu: N/A
Info:      Processes: 163 Uptime: 4 min Memory: 501.7/7948.2MB Client: Shell (bash) inxi: 2.3.53

Posted: **Wed Jan 17, 2018 3:09 pm**

We are now up to 4.14-17 (4.14-13.2) in the test repo. This incorporates up to the vanilla kernel 4.14.14 rc2 release.

By the way, it's now a lot simpler to adapt the kernel for building on MX, and mmikeinsantarosa has a new HP Xeon workstation that can crank them out in maybe ten minutes per kernel. Hopefully, he can find the time to help with these.

Posted: **Thu Jan 18, 2018 2:22 am**

btw, pls remove liquorix 4.14.0-13.1 from mxpi test repo. it is a debug kernel, replaced by 4.14.0-13.2.
https://techpatterns.com/forums/about2643.html

Posted: **Thu Feb 01, 2018 3:58 pm**

We should now be up to 4.14-22 (4.14-15.2).

When asked why Liquorix uses good ol' cpufreq instead of pstate like Debian for Intel processors, Steve Damentz replied:

When intel_pstate is used with MuQSS, intel_pstate is too aggressive at increasing frequency, leaving the CPU running at a higher voltage than necessary when idle or running mixed loads. The 'schedutil' frequency governor has the same problem as 'intel_pstate'.

And even if these frequency spikes were fixed in a later version of MuQSS or intel_pstate, MuQSS distributes its workload significantly more evenly than CFS, resulting in less opportunities to boost individual cores. With MuQSS, it's more important that all core turbo works correctly rather than single core.

Posted: **Tue Mar 13, 2018 1:44 pm**

We have been rolling in backports as they appear. We are now up to 4.15-4 in the test repo, which incorporates the 4.15.9 and 4.15.10-rc kernel patches. All major dkms packages should build with this kernel with the versions of those now in our main MX repo.

Posted: **Tue Mar 13, 2018 4:40 pm**

Stevo,

I am trying to understand these kernel numberings.

We are now up to 4.15-4 in the test repo, which incorporates the 4.15.9 and 4.15.10-rc kernel patches.

What is the 4.15-4? Where is the -4 coming from? Is that an MX number, because it seems it is actually from 4.15.9 and 10.
Where can you find the actual kernel numbers that correspond to these MX numbers.

I am currently running 4.15.5-antix.1. I thought that .1 was the internal revision number, and the .5 is the true kernel.org version.

Posted: **Tue Mar 13, 2018 4:48 pm**

Debian and Liquorix both use dual versioning for the kernel. The 4.15-4 means that it's the fourth version of the 4.15 kernel that Liquorix has released. The 4.15-1 first release was actually based on the 4.15.5 vanilla kernel release.

Example:

Code: Select all

$ uname -a
Linux mx1 4.15.0-7.1-liquorix-amd64 #1 ZEN SMP PREEMPT liquorix 4.15-3~mx17+1 (2018-03-07) x86_64 GNU/Linux

means that the third Liquorix version is based on the 4.15.7 kernel release.

AntiX kernels are built in a different manner, and don't have the same dual versioning scheme. You can see the Liquorix source packages at the bottom of this page: https://liquorix.net/debian/pool/main/l/linux-liquorix/

It's probably possible to adapt the antiX kernel builds to use the same framework as Liquorix. You just have to use the antiX config files, throw out the Liquorix patches in favor of the 4.15.X one and the antiX custom patches, and adjust the abi in debian/config/defines, as well as fixing the gcc version in that if necessary.

Posted: **Tue Mar 13, 2018 5:04 pm**

Thanks Stevo, I thought it was something complex like that.

I am often wondering how to see which actual kernel.org version these derivatives are based on. So for Liquorix, the source link will have the actual kernel version.
MX and antix, I am still not clear where I can find the actual kernel.org version. I think the latest MX kernel is the 4.15.3 or .4.

Posted: **Tue Mar 13, 2018 5:14 pm**

antiX is easy - it is the same as the version from kernel.org e.g. the one you are currently using, 4.15.5-antix.1, is compiled from kernel.org's 4.15.5
Soon to hit the repos will be antiX kernel 4.15.9-antix.1, built on ... I'm sure you can work out which kernel.org version.

Posted: **Tue Mar 13, 2018 5:24 pm**

entropyfoe wrote:Thanks Stevo, I thought it was something complex like that.

I am often wondering how to see which actual kernel.org version these derivatives are based on. So for Liquorix, the source link will have the actual kernel version.
MX and antix, I am still not clear where I can find the actual kernel.org version. I think the latest MX kernel is the 4.15.3 or .4.

For the Liquorix kernels, the number that reflect what version of the vanilla kernel it's based on is set in the abi line in /debian/config/defines, which is 9.1 in the 4.15-4 Liquorix kernel. The ".1" means that it's the first version based on that particular 4.15.9 kernel patch. The "4.15-4" comes from the versioning in /debian/changelog.

Posted: **Mon Mar 19, 2018 7:50 pm**

Now updated to 4.15-5 (4.15-10.1) which incorporates the vanilla 4.15.10 patch as well as 4.15-11 rc1.

Posted: **Mon Apr 16, 2018 10:35 am**

The latest linux-liquorix-4.15-11.1 kernel is available for testing from the test repo.

Please let us know how it plays.

mike

Posted: **Tue May 01, 2018 8:11 pm**

The latest linux-liquorix_4.15-16.1 kernel is now available for download from the test repo. - mike

Posted: **Fri May 04, 2018 2:43 am**

installed the latest liquorix, found this bug:

Code: Select all

Setting up linux-image-4.15.0-18.4-liquorix-amd64 (4.15-16.1~mx17+1) ...
debconf: unable to initialize frontend: Gnome
debconf: (Can't locate Gtk3.pm in @INC (you may need to install the Gtk3 module) (@INC contains: /etc/perl /usr/local/lib/x86_64-linux-gnu/perl/5.24.1 /usr/local/share/perl/5.24.1 /usr/lib/x86_64-linux-gnu/perl5/5.24 /usr/share/perl5 /usr/lib/x86_64-linux-gnu/perl/5.24 /usr/share/perl/5.24 /usr/local/lib/site_perl /usr/lib/x86_64-linux-gnu/perl-base) at /usr/share/perl5/Debconf/FrontEnd/Gnome.pm line 151.)
debconf: falling back to frontend: Dialog
debconf: unable to initialize frontend: Dialog
debconf: (TERM is not set, so the dialog frontend is not usable.)
debconf: falling back to frontend: Readline

Posted: **Fri May 04, 2018 4:23 pm**

That's weird...the missing file is in libgtk3-perl, but we never needed that before. But I remember seeing stuff like that before, which I remember were just warnings that it couldn't find that file, and that it was going to fall back to readline.

The installation went successfully after that, right?

Posted: **Fri May 04, 2018 5:41 pm**

Stevo wrote:That's weird...the missing file is in libgtk3-perl, but we never needed that before. But I remember seeing stuff like that before, which I remember were just warnings that it couldn't find that file, and that it was going to fall back to readline.

The installation went successfully after that, right?

My 64 bit build system also does a lot better with libgtk3-perl onboard. What do you think, a +2 with it added to the depends?

Posted: **Fri May 04, 2018 6:46 pm**

Stevo wrote:.....
The installation went successfully after that, right?

installation is ok, no problem.
did a search "unable to initialize frontend", found similar bug in this forum couple years back.

Posted: **Fri May 04, 2018 7:40 pm**

mmikeinsantarosa wrote:
Stevo wrote:That's weird...the missing file is in libgtk3-perl, but we never needed that before. But I remember seeing stuff like that before, which I remember were just warnings that it couldn't find that file, and that it was going to fall back to readline.

The installation went successfully after that, right?
My 64 bit build system also does a lot better with libgtk3-perl onboard. What do you think, a +2 with it added to the depends?

It doesn't die without the perl package, just throws that notice...you could argue that an enormous number of packages have that as a suggested package, in that case.

Posted: **Sun May 06, 2018 5:54 pm**

The latest linux-liquorix_4.16-1.1 is now available to download from the test repo.

- mike

Posted: **Thu May 24, 2018 6:01 pm**

We now have 4.16-3.1 (4.16.10) in the test repo, which is based on the 4.16.10 and 4.16.11 rc vanilla kernel sources.

Posted: **Wed May 30, 2018 3:04 pm**

Updated to 4.16.4.1 (4.16.12) in the test repo.

Posted: **Fri Jun 15, 2018 7:36 pm**

Updated in the test repo to 4.16-7 (4.16-15.1) based on the 4.16.15 kernel release.

Posted: **Sun Jul 01, 2018 5:35 pm**

We now have the last 4.16 kernel version, 4.16-11, and the first 4.17.0-1 version, which is based on vanilla kernel release 4.17.3. I installed that on MX 17-x64 in Virtual Box, and continue to get the resizable window and shared folder features, so that means either the outside virtualbox-guest-* modules are building successfully, or it's using the kernel's internal versions of those now. I haven't figured out which applies yet.

Posted: **Tue Jul 17, 2018 2:21 pm**

Updated to the latest 4.17-4 release, based on the 4.17.6 vanilla kernel, in the test repo.

Posted: **Fri Aug 03, 2018 1:19 pm**

Test repo's updated to 4.17-7, (4.17.11.1), based on vanilla kernel 4.17.11.

Posted: **Wed Aug 08, 2018 8:27 pm**

Will it be OK to install kernel 4.14 from /mx/testrepo/pool/test/l/linux-liquorix in MX 17.1

Posted: **Wed Aug 08, 2018 10:03 pm**

I tried the Debian backport 4.17 but Vbox doesn't like it.

I'll try the test repo version to see if if plays with Vbox without tweaking.

Posted: **Thu Aug 09, 2018 3:49 pm**

Virtual Box modules for host, or in a guest? Vbox 5.2.16 in the test repo should work for the host modules.

The last 4.14 kernel builds do include the Meltdown mitigation, though are older than the 4.15 stock Debian kernel in MX 17.1, so I can't really see the point of that version over a newer Liquorix version. The mitigations have been optimized in more recent kernels, and may even be out for 32-bit in a future kernel--maybe 4.19.

Posted: **Wed Aug 15, 2018 3:15 pm**

The new 4.17-10 (based on 4.17.14) release is now in the test repo. This now has a workaround for the MuQSS scheduler bug that was causing to the use of excess CPU cycles, so should improve the battery life somewhat. CPU use at idle should now approach that of the Debian kernel.

Posted: **Wed Aug 22, 2018 1:02 pm**

We now have 4.17-13 (based on 4.17.17 and 4.17.18 rc1) in the test repo. Changes over the last few releases include:

linux-liquorix (4.17-13ubuntu1~xenial) xenial; urgency=medium

* merge 4.17.18-rc updates
* merge bfq updates from algodev-github/bfq-mq
* merge intel bugfix
- drm/i915: Increase LSPCON timeout
* update version to 17.3

linux-liquorix (4.17-12) unstable; urgency=medium

* remove modification to cpufreq/ondemand (it changed unrelated thing)
* merge hrtimeout muqss patches, preserve 1000hz timer config
* update version to 17.2

linux-liquorix (4.17-11) unstable; urgency=medium

* merge 4.17.17
* merge 4.17.18-rc
* cpufreq/ondemand: raise minimum up_threshold to 10%
* update version to 17.1

Posted: **Wed Aug 22, 2018 1:23 pm**

4.17.0-17.3-liquorix-amd64 #1 ZEN SMP PREEMPT liquorix 4.17-13~mx17+1 (2018-08-21) x86_64 GNU/Linux

Works well with Nvidia 390.77 video driver. Thank you, Steven.

Posted: **Thu Aug 23, 2018 12:51 am**

Time to finally change kernels...

I hadn't seen the need to change from the 4.15 liquorix until now, with this new vulnerability.

On another note, 4.16 kernels didn't seem to work well in some distros of mine where there are frequent kernel updates/changes (Korora, and an Arch derivative). With 4.16 kernel, those distros kept freezing/hanging. Once the latest kernel series moved to 4.17 in those distros, it was fine.

Posted: **Thu Aug 23, 2018 2:03 pm**

asqwerth wrote: Thu Aug 23, 2018 12:51 am Time to finally change kernels...

I hadn't seen the need to change from the 4.15 liquorix until now, with this new vulnerability.

On another note, 4.16 kernels didn't seem to work well in some distros of mine where there are frequent kernel updates/changes (Korora, and an Arch derivative). With 4.16 kernel, those distros kept freezing/hanging. Once the latest kernel series moved to 4.17 in those distros, it was fine.

I haven't read up on the new L1TF problem, but I got the impression that it required actual hardware access for a desktop system. It was considered much more of a problem for virtualized systems on network servers.

I haven't tested if there's actually any Meltdown kpti mitigation for 32-bit systems yet, either. I'll see what the checker reports in Virtual Box.

Posted: **Thu Aug 23, 2018 11:50 pm**

I would prefer not to change, to be honest. 4.15 liquorix works nicely on both MX15/16 as well as MX17 installations, on both my PC and new laptop.

Posted: **Fri Aug 24, 2018 3:02 am**

asqwerth wrote: Thu Aug 23, 2018 11:50 pmI would prefer not to change, to be honest................

imo, always go with the latest stable kernel 4.17.18 (self compiled).
pro - fix faults, improve codes/securities.
con - new fix, come with new error, cycle continue endlessly.

Posted: **Mon Sep 03, 2018 10:45 pm**

We now have 4.18-4 in the test repo, based on vanilla kernel release 4.18.5. Upgraders should also use the latest Nvidia driver from backports as necessary, or other dkms packages and firmware from our MX test repo if your hardware requires those.

All 4.17 Liquorix kernel versions have been removed except for the last release.

Posted: **Tue Sep 04, 2018 10:31 pm**

https://plus.google.com/communities/117 ... 4346186936
https://drive.google.com/drive/folders/ ... DugCW492cp
There is a kernel patch-set from John Brodie for building a 32-Bit Liquorix-kernel (4.16.16-zen) for my Asus T100TA.
Question:
The 32-Bit Liquorix kernel-configuration file is ".config-i686-zen (baytrail)". Would that be suitable for building a live-kernel for MX-17?
Any comments highly appreciated.

Posted: **Wed Sep 05, 2018 3:55 am**

Since I upgraded from 4.15 to 4.17.x (I do not remember it now) the laptop works much better in general, especially shutting down is unbelievably quicker.

Posted: **Wed Sep 05, 2018 1:32 pm**

cinclus wrote: Tue Sep 04, 2018 10:31 pm https://plus.google.com/communities/117 ... 4346186936
https://drive.google.com/drive/folders/ ... DugCW492cp
There is a kernel patch-set from John Brodie for building a 32-Bit Liquorix-kernel (4.16.16-zen) for my Asus T100TA.
Question:
The 32-Bit Liquorix kernel-configuration file is ".config-i686-zen (baytrail)". Would that be suitable for building a live-kernel for MX-17?
Any comments highly appreciated.

Since I don't know what's different in his patchset, I don't feel qualified to answer that question.

Posted: **Wed Sep 05, 2018 6:02 pm**

cinclus wrote: Tue Sep 04, 2018 10:31 pm patch-set from John Brodie for building a 32-Bit Liquorix-kernel (4.16.16-zen) for my Asus T100TA.
Question:
The 32-Bit Liquorix kernel-configuration file is ".config-i686-zen (baytrail)". Would that be suitable for building a live-kernel for MX-17?

I would expect so. There is a 4.16.16-zen-i686 kernel already built on that site. It works on Peppermint, SparkyLinux, Mint 19 and was derived from a 4.16.11-zen-amd64 kernel build that does run on a remastered liveUSB MX-17.1 on my Asus T100CHI. But I haven't tested 4.16.16-zen-i686 on MX-Linux. The .config would be a good starting point if it doesn't just work. The kernel should work on an installation. It's the remastering support that is a little more demanding. Despite the Ubuntu name in the G+ group, the Ubuntu patches are not part of the built kernels from there.

Another approach would be to diff or meld the official liquorix .config, mine and an equivalent MX-Linux kernel .config. It's a bit tedious, but with enough trial and error you should get something that works. If it doesn't work, getting support to fix a customized kernel could be a challenge. The good news is that kernel support for the T100 family has never been better and it is possible to run with unmodified kernels >= 4.16. Auto dimming won't work and nobody has baytrail soc camera support, but most other stuff works.
-John

Posted: **Wed Sep 05, 2018 7:26 pm**

cinclus, I have an Asus T100TA netbook and have been unable to boot into any version of linux. Could you tell me how you did it? I would really like to install MX-17.1 on my netbook as well. Thank you for any assistance.

Posted: **Sat Sep 08, 2018 9:56 am**

jbMacAZ wrote: Wed Sep 05, 2018 6:02 pm
cinclus wrote: Tue Sep 04, 2018 10:31 pm The 32-Bit Liquorix kernel-configuration file is ".config-i686-zen (baytrail)". Would that be suitable for building a live-kernel for MX-17?
There is a 4.16.16-zen-i686 kernel already built on that site. It works on Peppermint, SparkyLinux, Mint 19 and was derived from a 4.16.11-zen-amd64 kernel build that does run on a remastered liveUSB MX-17.1 on my Asus T100CHI. But I haven't tested 4.16.16-zen-i686 on MX-Linux. The .config would be a good starting point if it doesn't just work. The kernel should work on an installation. It's the remastering support that is a little more demanding. Despite the Ubuntu name in the G+ group, the Ubuntu patches are not part of the built kernels from there.
Another approach would be to diff or meld the official liquorix .config, mine and an equivalent MX-Linux kernel .config. It's a bit tedious, but with enough trial and error you should get something that works. If it doesn't work, getting support to fix a customized kernel could be a challenge. The good news is that kernel support for the T100 family has never been better and it is possible to run with unmodified kernels >= 4.16. Auto dimming won't work and nobody has baytrail soc camera support, but most other stuff works.
-John

John,

thank you very much. These a very valuable hints from where to start. Perhaps a remastered MX-17 with this kernel
http://mxrepo.com/mx/testrepo/pool/test ... 1_i386.deb
could be a good starting point for learning to do the difficult 32-Bit uefi settings. But to go further and build a new kernel a patch-set for that very kernel would perhaps be helpful which I can't find under that same directory
http://mxrepo.com/mx/testrepo/pool/test ... -liquorix/.

-Joachim

Posted: **Sat Sep 08, 2018 2:17 pm**

The original 4.16-6 packaging is on github here: https://github.com/damentz/liquorix-pac ... ter=4.17-2

So you'd just need to get the 4.16.0 kernel tarball from kernel.org and rename it to linux-liquorix_4.16.orig.tar.xz, then extract it and the package tarball, and then put the debian folder from that into the extracted source. Then your extra patches can be added to debian/patches and the series file there, and hope that they are compatible.

Posted: **Sat Sep 08, 2018 7:00 pm**

Sorry, the built 32 bit kernel (4.16.16-zen-i686) is at the G+ T100/Ubuntu group community files. Try this link https://drive.google.com/drive/folders/ ... k_wGxaWPwP
copy the 2 files to an empty folder on your T100TA , open a terminal and install it with

Code: Select all

sudo dpkg -i *.deb

Next you need to use the wiki to update the kernel (kernel updater) on the liveUSB before remastering.

Disclaimer: 32 bit kerrnel optimized specifically for the the T100 (Intel baytrail). This kernel is unknown to the MX-linux team, and I am a relative newbie here...

Posted: **Mon Sep 17, 2018 5:54 pm**

Stevo wrote: Mon Sep 03, 2018 10:45 pm We now have 4.18-4 in the test repo, based on vanilla kernel release 4.18.5. Upgraders should also use the latest Nvidia driver from backports as necessary, or other dkms packages and firmware from our MX test repo if your hardware requires those.

All 4.17 Liquorix kernel versions have been removed except for the last release.

After having latest Liquorix kernel 4.18.0-8.1-liquorix-amd64 from test-repo installed,
and all works great.. I thought, why not give latest nvidia driver 390.48-2~mx17+1 from test-repo a try.
Not sure what the best procedure is to install this from test-repo.
I tried it this way: Enabled test-repo and run "ddm-mx -i nvidia" from console.
It looked promising, but ... here a short log with the final error building the module:

Code: Select all

 ddm-mx -i nvidia
 ...
 Kandidat ist: 390.48-2~mx17+1
 ...
 Nvidia-Befehl = apt-get install --reinstall -y --force-yes   nvidia-driver nvidia-settings nvidia-kernel-dkms nvidia-xconfig
 ...
nvidia-kernel-dkms (390.48-2~mx17+1) wird eingerichtet ...
Loading new nvidia-current-390.48 DKMS files...
Building for 4.18.0-8.1-liquorix-amd64
Building initial module for 4.18.0-8.1-liquorix-amd64
Error! Bad return status for module build on kernel: 4.18.0-8.1-liquorix-amd64 (x86_64)
Consult /var/lib/dkms/nvidia-current/390.48/build/make.log for more information.
...
update-initramfs: Generating /boot/initrd.img-4.18.0-8.1-liquorix-amd64
/usr/local/bin/ddm-mx: Zeile 472: erstelle Datei /etc/X11/xorg.conf: Datei oder Verzeichnis nicht gefunden

WARNING: Unable to locate/open X configuration file.

New X configuration file written to '/etc/X11/xorg.conf'

Rebooting into console purged with "ddm-mx -p nvidia"
with this card:

Code: Select all

Graphics:  Device-1: NVIDIA GK104 [GeForce GTX 770] driver: nouveau v: kernel 
           Display: x11 server: X.Org 1.19.2 driver: nouveau unloaded: fbdev,modesetting,vesa 
           resolution: 1680x1050~60Hz, 1920x1080~60Hz 
           OpenGL: renderer: Gallium 0.4 on NVE4 v: 4.3 Mesa 13.0.6

What the safest procedure or alternative procedure to do the job?

Posted: **Mon Sep 17, 2018 10:00 pm**

I'm pretty sure you'll have to install the newer Nvidia driver from backports for a 4.18 kernel until I port it over to the test repo. I know that version builds. The Nvidia-installer makes it pretty easy to install from backports, though.

Posted: **Tue Sep 18, 2018 1:05 pm**

OK, nvidia-driver 390.77 is ported over from backports to our test repo, so I hope it's now installable.

Posted: **Tue Sep 18, 2018 2:36 pm**

... One newbe question: What is the main advantage of the Liquorix Kernel, is it mostly for the compilation process and/ or gaming ?
Some tests here:
https://www.phoronix.com/scan.php?page= ... .17-Kernel

Edit:
I see than it is mostly for audio. and compilation.

Posted: **Tue Oct 02, 2018 2:59 pm**

Now updated to 4.18-13 (4.18.0-11.1) in the test repo, apparently with the nouveau drm problems worked out of the 4.18.11 base kernel release.

Posted: **Thu Nov 08, 2018 7:55 pm**

We're now up to 4.18-21, which is based on the 4.18.17 kernel source.

Posted: **Wed Nov 21, 2018 6:11 pm**

We're now up to 4.18-26, which disables that unfortunate STIPB mitigation which affected performance for many operations with hyperthreading.

Posted: **Wed Nov 21, 2018 7:08 pm**

Stevo wrote: Wed Nov 21, 2018 6:11 pm We're now up to 4.18-26, which disables that unfortunate STIPB mitigation which affected performance for many operations with hyperthreading.

Yay! And thank you.

Posted: **Tue Dec 11, 2018 3:10 pm**

We now have the 4.19-1 (4.19.0-8.1) Liquorix kernel in the test repo, which is based on the 4.19.8 and 4.19.9~rc vanilla kernel releases. We will be moving the compatible Nvidia 390.87 drivers very shortly to main in preparation for MX 18, which will be using a Debian 4.19 kernel, so you might wish to wait a bit for those to appear there if you use those--or you may already have installed those from the dev repo.

Changes include:
* switch to kernel v4.19 base
* merge 4.19.8
* merge 4.19.9-rc
* add muqss build fix for v4.19.7
* enable hierarchical group scheduling for bfq-sq + bfq-mq
* update version to 8.1

Posted: **Thu Dec 13, 2018 7:11 am**

wow, thank you very much.

Posted: **Tue Dec 18, 2018 7:05 pm**

Updated to 4.19-3 (4.19.0-10.1) in the test repo, which is based on vanilla kernel 4.19.10.

Posted: **Thu Dec 27, 2018 3:33 pm**

Now updated to 4.19-6 (4.19.0-12.1) in the test repo, which is based on the 4.9.12 vanilla kernel.

Posted: **Tue Jan 22, 2019 6:29 pm**

Now updated to 4.20-1 (44.20.0-3.1) in the test repo.

Please Note: The current Nvidia driver in our repos won't build on it, and it will need virtualbox 5.2.24 from the test repo, or virtualbox 6.0.2 from Oracle.

Posted: **Thu Feb 14, 2019 8:56 pm**

Now up to 4.20-7 (4.20.0-8.2) in our test repository. The Nvidia driver has since been updated to build with it.

Posted: **Sat Feb 16, 2019 6:27 am**

Stevo wrote: Thu Feb 14, 2019 8:56 pm Now up to 4.20-7 (4.20.0-8.2) in our test repository. The Nvidia driver has since been updated to build with it.

Nvidia legacy 340.xx don't build with it as none of previous versions of liquorix 4.20
Blank screen after reboot and again after reinstall from console with "ddm-mx -i nvidia"
Can you please update Nvidia legacy drivers too?

Posted: **Mon Mar 04, 2019 10:10 am**

Since this kernel is available only in the test repo, what is the proper way to install, so that it upgrades automatically to new versions?

Or do I have to manually update everytime?

Posted: **Mon Mar 04, 2019 11:22 am**

Otter wrote: Mon Mar 04, 2019 10:10 am Since this kernel is available only in the test repo, what is the proper way to install, so that it upgrades automatically to new versions?

Or do I have to manually update everytime?

liquorix kernel installs are manual and cumulative. If you install a new kernel every time a new one shows up, you'll have a lot of kernels installed and a pretty long list to boot from in grub. You should always keep one kernel on your system that works well with everything. Normally, you would install a new one and test it to make sure everything still works.

The easiest way to install a new liquorix kernel is from mxpi (mx package installer) from the Popular Applications tab locating kernels then checking the Liquorix 64 bit item.

mxpi.png

After you have multiple kernels installed, you can use MX Tools->MX Boot Options to set which one to boot from next time.
*Check the Options: Boot to drop down list.
When you want to remove a kernel, you can also use MX Boot options to show a list of the installed kernels, determine which one(s) you no longer want, note these, then use synaptic to uninstall them.

If the last kernel you installed causes your system to be unstable, after a restart, you can select a different kernel to boot from in the grub menu to get back to your desktop. Once there you can use mx boot options and set it to not boot from that last kernel, then go into synaptic and remove it.

*You can not remove a kernel you are currently booted from.
** You can also use grub-customier to see what kernels are installed and set their listed order and which one to boot from.

Posted: **Mon Mar 04, 2019 4:28 pm**

Liquorix kernels and headers also have a metapackage, such as "linux-image-liquorix-amd64" or "liquorix-headers-liquorix-amd64" for 64-bit CPUs that will pull in the latest version of the actual packages. If you install those from the test repo, you can then use the Package Installer to check for upgrades for those two packages, and upgrading those will pull in the newer kernel headers and kernel image. Older kernels are retained for safety's sake and must be installed manually--Synaptic's status and search functions help here. (installed packages, search for "liquorix")

We don't want to make upgrades too automatic unless the kernel fixes some security issue...

Posted: **Thu Mar 07, 2019 12:45 pm**

Thank you very much to you both for the detailed replies. I understand that I'll have to manually update Liquorix.

I'm not new to Linux distros, so I've already been following everything that you both have posted and I'm really grateful that you took the time to post all those stuffs. Thanks again. :)

Posted: **Fri Mar 08, 2019 4:57 pm**

dexy wrote: Sat Feb 16, 2019 6:27 am
Stevo wrote: Thu Feb 14, 2019 8:56 pm Now up to 4.20-7 (4.20.0-8.2) in our test repository. The Nvidia driver has since been updated to build with it.
Nvidia legacy 340.xx don't build with it as none of previous versions of liquorix 4.20
Blank screen after reboot and again after reinstall from console with "ddm-mx -i nvidia"
Can you please update Nvidia legacy drivers too?

We now have an update to the legacy 340xx drivers from Sid in test, which may help:

* use-nv-kernel-ARCH.o_shipped.patch: Simplify for better kernel
compatibility. (Closes: #922479)

And we need testers before we can move them to main, since we are leery of pushing drivers to main without testing, and I don't have the hardware.

The bug report says it will now build on 4.20 kernels.

Posted: **Sat Mar 09, 2019 11:11 am**

I have it on my build laptop

Code: Select all

System:    Host: mx17mainlt Kernel: 4.20.0-14.1-liquorix-amd64 x86_64 bits: 64 
           Desktop: Xfce 4.12.3 Distro: MX-18.1_x64 Continuum March 14  2018

So far, so good.

Posted: **Sat Mar 09, 2019 4:55 pm**

Thanks! Though I meant users that need the Nvidia legacy 304xx and 340xx drivers to build with it.

Posted: **Sat Mar 09, 2019 6:13 pm**

I install 4.20.0-14.1-liquorix-amd64 x86_64 on antiX 17.4 works well.

But if I want to boot to say 4.20.12-antix.1-amd64-smp I have to rerun sgfxi to boot to the desktop.
On my laptop with only antiX kernels I can boot to any version kernel..

(mainline 5)

Posted: **Sat Mar 09, 2019 7:10 pm**

If you do use sgfxi, it's standard to need to run it again to rebuild the drivers for new kernels (some say run it twice).

Liquorix just updated to 4.20-12 in the test repo, which provides 4.20.0-14.1 kernel packages, based on the 4.20.14 vanilla kernel.

Posted: **Sat Mar 09, 2019 7:50 pm**

I already know this as I have 4 antiX kernels installed.

Stevo wrote: Sat Mar 09, 2019 7:10 pm If you do use sgfxi, it's standard to need to run it again to rebuild the drivers for new kernels (some say run it twice).

Liquorix just updated to 4.20-12 in the test repo, which provides 4.20.0-14.1 kernel packages, based on the 4.20.14 vanilla kernel.

No I have to run sgfxi every time I want to boot to a different kernel this only happened after installing the Liquorix kernel . booting stops at command prompt after loading the printer drivers if I want to boot to say antiX 4.20.12 .
With my laptop and only antiX kernels installed I can boot straight to the desktop at anytime without using sgfxi no matter what kernel I chose to use..
And the fact that I have to use the advanced gurb menu to select Liquorix kernel . If I could move it the the main grub screen would be better.

It is ok stevo

(mainline 5)

Posted: **Sat Mar 09, 2019 11:03 pm**

Stevo wrote: Sat Mar 09, 2019 4:55 pm Thanks! Though I meant users that need the Nvidia legacy 304xx and 340xx drivers to build with it.

Oh great, all them clicks and 0 points

Posted: **Sun Mar 10, 2019 6:42 am**

Liquorix has been updated this afternoon antix17.3 4.20.0-15.1-liquorix-amd64 #1 ZEN SMP PREEMPT liquorix 4.20-13.1~sid (2019-03-10) x86_64 GNU/Linux

Also I had a win with changing my default boot kernel to 4.20.0-15.1-liquorix-amd64 #1 ZEN SMP PREEMPT liquorix 4.20-13.1~sid (2019-03-10) x86_64 GNU/Linux

One down one to go..

Posted: **Sun Mar 10, 2019 11:18 am**

linux-image-4.20.0-14.1-liquorix-amd64 fails to boot in GUI mode because nvidia modules failed to build. MX18 vanilla.

Code: Select all

CPU:       Topology: 8-Core model: AMD FX-8320 bits: 64 type: MCP L2 cache: 2048 KiB 
           Speed: 1525 MHz min/max: 1400/3500 MHz Core speeds (MHz): 1: 3079 2: 2414 3: 2161 4: 2325 5: 1726 6: 1738 7: 2072 
           8: 2202 
Graphics:  Device-1: NVIDIA GM107 [GeForce GTX 750 Ti] driver: nvidia v: 390.87 
           Display: x11 server: X.Org 1.19.2 driver: nvidia resolution: 1920x1080~60Hz 
           OpenGL: renderer: GeForce GTX 750 Ti/PCIe/SSE2 v: 4.6.0 NVIDIA 390.87

Posted: **Sun Mar 10, 2019 7:55 pm**

My mobile broadband quit working after booting on the new kernel. I'll need to revert back.

Posted: **Sun Mar 10, 2019 8:26 pm**

KoO wrote: Sun Mar 10, 2019 6:42 am Liquorix has been updated this afternoon antix17.3 4.20.0-15.1-liquorix-amd64 #1 ZEN SMP PREEMPT liquorix 4.20-13.1~sid (2019-03-10) x86_64 GNU/Linux

Also I had a win with changing my default boot kernel to 4.20.0-15.1-liquorix-amd64 #1 ZEN SMP PREEMPT liquorix 4.20-13.1~sid (2019-03-10) x86_64 GNU/Linux

One down one to go..

Please only report on the packages from the MX repositories here. You're getting yours from the upstream Liquorix repo, which is built against gcc-8 on Sid, and that may lead to problems with the Nvidia driver rebuild. Again, I also have backports in my OBS repository for those that don't want the whole MX repo.

Posted: **Sun Mar 10, 2019 8:38 pm**

mmikeinsantarosa wrote: Sun Mar 10, 2019 7:55 pm My mobile broadband quit working after booting on the new kernel. I'll need to revert back.

Is that the first 4.20 kernel you've tried?

Posted: **Sun Mar 10, 2019 8:40 pm**

Otter wrote: Sun Mar 10, 2019 11:18 am linux-image-4.20.0-14.1-liquorix-amd64 fails to boot in GUI mode because nvidia modules failed to build. MX18 vanilla.

Code: Select all

CPU:       Topology: 8-Core model: AMD FX-8320 bits: 64 type: MCP L2 cache: 2048 KiB 
           Speed: 1525 MHz min/max: 1400/3500 MHz Core speeds (MHz): 1: 3079 2: 2414 3: 2161 4: 2325 5: 1726 6: 1738 7: 2072 
           8: 2202 
Graphics:  Device-1: NVIDIA GM107 [GeForce GTX 750 Ti] driver: nvidia v: 390.87 
           Display: x11 server: X.Org 1.19.2 driver: nvidia resolution: 1920x1080~60Hz 
           OpenGL: renderer: GeForce GTX 750 Ti/PCIe/SSE2 v: 4.6.0 NVIDIA 390.87

Can you give the output of

Code: Select all

sudo dpkg-reconfigure nvidia-kernel-dkms

here in code tags so we can see the error?

Also the output of

Code: Select all

apt policy nvidia-driver

Posted: **Sun Mar 10, 2019 8:53 pm**

Stevo wrote: Sun Mar 10, 2019 8:38 pm
mmikeinsantarosa wrote: Sun Mar 10, 2019 7:55 pm My mobile broadband quit working after booting on the new kernel. I'll need to revert back.
Is that the first 4.20 kernel you've tried?

yup

Posted: **Sun Mar 10, 2019 8:59 pm**

Stevo wrote: Sat Mar 09, 2019 4:55 pm Though I meant users that need the Nvidia legacy 304xx and 340xx drivers to build with it.

Many thanks stevo,
What I can tell you is that it runs nice with 4.20.12-antix.1-amd64 on antiX here.

Code: Select all

System:
  Host: antix1 Kernel: 4.20.12-antix.1-amd64-smp x86_64 bits: 64 Desktop: IceWM 1.4.2 
  Distro: antiX-17.3_x64-full Helen Keller 25 December 2018 
Machine:
  Type: Laptop System: MEDION product: WIM2170 v: 20 serial: <root required> 
  Mobo: MEDION model: WIM2170 serial: <root required> BIOS: Phoenix v: 1.05 
  date: 11/01/2007 
Battery:
  ID-1: BAT0 charge: 64.2 Wh condition: 66.5/79.9 Wh (83%) 
CPU:
  Topology: Dual Core model: Intel Core2 Duo T5450 bits: 64 type: MCP 
  L2 cache: 2048 KiB 
  Speed: 1594 MHz min/max: 1000/1667 MHz Core speeds (MHz): 1: 998 2: 998 
Graphics:
  Device-1: NVIDIA G86M [GeForce 8400M GS] driver: nvidia v: 340.107 
  Display: server: X.Org 1.19.2 driver: nvidia resolution: 1280x800~60Hz 
  OpenGL: renderer: GeForce 8400M GS/PCIe/SSE2 v: 3.3.0 NVIDIA 340.107

Code: Select all

helga@antix1:~
$ apt-cache policy nvidia-legacy-340xx-driver
nvidia-legacy-340xx-driver:
  Installiert:           340.107-4~mx17+1
  Installationskandidat: 340.107-4~mx17+1
  Versionstabelle:
 *** 340.107-4~mx17+1 100
        100 /var/lib/dpkg/status
     340.107-2~mx17+1 500
        500 http://la.mxrepo.com/antix/stretch stretch/nonfree amd64 Packages
     340.106-2~deb9u1 500
        500 http://mirror.plusserver.com/debian/debian stretch/non-free amd64 Packages

Posted: **Sun Mar 10, 2019 9:43 pm**

Yes, that's one of the new drivers we put in the MX test repo for safety's sake until enough users test it. Thanks!

Posted: **Sun Mar 10, 2019 10:08 pm**

Stevo wrote: Sun Mar 10, 2019 8:26 pm
KoO wrote: Sun Mar 10, 2019 6:42 am Liquorix has been updated this afternoon antix17.3 4.20.0-15.1-liquorix-amd64 #1 ZEN SMP PREEMPT liquorix 4.20-13.1~sid (2019-03-10) x86_64 GNU/Linux

Also I had a win with changing my default boot kernel to 4.20.0-15.1-liquorix-amd64 #1 ZEN SMP PREEMPT liquorix 4.20-13.1~sid (2019-03-10) x86_64 GNU/Linux

One down one to go..
Please only report on the packages from the MX repositories here. You're getting yours from the upstream Liquorix repo, which is built against gcc-8 on Sid, and that may lead to problems with the Nvidia driver rebuild. Again, I also have backports in my OBS repository for those that don't want the whole MX repo.

Sorry Stevo never realised I was braking the rules..

I have completely removed liquorix from my system and back running on antix17.3 4.20.12-antix.1-amd64-smp #1 SMP PREEMPT Mon Feb 25 00:14:08 EET 2019 x86_64 GNU/Linux as default.

Will just wait and see if antiX build the liquorix kernel. As in an earlier thread was stated that antiX kernels are build on different framework to build their kernels than MX.. ?

The liquorix ran just fine but I did have the Nvidia rebuild problem as stated earlier.
Sorry Again

Posted: **Mon Mar 11, 2019 3:49 am**

Stevo wrote: Sun Mar 10, 2019 8:40 pm
Otter wrote: Sun Mar 10, 2019 11:18 am linux-image-4.20.0-14.1-liquorix-amd64 fails to boot in GUI mode because nvidia modules failed to build. MX18 vanilla.
Code: Select all
CPU:       Topology: 8-Core model: AMD FX-8320 bits: 64 type: MCP L2 cache: 2048 KiB 
           Speed: 1525 MHz min/max: 1400/3500 MHz Core speeds (MHz): 1: 3079 2: 2414 3: 2161 4: 2325 5: 1726 6: 1738 7: 2072 
           8: 2202 
Graphics:  Device-1: NVIDIA GM107 [GeForce GTX 750 Ti] driver: nvidia v: 390.87 
           Display: x11 server: X.Org 1.19.2 driver: nvidia resolution: 1920x1080~60Hz 
           OpenGL: renderer: GeForce GTX 750 Ti/PCIe/SSE2 v: 4.6.0 NVIDIA 390.87
Can you give the output of
Code: Select all
sudo dpkg-reconfigure nvidia-kernel-dkms
here in code tags so we can see the error?

Also the output of
Code: Select all
apt policy nvidia-driver

Solved it. I had made gcc-8 as default compiler. Changed it to gcc-6 with update alternatives, ran sudo dpkg-reconfigure nvidia-kernel-dkms & dkms install completed successfully. Ill keep this in mind. Thanks for pointing out in the right direction. :)

Posted: **Mon Mar 11, 2019 9:53 pm**

KoO wrote: Sun Mar 10, 2019 10:08 pm
Stevo wrote: Sun Mar 10, 2019 8:26 pm
KoO wrote: Sun Mar 10, 2019 6:42 am Liquorix has been updated this afternoon antix17.3 4.20.0-15.1-liquorix-amd64 #1 ZEN SMP PREEMPT liquorix 4.20-13.1~sid (2019-03-10) x86_64 GNU/Linux

Also I had a win with changing my default boot kernel to 4.20.0-15.1-liquorix-amd64 #1 ZEN SMP PREEMPT liquorix 4.20-13.1~sid (2019-03-10) x86_64 GNU/Linux

One down one to go..
Please only report on the packages from the MX repositories here. You're getting yours from the upstream Liquorix repo, which is built against gcc-8 on Sid, and that may lead to problems with the Nvidia driver rebuild. Again, I also have backports in my OBS repository for those that don't want the whole MX repo.
Sorry Stevo never realised I was braking the rules..

I have completely removed liquorix from my system and back running on antix17.3 4.20.12-antix.1-amd64-smp #1 SMP PREEMPT Mon Feb 25 00:14:08 EET 2019 x86_64 GNU/Linux as default.

Will just wait and see if antiX build the liquorix kernel. As in an earlier thread was stated that antiX kernels are build on different framework to build their kernels than MX.. ?

The liquorix ran just fine but I did have the Nvidia rebuild problem as stated earlier.
Sorry Again

If you are using the kernels directly from Liquorix, they have their own forum...where they will point you to my separate OBS repo for Stretch/antiX Liquorix backports (for the third time in this thread). I doubt that antiX has the time to reinvent the wheel when I'm already building the kernel backports.

Posted: **Tue Mar 19, 2019 3:10 pm**

We have now added the last release of the Liquorix 4.20 kernel series, 4.20-15, which is based on the 4.20.16 vanilla kernel release.

We've also added the new 5.0.0-1 Liquorix kernel. This version switches back to p-state power saving for modern Intel CPUs, which is the same that the stock MX and Debian kernels use. Like with those, it's also possible to start with a boot flag to disable p-state and use cpufreq instead.

64-bit dkms packages tested and updated to build with the new 5.0 kernel:

The new Nvidia 410.104 driver in our test repo. Older versions will not build, and Nvidia only supports 64-bit systems with the 4XX releases, though also supporting 32-bit programs on 64-bit. I was able to get Bumblebee working again on my Optimus laptop for both 64-bit and 32-bit, though the MX Nvidia driver installer might need updating to work with the newer driver---primus packages apparently are not needed.

Code: Select all

$ optirun inxi -G
Graphics:  Device-1: Intel driver: i915 v: kernel 
           Device-2: NVIDIA driver: nvidia v: 410.104 
           Display: x11 server: X.Org 1.19.2 driver: intel resolution: 1920x1080~60Hz 
           OpenGL: renderer: GeForce GTX 1050 Ti/PCIe/SSE2 v: 4.6.0 NVIDIA 410.104

The latest Virtualbox 6.0.4-7~mx17+1 backport from Sid in the test repo. This also only supports 64-bit host systems now, though 32-bit guests are still supported.

Broadcom-sta-dkms 6.30.223.271-9.1~mx17+1 in the main repo builds.

Ndiswrapper-dkms was patched for 5.0 support in 1.61-0.1~mx17+4 and is in the main repo.

Bbswitch-dkms for Bumblebee in the main repo still builds.

The latest zfs-dkms in the test repo successfully builds.

Posted: **Wed Mar 20, 2019 10:14 am**

Dear Stevo,

Thanks for letting me know about this particular Liquorix thread. I'll be following this one as well as the older one.

Lawrence

Posted: **Wed Mar 20, 2019 10:37 am**

5.0.0-1 Liquorix so far so good here.

Posted: **Wed Mar 20, 2019 11:43 am**

5.0.0.2.1 working great on my old thinkpad W520 and X230 !

Posted: **Thu Mar 21, 2019 9:26 am**

Mine too on an Asus Rogstrix.

Posted: **Thu Mar 21, 2019 3:47 pm**

Stevo wrote: Fri Mar 08, 2019 4:57 pm
dexy wrote: Sat Feb 16, 2019 6:27 am
Stevo wrote: Thu Feb 14, 2019 8:56 pm Now up to 4.20-7 (4.20.0-8.2) in our test repository. The Nvidia driver has since been updated to build with it.
Nvidia legacy 340.xx don't build with it as none of previous versions of liquorix 4.20
Blank screen after reboot and again after reinstall from console with "ddm-mx -i nvidia"
Can you please update Nvidia legacy drivers too?
We now have an update to the legacy 340xx drivers from Sid in test, which may help:

* use-nv-kernel-ARCH.o_shipped.patch: Simplify for better kernel
compatibility. (Closes: #922479)
And we need testers before we can move them to main, since we are leery of pushing drivers to main without testing, and I don't have the hardware.

The bug report says it will now build on 4.20 kernels.

Works like a charm.

Code: Select all

System:    Host: mx Kernel: 4.20.0-16.2-liquorix-amd64 x86_64 bits: 64 compiler: gcc v: 6.3.0 
           Desktop: Xfce 4.12.3 Distro: MX-18.1_x64 Continuum Feb 9  2019 
           base: Debian GNU/Linux 9 (stretch) 
Machine:   Type: Desktop System: FUJITSU SIEMENS product: ESPRIMO P5925 v: N/A serial: <filter> 
           Mobo: FUJITSU SIEMENS model: D2584-A1 v: S26361-D2584-A1 serial: <filter> 
           BIOS: FUJITSU SIEMENS // Phoenix v: 6.00 R1.18.2584.A1 date: 02/05/2009 
CPU:       Topology: Dual Core model: Intel Core2 Duo E6550 bits: 64 type: MCP arch: Core Merom 
           rev: B L2 cache: 4096 KiB 
           flags: lm nx pae sse sse2 sse3 ssse3 vmx bogomips: 9309 
           Speed: 2128 MHz min/max: 1999/2332 MHz Core speeds (MHz): 1: 2128 2: 2044 
Graphics:  Device-1: NVIDIA G84 [GeForce 8600 GTS] vendor: Micro-Star MSI driver: nvidia 
           v: 340.107 bus ID: 01:00.0 
           Display: x11 server: X.Org 1.19.2 driver: nvidia resolution: 1680x1050~60Hz 
           OpenGL: renderer: GeForce 8600 GTS/PCIe/SSE2 v: 3.3.0 NVIDIA 340.107 
           direct render: Yes 
Audio:     Device-1: Intel 82801I HD Audio vendor: Fujitsu Solutions driver: snd_hda_intel 
           v: kernel bus ID: 00:1b.0 
           Sound Server: ALSA v: k4.20.0-16.2-liquorix-amd64 
Network:   Device-1: Intel 82566DM-2 Gigabit Network vendor: Fujitsu Solutions driver: e1000e 
           v: 3.2.6-k port: 1820 bus ID: 00:19.0 
           IF: eth0 state: up speed: 100 Mbps duplex: full mac: <filter> 
           IF-ID-1: ppp0 state: unknown speed: N/A duplex: N/A mac: N/A 
Drives:    Local Storage: total: 149.05 GiB used: 44.07 GiB (29.6%) 
           ID-1: /dev/sda vendor: Western Digital model: WD1600AAJS-00PSA0 size: 149.05 GiB 
Partition: ID-1: / size: 55.86 GiB used: 9.10 GiB (16.3%) fs: ext4 dev: /dev/sda3 
Sensors:   System Temperatures: cpu: 40.0 C mobo: N/A gpu: nvidia temp: 74 C 
           Fan Speeds (RPM): N/A gpu: nvidia fan: 50% 
Repos:     Active apt repos in: /etc/apt/sources.list.d/antix.list 
           1: deb http://la.mxrepo.com/antix/stretch/ stretch main
           Active apt repos in: /etc/apt/sources.list.d/debian-stable-updates.list 
           1: deb http://debian.petarmaric.com/debian/ stretch-updates main contrib non-free
           Active apt repos in: /etc/apt/sources.list.d/debian.list 
           1: deb http://debian.petarmaric.com/debian/ stretch main contrib non-free
           2: deb http://security.debian.org/ stretch/updates main contrib non-free
           Active apt repos in: /etc/apt/sources.list.d/mx.list 
           1: deb http://mxrepo.com/mx/repo/ stretch main non-free
           No active apt repos in: /etc/apt/sources.list.d/various.list 
Info:      Processes: 196 Uptime: 11h 40m Memory: 7.54 GiB used: 1.16 GiB (15.4%) Init: SysVinit 
           runlevel: 5 Compilers: gcc: 6.3.0 Shell: bash v: 4.4.12 inxi: 3.0.29

Thanks Stevo

EDIT:
Unfortunately it won't build with newest liquorix 5.0 kernels.

I like and use liquorix kernels because on my machine they work best over all other kernels (I try them all).
Machine is more responsive in multitasking and even in browsing internet (sites and browsers tend to be resource hungrier as time pass), coping/moving large (numbers of) files and compressing/decompressing archives are lag free etc.
So I really appreciate your hard work to bring these kernels in mx linux.

Posted: **Fri Apr 12, 2019 3:29 pm**

Updating to 5.0-6, based on 5.0.7 kernel, in the test repo.
I'm also sending the Nvidia 340xx legacy drivers to the test repo which are patched to build on 5.0 kernels. The 390xx legacy drivers in main will also build on these kernels, for those that can't use the 410.104 in the test repo, or or still using 32-bit.

Posted: **Fri Apr 12, 2019 5:37 pm**

Works perfectly.

Posted: **Fri Apr 12, 2019 6:56 pm**

Tried your Liquorix 5.0.7 on antiX 17.4.1 yesterday won,t boot on to desktop even after running (ddm-mx -i nvidia) 410.104 driver . Uninstalled
But your Liquorix 5.0.6 runs just fine.

Posted: **Fri Apr 12, 2019 9:32 pm**

Stretch-backports has removed the 410.104 driver, but that doesn't make any difference it you already had it installed. The legacy 390xx 390.116 driver in MX main also builds on the 5.0 kernel.

Posted: **Fri Apr 12, 2019 10:36 pm**

Thanks Stevo I have uninstall 5.0.7. for some reason won't go to the desktop after ddm-mx -i nvidia. Will say with 5.0.6 for now.. Awesome Sound (only thing is using mvp a small 4mm opaque bar at the top of the screen not even worth worrying about really)
Still running 410.104 from Deb.

anticapitalista Any hope uploading the 390.116 to antiX repo (No biggie if not). Many repo's in the antiX list not even working. Been deleting them from the list.

Thanks

Posted: **Sat Apr 13, 2019 5:10 am**

KoO wrote: Fri Apr 12, 2019 10:36 pm
anticapitalista Any hope uploading the 390.116 to antiX repo (No biggie if not). Many repo's in the antiX list not even working. Been deleting them from the list.

Thanks

According to this all the mirrors are working fine. Post your antix.list

https://antixlinux.com/mirmon-packages/

Posted: **Sat Apr 13, 2019 8:03 am**

Sorry anticapitalista I did not mean the main antiX repos.

sudo grep -Erh ^deb /etc/apt/sources.list*
deb http://mx.debian.nz/antix/stretch/ stretch nonfree nosystemd main
deb http://ftp.au.debian.org/debian/ stretch main contrib non-free
deb http://security.debian.org/ stretch/updates main contrib non-free
deb http://ftp.au.debian.org/debian/ stretch-updates non-free contrib main

Just the extra repos like onion , Liquorix ,opera I just remove these.

Posted: **Sat Apr 13, 2019 2:25 pm**

KoO wrote: Fri Apr 12, 2019 10:36 pm Thanks Stevo I have uninstall 5.0.7. for some reason won't go to the desktop after ddm-mx -i nvidia. Will say with 5.0.6 for now.. Awesome Sound (only thing is using mvp a small 4mm opaque bar at the top of the screen not even worth worrying about really)
Still running 410.104 from Deb.

anticapitalista Any hope uploading the 390.116 to antiX repo (No biggie if not). Many repo's in the antiX list not even working. Been deleting them from the list.

Thanks

Did you also install the 5.0-6 (5.0.0-7.1) Liquorix kernel headers? If you have module-assistant installed and the repo with the headers enabled, "sudo m-a prepare" will automatically get them if you're running the kernel.

Posted: **Sat Apr 13, 2019 4:39 pm**

The patched Nvidia 340xx legacy driver runs well here with 5.0.0-7.1-liquorix

Code: Select all

System:    Host: mx Kernel: 5.0.0-7.1-liquorix-amd64 x86_64 bits: 64 compiler: gcc v: 6.3.0 
           Desktop: Xfce 4.12.3 Distro: MX-18.2_x64 Continuum Dec 20  2018 
           base: Debian GNU/Linux 9 (stretch) 
Machine:   Type: Laptop System: MEDION product: WIM2170 v: 20 serial: <filter> 
           Mobo: MEDION model: WIM2170 serial: <filter> BIOS: Phoenix v: 1.05 date: 11/01/2007 
Battery:   ID-1: BAT0 charge: 66.5 Wh condition: 66.5/79.9 Wh (83%) model: FOX-LGC-72 WIS_ME3 
           status: Full 
CPU:       Topology: Dual Core model: Intel Core2 Duo T5450 bits: 64 type: MCP arch: Core Merom 
           rev: D L2 cache: 2048 KiB 
           flags: lm nx pae sse sse2 sse3 ssse3 bogomips: 6650 
           Speed: 1523 MHz min/max: 1000/1667 MHz Core speeds (MHz): 1: 1523 2: 1366 
Graphics:  Device-1: NVIDIA G86M [GeForce 8400M GS] vendor: Wistron driver: nvidia v: 340.107 
           bus ID: 01:00.0 
           Display: x11 server: X.Org 1.19.2 driver: nvidia resolution: 1280x800~60Hz 
           OpenGL: renderer: GeForce 8400M GS/PCIe/SSE2 v: 3.3.0 NVIDIA 340.107 
           direct render: Yes 
Audio:     Device-1: Intel 82801H HD Audio vendor: Wistron driver: snd_hda_intel v: kernel 
           bus ID: 00:1b.0 
           Sound Server: ALSA v: k5.0.0-7.1-liquorix-amd64 
Network:   Device-1: Realtek RTL8101/2/6E PCI Express Fast/Gigabit Ethernet 
           vendor: Wistron RTL8101e Medion WIM 2210 Notebook PC driver: r8169 v: kernel 
           port: 4000 bus ID: 06:00.0 
           IF: eth0 state: down mac: <filter> 
           Device-2: Qualcomm Atheros AR242x / AR542x Wireless Network Adapter driver: ath5k 
           v: kernel port: 4000 bus ID: 08:00.0 
           IF: wlan0 state: up mac: <filter> 
Drives:    Local Storage: total: 111.79 GiB used: 7.10 GiB (6.3%) 
           ID-1: /dev/sdb vendor: Samsung model: SSD 750 EVO 120GB size: 111.79 GiB 
Partition: ID-1: / size: 16.25 GiB used: 7.10 GiB (43.7%) fs: ext4 dev: /dev/sdb2 
Sensors:   System Temperatures: cpu: 56.0 C mobo: N/A gpu: nvidia temp: 60 C 
           Fan Speeds (RPM): N/A 
Repos:     Active apt repos in: /etc/apt/sources.list.d/antix.list 
           1: deb http://la.mxrepo.com/antix/stretch/ stretch main
           Active apt repos in: /etc/apt/sources.list.d/debian-stable-updates.list 
           1: deb http://ftp.de.debian.org/debian/ stretch-updates main contrib non-free
           Active apt repos in: /etc/apt/sources.list.d/debian.list 
           1: deb http://ftp.de.debian.org/debian/ stretch main contrib non-free
           2: deb http://security.debian.org/ stretch/updates main contrib non-free
           Active apt repos in: /etc/apt/sources.list.d/mx.list 
           1: deb http://la.mxrepo.com/mx/repo/ stretch main non-free
           No active apt repos in: /etc/apt/sources.list.d/various.list 
Info:      Processes: 200 Uptime: 25m Memory: 3.85 GiB used: 770.7 MiB (19.5%) Init: SysVinit 
           runlevel: 5 Compilers: gcc: 6.3.0 Shell: bash v: 4.4.12 inxi: 3.0.33

Thanks .

Posted: **Sat Apr 13, 2019 5:20 pm**

My mobile broadband appears to like this one.

Posted: **Sat Apr 13, 2019 5:20 pm**

A general question: The liquorix kernel does not upgrade automatically. iam on 5.0.0-4.
When does it make sense to upgrade manually? And is there anyplace o see - in plain english, what the changes are in new versions?
Thanks a lot. its working great on my aging thinkpad w520/x230.,

Posted: **Sat Apr 13, 2019 5:57 pm**

caprea wrote: Sat Apr 13, 2019 4:39 pm The patched Nvidia 340xx legacy driver runs well here with 5.0.0-7.1-liquorix
...

Cool! Anti may want to add it to the antiX repos for 5.0 kernels, too. Nvidia may have given up on the 304xx drivers--at least Arch isn't even providing those any longer.

Posted: **Sat Apr 13, 2019 9:00 pm**

Stevo wrote: Sat Apr 13, 2019 2:25 pm
KoO wrote: Fri Apr 12, 2019 10:36 pm Thanks Stevo I have uninstall 5.0.7. for some reason won't go to the desktop after ddm-mx -i nvidia. Will say with 5.0.6 for now.. Awesome Sound (only thing is using mvp a small 4mm opaque bar at the top of the screen not even worth worrying about really)
Still running 410.104 from Deb.

anticapitalista Any hope uploading the 390.116 to antiX repo (No biggie if not). Many repo's in the antiX list not even working. Been deleting them from the list. (saying with sgfxi)

Thanks
Did you also install the 5.0-6 (5.0.0-7.1) Liquorix kernel headers? If you have module-assistant installed and the repo with the headers enabled, "sudo m-a prepare" will automatically get them if you're running the kernel.

Well don't ask me how.

Reinstalled Liquorix 5.0.0-7.1 from the MX test repo with the header as I did the first time. Then rebooted I had 410.104 from deb now removed from the server. With MX test repo still on after (ddm-mx -i nvidia) it install the MX of 410.104 instead. Just ended up at the command line again just would not boot to desktop.

With the 410.104 deb no longer on server had no choice but to use the MX version of the driver. No matter what I did would not go to the desktop.

So then with only one option left = sgfxi drop to su installed 418.43 rebooted straight to the logon screen.

I have tested everything I can, all is working as it should music awesome sound, movies , youtube. Also can not find one broken package.. I'm Staying Right Here

5.0.0-6.1 is your obs version from opensuse
5.0.0-7.1 is your MX test version

Thanks Stevo

Posted: **Sat Apr 13, 2019 10:19 pm**

Sid has a newer version of the 304xx legacy drivers that may fix the builds on the 5.0 kernel, so I'll try that backport.

Posted: **Sat Apr 13, 2019 11:46 pm**

Stevo

I will be sticking to the nvidia proprietary driver. I know it is non-free but so was my video card non-free.

Thanks for your Great work.

Posted: **Sun Apr 14, 2019 4:12 pm**

nvidia module install fails for 5.0.x series. Here is the make.log for 5.0.0-5.1-liquorix-amd64.

Code: Select all

$ apt policy nvidia-driver
nvidia-driver:
  Installed: 390.87-8~deb9u1
  Candidate: 390.87-8~deb9u1
  Version table:
 *** 390.87-8~deb9u1 500
        500 https://xxxyyyzzz/debian stretch/non-free amd64 Packages
        100 /var/lib/dpkg/status

Nope, I'm not using gcc7/8 and rather using "gcc version 6.3.0 20170516 (Debian 6.3.0-18+deb9u1)" from the stable repo.

Posted: **Sun Apr 14, 2019 5:06 pm**

Otter wrote: Sun Apr 14, 2019 4:12 pm nvidia module install fails for 5.0.x series. Here is the make.log for 5.0.0-5.1-liquorix-amd64.
Code: Select all
$ apt policy nvidia-driver
nvidia-driver:
  Installed: 390.87-8~deb9u1
  Candidate: 390.87-8~deb9u1
  Version table:
 *** 390.87-8~deb9u1 500
        500 https://xxxyyyzzz/debian stretch/non-free amd64 Packages
        100 /var/lib/dpkg/status
Nope, I'm not using gcc7/8 and rather using "gcc version 6.3.0 20170516 (Debian 6.3.0-18+deb9u1)" from the stable repo.

Yes, we know that 390.87 doesn't build on 5.0 kernels, but nvidia-legacy-390xx 390.116 in our main repo does. The MX Nvidia installer doesn't account for these things, since the official kernel is still 4.19, and things are changing quickly with the Nvidia drivers.

I still had to adapt and add the Arch AUR patch to get the Sid nvidia-legacy-304xx driver to build on 5.0 kernels, but it's on its way to the test repo now. If it works, antiX should also be interested in the patched version. I can build it now, but don't have the hardware to test it.

Posted: **Wed Apr 17, 2019 6:21 am**

I can test it, if you're interested.

BTW GPU info. in case if you need it.

Code: Select all

Graphics:  Device-1: NVIDIA GM107 [GeForce GTX 750 Ti] driver: nvidia v: 390.87
Display: x11 server: X.Org 1.19.2 driver: nvidia resolution: 1920x1080~60Hz
OpenGL: renderer: GeForce GTX 750 Ti/PCIe/SSE2 v: 4.6.0 NVIDIA 390.87

Posted: **Fri Apr 19, 2019 12:22 pm**

Stevo wrote: Fri Apr 12, 2019 3:29 pm Updating to 5.0-6, based on 5.0.7 kernel, in the test repo.
I'm also sending the Nvidia 340xx legacy drivers to the test repo which are patched to build on 5.0 kernels. The 390xx legacy drivers in main will also build on these kernels, for those that can't use the 410.104 in the test repo, or or still using 32-bit.

Patched Nvidia 340xx legacy drivers build with no problem, even with newest liquorix 5.0-7~mx17+1

Code: Select all

System:    Host: mx Kernel: 5.0.0-8.1-liquorix-amd64 x86_64 bits: 64 compiler: gcc v: 6.3.0 
           Desktop: Xfce 4.12.3 Distro: MX-18.2_x64 Continuum Feb 9  2019 
           base: Debian GNU/Linux 9 (stretch) 
Machine:   Type: Desktop System: FUJITSU SIEMENS product: ESPRIMO P5925 v: N/A serial: <filter> 
           Mobo: FUJITSU SIEMENS model: D2584-A1 v: S26361-D2584-A1 serial: <filter> 
           BIOS: FUJITSU SIEMENS // Phoenix v: 6.00 R1.18.2584.A1 date: 02/05/2009 
CPU:       Topology: Dual Core model: Intel Core2 Duo E6550 bits: 64 type: MCP arch: Core Merom 
           rev: B L2 cache: 4096 KiB 
           flags: lm nx pae sse sse2 sse3 ssse3 vmx bogomips: 9309 
           Speed: 1995 MHz min/max: 1999/2332 MHz Core speeds (MHz): 1: 1995 2: 2166 
Graphics:  Device-1: NVIDIA G84 [GeForce 8600 GTS] vendor: Micro-Star MSI driver: nvidia 
           v: 340.107 bus ID: 01:00.0 
           Display: x11 server: X.Org 1.19.2 driver: nvidia resolution: 1680x1050~60Hz 
           OpenGL: renderer: GeForce 8600 GTS/PCIe/SSE2 v: 3.3.0 NVIDIA 340.107 
           direct render: Yes 
Audio:     Device-1: Intel 82801I HD Audio vendor: Fujitsu Solutions driver: snd_hda_intel 
           v: kernel bus ID: 00:1b.0 
           Sound Server: ALSA v: k5.0.0-8.1-liquorix-amd64 
Network:   Device-1: Intel 82566DM-2 Gigabit Network vendor: Fujitsu Solutions driver: e1000e 
           v: 3.2.6-k port: 1820 bus ID: 00:19.0 
           IF: eth0 state: up speed: 100 Mbps duplex: full mac: <filter> 
           IF-ID-1: ppp0 state: unknown speed: N/A duplex: N/A mac: N/A 
Drives:    Local Storage: total: 152.80 GiB used: 46.71 GiB (30.6%) 
           ID-1: /dev/sda vendor: Western Digital model: WD1600AAJS-00PSA0 size: 149.05 GiB 
           ID-2: /dev/sdb type: USB model: General size: 3.75 GiB 
Partition: ID-1: / size: 55.86 GiB used: 10.01 GiB (17.9%) fs: ext4 dev: /dev/sda3 
Sensors:   System Temperatures: cpu: 38.0 C mobo: N/A gpu: nvidia temp: 74 C 
           Fan Speeds (RPM): N/A gpu: nvidia fan: 40% 
Repos:     Active apt repos in: /etc/apt/sources.list.d/antix.list 
           1: deb http://la.mxrepo.com/antix/stretch stretch main
           Active apt repos in: /etc/apt/sources.list.d/debian-stable-updates.list 
           1: deb http://ftp.us.debian.org/debian/ stretch-updates main contrib non-free
           Active apt repos in: /etc/apt/sources.list.d/debian.list 
           1: deb http://ftp.us.debian.org/debian/ stretch main contrib non-free
           2: deb http://security.debian.org/ stretch/updates main contrib non-free
           Active apt repos in: /etc/apt/sources.list.d/mx.list 
           1: deb http://mxrepo.com/mx/repo/ stretch main non-free
           Active apt repos in: /etc/apt/sources.list.d/skype-stable.list 
           1: deb [arch=amd64] https://repo.skype.com/deb stable main
           No active apt repos in: /etc/apt/sources.list.d/various.list 
Info:      Processes: 190 Uptime: 6m Memory: 7.54 GiB used: 807.6 MiB (10.5%) Init: SysVinit 
           runlevel: 5 Compilers: gcc: 6.3.0 Shell: bash v: 4.4.12 inxi: 3.0.33

Thank you Stevo

Posted: **Fri Apr 19, 2019 1:00 pm**

Some thing Different..

Code: Select all

 System:    Host: debian10 Kernel: 5.0.0-8.1-liquorix-amd64 x86_64 bits: 64 Desktop: i3 4.16.1-169-g60a6d149 
           Distro: Debian GNU/Linux buster/sid 
Machine:   Type: Desktop System: ASUS product: All Series v: N/A serial: <root required> 
           Mobo: ASUSTeK model: H97I-PLUS v: Rev X.0x serial: <root required> UEFI: American Megatrends v: 3602 
           date: 04/08/2018 
CPU:       Topology: Quad Core model: Intel Xeon E3-1241 v3 bits: 64 type: MT MCP L2 cache: 8192 KiB 
           Speed: 1256 MHz min/max: 800/3900 MHz Core speeds (MHz): 1: 940 2: 943 3: 940 4: 944 5: 872 6: 969 7: 955 8: 947 
Graphics:  Device-1: NVIDIA GM204 [GeForce GTX 970] driver: nvidia v: 418.56 
           Display: x11 server: X.Org 1.20.3 driver: nvidia resolution: 2560x1440~60Hz 
           OpenGL: renderer: GeForce GTX 970/PCIe/SSE2 v: 4.6.0 NVIDIA 418.56 
Audio:     Device-1: Intel 9 Series Family HD Audio driver: snd_hda_intel 
           Device-2: NVIDIA GM204 High Definition Audio driver: snd_hda_intel 
           Device-3: TEAC type: USB driver: hid-generic,snd-usb-audio,usbhid 
           Device-4: C-Media type: USB driver: hid-generic,snd-usb-audio,usbhid 
           Sound Server: ALSA v: k5.0.0-8.1-liquorix-amd64 
Network:   Device-1: Intel Ethernet I218-V driver: e1000e 
           IF: eno1 state: up speed: 1000 Mbps duplex: full mac: 08:62:66:c7:c3:66 
Drives:    Local Storage: total: 931.52 GiB used: 382.44 GiB (41.1%) 
           ID-1: /dev/sda vendor: Samsung model: SSD 860 EVO 500GB size: 465.76 GiB 
           ID-2: /dev/sdb vendor: Samsung model: SSD 850 EVO 500GB size: 465.76 GiB 
Partition: ID-1: / size: 143.19 GiB used: 26.27 GiB (18.3%) fs: ext4 dev: /dev/sda4 
           ID-2: swap-1 size: 4.0 MiB used: 3.9 MiB (97.7%) fs: swap dev: /dev/sda6 
Sensors:   System Temperatures: cpu: 33.5 C mobo: 27.8 C gpu: nvidia temp: 52 C 
           Fan Speeds (RPM): cpu: 2057 fan-1: 916 fan-3: 922 fan-4: 0 fan-5: 0 gpu: nvidia fan: 0% 
Info:      Processes: 224 Uptime: 8h 15m Memory: 15.61 GiB used: 1.41 GiB (9.0%) Shell: bash inxi: 3.0.32

Posted: **Fri Apr 19, 2019 1:19 pm**

Stevo wrote: Sat Apr 13, 2019 5:57 pm
caprea wrote: Sat Apr 13, 2019 4:39 pm The patched Nvidia 340xx legacy driver runs well here with 5.0.0-7.1-liquorix
...
Cool! Anti may want to add it to the antiX repos for 5.0 kernels, too. Nvidia may have given up on the 304xx drivers--at least Arch isn't even providing those any longer.

The patched Nvidia 304xx legacy driver also runs well here with 5.0.0-7.1-liquorix.
(And many (all?) other kernels: 4.9;4.15;4.20; only exception: 4.19.0.1)

Posted: **Mon Jun 03, 2019 4:08 pm**

We've now added the 5.1-1 (based on the 5.1.6 vanilla) Liquorix kernel, as well as removed all but the last 5.0 packages. The following DKMS drivers will build on it, at least on my tests for 64-bit.

Patched broadcom-sta-dkms in our test repo.
Virtual Box 5.2.30 in the test repo.
Nvidia driver 4.18.74 in the test repo.
Ndiswrapper in the main repo.

Posted: **Tue Jun 04, 2019 9:35 am**

Stevo wrote: Mon Jun 03, 2019 4:08 pm We've now added the 5.1-1 (based on the 5.1.6 vanilla) Liquorix kernel

You chose not to add the headers as a dependency?

Posted: **Tue Jun 04, 2019 12:23 pm**

@Stevo: did you know that Liquorix now offer stretch-based kernel versions?

https://liquorix.net/debian/dists/

Posted: **Tue Jun 04, 2019 2:47 pm**

Friedrich wrote: Tue Jun 04, 2019 9:35 am
Stevo wrote: Mon Jun 03, 2019 4:08 pm We've now added the 5.1-1 (based on the 5.1.6 vanilla) Liquorix kernel
You chose not to add the headers as a dependency?

Yes, I left the dependencies as is; they are not a hard dependency of any Debian type kernel, but the MX Package Installer does automatically install the headers along with the kernel. If you're missing them, module-assistant's "m-a prepare" command is easy enough to run to solve that issue, IMO.

Posted: **Tue Jun 04, 2019 2:50 pm**

Head_on_a_Stick wrote: Tue Jun 04, 2019 12:23 pm @Stevo: did you know that Liquorix now offer stretch-based kernel versions?

https://liquorix.net/debian/dists/

Yes, perhaps we can switch the package installer to use their repo now. It would save me a couple of hours a week compiling time...

Posted: **Tue Jun 04, 2019 4:48 pm**

Stevo wrote: Tue Jun 04, 2019 2:47 pm .. the MX Package Installer does automatically install the headers along with the kernel.

Seems it does not. That's why I am asking.
Tested on 2 separate PC.

Posted: **Tue Jun 04, 2019 7:09 pm**

Can you enable the MX test repo in the MX repo manager, update the apt database

Code: Select all

sudo apt update

Then check:

Code: Select all

apt policy linux-headers-5.1.0*

If not installed, run

Code: Select all

sudo m-a prepare

as above to get them, then disable the test repo in Repo Man.

I'll check to see what's wrong with the package installer, though we are going to switch to the Liquorix repo soon.

Posted: **Wed Jun 05, 2019 9:42 am**

Your latest liquorix kernel can actually run my mobile broadband card but I did have to upgrade virtualbox to the latest in test to get a /dev/vboxdrv to show up.

Posted: **Wed Jun 05, 2019 3:23 pm**

Actually, virtualbox 5.2.30 also works fine with it, and it's also in the test repo. I prefer it because it's easier to theme.

Switching to the Liquorix version might have some issues if you update often, as they introduce changes and then pull them quickly when they prove to have problems--just look at the latest changelog--something obviously went wrong with those changes:

Code: Select all

linux-liquorix (5.1-4ubuntu1~xenial) xenial; urgency=medium

  * disable WireGuard module
  * disable RCU no-callback + expedited grace periods
  * revert all Clear Linux patches
  * merge new 5.1.7 release candidate patches
  * update version to 5.1.0-6.4

 -- Steven Barrett <steven@liquorix.net>  Mon, 03 Jun 2019 18:29:27 -0500

linux-liquorix (5.1-3) unstable; urgency=medium

  * remove problematic Clear Linux patches
   - zero extra registers
   - add scheduler turbo3 patch
  * update version to 5.1.0-6.3 

 -- Steven Barrett <steven@liquorix.net>  Sun, 02 Jun 2019 13:56:56 -0500

linux-liquorix (5.1-2) unstable; urgency=medium

  * merge 5.1.7 release candidate patches
  * merge Clear Linux patches
  * enable WireGuard module
  * enable RCU no-callback + expedited grace periods
  * update version to 5.1.0-6.2

 -- Steven Barrett <steven@liquorix.net>  Sun, 02 Jun 2019 13:17:03 -0500

Just always keep your known working kernel as a backup in case you get a quirky one.

Posted: **Wed Jun 05, 2019 4:04 pm**

Stevo wrote:I'll check to see what's wrong with the package installer, though we are going to switch to the Liquorix repo soon.

My question was meant as a hint to a possible inconsistency somewhere.
Sorry, that you read that as a request for support.
The last thing I want to do is wasting your precious time.

Posted: **Sun Jul 28, 2019 5:01 pm**

The new 5.2-2 Liquorix kernel is headed for the test repo.

Vbox 5.2.32 and 6.0.10 will build on it, along with our latest broadcom-sta and ndiswrapper packages. None of the Nvidia drivers will, except a patched 418.74 driver I just sent up to the test repo along with it. I hope to get the 390 drivers patched as well, and then try the legacy drivers if Debian doesn't beat me to that.

Posted: **Sun Sep 01, 2019 5:09 pm**

Stevo wrote: Sun Jul 28, 2019 5:01 pm The new 5.2-2 Liquorix kernel is headed for the test repo.

Vbox 5.2.32 and 6.0.10 will build on it, along with our latest broadcom-sta and ndiswrapper packages. None of the Nvidia drivers will, except a patched 418.74 driver I just sent up to the test repo along with it. I hope to get the 390 drivers patched as well, and then try the legacy drivers if Debian doesn't beat me to that.

Hello, I know that you are busy with MX 19 but when you have time you can check this.
I think that Debian already do something about it.
I'm especially interested in 340xx, so:

Source Package: nvidia-graphics-drivers-legacy-340xx (340.107-6) [non-free]
https://packages.debian.org/source/sid/ ... gacy-340xx

Package: nvidia-legacy-340xx-kernel-source (340.107-6) [non-free]

This package contains the blobs for building kernel modules for the amd64 architecture. Building the kernel modules has been tested up to Linux 5.2.

Package: nvidia-legacy-340xx-driver (340.107-6) [non-free]

Building the kernel module has been tested up to Linux 5.2.

I hope that this can somehow help to make 340xx build on Liquorix 5.xx

Regard

Posted: **Wed Sep 04, 2019 12:55 pm**

nvidia-legacy-340xx (340.107-6) is now in MX Test Repo, thanks to Stevo I assume.
It build and work well with kernel 5.2.0-10.2-liquorix-amd64 x86_64, latest in MX Test Repo:

Code: Select all

System:    Host: mx Kernel: 5.2.0-10.2-liquorix-amd64 x86_64 bits: 64 compiler: gcc v: 6.3.0 
           Desktop: Xfce 4.12.3 Distro: MX-18.3_x64 Continuum Feb 9  2019 
           base: Debian GNU/Linux 9 (stretch) 
Machine:   Type: Desktop System: FUJITSU SIEMENS product: ESPRIMO P5925 v: N/A serial: <filter> 
           Mobo: FUJITSU SIEMENS model: D2584-A1 v: S26361-D2584-A1 serial: <filter> 
           BIOS: FUJITSU SIEMENS // Phoenix v: 6.00 R1.18.2584.A1 date: 02/05/2009 
CPU:       Topology: Quad Core model: Intel Core2 Quad Q6600 bits: 64 type: MCP arch: Core Merom 
           rev: B L2 cache: 4096 KiB 
           flags: lm nx pae sse sse2 sse3 ssse3 vmx bogomips: 19152 
           Speed: 2051 MHz min/max: 1600/2400 MHz Core speeds (MHz): 1: 1596 2: 1596 3: 1596 
           4: 1596 
Graphics:  Device-1: NVIDIA G84 [GeForce 8600 GTS] vendor: Micro-Star MSI driver: nvidia 
           v: 340.107 bus ID: 01:00.0 
           Display: x11 server: X.Org 1.19.2 driver: nvidia resolution: 1680x1050~60Hz 
           OpenGL: renderer: GeForce 8600 GTS/PCIe/SSE2 v: 3.3.0 NVIDIA 340.107 
           direct render: Yes 
Audio:     Device-1: Intel 82801I HD Audio vendor: Fujitsu Solutions driver: snd_hda_intel 
           v: kernel bus ID: 00:1b.0 
           Sound Server: ALSA v: k5.2.0-10.2-liquorix-amd64 
Network:   Device-1: Intel 82566DM-2 Gigabit Network vendor: Fujitsu Solutions driver: e1000e 
           v: 3.2.6-k port: 1820 bus ID: 00:19.0 
           IF: eth0 state: up speed: 100 Mbps duplex: full mac: <filter> 
Drives:    Local Storage: total: 223.58 GiB used: 60.08 GiB (26.9%) 
           ID-1: /dev/sda vendor: Western Digital model: WD1600AAJS-00PSA0 size: 149.05 GiB 
           ID-2: /dev/sdb vendor: Seagate model: ST380815AS size: 74.53 GiB 
Partition: ID-1: / size: 55.86 GiB used: 19.89 GiB (35.6%) fs: ext4 dev: /dev/sda3 
Sensors:   System Temperatures: cpu: 46.0 C mobo: N/A gpu: nvidia temp: 74 C 
           Fan Speeds (RPM): N/A gpu: nvidia fan: 50% 
Repos:     No active apt repos in: /etc/apt/sources.list 
           Active apt repos in: /etc/apt/sources.list.d/antix.list 
           1: deb http://la.mxrepo.com/antix/stretch/ stretch main
           No active apt repos in: /etc/apt/sources.list.d/brave-browser-release-.list 
           Active apt repos in: /etc/apt/sources.list.d/debian-stable-updates.list 
           1: deb http://ftp.us.debian.org/debian/ stretch-updates non-free contrib main
           Active apt repos in: /etc/apt/sources.list.d/debian.list 
           1: deb http://ftp.us.debian.org/debian/ stretch main contrib non-free
           2: deb http://security.debian.org/ stretch/updates main contrib non-free
           Active apt repos in: /etc/apt/sources.list.d/mx.list 
           1: deb http://mxrepo.com/mx/repo/ stretch main non-free
           Active apt repos in: /etc/apt/sources.list.d/skype-stable.list 
           1: deb [arch=amd64] https://repo.skype.com/deb/ stable main
           No active apt repos in: /etc/apt/sources.list.d/various.list 
Info:      Processes: 187 Uptime: 7m Memory: 7.54 GiB used: 918.4 MiB (11.9%) Init: SysVinit 
           runlevel: 5 Compilers: gcc: 6.3.0 Shell: bash v: 4.4.12 inxi: 3.0.33

Noticed CPU upgrade?

However it won't build with default MX kernel and nothing could help, nor reinstall with 'ddm-mx -i nvidia' from console after booting in blank screen, nor rebuild dkms with '/usr/share/mx-packageinstaller-pkglist/rebuild_dkms_packages.sh' from console either.

Anybody to point me how I can set booting default kernel with nouveau instead nvidia, just in case I need it at any point? Possible?

Posted: **Wed Sep 04, 2019 2:09 pm**

dexy wrote: Wed Sep 04, 2019 12:55 pm nvidia-legacy-340xx (340.107-6) is now in MX Test Repo, thanks to Stevo I assume.
It build and work well with kernel 5.2.0-10.2-liquorix-amd64 x86_64, latest in MX Test Repo:

Code: Select all

System:    Host: mx Kernel: 5.2.0-10.2-liquorix-amd64 x86_64 bits: 64 compiler: gcc v: 6.3.0 
           Desktop: Xfce 4.12.3 Distro: MX-18.3_x64 Continuum Feb 9  2019 
           base: Debian GNU/Linux 9 (stretch) 
Machine:   Type: Desktop System: FUJITSU SIEMENS product: ESPRIMO P5925 v: N/A serial: <filter> 
           Mobo: FUJITSU SIEMENS model: D2584-A1 v: S26361-D2584-A1 serial: <filter> 
           BIOS: FUJITSU SIEMENS // Phoenix v: 6.00 R1.18.2584.A1 date: 02/05/2009 
CPU:       Topology: Quad Core model: Intel Core2 Quad Q6600 bits: 64 type: MCP arch: Core Merom 
           rev: B L2 cache: 4096 KiB 
           flags: lm nx pae sse sse2 sse3 ssse3 vmx bogomips: 19152 
           Speed: 2051 MHz min/max: 1600/2400 MHz Core speeds (MHz): 1: 1596 2: 1596 3: 1596 
           4: 1596 
Graphics:  Device-1: NVIDIA G84 [GeForce 8600 GTS] vendor: Micro-Star MSI driver: nvidia 
           v: 340.107 bus ID: 01:00.0 
           Display: x11 server: X.Org 1.19.2 driver: nvidia resolution: 1680x1050~60Hz 
           OpenGL: renderer: GeForce 8600 GTS/PCIe/SSE2 v: 3.3.0 NVIDIA 340.107 
           direct render: Yes 
Audio:     Device-1: Intel 82801I HD Audio vendor: Fujitsu Solutions driver: snd_hda_intel 
           v: kernel bus ID: 00:1b.0 
           Sound Server: ALSA v: k5.2.0-10.2-liquorix-amd64 
Network:   Device-1: Intel 82566DM-2 Gigabit Network vendor: Fujitsu Solutions driver: e1000e 
           v: 3.2.6-k port: 1820 bus ID: 00:19.0 
           IF: eth0 state: up speed: 100 Mbps duplex: full mac: <filter> 
Drives:    Local Storage: total: 223.58 GiB used: 60.08 GiB (26.9%) 
           ID-1: /dev/sda vendor: Western Digital model: WD1600AAJS-00PSA0 size: 149.05 GiB 
           ID-2: /dev/sdb vendor: Seagate model: ST380815AS size: 74.53 GiB 
Partition: ID-1: / size: 55.86 GiB used: 19.89 GiB (35.6%) fs: ext4 dev: /dev/sda3 
Sensors:   System Temperatures: cpu: 46.0 C mobo: N/A gpu: nvidia temp: 74 C 
           Fan Speeds (RPM): N/A gpu: nvidia fan: 50% 
Repos:     No active apt repos in: /etc/apt/sources.list 
           Active apt repos in: /etc/apt/sources.list.d/antix.list 
           1: deb http://la.mxrepo.com/antix/stretch/ stretch main
           No active apt repos in: /etc/apt/sources.list.d/brave-browser-release-.list 
           Active apt repos in: /etc/apt/sources.list.d/debian-stable-updates.list 
           1: deb http://ftp.us.debian.org/debian/ stretch-updates non-free contrib main
           Active apt repos in: /etc/apt/sources.list.d/debian.list 
           1: deb http://ftp.us.debian.org/debian/ stretch main contrib non-free
           2: deb http://security.debian.org/ stretch/updates main contrib non-free
           Active apt repos in: /etc/apt/sources.list.d/mx.list 
           1: deb http://mxrepo.com/mx/repo/ stretch main non-free
           Active apt repos in: /etc/apt/sources.list.d/skype-stable.list 
           1: deb [arch=amd64] https://repo.skype.com/deb/ stable main
           No active apt repos in: /etc/apt/sources.list.d/various.list 
Info:      Processes: 187 Uptime: 7m Memory: 7.54 GiB used: 918.4 MiB (11.9%) Init: SysVinit 
           runlevel: 5 Compilers: gcc: 6.3.0 Shell: bash v: 4.4.12 inxi: 3.0.33

Noticed CPU upgrade?

However it won't build with default MX kernel and nothing could help, nor reinstall with 'ddm-mx -i nvidia' from console after booting in blank screen, nor rebuild dkms with '/usr/share/mx-packageinstaller-pkglist/rebuild_dkms_packages.sh' from console either.

Anybody to point me how I can set booting default kernel with nouveau instead nvidia, just in case I need it at any point? Possible?

I just went through something similar so I put it in the wiki - mike

Posted: **Wed Sep 04, 2019 5:04 pm**

It looks like their last change didn't fully work

:

Code: Select all

nvidia-graphics-drivers-legacy-340xx (340.107-6) unstable; urgency=medium

  * Add conftest-include-guard.patch to restore compatibility with older
    kernels.

 -- Andreas Beckmann <anbe@debian.org>  Sat, 17 Aug 2019 21:46:00 +0200

nvidia-graphics-drivers-legacy-340xx (340.107-5) unstable; urgency=medium

  * Add buildfix_kernel_4.11.patch (replacing vm-fault.patch),
    buildfix_kernel_5.0.patch, buildfix_kernel_5.2.patch from Ubuntu to fix
    kernel module build for Linux 5.2.  (Closes: #934295, #923815)
  * Bump Standards-Version to 4.4.0. No changes needed.

 -- Andreas Beckmann <anbe@debian.org>  Mon, 12 Aug 2019 12:20:21 +0200

Posted: **Thu Sep 05, 2019 7:36 am**

@mike:
Thanks for advice, but I mean to keep both kernels functional with installed nvidia non-free driver, at this point where this version of nvidia driver build kernel module well for latest liquorix but not for mx stock kernel.
What I mean is to have stock kernel to boot with nouveau and liquorix to boot with nvidia. If it is possible at all?!

@stevo:
So we can wait debian to build new driver version with updated conftest-include-guard.patch or "we" can compile mx driver version with included some better patch :)
I'm just joking, it's not urgent at all. Latest liquorix work just well and this newest nvidia legacy seems to be stable as always. We can wait debian for backward kernel compatibility.

Posted: **Thu Sep 05, 2019 2:43 pm**

I think it's possible to create a script to swap an xorg.conf file for the Nvidia driver in and out, and also to toggle the nouveau driver blacklist at the same time. I'm pretty sure the nouveau driver will handle the graphics automatically without the blacklist and xorg.conf.

Posted: **Fri Sep 06, 2019 1:16 pm**

I think so for nouveau. Very good idea for the script. Just to find out when and how to call script in boot process to check which kernel is loaded and proceed according to that. It could be helpful to have one kernel as safety boot when similar problems arrive that can boot in DE.
I will investigate this further and maybe start new thread about it because it's beyond just liquorix kernel for which is this thread.

Thanks Stevo

Posted: **Fri Sep 06, 2019 2:52 pm**

You could have the script grep the output of "uname -r" for "liquorix", and then proceed depending on what it finds.

Posted: **Tue Oct 29, 2019 3:09 pm**

We now have the latest Liquorix 5.3-1 kernel in the test repo, based on the vanilla kernel 5.3.7 release. All 5.2 releases except for the last one have been removed from the repo.

If you are using out-of-tree DKMS drivers, such as Nvidia, broadcom-sta-dkms, virtualbox 5.2.X or 6.X, and so on, you should upgrade to the test repo (or experimental for Vbox 5.2.X) versions first, then install the latest kernel.

Posted: **Sun Dec 15, 2019 1:16 am**

Is there any chance of getting a 4.14 kernel back? It is an LTS kernel with an EOL years after even the 5.4 kernels, and a year later than the 4.9 kernel which is still available.

https://www.kernel.org/category/releases.html

Longterm release kernels
Version Maintainer Released Projected EOL
5.4 Greg Kroah-Hartman & Sasha Levin 2019-11-24 Dec, 2021
4.19 Greg Kroah-Hartman & Sasha Levin 2018-10-22 Dec, 2020
4.14 Greg Kroah-Hartman & Sasha Levin 2017-11-12 Jan, 2024
4.9 Greg Kroah-Hartman & Sasha Levin 2016-12-11 Jan, 2023
4.4 Greg Kroah-Hartman & Sasha Levin 2016-01-10 Feb, 2022
3.16 Ben Hutchings 2014-08-03 Jun, 2020

Posted: **Tue Feb 04, 2020 4:51 pm**

The Liquorix kernels don't incorporate any LTS patches at all--they are more for those that live at the leading edge.

We now have Liquorix 5.5 in the test repo. If you're using Virtual Box or Nvidia drivers, you must upgrade to the test repo versions of those first before the 5.5 kernel update, otherwise the DKMS driver builds will fail, along with the kernel installation.

Though almost nobody is using ndiswrapper, we just pushed an update into main that allows it to build on the 5.5 kernel, too. Broadcom-sta drivers in main were already compatible.

Posted: **Fri Feb 21, 2020 2:38 pm**

Just updated last night to 5.5-8 (5.5.0-5.1)...or apparently we tried, but the upload failed.

It should be fixed very shortly, though.

Posted: **Tue Apr 07, 2020 11:43 pm**

Now updated to 5.5-19 (kernel base release 5.5.15). The backported Wireguard VPN support from 5.6 has been restored.

Posted: **Mon Apr 27, 2020 11:56 pm**

We now have the last 5.5-23 Liquorix kernel in the test repo, as well as the first 5.6-1 release, which is based on the 5.6.8 vanilla kernel.

Users of the following drivers should update before installing the new 5.6 kernel:

Virtualbox 6.1.16 in our test repo is known to build and work with it, as well as the nvidia-driver 440.82 in the test repo. The legacy 390xx and 340xx drivers in the TR also have patches for it, but need testing.

You may have to update broadcom-sta-dkms from the test repo if you need that wi-fi driver, otherwise, you should uninstall it, along with ndiswrapper-dkms, to save time on updates--why build them if you don't use them?

A patched version of bbswitch-dkms for those that use Bumblebee with Optimus laptops has also been updated in main to build with 5.6 kernels.

MX Linux Forum

MX 17/18 Repository: The Liquorix Kernel Thread

MX 17/18 Repository: The Liquorix Kernel Thread

Re: MX 17 Repository: The Liquorix Kernel Thread

Re: MX 17 Repository: The Liquorix Kernel Thread

Re: MX 17 Repository: The Liquorix Kernel Thread

Re: MX 17 Repository: The Liquorix Kernel Thread

Re: MX 17 Repository: The Liquorix Kernel Thread

Re: MX 17 Repository: The Liquorix Kernel Thread

Re: MX 17 Repository: The Liquorix Kernel Thread

Re: MX 17 Repository: The Liquorix Kernel Thread

Re: MX 17 Repository: The Liquorix Kernel Thread

Re: MX 17 Repository: The Liquorix Kernel Thread

Re: MX 17 Repository: The Liquorix Kernel Thread

Re: MX 17 Repository: The Liquorix Kernel Thread

Re: MX 17 Repository: The Liquorix Kernel Thread

Re: MX 17 Repository: The Liquorix Kernel Thread

Re: MX 17 Repository: The Liquorix Kernel Thread

Re: MX 17 Repository: The Liquorix Kernel Thread

Re: MX 17 Repository: The Liquorix Kernel Thread

Re: MX 17 Repository: The Liquorix Kernel Thread

Re: MX 17 Repository: The Liquorix Kernel Thread

Re: MX 17 Repository: The Liquorix Kernel Thread

Re: MX 17 Repository: The Liquorix Kernel Thread

Re: MX 17 Repository: The Liquorix Kernel Thread

Re: MX 17 Repository: The Liquorix Kernel Thread

Re: MX 17 Repository: The Liquorix Kernel Thread

Re: MX 17 Repository: The Liquorix Kernel Thread

Re: MX 17 Repository: The Liquorix Kernel Thread

Re: MX 17 Repository: The Liquorix Kernel Thread

Re: MX 17 Repository: The Liquorix Kernel Thread

Re: MX 17 Repository: The Liquorix Kernel Thread

Re: MX 17 Repository: The Liquorix Kernel Thread

Re: MX 17 Repository: The Liquorix Kernel Thread

Re: MX 17 Repository: The Liquorix Kernel Thread

Re: MX 17 Repository: The Liquorix Kernel Thread

Re: MX 17 Repository: The Liquorix Kernel Thread

Re: MX 17 Repository: The Liquorix Kernel Thread

Re: MX 17 Repository: The Liquorix Kernel Thread

Re: MX 17 Repository: The Liquorix Kernel Thread

Re: MX 17 Repository: The Liquorix Kernel Thread

Re: MX 17 Repository: The Liquorix Kernel Thread

Re: MX 17 Repository: The Liquorix Kernel Thread

Re: MX 17 Repository: The Liquorix Kernel Thread

Re: MX 17 Repository: The Liquorix Kernel Thread

Re: MX 17 Repository: The Liquorix Kernel Thread

Re: MX 17 Repository: The Liquorix Kernel Thread

Re: MX 17 Repository: The Liquorix Kernel Thread

Re: MX 17 Repository: The Liquorix Kernel Thread

Re: MX 17 Repository: The Liquorix Kernel Thread

Re: MX 17 Repository: The Liquorix Kernel Thread

Re: MX 17 Repository: The Liquorix Kernel Thread

Re: MX 17 Repository: The Liquorix Kernel Thread

Re: MX 17 Repository: The Liquorix Kernel Thread

Re: MX 17 Repository: The Liquorix Kernel Thread

Re: MX 17 Repository: The Liquorix Kernel Thread

Re: MX 17 Repository: The Liquorix Kernel Thread

Re: MX 17 Repository: The Liquorix Kernel Thread

Re: MX 17 Repository: The Liquorix Kernel Thread

Re: MX 17 Repository: The Liquorix Kernel Thread

Re: MX 17 Repository: The Liquorix Kernel Thread

Re: MX 17 Repository: The Liquorix Kernel Thread

Re: MX 17 Repository: The Liquorix Kernel Thread

Re: MX 17 Repository: The Liquorix Kernel Thread

Re: MX 17 Repository: The Liquorix Kernel Thread

Re: MX 17 Repository: The Liquorix Kernel Thread

Re: MX 17 Repository: The Liquorix Kernel Thread

Re: MX 17 Repository: The Liquorix Kernel Thread

Re: MX 17 Repository: The Liquorix Kernel Thread

Re: MX 17 Repository: The Liquorix Kernel Thread

Re: MX 17 Repository: The Liquorix Kernel Thread

Baytrail-kernel Re: MX 17 Repository: The Liquorix Kernel Thread

Re: MX 17 Repository: The Liquorix Kernel Thread

Re: Baytrail-kernel Re: MX 17 Repository: The Liquorix Kernel Thread

Re: Baytrail-kernel Re: MX 17 Repository: The Liquorix Kernel Thread

Re: MX 17 Repository: The Liquorix Kernel Thread

Re: Baytrail-kernel Re: MX 17 Repository: The Liquorix Kernel Thread

Re: MX 17 Repository: The Liquorix Kernel Thread

Re: MX 17 Repository: The Liquorix Kernel Thread

Re: MX 17 Repository: The Liquorix Kernel Thread