Kimiblock Moe
Kimiblock Moe
> Arch下请尝试添加archlinuxcn的aur后通过[Stable Release](https://aur.archlinux.org/packages/clash-nyanpasu) / [Binary Package](https://aur.archlinux.org/packages/clash-nyanpasu-bin)安装 AUR 是用户软件打包脚本的聚集地, 不是仓库. Nyanpasu 也没有进入 CN 仓库.
Does Fractal specify to use GPL 3 only? If I missed something lmk
``` jsonschema.exceptions.ValidationError: 'gnome-unstable' is not one of ['extra-x86_64', 'archlinuxcn-x86_64', 'multilib', 'multilib-archlinuxcn', 'extra-aarch64'] ``` Weird...
> lilac doesn't support gnome-unstable。 Okay, will check if Fractal builds with gtk4 from the repos
Builds perfectly fine on top of `gtk4 1:4.14.2-1` and `libadwaita 1:1.5.0-1`, prefix `gnome-unstable` has been removed. -- Sincerely, Kimiblock
From what I've tested, the specific branch doesn't work on my hybrid GPU system. The PKGBUILD is listed as follows: ``` pkgname=resources pkgver=1.7.1 pkgrel=1 pkgdesc='Monitor for system resources and processes'...
I did a little bit of experiment and it turns out that `NVreg_RegistryDwords="RMForcePstate=0"` was the root cause. But according to [this documentation](https://docs.nvidia.com/gameworks/content/gameworkslibrary/coresdk/nvapi/group__gpupstate.html), P0 should be "best performance", right?
That’s true, but open drivers currently have stuttering issues after idle. I’m looking for ways to mitigate it.
I recently saw this happening. The solution is to force a device list refresh on Synapse: ``` INSERT INTO device_lists_remote_resync VALUES ('@mxid:example.org', (EXTRACT(epoch FROM NOW()) * 1000)::BIGINT); ```
Hmmm... On my machine htop shows fotema barely uses 2% of a CPU core, the progress bar never moved for like half an hour