Become a MacRumors Supporter for $50/year with no ads, ability to filter front page stories, and private forums.

osxfr33k

macrumors regular
Jun 26, 2019
164
21
Just outside right now.
Think it was called "DBG-BOOTx64.efi". Pls check.
Use from 059a

DBG Opencore only otherwise 059 never had one. I never had 059a just 059 then to 060. Do you have previous compiled copies laying around?
 

osxfr33k

macrumors regular
Jun 26, 2019
164
21
You are correct. Only started doing Debug Versions from v059a.

Got a Media Error just had to click on Enter to proceed. Still no GUI weird but this is from 059a right? I had 059 working before let me try 059 again.

How difficult would it be to start with the 059 source create a DBG and re-compile because that is the version that works anything after 059 stopped working as far as the GUI menu goes.

I need to run to Coctco soon I'll wait to see what you want me to try next if you think its feasible to re-compile 059 not 059a with a DBG file, I have to assume this will take some time if you can do this, I'll run that version when its ready.

Thanks!
 

Attachments

  • refind.log 2.zip
    5.5 KB · Views: 115
Last edited:

osxfr33k

macrumors regular
Jun 26, 2019
164
21
Run swap in the efi from 059, reboot with this and report.

So used the 059 library and the 059a dedug file it doesn't like it for some reason see refind.log zipped and picture of boot issue.
 

Attachments

  • refind.log 3.zip
    3.4 KB · Views: 95
  • IMG_1125.jpg
    IMG_1125.jpg
    592.1 KB · Views: 107

Dayo

macrumors 68020
Original poster
Dec 21, 2018
2,257
1,279
So used the 059 library and the 059a dedug file it doesn't like it for some reason see refind.log zipped and picture of boot issue.
Confused. I thought you were only swapping in the BOOTx64 from each version. Don't complicate it at this point.

  • You had a 060 setup
  • You were supposed to rename the BOOTx64 efi file in that setup and paste in one from 059a.
  • Now, rename the 059a file and paste in the BOOTx64 efi file from v059.
  • Don't change anything else. It's the 060 setup with only BOOTx64.efi files changing
 

osxfr33k

macrumors regular
Jun 26, 2019
164
21
Confused. I thought you were only swapping in the BOOTx64 from each version. Don't complicate it at this point.

  • You had a 060 setup
  • You were supposed to rename the BOOTx64 efi file in that setup and paste in one from 059a.
  • Now, rename the 059a file and paste in the BOOTx64 efi file from v059.
  • Don't change anything else

Your confusing me now to I had 060a setup and placed in the DBG file you attached. Tell me exactly which version you want in EFI right now its 059 with the Debug file you attached. The first time it was 060a library with the DGB file you attached.
 

osxfr33k

macrumors regular
Jun 26, 2019
164
21
Paste in BOOTx64.efi from v059.
This is not a debug version so you should just tell what happens.

Everything works fine in 059 when I swap 059 boot file for the 059a DBG(renamed of course) I get the error posted above and the refind.log is from 059 package with 059a debug file you attached is this what you wanted? If I replace the 059 file back it boots normal I have the GUI boot menu.

I already posted library 060a in EFI with the DBG file you attached replaced in the 060a library. Same issue no GUI menu and the media error. So you have from 060a and 059 libraries the DBG file you attached replaced in both libraries.

Do you want me to put in the library 060a and boot file 059 known working and see what happens?

Ok so I installed library from 060a and replaced 060a "BOOTx64.efi" with the one from 059 works perfectly fine.
 
Last edited:

Dayo

macrumors 68020
Original poster
Dec 21, 2018
2,257
1,279
Do you want me to put in the library 060a and boot file 059 known working and see what happens?

My expectation of what should have been happening all this time is this:
  1. You had a v060a setup and ran the debug version and posted the log
  2. You swapped in the BOOTx64.efi file from v059a that I attached into the same folder and rebooted, and posted the log
  3. You should now swap in a BOOTx64.efi file from v059 into the same folder, reboot and report what happens as this is not a debug version.
That's what has been requested. Don't introduce anything else into the picture.
 
  • Like
Reactions: osxfr33k

osxfr33k

macrumors regular
Jun 26, 2019
164
21
My expectation of what should have been happening all this time is this:
  1. You had a v060a setup and ran the debug version and posted the log
  2. You swapped in the BOOTx64.efi file from v059a that I attached into the same folder and rebooted, and posted the log
  3. You should now swap in a BOOTx64.efi file from v059 into the same folder, reboot and report what happens as this is not a debug version.
That's all you need to do. Don't introduce anything else into the picture.

Yes did that I edited my post after yours.
 

Dayo

macrumors 68020
Original poster
Dec 21, 2018
2,257
1,279
Just make a new post and report what happened after you copied in the BOOTx64.efi file from v059 into the v060a folder and rebooted.
 

osxfr33k

macrumors regular
Jun 26, 2019
164
21
Just make a new post and report what happened after you copied in the BOOTx64.efi file from v059 into the v060a folder and rebooted.

I have a normal boot and rEFInd GUI menu all ways of booting are working OC, OC_ALt and from the main GUI rEFInd menu the Catalina Icon.
 

Dayo

macrumors 68020
Original poster
Dec 21, 2018
2,257
1,279
I have a normal boot and rEFInd GUI
I see. Thanks.

Can you confirm that this was all on the same machine and that no other changes were made apart from changing the BOOTx64 files?
 

osxfr33k

macrumors regular
Jun 26, 2019
164
21
I see. Thanks.

Can you confirm that this was all on the same machine and that no other changes were made apart from changing the BOOTx64 files?

Same machine same hardware same graphics card

NVIDIA GeForce 8800 GT
 

Dayo

macrumors 68020
Original poster
Dec 21, 2018
2,257
1,279
Well, something doesn't add up.

The line of code that is apparently returning - GraphicsOutput ...NOT FOUND! in v059 and v059a has not changed since the original release of Refind v0.12.0 from the original author. Basically not possible that it would suddenly stop working on the same setup and the same environment.

The expected outcome of the last test was a blank screen and everything says something is different and it seems that your working scenario is one with the legacy video patch perhaps and that the not working ones are somehow in a different environment.

Anyway, one last throw of the dice is to go back to the v060a BOOTx64.efi, open the "BOOT/chainloader/config.conf" and uncomment the "#text_renderer false" line under advanced configuration section and test that.

Make sure it is on the same environment as the v059 one as your results say they are not.
 

Dayo

macrumors 68020
Original poster
Dec 21, 2018
2,257
1,279
Well, something doesn't add up.

The line of code that is apparently returning - GraphicsOutput ...NOT FOUND! in v059 and v059a
I meant v059a and v060a. No reason why it should work in v059 unless something else is different.
 

osxfr33k

macrumors regular
Jun 26, 2019
164
21
I meant v059a and v060a. No reason why it should work in v059 unless something else is different.

I will have to try this a bit later but my theory is something compiled in 059 went wrong and is working on fine on my 8800 and other user machines and later compiled versions corrected some source mistake and has now broken GUI menu for 8800. I installed a fresh copy of 10.15.6 no Legacy patch I don't want to break anything for when I place my RX560 back into the Mac.

My Theory is sound because 059 Boot EFI works in all versions what else could it be.....
 

Dayo

macrumors 68020
Original poster
Dec 21, 2018
2,257
1,279
...what else could it be
Well, debug logging was introduced as from v059a. If you are absolutely sure there is no difference in the environment, that is the only other change. Not sure how it could be but after eliminating everything, this is what remains.

BTW, there is no "Library" this setup is just a link between two separate independent applications, Refind and OpenCore. You can mix and match them as you please as they operate independently.

So you can keep updating the OpenCore bit on every release and maintain the BOOTx64.efi from v059.
Basically no need to change your GPU if you want to keep it.
 
  • Like
Reactions: osxfr33k

osxfr33k

macrumors regular
Jun 26, 2019
164
21
Well, debug logging was introduced as from v059a. If you are absolutely sure there is no difference in the environment, that is the only other change. Not sure how it could be but after eliminating everything, this is what remains.

BTW, there is no "Library" this setup is just a link between two separate independent applications, Refind and OpenCore. You can mix and match them as you please as they operate independently.

So you can keep updating the OpenCore bit on every release and maintain the BOOTx64.efi from v059.
Basically no need to change your GPU if you want to keep it.

Sounds good I can do that instead :)

I mentioned this in one of the posts above and I will post this in the OpenCore forums but OC_ALT boots always without black screen with Board Product Mac-F42C88C8 but OC boots to black screen with Board Product Mac-7BA5B2D9E42DDD94 removing Shikigva=80 from Nvram OC took care of this in version 060 but now even with that flag removed it boots to black screen. This is with Graphics Card ITX Aero RX560 may be forced to load an RX580 and deal with buying another card soon. Just a lot of little things going wrong but anyone else with a RX560 will most likely have the same issue.
 

Dayo

macrumors 68020
Original poster
Dec 21, 2018
2,257
1,279
I will post this in the OpenCore forums but ...
Understand that this guide is not creating some special program. It is just a PROCESS that allows two completely separate individual programs, Refind and OpenCore, to work together.

So you should consider each one as if you simply got that program and installed. If you had an issue if you had downloaded and installed OpenCore by itself, you would go to the relevant place to ask for help on it. The fact that you are using this process does not change that.

OC_ALT is just normal OpenCore set to work out of that folder. Everything else is the same. So if you have an issue with configuring it or the other one, treat this as any normal OpenCore installation.

This also means you not bound to the provided sample config file that came with it. If the other provided config file works for you, overwrite this with that. Applies vice versa.

As repeated several times though, for the intricacies of OpenCore or Refind config, go to the right place to ask for help.

You don't even need to mention that you are using this guide as it is not relevant. There are far more knowledgeable people there that can help out better. (You can tag me if you want and I will chip in if I have something useful to offer)

Issues relating to making the two programs work together as per this guide are welcome here as I fully understand these having pulled the process together.
 
Last edited:
  • Like
Reactions: osxfr33k

startergo

macrumors 603
Sep 20, 2018
5,020
2,282
What happened to the Graphics?
1596580007217.png


Code:
Load Refind EFI Drivers...
0:562  0:016  Refind EFI Driver Count = 0

0:580  0:017  Read Config...
0:596  0:016    - WARN: Cannot Find Specified Configuration File
0:642  0:046    - WARN: Cannot Find Specified Icons Directory. Switching to Text Mode
@Dayo Did you modify something for the locations? I am on an HFS+ drive with location:
/Volumes/Refind/System/Library/CoreServices/boot.efi
 
Register on MacRumors! This sidebar will go away, and you'll see fewer ads.