Jump to content

Clover General discussion

ErmaC

By ErmaC,
in Clover

 Share
30960 posts in this topic

Recommended Posts

Guest ricoc90
Guest ricoc90
Posted
Posted

I wanted to boot my Optiplex through UEFI. However, the os x partitions are not showing up then. Looking at the log, it seems that the drivers are not being loaded:
 

...
0:127  0:000  Hiding entries with string Herstel
0:127  0:000  Hiding entries with string Data
0:127  0:000  Hiding entries with string Windows
0:127  0:000  Hiding entries with string Preboot
0:127  0:000  === [ LoadDrivers ] =======================================
0:127  0:000  === [ InitScreen ] ========================================
0:127  0:000  SetMaxResolution: found best mode 8: 1920x1080
0:495  0:367  Video mode change to mode #8: Success
...

Any idea why? Booting legacy works fine though:

2:729  0:000  Hiding entries with string Herstel
2:729  0:000  Hiding entries with string Data
2:729  0:000  Hiding entries with string Windows
2:729  0:000  Hiding entries with string Preboot
2:729  0:000  === [ LoadDrivers ] =======================================
2:730  0:000  Loading AppleImageCodec-64.efi  status=Success
2:731  0:000  Loading AppleUITheme-64.efi  status=Success
2:731  0:000  Loading AppleKeyAggregator-64.efi  status=Success
2:731  0:000  Loading FSInject-64.efi  status=Success
2:732  0:000  Loading FirmwareVolume-64.efi  status=Success
2:732  0:000  Loading SMCHelper-64.efi  status=Success
2:732  0:000  Loading VBoxHfs-64.efi  status=Success
2:734  0:002   - driver needs connecting
2:734  0:000  Loading apfs.efi  status=Success
2:737  0:002   - driver needs connecting
2:737  0:000  2 drivers needs connecting ...
2:737  0:000  PlatformDriverOverrideProtocol->GetDriver overriden
2:737  0:000  APFS driver loaded
2:958  0:221  === [ InitScreen ] ========================================

post-1502423-0-79502100-1508784924_thumb.png

 

Edit: Also, when booting in UEFI i'm not able to enter UEFI shell. Looks like it can't find Shell64U.efi

smolderas
smolderas
Posted
Posted

I wanted to boot my Optiplex through UEFI. However, the os x partitions are not showing up then. Looking at the log, it seems that the drivers are not being loaded:

 

...
0:127  0:000  Hiding entries with string Herstel
0:127  0:000  Hiding entries with string Data
0:127  0:000  Hiding entries with string Windows
0:127  0:000  Hiding entries with string Preboot
0:127  0:000  === [ LoadDrivers ] =======================================
0:127  0:000  === [ InitScreen ] ========================================
0:127  0:000  SetMaxResolution: found best mode 8: 1920x1080
0:495  0:367  Video mode change to mode #8: Success
...

Any idea why? Booting legacy works fine though:

2:729  0:000  Hiding entries with string Herstel
2:729  0:000  Hiding entries with string Data
2:729  0:000  Hiding entries with string Windows
2:729  0:000  Hiding entries with string Preboot
2:729  0:000  === [ LoadDrivers ] =======================================
2:730  0:000  Loading AppleImageCodec-64.efi  status=Success
2:731  0:000  Loading AppleUITheme-64.efi  status=Success
2:731  0:000  Loading AppleKeyAggregator-64.efi  status=Success
2:731  0:000  Loading FSInject-64.efi  status=Success
2:732  0:000  Loading FirmwareVolume-64.efi  status=Success
2:732  0:000  Loading SMCHelper-64.efi  status=Success
2:732  0:000  Loading VBoxHfs-64.efi  status=Success
2:734  0:002   - driver needs connecting
2:734  0:000  Loading apfs.efi  status=Success
2:737  0:002   - driver needs connecting
2:737  0:000  2 drivers needs connecting ...
2:737  0:000  PlatformDriverOverrideProtocol->GetDriver overriden
2:737  0:000  APFS driver loaded
2:958  0:221  === [ InitScreen ] ========================================

attachicon.gifSchermafbeelding 2017-10-23 om 20.54.30.png

 

Edit: Also, when booting in UEFI i'm not able to enter UEFI shell. Looks like it can't find Shell64U.efi

Maybe your mainboard have this "semi" UEFI (like mine) called hybrid efi, which is a half implementation of UEFI. So in return you would be booting in legacy mode.

 

Edit: I have a ga-z68x-ud5-b3

Guest ricoc90
Guest ricoc90
Posted
Posted 
0:173  0:000  Default theme: embedded
0:173  0:000  Hiding entries with string Herstel
0:173  0:000  Hiding entries with string Data
0:173  0:000  Hiding entries with string Windows
0:173  0:000  Hiding entries with string Preboot
0:173  0:000  === [ LoadDrivers ] =======================================
0:182  0:008  Loading APFS-64.EFI  status=Success
0:244  0:062   - driver needs connecting
0:244  0:000  Loading OsxFatBinaryDrv-64.efi  status=Success
0:253  0:008  Loading AppleImageCodec-64.efi  status=Success
0:262  0:008  Loading AppleUITheme-64.efi  status=Success
0:271  0:009  Loading DataHubDxe-64.efi  status=Success
0:281  0:010  Loading AppleKeyAggregator-64.efi  status=Success
0:290  0:008  Loading VBoxHfs-64.efi  status=Success
0:299  0:009   - driver needs connecting
0:299  0:000  Loading FSInject-64.efi  status=Success
0:308  0:008  Loading FirmwareVolume-64.efi  status=Success
0:317  0:008  Loading SMCHelper-64.efi  status=Success
0:325  0:008  Loading PartitionDxe-64.efi  status=Success
0:334  0:008   - driver needs connecting
0:334  0:000  Loading Fat-64.efi  status=Success
0:343  0:009   - driver needs connecting
0:343  0:000  Loading EmuVariableUefi-64.efi  status=Success
0:352  0:008  EmuVariableUefi Initialize: VariableCommonInitialize = Success, orig services stored, install gEmuVariableControlProtocolGuid = Success
0:352  0:000  Loading OsxAptioFixDrv-64.efi  status=Success
0:361  0:008  4 drivers needs connecting ...
0:361  0:000  PlatformDriverOverrideProtocol not found. Installing ... Success
0:361  0:000  Partition driver loaded: 
0:361  0:000  APFS driver loaded
0:361  0:000  Searching for invalid DiskIo BY_DRIVER connects: not found, all ok
0:899  0:537  EmuVariable InstallEmulation: orig vars copied, emu.var.services installed, CreateEvent VirtualAddressChange = Success, CreateEvent ExitBootServices = Success, set Status=Success
0:920  0:021  === [ InitScreen ] ========================================
0:920  0:000  SetMaxResolution: found best mode 8: 1920x1080

Maybe your mainboard have this "semi" UEFI (like mine) called hybrid efi, which is a half implementation of UEFI. So in return you would be booting in legacy mode.

 

Edit: I have a ga-z68x-ud5-b3

Don't think so, I booted in UEFI before w/o issues. Looks like Clover is skipping the entire EFI folder as it looks like to me:

0:601  0:000  - [03]: Volume: PciRoot(0x0)\Pci(0x1F,0x2)\Sata(0x0,0xFFFF,0x0)\HD(1,GPT,F06DA778-D2F8-4331-A013-BBDDE9104513,0x28,0x64000)
0:602  0:000          Result of bootcode detection: bootable unknown (legacy)
0:609  0:007          This is SelfVolume !!

...

0:653  0:000 Checking volume "EFI" (PciRoot(0x0)\Pci(0x1F,0x2)\Sata(0x0,0xFFFF,0x0)\HD(1,GPT,F06DA778-D2F8-4331-A013-BBDDE9104513,0x28,0x64000)) ... skipped

EDIT:

 

Clover on a fat32 formatted USB boots fine in UEFI:

0:173  0:000  Default theme: embedded
0:173  0:000  Hiding entries with string Herstel
0:173  0:000  Hiding entries with string Data
0:173  0:000  Hiding entries with string Windows
0:173  0:000  Hiding entries with string Preboot
0:173  0:000  === [ LoadDrivers ] =======================================
0:182  0:008  Loading APFS-64.EFI  status=Success
0:244  0:062   - driver needs connecting
0:244  0:000  Loading OsxFatBinaryDrv-64.efi  status=Success
0:253  0:008  Loading AppleImageCodec-64.efi  status=Success
0:262  0:008  Loading AppleUITheme-64.efi  status=Success
0:271  0:009  Loading DataHubDxe-64.efi  status=Success
0:281  0:010  Loading AppleKeyAggregator-64.efi  status=Success
0:290  0:008  Loading VBoxHfs-64.efi  status=Success
0:299  0:009   - driver needs connecting
0:299  0:000  Loading FSInject-64.efi  status=Success
0:308  0:008  Loading FirmwareVolume-64.efi  status=Success
0:317  0:008  Loading SMCHelper-64.efi  status=Success
0:325  0:008  Loading PartitionDxe-64.efi  status=Success
0:334  0:008   - driver needs connecting
0:334  0:000  Loading Fat-64.efi  status=Success
0:343  0:009   - driver needs connecting
0:343  0:000  Loading EmuVariableUefi-64.efi  status=Success
0:352  0:008  EmuVariableUefi Initialize: VariableCommonInitialize = Success, orig services stored, install gEmuVariableControlProtocolGuid = Success
0:352  0:000  Loading OsxAptioFixDrv-64.efi  status=Success
0:361  0:008  4 drivers needs connecting ...
0:361  0:000  PlatformDriverOverrideProtocol not found. Installing ... Success
0:361  0:000  Partition driver loaded: 
0:361  0:000  APFS driver loaded
0:361  0:000  Searching for invalid DiskIo BY_DRIVER connects: not found, all ok
0:899  0:537  EmuVariable InstallEmulation: orig vars copied, emu.var.services installed, CreateEvent VirtualAddressChange = Success, CreateEvent ExitBootServices = Success, set Status=Success
0:920  0:021  === [ InitScreen ] ========================================
0:920  0:000  SetMaxResolution: found best mode 8: 1920x1080

So the issue is

- my Clover install or

- my BIOS

Maybe it's worth mentioning that with older Clover versions, I wasn't able to boot UEFI from the EFI partition AT ALL, it'd make the BIOS freeze. Actually I wasn't even able to navigate the EFI partition, BIOS GUI would malform.

 

EDIT2:

 

Nevermind. It's fixed now. Re-installing Clover didn't work, reformatting the EFI partition did. I still don't now what the issue was, but it's working now.

Ramalama
Ramalama
Posted
Posted

@slice

Do Clover injects default a FakeCPUID for Skylake-X ?

 

Because its strange.

If i remove FakeCPUID from Clover Config, im still able to boot...

If i use my Original CPUID as FakeCPUID, i cant boot (0x050654)...

 

So thats why i think, that Clover injects a FakeCPUID, if i doesnt specify one in the Config...

 

Cheers :-)

  • Like 1
Slice
Slice
Posted
Posted

@slice

Do Clover injects default a FakeCPUID for Skylake-X ?

 

Because its strange.

If i remove FakeCPUID from Clover Config, im still able to boot...

If i use my Original CPUID as FakeCPUID, i cant boot (0x050654)...

 

So thats why i think, that Clover injects a FakeCPUID, if i doesnt specify one in the Config...

 

Cheers :-)

I didn't make default FakeCPUID.

But I may propose that if it removed then nothing to patch.

If you set some FakeCPUID then the patch will occured and it is not good.

What is your system version? Upload, please, your kernel to check if the patch may work.

fusion71au
fusion71au
Posted
Posted

Hi Slice,

 

I get a red screen error on my legacy desktop GAP55aUd3/Intel i5-750/ATI HD 5770 with officially released Clover >r4060:

 

 

attachicon.gifClover 4061 red screen.JPG

 

Seems that commit r4061 causes the regression -

in rEFIt_UEFI/refit.inf

+ XCODE:*_*_*_CC_FLAGS = -fsigned-char -O2 -fno-common

 

 

The system makes it to the Clover GUI but red screens when applying Clover DSDT fixes, attempting to boot OS X (see attached debug log for r4061).

 

My system boots fine if I use Clover compiled without the -fno-common flag for Xcode -  eg see attached boot log with r4097.

 

@Slice,

 

Any reason why official Clover builds from SourceForge still use -fno-common for XCODE compilation, as I reported in the Clover bug thread a few months ago ---> red screen error on certain BIOS?

 

Also @Rehabman's fork of Clover r4264 has fixed this bug reported by @MakAsus in post#14840:  "If I choose kext injection control in Clover Gui, go to the folder "other", and do not change anything there, just exit this folder and injection control menu, then try to boot from selected disk, boot fails."  

 

The InjectKexts set to Detect works + you can also boot OS X with/without injected kexts (in addition to individual kext blocking) in his version...

 

 

post-846696-0-42736200-1508846818_thumb.png

post-846696-0-99789700-1508846929_thumb.png

post-846696-0-93867500-1508846950_thumb.png

 

Clover_v2.4k_r4264.RM-4339.750c5fff.pkg.zip

  • Like 1
RehabMan
RehabMan
Posted
Posted

@Slice,

 

Any reason why official Clover builds from SourceForge still use -fno-common for XCODE compilation, as I reported in the Clover bug thread a few months ago ---> red screen error on certain BIOS?

 

Also @Rehabman's fork of Clover r4264 has fixed this bug reported by @MakAsus in post#14840:  "If I choose kext injection control in Clover Gui, go to the folder "other", and do not change anything there, just exit this folder and injection control menu, then try to boot from selected disk, boot fails."  

 

The InjectKexts set to Detect works + you can also boot OS X with/without injected kexts (in addition to individual kext blocking) in his version...

 

 

 

attachicon.gifscreenshot0.png

attachicon.gifscreenshot1.png

attachicon.gifscreenshot2.png

 

 

There are quite a few fixes/features I have been working on.

 

Full disclosure in the README:

https://github.com/RehabMan/Clover/blob/master/README.md

 

I will be making a proposal in the "Clover Bug/Issue Report and Patch" thread when I'm ready (relatively soon).

 

Good to see someone is building/testing besides me and the few I know of.

  • Like 6
Slice
Slice
Posted
Posted

 

Also @Rehabman's fork of Clover r4264 has fixed this bug reported by @MakAsus in post#14840:  "If I choose kext injection control in Clover Gui, go to the folder "other", and do not change anything there, just exit this folder and injection control menu, then try to boot from selected disk, boot fails." 

 

This is resolved in official Clover.

 

About -fno-common. There was a serios reason provided by other developers.

I can't accept a patch without reasonable explanation. One want this second want another. I will choose?

  • Like 4
fusion71au
fusion71au
Posted
Posted

About -fno-common. There was a serios reason provided by other developers.

I can't accept a patch without reasonable explanation. One want this second want another. I will choose?

 

I think @apianti provided a good reason for not using it ...

 

This is not a good flag because in EFI binaries the rdata section is combined with the text section, that is needed. I believe this places the variables in the data section and that the -fcommon flag should be being used instead (it is the default, but not on all platforms).

 

  • All the official Clover versions before r4061 did not use the flag and worked for me.  Only "advantage" I can see is that using the flag results in a 1-2KB smaller compiled binary CLOVERX64.efi.
  • Clover without the flag boots my other systems without issue.
  • Newbs who can't compile their own Clover and have similar hardware to my 5 series GA-P55aUD3 won't be able to boot with Clover's auto dsdt patching, using officially released Clover eg @fallen00sniper post#3: "fixusb_1000 causes a black screen with red text for me"
  • Like 1
thbluebird
thbluebird
Posted
Posted

Greetings,

 

I've really enjoyed working with OS X ( OS: 10.11.5 ) on my laptop " Acer Aspire E5-574G-54Y2" The Clover Bootloader  ( Clover revision: 3544 ) is Awesome, as well as the contributors that have made it possible.

I'm able to boot and work, but I'm experiencing random boots and I have my NVIDIA graphic device listed, and showing to be working as a 3D accelerator (with 0 MB VRAM size ), but I have not been able to boot/use it as the primary graphics device ( I’ve tried several solutions listed for my NVIDIA 940M, but no luck, I still boot into a black screen- I can hear error sounds made from typing keys- like the system has properly booted, but just has a black screen. One thing I found odd, the Intel Graphics Card that is used ( Intel® HD Graphics 520 (Skylake GT2) is showing that there is no kext loaded for the device.

 

The audio is working quite well. It appears to be setup correctly.

 

The ACPI/DSDT files were found in ESP/EFI/CLOVER/ACPI/origin.

 

The video ROMS were found in ESP/EFI/CLOVER/ROM/

 

I am hoping someone can help me with the proper setup, config, DSDT, etc.

I have attached some files and would be happy to provide some more details/files if needed.

 

Thanks a bunch in advance for all the hard work and contributions!

 

Sincerely,

iMAC 14,2 setup files.zip

rotoyouoio
rotoyouoio
Posted
Posted

i've wasted a {censored}load of of time to test EVERY component by replacing it, so please don't tell me that mine is faulty, or to try other efi modules, or to lower the bios settings or any other obvious first steps. really frustrated with this.

 

on asus (quite possibly other vendors are affected too) x299 motherboards there is an issue of memory allocation errors with uefi boot. i can only but certainly reproduce the problem when a usb3 storage device is attached, others have reported that no matter what the usb generation is.

 

memcheck within os is a witness of this problem, and every time the occupied address ends in ***d30

 

this corrupted operation affects not only memcheck, but every operation possible. a more obvious way to produce evidence for the non believers is to render an hour or two of RED camera files to a compressed codec onto an external storage device and see the result is corrupted

 

i'm rather tired of proving that this is an actual error and not memtest being outdated. memtest is only a tool to witness this, not to test the memory

 

this obviously does not happen with legacy boot

 

quite possible this is a problem on other aptiov5 capsules and even more possible that future platforms will posses this problem too

 

to my limited understanding (it might be wrong) this effect is an evolution of memory allocation problems that people encountered on x99 platforms with aptiov5 capsules and hence aptiofix related. but back in the day this occured only before kernel loading. and i've seen somewhere, that dmazar refused to revisit aptiofix stating that it's too much time to do this from scratch.

SavageAUS
SavageAUS
Posted
Posted

Greetings,

 

I've really enjoyed working with OS X ( OS: 10.11.5 ) on my laptop " Acer Aspire E5-574G-54Y2" The Clover Bootloader  ( Clover revision: 3544 ) is Awesome, as well as the contributors that have made it possible.

I'm able to boot and work, but I'm experiencing random boots and I have my NVIDIA graphic device listed, and showing to be working as a 3D accelerator (with 0 MB VRAM size ), but I have not been able to boot/use it as the primary graphics device ( I’ve tried several solutions listed for my NVIDIA 940M, but no luck, I still boot into a black screen- I can hear error sounds made from typing keys- like the system has properly booted, but just has a black screen. One thing I found odd, the Intel Graphics Card that is used ( Intel® HD Graphics 520 (Skylake GT2) is showing that there is no kext loaded for the device.

 

The audio is working quite well. It appears to be setup correctly.

 

The ACPI/DSDT files were found in ESP/EFI/CLOVER/ACPI/origin.

 

The video ROMS were found in ESP/EFI/CLOVER/ROM/

 

I am hoping someone can help me with the proper setup, config, DSDT, etc.

I have attached some files and would be happy to provide some more details/files if needed.

 

Thanks a bunch in advance for all the hard work and contributions!

 

Sincerely,

You have so many parches in kextstopatch section enabled its hard to tell what device your trying to patch, that needs to be cleaned up.

You are also using an old bios version.

Please add system specs to signature and open a topic in the relevant section as this doesn't seem clover related.

Also when you create a new topic in the proper section, please upload clover folder minus themes and remove serial number, mlb etc from config.plist.

mhaeuser
mhaeuser
Posted
Posted

@rotoyouoio Sorry, can't quite follow what you are talking about... Usually people speak of 'memory allocation errors' in regards to early boot, where boot.efi might not get the memory it wants. If you meant that, how can you boot into the OS? And if it's not that, how is it related to Clover and how did you conclude it was an alloc and not a mapping or MMIO error?

 

EDIT: Somehow skipped the last paragraph. What you are facing is NOT a memory alloc error, because otherwise the kernel would not end up in mem. It might be a mapping error somehow caused by Aptio or even AptioFix. Dump a memmap and find out which address is faulty in that very boot cycle, its type may be relevant.

  • Like 2
rotoyouoio
rotoyouoio
Posted
Posted

@rotoyouoio Sorry, can't quite follow what you are talking about... Usually people speak of 'memory allocation errors' in regards to early boot, where boot.efi might not get the memory it wants. If you meant that, how can you boot into the OS? And if it's not that, how is it related to Clover and how did you conclude it was an alloc and not a mapping or MMIO error?

 

EDIT: Somehow skipped the last paragraph. What you are facing is NOT a memory alloc error, because otherwise the kernel would not end up in mem. It might be a mapping error somehow caused by Aptio or even AptioFix. Dump a memmap and find out which address is faulty in that very boot cycle, its type may be relevant.

will do, but the address is non constant, though it always ends in ***d30

 

and i maybe naming it wrong, forgive me, trying the best i can.

 

and the error does not prevent booting. the system is operational

 

the last phase of troubleshooting i did before confirming it with others looked like this:

 

strip the mobo from everything, attach components one by one. attach usb3 internal cardreader, get errors. disconnect it. have a hunch the problem is more generic. boot into system. get pass the stuck address test. stop. attach a usb3 hardrive. start testing. errors. disconnect it. start testing. no errors. so the problem is rather dynamic. and completely absent during legacy boot. and i need point out once again, that it affects everything, not only the outdated memtest.

 

will update once i dump

arabesc
arabesc
Posted
Posted

 

I can't make Clover to boot from a select the last booted volume, I mean the DefaultVolume/LastBootedVolume option. It almost always selects the same volume.

According to the guide it's necessary to remove the EmuVariableUefi-64.efi module, but I can't remove it because it's required for Nvidia Web Driver. The guide on Nvidia Web Driver mentions that module, and I can confirm that my system is unbootable without EmuVariableUefi-64.efi.

Is there a solution to this issue?

 

Here is the Boot section from my config:

<key>Boot</key>
<dict>
    <key>Arguments</key>
    <string>dart=0 darkwake=1 -shikigva</string>
    <key>CustomLogo</key>
    <string>Alternate</string>
    <key>Debug</key>
    <false/>
    <key>DefaultVolume</key>
    <string>LastBootedVolume</string>
    <key>Legacy</key>
    <string>PBR</string>
    <key>Log</key>
    <false/>
    <key>Secure</key>
    <false/>
    <key>Timeout</key>
    <integer>-1</integer>
    <key>XMPDetection</key>
    <string>Yes</string>
</dict>

Could someone help me on the issue, please?

arabesc
arabesc
Posted
Posted

LastBootedVolume only works with a functional nvram. you don't have any, since you require emuvariable

Is it possible to use emuvariable functionality for LastBootedVolume feature?

I'm not sure but it seems that LastBootedVolume worked before I added emuvariable module.

rotoyouoio
rotoyouoio
Posted
Posted

@rotoyouoio Sorry, can't quite follow what you are talking about... Usually people speak of 'memory allocation errors' in regards to early boot, where boot.efi might not get the memory it wants. If you meant that, how can you boot into the OS? And if it's not that, how is it related to Clover and how did you conclude it was an alloc and not a mapping or MMIO error?

 

EDIT: Somehow skipped the last paragraph. What you are facing is NOT a memory alloc error, because otherwise the kernel would not end up in mem. It might be a mapping error somehow caused by Aptio or even AptioFix. Dump a memmap and find out which address is faulty in that very boot cycle, its type may be relevant.

 

 
to continue
 
address after running darwindumper:
 
FAILURE! Data mismatch at local address 0x0000000ecbaf5d30

 

Actual Data: 0x0000000e88498849
 
does darwindumper do the dump you requested?

DarwinDumper_3.0.3_25.10_14.27.59_iMac19,1_AMI_X64_4264.RM-4339.22551(750c5fff.b2eb1d0b90)__Unknown_17B45a_user.zip

thbluebird
thbluebird
Posted
Posted

You have so many parches in kextstopatch section enabled its hard to tell what device your trying to patch, that needs to be cleaned up.

You are also using an old bios version.

Please add system specs to signature and open a topic in the relevant section as this doesn't seem clover related.

Also when you create a new topic in the proper section, please upload clover folder minus themes and remove serial number, mlb etc from config.plist.

 Hi SavageAUS,

 

Thanks for the help getting me started.

 

I followed the steps you mentioned ( I uploaded the corrected files on my original post as well).

I started a new thread - listed below.

Please let me know if there is any added info I can provide.

 

Regards,

 

http://www.insanelymac.com/forum/topic/328909-budget-gaming-laptop-acer-aspire-e5-574g-54y2-final-polish/?p=2522269

Slice
Slice
Posted
Posted

@Slice,

 

I normally use XCODE5 toolchain setting when compiling from official SVN repo but XCODE8 toolchain also works (using XCODE 9.0.1 in 10.13.x or 10.12.6).

 

Building from @rehabman's GIT repo needs XCODE8 setting.

May I proposed that Red Screen Panic occurred only with Xcode8 toolset?

  • Like 1
 Share
Go to topic listing
×
×
  • Create New...