Page 1 of 1
MX 19 Repository: The Liquorix Kernel Thread
Posted: Tue Oct 29, 2019 3:12 pm
by Stevo
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. These kernels are available only for 64-bit users.
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.
Re: MX 19 Repository: The Liquorix Kernel Thread
Posted: Fri Nov 01, 2019 1:08 pm
by imschmeg
My MX19 installer failed installing the 5.3.0-7.1-liquorix-amd64 kernel. This happened in a vbox (6.0.14) VM.
Got a pop-up window that says "Problem detected while installing, plese inpect the conole output." The console ouptut is:
Code: Select all
Hit:1 http://deb.debian.org/debian-security buster/updates InRelease
Hit:2 http://debian.csail.mit.edu/debian buster-updates InRelease
Hit:3 http://debian.csail.mit.edu/debian buster InRelease
Hit:4 http://mxlinux.csail.mit.edu/mxlinux/antix//buster buster InRelease
Hit:5 http://mxlinux.csail.mit.edu/mxlinux/mx/repo buster InRelease
Reading package lists...
Hit:1 http://debian.csail.mit.edu/debian buster-updates InRelease
Hit:2 http://debian.csail.mit.edu/debian buster InRelease
Hit:3 http://mxlinux.csail.mit.edu/mxlinux/antix//buster buster InRelease
Hit:4 http://mxlinux.csail.mit.edu/mxlinux/mx/repo buster InRelease
Hit:5 http://deb.debian.org/debian-security buster/updates InRelease
Get:6 http://mxrepo.com/mx/testrepo buster InRelease [4,963 B]
Get:7 http://mxrepo.com/mx/testrepo buster/test i386 Packages [230 kB]
Get:8 http://mxrepo.com/mx/testrepo buster/test amd64 Packages [233 kB]
Fetched 469 kB in 2s (234 kB/s)
Reading package lists...
Reading package lists...
Building dependency tree...
Reading state information...
The following additional packages will be installed:
linux-headers-5.3.0-7.1-liquorix-amd64 linux-image-5.3.0-7.1-liquorix-amd64
Suggested packages:
linux-doc-5.3 crda
The following NEW packages will be installed:
linux-headers-5.3.0-7.1-liquorix-amd64 linux-headers-liquorix-amd64
linux-image-5.3.0-7.1-liquorix-amd64 linux-image-liquorix-amd64
0 upgraded, 4 newly installed, 2 reinstalled, 0 to remove and 0 not upgraded.
Need to get 69.7 MB of archives.
After this operation, 367 MB of additional disk space will be used.
Do you want to continue? [Y/n]
Get:1 http://mxlinux.csail.mit.edu/mxlinux/mx/repo buster/non-free amd64 broadcom-sta-dkms all 6.30.223.271-10mx19+1 [2,207 kB]
Get:2 http://mxrepo.com/mx/testrepo buster/test amd64 linux-image-5.3.0-7.1-liquorix-amd64 amd64 5.3-1~mx19+1 [58.1 MB]
Get:3 http://mxlinux.csail.mit.edu/mxlinux/mx/repo buster/main amd64 ndiswrapper-dkms all 1.61-0.1~mx19+4 [157 kB]
Get:4 http://mxrepo.com/mx/testrepo buster/test amd64 linux-headers-5.3.0-7.1-liquorix-amd64 amd64 5.3-1~mx19+1 [8,891 kB]
Get:5 http://mxrepo.com/mx/testrepo buster/test amd64 linux-headers-liquorix-amd64 amd64 5.3-1~mx19+1 [154 kB]
Get:6 http://mxrepo.com/mx/testrepo buster/test amd64 linux-image-liquorix-amd64 amd64 5.3-1~mx19+1 [154 kB]
Preconfiguring packages ...
Fetched 69.7 MB in 23s (3,035 kB/s)
Selecting previously unselected package linux-image-5.3.0-7.1-liquorix-amd64.
(Reading database ... 366501 files and directories currently installed.)
Preparing to unpack .../0-linux-image-5.3.0-7.1-liquorix-amd64_5.3-1~mx19+1_amd64.deb ...
Unpacking linux-image-5.3.0-7.1-liquorix-amd64 (5.3-1~mx19+1) ...
Preparing to unpack .../1-broadcom-sta-dkms_6.30.223.271-10mx19+1_all.deb ...
-------- Uninstall Beginning --------
Module: broadcom-sta
Version: 6.30.223.271
Kernel: 4.19.0-6-amd64 (x86_64)
-------------------------------------
Status: Before uninstall, this module version was ACTIVE on this kernel.
wl.ko:
- Uninstallation
- Deleting from: /lib/modules/4.19.0-6-amd64/updates/dkms/
rmdir: failed to remove directory 'updates': Directory not empty
- Original module
- No original module was found for this module on this kernel.
- Use the dkms install command to reinstall any previous module version.
depmod........
update-initramfs..................
DKMS: uninstall completed.
------------------------------
Deleting module version: 6.30.223.271
completely from the DKMS tree.
------------------------------
Done.
Unpacking broadcom-sta-dkms (6.30.223.271-10mx19+1) over (6.30.223.271-10mx19+1) ...
Selecting previously unselected package linux-headers-5.3.0-7.1-liquorix-amd64.
Preparing to unpack .../2-linux-headers-5.3.0-7.1-liquorix-amd64_5.3-1~mx19+1_amd64.deb ...
Unpacking linux-headers-5.3.0-7.1-liquorix-amd64 (5.3-1~mx19+1) ...
Preparing to unpack .../3-ndiswrapper-dkms_1.61-0.1~mx19+4_all.deb ...
-------- Uninstall Beginning --------
Module: ndiswrapper
Version: 1.61
Kernel: 4.19.0-6-amd64 (x86_64)
-------------------------------------
Status: Before uninstall, this module version was ACTIVE on this kernel.
ndiswrapper.ko:
- Uninstallation
- Deleting from: /lib/modules/4.19.0-6-amd64/updates/
rmdir: failed to remove 'updates': Directory not empty
- Original module
- No original module was found for this module on this kernel.
- Use the dkms install command to reinstall any previous module version.
depmod...
DKMS: uninstall completed.
------------------------------
Deleting module version: 1.61
completely from the DKMS tree.
------------------------------
Done.
Unpacking ndiswrapper-dkms (1.61-0.1~mx19+4) over (1.61-0.1~mx19+4) ...
Selecting previously unselected package linux-headers-liquorix-amd64.
Preparing to unpack .../4-linux-headers-liquorix-amd64_5.3-1~mx19+1_amd64.deb ...
Unpacking linux-headers-liquorix-amd64 (5.3-1~mx19+1) ...
Selecting previously unselected package linux-image-liquorix-amd64.
Preparing to unpack .../5-linux-image-liquorix-amd64_5.3-1~mx19+1_amd64.deb ...
Unpacking linux-image-liquorix-amd64 (5.3-1~mx19+1) ...
Setting up ndiswrapper-dkms (1.61-0.1~mx19+4) ...
Loading new ndiswrapper-1.61 DKMS files...
Building for 4.19.0-6-amd64 5.3.0-7.1-liquorix-amd64
Building initial module for 4.19.0-6-amd64
Done.
ndiswrapper.ko:
Running module version sanity check.
- Original module
- No original module exists within this kernel
- Installation
- Installing to /lib/modules/4.19.0-6-amd64/updates/
depmod...
System has not been booted with systemd as init system (PID 1). Can't operate.
DKMS: install completed.
Failed to connect to bus: Host is down
Building initial module for 5.3.0-7.1-liquorix-amd64
Error! Bad return status for module build on kernel: 5.3.0-7.1-liquorix-amd64 (x86_64)
Consult /var/lib/dkms/ndiswrapper/1.61/build/make.log for more information.
Setting up broadcom-sta-dkms (6.30.223.271-10mx19+1) ...
dpkg: error processing package ndiswrapper-dkms (--configure):
installed ndiswrapper-dkms package post-installation script subprocess returned error exit status 10
Loading new broadcom-sta-6.30.223.271 DKMS files...
Building for 4.19.0-6-amd64 5.3.0-7.1-liquorix-amd64
Building initial module for 4.19.0-6-amd64
Done.
wl.ko:
Running module version sanity check.
- Original module
- No original module exists within this kernel
- Installation
- Installing to /lib/modules/4.19.0-6-amd64/updates/dkms/
depmod...
System has not been booted with systemd as init system (PID 1). Can't operate.
Failed to connect to bus: Host is down
Backing up initrd.img-4.19.0-6-amd64 to /boot/initrd.img-4.19.0-6-amd64.old-dkms
Making new initrd.img-4.19.0-6-amd64
(If next boot fails, revert to initrd.img-4.19.0-6-amd64.old-dkms image)
update-initramfs..........
DKMS: install completed.
Building initial module for 5.3.0-7.1-liquorix-amd64
Done.
wl.ko:
Running module version sanity check.
- Original module
- No original module exists within this kernel
- Installation
- Installing to /lib/modules/5.3.0-7.1-liquorix-amd64/updates/dkms/
depmod...
System has not been booted with systemd as init system (PID 1). Can't operate.
Failed to connect to bus: Host is down
Warning: Unable to find an initial ram disk that I know how to handle.
Will not try to make an initrd.
DKMS: install completed.
Setting up linux-headers-5.3.0-7.1-liquorix-amd64 (5.3-1~mx19+1) ...
Examining /etc/kernel/header_postinst.d.
run-parts: executing /etc/kernel/header_postinst.d/dkms 5.3.0-7.1-liquorix-amd64
Error! Bad return status for module build on kernel: 5.3.0-7.1-liquorix-amd64 (x86_64)
Consult /var/lib/dkms/ndiswrapper/1.61/build/make.log for more information.
System has not been booted with systemd as init system (PID 1). Can't operate.
Failed to connect to bus: Host is down
Setting up linux-image-5.3.0-7.1-liquorix-amd64 (5.3-1~mx19+1) ...
/etc/kernel/postinst.d/dkms:
Error! Bad return status for module build on kernel: 5.3.0-7.1-liquorix-amd64 (x86_64)
Consult /var/lib/dkms/ndiswrapper/1.61/build/make.log for more information.
/etc/kernel/postinst.d/initramfs-tools:
update-initramfs: Generating /boot/initrd.img-5.3.0-7.1-liquorix-amd64
cryptsetup: WARNING: The initramfs image may not contain cryptsetup binaries
nor crypto modules. If that's on purpose, you may want to uninstall the
'cryptsetup-initramfs' package in order to disable the cryptsetup initramfs
integration and avoid this warning.
I: The initramfs will attempt to resume from /dev/sda2
I: (UUID=c3286ac4-7525-402d-88f6-5eb20bf1beea)
I: Set the RESUME variable to override this.
/etc/kernel/postinst.d/zz-update-grub:
Generating grub configuration file ...
Found theme: /boot/grub/themes/linen/theme.txt
Found linux image: /boot/vmlinuz-5.3.0-7.1-liquorix-amd64
Found initrd image: /boot/initrd.img-5.3.0-7.1-liquorix-amd64
Found linux image: /boot/vmlinuz-4.19.0-6-amd64
Found initrd image: /boot/initrd.img-4.19.0-6-amd64
Found memtest86+ image: /boot/memtest86+.bin
done
Setting up linux-image-liquorix-amd64 (5.3-1~mx19+1) ...
Setting up linux-headers-liquorix-amd64 (5.3-1~mx19+1) ...
Errors were encountered while processing:
ndiswrapper-dkms
E: Sub-process /usr/bin/dpkg returned an error code (1)
/usr/bin/rebuild_dkms_packages.sh: line 11: dpkg-reconfigure: command not found
/usr/bin/rebuild_dkms_packages.sh: line 11: dpkg-reconfigure: command not found
/usr/bin/rebuild_dkms_packages.sh: line 11: dpkg-reconfigure: command not found
Reading package lists...
Building dependency tree...
Reading state information...
The following packages will be REMOVED:
linux-headers-liquorix-amd64 linux-image-liquorix-amd64
0 upgraded, 0 newly installed, 2 to remove and 0 not upgraded.
1 not fully installed or removed.
After this operation, 322 kB disk space will be freed.(Reading database ... (Reading database ... 5%
(Reading database ... 10%
(Reading database ... 15%(Reading database ... 20%
(Reading database ... 25%
(Reading database ... 30%
(Reading database ... 35%
(Reading database ... 40%
(Reading database ... 45%
(Reading database ... 50%(Reading database ... 55%(Reading database ... 60%(Reading database ... 65%(Reading database ... 70%(Reading database ... 75%(Reading database ... 80%(Reading database ... 85%(Reading database ... 90%(Reading database ... 95%(Reading database ... 100%Removing linux-headers-liquorix-amd64 (5.3-1~mx19+1) ...Removing linux-image-liquorix-amd64 (5.3-1~mx19+1) ...Setting up ndiswrapper-dkms (1.61-0.1~mx19+4) ...
Module: ndiswrapper
Version: 1.61
Kernel: 4.19.0-6-amd64 (x86_64)
-------------------------------------Status: Before uninstall, this module version was ACTIVE on this kernel.
ndiswrapper.ko:
- Uninstallation
- Deleting from: /lib/modules/4.19.0-6-amd64/updates/failed to remove 'updates': Directory not empty - Original module
- No original module was found for this module on this kernel.
- Use the dkms install command to reinstall any previous module version.
DKMS: uninstall completed.
------------------------------
Deleting module version: 1.61
completely from the DKMS tree.
------------------------------Done.Loading new ndiswrapper-1.61 DKMS files...Building for 4.19.0-6-amd64 5.3.0-7.1-liquorix-amd64Building initial module for 4.19.0-6-amd64Done.
ndiswrapper.ko:Running module version sanity check. - Original module - No original module exists within this kernel
- Installation - Installing to /lib/modules/4.19.0-6-amd64/updates/Failed to connect to bus: Host is down
DKMS: install completed.Building initial module for 5.3.0-7.1-liquorix-amd64dpkg: error processing package ndiswrapper-dkms (--configure):
installed ndiswrapper-dkms package post-installation script subprocess returned error exit status 10Errors were encountered while processing: ndiswrapper-dkms
E: Sub-process /usr/bin/dpkg returned an error code (1)
Hit:1 http://deb.debian.org/debian-security buster/updates InRelease
Hit:2 http://mxlinux.csail.mit.edu/mxlinux/antix//buster buster InRelease
Hit:3 http://debian.csail.mit.edu/debian buster-updates InRelease
Hit:4 http://mxlinux.csail.mit.edu/mxlinux/mx/repo buster InRelease
Hit:5 http://debian.csail.mit.edu/debian buster InRelease
Reading package lists...
Re: MX 19 Repository: The Liquorix Kernel Thread
Posted: Fri Nov 01, 2019 1:42 pm
by Jerry3904
Do you mean the systemd messages? I believe those are merely informational; can you boot into the new kernel?
Re: MX 19 Repository: The Liquorix Kernel Thread
Posted: Fri Nov 01, 2019 2:18 pm
by oops
Stevo wrote: Tue Oct 29, 2019 3:12 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. These kernels are available only for 64-bit users.
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.
Thx ... Kernel 5.3.0-7.1-liquorix-amd64 works great here. (5.3-1 not yet into the repository)
Code: Select all
cat /proc/cmdline
audit=0 BOOT_IMAGE=/boot/vmlinuz-5.3.0-7.1-liquorix-amd64 root=UUID= ... quiet
Re: MX 19 Repository: The Liquorix Kernel Thread
Posted: Fri Nov 01, 2019 4:59 pm
by imschmeg
The non-systemd new liquorix kernel booted OK. But the systemd one failed to boot the first time with at least severe video problems. I tried to attach a screen shot, but even at just 423K, the attachments adder is saying it's too big. However, the new kernel did reboot OK with systemd or without after that first failure.
So, false alarm?
Re: MX 19 Repository: The Liquorix Kernel Thread
Posted: Fri Nov 01, 2019 6:03 pm
by Stevo
Ahem. I repeat:
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.
The stock ndiswrapper-dkms which had the build failures falls into that category, but If you're not using it--very, very people are--you can remove instead of upgrading it to speed up the kernel install. The same goes for broadcom-sta-dkms: if you don't have a Broadcom wi-fi device, you don't need that package!
If you don't know what dkms drivers you have installed, just hit the Status/Installed tabs in Synaptic, then do a Quick Search for "dkms".
Re: MX 19 Repository: The Liquorix Kernel Thread
Posted: Fri Nov 01, 2019 11:05 pm
by imschmeg
Sorry! Well, that's what the VM is for - make all my mistakes there...
Re: MX 19 Repository: The Liquorix Kernel Thread
Posted: Fri Nov 01, 2019 11:15 pm
by Stevo
Ah! The MX virtualbox-guest packages in the guest also need to be updated to 6.0.14 from the test repo to handle the latest kernel, then.
Re: MX 19 Repository: The Liquorix Kernel Thread
Posted: Mon Nov 04, 2019 6:25 am
by oops
Stevo wrote: Tue Oct 29, 2019 3:12 pm
... kernels are available only for 64-bit users.
... Why only for 64-bit and not 32-bit , it's a choice of the liquorix kernel dev. ?
Re: MX 19 Repository: The Liquorix Kernel Thread
Posted: Wed Nov 06, 2019 3:47 pm
by cinclus
Re: MX 19 Repository: The Liquorix Kernel Thread
Posted: Wed Nov 06, 2019 5:50 pm
by manyroads
I am happy to note that this is the first Liquorix kernel to function on my Dell Latitude E5470. I am running the following wms/DE bspwm, hlwm, and xfce4.14 if that makes a difference.
Re: MX 19 Repository: The Liquorix Kernel Thread
Posted: Wed Nov 06, 2019 6:34 pm
by oops
Thanks for the information Cinclus.
Re: MX 19 Repository: The Liquorix Kernel Thread
Posted: Tue Feb 04, 2020 4:54 pm
by Stevo
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.
Re: MX 19 Repository: The Liquorix Kernel Thread
Posted: Mon Feb 10, 2020 10:03 pm
by jdhedden
I found a problem with Liquorix 5.5 in that Ctrl-Alt-F1 brings up a non-working console (blank screen except for a non-responsive blinking underscore cursor). If I boot into Liquorix 5.3, then Ctrl-Alt-F1 does get me to a working console.
Re: MX 19 Repository: The Liquorix Kernel Thread
Posted: Mon Feb 10, 2020 10:10 pm
by jdhedden
What is different between the 'buster' version of Liquorix kernels found on
https://liquorix.net/debian/pool/main/l/linux-liquorix/, and the 'mx19-1' versions found in AHS?
Re: MX 19 Repository: The Liquorix Kernel Thread
Posted: Mon Feb 10, 2020 10:21 pm
by jdhedden
I noted something else different between 5.3. and 5.5. I run 4 "threads" of mersenne prime search. On 5.3, my conky shows 50% cpu usage (top shows 400%). On 5.5, conky show 25% (top still shows 400%). Any clue why?
I have a Ryzen 7 cpu. inxi states it has 8 cores, but /proc/cpuinfo show 16 processors. Again, why?
It's all inconsistent. The mersenne prime search is definitely max'ing out 4 of something (core or processor) hence the 400% on top. So is this 50% of 8 cores under 5.3, and 25% of 16 processors under 5.5?
Re: MX 19 Repository: The Liquorix Kernel Thread
Posted: Mon Feb 10, 2020 10:55 pm
by Stevo
The MX kernels in the MX test repos (not ahs) are essentially the same as the ones from the Liquorix repo--we just don't update them quite as often. They don't take that long to build on my 6-core gaming laptop, either.
I noticed that some reporting apps seemed to show too much work being done on 5.4, such as showing most of the capacity being used when I specified only half of my available threads be used on a build, but seem more accurate on 5.5. S-tui from our test repos seems accurate for either kernel series, at least for me, and allows you to stress your machine up to 100% at will.
That may be due to scheduler and other tweaks that are continuously being done in that kernel, but you'd have to ask about that on the Liquorix forums.
Re: MX 19 Repository: The Liquorix Kernel Thread
Posted: Mon Feb 10, 2020 11:17 pm
by Stevo
I have a Ryzen 7 cpu. inxi states it has 8 cores, but /proc/cpuinfo show 16 processors. Again, why?
Inxi may need to be updated for the Ryzen 7. Report that as a bug if it happens on other kernels. Or it may be reporting it correctly, and you have two threads of execution for each core, each of which is being seen as a processor, like for my laptop:
CPU: Topology: 6-Core model: Intel Core i7-8750H bits: 64 type: MT MCP L2 cache: 9216 KiB
Speed: 800 MHz min/max: 800/4100 MHz Core speeds (MHz): 1: 800 2: 800 3: 800 4: 800 5: 800 6: 800 7: 800 8: 800
9: 800 10: 800 11: 800 12: 800
That actually seems more likely to be the case...
Re: MX 19 Repository: The Liquorix Kernel Thread
Posted: Tue Feb 11, 2020 2:18 am
by KoO
jdhedden wrote: Mon Feb 10, 2020 10:21 pm
I have a Ryzen 7 cpu. inxi states it has 8 cores, but /proc/cpuinfo show 16 processors. Again, why?
Thats because a Ryzen 7 cpu has 8 cores and 16 threads. Maybe inxi only looks at the 8 main cores and cat /proc/cpuinfo looks at all the cores.
This is where Liquorix stores its kernels for Debian after being checked by the Debian team.
And mx19.1 AHS version have been made compatible to run on mx19 and may have been changed in some way by the mx team.
I have found that Liquorix kernels on my system tend to use a bit more cpu percentage anyway.
Re: MX 19 Repository: The Liquorix Kernel Thread
Posted: Tue Feb 11, 2020 3:25 pm
by Stevo
This is where Liquorix stores its kernels for Debian after being checked by the Debian team.
I'm pretty sure that there's no "Debian team" involved at all with Liquorix--just Steve Damentz.
I generally don't change anything at all for our Liquorix rebuilds except the version and the name of the maintainer.
Re: MX 19 Repository: The Liquorix Kernel Thread
Posted: Wed Feb 12, 2020 11:15 am
by jdhedden
jdhedden wrote: Mon Feb 10, 2020 10:03 pm
I found a problem with Liquorix 5.5 in that Ctrl-Alt-F1 brings up a non-working console (blank screen except for a non-responsive blinking underscore cursor). If I boot into Liquorix 5.3, then Ctrl-Alt-F1 does get me to a working console.
Can anyone else confirm working/non-working console under Liquorix 5.5?
Re: MX 19 Repository: The Liquorix Kernel Thread
Posted: Thu Feb 13, 2020 7:28 pm
by Stevo
I also get a black screen with Ctl-Alt-F1, but F2 through F6 still work, and F1 then worked after I tested all of those. Can you see if you get the same result?
I guess I installed some screen reader when testing something else, because I got a surprise when a robotic voice came out of the speakers when I switched to a console login: "WELCOME TO MX LINUX POWERED BY DEBIAN PREPARE TO DIE PUNY FLESHBAG !" (OK, I may have embellished the last part a bit, but that's what I expected it to finish with)
Re: MX 19 Repository: The Liquorix Kernel Thread
Posted: Fri Feb 21, 2020 2:37 pm
by Stevo
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.
Re: MX 19 Repository: The Liquorix Kernel Thread
Posted: Thu Mar 05, 2020 8:47 pm
by KoO
Hey Stevo
Would it be possible to remove on bootup the ACPI and Watchdog SP5100 Errors from the Liquorix kernel Please..?
I have B450-I and running at the moment Linux mx19 5.5.0-7.1-liquorix-amd64 #1 ZEN SMP PREEMPT liquorix 5.5-10~mx19+1 (2020-03-02) x86_64 GNU/Linux, but it happens with all Liquorix kernels and not the 5.4 MX kernel. Or even if I can turn off the errors at boot would be Ok.?
Re: MX 19 Repository: The Liquorix Kernel Thread
Posted: Thu Mar 05, 2020 11:58 pm
by Stevo
They don't add the boot warnings to the kernel by design, so I can't just flip a config switch to remove them.
My understanding is that those might be due to specific problems with your BIOS, and sometimes those can be reduced with a BIOS update or a boot flag, but perhaps Googling the error string would come up with some solution, or even asking on the Liquorix forum. Most of those warnings turn out to be harmless, though.
Re: MX 19 Repository: The Liquorix Kernel Thread
Posted: Fri Mar 06, 2020 4:29 am
by KoO
Thanks for the update Stevo
They are harmless. No it is not my bios it is the latest version it happens of every computer I have ever installed the liquorix kernel on. As I use goduckgo all of the time,I now have tried google and their is a lot more info. Their is away off turning off the errors at bootup I just need to found it and do more research.
Thanks Again
Re: MX 19 Repository: The Liquorix Kernel Thread
Posted: Fri Mar 06, 2020 5:44 am
by JayM
I've gotten ACPI "errors" on every computer I've ever owned when booting every Linux distro I've used: Ubuntu, PCLinuxOS, Mint and MX, no matter what kernel. They can be safely ignored.
Re: MX 19 Repository: The Liquorix Kernel Thread
Posted: Fri Mar 06, 2020 6:32 am
by KoO
Thanks JayM
Re: MX 19 Repository: The Liquorix Kernel Thread
Posted: Tue Apr 07, 2020 11:42 pm
by Stevo
Now updated to 5.5-19 (kernel base release 5.5.15). The backported Wireguard VPN support from 5.6 has been restored.
Re: MX 19 Repository: The Liquorix Kernel Thread
Posted: Mon Apr 27, 2020 11:53 pm
by Stevo
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.
Re: MX 19 Repository: The Liquorix Kernel Thread
Posted: Tue Apr 28, 2020 12:49 am
by imschmeg
@Stevo
You mean Virtualbox 6.1.6, right?
Re: MX 19 Repository: The Liquorix Kernel Thread
Posted: Sun May 03, 2020 11:59 am
by mmikeinsantarosa
I wanted to upgrade to the latest liquorix kernel and virtualbox. I have been running the stock 4.19 kernel and VBox 6.1.4. Some of the newer kernels I've tried with virtualbox-6.1.4 ahve made my VM's and system unstable to th epoint of locking up my system completely.
steveo indictated that I should upgrade VBox then the kernel so that's how I proceeded.
After launching synaptic and enabling test w/preferences set to mx and reloading, synaptic couldn't see the virtualbox-6.1.6 that is in test.
I ran
and this command did show virtualbox-6.1.6 was available so I installed it using
Code: Select all
sudo apt-get install -t mx virtualbox
and it installed without issue.
To get the latest liquorix kernel, I used mxpi and from the main tree selector, I checked
Kernels->Liquorix 64 bit (Liquorix kernel Metldown patched)
kernel-pic.png
and installed.
The kernel installed with an error but I couldn't see what that was.
I used mx tools->boot options to boot to the new kernel and restarted.
When I launched virtualbox, it wouldn't start indicating that I needed to reinstall virtualbox-dkms again which I did but had the same problem with virtualbox.
I changed boot options to go back to the original 4.19 kernel, restarted, removed the new liquorix kernel and virtualbox and put the stock virtualbox back on and all was well.
Now synaptic showed the new virtualbox-6.1.6 so I upgraded and virtualbox worked w/o issue.
Next I used synaptic (w/test enabled) to locate the latest liquorix kernel tagged 5.6-2 (5.6.0-8.1-liquorix-amd64) which it did w/o issue, changed boot options to use this kernel and restarted.
All is well with the latest liquorix kernel and VBox 6.1.6.
Summary:
I'm curious why synaptic originally couldn't see virtualbox-6.1.6
-If somebody is running an older virtualbox, does their synaptic show 6.1.6 is available?
Which kernel does mxpi have hooked up to this pick? It didn't install correctly?
After installing the kernel that was hooked up to mxpi, virtualbox-6.1.6 was broken.
-Has anybody else tried to upgrade to this kernel after installing VBox-6.1.6 and if so, was VBox OK?
I have no issues with these packages now but I thought I'd report what I saw yesterday.
Code: Select all
$ inxi -F
System: Host: mx19LT01 Kernel: 5.6.0-8.1-liquorix-amd64 x86_64 bits: 64 Desktop: Xfce 4.14.2
Distro: MX-19.1_x64 patito feo October 21 2019
Machine: Type: Laptop System: Dell product: Precision 3510 v: N/A serial: <root required>
Mobo: Dell model: 0PVGJH v: A00 serial: <root required> UEFI [Legacy]: Dell v: 01.08.03 date: 07/14/2016
Battery: ID-1: BAT0 charge: 37.9 Wh condition: 37.9/62.0 Wh (61%)
CPU: Topology: Quad Core model: Intel Core i7-6820HQ bits: 64 type: MT MCP L2 cache: 8192 KiB
Speed: 2875 MHz min/max: 800/3600 MHz Core speeds (MHz): 1: 2988 2: 3245 3: 3320 4: 3325 5: 3270 6: 3280 7: 3162
8: 3298
Graphics: Device-1: Intel HD Graphics 530 driver: i915 v: kernel
Device-2: Advanced Micro Devices [AMD/ATI] Venus LE [Radeon HD 8830M] driver: radeon v: kernel
Display: x11 server: X.Org 1.20.4 driver: ati,modesetting,radeon unloaded: fbdev,vesa resolution: 1920x1080~60Hz
OpenGL: renderer: Mesa DRI Intel HD Graphics 530 (Skylake GT2) v: 4.5 Mesa 18.3.6
Audio: Device-1: Intel Sunrise Point-H HD Audio driver: snd_hda_intel
Sound Server: ALSA v: k5.6.0-8.1-liquorix-amd64
Network: Device-1: Intel Ethernet I219-LM driver: e1000e
IF: eth0 state: down mac: 28:f1:0e:1d:95:cf
Device-2: Intel Wireless 8260 driver: iwlwifi
IF: wlan0 state: up mac: e4:a4:71:3c:0f:87
IF-ID-1: wwan0 state: down mac: 36:90:18:97:0c:ff
Drives: Local Storage: total: 476.94 GiB used: 409.06 GiB (85.8%)
ID-1: /dev/sda vendor: LITE-ON model: CV3-8D512-11 SATA 512GB size: 476.94 GiB
Partition: ID-1: / size: 466.53 GiB used: 409.06 GiB (87.7%) fs: ext4 dev: /dev/sda1
ID-2: swap-1 size: 1.95 GiB used: 0 KiB (0.0%) fs: swap dev: /dev/sda2
Sensors: System Temperatures: cpu: 66.0 C mobo: 53.0 C sodimm: 49.0 C gpu: radeon temp: 25 C
Fan Speeds (RPM): cpu: 2207
Info: Processes: 280 Uptime: 1h 01m Memory: 31.01 GiB used: 24.30 GiB (78.4%) Shell: bash inxi: 3.0.36
- mike
Re: MX 19 Repository: The Liquorix Kernel Thread
Posted: Mon May 04, 2020 2:18 am
by Stevo
Synaptic won't see any packages from the MX 19 test repo until you specifically tell it to prefer the packages from there. MXPI is the recommended UI for installing from the test repo, anyway.
Yes, I'm also using VBox 6.1.6 with the latest Liquorix 5.6 kernel. The -ext-pack package is suggested, not an automatic upgrade, so you should type "virtualbox" in MXPI's search on the test repo tab and install everything that's an upgrade.
Re: MX 19 Repository: The Liquorix Kernel Thread
Posted: Mon May 04, 2020 11:16 am
by mmikeinsantarosa
Stevo wrote: Mon May 04, 2020 2:18 am
Synaptic won't see any packages from the MX 19 test repo until you specifically tell it to prefer the packages from there. MXPI is the recommended UI for installing from the test repo, anyway.
Yes, I'm also using VBox 6.1.6 with the latest Liquorix 5.6 kernel. The -ext-pack package is suggested, not an automatic upgrade, so you should type "virtualbox" in MXPI's search on the test repo tab and install everything that's an upgrade.
And that's what I did, Enabled test and set preferences to mx and reloaded. After this VB-6.1.6 didn't show up in synaptic. At the time, I didn't try mxpi for a newer VB. Instead, I used apt-cache policy to see if there was a newer one available and Vbox 6.1.6 was.
Re: MX 19 Repository: The Liquorix Kernel Thread
Posted: Sun Jul 05, 2020 5:30 am
by asqwerth
This is regarding Liquorix 5.7 in Test Repo. I'm finally able to use my network card on my laptop with Liq 5.7.
It wasn't working with Liq 5.2 to 5.6. Really weird. My machine is only about 3 years old.
However, it can't build the VB modules for 6.1.
Code: Select all
Selecting previously unselected package linux-headers-5.7.0-6.4-liquorix-amd64.
(Reading database ... 428755 files and directories currently installed.)
Preparing to unpack .../linux-headers-5.7.0-6.4-liquorix-amd64_5.7-6~mx19+1_amd64.deb ...
Unpacking linux-headers-5.7.0-6.4-liquorix-amd64 (5.7-6~mx19+1) ...
Selecting previously unselected package linux-image-5.7.0-6.4-liquorix-amd64.
Preparing to unpack .../linux-image-5.7.0-6.4-liquorix-amd64_5.7-6~mx19+1_amd64.deb ...
Unpacking linux-image-5.7.0-6.4-liquorix-amd64 (5.7-6~mx19+1) ...
Setting up linux-headers-5.7.0-6.4-liquorix-amd64 (5.7-6~mx19+1) ...
/etc/kernel/header_postinst.d/dkms:
Error! Bad return status for module build on kernel: 5.7.0-6.4-liquorix-amd64 (x86_64)
Consult /var/lib/dkms/broadcom-sta/6.30.223.271/build/make.log for more information.
System has not been booted with systemd as init system (PID 1). Can't operate.
Failed to connect to bus: Host is down
Error! Bad return status for module build on kernel: 5.7.0-6.4-liquorix-amd64 (x86_64)
Consult /var/lib/dkms/virtualbox/6.1.2/build/make.log for more information.
Error! Bad return status for module build on kernel: 5.7.0-6.4-liquorix-amd64 (x86_64)
Consult /var/lib/dkms/virtualbox-guest/6.1.2/build/make.log for more information.
Setting up linux-image-5.7.0-6.4-liquorix-amd64 (5.7-6~mx19+1) ...
I: /vmlinuz is now a symlink to boot/vmlinuz-5.7.0-6.4-liquorix-amd64
I: /initrd.img is now a symlink to boot/initrd.img-5.7.0-6.4-liquorix-amd64
/etc/kernel/postinst.d/dkms:
Error! Bad return status for module build on kernel: 5.7.0-6.4-liquorix-amd64 (x86_64)
Consult /var/lib/dkms/broadcom-sta/6.30.223.271/build/make.log for more information.
Error! Bad return status for module build on kernel: 5.7.0-6.4-liquorix-amd64 (x86_64)
Consult /var/lib/dkms/virtualbox/6.1.2/build/make.log for more information.
Error! Bad return status for module build on kernel: 5.7.0-6.4-liquorix-amd64 (x86_64)
Consult /var/lib/dkms/virtualbox-guest/6.1.2/build/make.log for more information.
/etc/kernel/postinst.d/initramfs-tools:
update-initramfs: Generating /boot/initrd.img-5.7.0-6.4-liquorix-amd64
W: Possible missing firmware /lib/firmware/rtl_nic/rtl8125a-3.fw for module r8169
W: Possible missing firmware /lib/firmware/rtl_nic/rtl8168fp-3.fw for module r8169
cryptsetup: WARNING: The initramfs image may not contain cryptsetup binaries
nor crypto modules. If that's on purpose, you may want to uninstall the
'cryptsetup-initramfs' package in order to disable the cryptsetup initramfs
integration and avoid this warning.
W: Possible missing firmware /lib/firmware/i915/skl_huc_2.0.0.bin for module i915
W: Possible missing firmware /lib/firmware/i915/bxt_huc_2.0.0.bin for module i915
W: Possible missing firmware /lib/firmware/i915/kbl_huc_4.0.0.bin for module i915
W: Possible missing firmware /lib/firmware/i915/glk_huc_4.0.0.bin for module i915
W: Possible missing firmware /lib/firmware/i915/kbl_huc_4.0.0.bin for module i915
W: Possible missing firmware /lib/firmware/i915/cml_huc_4.0.0.bin for module i915
W: Possible missing firmware /lib/firmware/i915/cml_guc_33.0.0.bin for module i915
W: Possible missing firmware /lib/firmware/i915/icl_huc_9.0.0.bin for module i915
W: Possible missing firmware /lib/firmware/i915/ehl_huc_9.0.0.bin for module i915
W: Possible missing firmware /lib/firmware/i915/ehl_guc_33.0.4.bin for module i915
W: Possible missing firmware /lib/firmware/i915/tgl_huc_7.0.12.bin for module i915
W: Possible missing firmware /lib/firmware/i915/tgl_guc_35.2.0.bin for module i915
W: Possible missing firmware /lib/firmware/i915/icl_dmc_ver1_09.bin for module i915
W: Possible missing firmware /lib/firmware/i915/tgl_dmc_ver2_06.bin for module i915
/etc/kernel/postinst.d/zz-update-grub:
Generating grub configuration file ...
Found theme: /boot/grub/themes/linen/theme.txt
Found linux image: /boot/vmlinuz-5.7.0-6.4-liquorix-amd64
Found initrd image: /boot/initrd.img-5.7.0-6.4-liquorix-amd64
Found linux image: /boot/vmlinuz-4.19.0-6-amd64
Found initrd image: /boot/initrd.img-4.19.0-6-amd64
Found mtest-64.efi image: /boot/uefi-mt/mtest-64.efi
Adding boot menu entry for EFI firmware configuration
done
Trying to open VB and run a VM led to the usual:
Code: Select all
VirtualBox Linux kernel driver is either not loaded or not set up correctly. Please reinstall virtualbox-dkms package and load the kernel module by executing
'modprobe vboxdrv'
as root.
When I tried to reinstall the dkms package:
Code: Select all
sudo apt install --reinstall virtualbox-dkms
Reading package lists... Done
Building dependency tree
Reading state information... Done
The following packages were automatically installed and are no longer required:
gnome-desktop3-data gnome-settings-daemon gnome-settings-daemon-common libfuse3-3
libgeoclue-2-0 libgeocode-glib0 libgnome-desktop-3-17 libgweather-3-15
libgweather-common libmicrodns0 libmikmod3 libsdl-mixer1.2
Use 'sudo apt autoremove' to remove them.
0 upgraded, 0 newly installed, 1 reinstalled, 0 to remove and 0 not upgraded.
Need to get 716 kB of archives.
After this operation, 0 B of additional disk space will be used.
Get:1 https://mirrors.xtom.com.hk/mx-packages/mx/repo buster/main amd64 virtualbox-dkms amd64 6.1.2-dfsg-1~mx19+1 [716 kB]
Fetched 716 kB in 0s (1,614 kB/s)
(Reading database ... 458143 files and directories currently installed.)
Preparing to unpack .../virtualbox-dkms_6.1.2-dfsg-1~mx19+1_amd64.deb ...
-------- Uninstall Beginning --------
Module: virtualbox
Version: 6.1.2
Kernel: 4.19.0-6-amd64 (x86_64)
-------------------------------------
Status: Before uninstall, this module version was ACTIVE on this kernel.
vboxdrv.ko:
- Uninstallation
- Deleting from: /lib/modules/4.19.0-6-amd64/updates/
rmdir: failed to remove 'updates': Directory not empty
- Original module
- No original module was found for this module on this kernel.
- Use the dkms install command to reinstall any previous module version.
vboxnetadp.ko:
- Uninstallation
- Deleting from: /lib/modules/4.19.0-6-amd64/updates/
rmdir: failed to remove 'updates': Directory not empty
- Original module
- No original module was found for this module on this kernel.
- Use the dkms install command to reinstall any previous module version.
vboxnetflt.ko:
- Uninstallation
- Deleting from: /lib/modules/4.19.0-6-amd64/updates/
rmdir: failed to remove 'updates': Directory not empty
- Original module
- No original module was found for this module on this kernel.
- Use the dkms install command to reinstall any previous module version.
depmod...
DKMS: uninstall completed.
------------------------------
Deleting module version: 6.1.2
completely from the DKMS tree.
------------------------------
Done.
Unpacking virtualbox-dkms (6.1.2-dfsg-1~mx19+1) over (6.1.2-dfsg-1~mx19+1) ...
Setting up virtualbox-dkms (6.1.2-dfsg-1~mx19+1) ...
Loading new virtualbox-6.1.2 DKMS files...
Building for 5.7.0-6.4-liquorix-amd64
Building initial module for 5.7.0-6.4-liquorix-amd64
Error! Bad return status for module build on kernel: 5.7.0-6.4-liquorix-amd64 (x86_64)
Consult /var/lib/dkms/virtualbox/6.1.2/build/make.log for more information.
dpkg: error processing package virtualbox-dkms (--configure):
installed virtualbox-dkms package post-installation script subprocess returned error exit status 10
Errors were encountered while processing:
virtualbox-dkms
E: Sub-process /usr/bin/dpkg returned an error code (1)
tuaz@mx19:~
$ sudo dpkg -C
The following packages are only half configured, probably due to problems
configuring them the first time. The configuration should be retried using
dpkg --configure <package> or the configure menu option in dselect:
virtualbox-dkms x86 virtualization solution - kernel module sources for d
Code: Select all
sudo dpkg --configure --pending
Setting up virtualbox-dkms (6.1.2-dfsg-1~mx19+1) ...
Removing old virtualbox-6.1.2 DKMS files...
------------------------------
Deleting module version: 6.1.2
completely from the DKMS tree.
------------------------------
Done.
Loading new virtualbox-6.1.2 DKMS files...
Building for 5.7.0-6.4-liquorix-amd64
Building initial module for 5.7.0-6.4-liquorix-amd64
Error! Bad return status for module build on kernel: 5.7.0-6.4-liquorix-amd64 (x86_64)
Consult /var/lib/dkms/virtualbox/6.1.2/build/make.log for more information.
dpkg: error processing package virtualbox-dkms (--configure):
installed virtualbox-dkms package post-installation script subprocess returned error exit status 10
Errors were encountered while processing:
virtualbox-dkms
tuaz@mx19:~
$ sudo modprobe vboxdrv
modprobe: FATAL: Module vboxdrv not found in directory /lib/modules/5.7.0-6.4-liquorix-amd64
QSI of laptop:
Code: Select all
System:
Host: mx19 Kernel: 5.7.0-6.4-liquorix-amd64 x86_64 bits: 64 compiler: gcc
v: 8.3.0
parameters: audit=0 intel_pstate=disable
BOOT_IMAGE=/boot/vmlinuz-5.7.0-6.4-liquorix-amd64
root=UUID=d36550cf-8350-4b1c-805f-10edeabce122 ro quiet splash
Desktop: Xfce 4.14.2 tk: Gtk 3.24.5 info: xfce4-panel wm: xfwm4
dm: LightDM 1.26.0 Distro: MX-19.2_x64 patito feo October 21 2019
base: Debian GNU/Linux 10 (buster)
Machine:
Type: Laptop System: product: N13xWU v: N/A serial: <filter>
Chassis: type: 10 serial: <filter>
Mobo: model: N13xWU serial: <filter> UEFI: American Megatrends
v: 1.05.04 date: 08/04/2017
Battery:
ID-1: BAT0 charge: 29.8 Wh condition: 32.8/35.3 Wh (93%) volts: 12.0/11.4
model: Notebook BAT type: Li-ion serial: <filter> status: Discharging
CPU:
Topology: Quad Core model: Intel Core i7-8550U bits: 64 type: MT MCP
arch: Kaby Lake family: 6 model-id: 8E (142) stepping: A (10) microcode: D6
L2 cache: 8192 KiB
flags: avx avx2 lm nx pae sse sse2 sse3 sse4_1 sse4_2 ssse3 vmx bogomips: 31999
Speed: 1021 MHz min/max: 400/1100 MHz boost: enabled Core speeds (MHz): 1: 800
2: 800 3: 800 4: 800 5: 800 6: 800 7: 800 8: 800
Vulnerabilities: Type: itlb_multihit status: KVM: Split huge pages
Type: l1tf
mitigation: PTE Inversion; VMX: conditional cache flushes, SMT vulnerable
Type: mds mitigation: Clear CPU buffers; SMT vulnerable
Type: meltdown mitigation: PTI
Type: spec_store_bypass
mitigation: Speculative Store Bypass disabled via prctl and seccomp
Type: spectre_v1
mitigation: usercopy/swapgs barriers and __user pointer sanitization
Type: spectre_v2 mitigation: Full generic retpoline, IBPB: conditional,
IBRS_FW, STIBP: conditional, RSB filling
Type: srbds mitigation: Microcode
Type: tsx_async_abort status: Not affected
Graphics:
Device-1: Intel UHD Graphics 620 vendor: CLEVO/KAPOK driver: i915 v: kernel
bus ID: 00:02.0 chip ID: 8086:5917
Display: x11 server: X.Org 1.20.4 driver: modesetting unloaded: fbdev,vesa
resolution: 1920x1080~60Hz
OpenGL: renderer: Mesa DRI Intel UHD Graphics 620 (Kabylake GT2)
v: 4.5 Mesa 18.3.6 compat-v: 3.0 direct render: Yes
Audio:
Device-1: Intel Sunrise Point-LP HD Audio vendor: CLEVO/KAPOK
driver: snd_hda_intel v: kernel bus ID: 00:1f.3 chip ID: 8086:9d71
Sound Server: ALSA v: k5.7.0-6.4-liquorix-amd64
Network:
Device-1: Realtek RTL8111/8168/8411 PCI Express Gigabit Ethernet
vendor: CLEVO/KAPOK driver: r8169 v: kernel port: e000 bus ID: 3a:00.1
chip ID: 10ec:8168
IF: eth0 state: down mac: <filter>
Device-2: Intel Dual Band Wireless-AC 3168NGW [Stone Peak] driver: iwlwifi
v: kernel port: e000 bus ID: 3b:00.0 chip ID: 8086:24fb
IF: wlan0 state: up mac: <filter>
Drives:
Local Storage: total: 465.76 GiB used: 38.00 GiB (8.2%)
ID-1: /dev/sda vendor: Samsung model: SSD 850 EVO M.2 500GB size: 465.76 GiB
block size: physical: 512 B logical: 512 B speed: 6.0 Gb/s serial: <filter>
rev: 1B6Q scheme: GPT
Partition:
ID-1: / raw size: 54.69 GiB size: 53.58 GiB (97.97%) used: 15.10 GiB (28.2%)
fs: ext4 dev: /dev/sda4
Sensors:
System Temperatures: cpu: 53.0 C mobo: N/A
Fan Speeds (RPM): N/A
Repos:
No active apt repos in: /etc/apt/sources.list
Active apt repos in: /etc/apt/sources.list.d/debian-stable-updates.list
1: deb http://deb.debian.org/debian buster-updates main contrib non-free
Active apt repos in: /etc/apt/sources.list.d/debian.list
1: deb http://deb.debian.org/debian buster main contrib non-free
2: deb http://deb.debian.org/debian-security buster/updates main contrib non-free
Active apt repos in: /etc/apt/sources.list.d/google-chrome.list
1: deb [arch=amd64] http://dl.google.com/linux/chrome/deb/ stable main
Active apt repos in: /etc/apt/sources.list.d/mx.list
1: deb https://mirrors.xtom.com.hk/mx-packages/mx/repo/ buster 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
Active apt repos in: /etc/apt/sources.list.d/teams.list
1: deb [arch=amd64] https://packages.microsoft.com/repos/ms-teams stable main
No active apt repos in: /etc/apt/sources.list.d/various.list
Info:
Processes: 266 Uptime: 19m Memory: 15.53 GiB used: 1.61 GiB (10.4%)
Init: SysVinit v: 2.93 runlevel: 5 default: 5 Compilers: gcc: 8.3.0 alt: 8
Shell: bash v: 5.0.3 running in: quick-system-in inxi: 3.0.36
Re: MX 19 Repository: The Liquorix Kernel Thread
Posted: Sun Jul 05, 2020 9:28 am
by eriefisher
This is one of the biggest issues with Virtual box. You never know if the modules going to get built or not or it doesn't get loaded at boot. It happen all the time. My solution was to rid myself of this closed source software and start using KVM. It's easy to set up, runs natively in the kernel and you already have most of it built in. There are a few packages to install to manage it but easily available. It will also import your VB vm's. Problem solved, no more flaky closed source software.
Re: MX 19 Repository: The Liquorix Kernel Thread
Posted: Mon Sep 07, 2020 11:58 am
by andyprough
The 5.8-3 Liquorix kernel has been added to the MX Testing Repo.
However neither the Nvidia or Virtualbox packages have yet been updated to build their kernel modules with 5.8 series kernels. So we do not have working Nvidia drivers or Virtualbox building for 5.8 kernels yet. If you need Nvidia or Virtualbox drivers, do not use this 5.8 Liquorix kernel for now. I'll put updates on this Liquorix kernel announcement thread as Nvidia and Virtualbox drivers become available.
Re: MX 19 Repository: The Liquorix Kernel Thread
Posted: Thu Sep 10, 2020 4:59 am
by fossean
The latest nvidia drivers in the test repo (450.66) are now working working correctly with liquorix 5.8.0-7.1
Re: MX 19 Repository: The Liquorix Kernel Thread
Posted: Tue Nov 10, 2020 6:17 am
by fossean
Upgrade to latest Liquorix 5.9.0-6.2 boots successfully with latest nvidia drivers (450.80.02).
Attempt to boot with previous nvidia driver failed and loaded nouveau instead.
Code: Select all
System: Host: <filter> Kernel: 5.9.0-6.2-liquorix-amd64 x86_64 bits: 64 compiler: N/A
parameters: audit=0 intel_pstate=disable
BOOT_IMAGE=/boot/vmlinuz-5.9.0-6.2-liquorix-amd64
root=UUID=<filter> ro quiet splash
Desktop: Xfce 4.14.2 tk: Gtk 3.24.5 info: xfce4-panel wm: Compiz 0.8.18
dm: LightDM 1.26.0 Distro: MX-19.2_x64 patito feo October 15 2019
base: Debian GNU/Linux 10 (buster)
Machine: Type: Desktop Mobo: MSI model: 760GA-P43(FX) (MS-7699) v: 1.0 serial: <filter>
BIOS: American Megatrends v: 1.3 date: 10/14/2014
CPU: Topology: 6-Core model: AMD FX-6300 bits: 64 type: MCP arch: Bulldozer
family: 15 (21) model-id: 2 stepping: N/A microcode: 6000852 L2 cache: 2048 KiB
flags: avx lm nx pae sse sse2 sse3 sse4_1 sse4_2 sse4a ssse3 svm bogomips: 41995
Speed: 1396 MHz min/max: 1400/3500 MHz boost: enabled Core speeds (MHz): 1: 1400
2: 1399 3: 2402 4: 3424 5: 1399 6: 1399
Vulnerabilities: Type: itlb_multihit status: Not affected
Type: l1tf status: Not affected
Type: mds status: Not affected
Type: meltdown status: Not affected
Type: spec_store_bypass
mitigation: Speculative Store Bypass disabled via prctl and seccomp
Type: spectre_v1 mitigation: usercopy/swapgs barriers and __user pointer sanitization
Type: spectre_v2
mitigation: Full AMD retpoline, IBPB: conditional, STIBP: disabled, RSB filling
Type: srbds status: Not affected
Type: tsx_async_abort status: Not affected
Graphics: Device-1: NVIDIA GP106 [GeForce GTX 1060 3GB] vendor: ZOTAC driver: nvidia
v: 450.80.02 bus ID: 01:00.0 chip ID: 10de:1c02
Display: x11 server: X.Org 1.20.4 driver: nvidia
unloaded: fbdev,modesetting,nouveau,vesa alternate: nv compositor: compiz v: 0.8.18
resolution: 1920x1080~60Hz
OpenGL: renderer: GeForce GTX 1060 3GB/PCIe/SSE2 v: 4.6.0 NVIDIA 450.80.02
direct render: Yes
Audio: Device-1: AMD SBx00 Azalia vendor: Micro-Star MSI driver: snd_hda_intel v: kernel
bus ID: 00:14.2 chip ID: 1002:4383
Device-2: NVIDIA GP106 High Definition Audio vendor: ZOTAC driver: snd_hda_intel
v: kernel bus ID: 01:00.1 chip ID: 10de:10f1
Sound Server: ALSA v: k5.9.0-6.2-liquorix-amd64
Network: Device-1: Realtek RTL8111/8168/8411 PCI Express Gigabit Ethernet
vendor: Micro-Star MSI driver: r8169 v: kernel port: c800 bus ID: 02:00.0
chip ID: 10ec:8168
IF: eth0 state: up speed: 1000 Mbps duplex: full mac: <filter>
Drives: Local Storage: total: 1.49 TiB used: 575.25 GiB (37.7%)
ID-1: /dev/sda vendor: Seagate model: ST1000DM003-1ER162 size: 931.51 GiB block size:
physical: 4096 B logical: 512 B speed: 3.0 Gb/s rotation: 7200 rpm serial: <filter>
rev: CC45 scheme: MBR
ID-2: /dev/sdb vendor: Western Digital model: WD6400AAKS-22A7B2 size: 596.17 GiB
block size: physical: 512 B logical: 512 B speed: 3.0 Gb/s serial: <filter> rev: 3B01
scheme: MBR
Partition: ID-1: / raw size: 29.30 GiB size: 28.71 GiB (98.00%) used: 17.73 GiB (61.7%) fs: ext4
dev: /dev/sda5
ID-2: /home raw size: 900.78 GiB size: 885.64 GiB (98.32%) used: 557.52 GiB (63.0%)
fs: ext4 dev: /dev/sda7
ID-3: swap-1 size: 450.0 MiB used: 0 KiB (0.0%) fs: swap swappiness: 15 (default 60)
cache pressure: 100 (default) dev: /dev/sda6
Sensors: System Temperatures: cpu: 57.0 C mobo: 40.0 C gpu: nvidia temp: 40 C
Fan Speeds (RPM): cpu: 0 fan-1: 656 fan-3: 0 gpu: nvidia fan: 55%
Voltages: 12v: N/A 5v: N/A 3.3v: 3.34 vbat: 3.23
Repos: No active apt repos in: /etc/apt/sources.list
Active apt repos in: /etc/apt/sources.list.d/debian-stable-updates.list
1: deb http://deb.debian.org/debian/ buster-updates main contrib non-free
Active apt repos in: /etc/apt/sources.list.d/debian.list
1: deb http://deb.debian.org/debian/ buster main contrib non-free
2: deb http://deb.debian.org/debian-security/ buster/updates main contrib non-free
Active apt repos in: /etc/apt/sources.list.d/mx.list
1: deb http://mxrepo.com/mx/repo/ buster main non-free
Active apt repos in: /etc/apt/sources.list.d/spotify.list
1: deb http://repository.spotify.com stable non-free
No active apt repos in: /etc/apt/sources.list.d/various.list
Active apt repos in: /etc/apt/sources.list.d/vivaldi.list
1: deb http://repo.vivaldi.com/stable/deb/ stable main
Info: Processes: 265 Uptime: 2m Memory: 15.63 GiB used: 847.5 MiB (5.3%) Init: SysVinit
v: 2.93 runlevel: 5 default: 5 Compilers: gcc: 8.3.0 alt: 8 Shell: quick-system-in
running in: quick-system-in inxi: 3.0.36
Re: MX 19 Repository: The Liquorix Kernel Thread
Posted: Tue Nov 10, 2020 6:23 pm
by Stevo
Is that 5.9 kernel from our test repo? Hopefully, the new maintainer will announce at least major version bumps here...hint hint
Re: MX 19 Repository: The Liquorix Kernel Thread
Posted: Wed Nov 18, 2020 10:59 am
by Otter
Stevo wrote: Tue Nov 10, 2020 6:23 pm
Is that 5.9 kernel from our test repo? Hopefully, the new maintainer will announce at least major version bumps here...hint hint
5.9.0-8.3-liquorix-amd64 from test repo works with nvidia driver from test repo. I have AHS repo enabled too. Thanks to all the maintainers.
Re: MX 19 Repository: The Liquorix Kernel Thread
Posted: Wed Nov 18, 2020 12:44 pm
by andyprough
Stevo wrote: Tue Nov 10, 2020 6:23 pm
Is that 5.9 kernel from our test repo? Hopefully, the new maintainer will announce at least major version bumps here...hint hint
I'd better start doing those announcements, it's not something I'd been thinking about before.
Can you tell us Steve why Nvidia is suddenly working by default with these recent versions of Liquorix? Is it because of new Nvidia firmware in the repo?
Re: MX 19 Repository: The Liquorix Kernel Thread
Posted: Wed Nov 18, 2020 4:03 pm
by Stevo
It's because Debian added 5.9-compatible new Nvidia driver versions upstream in Sid, I backported them and sent them to Tim, and he added them to the repos. No mystery--I have had to do that with most new major kernel version bumps. Virtual Box is another big pain, too.
Re: MX 19 Repository: The Liquorix Kernel Thread
Posted: Mon Jan 04, 2021 1:26 pm
by andyprough
There's been a flurry of activity on the new Liquorix kernel 5.10 this week, so I've started out by building the 5.10-5 package. I've sent it to Tim for inclusion in the test repo.
Prior warnings about needing to install the latest Virtualbox, Nvidia, broadcom, and Bumblebee firmware prior to installing this new kernel MAY apply - hopefully Stevo will weigh in on that point.
Re: MX 19 Repository: The Liquorix Kernel Thread
Posted: Tue Jan 05, 2021 8:56 am
by fossean
Liquorix 5.10.0-4.3 booting fine here with latest available Nvidia driver 455.45.01
Code: Select all
System: Host: <filter> Kernel: 5.10.0-4.3-liquorix-amd64 x86_64 bits: 64 compiler: N/A
parameters: audit=0 intel_pstate=disable
BOOT_IMAGE=/boot/vmlinuz-5.10.0-4.3-liquorix-amd64
root=UUID=<filter> ro quiet splash
Desktop: Xfce 4.14.2 tk: Gtk 3.24.5 info: xfce4-panel wm: Compiz 0.8.18
dm: LightDM 1.26.0 Distro: MX-19.3_x64 patito feo October 15 2019
base: Debian GNU/Linux 10 (buster)
Machine: Type: Desktop Mobo: MSI model: 760GA-P43(FX) (MS-7699) v: 1.0 serial: <filter>
BIOS: American Megatrends v: 1.3 date: 10/14/2014
CPU: Topology: 6-Core model: AMD FX-6300 bits: 64 type: MCP arch: Bulldozer
family: 15 (21) model-id: 2 stepping: N/A microcode: 6000852 L2 cache: 2048 KiB
flags: avx lm nx pae sse sse2 sse3 sse4_1 sse4_2 sse4a ssse3 svm bogomips: 42000
Speed: 3798 MHz min/max: 1400/3500 MHz boost: enabled Core speeds (MHz): 1: 3261
2: 2868 3: 1398 4: 1399 5: 1676 6: 1849
Vulnerabilities: Type: itlb_multihit status: Not affected
Type: l1tf status: Not affected
Type: mds status: Not affected
Type: meltdown status: Not affected
Type: spec_store_bypass
mitigation: Speculative Store Bypass disabled via prctl and seccomp
Type: spectre_v1 mitigation: usercopy/swapgs barriers and __user pointer sanitization
Type: spectre_v2
mitigation: Full AMD retpoline, IBPB: conditional, STIBP: disabled, RSB filling
Type: srbds status: Not affected
Type: tsx_async_abort status: Not affected
Graphics: Device-1: NVIDIA GP106 [GeForce GTX 1060 3GB] vendor: ZOTAC driver: nvidia
v: 455.45.01 bus ID: 01:00.0 chip ID: 10de:1c02
Display: x11 server: X.Org 1.20.4 driver: nvidia
unloaded: fbdev,modesetting,nouveau,vesa alternate: nv compositor: compiz v: 0.8.18
resolution: 1920x1080~60Hz
OpenGL: renderer: GeForce GTX 1060 3GB/PCIe/SSE2 v: 4.6.0 NVIDIA 455.45.01
direct render: Yes
Audio: Device-1: AMD SBx00 Azalia vendor: Micro-Star MSI driver: snd_hda_intel v: kernel
bus ID: 00:14.2 chip ID: 1002:4383
Device-2: NVIDIA GP106 High Definition Audio vendor: ZOTAC driver: snd_hda_intel
v: kernel bus ID: 01:00.1 chip ID: 10de:10f1
Device-3: C-Media type: USB driver: hid-generic,snd-usb-audio,usbhid bus ID: 2-2:2
chip ID: 0d8c:0012 serial: <filter>
Sound Server: ALSA v: k5.10.0-4.3-liquorix-amd64
Network: Device-1: Realtek RTL8111/8168/8411 PCI Express Gigabit Ethernet
vendor: Micro-Star MSI driver: r8169 v: kernel port: c800 bus ID: 02:00.0
chip ID: 10ec:8168
IF: eth0 state: up speed: 1000 Mbps duplex: full mac: <filter>
Drives: Local Storage: total: 1.49 TiB used: 748.99 GiB (49.0%)
ID-1: /dev/sda vendor: Seagate model: ST1000DM003-1ER162 size: 931.51 GiB block size:
physical: 4096 B logical: 512 B speed: 3.0 Gb/s rotation: 7200 rpm serial: <filter>
rev: CC45 scheme: MBR
ID-2: /dev/sdb vendor: Western Digital model: WD6400AAKS-22A7B2 size: 596.17 GiB
block size: physical: 512 B logical: 512 B speed: 3.0 Gb/s serial: <filter> rev: 3B01
scheme: MBR
Partition: ID-1: / raw size: 29.30 GiB size: 28.71 GiB (98.00%) used: 19.23 GiB (67.0%) fs: ext4
dev: /dev/sda5
ID-2: /home raw size: 900.78 GiB size: 885.64 GiB (98.32%) used: 521.96 GiB (58.9%)
fs: ext4 dev: /dev/sda7
ID-3: swap-1 size: 450.0 MiB used: 0 KiB (0.0%) fs: swap swappiness: 15 (default 60)
cache pressure: 100 (default) dev: /dev/sda6
Sensors: System Temperatures: cpu: 51.0 C mobo: 35.0 C gpu: nvidia temp: 31 C
Fan Speeds (RPM): cpu: 0 fan-1: 643 fan-3: 0 gpu: nvidia fan: 53%
Voltages: 12v: N/A 5v: N/A 3.3v: 3.36 vbat: 3.25
Repos: No active apt repos in: /etc/apt/sources.list
Active apt repos in: /etc/apt/sources.list.d/debian-stable-updates.list
1: deb http://deb.debian.org/debian/ buster-updates main contrib non-free
Active apt repos in: /etc/apt/sources.list.d/debian.list
1: deb http://deb.debian.org/debian/ buster main contrib non-free
2: deb http://deb.debian.org/debian-security/ buster/updates main contrib non-free
Active apt repos in: /etc/apt/sources.list.d/mx.list
1: deb https://anorien.csc.warwick.ac.uk/mxlinux/packages/mx/repo/ buster main non-free
Active apt repos in: /etc/apt/sources.list.d/spotify.list
1: deb http://repository.spotify.com stable non-free
No active apt repos in: /etc/apt/sources.list.d/various.list
Active apt repos in: /etc/apt/sources.list.d/vivaldi.list
1: deb http://repo.vivaldi.com/stable/deb/ stable main
Info: Processes: 279 Uptime: 3m Memory: 15.63 GiB used: 1012.2 MiB (6.3%) Init: SysVinit
v: 2.93 runlevel: 5 default: 5 Compilers: gcc: 8.3.0 alt: 8 Shell: quick-system-in
running in: quick-system-in inxi: 3.0.36
Re: MX 19 Repository: The Liquorix Kernel Thread
Posted: Tue Jan 05, 2021 9:11 am
by andyprough
fossean wrote: Tue Jan 05, 2021 8:56 am
Liquorix 5.10.0-4.3 booting fine here with latest available Nvidia driver 455.45.01
That's great to hear.
Re: MX 19 Repository: The Liquorix Kernel Thread
Posted: Mon Jan 11, 2021 1:47 am
by JayM
Working fine here too. My VirtualBox (6.1.16) VMs wouldn't start until I installed the virtualbox-ext-pack package from the Test repo though (the Virtualbox Extensions were previously uninstalled and apparently weren't needed for the Debian 5.8.0-3 kernel but apparently are/is for the Liquorix kernel. All my VMs work now though.)
Re: MX 19 Repository: The Liquorix Kernel Thread
Posted: Mon Jan 11, 2021 8:54 am
by andyprough
JayM wrote: Mon Jan 11, 2021 1:47 am
Working fine here too. My VirtualBox (6.1.16) VMs wouldn't start until I installed the virtualbox-ext-pack package from the Test repo though (the Virtualbox Extensions were previously uninstalled and apparently weren't needed for the Debian 5.8.0-3 kernel but apparently are/is for the Liquorix kernel. All my VMs work now though.)
OK great. I'm sending up the latest 5.10-8 version of the Liquorix kernel today, should be in the test repo within a few hours.
Re: MX 19 Repository: The Liquorix Kernel Thread
Posted: Mon Jan 11, 2021 6:23 pm
by Stevo
Your previous 5.10 Liquorix kernel also works fine on an Acer Skylake Optimus laptop using Bumblebee with the patched 450.82 Nvidia drivers now in AHS and the MX test repos.
Re: MX 19 Repository: The Liquorix Kernel Thread
Posted: Mon Jan 11, 2021 6:51 pm
by andyprough
Re: MX 19 Repository: The Liquorix Kernel Thread
Posted: Tue Mar 02, 2021 11:38 pm
by andyprough
Once again, there's been another flurry of activity on the newest Liquorix kernel 5.11 this week, so I've started out by building the 5.11-6 package. Hopefully it will make it into the MX Test repo within the next day, depending on Tim's schedule.
Please let me know again if you have anything to report about it, good, bad, or ugly. As before, you might find you need to install the latest Virtualbox, Nvidia, broadcom, and Bumblebee firmware prior to installing this new kernel.
Re: MX 19 Repository: The Liquorix Kernel Thread
Posted: Wed Mar 03, 2021 3:05 am
by JayM
Question: I installed Liquorix 5.10.0-4.3 in January but now i can't find it in the test repo!?! I'd like to uninstall it prior to testing the latest 5.11 one so my (flat with no submenus) grub menu doesn't get too crowded. (I originally installed it from MXPI Pop Apps, Kernels.)
Re: MX 19 Repository: The Liquorix Kernel Thread
Posted: Wed Mar 03, 2021 8:21 am
by andyprough
JayM wrote: Wed Mar 03, 2021 3:05 am
Question: I installed Liquorix 5.10.0-4.3 in January but now i can't find it in the test repo!?! I'd like to uninstall it prior to testing the latest 5.11 one so my (flat with no submenus) grub menu doesn't get too crowded. (I originally installed it from MXPI Pop Apps, Kernels.)
Hi Jay, The way Tim handles the Liquorix repo is he has our most recent packaged version for each major version number (5.8.x, 5.9.x, 5.10.x) in the MX Test Repo, along with the very latest version that has been packaged. He removes the older ones after a new one comes in. So right at this moment, the 5.10.x versions in the MX Test Repo (
http://iso.mxrepo.com/mx/testrepo/pool/ ... x/?C=M;O=D) appear to be:
linux-image-5.10.0-15.2-liquorix-amd64_5.10-24
and
linux-image-5.10.0-17.1-liquorix-amd64_5.10-25
These would be the 5.10-24 and 5.10-25 kernels according to the Liquorix versioning, otherwise known as the 5.10.0-15.2 and 5.10.0-17.1 kernels according to the regular Linux kernel versioning. So your version 5.10.0-4.3 has been gone from the repo for a few weeks.
I would recommend using synaptic's Search function to find your kernel and kernel headers by searching for 'liquorix', and then using 'remove completely' in synaptic to remove them.
I know you are too advanced to make this mistake - but do please make sure you have booted up using a different kernel before removing it! I made that mistake myself once not that long ago - I only ever had to make that mistake once to have it burned into my consciousness forever. Since then, I always run 'uname -a' and double check my running kernel version before removing any kernels.
Re: MX 19 Repository: The Liquorix Kernel Thread
Posted: Thu Mar 04, 2021 9:39 am
by fossean
Liquorix 5.11.0-2.4 boots, but nvidia driver isn't loaded (installed driver is latest available in test repo, 455.45.01). Rebooted back to Liquorix 5.10 for now.
Code: Select all
System: Host: <filter> Kernel: 5.10.0-17.1-liquorix-amd64 x86_64 bits: 64 compiler: N/A
parameters: audit=0 intel_pstate=disable
BOOT_IMAGE=/boot/vmlinuz-5.10.0-17.1-liquorix-amd64
root=UUID=<filter> ro quiet splash
Desktop: Xfce 4.14.2 tk: Gtk 3.24.5 info: xfce4-panel wm: Compiz 0.8.18
dm: LightDM 1.26.0 Distro: MX-19.3_x64 patito feo October 15 2019
base: Debian GNU/Linux 10 (buster)
Machine: Type: Desktop Mobo: MSI model: 760GA-P43(FX) (MS-7699) v: 1.0 serial: <filter>
BIOS: American Megatrends v: 1.3 date: 10/14/2014
CPU: Topology: 6-Core model: AMD FX-6300 bits: 64 type: MCP arch: Bulldozer
family: 15 (21) model-id: 2 stepping: N/A microcode: 6000852 L2 cache: 2048 KiB
flags: avx lm nx pae sse sse2 sse3 sse4_1 sse4_2 sse4a ssse3 svm bogomips: 41999
Speed: 1394 MHz min/max: 1400/3500 MHz boost: enabled Core speeds (MHz): 1: 1878
2: 1587 3: 1400 4: 1400 5: 1522 6: 1468
Vulnerabilities: Type: itlb_multihit status: Not affected
Type: l1tf status: Not affected
Type: mds status: Not affected
Type: meltdown status: Not affected
Type: spec_store_bypass
mitigation: Speculative Store Bypass disabled via prctl and seccomp
Type: spectre_v1 mitigation: usercopy/swapgs barriers and __user pointer sanitization
Type: spectre_v2
mitigation: Full AMD retpoline, IBPB: conditional, STIBP: disabled, RSB filling
Type: srbds status: Not affected
Type: tsx_async_abort status: Not affected
Graphics: Device-1: NVIDIA GP106 [GeForce GTX 1060 3GB] vendor: ZOTAC driver: nvidia
v: 455.45.01 bus ID: 01:00.0 chip ID: 10de:1c02
Display: x11 server: X.Org 1.20.4 driver: nvidia
unloaded: fbdev,modesetting,nouveau,vesa alternate: nv compositor: compiz v: 0.8.18
resolution: 1920x1080~60Hz
OpenGL: renderer: GeForce GTX 1060 3GB/PCIe/SSE2 v: 4.6.0 NVIDIA 455.45.01
direct render: Yes
Audio: Device-1: AMD SBx00 Azalia vendor: Micro-Star MSI driver: snd_hda_intel v: kernel
bus ID: 00:14.2 chip ID: 1002:4383
Device-2: NVIDIA GP106 High Definition Audio vendor: ZOTAC driver: snd_hda_intel
v: kernel bus ID: 01:00.1 chip ID: 10de:10f1
Device-3: C-Media type: USB driver: hid-generic,snd-usb-audio,usbhid bus ID: 1-2:3
chip ID: 0d8c:0012 serial: <filter>
Sound Server: ALSA v: k5.10.0-17.1-liquorix-amd64
Network: Device-1: Realtek RTL8111/8168/8411 PCI Express Gigabit Ethernet
vendor: Micro-Star MSI driver: r8169 v: kernel port: c800 bus ID: 02:00.0
chip ID: 10ec:8168
IF: eth0 state: up speed: 1000 Mbps duplex: full mac: <filter>
Drives: Local Storage: total: 1.49 TiB used: 735.82 GiB (48.2%)
ID-1: /dev/sda vendor: Seagate model: ST1000DM003-1ER162 size: 931.51 GiB block size:
physical: 4096 B logical: 512 B speed: 3.0 Gb/s rotation: 7200 rpm serial: <filter>
rev: CC45 scheme: MBR
ID-2: /dev/sdb vendor: Western Digital model: WD6400AAKS-22A7B2 size: 596.17 GiB
block size: physical: 512 B logical: 512 B speed: 3.0 Gb/s serial: <filter> rev: 3B01
scheme: MBR
Partition: ID-1: / raw size: 29.30 GiB size: 28.71 GiB (98.00%) used: 19.69 GiB (68.6%) fs: ext4
dev: /dev/sda5
ID-2: /home raw size: 900.78 GiB size: 885.64 GiB (98.32%) used: 525.84 GiB (59.4%)
fs: ext4 dev: /dev/sda7
ID-3: swap-1 size: 450.0 MiB used: 0 KiB (0.0%) fs: swap swappiness: 15 (default 60)
cache pressure: 100 (default) dev: /dev/sda6
Sensors: System Temperatures: cpu: 51.0 C mobo: 37.0 C gpu: nvidia temp: 35 C
Fan Speeds (RPM): cpu: 0 fan-1: 642 fan-3: 0 gpu: nvidia fan: 54%
Voltages: 12v: N/A 5v: N/A 3.3v: 3.34 vbat: 3.25
Repos: No active apt repos in: /etc/apt/sources.list
Active apt repos in: /etc/apt/sources.list.d/debian-stable-updates.list
1: deb http://deb.debian.org/debian/ buster-updates main contrib non-free
Active apt repos in: /etc/apt/sources.list.d/debian.list
1: deb http://deb.debian.org/debian/ buster main contrib non-free
2: deb http://deb.debian.org/debian-security/ buster/updates main contrib non-free
Active apt repos in: /etc/apt/sources.list.d/mx.list
1: deb http://mirror.plusserver.com/mxlinux/mxlinux/mx/repo/ buster main non-free
Active apt repos in: /etc/apt/sources.list.d/spotify.list
1: deb http://repository.spotify.com stable non-free
No active apt repos in: /etc/apt/sources.list.d/various.list
Active apt repos in: /etc/apt/sources.list.d/vivaldi.list
1: deb http://repo.vivaldi.com/stable/deb/ stable main
Info: Processes: 277 Uptime: 18m Memory: 15.64 GiB used: 1.81 GiB (11.6%) Init: SysVinit
v: 2.93 runlevel: 5 default: 5 Compilers: gcc: 8.3.0 alt: 8 Shell: quick-system-in
running in: quick-system-in inxi: 3.0.36
Re: MX 19 Repository: The Liquorix Kernel Thread
Posted: Thu Mar 04, 2021 4:22 pm
by andyprough
fossean wrote: Thu Mar 04, 2021 9:39 am
Liquorix 5.11.0-2.4 boots, but nvidia driver isn't loaded (installed driver is latest available in test repo, 455.45.01). Rebooted back to Liquorix 5.10 for now.
We may need a new nvidia package like when this happened with Liquorix 5.6.
Re: MX 19 Repository: The Liquorix Kernel Thread
Posted: Sat Mar 13, 2021 9:03 am
by andyprough
I won't be updating the Liquorix 5.11 kernel this week as I'm out of town and away from my build computer, I'll do the next update next weekend.
Has anyone had any other good or bad experiences with the 5.11 series so far?
Re: MX 19 Repository: The Liquorix Kernel Thread
Posted: Sat Mar 20, 2021 5:03 pm
by ckester
andyprough wrote: Sat Mar 13, 2021 9:03 am
I won't be updating the Liquorix 5.11 kernel this week as I'm out of town and away from my build computer, I'll do the next update next weekend.
Has anyone had any other good or bad experiences with the 5.11 series so far?
$ uname -srvm
Linux 5.11.0-4.1-liquorix-amd64 #1 ZEN SMP PREEMPT liquorix 5.11-10~mx19+1 (2021-03-08) x86_64
No issues so far. :)
Re: MX 19 Repository: The Liquorix Kernel Thread
Posted: Sun Mar 21, 2021 10:48 pm
by Stevo
You may have to update the Nvidia drivers from buster-backports right now until I or another packager have time to port and test them for the MX repos. Backports is ahead of us at the moment.
Re: MX 19 Repository: The Liquorix Kernel Thread
Posted: Sun Mar 21, 2021 10:58 pm
by mmikeinsantarosa
virtualbox-6.1.18 for bullseye only
Re: MX 19 Repository: The Liquorix Kernel Thread
Posted: Mon Mar 22, 2021 5:33 pm
by Stevo
That last post might be in the wrong thread, except that we do need to rebuild the last virtualbox 6.1.18-3 from Sid, since the "-3" update there added a patch to support builds on the 5.11 kernel. Not only for mx21, but for mx19 and mx17 repos, too.
Re: MX 19 Repository: The Liquorix Kernel Thread
Posted: Wed May 19, 2021 11:19 pm
by andyprough
The Liquorix kernel 5.12 series is now available, and we are starting with version 5.12.3. Look for it to hit the repo soon.
Please let us know what works with it and what does not.
Re: MX 19 Repository: The Liquorix Kernel Thread
Posted: Thu May 20, 2021 3:12 am
by LibertyLinux
Resume from hibernation seems to take a tad longer but so far so good. I've no idea what to look for either but if the kernel doesn't automatically crash it I suppose it'll be ok.
System76 Lemur Pro Laptop
i7-1165G7, 16GB ddr4 3200, intel XE graphics, 980pro/970evo+ hd's / xfce
cool beans
Re: MX 19 Repository: The Liquorix Kernel Thread
Posted: Fri Jun 04, 2021 11:10 am
by fossean
Stevo wrote: Sun Mar 21, 2021 10:48 pm
You may have to update the Nvidia drivers from buster-backports right now until I or another packager have time to port and test them for the MX repos. Backports is ahead of us at the moment.
Liquorix 5.12.0-8.1 is working fine here with Nvidia 460.73 from backports.
Code: Select all
System: Host: <filter> Kernel: 5.12.0-8.1-liquorix-amd64 x86_64 bits: 64 compiler: N/A
parameters: audit=0 intel_pstate=disable
BOOT_IMAGE=/boot/vmlinuz-5.12.0-8.1-liquorix-amd64
root=UUID=<filter> ro quiet splash
Desktop: Xfce 4.14.2 tk: Gtk 3.24.5 info: xfce4-panel wm: Compiz 0.8.18
dm: LightDM 1.26.0 Distro: MX-19.4_x64 patito feo October 15 2019
base: Debian GNU/Linux 10 (buster)
Machine: Type: Desktop Mobo: MSI model: 760GA-P43(FX) (MS-7699) v: 1.0 serial: <filter>
BIOS: American Megatrends v: 1.3 date: 10/14/2014
CPU: Topology: 6-Core model: AMD FX-6300 bits: 64 type: MCP arch: Bulldozer
family: 15 (21) model-id: 2 stepping: N/A microcode: 6000852 L2 cache: 2048 KiB
flags: avx lm nx pae sse sse2 sse3 sse4_1 sse4_2 sse4a ssse3 svm bogomips: 41999
Speed: 1399 MHz min/max: 1400/3500 MHz boost: enabled Core speeds (MHz): 1: 1399
2: 1399 3: 3793 4: 1884 5: 3242 6: 2251
Vulnerabilities: Type: itlb_multihit status: Not affected
Type: l1tf status: Not affected
Type: mds status: Not affected
Type: meltdown status: Not affected
Type: spec_store_bypass
mitigation: Speculative Store Bypass disabled via prctl and seccomp
Type: spectre_v1 mitigation: usercopy/swapgs barriers and __user pointer sanitization
Type: spectre_v2
mitigation: Full AMD retpoline, IBPB: conditional, STIBP: disabled, RSB filling
Type: srbds status: Not affected
Type: tsx_async_abort status: Not affected
Graphics: Device-1: NVIDIA GP106 [GeForce GTX 1060 3GB] vendor: ZOTAC driver: nvidia
v: 460.73.01 bus ID: 01:00.0 chip ID: 10de:1c02
Display: x11 server: X.Org 1.20.4 driver: nvidia
unloaded: fbdev,modesetting,nouveau,vesa alternate: nv compositor: compiz v: 0.8.18
resolution: 1920x1080~60Hz
OpenGL: renderer: GeForce GTX 1060 3GB/PCIe/SSE2 v: 4.6.0 NVIDIA 460.73.01
direct render: Yes
Audio: Device-1: AMD SBx00 Azalia vendor: Micro-Star MSI driver: snd_hda_intel v: kernel
bus ID: 00:14.2 chip ID: 1002:4383
Device-2: NVIDIA GP106 High Definition Audio vendor: ZOTAC driver: snd_hda_intel
v: kernel bus ID: 01:00.1 chip ID: 10de:10f1
Sound Server: ALSA v: k5.12.0-8.1-liquorix-amd64
Network: Device-1: Realtek RTL8111/8168/8411 PCI Express Gigabit Ethernet
vendor: Micro-Star MSI driver: r8169 v: kernel port: c800 bus ID: 02:00.0
chip ID: 10ec:8168
IF: eth0 state: up speed: 1000 Mbps duplex: full mac: <filter>
Drives: Local Storage: total: 1.49 TiB used: 914.75 GiB (59.9%)
ID-1: /dev/sda vendor: Seagate model: ST1000DM003-1ER162 size: 931.51 GiB block size:
physical: 4096 B logical: 512 B speed: 3.0 Gb/s rotation: 7200 rpm serial: <filter>
rev: CC45 scheme: MBR
ID-2: /dev/sdb vendor: Western Digital model: WD6400AAKS-22A7B2 size: 596.17 GiB
block size: physical: 512 B logical: 512 B speed: 3.0 Gb/s serial: <filter> rev: 3B01
scheme: MBR
Partition: ID-1: / raw size: 29.30 GiB size: 28.71 GiB (98.00%) used: 21.61 GiB (75.3%) fs: ext4
dev: /dev/sda5
ID-2: /home raw size: 900.78 GiB size: 885.64 GiB (98.32%) used: 586.69 GiB (66.2%)
fs: ext4 dev: /dev/sda7
ID-3: swap-1 size: 450.0 MiB used: 0 KiB (0.0%) fs: swap swappiness: 15 (default 60)
cache pressure: 100 (default) dev: /dev/sda6
Sensors: System Temperatures: cpu: 61.0 C mobo: 46.8 C gpu: nvidia temp: 40 C
Fan Speeds (RPM): cpu: 0 fan-1: 654 fan-3: 0 gpu: nvidia fan: 57%
Voltages: 12v: N/A 5v: N/A 3.3v: 3.36 vbat: 3.25
Repos: No active apt repos in: /etc/apt/sources.list
Active apt repos in: /etc/apt/sources.list.d/debian-stable-updates.list
1: deb http://deb.debian.org/debian/ buster-updates main contrib non-free
Active apt repos in: /etc/apt/sources.list.d/debian.list
1: deb http://deb.debian.org/debian/ buster main contrib non-free
2: deb http://deb.debian.org/debian-security/ buster/updates main contrib non-free
Active apt repos in: /etc/apt/sources.list.d/google-earth-pro.list
1: deb [arch=amd64] http://dl.google.com/linux/earth/deb/ stable main
Active apt repos in: /etc/apt/sources.list.d/mx.list
1: deb http://mxrepo.com/mx/repo/ buster main non-free
Active apt repos in: /etc/apt/sources.list.d/spotify.list
1: deb http://repository.spotify.com stable non-free
No active apt repos in: /etc/apt/sources.list.d/various.list
Active apt repos in: /etc/apt/sources.list.d/vivaldi.list
1: deb http://repo.vivaldi.com/stable/deb/ stable main
Info: Processes: 282 Uptime: 13m Memory: 15.63 GiB used: 2.01 GiB (12.9%) Init: SysVinit
v: 2.93 runlevel: 5 default: 5 Compilers: gcc: 8.3.0 alt: 8 Shell: quick-system-in
running in: quick-system-in inxi: 3.0.36
Re: MX 19 Repository: The Liquorix Kernel Thread
Posted: Fri Jun 04, 2021 8:03 pm
by andyprough
fossean wrote: Fri Jun 04, 2021 11:10 am
Stevo wrote: Sun Mar 21, 2021 10:48 pm
You may have to update the Nvidia drivers from buster-backports right now until I or another packager have time to port and test them for the MX repos. Backports is ahead of us at the moment.
Liquorix 5.12.0-8.1 is working fine here with Nvidia 460.73 from backports.
That's good to hear. That version is also known as "5.12-7", because it is the 7th available Liquorix version of the 5.12 kernel. I'm in the process of packaging 5.12-12 right this moment.
Re: MX 19 Repository: The Liquorix Kernel Thread
Posted: Thu Jun 10, 2021 6:26 pm
by Stevo
Updated to the latest 5.12.0-9.1 version in the test repo--no problems to report so far!
Re: MX 19 Repository: The Liquorix Kernel Thread
Posted: Fri Jun 11, 2021 2:29 am
by andyprough
Stevo wrote: Thu Jun 10, 2021 6:26 pm
Updated to the latest 5.12.0-9.1 version in the test repo--no problems to report so far!
I'm kind of surprised to see that MX is the only distro on Repology that has Liquorix-linux in its official repos. Am I reading that correctly? I know Arch relegates it to the AUR and Ubuntu to a PPA, but I figured some other distros must be packaging it officially.
Re: MX 19 Repository: The Liquorix Kernel Thread
Posted: Fri Aug 13, 2021 10:08 pm
by andyprough
The Liquorix kernel 5.13 series is now available, and we are starting with version 5.13.3. Look for it to hit the repo soon if it hasn't already.
Kind of a Friday the 13th special for all you Jason horror movie fans.
Please let us know if it's working well for you or not.
Re: MX 19 Repository: The Liquorix Kernel Thread
Posted: Fri Aug 13, 2021 10:33 pm
by mmikeinsantarosa
.
Re: MX 19 Repository: The Liquorix Kernel Thread
Posted: Fri Aug 13, 2021 10:39 pm
by andyprough
It's a Jason Voorhees horror party. Fortunately I was born on the 13th, so unlike the rest of you I'm quite safe.
Don't any of you go for any moonlight lake swims tonight though...
Re: MX 19 Repository: The Liquorix Kernel Thread
Posted: Sun Aug 15, 2021 10:52 am
by tequila
Code: Select all
[code]
Snapshot created on: 20210805_1812
System: Kernel: 5.12.0-19.4-liquorix-amd64 x86_64 bits: 64 compiler: gcc v: 8.3.0
parameters: audit=0 intel_pstate=disable
BOOT_IMAGE=/boot/vmlinuz-5.12.0-19.4-liquorix-amd64
root=UUID=<filter> ro audit=0 intel_pstate=disable
nohz=off pcie_aspm=off intel_idle.max_cstate=0 idle=halt processor.max_cstate=0
ipv6.disable=1 i8042.nopnp rootflags=data=writeback nouveau.modeset=0
Desktop: Fluxbox 1.3.7 info: tint2 vt: 7 dm: LightDM 1.26.0
Distro: MX-19.4_x64 patito feo October 21 2019 base: Debian GNU/Linux 10 (buster)
Machine: Type: Laptop System: ASUSTeK product: GL702VSK v: 1.0 serial: <filter>
Mobo: ASUSTeK model: GL702VSK v: 1.0 serial: <filter> UEFI: American Megatrends
v: GL702VSK.311 date: 04/19/2019
Battery: ID-1: BAT0 charge: 61.6 Wh (96.6%) condition: 63.8/76.0 Wh (84.0%) volts: 15.2
min: 15.2 model: ASUSTeK ASUS Battery type: Li-ion serial: N/A status: Not charging
cycles: 12
CPU: Info: Quad Core model: Intel Core i7-7700HQ bits: 64 type: MT MCP arch: Kaby Lake
family: 6 model-id: 9E (158) stepping: 9 microcode: EA cache: L2: 6 MiB
flags: avx avx2 lm nx pae sse sse2 sse3 sse4_1 sse4_2 ssse3 vmx bogomips: 44798
Speed: 2630 MHz min/max: 800/2801 MHz boost: enabled Core speeds (MHz): 1: 2630
2: 1913 3: 1679 4: 1556 5: 1194 6: 1193 7: 1357 8: 1524
Vulnerabilities: Type: itlb_multihit status: KVM: VMX disabled
Type: l1tf mitigation: PTE Inversion
Type: mds mitigation: Clear CPU buffers; SMT vulnerable
Type: meltdown mitigation: PTI
Type: spec_store_bypass
mitigation: Speculative Store Bypass disabled via prctl and seccomp
Type: spectre_v1 mitigation: usercopy/swapgs barriers and __user pointer sanitization
Type: spectre_v2 mitigation: Full generic retpoline, IBPB: conditional, IBRS_FW,
STIBP: conditional, RSB filling
Type: srbds mitigation: Microcode
Type: tsx_async_abort status: Not affected
Graphics: Device-1: NVIDIA GP104BM [GeForce GTX 1070 Mobile] vendor: ASUSTeK driver: nvidia
v: 460.73.01 bus-ID: 01:00.0 chip-ID: 10de:1be1 class-ID: 0300
Device-2: Realtek type: USB driver: uvcvideo bus-ID: 1-4:2 chip-ID: 0bda:57fa
class-ID: 0e02 serial: <filter>
Display: x11 server: X.Org 1.20.10 driver: loaded: nvidia
note: n/a (using device driver) display-ID: :0.0 screens: 1
Screen-1: 0 s-res: 1920x1080 s-dpi: 128 s-size: 381x211mm (15.0x8.3")
s-diag: 436mm (17.1")
Monitor-1: DP-4 res: 1920x1080 hz: 75 dpi: 128 size: 382x215mm (15.0x8.5")
diag: 438mm (17.3")
OpenGL: renderer: GeForce GTX 1070/PCIe/SSE2 v: 4.6.0 NVIDIA 460.73.01
direct render: Yes
Audio: Device-1: Intel CM238 HD Audio vendor: ASUSTeK driver: snd_hda_intel v: kernel
bus-ID: 00:1f.3 chip-ID: 8086:a171 class-ID: 0403
Device-2: NVIDIA GP104 High Definition Audio vendor: ASUSTeK driver: snd_hda_intel
v: kernel bus-ID: 01:00.1 chip-ID: 10de:10f0 class-ID: 0403
Sound Server-1: ALSA v: k5.12.0-19.4-liquorix-amd64 running: yes
Sound Server-2: PulseAudio v: 13.0 running: yes
Network: Device-1: Intel Wireless 8260 driver: iwlwifi v: kernel modules: wl port: e000
bus-ID: 03:00.0 chip-ID: 8086:24f3 class-ID: 0280
IF: wlan0 state: down mac: <filter>
Device-2: Realtek RTL8111/8168/8411 PCI Express Gigabit Ethernet vendor: ASUSTeK
driver: r8169 v: kernel port: d000 bus-ID: 04:00.0 chip-ID: 10ec:8168 class-ID: 0200
IF: eth0 state: up speed: 1000 Mbps duplex: full mac: <filter>
Device-3: Realtek RTL8152 Fast Ethernet Adapter type: USB driver: r8152
bus-ID: 3-1.1:3 chip-ID: 0bda:8152 class-ID: 0000 serial: <filter>
IF: eth1 state: down mac: <filter>
IF-ID-1: docker0 state: down mac: <filter>
Bluetooth: Device-1: Intel type: USB driver: N/A bus-ID: 1-9:5 chip-ID: 8087:0a2b class-ID: e001
Drives: Local Storage: total: 1.34 TiB used: 677.17 GiB (49.4%)
SMART Message: Unable to run smartctl. Root privileges required.
ID-1: /dev/sda maj-min: 8:0 vendor: Micron model: 1100 MTFDDAV512TBN size: 476.94 GiB
block-size: physical: 512 B logical: 512 B speed: 6.0 Gb/s type: SSD serial: <filter>
rev: A033 scheme: GPT
ID-2: /dev/sdb maj-min: 8:16 vendor: Intel model: SSDSC2KG960G8 size: 894.25 GiB
block-size: physical: 4096 B logical: 512 B speed: 6.0 Gb/s type: SSD
serial: <filter> rev: 0132 scheme: GPT
Partition: ID-1: / raw-size: 75.69 GiB size: 74.01 GiB (97.77%) used: 18.01 GiB (24.3%) fs: ext4
dev: /dev/sda5 maj-min: 8:5
ID-2: /boot/efi raw-size: 1004 MiB size: 1002 MiB (99.80%) used: 28.7 MiB (2.9%)
fs: vfat dev: /dev/sda1 maj-min: 8:1
Swap: Alert: No swap data was found.
Sensors: System Temperatures: cpu: 56.0 C mobo: N/A gpu: nvidia temp: 48 C
Fan Speeds (RPM): cpu: 2700
Repos: Packages: note: see --pkg apt: 2439 lib: 1262 flatpak: 0
No active apt repos in: /etc/apt/sources.list
Active apt repos in: /etc/apt/sources.list.d/debian-stable-updates.list
1: deb http://deb.debian.org/debian/ buster-updates main contrib non-free
Active apt repos in: /etc/apt/sources.list.d/debian.list
1: deb http://deb.debian.org/debian/ buster main contrib non-free
2: deb http://deb.debian.org/debian-security/ buster/updates main contrib non-free
Active apt repos in: /etc/apt/sources.list.d/google-chrome.list
1: deb [arch=amd64] http://dl.google.com/linux/chrome/deb/ stable main
No active apt repos in: /etc/apt/sources.list.d/home:smplayerdev.list
No active apt repos in: /etc/apt/sources.list.d/liquorix.list
Active apt repos in: /etc/apt/sources.list.d/mx.list
1: deb http://mxrepo.com/mx/repo/ buster main non-free
2: deb http://mxrepo.com/mx/repo/ buster ahs
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
Active apt repos in: /etc/apt/sources.list.d/vivaldi.list
1: deb http://repo.vivaldi.com/stable/deb/ stable main
No active apt repos in: /etc/apt/sources.list.d/xanmod-kernel.list
Info: Processes: 243 Uptime: 5h 23m wakeups: 2 Memory: 31.32 GiB used: 2.01 GiB (6.4%)
Init: SysVinit v: 2.96 runlevel: 5 default: 5 tool: systemctl Compilers: gcc: 8.3.0
alt: 8 Shell: quick-system-in default: Bash v: 5.0.3 running-in: quick-system-in
inxi: 3.3.06
[/code]Liquorix kernel 5.13 series it doesn't work for me with nvidia
Ps:I mention the Liquorix kernel 5.13 series, installed with smxi with nvidia beta driver NVIDIA worked well
Re: MX 19 Repository: The Liquorix Kernel Thread
Posted: Thu Sep 02, 2021 12:41 pm
by fossean
tequila wrote: Sun Aug 15, 2021 10:52 am
Ps:I mention the Liquorix kernel 5.13 series, installed with smxi with nvidia beta driver NVIDIA worked well
Thanks for the heads up on smxi. I was unaware of this tool; it enabled installation of nvidia 470.63.01 (latest stable) which is running well with Liquorix 5.13. Nvidia 460 from backports was hanging at boot.
Re: MX 19 Repository: The Liquorix Kernel Thread
Posted: Thu Sep 02, 2021 2:52 pm
by Stevo
MX Nvidia (ddm-mx) has a "-b" flag on the command line that allows for the installation of the debian backports version, which is running ahead of our test repo version at the moment.
Debian still has the 5.13 kernel in Experimental, and even their latest Nvida drivers only support 5.10 or older.
Re: MX 19 Repository: The Liquorix Kernel Thread
Posted: Wed Apr 13, 2022 5:23 pm
by Stevo
Well...it's been a while since I updated this, but the 5.17-5 Liquorix kernel is now available. I also sent up patched realtek 8821ce and broadcom-sta dkms packages that are patched to build on it. Virtualbox 6.1.32 and Nvidia 510.47.03, already in our repos, successfully build on it.
Re: MX 19 Repository: The Liquorix Kernel Thread
Posted: Wed Apr 13, 2022 9:15 pm
by mmikeinsantarosa
my laptop likes the new liquorix kernel with broadcom-sta-dkms-6.30.223.271-17 and Virtualbox 6.1.32. And my mobile card is picky.
Re: MX 19 Repository: The Liquorix Kernel Thread
Posted: Sun Nov 19, 2023 5:39 am
by Snod Blatter
I know there probably aren't many of us running MX19 AHS these days but I'd like to point out that any Liquorix kernel from 6.4 onwards won't install because "Depends: libtraceevent1 (>= 1:1.3.0) but 1:1.1.2-1~mx19+1 is to be installed".
Could we get a newer libtraceevent1? Otherwise there's no point putting these kernels in the MX19 AHS repo. There is a 5.8.14-1~mx19+2 version in MX Test but I really don't know what version that actually is and MXPI seems to think the normal 1:1.1.2-1~mx19+1 version is newer anyway.
Cheers!
Re: MX 19 Repository: The Liquorix Kernel Thread
Posted: Sun Nov 19, 2023 1:31 pm
by Stevo
Snod Blatter wrote: Sun Nov 19, 2023 5:39 am
I know there probably aren't many of us running MX19 AHS these days but I'd like to point out that any Liquorix kernel from 6.4 onwards won't install because "Depends: libtraceevent1 (>= 1:1.3.0) but 1:1.1.2-1~mx19+1 is to be installed".
Could we get a newer libtraceevent1? Otherwise there's no point putting these kernels in the MX19 AHS repo. There is a 5.8.14-1~mx19+2 version in MX Test but I really don't know what version that actually is and MXPI seems to think the normal 1:1.1.2-1~mx19+1 version is newer anyway.
Cheers!
Whoops, that's my bad--it picked up a newer MX 21 set of packages that the 6.5 Debian kernel backports require for MX 21, and those won't build on MX 19 at all.
There's one last 6.5-17 Liquorix kernel I can rebuild for AHS, then we are testing the 6.6-1 Liquorix builds, though I only have done MX 23 for ahs-staging right now...running it at present:
Code: Select all
$ uname -a
Linux dellmx23 6.6.1-1-liquorix-amd64 #1 ZEN SMP PREEMPT liquorix 6.6-1~mx23ahs (2023-11-19) x86_64 GNU/Linux
With patched nvidia-driver for 6.6:
Code: Select all
$ nvidia-run-mx inxi -G
Graphics:
Device-1: NVIDIA GA107M [GeForce RTX 3050 Ti Mobile] driver: nvidia
v: 525.125.06
Device-2: AMD Cezanne [Radeon Vega Series / Radeon Mobile Series]
driver: amdgpu v: kernel
Device-3: Microdia Integrated_Webcam_HD type: USB driver: uvcvideo
Display: x11 server: X.Org v: 1.21.1.7 with: Xwayland v: 22.1.9 driver: X:
loaded: amdgpu,nvidia dri: radeonsi gpu: amdgpu resolution: 1920x1080~120Hz
API: OpenGL v: 4.6.0 NVIDIA 525.125.06 renderer: NVIDIA GeForce RTX 3050
Re: MX 19 Repository: The Liquorix Kernel Thread
Posted: Mon Nov 20, 2023 2:28 pm
by Snod Blatter
Liquorix 6.5-17 successfully installed, thanks Stevo!
Re: MX 19 Repository: The Liquorix Kernel Thread
Posted: Mon Nov 20, 2023 7:12 pm
by Stevo
Yes, that will be the final 6.5 Liquorix. We currently have Liquorix 6.6 in ahs-staging until we ensure our extra Realtek and broadcom-sta dkms drivers work with it.
Re: MX 19 Repository: The Liquorix Kernel Thread
Posted: Mon Nov 20, 2023 7:15 pm
by Stevo
Just tested broadcom-sta-dkms, and it builds successfully on 6.6.
