You are not logged in.
Consult /var/lib/dkms/nvidia/460.39/build/make.log for more information.
this file does not exist
EDIT:
Anyway... problem disappeared with 5.10.14-1-ck. Everything is fine now.
Last edited by sknd (2021-02-09 19:20:44)
Jaki koniec świata.Ziemia to nie cały świat ,a tylko mały Wąchock we wszechświecie.
Offline
Is it possible to apply ck patches to Intel clear Linux?
Offline
How was it useless? Do you know what a PKGBUILD is? Do you know what comments are? Can you read? Where exactly does the problem lie?
It didn't work, yes, yes, yes, see first answer.
G F Y
Offline
Your "first answer" was that the linked PKGBUILD is useless. If you can answer yes to all of these other questions, then you can surely point out where your problem lies.
Didn't work is not an error message if you get an error during the build you might want to open up your own thread with the exact details of where and how it fails.
Last edited by V1del (2021-02-26 18:48:31)
Offline
Your "first answer" was that the linked PKGBUILD is useless. If you caun answer yes to all of these other questions, then you can surely point out where your problem lies.
Didn't work is not an error message if you get an error during the build you might want to open up your own thread with the exact details of where and how it fails.
Thanks
G F Y
Offline
Haven't been able to update via the repo for several days now. Is this a repo issue or something on my end?
"error: failed retrieving file 'repo-ck.db' from repo-ck.com : Resolving timed out after 10000 milliseconds
error: failed to update repo-ck (download library error)
Hey, be nice...I'm new at this!
Offline
That's odd, it works for me.
CPU-optimized Linux-ck packages @ Repo-ck • AUR packages • Zsh and other configs
Offline
I just added the aviallon mirror which seems to have resolved the issue. No idea why I can't connect to your repo.
Hey, be nice...I'm new at this!
Offline
I'm pretty noob at this stuff, but none of my docker containers start properly when booted into 5.11.11-2-ck-zen, but they're all fine when booting into the 5.11.11-arch1-1 Linux kernel.
"$ docker restart portainer
Error response from daemon: Cannot restart container portainer: OCI runtime create failed: container_linux.go:367: starting container process caused: process_linux.go:495: container init caused: process_linux.go:458: setting cgroup config for procHooks process caused: can't load program: invalid argument: unknown
I don't know if you speak docker or not...
Hey, be nice...I'm new at this!
Offline
@wilberfan I get the same error with Docker when running linux-ck-skylake, but I have no problem with the standard Arch kernel; see here for more details. So it seems that there is an issue with Docker and linux-ck at the moment.
Offline
@snack Updated linux-ck just now to v5.11.12-arch1-1, but still having the docker issue.
Last edited by wilberfan (2021-04-09 23:42:41)
Hey, be nice...I'm new at this!
Offline
@wilberfan I'm sorry but I'm not an expert of docker nor of the CK patchset. I was simply blindly following the Mattermost setup instructions, and decided to give a shot with the default kernel when I saw your post reporting the same error on a different workload when using the CK kernel. But I have no clue about why the default kernel worked for me and not for you.
Offline
@snack No expertise on your part assumed--I just wanted to let you know that the .12 -ck kernel upgrade had no effect on the docker issue we're both experiencing. I, too, have almost zero docker and kernel expertise.
Hey, be nice...I'm new at this!
Offline