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.
DELL Inspiron 14-3452, 32GB emmc, 4 GB RAM
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
DELL Inspiron 14-3452, 32GB emmc, 4 GB RAM
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
@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.
I have been experiencing the same problem with docker since a couple of weeks back (tops) with the ck kernel and I can't say precisely when it started but it's something I'm not experiencing with the default kernel on Arch. I have a Postgres container I use almost all the time and, after some update, I started having this issue:
Error response from daemon: 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
Which can easily be replicated with a simple "hello-world":
$ docker -D -l debug run --rm hello-world
DEBU[0000] [hijack] End of stdout
docker: Error response from daemon: 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 remember some time ago there was some problems with cgroups and the ck patchset while using docker, I even wrote down something on the Arch wiki but since it was not a problem anymore, makes sense to be removed. Actually, going through the history of that page, that happened on kernel 4.20 on June, 2019. It was quite a while ago and I don't believe they are related. I tried looking on journalctl but couldn't find anything more on this, as the error message is the same.
I'm running kernel 5.11.13-2-ck with preset 12 (ZEN2) applied. I'll try to compile the kernel on the default preset and check some configs in my BIOS that sometimes creates some odd behaviors on Linux (and update this message with my findings).
UPDATE
Using the generic preset (for linux-ck) produced the same result on docker, whereas the BIOS setting I usually change on my workstation (disable CSTATES) just made my Linux crash randomly (I don't really know why, I think it's related to my specific hardware), but nothing different on docker. Oh well ...
Last edited by vltr (2021-04-13 13:52:54)
"For a successful technology, reality must take precedence over public relations, for Nature cannot be fooled." -- Richard P. Feynman
Offline
Is linux-ck-haswell dropped from repo-ck ?
Offline
No, haswell should be there. Rsync timed out on 5.11.16 and didn't recover. 5.12.0 is there now.
CPU-optimized Linux-ck packages @ Repo-ck • AUR packages • Zsh and other configs
Offline
Since the upgrade to 5.12 I get a black screen at boot instead of the graphical login window, with Intel VGA. No problem with 5.11. Is anybody else getting the same error?
I guess i'ts not CK fault but rather a bug in the new kernel, but I ask here anyway since Arch kernel is still at previous version.
Offline
As a control, you can test the Arch kernel by pulling it out of [testing].
CPU-optimized Linux-ck packages @ Repo-ck • AUR packages • Zsh and other configs
Offline
Not a CK issue. I waited for 5.12.1 to hit the core repo. Intel graphics here and screen is flashing blank approx every second, from bios thru desktop. Craziest "stable" kernel bug to get through to one of my systems in about a decade.
Thank goodness for the LTS kernel! Now, to find the upstream kernel bug...
Offline
@tekstryder The same here with 5.12.1 from [core], except for the fact that my laptop panel is totally blank and that the external monitor attached through HDMI works fine. As I suspected this is not a CK issue. I'm currently on LTS (God bless LTS...) waiting for a fix, I'll add a bug report later although I cannot find anything suspect in the logs.
Offline
Is it possible to compile linux-ck kernel with modprobe on a machine with 512Mb RAM? zRAM with 96Mb still not help.
It always stuck on:
ZSTD22 arch/x86/boot/compressed/vmlinux.bin.zst
zstd: error 11 : Allocation error : not enough memory
make[2]: *** [arch/x86/boot/compressed/Makefile:134: arch/x86/boot/compressed/vmlinux.bin.zst] Error 11
make[2]: *** Deleting file 'arch/x86/boot/compressed/vmlinux.bin.zst'
make[1]: *** [arch/x86/boot/Makefile:115: arch/x86/boot/compressed/vmlinux] Error 2
Offline
Version 5.12.4-1 fixes the blank laptop panel issue for me.
Offline
Had to downgrade to 5.12.1-1-ck-nehalem because linux-ck-nehalem-5.12.4-1 freezes the system at boot when "Loading initial ramdisk".
Offline
Had to downgrade to 5.12.1-1-ck-nehalem because linux-ck-nehalem-5.12.4-1 freezes the system at boot when "Loading initial ramdisk".
I'm seeing the same thing with linux-ck (the generic version, as my core2 is no longer supported). I've tried playing with /etc/mkinitcpio.conf, comparing packages with lsinitcpio etcetera, all to no avail. For me linux-ck-5.12.3-1 is the last version I can boot. At first I thought this was not ck related, but now I'm starting to think it is, even though I've not been able to pinpoint what's going on. FWIW, linux, linux-zen and linux-tkg-muqss all boot just fine.
Offline
GAZ082 wrote:Had to downgrade to 5.12.1-1-ck-nehalem because linux-ck-nehalem-5.12.4-1 freezes the system at boot when "Loading initial ramdisk".
I'm seeing the same thing with linux-ck (the generic version, as my core2 is no longer supported). I've tried playing with /etc/mkinitcpio.conf, comparing packages with lsinitcpio etcetera, all to no avail. For me linux-ck-5.12.3-1 is the last version I can boot. At first I thought this was not ck related, but now I'm starting to think it is, even though I've not been able to pinpoint what's going on. FWIW, linux, linux-zen and linux-tkg-muqss all boot just fine.
Linux-ck bobcat is gone and now generic linux-ck is screwed up. You can't win.
DELL Inspiron 14-3452, 32GB emmc, 4 GB RAM
Offline