Welcome!

The kernel problem with recent updates has been solved. Find the solution here

Important information
-- Required MX 15/16 Repository Changes
-- Information on torrent hosting changes
-- Information on MX15/16 GPG Keys
-- Spectre and Meltdown vulnerabilities

News
-- Introducing our new Website
-- MX Linux on social media: here

Current releases
-- MX-18.3 Point Release release info here
-- Migration Information to MX-18 here
-- antiX-17.4.1 release info here

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

MX 17/18 Repository: The Liquorix Kernel Thread

User avatar
Stevo
Developer
Posts: 20096
Joined: Fri Dec 15, 2006 8:07 pm

Re: MX 17/18 Repository: The Liquorix Kernel Thread

#151

Post by Stevo » 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.

Friedrich
Forum Novice
Forum  Novice
Posts: 96
Joined: Sun Dec 23, 2018 2:50 am

Re: MX 17/18 Repository: The Liquorix Kernel Thread

#152

Post by Friedrich » 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.

User avatar
Stevo
Developer
Posts: 20096
Joined: Fri Dec 15, 2006 8:07 pm

Re: MX 17/18 Repository: The Liquorix Kernel Thread

#153

Post by Stevo » 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.

User avatar
dexy
Forum Novice
Forum  Novice
Posts: 10
Joined: Wed Dec 26, 2018 3:04 am

Re: MX 17/18 Repository: The Liquorix Kernel Thread

#154

Post by dexy » 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
Be aware that they don't want You to be aware!

User avatar
dexy
Forum Novice
Forum  Novice
Posts: 10
Joined: Wed Dec 26, 2018 3:04 am

Re: MX 17/18 Repository: The Liquorix Kernel Thread

#155

Post by dexy » 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? :happy:

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?
Be aware that they don't want You to be aware!

User avatar
mmikeinsantarosa
Developer
Posts: 2989
Joined: Thu May 01, 2014 10:12 am

Re: MX 17/18 Repository: The Liquorix Kernel Thread

#156

Post by mmikeinsantarosa » 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? :happy:

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
LT: MX18.2 Quad Core model: Intel Core i7-6820HQ Kernel: 5.0.0-7.1-liquorix-amd64 x86_64

User avatar
Stevo
Developer
Posts: 20096
Joined: Fri Dec 15, 2006 8:07 pm

Re: MX 17/18 Repository: The Liquorix Kernel Thread

#157

Post by Stevo » Wed Sep 04, 2019 5:04 pm

It looks like their last change didn't fully work :frown: :frown: :

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

User avatar
dexy
Forum Novice
Forum  Novice
Posts: 10
Joined: Wed Dec 26, 2018 3:04 am

Re: MX 17/18 Repository: The Liquorix Kernel Thread

#158

Post by dexy » 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.
Be aware that they don't want You to be aware!

User avatar
Stevo
Developer
Posts: 20096
Joined: Fri Dec 15, 2006 8:07 pm

Re: MX 17/18 Repository: The Liquorix Kernel Thread

#159

Post by Stevo » 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.

User avatar
dexy
Forum Novice
Forum  Novice
Posts: 10
Joined: Wed Dec 26, 2018 3:04 am

Re: MX 17/18 Repository: The Liquorix Kernel Thread

#160

Post by dexy » 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
Be aware that they don't want You to be aware!

Post Reply

Return to “Package Requests/Status - MX 17/18”