MX 17/18 Repository: The Liquorix Kernel Thread

[KoO]

Some thing Different..

Code: Select all

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

[Friedrich]

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

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

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

[Stevo]

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

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

[Friedrich]

We've now added the 5.1-1 (based on the 5.1.6 vanilla) Liquorix kernel

You chose not to add the headers as a dependency?

[Head_on_a_Stick]

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

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

[Stevo]

We've now added the 5.1-1 (based on the 5.1.6 vanilla) Liquorix kernel

You chose not to add the headers as a dependency?

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

[Stevo]

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

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

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

[Friedrich]

.. the MX Package Installer does automatically install the headers along with the kernel.

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

[Stevo]

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

Code: Select all

sudo apt update

Then check:

Code: Select all

apt policy linux-headers-5.1.0*

If not installed, run

Code: Select all

sudo m-a prepare 

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

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

[mmikeinsantarosa]

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