MX 19 Repository: The Liquorix Kernel Thread

[imschmeg]

@Stevo
You mean Virtualbox 6.1.6, right?

[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

Code: Select all

apt-cache policy virtualbox

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

[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.

[mmikeinsantarosa]

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.

[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 

[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.

[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.

[fossean]

The latest nvidia drivers in the test repo (450.66) are now working working correctly with liquorix 5.8.0-7.1

[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 

[Stevo]

Is that 5.9 kernel from our test repo? Hopefully, the new maintainer will announce at least major version bumps here...hint hint