-
Notifications
You must be signed in to change notification settings - Fork 50
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Failed to "Install Config" from GUI #118
Comments
Can you try redoing the latest GUI installation steps? The old location and old scripts seemed to be getting referenced and used here. |
@jlobue10 when you mentioned "old location" do you mean the GUI still displayed the default path as
the same thing still appeared and with the same result.... Btw rEFInd is kind of installed as I can found it in the EFI boot options, but it is not the default option and the images are not set properly, i.e. it looks very ugly Q.Q |
I mean the script that was being called appears to be from the old location. Do Install rEFInd, Create config and Install config work for you after reinstalling the GUI with the newer method? Also, what is your output of |
Did every steps after reinstalling, but still got the same result - same error message when trying to
Here is the result:
Thank you so much! |
I see that part of your problem is that the Windows EFI entry is active and taking precedence over rEFInd. I'll have to update my OLED Deck to debug further. It's been a while here. |
@jlobue10 thank you so much! Or should I do anything from Windows to prevent it from taking precedence? Btw, wanted to share this screen with you: this is what I got after the installation - all the images (the background and icons) are not installed properly |
Every time I tried to run "Install Config", it will show this error to me"
sudo su
/home/deck/.local/SteamDeck_rEFInd/GUI/
. The message is mentioning something different (/home/deck/.SteamDeck_rEFInd/GUI/
), but I think they are the same? At least I tried manually created that folder and copied the files, still getting the same error.I am not sure what I have missed, any help or hints would be much appreciated!
The text was updated successfully, but these errors were encountered: