Give me a few minutes. I can write the exact step for you to follow.
DearthnVader can also check if the steps I provide are correct or not.
Got a tip for us?
Let us know
Become a MacRumors Supporter for $50/year with no ads, ability to filter front page stories, and private forums.
Resolved Boot menus for graphics output protocol.(AMD only)see page 13
- Thread starter DearthnVader
- Start date
- Sort by reaction score
Give me a few minutes. I can write the exact step for you to follow.
DearthnVader can also check if the steps I provide are correct or not.
1) Go to this link
https://drive.google.com/open?id=1qrXbRiFIfqeqaxgmZ8tPGQn4PIdLL_Hh
download the refind(1).zip
2) Unzip it, you should able to see something like this inside the folder.
3) open terminal, then enter
Code:
diskutil listyou will see something like this
You can see that there are many partitions named EFI with the size of 209.7MB, that's what we want.
In my case, I am now booting from disk6. That's my primary partition, so, I don't want to touch that drive.
disk1 is to store the most important data. Even I have backup, I don't want to touch that either.
disk2 is my backup daily clone. I can trash it at any time. So, I use that as my test drive.
This beta test should be very very safe, so, no need to worry too much. Avoid those super important drive is good enough. If you still has concern, and you have no HDD around can be installed to just run this test, you may insert a USB drive into the cMP's front USB 2.0 port. Format that to HFS+ in disk utility, then run the above command again to check if the USB driver has this 209.7MB EFI partition. If yes, you can use that.
So, pick a disk number that has that 209.7MB EFI partition. In my case, I use disk2.
4) in terminal, enter
Code:
sudo mkdir /Volumes/EFIN.B. Admin password is required, just type that and press enter, nothing will be displayed on the screen
5) in terminal, enter
Code:
sudo mount -t msdos /dev/disk2s1 /Volumes/EFIN.B. if your disk number is 3, then the disk2s1 will be disk3s1. You have to replace that with the correct disk number
6) Now you should see a drive like this is mounted in Finder (or on desktop, depends on your setting)
7) Open this drive in Finder. Depends on the drive you chose, it may be blank, may be have something inside. If there is already a folder also call "EFI", you are good to go. If nothing there, then create a folder called "EFI" (capital letter) by yourself.
8) Copy the whole "refind" folder inside that "EFI" folder. No need to worry if something is already there (like my screen capture below), no need to touch them.
9) back to terminal, enter
Code:
sudo bless --mount /Volumes/EFI --setBoot -nextonly --file /Volumes/EFI/efi/refind/REFIND.efiIf it ask your admin password again, just enter that again.
10) Now, everything is done. You can restart your computer in the normal way.
There are few possibilities
A) You see nothing on the screen, and keyboard Caps lock key no response. That most likely rEFInd cannot start up properly. Give it 3 minutes, if still nothing happen. Press and hold power button to force shutdown the Mac. Then your Mac will back to normal on next boot.
B) You can see nothing, but the keyboard Caps lock key work. This should means rEFInd is properly started, but the UEFI GOP driver not working as expected. You should able to press "Enter" to continue the boot. Once boot to desktop, your Mac is already back to normal. If the Mac seems cannot boot to desktop after you press Enter and wait for a reasonable amount of time. Then force shutdown, your Mac will back to normal.
C) You can see the boot screen, but once you pick an OS to continue to boot, it failed. This mean the UEFI GOP is working, just need to fix the boot loader. Again, shutdown / force shutdown can bring your Mac back to normal.
D) You can see the boot screen, and you can continue boot to OS. This mean DearthnVader's work is perfect for a 3,1.
Last edited:
They definitely read them. I’ve been talking back and forth with an engineer on the bug report site.
Code:
sudo bless --mount /Volumes/EFI --setBoot -nextonly --file /Volumes/EFI/efi/refind/REFIND.efi --shortform
Awesome, I figured it would work with the 3,1, just don't know why it doesn't seem to with the 5,1.
4,1 untested, as I assume most folks already flashed them to 5,1.
Million thanks, you proved DearthnVader’s work is actually good.
After a day at home, I am now out of town again. So, can’t perform more test until next week.
I am still wondering if that’s 5,1’s problem, or my setup causing the issue. e.g. one of my hard drive causing rEFInd can’t start.
Hopefully another 5,1 beta tester can join us.
I just tried it with my 5,1. I didn't see any boot screen. It started up the macOS installation on the drive I installed it on though.
I just tried it with my 4.1 flashed to 5.1 (With RX580 Pulse)
No Screen
Refind.log:
0:100 0:100 MemLog inited, TSC freq: 3457999609
0:100 0:000 Now is 27.8.2018, 5:41:36 (GMT)
0:116 0:016 Starting rEFInd on Apple EFI
2:843 2:726 ScanVolumes()
2:851 0:008 ScanVolumes add whole disk volume to list
2:857 0:005 ScanVolumes add EFI to list
2:862 0:005 ScanVolumes add unknown volume to list
2:871 0:008 ScanVolumes add whole disk volume to list
2:885 0:014 ScanVolumes add GAMES_WIN to list
2:893 0:008 ScanVolumes add whole disk volume to list
2:902 0:009 ScanVolumes add FAT volume to list
2:918 0:015 ScanVolumes add Réservé au système to list
2:926 0:008 ScanVolumes add SYSTEME to list
2:934 0:008 ScanVolumes add whole disk volume to list
2:939 0:005 ScanVolumes add EFI to list
2:944 0:005 ScanVolumes add GAMES_MAC to list
2:952 0:008 ScanVolumes add whole disk volume to list
2:957 0:005 ScanVolumes add EFI to list
2:973 0:015 ScanVolumes add DATAS_MAC to list
2:981 0:008 ScanVolumes add whole disk volume to list
2:988 0:006 ScanVolumes add DATAS_WIN to list
3:005 0:016 ScanVolumes add unknown volume to list
3:009 0:004 ScanVolumes add Preboot to list
3:013 0:004 ScanVolumes add Macintosh HD to list
3:017 0:004 ScanVolumes add Recovery to list
3:022 0:004 ScanVolumes add VM to list
3:051 0:029 ConsoleControl ok
3:055 0:003 UgaDraw ok
3:059 0:003 GraphicsOutput ok
3:063 0:003 Available graphics modes for refit.conf screen_resolution:
3:066 0:003 Curr. Mode = 0, Modes = 0, FB = 0, FB size=0x0
3:070 0:003 SetMaxResolution: found best mode 0: 0x0
3:084 0:013 - already set
No Screen
Refind.log:
0:100 0:100 MemLog inited, TSC freq: 3457999609
0:100 0:000 Now is 27.8.2018, 5:41:36 (GMT)
0:116 0:016 Starting rEFInd on Apple EFI
2:843 2:726 ScanVolumes()
2:851 0:008 ScanVolumes add whole disk volume to list
2:857 0:005 ScanVolumes add EFI to list
2:862 0:005 ScanVolumes add unknown volume to list
2:871 0:008 ScanVolumes add whole disk volume to list
2:885 0:014 ScanVolumes add GAMES_WIN to list
2:893 0:008 ScanVolumes add whole disk volume to list
2:902 0:009 ScanVolumes add FAT volume to list
2:918 0:015 ScanVolumes add Réservé au système to list
2:926 0:008 ScanVolumes add SYSTEME to list
2:934 0:008 ScanVolumes add whole disk volume to list
2:939 0:005 ScanVolumes add EFI to list
2:944 0:005 ScanVolumes add GAMES_MAC to list
2:952 0:008 ScanVolumes add whole disk volume to list
2:957 0:005 ScanVolumes add EFI to list
2:973 0:015 ScanVolumes add DATAS_MAC to list
2:981 0:008 ScanVolumes add whole disk volume to list
2:988 0:006 ScanVolumes add DATAS_WIN to list
3:005 0:016 ScanVolumes add unknown volume to list
3:009 0:004 ScanVolumes add Preboot to list
3:013 0:004 ScanVolumes add Macintosh HD to list
3:017 0:004 ScanVolumes add Recovery to list
3:022 0:004 ScanVolumes add VM to list
3:051 0:029 ConsoleControl ok
3:055 0:003 UgaDraw ok
3:059 0:003 GraphicsOutput ok
3:063 0:003 Available graphics modes for refit.conf screen_resolution:
3:066 0:003 Curr. Mode = 0, Modes = 0, FB = 0, FB size=0x0
3:070 0:003 SetMaxResolution: found best mode 0: 0x0
3:084 0:013 - already set
Thanks both!
It seems at least the rEFInd can actually start up properly on a flashed 5,1. There is something on my cMP stop it to initialise properly.
However, if I read that correctly. It's still using UGA on the 5,1, but not GOP. That's why we still can't get boot screen yet on the 5,1.
Perhaps we could compare with the log of a 3,1 to confirm that it says something other than "UgaDraw." Could somebody that has tried this on a 3,1 and got it working please provide your refind.log?
got a reply from apple for boot screens:
Please know that our engineering team has determined that this issue behaves as intended based on the information provided.
They closed the issue.
in 4 hours apple will probably release the new beta, we'll see if it contains boot-screens or not.
Please know that our engineering team has determined that this issue behaves as intended based on the information provided.
They closed the issue.
in 4 hours apple will probably release the new beta, we'll see if it contains boot-screens or not.
Last edited:
Code:
1:639 0:024 ScanVolumes add FAT volume to list
1:722 0:082 ConsoleControl ok
1:741 0:019 UgaDraw ok
1:789 0:047 GraphicsOutput ok
1:808 0:019 Available graphics modes for refit.conf screen_resolution:
1:825 0:016 Curr. Mode = -1, Modes = 5, FB = 80000000, FB size=0xC0000000
1:841 0:016 SetMaxResolution: found best mode 0: 1280x1024
1:875 0:033 About to switch to graphic mode 0
1:940 0:065 Video mode change to mode #0: Success
1:958 0:017 - setSo on the 5,1 we are not getting any modes, nor the Framebuffer, nor the size of the frame buffer.
I'm not sure the reason for this.
We really need someone with a 4,1 to report if they are still running a 4,1 firmware.
the new beta is out. I'm not a developer so I have to wait for the public beta. Has anyone seen any difference with the bootrom ?
It seems that the firmware is unchanged... Unfortunately, given their recent response to the issue, Apple will probably not be giving us boot screens after all. It's up to us then!
Here you go (Mac Pro 3,1).
Code:
0:100 0:100 MemLog inited, TSC freq: 2793088881
0:100 0:000 Now is 25.8.2018, 13:13:19 (GMT)
0:136 0:036 Starting rEFInd on Apple EFI
0:691 0:554 ScanVolumes()
0:701 0:009 ScanVolumes add whole disk volume to list
0:707 0:006 ScanVolumes add EFI to list
0:714 0:006 ScanVolumes add PCIe to list
0:722 0:007 ScanVolumes add Recovery HD to list
0:746 0:024 ConsoleControl ok
0:752 0:006 UgaDraw ok
0:757 0:005 GraphicsOutput ok
0:763 0:006 Available graphics modes for refit.conf screen_resolution:
0:777 0:013 Curr. Mode = -1, Modes = 8, FB = 80000000, FB size=0xFF000000
0:782 0:005 SetMaxResolution: found best mode 0: 1920x1200
0:793 0:011 About to switch to graphic mode 0
0:837 0:044 Video mode change to mode #0: Success
0:843 0:005 - set
Their response doesn't exactly clarify if it's an issue that they are willing to fix or not. I hope they do!
@thomasthegps - If you're not a developer, how were you able to ask about the boot screens?! Who did you reach out to and what did you ask them?
@MisterAndrew - Exactly. I still have a feeling the boot screens are coming, specifically in Beta 10.