Hello there, i’m on the process of installing cachyos on all my devices, and i have encountered of lot of issues since yesterday :
Normal install doesn’t start at all (stay on SYSTEMD-BOOT or GRUB), when start calamares_online.sh there seems to be a dependency hell behind (1st python312, then icu… updating all depandencies doesn’t seem to be enough), and it’s the case on 3 different devices, with different version of the iso (the last one and the april one). So i took an EOS iso and added cachyos repos, better than nothing.
Install on the ROG ALLY of the handled edition seems broken when using encrypted install (i have the projet to tpm unlock after, it works very well on all my other devices).
That’s all, thanks again for that amazing distro !
I dont know, why you would need to pull in python312. This is not required by anything of us.
Same as the ICU update, this has been rolled out around 1 month ago.
It would be important to share logs, so that we can identify them. The installer does upload them for you and provides a link.
Normal install doesn’t start at all (stay on SYSTEMD-BOOT or GRUB), when start calamares_online.sh there seems to be a dependency hell behind
oh, that sounds like youre not using the latest ISO. The Calamares online script does fetch the latest calamares from our repository, and this is handled via 2 versions. One for the newer release and one for an older one, which then gets deprecated after around 15 days, when we start the testing period for the new release.
Hey, thanks for your answers, i don’t why too, the calamares online doesn’t start at all and doesn’t crash (it stay on the 1st window after selecting the bootloader option), and when i start calamares_online.sh it just show some lib issues (at 1st python, after pacman -Sy python others…).
I will try this week but it seems like it can’t work on any of my systems.
And for the ROG Ally i will try later too with the pastin code for logs, but really seems linked to the luks option.
To which script does the “launch installer” button point? I tried to install cachyos on a 2GB ram system, before I changed the welcom.conf in /etc/calamares/modules, but no it seems the file gets overwritten. Thanks to your explanation, It’s clear to me now that calamares get’s reinstalled and the welcome_online.conf is replaced. If I could change the script to not reinstall calamares, I could proceed the installation on my 2GB ram system.
Anyways, you can mitigate this with changing the config, as you already noted.
We are all time fetching the latest calamares to the repository, so we can send fixes “ondemand” to the user, in case at the release was an issue.
Please run following on the latest May ISO:
sudo pacman -Sy cachyos-calamares-qt6-next-grub
Modify the welcome.conf
sudo -E dbus-launch calamares -D6
Hi there, I have an issue that the packages section of the installer doesn’t show anything. It shows just blank. However when I continue, the final installation fails. Who knows why and how can I solve it?
I’ve been able to install. However now I can’t boot into the cachyos because the refund boot manager shows a white blank space. I installed windows 11, then installed cachyos alongside windows 11 on the same SSD. Now refind can’t recognise any of the OS. I’ve attached a photo of the refind page
Did you disable secure boot? Because if you have secure boot enabled than it will prevent you from booting CachyOS. As to why Windows 11 is not showing up, that is a question that needs to be answered as that should show up no matter what if the boot loader was configured correctly. Another thing that might be causing this is the fact that both windows 11 and systemd/refind require you to set the boot parameter on the esp partition (vfat32). you need at least one fat32 partition in order to create and use a vfat partition which supports esp. But if you reformat the esp partition with a new one, then you may have deleted your windows as the reformatting process, even if it is of the same type of partition as prior, it still wipes the data. I hate to say this but it is possible that the windows 11 boot image was deleted, thus meaning you have no method to access the operating system.
Thank you for your response. Grub is working fine however and I can still boot into my windows 11. I realised I have two esp, one for Windows which contains the windows boot manager. The partition space is 100mb. Then there’s another esp that contains the refind and grub bootloaders.
Also, I don’t have secure boot on. Secure boot is disabled.
