Hm I'm sorry to hear that. I have no clue what would cause that considering many people including me haven't had any issues. It is still a relatively new kernel in comparison to say Zen kernel so likely still bugs to be worked out. Do you by chance have any strange configurations that aren't normal that could cause it or an unusual hardware setup? Are you on dragonised KDE and able to get logs at all? It's possible there was an issue with your hardware like I had early on in the kernel development with the llvm variant in regards to audio and virtual machines not working. Been fine for a long time for me now though. Good luck!
No, I am using sway
I don’t look too much at hardware configurations (I let hardware configurations to be at it’s default , just do somewhat theaming, that also not too much )
My hardware is also descent not any different thing in it , It is almost 4 years old laptop.
Linux cacULE is also a kernel provided by cachyos and that is not causing any problem , I think I should stick to it , for now.
Installing that gives me
warning: ckbcomp: local (1.207-1) is newer than cachyos (1.205-1)
warning: downgrade: local (11.0.0-1) is newer than cachyos (10.1.0-1)
warning: harfbuzz: local (3.3.1-1) is newer than cachyos-v3 (3.2.0-1.1)
warning: harfbuzz-icu: local (3.3.1-1) is newer than cachyos-v3 (3.2.0-1.1)
warning: inxi: local (3.3.12.1-1) is newer than cachyos (3.3.07.1-1)
warning: lcms2: local (2.13-2) is newer than cachyos-v3 (2.13-1.1)
warning: lib32-harfbuzz: local (3.3.1-1) is newer than cachyos-v3 (3.2.0-1.1)
warning: lib32-libcups: local (2.4.1-1) is newer than cachyos-v3 (2.4.0-1.1)
warning: lib32-nvidia-utils: local (510.47.03-1) is newer than cachyos-v3 (495.46-1.1)
warning: lib32-opencl-nvidia: local (510.47.03-1) is newer than cachyos-v3 (495.46-1.1)
warning: libpamac-aur: local (11.2.0-5) is newer than cachyos (11.2.0-0)
warning: libxnvctrl: local (510.47.03-1) is newer than cachyos-v3 (495.46-2.1)
warning: nerd-fonts-fantasque-sans-mono: local (2.1.0-3) is newer than cachyos (2.1.0-1)
warning: nvidia-dkms: local (510.47.03-3) is newer than cachyos-v3 (495.46-2.1)
warning: nvidia-settings: local (510.47.03-1) is newer than cachyos-v3 (495.46-2.1)
warning: nvidia-utils: local (510.47.03-3) is newer than cachyos-v3 (495.46-2.1)
warning: opencl-nvidia: local (510.47.03-3) is newer than cachyos-v3 (495.46-2.1)
warning: pamac-aur: local (10.3.0-4) is newer than cachyos (10.3.0-1)
warning: plymouth-git: local (0.9.5.r110.g5b91b9e-1) is newer than cachyos (0.9.5.r106.gbad6d41-1)
warning: python-pyqt5-sip: local (12.9.1-1) is newer than cachyos-v3 (12.9.0-3.1)
warning: re2: local (1:20220201-1) is newer than cachyos-v3 (1:20211101-1.1)
warning: rest: local (0.8.1+r4+ge5ee6ef-1) is newer than cachyos-v3 (0.8.1-3.1)
warning: thunderbird: local (91.5.1-1) is newer than cachyos-v3 (91.5.0-2.1)
warning: wine: local (7.0-1) is newer than cachyos-v3 (7.0rc5-1.1)
Running garuda-update wants to update/replace 1068 packages..... doesn't look good to me. Could be a nuke.
Well the repo modifies the pacman.conf and puts cachyos above garuda which means it has priority when updating the system. So because of that and the fact you weren't using cachyos repo before, it may ask to rebuild packages from the cachyos repo as opposed to what you currently have compiled through the Garuda/Arch repos. As cachyos generally optimises these packages better with gcc v3 and CPU auto detection among other features, I would recommend to select yes to installing those packages and then you will be on a more optimised KDE. It definitely felt smoother after I did this and rebooted. The warnings are always going to be there though of course because Arch may have newer builds for some packages while cachyos has priority meaning it installs from there even if it's slightly older. I'm happy with how my system is now though after installing the repo, kernel and allowing packages to be recompiled through the cachyos repo.
1 Like
Those issues come mostly if there any issue if building the repo which we try to fix them fast as possible. The last weeks the complete Repo is completley stable and runs like a charm.
Its not just the KDE packages. Sadly we cant optimize the gcc in v3 which result in different DKMS errors, but we provide a bolted llvm toolchain and of course GCC-GIT and LLVM-Git and my other packages.
1 Like