MX 19 Repository: The Liquorix Kernel Thread

User Package Requests for MX-19
Message
Author
User avatar
manyroads
Posts: 2657
Joined: Sat Jun 30, 2018 6:33 pm

Re: MX 19 Repository: The Liquorix Kernel Thread

#11 Post 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.
Pax vobiscum,
Mark Rabideau - ManyRoads Genealogy -or- eirenicon llc. (geeky stuff)
i3wm, bspwm, hlwm, dwm, spectrwm ~ Linux #449130
"For every complex problem there is an answer that is clear, simple, and wrong." -- H. L. Mencken

User avatar
oops
Posts: 1933
Joined: Tue Apr 10, 2018 5:07 pm

Re: MX 19 Repository: The Liquorix Kernel Thread

#12 Post by oops »

cinclus wrote: Wed Nov 06, 2019 3:47 pm Yes it is.
https://techpatterns.com/forums/about2734.html
Thanks for the information Cinclus.
Pour les nouveaux utilisateurs: Alt+F1 pour le manuel, ou FAQS, MX MANUEL, et Conseils Debian - Info. système “quick-system-info-mx” (QSI) ... Ici: System: MX-19_x64 & antiX19_x32

User avatar
Stevo
Developer
Posts: 14643
Joined: Fri Dec 15, 2006 7:07 pm

Re: MX 19 Repository: The Liquorix Kernel Thread

#13 Post 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.

User avatar
jdhedden
Posts: 19
Joined: Mon Dec 23, 2019 12:59 pm

Re: MX 19 Repository: The Liquorix Kernel Thread

#14 Post 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.

User avatar
jdhedden
Posts: 19
Joined: Mon Dec 23, 2019 12:59 pm

Re: MX 19 Repository: The Liquorix Kernel Thread

#15 Post 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?

User avatar
jdhedden
Posts: 19
Joined: Mon Dec 23, 2019 12:59 pm

Re: MX 19 Repository: The Liquorix Kernel Thread

#16 Post 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?

User avatar
Stevo
Developer
Posts: 14643
Joined: Fri Dec 15, 2006 7:07 pm

Re: MX 19 Repository: The Liquorix Kernel Thread

#17 Post 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.
Last edited by Stevo on Tue Feb 11, 2020 3:19 pm, edited 1 time in total.

User avatar
Stevo
Developer
Posts: 14643
Joined: Fri Dec 15, 2006 7:07 pm

Re: MX 19 Repository: The Liquorix Kernel Thread

#18 Post 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...

User avatar
KoO
Posts: 491
Joined: Fri Feb 10, 2017 12:21 am

Re: MX 19 Repository: The Liquorix Kernel Thread

#19 Post 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.
jdhedden wrote: Mon Feb 10, 2020 10:10 pm 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?
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.
Main : MX 19.1-AHS (i3) 5.4.13-1~mx19+1, Asus B450-i AMD 5 3600 , 32gb Hyper-X 3200 , GTX970 . :linuxlove:
Lenovo T430 : Debian10 antiX17 (i3) , 4.20.12 , i5 , 12gb .
Lenovo X220 : Test Machine (ATM)

User avatar
Stevo
Developer
Posts: 14643
Joined: Fri Dec 15, 2006 7:07 pm

Re: MX 19 Repository: The Liquorix Kernel Thread

#20 Post 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.

Post Reply

Return to “Package Requests/Status - MX-19”