Update - Refit does same thing, if using custom theme???
This thread was originally for my black screen issues, which fixed with reFIND, however, now to get into endeavourOS i have to go through systemD-Boot, which is fine and all but feels a bit odd. Are there any config files I can go through to go straight to endeauvourOS
archived - Hello! So, I’m confused out of my mind, about this weird problem, it is essentially, if I hard power reset I have to more on that below, I will boot into endeavoros, it’ll just be black, along with my bios screen etc. being black Gigabyte mb. I have found turning on CSM fixes it sometimes, however, that breaks sleep mode, which then won’t turn display back on if I ever go into sleep mode… Now how do I currently fix it? Well, I blindly guess which one is Windows, go into windows, click restart, and then it all works normally. My startup logs look normal every time, and, same results if i click restart in enderavorOS, they’re installed in different ssd/hdd.
Oh also, I tried installing theme and reFIND failed to show the theme, *adding the include themes/rEFInd-minimal/theme.conf into refind.conf, and making themes folder and putting the theme in there. Not sure if related or not.
are there more details on doing the transfer?, as long as I still have windows as a backup, idgf about my Linux installation Mostly using it to get more familiar with Linux I found some older posts, but they’re very unorganized. Also i think I fixed the themes by renaming the folder
Interesting, what do you suggest to do? I looked thru conf, and found this think this would help?
# When scanning volumes for EFI boot loaders, rEFInd always looks for
# macOS's and Microsoft Windows' boot loaders in their normal locations,
# and scans the root directory and every subdirectory of the /EFI directory
# for additional boot loaders, but it doesn't recurse into these directories.
# The also_scan_dirs token adds more directories to the scan list.
# Directories are specified relative to the volume's root directory. This
# option applies to ALL the volumes that rEFInd scans UNLESS you include
# a volume name and colon before the directory name, as in "myvol:/somedir"
# to scan the somedir directory only on the filesystem named myvol. If a
# specified directory doesn't exist, it's ignored (no error condition
# results). The default is to scan the "boot" directory in addition to
# various hard-coded directories.
Something sounds strange about this - does rEFInd not come up on boot? It should present AT LEAST enough choices to get anything started you wish. Usually it gives you some choices you DON’T want, which you then hide. It will automatically detect and present a Windows choice if that is present.
If rEFInd is not in charge on bootup, not sure WHAT is happening! Easy way to re-activate it is to run refind-install (it won’t overwrite modified files in your setup) or you can create your own entry in NVRAM if you choose to…
Heyo! Thx for your replies, I’ve since discovered some more interesting things??? Well first off, I have found this weird juggling of key combination pressing, after which I can hard restart my computer yanking the cord, or holding the top button like a sane person, which will then bring me into reFIND menu, which I can then use to goto SystemD-Boot, which will then take me into EndeavourOS, and work flawlessly. However, I’m not very happy bout my 5-10 mins juggling and pure panic of my system going black… I’m considering a fresh install of the whole OS, using this time Grub