I have a 12,1 MBP that has successfully and delightfully installed Garuda from a Live Install USB stick choose the Dragonized KDE Plasma.
For fun I moved to try the same Garuda but with the Hyprland edition. The Hyprland Live Install boots fine, but the problem is, the install fails. By that I mean:
If I use the Application Manager to fine Install, and choose that App, nothing happens when executing that App
If I navigate to Garuda Assistant and click the link for Install provided there, the click just loops back to the Window, so it closes the Window and re-opens Garuda Assistant.
So there is some kind of blocker on this Live Install version of Garuda? I am trying to wrap my head around why a Live Install would not offer up the usual choices of “where do you want me to install Linux”, etc. Does anyone have any insights as to why a Live Install ISO on a USB stick would fail in this manner? I am sure it is something trivial, but I cannot seem to get over this little hump.
Describe your issue in detail. The more we know, the better we can help
Show us the results of your searches, and what you’ve tried
After rebooting, post the FULL output of garuda-inxi in the body of the post (not linked externally, or collapsed with the “hide details” feature)
Format terminal output (including your garuda-inxi) as a code block by clicking the preformatted text button (</>) , or put three tildes (~) above and below the text
I would love to! The problem is, the Live Boot ISO now logs in to a black screen and frozen mouse. I have tried both choices, Open Source Drivers (appropriate as the MBP has Intel integrated graphics) and the NVideo proprietary version.
So nuts… cannot even get a garuda-inxi to add at this point… maybe I just try a new download of the ISO and today the version is better than the one I got a few days ago.
The USB Live Install brings up Garuda Hyprland login manager screen. I provide the garuda password, and that is when I am faced with the black screen and frozen mouse.
So I can only assume that since this same process worked for KDE Plasma flawlessly, it has to do with the Hyprland version. The SHA256 checks out legit.
I was able to get Hyprland to boot, a few times, but as mentioned, it would never actually install, so that was the time to log a garuda-inxi, but sadly, now, at this point, I cannot even get past the login.
I assume something is now pooched on the HD for this Live Install, and attempts to move past login are freezing due to it “finding” something… something it does not like.
Nevermind… I will just use the KDE Plasma as it is a delight, and perhaps come back to Hyprland with something I can grab second-hand, like an old Thinkpad or something.
No. It is strictly an Intel laptop with nothing weird in it save the Broadcom Wifi/Bluetooth chip, but that actually works fine in KDE Plasma, so why would it not work when exchanging KDE for Hyprland? Makes no sense. I am amazed Hyprland booted fine, a few times, but was unable to run the installer is all. Now that it does not even bring up the desktop though, that stumps me. I suppose an absolute clean wipe of the drive might be the ticket, but that would be cheating and would force me to re-install KDE Plasma too. A shame! My BTRFS drive has around 400GB unused so being able to dual boot into either KDE or Hyprland would be so awesome.
I used the garuda website, direct download. checked the SHA256, it all matched. So I am confident the code I am running on the USB stick is fine.
If I could login to Hyperland, I could easily get a copy of garuda-inxi as per the rules. I could also run lsblk. From my KDE install, list blocks shows this:
If when I provide the password “garuda” to the login for Hyprland, I get to Hyprland, which has happened on a few occasions, then yes, I appreciate the tip here, to try a terminal command like that to perhaps get past any problems present when using the GUI elements of Hyprland. My problem at the moment is login hangs on a blackscreen and frozen mouse! So I cannot access a terminal.
As I mentioned. This laptop has zero NVidia HW. It is manufactured with an Intel graphics chip. So while it may be true that it fails with NVidia GPUs, it is also true that it fails with Intel integrated graphics. Strangely, KDE Plasma has no such problems.
And again, the reason I cannot provide the inxi is simply because the Live Install fails to even get me to a point where it makes sense to have a terminal.
I will keep trying to get back to where Hyprland actually booted and does not hang … some combo I tried had worked a few times, although as I say, that was a bit superficial in that none of the “INSTALL” options of the Live Boot were present.
Understood. Clearly nothing jumped off the pages from my lsblk output. I am kinda miffed here that Hyprland did indeed successfully get past login a few times, as if I could get back to that point, I could indeed fire up a terminal and hopefully get a few more details to help on debugging why the install process does not kick off.
Ok. I figured out one thing for sure. If I assumed the Garuda Login for Hyperland had a User account set to garuda, and so all i needed to do was fill in the password as garuda, boy was I wrong. I used the Change User option, and explicitly provided garuda, and a password of garuda and then an only then did the login succeed. Who knew!
Wow. So now I am in Hyprland, where I can get a garuda-inxi to show off, and maybe learn why the install options just hangs from this Live Boot install attempt.
ruda@garuda in ~ as 🧙 took 3s
╰─λ sudo -E calamares
QStandardPaths: runtime directory '/run/user/1000' is not owned by UID 0, but a directory permissions 0700 owned by UID 1000 GID 1000
QStandardPaths: runtime directory '/run/user/1000' is not owned by UID 0, but a directory permissions 0700 owned by UID 1000 GID 1000
Authorization required, but no authorization protocol specified
Cannot open display ":1"
Missing information requested in the template may result in not receiving assistance