Failed to open \EFI\com.solus-project - Not Found

Axios

BuzzPCSOS Well I would say thats a good Development tho it might not seem
like.
Man over the years process of elimination has always been one my best tools
otherwise one can end up chasing ones tail all the time.
Guess thats why I keep stuff to when I have problems with other stuff...lol

Note: Maybe if some dev watching may have some input more now that you have nailed it
at least to Solus.

Sebastian

BuzzPCSOS So, I haven't been following this thread closely, but your reply about Install issues reminds me about my own situation. I have been testing Solus 4.6 ISO before release and also run into Installation issues. I have documented them in this issue

Bottom line is I also have an quite old HP Elite book, that only has experimental EFI support and installation fails in most cases.
Calamares installer recognizes it as BIOS and proceeds Installation with GPT partition, then fails to boot.
Calamares seems to be set up wrongly for old legacy BIOS systems.

I am on my phone, so writing sucks, but check out the issue I have linked.

BuzzPCSOS

Sebastian Thanks, yes I found your bug report when I was trying to sort out a boot issue with an old Toshiba laptop on another thread. I think I came to the same conclusion that you did. I finally managed to install Solus onto it by manually formatting to MBR and setting up the partitions manually.
Most Legacy systems can boot into GPT providing certain rules are met, I think this is what Calamares is trying to do but if you have a Legacy PC that does not support GPT then this method will fail. At that point manual partitioning is your friend.

In a nutshell, the issue mostly being discussed in this thread is that Solus 4.6 iso will not make a UEFI boot on some older computers that support dual (Legacy/UEFI) boot even though Solus 4.5 did. Updating 4.5 to 4.6 breaks UEFI either by running updates from 4.5 or as a clean install of 4.6.
Maybe related to Calamares but I think it is the failure of the 4.6 iso to boot into UEFI that is flagging the installer to make a Legacy only install.
I have not set up a bug report for this yet as some of the facts have been a bit hazy. Spending a while with an empty hard drive and some spare time to nail down exactly what is going on.

Axios

BuzzPCSOS I think you correct in your thinking at this point
Kinda where I left it to.

(Maybe related to Calamares but I think it is the failure of the 4.6 iso to boot into UEFI that is flagging the installer to make a Legacy only install.)
The big question is to why!!

Sebastian

Alright, no hurry. And thank you.

Just for clarification. I was talking about this:

BuzzPCSOS I have not set up a bug report for this yet as some of the facts have been a bit hazy. Spending a while with an empty hard drive and some spare time to nail down exactly what is going on.

I would also encourage you just to open an issue for this even if you don't have all details figured out yet. You can add details later.
It's good to bring devs attention to this issue, they kind of gotta figure out a solution for this before next ISO release, cause people running into unbootable systems right after installation is no good at all.

BuzzPCSOS

Axios Good call. I do updates every Friday so I can fairly accurately nail it down to something that got pushed across in March. Just a case of backtracking to see what UEFI elements got changed around then.
A little busy right now but will be treating that as the next step.
It would also be good to get an idea of how many other old PCs are also victims of this. There seems to be plenty of similar concerns for other distros out there.

Sebastian

I believe 4.5 was the first ISO with Calamares installer. How certain are you, that 4.5 Calamares actually identified your machine differently, opposed to identifying the system same but then act differently?
Reasons for Calamares acting differently might be a different Calamares version or a different Calamares configuration.

On the partitioning screen on the left top corner, it says BIOS. But when you click on or next to that, you get a tool tip explaining that this means your system is either pure legacy BIOS or BIOS with UEFI comptability mode opposed to pure UEFI I guess.
It it says BIOS for you too, how certain are you that 4.5 Calamares said UEFI instead?
You have a way to boot into 4.5 ISO and take a look?
This might narrow things down.

BuzzPCSOS

Sebastian Simply put. Pretty certain.
I have recently booted from and installed from 4.5 and 4.6 ISOs. Happy to try again to clarify any points I have missed.
4.5 installed as UEFI and GPT. It created an EFI partition and booted without any error messages.
4.6 installed as BIOS and GPT. It installed GRUB as the boot manager.
Booting from 4.5 iso UEFI mode - shows no error messages.
Booting from 4.6 iso UEFI mode - shows Failed to open \EFI\BOOT - Not Found
Updating 4.5 to 4.6 causes the Failed to open \EFI\com.solus-project - Not Found. Which was the error message I first noticed in March.
I will try another two installs when I have a little more time and check your recommendations.

Axios

Sebastian Yes thats what we are talking about.
I had alitte go around with it on an older dell but reburnt the iso with gnome-disks and it worked booted
into eufi fine and had efi listed instead of bios for install.
Something seems little temperamental or something.

Did not mean to interrupt.

BuzzPCSOS

Sebastian I would really like to get to the bottom of this.
Booted into 4.5 install and took a snapshot of the summary screen. UEFI and GPT
Booted into 4.6 install and took a snapshot of the summary screen. BIOS and GPT
Went onto the forum to post images and saw your post, realised I was one screen too far so did the process again to get the right pictures.
This time on 4.6 I am getting UEFI and GPT. Something has changed between two boots of Solus not more than a few minutes between. I know I was in UEFI boot mode on both occasions, I've done it so often now I could do it in my sleep.
I can get UEFI now I think but now I get this

Which was very similar to the error screen that flashed up during Spiral Linux boot. A few days earlier I did try manually setting boot path to \EFI\BOOT\fbx64.efi which initially took me to a MOK enrolment screen which failed to enrol because I don't have Secure Boot I guess. I am supposing that the error screen I am seeing now is a result of my fiddling although I am still getting the original Failed to open message which was my original issue.
I have tried installing mokutil and running sudo mokutil --reset but it just returns EFI variables are not supported on this system. Undecided if I have had a mediocre success or an abject failure.

TraceyC

Please open an issue for the issues you're seeing with the installer on our bug tracker for this. By opening an issue, it will allow our developers to look into it and keep track of progress.

As you've likely seen, there is more than one issue reported with Calamares. We'd like to get those sorted out.

Thanks!

BuzzPCSOS

TraceyC Here you are. Thank you.

« Previous Page