Skip to main content ↑ ↓
Topic: Is https://github.com/artix-linux/{packages,packages-galaxy} still current? (Read 1803 times) previous topic - next topic
0 Members and 1 Guest are viewing this topic.

Is https://github.com/artix-linux/{packages,packages-galaxy} still current?

https://github.com/artix-linux/{packages,packages-galaxy} seems to have been
archived, and a Google search also leads me to archived files.
https://github.com/artix-linux/documentation seems to say the sites are still
current, but the PKGBUILDS are out of date.
Can you please tell me where the current PKGBUILD sources are? Are you back on
Sourceforge? (I can build 4.17.12 from asp, but I'd have to download the entire
kernel source. Please don't tell me to install the prepackaged kernel, INTEL_MEI
and all).

Re: Is https://github.com/artix-linux/{packages,packages-galaxy} still current?

Reply #1 –
Hello,
Artix infrastructure was changed and moved to self-hosted gitea service.
https://gitea.artixlinux.org/

Each package is in its own repository and these repositories are "grouped"
together to form "packages" and "packages-galaxy" repositories.

Re: Is https://github.com/artix-linux/{packages,packages-galaxy} still current?

Reply #2 –
As far as MEI is concerned, I just make a module blacklist:

Code: [Select]
$ cat /etc/modprobe.d/blacklist.conf 
blacklist mei
blacklist mei_me
blacklist mei_wdt

Re: Is https://github.com/artix-linux/{packages,packages-galaxy} still current?

Reply #3 –
Thanks!
And I still have to download the entire source (hopefully only once). What
happened to patches? Are we no longer using the vanilla kernel, but a distro
version as in Ubuntu?

Edit:
https://www.kernel.org/category/site-news.html seems to be relevant here.

Re: Is https://github.com/artix-linux/{packages,packages-galaxy} still current?

Reply #4 –
(came across this topic while trying to compile an artix kernel :D )
The intel MEI kernel modules have nothing to do with the functioning or non-functioning of MEI

You either use

https://github.com/bol-van/me-disable/blob/master/mei-disable.c

or

https://github.com/corna/me_cleaner/

or whatever works for your bios/mobo, it's a pretty complex topic, and the ways to (try to) disable vary depending on hardware.

For me the first link seems to be working, as I have an unsupported mobo, but I had to change the device to mei0

static const char *DEV_NAME = "/dev/mei0";

It fails seconds after that (check dmesg), and it persists across soft reboots, if you do a full shut down - boot cycle, it needs re-executing.

Code: [Select]
[ 7966.779994] mei_me 0000:00:16.0: cl:host=01 me=32 fw disconnect request received
[ 7966.783322] mei_me 0000:00:16.0: FW not ready: resetting.
[ 7966.783352] mei_me 0000:00:16.0: unexpected reset: dev_state = ENABLED fw status = 90000255 84280106 00000020 00084000 00000000 00000000
[ 7968.905772] mei_me 0000:00:16.0: wait hw ready failed
[ 7968.905778] mei_me 0000:00:16.0: hw_start failed ret = -62
[ 7968.905806] mei_me 0000:00:16.0: unexpected reset: dev_state = RESETTING fw status = 90132054 34470006 00000020 00080000 00000000 00000000
[ 7968.905815] mei_me 0000:00:16.0: H_RST is set = 0x80000031
[ 7971.039116] mei_me 0000:00:16.0: wait hw ready failed
[ 7971.039123] mei_me 0000:00:16.0: hw_start failed ret = -62
[ 7971.039151] mei_me 0000:00:16.0: unexpected reset: dev_state = RESETTING fw status = 90132054 34470006 00000020 00080000 00000000 00000000
[ 7971.039159] mei_me 0000:00:16.0: H_RST is set = 0x80000031
[ 7973.172443] mei_me 0000:00:16.0: wait hw ready failed
[ 7973.172450] mei_me 0000:00:16.0: hw_start failed ret = -62
[ 7973.172477] mei_me 0000:00:16.0: unexpected reset: dev_state = RESETTING fw status = 90132054 34470006 00000020 00080000 00000000 00000000
[ 7973.172482] mei_me 0000:00:16.0: reset: reached maximal consecutive resets: disabling the device
[ 7973.172485] mei_me 0000:00:16.0: device disabled = -19