rotoyouoio Posted October 25, 2017 Share Posted October 25, 2017 Could someone help me on the issue, please? LastBootedVolume only works with a functional nvram. you don't have any, since you require emuvariable Link to comment Share on other sites More sharing options...
arabesc Posted October 25, 2017 Share Posted October 25, 2017 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. Link to comment Share on other sites More sharing options...
rotoyouoio Posted October 25, 2017 Share Posted October 25, 2017 @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 Link to comment Share on other sites More sharing options...
thbluebird Posted October 25, 2017 Share Posted October 25, 2017 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 Link to comment Share on other sites More sharing options...
Slice Posted October 25, 2017 Share Posted October 25, 2017 @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? 1 Link to comment Share on other sites More sharing options...
Vampirexx Posted October 25, 2017 Share Posted October 25, 2017 Hi Slice thanx for the amazing clover! Maybe it is well known question, but is it possible to disable discreet gpu, so we can easily install high sierra on laptop with clover? Currently it requires some tricky job to disable through DSDT file and SSDT it is quite a pain in the ass for non developer users. I hope you can make it, and thank for your hard work 1 Link to comment Share on other sites More sharing options...
mhaeuser Posted October 25, 2017 Share Posted October 25, 2017 to continue address after running darwindumper: FAILURE! Data mismatch at local address 0x0000000ecbaf5d30 Actual Data: 0x0000000e88498849 does darwindumper do the dump you requested? I'm currently without home internet connection (might be up tomorrow, currently on my phone), will check asap. Where is that msg shown? Link to comment Share on other sites More sharing options...
fusion71au Posted October 25, 2017 Share Posted October 25, 2017 May I proposed that Red Screen Panic occurred only with Xcode8 toolset? No. Only if I compile Clover with XCODE5 or XCODE8 toolchain and -fno-common flag is present in refit.inf. No problem if I compile with XCODE5 or XCODE8 toolchain without the flag. No problem if I compile with GCC53 in Linux Mint 18.1. Here is boot log from successful boot with r4264 compiled with XCODE8 toolchain and -fno-common flag removed in refit.inf ... 0:100 0:100 MemLog inited, TSC freq: 2664769607 0:100 0:000 LegacyRegion2: Chipset/proc: 0xD1318086 0:100 0:000 Core i7 processors (PAM 0x40-0x47) 0:100 0:000 Test PAM1=(0x41=11, 0x5a=00, 0x81=0D, 0x91=21) at chipset D1318086 0:100 0:000 , Install = Success 0:112 0:012 BiosVideoDriverBindingStart! 0:112 0:000 BiosVideoCheckForVbe 0:112 0:000 EdidOverride not found 0:145 0:033 Edid1+ 0:145 0:000 found Detail Timing 1920x1200 0:178 0:032 Edid0+ 0:178 0:000 found Detail Timing 1920x1200 0:178 0:000 ... already present 0:185 0:007 0 1152x864 attr=BB - ok, edid+, working, highest, pref=0 0:186 0:000 1 1280x960 attr=BB - ok, edid- 0:186 0:000 2 640x480 attr=BB - ok, edid+, 640x480, working 0:187 0:000 3 800x600 attr=BB - ok, edid+, 800x600, working 0:187 0:000 4 1024x768 attr=BB - ok, edid+, 1024x768, working 0:187 0:000 5 1280x1024 attr=BB - ok, edid+, working, highest, pref=5 0:188 0:001 6 1400x1050 attr=BB - ok, edid- 0:190 0:001 7 1600x1200 attr=BB - ok, edid+, working, highest, pref=7 0:194 0:004 BV new mode: 7 1600x1200 0:422 0:228 SetMode pref 7 (7) = Success 0:695 0:273 Found supported controller for BiosBlockIO class=010601 0:696 0:000 Int13Extensions: INT 13 41 DL=80 : CF=0 BX=AA55 CX=0005 0:696 0:000 GetDriveParameters: INT 13 48 DL=80 : CF=0 AH=00 0:696 0:000 BlockSize = 512 LastBlock = 234441647 0:696 0:000 Int13Extensions: INT 13 41 DL=81 : CF=0 BX=AA55 CX=0005 0:696 0:000 GetDriveParameters: INT 13 48 DL=81 : CF=0 AH=00 0:696 0:000 BlockSize = 512 LastBlock = -387938129 0:696 0:000 Int13Extensions: INT 13 41 DL=82 : CF=0 BX=AA55 CX=0005 0:696 0:000 GetDriveParameters: INT 13 48 DL=82 : CF=0 AH=00 0:696 0:000 BlockSize = 512 LastBlock = 1953525167 1:399 0:702 1:399 0:000 Now is 25.10.2017, 22:14:27 (GMT) 1:399 0:000 Starting Clover revision: 4264.RM-4339.22530(750c5fff.eeb476310e) on CLOVER EFI 1:399 0:000 Build with: [Args: -mc --no-usb -D NO_GRUB_DRIVERS_EMBEDDED -D CHECK_FLAGS -D USE_APPLE_HFSPLUS_DRIVER -t XCODE8 | -D DISABLE_USB_SUPPORT -D NO_GRUB_DRIVERS_EMBEDDED -D CHECK_FLAGS -D USE_BIOS_BLOCKIO -D USE_LOW_EBDA -a X64 -b RELEASE -t XCODE8 -n 5 | OS: 10.13.1 | XCODE: 9.0.1] 1:399 0:000 SelfDevicePath=PcieRoot(0x0)\Pci(0x1C,0x0)\Pci(0x0,0x0)\VenHw(CF31FAC5-C24E-11D2-85F3-00A0C93EC93B,80)\HD(1,MBR,0x50CFED9B,0x800,0x32000) @DED2B698 1:399 0:000 SelfDirPath = \EFI\CLOVER 1:399 0:000 === [ Get Smbios ] ======================================== 1:399 0:000 Type 16 Index = 0 1:399 0:000 Total Memory Slots Count = 4 1:399 0:000 Type 17 Index = 0 1:399 0:000 SmbiosTable.Type17->Speed = 1333MHz 1:399 0:000 SmbiosTable.Type17->Size = 2048MB 1:399 0:000 SmbiosTable.Type17->Bank/Device = Bank0/1 A0 1:399 0:000 SmbiosTable.Type17->Vendor = 1:399 0:000 SmbiosTable.Type17->SerialNumber = 1:399 0:000 SmbiosTable.Type17->PartNumber = 1:399 0:000 Type 17 Index = 1 1:399 0:000 SmbiosTable.Type17->Speed = 1333MHz 1:399 0:000 SmbiosTable.Type17->Size = 4096MB 1:399 0:000 SmbiosTable.Type17->Bank/Device = Bank2/3 A1 1:399 0:000 SmbiosTable.Type17->Vendor = 1:399 0:000 SmbiosTable.Type17->SerialNumber = 1:399 0:000 SmbiosTable.Type17->PartNumber = 1:399 0:000 Type 17 Index = 2 1:399 0:000 SmbiosTable.Type17->Speed = 1333MHz 1:399 0:000 SmbiosTable.Type17->Size = 2048MB 1:399 0:000 SmbiosTable.Type17->Bank/Device = Bank4/5 A2 1:399 0:000 SmbiosTable.Type17->Vendor = 1:399 0:000 SmbiosTable.Type17->SerialNumber = 1:399 0:000 SmbiosTable.Type17->PartNumber = 1:399 0:000 Type 17 Index = 3 1:399 0:000 Ignoring insane frequency value 0MHz 1:399 0:000 SmbiosTable.Type17->Speed = 0MHz 1:399 0:000 SmbiosTable.Type17->Size = 0MB 1:399 0:000 SmbiosTable.Type17->Bank/Device = Bank6/7 A3 1:399 0:000 SmbiosTable.Type17->Vendor = <null string> 1:399 0:000 SmbiosTable.Type17->SerialNumber = <null string> 1:399 0:000 SmbiosTable.Type17->PartNumber = <null string> 1:399 0:000 Boot status=0 1:399 0:000 Running on: 'P55A-UD3' with board 'P55A-UD3' 1:399 0:000 === [ GetCPUProperties ] ================================== 1:399 0:000 CPU Vendor = 756E6547 Model=106E5 1:399 0:000 The CPU supported SSE4.1 1:399 0:000 BrandString = Intel® Core i5 CPU 750 @ 2.67GHz 1:399 0:000 The CPU supported turbo 1:399 0:000 MSR 0x35 40004 1:399 0:000 FSBFrequency = 140 MHz, DMI FSBFrequency = 133 MHz, Corrected FSBFrequency = 133 MHz 1:399 0:000 MaxDiv/MinDiv: 20.0/9 1:399 0:000 Turbo: 21/21/24/24 1:399 0:000 Features: 0xBFEBFBFF 1:399 0:000 Threads: 4 1:399 0:000 Cores: 4 1:399 0:000 FSB: 133 MHz 1:399 0:000 CPU: 2800 MHz 1:399 0:000 TSC: 2800 MHz 1:399 0:000 PIS: 533 MHz 1:399 0:000 ExternalClock: 133 MHz 1:399 0:000 === [ GetDevices ] ======================================== 1:399 0:000 PCI (00|00:00.00) : 8086 D131 class=060000 1:399 0:000 PCI (00|00:03.00) : 8086 D138 class=060400 1:399 0:000 PCI (00|01:00.00) : 1002 68B8 class=030000 1:399 0:000 - GFX: Model=ATI Radeon HD 5770 Series (ATI/AMD) 1:399 0:000 PCI (00|01:00.01) : 1002 AA58 class=040300 1:399 0:000 - HDMI Audio: 1:399 0:000 PCI (00|00:08.00) : 8086 D155 class=088000 1:399 0:000 PCI (00|00:08.01) : 8086 D156 class=088000 1:399 0:000 PCI (00|00:08.02) : 8086 D157 class=088000 1:399 0:000 PCI (00|00:08.03) : 8086 D158 class=088000 1:399 0:000 PCI (00|00:10.00) : 8086 D150 class=088000 1:399 0:000 PCI (00|00:10.01) : 8086 D151 class=088000 1:399 0:000 PCI (00|00:1A.00) : 8086 3B3B class=0C0300 1:399 0:000 PCI (00|00:1A.01) : 8086 3B3E class=0C0300 1:399 0:000 PCI (00|00:1A.02) : 8086 3B3F class=0C0300 1:399 0:000 PCI (00|00:1A.07) : 8086 3B3C class=0C0320 1:399 0:000 PCI (00|00:1B.00) : 8086 3B56 class=040300 1:399 0:000 PCI (00|00:1C.00) : 8086 3B42 class=060400 1:399 0:000 PCI (00|02:00.00) : 1B4B 9128 class=010601 1:399 0:000 PCI (00|00:1C.01) : 8086 3B44 class=060400 1:399 0:000 PCI (00|03:00.00) : 10EC 8168 class=020000 1:399 0:000 - LAN: 0 Vendor=Realtek 1:399 0:000 PCI (00|00:1C.02) : 8086 3B46 class=060400 1:399 0:000 PCI (00|04:00.00) : 1033 0194 class=0C0330 1:399 0:000 PCI (00|00:1C.03) : 8086 3B48 class=060400 1:399 0:000 PCI (00|05:00.00) : 168C 002E class=028000 1:399 0:000 - WIFI: Vendor=Atheros 1:399 0:000 PCI (00|00:1D.00) : 8086 3B36 class=0C0300 1:399 0:000 PCI (00|00:1D.01) : 8086 3B37 class=0C0300 1:399 0:000 PCI (00|00:1D.02) : 8086 3B38 class=0C0300 1:399 0:000 PCI (00|00:1D.03) : 8086 3B39 class=0C0300 1:399 0:000 PCI (00|00:1D.07) : 8086 3B34 class=0C0320 1:399 0:000 PCI (00|00:1E.00) : 8086 244E class=060401 1:399 0:000 PCI (00|06:04.00) : 1106 3038 class=0C0300 1:399 0:000 PCI (00|06:04.02) : 1106 3104 class=0C0320 1:399 0:000 PCI (00|06:05.00) : 1283 8213 class=010185 1:399 0:000 PCI (00|00:1F.00) : 8086 3B02 class=060100 1:399 0:000 PCI (00|00:1F.02) : 8086 3B22 class=010601 1:399 0:000 PCI (00|00:1F.03) : 8086 3B30 class=0C0500 1:399 0:000 PCI (00|3F:00.00) : 8086 2C51 class=060000 1:399 0:000 PCI (00|3F:00.01) : 8086 2C81 class=060000 1:399 0:000 PCI (00|3F:02.00) : 8086 2C90 class=060000 1:399 0:000 PCI (00|3F:02.01) : 8086 2C91 class=060000 1:399 0:000 PCI (00|3F:03.00) : 8086 2C98 class=060000 1:399 0:000 PCI (00|3F:03.01) : 8086 2C99 class=060000 1:399 0:000 PCI (00|3F:03.04) : 8086 2C9C class=060000 1:399 0:000 PCI (00|3F:04.00) : 8086 2CA0 class=060000 1:399 0:000 PCI (00|3F:04.01) : 8086 2CA1 class=060000 1:399 0:000 PCI (00|3F:04.02) : 8086 2CA2 class=060000 1:399 0:000 PCI (00|3F:04.03) : 8086 2CA3 class=060000 1:399 0:000 PCI (00|3F:05.00) : 8086 2CA8 class=060000 1:399 0:000 PCI (00|3F:05.01) : 8086 2CA9 class=060000 1:399 0:000 PCI (00|3F:05.02) : 8086 2CAA class=060000 1:399 0:000 PCI (00|3F:05.03) : 8086 2CAB class=060000 1:399 0:000 === [ GetDefaultSettings ] ================================ 1:399 0:000 Clover load options size = 0 bytes 1:404 0:005 EFI\CLOVER\config.plist loaded: Success 1:404 0:000 === [ GetListOfThemes ] =================================== 1:407 0:002 - [00]: Material 1:412 0:004 - [01]: BGM 1:416 0:004 - [02]: embedded 1:418 0:001 - [02]: random 1:418 0:000 - [02]: clover-minimal 1:423 0:004 === [ Found config plists ] =============================== 1:423 0:000 - config.plist 1:424 0:000 - config14,2.plist 1:424 0:000 === [ GetEarlyUserSettings ] ============================== 1:424 0:000 timeout set to 3 1:424 0:000 Custom boot CUSTOM_BOOT_DISABLED (0x0) 1:424 0:000 KextsToPatch: 4 requested 1:424 0:000 - [00]: AppleAHCIPort (External icons patch) :: BinPatch :: data len: 8 1:424 0:000 - [01]: AppleAHCIPort (fix IO error ICH10 for 10.13, credit SunKi) :: MatchOS: 10.13.x :: BinPatch :: data len: 20 1:424 0:000 - [02]: AppleAHCIPort (fix hotplug ICH10 for 10.13, credit SunKi) :: MatchOS: 10.13.x :: BinPatch :: data len: 26 1:424 0:000 - [03]: IOAHCIBlockStorage (TRIM Enabler) :: BinPatch :: data len: 11 1:424 0:000 Default theme: BGM 1:424 0:000 Hiding entries with string bootmgr.efi 1:424 0:000 === [ LoadDrivers ] ======================================= 1:425 0:001 Loading AppleImageCodec-64.efi status=Success 1:425 0:000 Loading AppleKeyAggregator-64.efi status=Success 1:425 0:000 Loading AppleUITheme-64.efi status=Success 1:426 0:000 Loading NTFS.efi status=Success 1:430 0:004 - driver needs connecting 1:430 0:000 Loading PartitionDxe-64.efi status=Success 1:432 0:001 - driver needs connecting 1:432 0:000 Loading HFSPlus.efi status=Success 1:435 0:003 - driver needs connecting 1:435 0:000 Loading FirmwareVolume-64.efi status=Success 1:437 0:001 Loading FSInject-64.efi status=Success 1:437 0:000 Loading GrubUDF-64.efi status=Success 1:438 0:001 - driver needs connecting 1:438 0:000 Loading SMCHelper-64.efi status=Success 1:438 0:000 Loading VBoxExt4-64.efi status=Success 1:438 0:000 - driver needs connecting 1:438 0:000 Loading VBoxIso9600-64.efi status=Success 1:440 0:001 - driver needs connecting 1:440 0:000 Video bios patch requested or CustomEDID - forcing video reconnect 1:440 0:000 7 drivers needs connecting ... 1:440 0:000 PlatformDriverOverrideProtocol->GetDriver overriden 1:440 0:000 Partition driver loaded: 1:440 0:000 HFS+ driver loaded 1:440 0:000 Video driver loaded: disconnect Success 1:595 0:155 VideoBiosPatchNativeFromEdid: 1:595 0:000 Bios: ATI, MasterDataTables: 0xCA758, std_vesa: 0xCA79C, ati_mode_table: 0xCA7A0, mode_table_size: 0x1F8 BT_ATI_2 1:595 0:000 VideoBiosPatchInit(LegacyRegion = Not Found, LegacyRegion2 = Success) = Success 1:595 0:000 VideoBiosUnlock: unlocked 1:595 0:000 Patching: BT_ATI_2 1:595 0:000 Parse Edid: descriptor block 0 is timing descriptor (h_active: 1920, v_active: 1200, h_sync_offset: 48, h_sync_width: 32, h_blanking: 160, v_blanking: 35, pixel_clock: 15400, v_sync_offset: 3, v_sync_width: 6) 1:595 0:000 mode 0 (320x200) patched to 1920x1200 1:595 0:000 VideoBiosLock: Success 1:606 0:010 BiosVideoDriverBindingStart! 1:606 0:000 BiosVideoCheckForVbe 1:606 0:000 EdidOverride not found 1:640 0:033 Edid1+ 1:640 0:000 found Detail Timing 1920x1200 1:673 0:033 Edid0+ 1:673 0:000 found Detail Timing 1920x1200 1:673 0:000 ... already present 1:677 0:004 0 1920x1200 attr=BB - ok, edid+, working, highest, pref=0 1:681 0:003 1 1152x864 attr=BB - ok, edid+, working 1:682 0:000 2 1280x960 attr=BB - ok, edid- 1:682 0:000 3 640x480 attr=BB - ok, edid+, 640x480, working 1:682 0:000 4 800x600 attr=BB - ok, edid+, 800x600, working 1:682 0:000 5 1024x768 attr=BB - ok, edid+, 1024x768, working 1:683 0:000 6 1280x1024 attr=BB - ok, edid+, working 1:684 0:001 7 1400x1050 attr=BB - ok, edid- 1:685 0:001 8 1600x1200 attr=BB - ok, edid+, working 1:689 0:004 BV new mode: 0 1920x1200 1:912 0:223 SetMode pref 0 (0) = Success 6:312 4:399 === [ InitScreen ] ======================================== 6:312 0:000 SetScreenResolution: 1920x1080 - not found! 6:312 0:000 Console modes reported: 4, available modes: 6:312 0:000 - [01]: 80x25 6:312 0:000 - [02]: 80x50 6:312 0:000 - [03]: 100x31 6:312 0:000 - [04]: 240x63 (current mode) 6:312 0:000 SetScreenResolution: 1920x1200 - already set 6:312 0:000 reinit: self device path=PcieRoot(0x0)\Pci(0x1C,0x0)\Pci(0x0,0x0)\VenHw(CF31FAC5-C24E-11D2-85F3-00A0C93EC93B,80)\HD(1,MBR,0x50CFED9B,0x800,0x32000) 6:313 0:000 Using embedded font: Success 6:314 0:000 === [ GetMacAddress ] ===================================== 6:314 0:000 === [ ScanSPD ] =========================================== 6:314 0:000 SMBus device : 8086 3B30 class=0C0500 status=Success 6:314 0:000 SMBus CmdReg: 0x3 6:314 0:000 Scanning SMBus [8086:3B30], mmio: 0xFBFFC004, ioport: 0x500, hostc: 0x1 6:314 0:000 Slots to scan [8]... 6:315 0:000 SPD[0]: Type 11 @0x50 6:333 0:018 DDR speed 1333MHz 6:333 0:000 Slot: 0 Type 24 2048MB 1333MHz Vendor=Kingston PartNo=99U5458-001.A00LF SerialNo=0704020800070002 6:334 0:000 SPD[1]: Type 11 @0x51 6:353 0:018 DDR speed 1600MHz 6:353 0:000 Slot: 1 Type 24 4096MB 1600MHz Vendor=SK Hynix PartNo=HMT351U6CFR8C-PBN0 SerialNo=0005060606020A05 6:353 0:000 SPD[2]: Type 11 @0x52 6:372 0:018 DDR speed 1333MHz 6:372 0:000 Slot: 2 Type 24 2048MB 1333MHz Vendor=Kingston PartNo=99U5458-001.A00LF SerialNo=070A02080F040001 6:372 0:000 === [ GetAcpiTablesList ] ================================= 6:378 0:005 Get Acpi Tables List from RSDT: 6:378 0:000 - [00]: FACP GBTUACPI len=116 6:378 0:000 - [01]: HPET GBTUACPI len=56 6:378 0:000 - [02]: MCFG GBTUACPI len=60 6:378 0:000 - [03]: EUDS len=1376 6:378 0:000 - [04]: TAMG GBT B0 len=2610 6:378 0:000 - [05]: APIC GBTUACPI len=188 6:378 0:000 - [06]: SLIC SLIC-MPC len=374 6:378 0:000 - [07]: SSDT PPM RCM len=7220 6:378 0:000 Calibrated TSC Frequency = 2664769607 = 2664MHz 6:380 0:002 === [ GetUserSettings ] =================================== 6:380 0:000 USB FixOwnership: yes 6:380 0:000 Dropping 3 tables: 6:380 0:000 - [00]: Drop table signature="DMAR" (52414D44) 6:380 0:000 - set table: 52414D44, 0 to drop: no 6:380 0:000 - [01]: Drop table signature="SSDT" (54445353) table-id="CpuPm" (0000006D50757043) 6:380 0:000 - set table: 54445353, 6D50757043 to drop: no 6:380 0:000 - [02]: Drop table signature="SSDT" (54445353) table-id="Cpu0Ist" (0074734930757043) 6:380 0:000 - set table: 54445353, 74734930757043 to drop: no 6:380 0:000 - final DSDT Fix mask=1B6EF1DF 6:380 0:000 Using ProductName from config 6:380 0:000 ProductName: iMac11,3 6:380 0:000 BiosVersion: not set, Using BiosVersion from clover 6:380 0:000 BiosVersion: IM112.88Z.005B.B00.1708080439 6:380 0:000 BiosReleaseDate: 08/08/17 6:380 0:000 Using FirmwareFeatures from config 6:380 0:000 FirmwareFeatures: 0xE00DE137 6:380 0:000 Using FirmwareFeaturesMask from config 6:380 0:000 FirmwareFeaturesMask: 0xFF1FFF3F 6:380 0:000 PlatformFeature will not set in SMBIOS 6:380 0:000 PlatformFeature: 0xFFFF 6:380 0:000 Converted CustomUUID 9ecdd6b2-3d1a-8450-8a9a-130759752ccf 6:391 0:010 === [ ScanVolumes ] ======================================= 6:391 0:000 Found 16 volumes with blockIO 6:391 0:000 - [00]: Volume: PcieRoot(0x0)\Pci(0x1C,0x0)\Pci(0x0,0x0)\VenHw(CF31FAC5-C24E-11D2-85F3-00A0C93EC93B,80) 6:392 0:000 Result of bootcode detection: bootable unknown (legacy) 6:392 0:000 - [01]: Volume: PcieRoot(0x0)\Pci(0x1C,0x0)\Pci(0x0,0x0)\VenHw(CF31FAC5-C24E-11D2-85F3-00A0C93EC93B,81) 6:409 0:016 Result of bootcode detection: bootable unknown (legacy) 6:409 0:000 - [02]: Volume: PcieRoot(0x0)\Pci(0x1C,0x0)\Pci(0x0,0x0)\VenHw(CF31FAC5-C24E-11D2-85F3-00A0C93EC93B,82) 6:409 0:000 Result of bootcode detection: bootable unknown (legacy) 6:409 0:000 - [03]: Volume: PcieRoot(0x0)\Pci(0x1C,0x0)\Pci(0x0,0x0)\VenHw(CF31FAC5-C24E-11D2-85F3-00A0C93EC93B,80)\HD(1,MBR,0x50CFED9B,0x800,0x32000) 6:410 0:000 Result of bootcode detection: bootable unknown (legacy) 6:412 0:001 This is SelfVolume !! 6:412 0:000 - [04]: Volume: PcieRoot(0x0)\Pci(0x1C,0x0)\Pci(0x0,0x0)\VenHw(CF31FAC5-C24E-11D2-85F3-00A0C93EC93B,80)\HD(2,MBR,0x50CFED9B,0x32800,0xDF61000) 6:413 0:000 Result of bootcode detection: bootable Windows (vista,win) 6:413 0:000 - [05]: Volume: PcieRoot(0x0)\Pci(0x1C,0x0)\Pci(0x0,0x0)\VenHw(CF31FAC5-C24E-11D2-85F3-00A0C93EC93B,81)\HD(1,GPT,1B386756-0922-4B96-BD59-1FC3B79E189E,0x800,0x64000) 6:414 0:001 Result of bootcode detection: bootable unknown (legacy) 6:424 0:009 - [06]: Volume: PcieRoot(0x0)\Pci(0x1C,0x0)\Pci(0x0,0x0)\VenHw(CF31FAC5-C24E-11D2-85F3-00A0C93EC93B,81)\HD(2,GPT,55225B2F-270E-453A-88B9-E12C5D9F6F12,0x64800,0xC99A3800) 6:424 0:000 Result of bootcode detection: bootable Windows (vista,win) 6:424 0:000 - [07]: Volume: PcieRoot(0x0)\Pci(0x1C,0x0)\Pci(0x0,0x0)\VenHw(CF31FAC5-C24E-11D2-85F3-00A0C93EC93B,81)\HD(3,GPT,1FE507E9-E82B-43BF-8A8C-2249DFF67874,0xC9A08000,0xF8C68E0) 6:425 0:000 - [08]: Volume: PcieRoot(0x0)\Pci(0x1C,0x0)\Pci(0x0,0x0)\VenHw(CF31FAC5-C24E-11D2-85F3-00A0C93EC93B,81)\HD(4,GPT,06C99874-BE94-4641-9935-2BDC5778B0E9,0xD92CE8E0,0x135F20) 6:426 0:000 - [09]: Volume: PcieRoot(0x0)\Pci(0x1C,0x0)\Pci(0x0,0x0)\VenHw(CF31FAC5-C24E-11D2-85F3-00A0C93EC93B,81)\HD(5,GPT,A75A0F00-1C9A-40A7-9CC9-25EFEB5BA8D4,0xD9404800,0x40000) 6:426 0:000 Result of bootcode detection: bootable unknown (legacy) 6:426 0:000 - [10]: Volume: PcieRoot(0x0)\Pci(0x1C,0x0)\Pci(0x0,0x0)\VenHw(CF31FAC5-C24E-11D2-85F3-00A0C93EC93B,81)\HD(6,GPT,696E551C-EF37-4132-8ADD-F7E3932173C4,0xD9444800,0xF9C3800) 6:427 0:000 Result of bootcode detection: bootable Windows (vista,win) 6:427 0:000 - [11]: Volume: PcieRoot(0x0)\Pci(0x1C,0x0)\Pci(0x0,0x0)\VenHw(CF31FAC5-C24E-11D2-85F3-00A0C93EC93B,82)\HD(1,GPT,5BA2531C-72D6-4B9E-8519-A17EE40D1500,0x28,0x64000) 6:428 0:000 Result of bootcode detection: bootable unknown (legacy) 6:430 0:002 - [12]: Volume: PcieRoot(0x0)\Pci(0x1C,0x0)\Pci(0x0,0x0)\VenHw(CF31FAC5-C24E-11D2-85F3-00A0C93EC93B,82)\HD(2,GPT,685228AF-4F5E-4C8A-AA24-22FE96002F84,0x64800,0x6CEA2000) 6:436 0:005 Result of bootcode detection: bootable Windows (vista,win) 6:436 0:000 - [13]: Volume: PcieRoot(0x0)\Pci(0x1C,0x0)\Pci(0x0,0x0)\VenHw(CF31FAC5-C24E-11D2-85F3-00A0C93EC93B,82)\HD(3,GPT,7D80B5FA-7720-49DA-BC47-5637E5BD2009,0x6CF06800,0x40000) 6:437 0:000 - [14]: Volume: PcieRoot(0x0)\Pci(0x1C,0x0)\Pci(0x0,0x0)\VenHw(CF31FAC5-C24E-11D2-85F3-00A0C93EC93B,82)\HD(4,GPT,C94F3A09-FEFB-4C8C-982A-E0ACCAD515D3,0x6CF46800,0x768A668) 6:438 0:000 - [15]: Volume: PcieRoot(0x0)\Pci(0x1C,0x0)\Pci(0x0,0x0)\VenHw(CF31FAC5-C24E-11D2-85F3-00A0C93EC93B,82)\HD(5,GPT,623905BA-F830-4C63-900E-151E05317C0B,0x745D0E68,0x135F20) 6:494 0:056 PutNvramPlistToRtVars: nvram.plist not found 6:494 0:000 === [ InitTheme ] ========================================= 6:495 0:001 Using theme 'BGM' (EFI\CLOVER\themes\BGM) 6:495 0:000 OS main and drive as badge 6:497 0:001 Loading font from ThemeDir: Success 6:497 0:000 Choosing theme BGM 6:497 0:000 after NVRAM boot-args=dart=0 kext-dev-mode=1 -lilubeta 6:497 0:000 === [ Dump SMC keys from NVRAM ] ========================== 6:497 0:000 found AppleSMC protocol 6:497 0:000 === [ AddCustomEntries ] ================================== 6:497 0:000 Custom entry 0 skipped because it is hidden. 6:497 0:000 === [ ScanLoader ] ======================================== 6:497 0:000 - [03]: 'SYSTEM' 6:502 0:004 AddLoaderEntry for Volume Name=SYSTEM 6:502 0:000 Not match custom entry 0: Type: not match 6:509 0:007 - [04]: 'WIN7_X64SSD' 6:520 0:010 - [05]: 'EFI' 6:560 0:039 AddLoaderEntry for Volume Name=EFI 6:560 0:000 Not match custom entry 0: Type: not match 6:571 0:011 - [06]: 'DATA_TSH' 6:592 0:020 - [07]: 'Macintosh HD' 6:641 0:048 AddLoaderEntry for Volume Name=Macintosh HD 6:641 0:000 Not match custom entry 0: Type: not match 6:648 0:007 Check if volume Is Hibernated: 6:648 0:000 Check sleep image 'by signature': 6:702 0:054 read prefs \Library\Preferences\com.apple.PowerManagement.plist status=Success 6:702 0:000 using default sleep image name = \private\var\vm\sleepimage 6:724 0:021 sleepimage not found -> Not Found 6:724 0:000 hibernated: no - sign 6:730 0:006 - [08]: 'Recovery HD' 6:731 0:000 AddLoaderEntry for Volume Name=Recovery HD 6:731 0:000 Skipped because matching custom entry 0! 6:731 0:000 - [10]: 'WIN10' 6:741 0:010 - [11]: 'EFI' 6:767 0:025 - [12]: 'DATA' 6:778 0:011 - [14]: 'macOS' 6:869 0:091 AddLoaderEntry for Volume Name=macOS 6:869 0:000 Not match custom entry 0: Type: not match 6:899 0:029 Check if volume Is Hibernated: 6:899 0:000 Check sleep image 'by signature': 6:949 0:050 read prefs \Library\Preferences\com.apple.PowerManagement.plist status=Success 6:949 0:000 using default sleep image name = \private\var\vm\sleepimage 6:986 0:036 sleepimage not found -> Not Found 6:986 0:000 hibernated: no - sign 6:986 0:000 - [15]: 'Recovery HD' 6:987 0:000 AddLoaderEntry for Volume Name=Recovery HD 6:987 0:000 Skipped because matching custom entry 0! 6:987 0:000 === [ AddCustomTool ] ===================================== 6:991 0:003 found tool \EFI\CLOVER\tools\Shell64U.efi 6:991 0:000 Checking EFI partition Volume 5 for Clover 6:992 0:001 Found Clover 6:995 0:003 === [ GetEfiBootDeviceFromNvram ] ========================= 6:995 0:000 - found entry 0. 'Boot Microsoft EFI Boot from SYSTEM', Volume 'SYSTEM', DevicePath 'PcieRoot(0x0)\Pci(0x1C,0x0)\Pci(0x0,0x0)\VenHw(CF31FAC5-C24E-11D2-85F3-00A0C93EC93B,80)\HD(1,MBR,0x50CFED9B,0x800,0x32000)\EFI\microsoft\Boot\bootmgfw.efii' 6:995 0:000 DefaultIndex=0 and MainMenu.EntryCount=10 7:770 0:774 GUI ready 9:396 1:625 BootVariable of the entry is empty 9:396 0:000 === [ StartLoader ] ======================================= 9:396 0:000 Finally: ExternalClock=133MHz BusSpeed=133238kHz CPUFreq=2665MHz PIS: hw.busfrequency=532000000Hz 9:396 0:000 Loading boot.efi status=Success 9:823 0:427 GetOSVersion: 10.13.1 (17B45a) 9:823 0:000 CSR_CFG: CSR_ALLOW_UNTRUSTED_KEXTS | CSR_ALLOW_UNRESTRICTED_FS | CSR_ALLOW_TASK_FOR_PID | CSR_ALLOW_KERNEL_DEBUGGER | CSR_ALLOW_APPLE_INTERNAL | CSR_ALLOW_UNRESTRICTED_DTRACE | CSR_ALLOW_UNRESTRICTED_NVRAM | CSR_ALLOW_DEVICE_CONFIGURATION | CSR_ALLOW_ANY_RECOVERY_ 9:823 0:000 Filtering KextPatches: 9:823 0:000 - [00]: AppleAHCIPort (External icons patch) :: BinPatch :: [OS: 10.13.1 | MatchOS: All | MatchBuild: All] ==> allowed 9:823 0:000 - [01]: AppleAHCIPort (fix IO error ICH10 for 10.13, credit SunKi) :: BinPatch :: [OS: 10.13.1 | MatchOS: 10.13.x | MatchBuild: All] ==> allowed 9:823 0:000 - [02]: AppleAHCIPort (fix hotplug ICH10 for 10.13, credit SunKi) :: BinPatch :: [OS: 10.13.1 | MatchOS: 10.13.x | MatchBuild: All] ==> allowed 9:823 0:000 - [03]: IOAHCIBlockStorage (TRIM Enabler) :: BinPatch :: [OS: 10.13.1 | MatchOS: All | MatchBuild: All] ==> allowed 9:823 0:000 Will not patch boot.efi 9:823 0:000 === [ PatchSmbios ] ======================================= 9:823 0:000 insert table 9 for dev 0:0 9:823 0:000 insert table 9 for dev 0:1 9:823 0:000 insert table 9 for dev 0:0 9:823 0:000 insert table 9 for dev 0:0 9:824 0:000 Channels: 2 9:824 0:000 Interleave: 0 2 1 3 4 6 5 7 8 10 9 11 12 14 13 15 16 18 17 19 20 22 21 23 9:824 0:000 SMBIOS Type 17 Index = 0 => 0 0: 9:824 0:000 BANK 0 DIMM0 1333MHz 2048MB 9:824 0:000 SMBIOS Type 17 Index = 1 => 2 2: 9:824 0:000 BANK 1 DIMM0 1333MHz 2048MB 9:824 0:000 SMBIOS Type 17 Index = 2 => 1 1: 9:824 0:000 BANK 0 DIMM1 1600MHz 4096MB 9:824 0:000 SMBIOS Type 17 Index = 3 => 3 3: 9:824 0:000 BANK 1 DIMM1 EMPTY 9:824 0:000 mTotalSystemMemory = 8192 9:824 0:000 NumberOfMemoryDevices = 4 9:824 0:000 Type20[0]->End = 0x1FFFFF, Type17[0] = 0x800 9:824 0:000 Type20[1]->End = 0x5FFFFF, Type17[2] = 0x2800 9:824 0:000 Type20[3]->End = 0x0, Type17[1] = 0x3800 9:824 0:000 === [ PatchACPI ] ========================================= 9:824 0:000 RSDT 0xDF7D1040 9:824 0:000 FADT from RSDT: 0xDF7D1100 9:824 0:000 Xsdt is not found! Creating new one 9:824 0:000 RsdPointer is Acpi 1.0 - creating new one Acpi 2.0 9:824 0:000 RsdPointer Acpi 2.0 installed 9:824 0:000 RSDT entries = 8 9:824 0:000 Xsdt reallocation done 9:824 0:000 old FADT length=74 9:824 0:000 Found OperationRegion(SMOD, SystemMemory, FF840, ...) 9:824 0:000 Found OperationRegion(LBOC, SystemMemory, FF820, ...) 9:824 0:000 Found OperationRegion(RCRB, SystemMemory, FED1C000, ...) 9:824 0:000 Found OperationRegion(ELKM, SystemMemory, FFFEA, ...) 9:824 0:000 Found OperationRegion(EXTM, SystemMemory, FF830, ...) 9:824 0:000 Found OperationRegion(INFO, SystemMemory, FF840, ...) 9:824 0:000 Apply DsdtFixMask=0x1B6EF1DF 9:824 0:000 drop _DSM mask=0x0000 9:824 0:000 === [ FixBiosDsdt ] ======================================= 9:824 0:000 VideoCard devID=0x68B81002 9:824 0:000 DisplayADR1[0] = 0x30000, DisplayADR2[0] = 0x0 9:824 0:000 USBADR[0] = 0x1A0000 and PCIe = 0xFFFE 9:824 0:000 USBADR[1] = 0x1A0001 and PCIe = 0xFFFE 9:824 0:000 USBADR[2] = 0x1A0002 and PCIe = 0xFFFE 9:824 0:000 USBADR[3] = 0x1A0007 and PCIe = 0xFFFE 9:838 0:013 Audio HDA (addr:0x1B0000) setting specified layout-id=1 (0x1) 9:838 0:000 USBADR[4] = 0x1C0002 and PCIe = 0x0 9:838 0:000 Found Airport Atheros at 0x1C0003, 0x0, DeviceID=0x002E 9:838 0:000 USBADR[5] = 0x1D0000 and PCIe = 0xFFFE 9:838 0:000 USBADR[6] = 0x1D0001 and PCIe = 0xFFFE 9:838 0:000 USBADR[7] = 0x1D0002 and PCIe = 0xFFFE 9:838 0:000 USBADR[8] = 0x1D0003 and PCIe = 0xFFFE 9:838 0:000 USBADR[9] = 0x1D0007 and PCIe = 0xFFFE 9:838 0:000 USBADR[10] = 0x1E0000 and PCIe = 0x40000 9:838 0:000 USBADR[11] = 0x1E0000 and PCIe = 0x40002 9:839 0:000 first CPU found at 2C offset 2F 9:839 0:000 slash found 9:839 0:000 Found ACPI CPU: CPU0 | CPU1 | CPU2 | CPU3 | CPU4 | CPU5 | CPU6 | CPU7 , within the score: _PR_ 9:839 0:000 Found PCIROOTUID = 0 9:839 0:000 Start RTC Fix 9:839 0:000 found RTC Length not match, Maybe will cause CMOS reset will patch it. 9:839 0:000 found RTC had IRQNoFlag will move -3 bytes 9:839 0:000 ...len=4301 9:839 0:000 new size written to 209D shift=0 len=4301 9:839 0:000 len after correct outers 4301 9:839 0:000 Start TMR Fix 9:839 0:000 Start PIC Fix 9:839 0:000 PIC size=2B at 1F44 9:839 0:000 found PIC had IRQNoFlag will move -3 bytes 9:839 0:000 Fix Device PIC size -3 9:839 0:000 Start HPET Fix 9:839 0:000 Start Display0 Fix 9:839 0:000 add device PEG0 9:839 0:000 add device GFX0 9:839 0:000 Creating Method(_DSM) for 1002 card 9:839 0:000 now inserting Video device 9:839 0:000 ... into created bridge 9:839 0:000 patch Display #0 of Vendor=0x1002 9:839 0:000 Start NetWork Fix 9:839 0:000 have no Network device while NetworkADR2=0 9:839 0:000 NetworkADR1=1C0001 NetworkADR2=0 9:839 0:000 network DSM created, size=78 9:839 0:000 Start Airport Fix 9:839 0:000 AirportADR=132C add patch size=A5 9:839 0:000 adr 132C size of arpt=E8 9:839 0:000 Start SBUS Fix PCI=701 len=4425 9:839 0:000 device (SBUS) found at 3AFF 9:839 0:000 SBUS code size fix = 0x0000005E 9:839 0:000 patch HDEF in DSDT 9:839 0:000 Start HDA Fix 9:840 0:000 found HDA device NAME(_ADR,0x001B0000) And Name is AZAL 9:840 0:000 Name AZAL present at 0x624, renaming to HDEF 9:840 0:000 Name AZAL present at 0x3B99, renaming to HDEF 9:840 0:000 Start Add MCHC 9:840 0:000 Start Add IMEI 9:840 0:000 Start HDMI1757 Fix 9:840 0:000 have no HDMI device while HDMIADR2=1 9:840 0:000 HDMIADR1=30000 HDMIADR2=1 9:840 0:000 with default properties 9:840 0:000 Start USB Fix 9:840 0:000 USB bridge[1A0000] at 2DD7, size = 31 9:840 0:000 USB bridge[1A0001] at 2E68, size = 31 9:840 0:000 USB bridge[1A0002] at 2EF9, size = 31 9:840 0:000 USB bridge[1A0007] at 2FBD, size = 31 9:841 0:000 USB bridge[1C0002] at 1242, size = E8 9:841 0:000 USB bridge[1D0000] at 2DFC, size = 31 9:841 0:000 USB bridge[1D0001] at 2E8D, size = 31 9:841 0:000 USB bridge[1D0002] at 2F1E, size = 31 9:841 0:000 USB bridge[1D0003] at 2FAF, size = 31 9:841 0:000 USB bridge[1D0007] at 31F3, size = 31 9:841 0:000 USB bridge[1E0000] at 1954, size = 2E5 9:841 0:000 _DSM already exists, patch USB will not be applied 9:842 0:000 USB bridge[1E0000] at 1954, size = 2E5 9:842 0:000 Start _WAK Return Fix 9:842 0:000 _WAK Method need return data, will patch it. 9:842 0:000 return len=4A49 9:842 0:000 deleting device CRT_ 9:842 0:000 deleting device DVI_ 9:842 0:000 deleting device SPKR 9:842 0:000 deleting device ECP_ 9:842 0:000 deleting device LPT_ 9:842 0:000 deleting device FDC0 9:842 0:000 deleting device ECP1 9:842 0:000 deleting device LPT1 9:842 0:000 Start PNLF Fix 9:842 0:000 found PWRB at 6FF 9:842 0:000 Start _S3D Fix 9:843 0:000 Start Darwin Fix 9:843 0:000 Name _OSI present at 0x2059, renaming to OOSI 9:843 0:000 Name _OSI present at 0x2065, renaming to OOSI 9:843 0:000 Name _OSI present at 0x2090, renaming to OOSI 9:843 0:000 Name _OSI present at 0x20A5, renaming to OOSI 9:843 0:000 Name _OSI present at 0x20DC, renaming to OOSI 9:843 0:000 Name _OSI present at 0x20E4, renaming to OOSI 9:843 0:000 Name _OSI present at 0x20F9, renaming to OOSI 9:843 0:000 Start SHUTDOWN Fix len=44FE 9:843 0:000 === [ ACPIDropTables ] ==================================== 9:843 0:000 === [ PatchAllSSDT ] ====================================== 9:843 0:000 Patch table: SSDT PPM RCM len=0x1C34 9:843 0:000 Drop tables from Xsdt, SIGN=XXXX TableID= Length=0 9:843 0:000 Xsdt has tables count=8 9:843 0:000 CPUBase=0 and ApicCPUBase=0 ApicCPUNum=8 9:843 0:000 Maximum control=0x14 9:843 0:000 Turbo control=0x18 9:843 0:000 P-States: min 0x9, max 0x18 9:843 0:000 SSDT with CPU P-States generated successfully 9:843 0:000 SSDT with CPU C-States generated successfully 9:843 0:000 === [ RestSetup macOS ] =================================== 9:843 0:000 EdidDiscovered size=128 9:843 0:000 ------- EDID Table 9:843 0:000 000 | 00 FF FF FF FF FF FF 00 10 AC 9:843 0:000 010 | 2B A0 53 57 31 31 09 12 01 04 9:843 0:000 020 | A5 34 20 78 22 B3 25 AC 51 30 9:843 0:000 030 | B4 26 10 50 54 A5 4B 00 81 80 9:843 0:000 040 | A9 40 71 4F 01 01 01 01 01 01 9:843 0:000 050 | 01 01 01 01 28 3C 80 A0 70 B0 9:843 0:000 060 | 23 40 30 20 36 00 07 40 21 00 9:843 0:000 070 | 00 1A 00 00 00 FF 00 44 50 30 9:843 0:000 080 | 32 39 38 32 4F 31 31 57 53 0A 9:843 0:000 090 | 00 00 00 FC 00 44 45 4C 4C 20 9:843 0:000 100 | 32 34 30 38 57 46 50 0A 00 00 9:843 0:000 110 | 00 FD 00 38 4C 1E 53 11 01 0A 9:843 0:000 120 | 20 20 20 20 20 20 00 AD 9:843 0:000 Framebuffer @0xE0000000 MMIO @0xFBBC0000 I/O Port @0x0000EE00 ROM Addr @0x00000000 9:843 0:000 PCI region 1 = 0x00000000, region3 = 0x00000000, region5 = 0x00000000 9:843 0:000 BIOS_0_SCRATCH=0x00000004, 1=0x000000FF, 2=0x00000000, 3=0x00000000, 4=0x00000000, 5=0x00000000, 6=0x00000000 9:843 0:000 RADEON_CRTC2_GEN_CNTL == 0x00000000 9:843 0:000 card posted because CONFIG_MEMSIZE=0x400 9:843 0:000 ATI card POSTed, 9:843 0:000 Set VRAM for Juniper =1024Mb 9:843 0:000 ATI: get_vram_size returned 0x40000000 9:843 0:000 ATI Radeon EVERGREEN+ family 9:843 0:000 Users config name Vervet 9:843 0:000 use N ports setting from config.plist: 4 9:843 0:000 (AtiPorts) Nr of ports set to: 4 9:843 0:000 ATI Juniper ATI Radeon HD 5770 Series 1024MB (Vervet) [1002:68B8] (subsys [1682:2991]):: PcieRoot(0x0)\Pci(0x3,0x0)\Pci(0x0,0x0) 9:843 0:000 setting specified layout-id=1 (0x1) 9:844 0:000 stringlength = 7914 9:844 0:000 CurrentMode: Width=1920 Height=1200 9:844 0:000 Beginning FSInjection FSInjectionInstall ... - Our FSI_SIMPLE_FILE_SYSTEM_PROTOCOL installed on handle: DECFD898 FSInjectionInstall ... - Our FSI_SIMPLE_FILE_SYSTEM_PROTOCOL installed on handle: DECFD898 9:844 0:000 Use origin smbios table type 1 guid. 9:845 0:000 Preparing kexts injection for arch=x86_64 from EFI\CLOVER\kexts\Other 9:845 0:000 Extra kext: EFI\CLOVER\kexts\Other\RealtekRTL8111.kext 9:854 0:009 Extra kext: EFI\CLOVER\kexts\Other\FakeSMC.kext 9:859 0:004 |-- PlugIn kext: EFI\CLOVER\kexts\Other\FakeSMC.kext\Contents\PlugIns\LPCSensors.kext 9:890 0:030 |-- PlugIn kext: EFI\CLOVER\kexts\Other\FakeSMC.kext\Contents\PlugIns\GPUSensors.kext 9:896 0:006 |-- PlugIn kext: EFI\CLOVER\kexts\Other\FakeSMC.kext\Contents\PlugIns\CPUSensors.kext 9:899 0:003 Custom boot is disabled Preboot log from official Clover r4259 (pre-compiled by @Slice using XCODE5 TC, downloaded from SourceForge) ---> Red Screen, doesn't make it past selecting OS X volume from GUI... 0:100 0:100 MemLog inited, TSC freq: 2664776353 0:100 0:000 LegacyRegion2: Chipset/proc: 0xD1318086 0:100 0:000 Core i7 processors (PAM 0x40-0x47) 0:100 0:000 Test PAM1=(0x41=11, 0x5a=00, 0x81=0D, 0x91=21) at chipset D1318086 0:100 0:000 , Install = Success 0:112 0:012 BiosVideoDriverBindingStart! 0:112 0:000 BiosVideoCheckForVbe 0:112 0:000 EdidOverride not found 0:145 0:033 Edid1+ 0:145 0:000 found Detail Timing 1920x1200 0:178 0:033 Edid0+ 0:178 0:000 found Detail Timing 1920x1200 0:178 0:000 ... already present 0:186 0:007 0 1152x864 attr=BB - ok, edid+, working, highest, pref=0 0:186 0:000 1 1280x960 attr=BB - ok, edid- 0:186 0:000 2 640x480 attr=BB - ok, edid+, 640x480, working 0:187 0:000 3 800x600 attr=BB - ok, edid+, 800x600, working 0:187 0:000 4 1024x768 attr=BB - ok, edid+, 1024x768, working 0:187 0:000 5 1280x1024 attr=BB - ok, edid+, working, highest, pref=5 0:188 0:001 6 1400x1050 attr=BB - ok, edid- 0:190 0:001 7 1600x1200 attr=BB - ok, edid+, working, highest, pref=7 0:194 0:004 BV new mode: 7 1600x1200 0:424 0:229 SetMode pref 7 (7) = Success 7:320 6:895 7:320 0:000 Now is 25.10.2017, 23:42:45 (GMT) 7:320 0:000 Starting Clover revision: 4259 on CLOVER EFI 7:320 0:000 Build with: [Args: -D NO_GRUB_DRIVERS_EMBEDDED | -D NO_GRUB_DRIVERS_EMBEDDED -D USE_LOW_EBDA -a X64 -b RELEASE -t XCODE5 -n 5 | OS: 10.12.6 | XCODE: 9.0.1] 7:320 0:000 SelfDevicePath=PcieRoot(0x0)\Pci(0x1A,0x7)\USB(0x2,0x0)\HD(1,MBR,0xDDF06EF8,0x80,0xF3800) @DDC19698 7:320 0:000 SelfDirPath = \EFI\CLOVER 7:320 0:000 === [ Get Smbios ] ======================================== 7:320 0:000 Type 16 Index = 0 7:320 0:000 Total Memory Slots Count = 4 7:320 0:000 Type 17 Index = 0 7:320 0:000 SmbiosTable.Type17->Speed = 1333MHz 7:320 0:000 SmbiosTable.Type17->Size = 2048MB 7:320 0:000 SmbiosTable.Type17->Bank/Device = Bank0/1 A0 7:320 0:000 SmbiosTable.Type17->Vendor = 7:320 0:000 SmbiosTable.Type17->SerialNumber = 7:320 0:000 SmbiosTable.Type17->PartNumber = 7:320 0:000 Type 17 Index = 1 7:320 0:000 SmbiosTable.Type17->Speed = 1333MHz 7:320 0:000 SmbiosTable.Type17->Size = 4096MB 7:320 0:000 SmbiosTable.Type17->Bank/Device = Bank2/3 A1 7:320 0:000 SmbiosTable.Type17->Vendor = 7:320 0:000 SmbiosTable.Type17->SerialNumber = 7:320 0:000 SmbiosTable.Type17->PartNumber = 7:320 0:000 Type 17 Index = 2 7:320 0:000 SmbiosTable.Type17->Speed = 1333MHz 7:320 0:000 SmbiosTable.Type17->Size = 2048MB 7:320 0:000 SmbiosTable.Type17->Bank/Device = Bank4/5 A2 7:320 0:000 SmbiosTable.Type17->Vendor = 7:320 0:000 SmbiosTable.Type17->SerialNumber = 7:320 0:000 SmbiosTable.Type17->PartNumber = 7:320 0:000 Type 17 Index = 3 7:320 0:000 Ignoring insane frequency value 0MHz 7:320 0:000 SmbiosTable.Type17->Speed = 0MHz 7:320 0:000 SmbiosTable.Type17->Size = 0MB 7:320 0:000 SmbiosTable.Type17->Bank/Device = Bank6/7 A3 7:320 0:000 SmbiosTable.Type17->Vendor = <null string> 7:320 0:000 SmbiosTable.Type17->SerialNumber = <null string> 7:320 0:000 SmbiosTable.Type17->PartNumber = <null string> 7:320 0:000 Boot status=0 7:320 0:000 Running on: 'P55A-UD3' with board 'P55A-UD3' 7:320 0:000 === [ GetCPUProperties ] ================================== 7:320 0:000 CPU Vendor = 756E6547 Model=106E5 7:320 0:000 The CPU supported SSE4.1 7:320 0:000 BrandString = Intel® Core i5 CPU 750 @ 2.67GHz 7:320 0:000 The CPU supported turbo 7:320 0:000 MSR 0x35 40004 7:320 0:000 FSBFrequency = 140 MHz, DMI FSBFrequency = 133 MHz, Corrected FSBFrequency = 133 MHz 7:320 0:000 MaxDiv/MinDiv: 20.0/9 7:320 0:000 Turbo: 21/21/24/24 7:320 0:000 Features: 0xBFEBFBFF 7:320 0:000 Threads: 4 7:320 0:000 Cores: 4 7:320 0:000 FSB: 133 MHz 7:320 0:000 CPU: 2800 MHz 7:320 0:000 TSC: 2800 MHz 7:320 0:000 PIS: 533 MHz 7:320 0:000 ExternalClock: 133 MHz 7:320 0:000 === [ GetDevices ] ======================================== 7:320 0:000 PCI (00|00:00.00) : 8086 D131 class=060000 7:320 0:000 PCI (00|00:03.00) : 8086 D138 class=060400 7:320 0:000 PCI (00|01:00.00) : 1002 68B8 class=030000 7:320 0:000 - GFX: Model=ATI Radeon HD 5770 Series (ATI/AMD) 7:320 0:000 PCI (00|01:00.01) : 1002 AA58 class=040300 7:320 0:000 - HDMI Audio: 7:320 0:000 PCI (00|00:08.00) : 8086 D155 class=088000 7:320 0:000 PCI (00|00:08.01) : 8086 D156 class=088000 7:320 0:000 PCI (00|00:08.02) : 8086 D157 class=088000 7:320 0:000 PCI (00|00:08.03) : 8086 D158 class=088000 7:320 0:000 PCI (00|00:10.00) : 8086 D150 class=088000 7:320 0:000 PCI (00|00:10.01) : 8086 D151 class=088000 7:320 0:000 PCI (00|00:1A.00) : 8086 3B3B class=0C0300 7:320 0:000 PCI (00|00:1A.01) : 8086 3B3E class=0C0300 7:320 0:000 PCI (00|00:1A.02) : 8086 3B3F class=0C0300 7:320 0:000 PCI (00|00:1A.07) : 8086 3B3C class=0C0320 7:320 0:000 PCI (00|00:1B.00) : 8086 3B56 class=040300 7:320 0:000 PCI (00|00:1C.00) : 8086 3B42 class=060400 7:320 0:000 PCI (00|02:00.00) : 1B4B 9128 class=010601 7:320 0:000 PCI (00|00:1C.01) : 8086 3B44 class=060400 7:320 0:000 PCI (00|03:00.00) : 10EC 8168 class=020000 7:320 0:000 - LAN: 0 Vendor=Realtek 7:320 0:000 PCI (00|00:1C.02) : 8086 3B46 class=060400 7:320 0:000 PCI (00|04:00.00) : 1033 0194 class=0C0330 7:320 0:000 PCI (00|00:1C.03) : 8086 3B48 class=060400 7:320 0:000 PCI (00|05:00.00) : 168C 002E class=028000 7:320 0:000 - WIFI: Vendor=Atheros 7:320 0:000 PCI (00|00:1D.00) : 8086 3B36 class=0C0300 7:320 0:000 PCI (00|00:1D.01) : 8086 3B37 class=0C0300 7:320 0:000 PCI (00|00:1D.02) : 8086 3B38 class=0C0300 7:320 0:000 PCI (00|00:1D.03) : 8086 3B39 class=0C0300 7:320 0:000 PCI (00|00:1D.07) : 8086 3B34 class=0C0320 7:320 0:000 PCI (00|00:1E.00) : 8086 244E class=060401 7:320 0:000 PCI (00|06:04.00) : 1106 3038 class=0C0300 7:320 0:000 PCI (00|06:04.02) : 1106 3104 class=0C0320 7:320 0:000 PCI (00|06:05.00) : 1283 8213 class=010185 7:320 0:000 PCI (00|00:1F.00) : 8086 3B02 class=060100 7:320 0:000 PCI (00|00:1F.02) : 8086 3B22 class=010601 7:320 0:000 PCI (00|00:1F.03) : 8086 3B30 class=0C0500 7:320 0:000 PCI (00|3F:00.00) : 8086 2C51 class=060000 7:320 0:000 PCI (00|3F:00.01) : 8086 2C81 class=060000 7:320 0:000 PCI (00|3F:02.00) : 8086 2C90 class=060000 7:320 0:000 PCI (00|3F:02.01) : 8086 2C91 class=060000 7:320 0:000 PCI (00|3F:03.00) : 8086 2C98 class=060000 7:320 0:000 PCI (00|3F:03.01) : 8086 2C99 class=060000 7:320 0:000 PCI (00|3F:03.04) : 8086 2C9C class=060000 7:320 0:000 PCI (00|3F:04.00) : 8086 2CA0 class=060000 7:320 0:000 PCI (00|3F:04.01) : 8086 2CA1 class=060000 7:320 0:000 PCI (00|3F:04.02) : 8086 2CA2 class=060000 7:320 0:000 PCI (00|3F:04.03) : 8086 2CA3 class=060000 7:320 0:000 PCI (00|3F:05.00) : 8086 2CA8 class=060000 7:320 0:000 PCI (00|3F:05.01) : 8086 2CA9 class=060000 7:321 0:000 PCI (00|3F:05.02) : 8086 2CAA class=060000 7:321 0:000 PCI (00|3F:05.03) : 8086 2CAB class=060000 7:321 0:000 === [ GetDefaultSettings ] ================================ 7:321 0:000 Clover load options size = 0 bytes 7:362 0:041 EFI\CLOVER\config.plist loaded: Success 7:362 0:000 === [ GetListOfThemes ] =================================== 7:402 0:039 - [00]: BGM 7:483 0:081 - [01]: embedded 7:511 0:027 - [01]: random 7:539 0:028 === [ Found config plists ] =============================== 7:539 0:000 - config.plist 7:552 0:012 - config_null.plist 7:552 0:000 - config14,2.plist 7:552 0:000 === [ GetEarlyUserSettings ] ============================== 7:552 0:000 timeout set to 3 7:552 0:000 Custom boot CUSTOM_BOOT_DISABLED (0x0) 7:552 0:000 KextsToPatch: 4 requested 7:552 0:000 - [00]: AppleAHCIPort (External icons patch) :: BinPatch :: data len: 8 7:552 0:000 - [01]: AppleAHCIPort (fix IO error ICH10 for 10.13, credit SunKi) :: MatchOS: 10.13.x :: BinPatch :: data len: 20 7:552 0:000 - [02]: AppleAHCIPort (fix hotplug ICH10 for 10.13, credit SunKi) :: MatchOS: 10.13.x :: BinPatch :: data len: 26 7:552 0:000 - [03]: IOAHCIBlockStorage (TRIM Enabler) :: BinPatch :: data len: 11 7:552 0:000 Default theme: BGM 7:552 0:000 Hiding entries with string bootmgr.efi 7:552 0:000 === [ LoadDrivers ] ======================================= 7:566 0:013 Loading AppleImageCodec-64.efi status=Success 7:592 0:026 Loading AppleKeyAggregator-64.efi status=Success 7:606 0:014 Loading AppleUITheme-64.efi status=Success 7:606 0:000 Loading FirmwareVolume-64.efi status=Success 7:620 0:014 Loading FSInject-64.efi status=Success 7:649 0:028 Loading apfs-64.efi status=Success 7:762 0:113 - driver needs connecting 7:762 0:000 Loading PartitionDxe-64.efi status=Success 7:790 0:028 - driver needs connecting 7:790 0:000 Loading SMCHelper-64.efi status=Success 7:804 0:014 Loading GrubUDF-64.efi status=Success 7:818 0:014 - driver needs connecting 7:818 0:000 Loading HFSPlus-64.efi status=Success 7:832 0:014 - driver needs connecting 7:832 0:000 Loading NTFS-64.efi status=Success 7:860 0:028 - driver needs connecting 7:860 0:000 Loading VBoxExt4-64.efi status=Success 7:874 0:013 - driver needs connecting 7:874 0:000 Loading VBoxIso9600-64.efi status=Success 7:888 0:014 - driver needs connecting 7:888 0:000 Video bios patch requested or CustomEDID - forcing video reconnect 7:888 0:000 8 drivers needs connecting ... 7:888 0:000 PlatformDriverOverrideProtocol->GetDriver overriden 7:888 0:000 Partition driver loaded: CD disconnect Success 7:888 0:000 HFS+ driver loaded 7:888 0:000 APFS driver loaded 7:889 0:000 Video driver loaded: disconnect Success 8:036 0:147 VideoBiosPatchNativeFromEdid: 8:036 0:000 Bios: ATI, MasterDataTables: 0xCA758, std_vesa: 0xCA79C, ati_mode_table: 0xCA7A0, mode_table_size: 0x1F8 BT_ATI_2 8:036 0:000 VideoBiosPatchInit(LegacyRegion = Not Found, LegacyRegion2 = Success) = Success 8:036 0:000 VideoBiosUnlock: unlocked 8:036 0:000 Patching: BT_ATI_2 8:036 0:000 Parse Edid: descriptor block 0 is timing descriptor (h_active: 1920, v_active: 1200, h_sync_offset: 48, h_sync_width: 32, h_blanking: 160, v_blanking: 35, pixel_clock: 15400, v_sync_offset: 3, v_sync_width: 6) 8:036 0:000 mode 0 (320x200) patched to 1920x1200 8:036 0:000 VideoBiosLock: Success 8:050 0:013 BiosVideoDriverBindingStart! 8:050 0:000 BiosVideoCheckForVbe 8:050 0:000 EdidOverride not found 8:083 0:033 Edid1+ 8:083 0:000 found Detail Timing 1920x1200 8:116 0:033 Edid0+ 8:116 0:000 found Detail Timing 1920x1200 8:116 0:000 ... already present 8:120 0:004 0 1920x1200 attr=BB - ok, edid+, working, highest, pref=0 8:124 0:003 1 1152x864 attr=BB - ok, edid+, working 8:125 0:000 2 1280x960 attr=BB - ok, edid- 8:125 0:000 3 640x480 attr=BB - ok, edid+, 640x480, working 8:125 0:000 4 800x600 attr=BB - ok, edid+, 800x600, working 8:125 0:000 5 1024x768 attr=BB - ok, edid+, 1024x768, working 8:125 0:000 6 1280x1024 attr=BB - ok, edid+, working 8:127 0:001 7 1400x1050 attr=BB - ok, edid- 8:128 0:001 8 1600x1200 attr=BB - ok, edid+, working 8:132 0:004 BV new mode: 0 1920x1200 8:370 0:237 SetMode pref 0 (0) = Success 11:598 3:227 === [ InitScreen ] ======================================== 11:598 0:000 SetScreenResolution: 1920x1080 - not found! 11:598 0:000 Console modes reported: 4, available modes: 11:598 0:000 - [01]: 80x25 11:598 0:000 - [02]: 80x50 11:598 0:000 - [03]: 100x31 11:598 0:000 - [04]: 240x63 (current mode) 11:598 0:000 SetScreenResolution: 1920x1200 - already set 11:598 0:000 reinit: self device path=PcieRoot(0x0)\Pci(0x1A,0x7)\USB(0x2,0x0)\HD(1,MBR,0xDDF06EF8,0x80,0xF3800) 11:598 0:000 Using embedded font: Success 11:600 0:002 === [ GetMacAddress ] ===================================== 11:600 0:000 === [ ScanSPD ] =========================================== 11:601 0:000 SMBus device : 8086 3B30 class=0C0500 status=Success 11:601 0:000 SMBus CmdReg: 0x3 11:601 0:000 Scanning SMBus [8086:3B30], mmio: 0xFBFFC004, ioport: 0x500, hostc: 0x1 11:601 0:000 Slots to scan [8]... 11:601 0:000 SPD[0]: Type 11 @0x50 11:620 0:018 DDR speed 1333MHz 11:620 0:000 Slot: 0 Type 24 2048MB 1333MHz Vendor=Kingston PartNo=99U5458-001.A00LF SerialNo=0704020800070002 11:620 0:000 SPD[1]: Type 11 @0x51 11:639 0:018 DDR speed 1600MHz 11:639 0:000 Slot: 1 Type 24 4096MB 1600MHz Vendor=SK Hynix PartNo=HMT351U6CFR8C-PBN0 SerialNo=0005060606020A05 11:640 0:000 SPD[2]: Type 11 @0x52 11:658 0:018 DDR speed 1333MHz 11:658 0:000 Slot: 2 Type 24 2048MB 1333MHz Vendor=Kingston PartNo=99U5458-001.A00LF SerialNo=070A02080F040001 11:659 0:000 === [ GetAcpiTablesList ] ================================= 11:666 0:007 Get Acpi Tables List from RSDT: 11:666 0:000 - [00]: FACP GBTUACPI len=116 11:666 0:000 - [01]: HPET GBTUACPI len=56 11:666 0:000 - [02]: MCFG GBTUACPI len=60 11:666 0:000 - [03]: EUDS len=1376 11:666 0:000 - [04]: TAMG GBT B0 len=2610 11:666 0:000 - [05]: APIC GBTUACPI len=188 11:666 0:000 - [06]: SLIC SLIC-MPC len=374 11:666 0:000 - [07]: SSDT PPM RCM len=7220 11:666 0:000 Calibrated TSC Frequency = 2664776353 = 2664MHz 11:667 0:000 === [ GetUserSettings ] =================================== 11:667 0:000 USB FixOwnership: yes 11:667 0:000 Dropping 3 tables: 11:667 0:000 - [00]: Drop table signature="DMAR" (52414D44) 11:667 0:000 - set table: 52414D44, 0 to drop: no 11:667 0:000 - [01]: Drop table signature="SSDT" (54445353) table-id="CpuPm" (0000006D50757043) 11:667 0:000 - set table: 54445353, 6D50757043 to drop: no 11:667 0:000 - [02]: Drop table signature="SSDT" (54445353) table-id="Cpu0Ist" (0074734930757043) 11:667 0:000 - set table: 54445353, 74734930757043 to drop: no 11:667 0:000 - final DSDT Fix mask=1B6EF1DF 11:667 0:000 Using ProductName from config 11:667 0:000 ProductName: iMac11,3 11:667 0:000 BiosVersion: not set, Using BiosVersion from clover 11:667 0:000 BiosVersion: IM112.88Z.005B.B00.1708080439 11:667 0:000 BiosReleaseDate: 08/08/17 11:667 0:000 Using FirmwareFeatures from config 11:667 0:000 FirmwareFeatures: 0xE00DE137 11:667 0:000 Using FirmwareFeaturesMask from config 11:667 0:000 FirmwareFeaturesMask: 0xFF1FFF3F 11:667 0:000 PlatformFeature will not set in SMBIOS 11:667 0:000 PlatformFeature: 0xFFFF 11:667 0:000 Converted CustomUUID 9ecdd6b2-3d1a-8450-8a9a-130759752ccf 11:862 0:194 === [ ScanVolumes ] ======================================= 11:862 0:000 Found 23 volumes with blockIO 11:862 0:000 - [00]: Volume: PcieRoot(0x0)\Pci(0x1A,0x7)\USB(0x2,0x0) 11:873 0:011 Result of bootcode detection: bootable unknown (legacy) 11:873 0:000 USB volume 11:873 0:000 - [01]: Volume: PcieRoot(0x0)\Pci(0x1A,0x7)\USB(0x2,0x0)\HD(1,MBR,0xDDF06EF8,0x80,0xF3800) 11:885 0:011 Result of bootcode detection: bootable unknown (legacy) 11:885 0:000 USB volume 11:899 0:014 This is SelfVolume !! 11:899 0:000 - [02]: Volume: PcieRoot(0x0)\Pci(0x1D,0x7)\USB(0x0,0x0)\Unit(0x0) 11:899 0:000 USB volume 11:899 0:000 - [03]: Volume: PcieRoot(0x0)\Pci(0x1D,0x7)\USB(0x0,0x0)\Unit(0x1) 11:899 0:000 USB volume 11:899 0:000 - [04]: Volume: PcieRoot(0x0)\Pci(0x1D,0x7)\USB(0x0,0x0)\Unit(0x2) 11:899 0:000 USB volume 11:899 0:000 - [05]: Volume: PcieRoot(0x0)\Pci(0x1D,0x7)\USB(0x0,0x0)\Unit(0x3) 11:899 0:000 USB volume 11:899 0:000 - [06]: Volume: PcieRoot(0x0)\Pci(0x1F,0x2)\Sata(0x0,0x0,0x0) 11:901 0:002 Result of bootcode detection: bootable unknown (legacy) 11:901 0:000 - [07]: Volume: PcieRoot(0x0)\Pci(0x1F,0x2)\Sata(0x1,0x0,0x0) 11:921 0:020 Result of bootcode detection: bootable unknown (legacy) 11:921 0:000 - [08]: Volume: PcieRoot(0x0)\Pci(0x1F,0x2)\Sata(0x5,0x0,0x0) 11:922 0:000 Result of bootcode detection: bootable unknown (legacy) 11:922 0:000 - [09]: Volume: PcieRoot(0x0)\Pci(0x1F,0x2)\Sata(0x0,0x0,0x0)\HD(1,MBR,0x50CFED9B,0x800,0x32000) 11:922 0:000 Result of bootcode detection: bootable unknown (legacy) 11:923 0:000 - [10]: Volume: PcieRoot(0x0)\Pci(0x1F,0x2)\Sata(0x0,0x0,0x0)\HD(2,MBR,0x50CFED9B,0x32800,0xDF61000) 11:923 0:000 Result of bootcode detection: bootable Windows (vista,win) 11:923 0:000 - [11]: Volume: PcieRoot(0x0)\Pci(0x1F,0x2)\Sata(0x1,0x0,0x0)\HD(1,GPT,1B386756-0922-4B96-BD59-1FC3B79E189E,0x800,0x64000) 11:926 0:003 Result of bootcode detection: bootable unknown (legacy) 11:936 0:009 - [12]: Volume: PcieRoot(0x0)\Pci(0x1F,0x2)\Sata(0x1,0x0,0x0)\HD(2,GPT,55225B2F-270E-453A-88B9-E12C5D9F6F12,0x64800,0xC99A3800) 11:936 0:000 Result of bootcode detection: bootable Windows (vista,win) 11:936 0:000 - [13]: Volume: PcieRoot(0x0)\Pci(0x1F,0x2)\Sata(0x1,0x0,0x0)\HD(3,GPT,1FE507E9-E82B-43BF-8A8C-2249DFF67874,0xC9A08000,0xF8C68E0) 11:936 0:000 - [14]: Volume: PcieRoot(0x0)\Pci(0x1F,0x2)\Sata(0x1,0x0,0x0)\HD(4,GPT,06C99874-BE94-4641-9935-2BDC5778B0E9,0xD92CE8E0,0x135F20) 11:936 0:000 - [15]: Volume: PcieRoot(0x0)\Pci(0x1F,0x2)\Sata(0x1,0x0,0x0)\HD(5,GPT,A75A0F00-1C9A-40A7-9CC9-25EFEB5BA8D4,0xD9404800,0x40000) 11:936 0:000 Result of bootcode detection: bootable unknown (legacy) 11:936 0:000 - [16]: Volume: PcieRoot(0x0)\Pci(0x1F,0x2)\Sata(0x1,0x0,0x0)\HD(6,GPT,696E551C-EF37-4132-8ADD-F7E3932173C4,0xD9444800,0xF9C3800) 11:937 0:000 Result of bootcode detection: bootable Windows (vista,win) 11:937 0:000 - [17]: Volume: PcieRoot(0x0)\Pci(0x1F,0x2)\Sata(0x5,0x0,0x0)\HD(1,GPT,5BA2531C-72D6-4B9E-8519-A17EE40D1500,0x28,0x64000) 11:937 0:000 Result of bootcode detection: bootable unknown (legacy) 11:957 0:020 - [18]: Volume: PcieRoot(0x0)\Pci(0x1F,0x2)\Sata(0x5,0x0,0x0)\HD(2,GPT,685228AF-4F5E-4C8A-AA24-22FE96002F84,0x64800,0x6CEA2000) 11:965 0:007 Result of bootcode detection: bootable Windows (vista,win) 11:965 0:000 - [19]: Volume: PcieRoot(0x0)\Pci(0x1F,0x2)\Sata(0x5,0x0,0x0)\HD(3,GPT,7D80B5FA-7720-49DA-BC47-5637E5BD2009,0x6CF06800,0x40000) 11:965 0:000 - [20]: Volume: PcieRoot(0x0)\Pci(0x1F,0x2)\Sata(0x5,0x0,0x0)\HD(4,GPT,C94F3A09-FEFB-4C8C-982A-E0ACCAD515D3,0x6CF46800,0x768A668) 11:988 0:022 - [21]: Volume: PcieRoot(0x0)\Pci(0x1F,0x2)\Sata(0x5,0x0,0x0)\HD(5,GPT,623905BA-F830-4C63-900E-151E05317C0B,0x745D0E68,0x135F20) 11:998 0:010 - [22]: Volume: PcieRoot(0x0)\Pci(0x1F,0x2)\Sata(0x3,0x0,0x0) 11:998 0:000 Found optical drive 12:023 0:024 PutNvramPlistToRtVars: nvram.plist not found 12:023 0:000 === [ InitTheme ] ========================================= 12:024 0:001 Using theme 'BGM' (EFI\CLOVER\themes\BGM) 12:024 0:000 OS main and drive as badge 12:040 0:015 Loading font from ThemeDir: Success 12:040 0:000 Choosing theme BGM 12:040 0:000 after NVRAM boot-args=dart=0 kext-dev-mode=1 -lilubeta 12:040 0:000 === [ Dump SMC keys from NVRAM ] ========================== 12:040 0:000 found AppleSMC protocol 12:040 0:000 === [ AddCustomEntries ] ================================== 12:040 0:000 Custom entry 0 skipped because it is hidden. 12:040 0:000 === [ ScanLoader ] ======================================== 12:040 0:000 - [01]: 'CLOVER' 12:040 0:000 - [09]: 'SYSTEM' 12:041 0:001 AddLoaderEntry for Volume Name=SYSTEM 12:041 0:000 Not match custom entry 0: Type: not match 12:085 0:043 - [10]: 'WIN7_X64SSD' 12:087 0:002 - [11]: 'EFI' 12:105 0:018 AddLoaderEntry for Volume Name=EFI 12:106 0:000 Not match custom entry 0: Type: not match 12:108 0:002 - [12]: 'DATA_TSH' 12:113 0:004 - [13]: 'Macintosh HD' 12:162 0:048 AddLoaderEntry for Volume Name=Macintosh HD 12:162 0:000 Not match custom entry 0: Type: not match 12:169 0:007 Check if volume Is Hibernated: 12:169 0:000 Check sleep image 'by signature': 12:224 0:054 read prefs \Library\Preferences\com.apple.PowerManagement.plist status=Success 12:224 0:000 using default sleep image name = \private\var\vm\sleepimage 12:245 0:020 sleepimage not found -> Not Found 12:245 0:000 hibernated: no - sign 12:287 0:042 - [14]: 'Recovery HD' 12:287 0:000 AddLoaderEntry for Volume Name=Recovery HD 12:287 0:000 Skipped because matching custom entry 0! 12:287 0:000 - [16]: 'WIN10' 12:289 0:002 - [17]: 'EFI' 12:311 0:021 - [18]: 'DATA' 12:314 0:002 - [20]: 'macOS' 12:356 0:042 AddLoaderEntry for Volume Name=macOS 12:356 0:000 Not match custom entry 0: Type: not match 12:386 0:030 Check if volume Is Hibernated: 12:386 0:000 Check sleep image 'by signature': 12:446 0:060 read prefs \Library\Preferences\com.apple.PowerManagement.plist status=Success 12:446 0:000 using default sleep image name = \private\var\vm\sleepimage 12:489 0:043 sleepimage not found -> Not Found 12:489 0:000 hibernated: no - sign 12:504 0:015 - [21]: 'Recovery HD' 12:505 0:000 AddLoaderEntry for Volume Name=Recovery HD 12:505 0:000 Skipped because matching custom entry 0! 12:505 0:000 === [ AddCustomTool ] ===================================== 12:519 0:014 found tool \EFI\CLOVER\tools\Shell64U.efi 12:519 0:000 Checking EFI partition Volume 11 for Clover 12:519 0:000 Found Clover 12:535 0:015 === [ GetEfiBootDeviceFromNvram ] ========================= 12:535 0:000 - found entry 0. 'Boot Microsoft EFI Boot from SYSTEM', Volume 'SYSTEM', DevicePath 'PcieRoot(0x0)\Pci(0x1F,0x2)\Sata(0x0,0x0,0x0)\HD(1,MBR,0x50CFED9B,0x800,0x32000)\EFI\microsoft\Boot\bootmgfw.efii' 12:535 0:000 DefaultIndex=0 and MainMenu.EntryCount=10 13:490 0:954 GUI ready PS - Thanks for commit 4265 to revert the flag . Link to comment Share on other sites More sharing options...
TheRacerMaster Posted October 26, 2017 Share Posted October 26, 2017 I'm currently without home internet connection (might be up tomorrow, currently on my phone), will check asap. Where is that msg shown? That looks like the output of Rember (GUI frontend for memtest on macOS). 1 Link to comment Share on other sites More sharing options...
Philip Petev Posted October 26, 2017 Share Posted October 26, 2017 Building from @rehabman's GIT repo needs XCODE8 setting. Actually, RehabMan has initially adapted only this profile, but the rest can be used as well. You can build RehabMan's fork with XCODE5, GCC53, GCC49 and even the little known XCLANG (Xcode is required) profile, using the attached file. EDIT: both the XCODE32 and XCLANG profiles have been retired in favor of the XCODE5 profile almost 6 months ago. Reference: https://github.com/tianocore/edk2/commit/f7bd152c2a05bd75471305184c25f14f01ccf0b7 tools_def.txt 1 Link to comment Share on other sites More sharing options...
rotoyouoio Posted October 26, 2017 Share Posted October 26, 2017 I'm currently without home internet connection (might be up tomorrow, currently on my phone), will check asap. Where is that msg shown? this is from memtest, it's an example of the actually occupied address during the time that darwin dump was made but the problem affects all the system Link to comment Share on other sites More sharing options...
Funky frank Posted October 26, 2017 Share Posted October 26, 2017 Hi guys, trying to determine actual cpu speed in my Sierra. Installed Intel Power Gadget, but that software only crashes and does not run. Any idea how to determine the actual cpu speed? Wasn't there a kind of fakesmc extension for that? Do I need to enable the XPCM option for my haswell cpu? Background is that my system started to become maybe a bit slow since some time, maybe it's caused by the nvidia web driver or no proper cpu pm. But I have written all values into ssdt using ssdtprgen. Link to comment Share on other sites More sharing options...
apianti Posted October 26, 2017 Share Posted October 26, 2017 @rotoyouoio, Can you please give some screen shots or something? It's hard to understand what you mean from just your description, but I'll try.... What EFI drivers are you using? Are you injecting kexts? What else are you doing? The problem with X99 systems does not appear to be related to this at all unless you have drastically over complicated what you mean. The X99 problem is a boot time error where not enough contiguous free space can be allocated to place the entirety of the kernel - this is still in protected mode, not virtual so there is no address translation yet. Your error, if I understand correctly, is happening after boot services and during the kernel's runtime and appears to be a virtual address translation error. There are plenty of reasons why this could happen, moving stuff in memory after it's address has been translated, improperly translating an address, or just not translating the address at all. Need much more information, probably deeper debugging, which is hard if no developer has the issue or cannot reproduce it... EDIT: I've never even seen you say anything about this before, so there's no need to get mad. Everyone is trying to help but remember that every one here is doing this in their free time as a hobby. We don't all have lots of time to do everything, the more users a problem affects the higher priority it will have. As far as dmazar, I don't know what you mean but he's a great guy and a friend, you may find yourself not getting help at all by insulting developers who, if not for them, you would still be complaining it didn't work but for another reason. And the reason that there is no different aptiofix is because no one has created a better idea than that collaboration from projectosx, and the slight modification for aptiofix2. By all means please develop another method. 2 Link to comment Share on other sites More sharing options...
Funky frank Posted October 26, 2017 Share Posted October 26, 2017 Also another question: I now for the first time installed clover to the EFI partition and copied my config over there. It boots into the clover menu, but stuck after starting boot at "++++++++++++". All kexts from my other clover existing, including fakesmc. Also the config is properly loaded (which works fine with the no-efi-clover installation). Any idea how to fix? Link to comment Share on other sites More sharing options...
apianti Posted October 26, 2017 Share Posted October 26, 2017 Hi guys, trying to determine actual cpu speed in my Sierra. Installed Intel Power Gadget, but that software only crashes and does not run. Any idea how to determine the actual cpu speed? Wasn't there a kind of fakesmc extension for that? Do I need to enable the XPCM option for my haswell cpu? Background is that my system started to become maybe a bit slow since some time, maybe it's caused by the nvidia web driver or no proper cpu pm. But I have written all values into ssdt using ssdtprgen. I believe there is a kext to go along with ssdtprgen that you load from the terminal, let it go while you do some activities, then come back and unload it. It should have spit out all the different multipliers your CPU reached, which you can then use to determine your frequency (usually times 100MHz) Also another question: I now for the first time installed clover to the EFI partition and copied my config over there. It boots into the clover menu, but stuck after starting boot at "++++++++++++". All kexts from my other clover existing, including fakesmc. Also the config is properly loaded (which works fine with the no-efi-clover installation). Any idea how to fix? UEFI boot? Do you have an aptiofix? Link to comment Share on other sites More sharing options...
Funky frank Posted October 26, 2017 Share Posted October 26, 2017 Ah thank you! Will try that ssdtgen kext, right! I used osxlowmemfixdrv until now, it worked. Will try aptiofix now.. EDIT: Thank you so much, you saved me lot of time. That was the problem aptiofix works nicely. Link to comment Share on other sites More sharing options...
apianti Posted October 26, 2017 Share Posted October 26, 2017 Ah thank you! Will try that ssdtgen kext, right! I used osxlowmemfixdrv until now, it worked. Will try aptiofix now.. LowMemFix only works for Insyde firmware because it releases a memory region that is in the way but is non-consequential. You shouldn't use it on any other firmware, and probably not even really at all. EDIT: Thank you so much, you saved me lot of time. That was the problem aptiofix works nicely. Try to use aptiofix2 if you can first, it works better. Aptiofix as a fallback. Link to comment Share on other sites More sharing options...
Funky frank Posted October 26, 2017 Share Posted October 26, 2017 works, too Curious, what is better in aptiofix2? apianti, since I have the opportunity to have access to your knowledge, can you answer me these questions: - disk numbers in diskutil seem to be random, so boot drive sometimes is disk0, sometimes disk1, etc. Is that normal? - Should I delete HFSPlus.efi from drivers64UEFI and always use VBoxHfs-64.efi instead? - Should I delete NTFS.efi from drivers64 and always use GrubNTFS-64.efi instead? - Will a High Sierra Update wipe my efi partition config? EDIT: Installing it on a SSD, so likely there will be a APFS conversion - Should I activate KernelXCPM on my Haswell? - Are there any new options to be added to successfully boot into High Sierra (coming from Sierra)? - The bit depth of the graphics seem to be reduced to 16bit per channel, this is since the first time of Nightshift activation. Same happened with an AMD gfx card before. Even if I turn off nightshift, the reduction is visible in graphical transitions (showing a step effect). Any idea here? EDIT: - If I then boot from an APFS High Sierra SSD and will backup to an HDD using CCC, will I be still able to directly boot from the HDD (still containing HFS+)? - Does fakesmc have any effect on cpu/system performance? Link to comment Share on other sites More sharing options...
apianti Posted October 26, 2017 Share Posted October 26, 2017 works, too Curious, what is better in aptiofix2? apianti, since I have the opportunity to have access to your knowledge, can you answer me these questions: Aptiofix2 does not relocate anything in memory so it should not interfere with anything, whereas for some reason aptiofix does interfere. Aptiofix can break firmware runtime, like nvram. - disk numbers in diskutil seem to be random, so boot drive sometimes is disk0, sometimes disk1, etc. Is that normal? Yes, it is the order they are enumerated, one disk may be busy and take longer to respond although it comes first in actual order. Those are just identifiers for the kernel for that boot, they no longer matter after restart/shutdown. That's why everything is identified by the partition identifier. - Should I delete HFSPlus.efi from drivers64UEFI and always use VBoxHfs-64.efi instead? That's your preference. VBoxHFS is open source but lacks features (it's slightly slower as well), however it seems to work better with some misbehaving firmwares. HFSPlus is closed source driver extracted from Apple firmware, it's fast and has more features, such as core storage RAID support and filevault. - Should I delete NTFS.efi from drivers64 and always use GrubNTFS-64.efi instead? You do not need an NTFS driver at all. Windows boots from the EFI partition so can be read directly from the firmware already. If there is any reason to have one I do not know what it is. - Will a High Sierra Update wipe my efi partition config? EDIT: Installing it on a SSD, so likely there will be a APFS conversion Good question, I'm not sure but I see no reason why it would touch the EFI partition. I haven't seen or heard of it. - Should I activate KernelXCPM on my Haswell? Can you boot without it/other patches? Is your power management working? Have you tried? Does it work? Does it give better performance? Beats me. - Are there any new options to be added to successfully boot into High Sierra (coming from Sierra)? Not that I'm aware of but it could be different depending on your hardware and kexts. - The bit depth of the graphics seem to be reduced to 16bit per channel, this is since the first time of Nightshift activation. Same happened with an AMD gfx card before. Even if I turn off nightshift, the reduction is visible in graphical transitions (showing a step effect). Any idea here? Might have something to do with injecting the wrong properties for the graphics, I am unsure how to even check that. Maybe check out ioreg for anything interesting. - If I then boot from an APFS High Sierra SSD and will backup to an HDD using CCC, will I be still able to directly boot from the HDD (still containing HFS+)? An APFS partition is a container and has another structure inside that contains the volumes like recovery, system, etc. It would not back up properly to a HFS+ partition. So probably no, but maybe it does something to convert either the HFS+ to an APFS or the APFS content to work on the HFS+. Really no idea... - Does fakesmc have any effect on cpu/system performance? Not anything meaningful, and not anymore than an actual SMC being present would. FakeSMC is just using values stored in memory to emulate that they were retrieved from an SMC, which Macs have but PCs do not. 2 Link to comment Share on other sites More sharing options...
Guest ricoc90 Posted October 26, 2017 Share Posted October 26, 2017 I wanted to install the beta 5 of 10.13.1 and ran into some issues with r4265: - macOS Build is not being recognized, thus had to copy my kexts to Other in order to be able to boot the 10.13.1 beta 5 update installer - Kext Inject Management is empty for the update installer - When looking at preboot.log, it turns up it's injecting kexts from 10.12, while I'm obviously on 10.13 preboot.log.zip Link to comment Share on other sites More sharing options...
magnifico Posted October 26, 2017 Share Posted October 26, 2017 Aptiofix2 does not relocate anything in memory so it should not interfere with anything, whereas for some reason aptiofix does interfere. Aptiofix can break firmware runtime, like nvram. Yes, it is the order they are enumerated, one disk may be busy and take longer to respond although it comes first in actual order. Those are just identifiers for the kernel for that boot, they no longer matter after restart/shutdown. That's why everything is identified by the partition identifier. That's your preference. VBoxHFS is open source but lacks features (it's slightly slower as well), however it seems to work better with some misbehaving firmwares. HFSPlus is closed source driver extracted from Apple firmware, it's fast and has more features, such as core storage RAID support and filevault. You do not need an NTFS driver at all. Windows boots from the EFI partition so can be read directly from the firmware already. If there is any reason to have one I do not know what it is. Good question, I'm not sure but I see no reason why it would touch the EFI partition. I haven't seen or heard of it. Can you boot without it/other patches? Is your power management working? Have you tried? Does it work? Does it give better performance? Beats me. Not that I'm aware of but it could be different depending on your hardware and kexts. Might have something to do with injecting the wrong properties for the graphics, I am unsure how to even check that. Maybe check out ioreg for anything interesting. An APFS partition is a container and has another structure inside that contains the volumes like recovery, system, etc. It would not back up properly to a HFS+ partition. So probably no, but maybe it does something to convert either the HFS+ to an APFS or the APFS content to work on the HFS+. Really no idea... Not anything meaningful, and not anymore than an actual SMC being present would. FakeSMC is just using values stored in memory to emulate that they were retrieved from an SMC, which Macs have but PCs do not. :lol:excellent and exemplary explanation Link to comment Share on other sites More sharing options...
rotoyouoio Posted October 26, 2017 Share Posted October 26, 2017 @rotoyouoio, Can you please give some screen shots or something? It's hard to understand what you mean from just your description, but I'll try.... What EFI drivers are you using? Are you injecting kexts? What else are you doing? The problem with X99 systems does not appear to be related to this at all unless you have drastically over complicated what you mean. The X99 problem is a boot time error where not enough contiguous free space can be allocated to place the entirety of the kernel - this is still in protected mode, not virtual so there is no address translation yet. Your error, if I understand correctly, is happening after boot services and during the kernel's runtime and appears to be a virtual address translation error. There are plenty of reasons why this could happen, moving stuff in memory after it's address has been translated, improperly translating an address, or just not translating the address at all. Need much more information, probably deeper debugging, which is hard if no developer has the issue or cannot reproduce it... EDIT: I've never even seen you say anything about this before, so there's no need to get mad. Everyone is trying to help but remember that every one here is doing this in their free time as a hobby. We don't all have lots of time to do everything, the more users a problem affects the higher priority it will have. As far as dmazar, I don't know what you mean but he's a great guy and a friend, you may find yourself not getting help at all by insulting developers who, if not for them, you would still be complaining it didn't work but for another reason. And the reason that there is no different aptiofix is because no one has created a better idea than that collaboration from projectosx, and the slight modification for aptiofix2. By all means please develop another method. umh... where did i insult any developer? i only said i was frustrated from diagnosing this. i mean i wasted a week before coming to the conclusion that it is not me being an idiot or the hardware being faulty. thus the frustration. the possibility of me being an idiot remains though. concerning dmazar. he might be a great guy, i just remember him saying that this is heavy work that he won't spend any more time when the x99 problem happened. and i've remembered this only to save someone's time pointing me at his direction. this in no way contradicts that he's a great guy and someone's good friend =0) anyway, back to the problem. screenshots of rember are in no way more informative than the text copied. i will spill my understanding of the problem, forgive me if it's too lame/nooblike/utterly silly the EFI (?) reserves and uses some physical memory addresses for hardware operation after the kernel is loaded, particularly usb storage devices (they are a certain condition for reproducing on x299 hardware), that the system considers available, hence writing to these addresses (virtual or not - no idea) is NOT successful, but the system has no idea. which means that when reading from these addresses - the system/software/memtest reads incorrect data, which can lead to practically anything. memtest is only different in the way that it knows what data must be returned after the inquiry. there. there is no way i can better describe the problem than the text above and in the previous posts. not that i expect you to diagnose this without such hardware, and i can live with legacy booting. (the only practical downside is sata hotplug not working in case of no harddrive attached to the hotplug port before boot) i am still rather grateful to be mentioned by someone like apianti and fritz (very little sarcasm here and it's in good spirit =0) this is more a cryout and a warning for future users of x299 platforms/a challenge for hackintosh (can a new term be made?) developers Link to comment Share on other sites More sharing options...
Funky frank Posted October 26, 2017 Share Posted October 26, 2017 apianti, thank you 1 Link to comment Share on other sites More sharing options...
apianti Posted October 27, 2017 Share Posted October 27, 2017 umh... where did i insult any developer? i only said i was frustrated from diagnosing this. i mean i wasted a week before coming to the conclusion that it is not me being an idiot or the hardware being faulty. thus the frustration. the possibility of me being an idiot remains though. concerning dmazar. he might be a great guy, i just remember him saying that this is heavy work that he won't spend any more time when the x99 problem happened. and i've remembered this only to save someone's time pointing me at his direction. this in no way contradicts that he's a great guy and someone's good friend =0) I was just warning you about getting angry when you are frustrated and mentioning someone who I know won't be helping since he has long left actively contributing to the community. You'll get more help if you put your frustration aside and try to give as much information as possible, even if it seems mundane or unrelated. anyway, back to the problem. screenshots of rember are in no way more informative than the text copied. i will spill my understanding of the problem, forgive me if it's too lame/nooblike/utterly silly the EFI (?) reserves and uses some physical memory addresses for hardware operation after the kernel is loaded, particularly usb storage devices (they are a certain condition for reproducing on x299 hardware), that the system considers available, hence writing to these addresses (virtual or not - no idea) is NOT successful, but the system has no idea. which means that when reading from these addresses - the system/software/memtest reads incorrect data, which can lead to practically anything. memtest is only different in the way that it knows what data must be returned after the inquiry. I have an idea what might be going on but I need more information, I would like to see screen shots of the error when it happens. I would like config.plist, boot.log, maybe ioreg and some DSDT/SSDT dumps. You can probably dump all that in one go with DarwinDumper (just select everything). Is the problem only related to USB devices in some way? EDIT: If you can dump your DSDT/SSDTs from clover too so they are the unpatched versions. there is no way i can better describe the problem than the text above and in the previous posts. not that i expect you to diagnose this without such hardware, and i can live with legacy booting. (the only practical downside is sata hotplug not working in case of no harddrive attached to the hotplug port before boot) i am still rather grateful to be mentioned by someone like apianti and fritz (very little sarcasm here and it's in good spirit =0) this is more a cryout and a warning for future users of x299 platforms/a challenge for hackintosh (can a new term be made?) developers I just don't think any one understands what you are describing and you aren't really changing the description or giving any different information so it's hard to tell what you are talking about. It's all good. 2 Link to comment Share on other sites More sharing options...
rotoyouoio Posted October 27, 2017 Share Posted October 27, 2017 I was just warning you about getting angry when you are frustrated and mentioning someone who I know won't be helping since he has long left actively contributing to the community. You'll get more help if you put your frustration aside and try to give as much information as possible, even if it seems mundane or unrelated. I have an idea what might be going on but I need more information, I would like to see screen shots of the error when it happens. I would like config.plist, boot.log, maybe ioreg and some DSDT/SSDT dumps. You can probably dump all that in one go with DarwinDumper (just select everything). Is the problem only related to USB devices in some way? EDIT: If you can dump your DSDT/SSDTs from clover too so they are the unpatched versions. I just don't think any one understands what you are describing and you aren't really changing the description or giving any different information so it's hard to tell what you are talking about. It's all good. i made Darwin do a dump over here http://www.insanelymac.com/forum/topic/284656-clover-general-discussion/?p=2522249 i think everything but the screenshots are in that darwin's dump =0) please correct me if i'm wrong. the error happens instantly in memtest/rember displaying that text all the other occurences are hard to screenshot, like finder getting stuck, resolve render output getting corrupted, or prefence files getting messed up up to the point of the system becoming unbootable (the reason i started testing initially) i can only reproduce this problem by having usb drive devices attached. so i believe that yes, only usb related dumping the original acpi tables is going to take some time, i am away from the machine now. i can, however, try to get a darwin dump with the original acpi tables from a similar setup, if my Darwin's dump is of no help without the original unpatched tables. I don't use a custom, only the patches that are in the plist an i believe that clover drops most of the secondary Link to comment Share on other sites More sharing options...
Recommended Posts