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
Here is a modified version of the Clover.efi with the GOP code that was commented out, sorry no package installer, the directions for building Clover are way too outdated, and it's a wonder I can get it to build at all. I'm not a programer, only a hacker, and I've not been able to figure out how to build the installer, yet.
Install it and bless it to you EFI/ESP partition, assuming you already have Clover installed. I just left the name Clover.efi, that way we know what we're booting.
https://drive.google.com/open?id=1I4Kj7HPqAbd6WqgQNsvsNK-WfIbNVbbI
[doublepost=1512317010][/doublepost]
No real Mac's to test, on my many Hacks, versions of Clover that predate HS bata won't boot HS, the Kernel loads, but the boot process stalls with errors.
Try the modded Clover.efi I posted and let me know what you get, whenever you have time.
Install it and bless it to you EFI/ESP partition, assuming you already have Clover installed. I just left the name Clover.efi, that way we know what we're booting.
https://drive.google.com/open?id=1I4Kj7HPqAbd6WqgQNsvsNK-WfIbNVbbI
[doublepost=1512317010][/doublepost]
No real Mac's to test, on my many Hacks, versions of Clover that predate HS bata won't boot HS, the Kernel loads, but the boot process stalls with errors.
Try the modded Clover.efi I posted and let me know what you get, whenever you have time.
OK. File downloaded.
Question
Should I put that in EFI/EFI/Clover? (The folder that contain CloverX64.efi)
Or put that in EFI/EFI/Boot? (the folder that contain BootX64.efi)
I am a bit confused because what I bless is the BootX64.efi.
If that file is for EFI/EFI/Clover. Should I bless that file directly?
Or still bless the bootX64.efi, but rename the original CloverX64.efi to CloverX64.bak, and make the new file as the CloverX64.efi?
You can really put it anywhere and bless it. I figured put it in the EFI/Boot dir and run the bless command on it, you'd have too files in the EFI/Boot dir, BootX64.efi and Clover.efi, but it really should't matter, as you're running the bless command on the Clover.efi, and that's what the Mac is going to use as a boot file.
Code:
sudo bless --mount /Volumes/EFI --setBoot --file /Volumes/EFI/efi/boot/CLOVER.efi --verbosePay attention to the verbose output and make sure there are no errors, and reboot.
I tested it in one of my VM's and it booted fine, but I have no way to know if/how it will work on a real Mac. Really none of the Clover options in the config.plist should matter much, nor any of the driver Clover installs, the code for GOP should be contained in this CLOVER.efi, and it will work or it won't.
If it doesn't I'll have to add some debug code to it, and figure out how to add it to the debug log so we can see at what point the code is failing. This is why I gave ups on rEFInd, it has no method of debugging, and I just didn't want to add it.
Last edited:
Done, same result. Clover is working, but black screen only.
This is the bless result.
The associate log is attached. The CsmVideoDxe seems loaded, bur screen inti still failed
0:259 0:013 === [ LoadDrivers ] =======================================
0:683 0:424 Loading AppleImageCodec-64.efi status=Success
0:752 0:069 Loading AppleKeyAggregator-64.efi status=Success
0:822 0:069 Loading AppleUITheme-64.efi status=Success
0:842 0:019 Loading DataHubDxe-64.efi status=Success
0:908 0:066 Loading FirmwareVolume-64.efi status=Success
1:007 0:098 Loading FSInject-64.efi status=Success
1:112 0:105 Loading OsxFatBinaryDrv-64.efi status=Success
1:171 0:058 Loading SMCHelper-64.efi status=Success
1:187 0:015 Loading VBoxHfs-64.efi status=Success
1:201 0:013 Loading CsmVideoDxe-64.efi status=Success
1:235 0:034 - driver needs connecting
1:240 0:005 1 drivers needs connecting ...
1:244 0:004 PlatformDriverOverrideProtocol not found. Installing ... Success
1:254 0:009 Video driver loaded: disconnect Success
1:269 0:015 Searching for invalid DiskIo BY_DRIVER connects: not found, all ok
6:089 4:820 === [ InitScreen ] ========================================
6:459 0:370 SetScreenResolution: 1920x1080 - not found!
6:494 0:034 Console modes reported: 1, available modes:
6:513 0:019 - [01]: 80x25 (current mode)
6:535 0:021 SetScreenResolution: 1920x1080 - not found!
6:577 0:042 reinit: self device path=PciRoot(0x0)\Pci(0x1F,0x2)\Sata(0x2,0x0,0x0)\HD(1,GPT,512E9338-97FA-49A2-9EFC-07DE40B22916,0x28,0x64000)
6:590 0:012 Using embedded font: Success
Ok, I'll make some more code changes and add debugging, may take me a day or two to figure out how debugging should work in Clover, no one on Clover's discussion forum on scourforge seems to want to answer a simple question, so I have to dig though the code and figure out how to make msglog statements appear in the debug log.
Really appreciate all you effort, especially you mentioned that you are not a cMP user.
Anyway, I will be here to help you to perform the test on a real Mac. Cheers!
I know I said I had given up on rEFInd, but I did a quick and dirty of a slightly altered version if anyone wants to try it.
https://drive.google.com/open?id=1huEJWNlWQD6SA6oSHNMa-je-HZom90SZ
Unpack the zip file and copy it to your EFI/ESP partition into the efi folder.
Then bless the REFIND2.efi, and reboot.
https://drive.google.com/open?id=1huEJWNlWQD6SA6oSHNMa-je-HZom90SZ
Unpack the zip file and copy it to your EFI/ESP partition into the efi folder.
Then bless the REFIND2.efi, and reboot.
Code:
sudo bless --mount /Volumes/EFI --setBoot --file /Volumes/EFI/efi/refind/REFIND2.efi --verboseTested, same result, black screen, no mouse or keyboard available. Unable continue to boot.
If you have you Mac EFI graphics card handy, try it with only that installed and see if you get to the rFEInd boot menu on that. At least that will let us know if rEFInd is booting at all.
I've done a little testing, and in my limited testing, and from what others have reported, it seems that AMD cards may work, while nVidia may not.
Tho, I maybe barking up the wrong tree, it's just odd that others got this to work.
I'm going to do some more testing........
OK, I have the card on hand, but can't do it right now. Most likely can do that early next week.
With rEFInd, GOP modes are set in the refind.conf, and they are going too differ from one graphics card to the next, or even one monitor to the next on the same graphics card.
With my RX580 connected to one display, valid modes were 0-7, with the same display connected to a GXT1050, valid modes were 0-10.
With my RX580 connected to one display, valid modes were 0-7, with the same display connected to a GXT1050, valid modes were 0-10.
Code:
# Set the screen's video resolution. Pass this option either:
# * two values, corresponding to the X and Y resolutions
# * one value, corresponding to a GOP (UEFI) video mode
# Note that not all resolutions are supported. On UEFI systems, passing
# an incorrect value results in a message being shown on the screen to
# that effect, along with a list of supported modes. On EFI 1.x systems
# (e.g., Macintoshes), setting an incorrect mode silently fails. On both
# types of systems, setting an incorrect resolution results in the default
# resolution being used. A resolution of 1024x768 usually works, but higher
# values often don't.
# Default is "0 0" (use the system default resolution, usually 800x600).
#
#resolution 1024 768
#resolution 1440 900
resolution 10OK, but is it possible to fix the resolution at 1920x1080? I think this is the most compatible resolution now. I am 100% sure both my video card and my monitor support this standard resolution.
Or I need to figure out the value for GOP video mode on my setup?
If the monitor you are using doesn't support scaling, and you don't set the proper mode in the refind.conf then you may never see any video.
Try like this for 1920x180
Code:
# Set the screen's video resolution. Pass this option either:
# * two values, corresponding to the X and Y resolutions
# * one value, corresponding to a GOP (UEFI) video mode
# Note that not all resolutions are supported. On UEFI systems, passing
# an incorrect value results in a message being shown on the screen to
# that effect, along with a list of supported modes. On EFI 1.x systems
# (e.g., Macintoshes), setting an incorrect mode silently fails. On both
# types of systems, setting an incorrect resolution results in the default
# resolution being used. A resolution of 1024x768 usually works, but higher
# values often don't.
# Default is "0 0" (use the system default resolution, usually 800x600).
#
resolution 1920 1080
#resolution 1440 900
#resolution 10This is what I get from the monitor manual. So, it looks like it can accept 1080p 60 signal and automatically adjust to display it properly.
I tried DearthnVader's version as well as the version I built with an official Mac card. They both boot fine with my 5770 installed. They also both boot with the RX 560 installed. In both cases, there is no output on the RX 560 screen until the OS is loaded. Nothing useful in the refind log.
Back at this, somewhat, armed with a real MacPro3,1.
No luck on GOP boot screens, but I was able to get VBIOS boot screens with Clover and boot the macOS. I haven't done a lot of testing, but if anyone wants to play along, I'll put up a howto?
No luck on GOP boot screens, but I was able to get VBIOS boot screens with Clover and boot the macOS. I haven't done a lot of testing, but if anyone wants to play along, I'll put up a howto?
Yes please, I am very interested in it. Million thanks in advance.
I am now with a 5,1 and a RX580. But for VBIOS, this should make any difference, right?
Should work, give me a few to post a how to and some screen shots.
Fist thing we need is Clover_v2.4k_r4558.
https://sourceforge.net/projects/cloverefiboot/files/Installer/
Next, what we really need for testing is a hard drive formatted Master Boot Record, this can be troublesome in the Disk Utility in High Sierra, so it's better to go to the command line.
Code:
diskutil list
/dev/disk0 (internal, physical):
#: TYPE NAME SIZE IDENTIFIER
0: GUID_partition_scheme *500.1 GB disk0
1: EFI EFI 209.7 MB disk0s1
2: Apple_HFS None 9.9 GB disk0s2
3: Apple_HFS El Capitan 489.2 GB disk0s3
4: Apple_Boot Recovery HD 650.0 MB disk0s4
/dev/disk1 (internal, physical):
#: TYPE NAME SIZE IDENTIFIER
0: FDisk_partition_scheme *500.1 GB disk1
1: DOS_FAT_32 NEXT 500.1 GB disk1s1
/dev/disk2 (internal, physical):
#: TYPE NAME SIZE IDENTIFIER
0: GUID_partition_scheme *1.0 TB disk2
1: Bios Boot Partition 1.0 MB disk2s1
2: Linux Filesystem 991.6 GB disk2s2
3: Linux Swap 8.6 GB disk2s3We can see here, I already have an MBR disk( disk1 ), so find the disk you want to format, then:
Code:
diskutil partitiondisk /dev/disk1 MBR FAT32 NAME 0bThen we can install Clover to our new drive:
Then we need to adjust our clover config in the EFI/Clover folder of our Fat32 drive:
Rename the config copy.txt to config.plist and replace the one Clover installed.
Then edit it with Clover Configurator adding you Serial Number and UUID.
You may also want to inject ATI or nVidia depending on your card, most of all Clovers patches I disabled, and if your system is other than 5,1, just change that too.
Once we are done, we head back to the command line to bless our disk for legacy( CSM( AKA Bios )) booting.
SIP must be disabled.
Code:
sudo bless -device /dev/disk1 --setBoot --nextonly --legacy --verboseAdjust /dev/disk1 as needed, and if you want to boot clover all the time, remove --nextonly, but for testing leave it in to be sure you can boot clover. This will only set the clover boot disk on the next boot, then revert to you selected startup disk.
Should work, give me a few to post a how to and some screen shots.
Fist thing we need is Clover_v2.4k_r4558.
https://sourceforge.net/projects/cloverefiboot/files/Installer/
Next, what we really need for testing is a hard drive formatted Master Boot Record, this can be troublesome in the Disk Utility in High Sierra, so it's better to go to the command line.
Code:diskutil list /dev/disk0 (internal, physical): #: TYPE NAME SIZE IDENTIFIER 0: GUID_partition_scheme *500.1 GB disk0 1: EFI EFI 209.7 MB disk0s1 2: Apple_HFS None 9.9 GB disk0s2 3: Apple_HFS El Capitan 489.2 GB disk0s3 4: Apple_Boot Recovery HD 650.0 MB disk0s4 /dev/disk1 (internal, physical): #: TYPE NAME SIZE IDENTIFIER 0: FDisk_partition_scheme *500.1 GB disk1 1: DOS_FAT_32 NEXT 500.1 GB disk1s1 /dev/disk2 (internal, physical): #: TYPE NAME SIZE IDENTIFIER 0: GUID_partition_scheme *1.0 TB disk2 1: Bios Boot Partition 1.0 MB disk2s1 2: Linux Filesystem 991.6 GB disk2s2 3: Linux Swap 8.6 GB disk2s3
We can see here, I already have an MBR disk( disk1 ), so find the disk you want to format, then:
Code:diskutil partitiondisk /dev/disk1 MBR FAT32 NAME 0b
Then we can install Clover to our new drive:
Then we need to adjust our clover config in the EFI/Clover folder of our Fat32 drive:
Rename the config copy.txt to config.plist and replace the one Clover installed.
Then edit it with Clover Configurator adding you Serial Number and UUID.
You may also want to inject ATI or nVidia depending on your card, most of all Clovers patches I disabled, and if your system is other than 5,1, just change that too.
Once we are done, we head back to the command line to bless our disk for legacy( CSM( AKA Bios )) booting.
SIP must be disabled.
Code:sudo bless -device /dev/disk1 --setBoot --nextonly --legacy --verbose
Adjust /dev/disk1 as needed, and if you want to boot clover all the time, remove --nextonly, but for testing leave it in to be sure you can boot clover. This will only set the clover boot disk on the next boot, then revert to you selected startup disk.
Thanks for the detailed instruction.
I've tried all internal HDD, HDD mounted on a PCIe SATA 3 card, and USB thumb drive on the native USB 2.0 port. Not quite there yet, but definitely something is working.
I formatted the driver to MBR FAT 32 (tired both terminal command and disk utility)
I installed Clover, set the Serial and UUID accordingly.
Inject ATI
Set boot timeout 20s, just to make sure there is enough time for my monitor to wake up.
Set the display to 1920x1080
Bless the drive as next boot drive
Even though I didn't boot to Clover, but I can see something
Which means the GPU is actually working and displaying. But just not to any boot loader or OS yet.
Some bug in the Clover installer, install the other first stage boot loader, AKA boot0af.
Got it, thanks! Will take some time to study that and look for the solution.
I tried the boot0af option in Clover, still the same error.
I'm not sure if this is helpful, but I ran into the no bootable device issue several times when getting my bootcamp volumes working. I think I posted in a few threads trying to find a solution. I eventually discovered that if I selected my bootcamp volume in the start up disc selection it would result in the no bootable disc behavior, but for some reason if I allowed bootchamp to do the drive selection it would boot it up no problem. I don't have an intimate understanding of the mechanisms in play, but it was my suspicion that whatever OS X was doing to bless the drive was leading to the problem. Perhaps there is an alternative way to select the clover boot volume other than the terminal bless command? It's tantalizing to see this, as I suspect your volume is there it's just the boot up that's not working. Here is the latest thread where I posted about this: https://forums.macrumors.com/threads/bootcamp-woes.2114109/#post-25965986
@Fl0r!anHehe, I must have been really lucky when (successfully) tried using Clover for getting boot screens last year. Most of those settings are not relevant until macOS has booted, so I guess it might only work on a special Clover release (or with specific GPUs?).
I currently can't replicate what I've done as I don't have access to a Mac Pro right now, but I can tell you that I was using my Sapphire R9 280 with stock UEFI Hybrid VBIOS. I just had a look in my downloads folder and I think I've been using Clover R3424. Maybe I had CsmVideoDxe installed, not sure.
Good luck!
Any chance you still have the r3424 installer pkg?
I've been unable to build this commit, as I have no idea what commit of EDK2 it's built against.