I do believe this may be one for the record books. I recently upgraded my system to accommodate a new ssd. I run three completely separate OS's each with their own ssd in a single tower. My priority boot was Garuda Linux and I edited the Garuda GRUB menu to recognize Windows 10 and Kali linux so that I could launch any of the othe OS's from there. Two nights ago, I updated the Bios on my ASUS Gaming TUF X570 Plus (WIFI) motherboard to version 4403 released in April of this year. Right after that, my drives were no longer recognizable as bootable devices. No problem, I have both ISO's and full backups for everything.
Windows 10 Pro installed easily on the new ssd and I was also able to easily restore all of my files and settings. Kali and Garuda were very problematic. They would not install no matter what I did with the BIOS. I turned off safe boot, disabled fast boot, made sure I had both UEFI and Legacy OPROM boot options available and enabled CSM compatibility. Nothing worked. Finally, I downloaded Balena etcher to windows and flashed ISO's of Garuda and Kali there instead of using my laptop (which also runs Garuda as the sole OS). After creating the bootable media in Windows, Kali installed without a hitch. It is now alive and well on its ssd.
I tried the same thing with Garuda and I successfully passed through GRUB and right into the live OS environment where I attempted to initiate the install with the "Install Garuda" icon on the desktop. I clicked on it and nothing happened. I double-clicked (just in case) and still nothing happened. I went to the Garuda Welcome window and clicked the "Install Garuda" button there. The window flashed and nothing happened. I clicked again. Still nothing. I repeated this pattern at least three times. I re-flashed the ISO and booted into the Live environment. I have changed up the bios settings and even tried disconnecting the other drives from the motherboard before installing but nothing has worked.
The live environment is fully functional; terminal access, wifi, partition manager, etc. But for some reason, the install action just won't launch. Garuda is the only OS affected. Just as a test, I initiated an install of Ubuntu 22.04 LTS. I went along just fine until I aborted it and I assume it would have installed just fine. I have combed all of the available logs in the live environment including the boot log and could not find anything that would explain the failure to launch. I even tried initiating the install and then re-opened the logs to see if there were any changes.
Has anyone out there experienced this? I am stumped. Any insight or advice would be very much appreciated.
You are probably right, but what if the MB only has a 2 GB RAM memory?
Then calamares also refuses to install
And because we don’t want to guess around here or ask for everything individually, we would always like to have the garuda-inxi.
╭─garuda@garuda in ~ as 🧙
╰─λ pkexec calamares
/usr/bin/calamares: error while loading shared libraries: libboost_python310.so.1.79.0: cannot open shared object file: No such file or directory
McFly: Importing shell history for the first time. This may take a minute or two...done.
~~~x
Trying to install on an NVME SSD, AMD graphics card and Ryzen 5 6 core CPU. Tried to install with Ventoy after disabling CSM and still same result. Please see out put from pkexec calamares. Same output from sudo -E calamares -d.
Thanks for the tutorial. the pkexec calamares query returned information indicating that clamares is not in the live environment and therefore cannot be executed. Is calamares the primary installer used in Garuda ISO's?
Update. I have determined that the problem is with the ISO; specifically with the Calamares installer. My Bios settings are fine as well as the target ssd. I just downloaded a newer release and the same result. There appears to be a conflict between the function call for libboost_python310.so.1.79.0 and what is actually in the /usr/lib/ folder. All I found was libboost_python310.so.1.80.0. If the code in calamares is trying to pull .79 instead of .80, then this would explain the error in pkexec. Any ideas on how to get the installer to point to what is most likely a newer version of libboost?
Just try a different ISO. Where did you get this? There isn’t even a 220921 on the website right now. I just checked the main download page and it is 220909.
What is the exact name of the ISO and where did you download it from?
Go to https://start.garuda.linux.org. Click on "Iso Builds" under our services. It will take you to a FOSS Host page with all the latest distros. Dragonized version is there built on 220924.
I can confirm this issue exists on garuda-dr460nized-linux-zen-220924.iso. It’s just as OP described: “Install Garuda Linux” desktop shortcut and button in Garuda Welcome appear to do nothing.
sudo -E calamares -d
calamares: error while loading shared libraries: libboost_python310.so.1.79.0: cannot open shared object file:
No such file or directory
garuda-dr460nized-linux-zen-220909.iso, the version on the main download page, is working normally (the Calamares installer launches as expected).