Jump to content

FileVault 2


vit9696
496 posts in this topic

Recommended Posts

I see. I remember getting that message, but not after pressing a button with the recompiled Usbkbxe, so perhaps mine really freezes and we have two different problems.

Perhaps I just didn't leave it on long enough... I'll try again today.

Curious that we both have freezing issues with the Logitech Unifying receiver, makes me wonder if that's at fault. I'll also try a new keyboard when I have the time. 

 

Both of us are having issues with no mouse support too.

 

Let me know if another Kbd fixes the issue, so I don't have to go out and buy a new Kbd, only to find it doesn't work either.

 

Thanks

Link to comment
Share on other sites

  • 2 weeks later...

FV2 works "flawlessly" on HP ProBook 4440s, only thing that does not work is keyboard/mouse inputs.  I attempted the AsAmiShim.efi (AptioInputFix), but still not working.  I thought about trying UsbFix, but figured that since the ProBook using PS/2 keyboard/mouse that it would make no difference?

Link to comment
Share on other sites

I think that ProBook (and most older HP laptops) uses Insyde EFI, so a shim meant for AMI Aptio UEFI wouldn't work.

Hm..  I do know I need OsxAptioFixDrv-64.efi for OS X/macOS to boot, unless that's different all together?  Should I try UsbKbDxe?

 

Also, I pulled up the boot.log file from Clover and saw this:

0:255  0:000  === [ LoadDrivers ] =======================================
0:255  0:000  Loading AppleImageCodec-64.efi  status=Success
0:256  0:001  Loading AsAmiShim.efi  status=Success
0:267  0:011  Loading AppleUITheme-64.efi  status=Success
0:279  0:011  Loading DataHubDxe-64.efi  status=Success
0:283  0:004  Loading HPFanReset.efi  status=Success
0:377  0:093  HPFanReset: successfully set fan control to BIOS mode.
0:377  0:000  Loading FirmwareVolume-64.efi  status=Success
0:378  0:001  Loading FSInject-64.efi  status=Success
0:385  0:007  Loading AppleKeyMapAggregator.efi  status=Success
0:386  0:000  Loading OsxFatBinaryDrv-64.efi  status=Success
0:387  0:001  Loading SMCHelper-64.efi  status=Success
0:398  0:010  Loading HFSPlus.efi  status=Success
0:398  0:000   - driver needs connecting
0:398  0:000  Loading NTFS.efi  status=Success
0:410  0:011   - driver needs connecting
0:410  0:000  Loading OsxAptioFix2Drv-64.efi  status=Success
0:417  0:007  2 drivers needs connecting ...
0:417  0:000  PlatformDriverOverrideProtocol not found. Installing ... Success
0:417  0:000  HFS+ driver loaded

It's showing the driver loading without error, but then I see the PlatformDriverOverrideProtocol issue at the bottom.

Link to comment
Share on other sites

FV2 works "flawlessly" on HP ProBook 4440s, only thing that does not work is keyboard/mouse inputs.  I attempted the AsAmiShim.efi (AptioInputFix), but still not working.  I thought about trying UsbFix, but figured that since the ProBook using PS/2 keyboard/mouse that it would make no difference?

There is the difference. We have no PS2 keyboard driver with KeyAggregator support except AsAmiShim which is for AMI UEFI only.

What to do? Become to be a programmer and write new driver.

Link to comment
Share on other sites

There is the difference. We have no PS2 keyboard driver with KeyAggregator support except AsAmiShim which is for AMI UEFI only.

What to do? Become to be a programmer and write new driver.

I understand this is slightly off-topic, but what is the difference between OsxAptioFix[2]Drv.efi and AsAmiShim.efi then?  Aren't they both for Ami UEFI?  And if that's the case, why is OsxAptioFixDrv.efi required for ProBooks despite the claim that they don't have an AMI UEFI BIOS then? I was under the impression they utilized AMI UEFI for that very reason.

Link to comment
Share on other sites

Does FV2 run with os x 10.12.5?

 

Yes, the update from 10.12.4 with FV2 went through smoothly on my machine. I updated to the latest Clover version (as of the date of this post) prior to updating the OS.

Link to comment
Share on other sites

I understand this is slightly off-topic, but what is the difference between OsxAptioFix[2]Drv.efi and AsAmiShim.efi then?  Aren't they both for Ami UEFI?  And if that's the case, why is OsxAptioFixDrv.efi required for ProBooks despite the claim that they don't have an AMI UEFI BIOS then? I was under the impression they utilized AMI UEFI for that very reason.

The name is historical. OsxAptioFix is not for AMI UEFI only. It is common driver correcting memory problems especially for AMI Aptio UEFI.

  • Like 1
Link to comment
Share on other sites

I'm having some trouble building the Clover pkg after I build Clover. I get these errors:

ld: warning: object file (/Users/jam2/EDK5/edk2/Clover/CloverPackage/sym/build/fdisk440/user.o64) was built for newer OSX version (10.12) than being linked (10.5)
	[LIPO] /Users/jam2/EDK5/edk2/Clover/CloverPackage/sym/utils/fdisk440
================= Making all in boot1-install =================
	[XCODE] boot1-install
================= Making all in partutil =================
	[XCODE] partutil
================= Making all in bdmesg =================
	[XCODE] bdmesg
================= Making all in clover-genconfig =================
	[XCODE] clover-genconfig
** INSTALL FAILED **


The following build commands failed:
	CompileC /Users/jam2/EDK5/edk2/Clover/CloverPackage/sym/build/clover-genconfig/clover-genconfig.build/Release/clover-genconfig.build/Objects-normal/i386/clover-genconfig.o clover-genconfig.c normal i386 c com.apple.compilers.llvm.clang.1_0.compiler
(1 failure)
make[1]: *** [/Users/jam2/EDK5/edk2/Clover/CloverPackage/sym/utils/clover-genconfig] Error 65
make: *** [all-recursive] Error 1

Can anyone offer me a little help as to what I'm doing wrong?

 

Also, I'm only able to build Clover once, then I get errors after I do  ./ebuild.sh cleanall.

Architecture(s)  = X64
Build target     = RELEASE
Toolchain        = XCODE5

Active Platform          = /Users/jam2/EDK5/edk2/Clover/Clover.dsc
Flash Image Definition   = /Users/jam2/EDK5/edk2/Clover/Clover.fdf

Processing meta-data ....... done!
Building ... /Users/jam2/EDK5/edk2/MdePkg/Library/BasePcdLibNull/BasePcdLibNull.inf [X64]
Building ... /Users/jam2/EDK5/edk2/MdePkg/Library/BaseDebugLibNull/BaseDebugLibNull.inf [X64]
Building ... /Users/jam2/EDK5/edk2/MdePkg/Library/BaseMemoryLib/BaseMemoryLib.inf [X64]
Building ... /Users/jam2/EDK5/edk2/MdePkg/Library/BaseLib/BaseLib.inf [X64]
Building ... /Users/jam2/EDK5/edk2/MdePkg/Library/BasePrintLib/BasePrintLib.inf [X64]
make: *** No rule to make target `tbuild'.  Stop.
make: *** No rule to make target `tbuild'.  Stop.
make: *** No rule to make target `tbuild'.  Stop.
make: *** No rule to make target `tbuild'.  Stop.


build.py...
 : error 7000: Failed to execute command
	make tbuild [/Users/jam2/EDK5/edk2/Build/Clover/RELEASE_XCODE5/X64/MdePkg/Library/BaseDebugLibNull/BaseDebugLibNull]


build.py...
 : error 7000: Failed to execute command
	make tbuild [/Users/jam2/EDK5/edk2/Build/Clover/RELEASE_XCODE5/X64/MdePkg/Library/BaseLib/BaseLib]


build.py...
 : error 7000: Failed to execute command
	make tbuild [/Users/jam2/EDK5/edk2/Build/Clover/RELEASE_XCODE5/X64/MdePkg/Library/BaseMemoryLib/BaseMemoryLib]


build.py...
 : error 7000: Failed to execute command
	make tbuild [/Users/jam2/EDK5/edk2/Build/Clover/RELEASE_XCODE5/X64/MdePkg/Library/BasePcdLibNull/BasePcdLibNull]


build.py...
 : error 7000: Failed to execute command
	make tbuild [/Users/jam2/EDK5/edk2/Build/Clover/RELEASE_XCODE5/X64/MdePkg/Library/BasePrintLib/BasePrintLib]


build.py...
 : error 7000: Failed to execute command
	make tbuild [/Users/jam2/EDK5/edk2/Build/Clover/RELEASE_XCODE5/X64/MdePkg/Library/BaseReportStatusCodeLibNull/BaseReportStatusCodeLibNull]


build.py...
 : error F002: Failed to build module
	/Users/jam2/EDK5/edk2/MdePkg/Library/BaseDebugLibNull/BaseDebugLibNull.inf [X64, XCODE5, RELEASE]

- Failed -
Build end time: 09:40:04, May.22 2017
Build total time: 00:00:10

Can anyone help me fix this, I'd like to try and mod the code a little, to see if I can get a working UsbKbd driver for my system for use with FV2.

 

 

 

 

  • Password input. To do that you need a keyboard driver, which knows about Apple key aggregation protocol, and the protocol itself.

    For key aggregation you may use Clover's AppleKeyAggregator.efi, it works more or less. If you have issues it might be better to use the original AppleKeyMapAggregator from Apple firmware.

    There are two input drivers for the time being:
    • Modified UsbKbDxe, a slightly altered version is present in Clover.
      Pros:
      — works with any USB keyboard in any BIOS;
      — offers completely functional Apple boot keys (CMD+V, 3+2, CMD+R, etc.);
      Cons:
      — might require a physical keyboard reconnect after driver load with AMI UEFI BIOS;
      — might lead to a complete freeze of the system with AMI UEFI BIOS.

      Recommendations:
      It is recommended to use this driver from BIOS or via legacy clover boot. In this case you will have no issues with keyboard connection. To solve freezing issues you will need to rebuild UsbKbDxe with a forced controller disconnect at EXIT BS.
      In case of Clover use:
      ./ebuild.sh -D EXIT_USBKB=1
      In case of the original driver see these PCDs. Both should be set to TRUE.
      In case of Clover FixOwnership might help you, but I would not recommend this.

 

 

 

 

 

Are there any instructions for building the UsbKbd driver linked in the CupertinoModulePkg?

 

Also, should I mod the CupertinoModulePkg.dec to read:

[PcdsFeatureFlag]
  ## Indicates if USB KeyBoard Driver disconnects itself when the Exit Boot
  ## Services event is triggered.<BR><BR>
  #   TRUE  - USB KeyBoard Driver will disconnect itself.<BR>
  #   FALSE - USB KeyBoard Driver will not disconnect itself.<BR>
  # @Prompt Disconnect the USB KeyBoard Driver when exitting Boot Services.
  gCupertinoModulePkgTokenSpaceGuid.PcdEnableDisconnectOnExitBootServicesInUsbKbDriver|TRUE|BOOLEAN|0x00000000

  ## Indicates if USB KeyBoard Driver registers a Apple KeyMap Database protocol installation notify.
  ## Services event is triggered.<BR><BR>
  #   TRUE  - USB KeyBoard Driver will registers a protocol installation notify.<BR>
  #   FALSE - USB KeyBoard Driver will registers a protocol installation notify.<BR>
  # @Prompt Register a protocol installation notify for Apple KeyMap Database when not found initially.
  gCupertinoModulePkgTokenSpaceGuid.PcdNotifyAppleKeyMapDbInUsbKbDriver|TRUE|BOOLEAN|0x00000001

  ## Indicates if USB KeyBoard Driver disconnects other drivers to take precedence.
  ## Services event is triggered.<BR><BR>
  #   TRUE  - USB KeyBoard Driver will disconnect other drivers.<BR>
  #   FALSE - USB KeyBoard Driver will not disconnect other drivers.<BR>
  # @Prompt Disconnect other drivers for the USB KeyBoard Driver to take precedence over them.
  gCupertinoModulePkgTokenSpaceGuid.PcdUsbKbDriverTakePrecedence|FALSE|BOOLEAN|0x00000002

Or is that not what was meant by "Both should be set to TRUE"?

 

 

EDIT: I noticed I'm getting this in my Clover Boot.log:

1:814  0:000  === [ LoadDrivers ] =======================================
1:817  0:003  Loading AppleImageCodec-64.efi  status=Success
1:821  0:003  Loading HashServiceFix-64.efi  status=Success
1:836  0:015  Loading UsbKbDxe.efi  status=Success
1:851  0:014   - driver needs connecting
1:851  0:000  Loading EmuVariableUefi-64.efi  status=Success
1:855  0:003  EmuVariableUefi Initialize: VariableCommonInitialize = Success, orig services stored, install gEmuVariableControlProtocolGuid = Success
1:859  0:003  Loading AppleUITheme-64.efi  status=Success
1:871  0:012  Loading FirmwareVolume-64.efi  status=Success
1:871  0:000  Loading HFSPlus.efi  status=Success
1:875  0:003   - driver needs connecting
1:875  0:000  Loading NTFS.efi  status=Success
1:896  0:021   - driver needs connecting
1:896  0:000  Loading FSInject-64.efi  status=Success
1:896  0:000  Loading SMCHelper-64.efi  status=Success
1:900  0:003  Loading AppleKeyAggregator.efi  status=Success
1:918  0:018  Loading IdeBusDxe_body.efi  status=Success
1:937  0:018   - driver needs connecting
1:937  0:000  Loading VBoxExt2-64.efi  status=Success
1:940  0:003   - driver needs connecting
1:940  0:000  Loading VBoxExt4-64.efi  status=Success
1:940  0:000   - driver needs connecting
1:940  0:000  Loading UsbMassStorageDxe.efi  status=Success
1:950  0:009   - driver needs connecting
1:960  0:010  Loading UsbMouseDxe.efi  status=Success
1:964  0:003   - driver needs connecting
1:964  0:000  Loading KeyboardDxe.efi  status=Success
1:966  0:002  Loading UsbBusDxe.efi  status=Success
1:967  0:001   - driver needs connecting
1:969  0:001  9 drivers needs connecting ...
1:969  0:000  PlatformDriverOverrideProtocol->GetDriver overriden
1:969  0:000  HFS+ driver loaded
3:537  1:567  EmuVariable InstallEmulation: orig vars copied, emu.var.services installed, CreateEvent VirtualAddressChange = Success, CreateEvent ExitBootServices = Success, set Status=Success

At this point I'm assuming the reason I'm having trouble is the UsbKbDxe.efi is not connecting to my USB KB. I must be running on the KeyboardDxe.efi, as far as I can tell, the Bios KB Driver. Thus the reason for my KB freeze?

 

 

Thanks

Link to comment
Share on other sites

Are there any instructions for building the UsbKbd driver linked in the CupertinoModulePkg?

Same as any other EDK2 package... Set up the EDK2 env and run 'build -a ARCH -b TARGET -t TOOLCHAIN -p CupertinoModulePkg/CupertinoModulePkg.dsc'.

 

Also, should I mod the CupertinoModulePkg.dec to read:

Well, read what they do and then enable what you want to enable?  :huh: When in doubt, you can enable all three.

Link to comment
Share on other sites

Same as any other EDK2 package... Set up the EDK2 env and run 'build -a ARCH -b TARGET -t TOOLCHAIN -p CupertinoModulePkg/CupertinoModulePkg.dsc'.

 

Well, read what they do and then enable what you want to enable?  :huh: When in doubt, you can enable all three.

Thanks Fritz,

 

My Keyboard shows up as Bios[iNT16] Keyboard Device:Primary Console Input Device in the Devtree of Clover's EFI Shell. I assume I need the KB to show up on the USB Bus, it does not in the Devtree. I tried to load the Ohcidxe.efi and the Uhcidxe.efi from my Clover build, but using the Ohcidxe.efi results in no KB input in Clover at all.

 

I would assume, that I need a working Ohci Driver to get thee UsbKb Driver to work?

 

Am I one the wrong track?

 

Does anyone have the UsbKb driver working with a Bios( non-UEFI ) motherboard?

Link to comment
Share on other sites

As far as I remember I tested UsbKb driver with legacy Clover so with non-UEFI BIOS.

 Hmmm.....

 

Really not sure what is going wrong, the UsbKbDxe loads, but needs to connect to the device. Am I wrong in assuming I need a working set of Usb drivers for Clover to make this work?

 

I've built Duet, but the CreateBootDisk.sh seems to be out of date, when I try to run it I get:

/Users/jam2/EDK7/edk2/DuetPkg/CreateBootDisk.sh usb /dev/disk1 /dev/disk1 FAT16 X64
Format /dev/disk1 ...
Create boot sector ...
ERROR: It's not a floppy disk!
GnuGenBootSector: ERROR 1003: Invalid option value
  Input file can't be found.
Path = Bs16-1.com
ERROR: It's not a floppy disk!
GnuGenBootSector: ERROR 1003: Invalid option value
  Output file can't be found.
Path = /Users/jam2/EDK7/edk2/DuetPkg/BootSector/bin/Mbr.com
ERROR: It's not a floppy disk!
GnuGenBootSector: ERROR 1003: Invalid option value
  Output file can't be found.
Done.
PLEASE UNPLUG USB, THEN PLUG IT AGAIN TO DO STEP2!

Same thing on Linux.

 

Can anyone offer any help on how to create a Duet USB Stick on OS X?

Link to comment
Share on other sites

After put this drivers to my EFI folder i receive this error

Found 1 Handles located by protocol
Installed onto CCC5E798
AmiShimPointerTimerSetup changed period 549254 to 60000, error 0
gAppleKeyMapDatabaseProtocolGuid is unavailable 14
AmiShim installation failed 1

and my preboot.log

0:100 0:100 MemLog inited, TSC freq: 3491915362
0:100 0:000
0:100 0:000 Now is 23.5.2017, 7:34:43 (GMT)
0:100 0:000 Starting Clover revision: 4061 on American Megatrends EFI
0:100 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.4 | XCODE: 8.2.1]
0:100 0:000 SelfDevicePath=PciRoot(0x0)\Pci(0x1F,0x2)\Sata(0x1,0xFFFF,0x0)\HD(1,GPT,7A728088-88F0-49F6-8830-C2DD60C6D0E2,0x28,0x64000) @CCC62A18
0:100 0:000 SelfDirPath = \EFI\BOOT
0:100 0:000 === [ Get Smbios ] ========================================
0:100 0:000 Type 16 Index = 0
0:100 0:000 Total Memory Slots Count = 4
0:100 0:000 Type 17 Index = 0
0:100 0:000 SmbiosTable.Type17->Speed = 1600MHz
0:100 0:000 SmbiosTable.Type17->Size = 8192MB
0:100 0:000 SmbiosTable.Type17->Bank/Device = BANK 0 ChannelA-DIMM0
0:100 0:000 SmbiosTable.Type17->Vendor = Kingston
0:100 0:000 SmbiosTable.Type17->SerialNumber = 6D160748
0:100 0:000 SmbiosTable.Type17->PartNumber = KHX1600C10D3/8G
0:100 0:000 Type 17 Index = 1
0:100 0:000 SmbiosTable.Type17->Speed = 1600MHz
0:100 0:000 SmbiosTable.Type17->Size = 8192MB
0:100 0:000 SmbiosTable.Type17->Bank/Device = BANK 1 ChannelA-DIMM1
0:100 0:000 SmbiosTable.Type17->Vendor = Kingston
0:100 0:000 SmbiosTable.Type17->SerialNumber = 68160948
0:100 0:000 SmbiosTable.Type17->PartNumber = KHX1600C10D3/8G
0:100 0:000 Type 17 Index = 2
0:100 0:000 SmbiosTable.Type17->Speed = 1600MHz
0:100 0:000 SmbiosTable.Type17->Size = 8192MB
0:100 0:000 SmbiosTable.Type17->Bank/Device = BANK 2 ChannelB-DIMM0
0:100 0:000 SmbiosTable.Type17->Vendor = Kingston
0:100 0:000 SmbiosTable.Type17->SerialNumber = 6616F347
0:100 0:000 SmbiosTable.Type17->PartNumber = KHX1600C10D3/8G
0:100 0:000 Type 17 Index = 3
0:100 0:000 SmbiosTable.Type17->Speed = 1600MHz
0:100 0:000 SmbiosTable.Type17->Size = 8192MB
0:100 0:000 SmbiosTable.Type17->Bank/Device = BANK 3 ChannelB-DIMM1
0:100 0:000 SmbiosTable.Type17->Vendor = Kingston
0:100 0:000 SmbiosTable.Type17->SerialNumber = 6516F447
0:100 0:000 SmbiosTable.Type17->PartNumber = KHX1600C10D3/8G
0:100 0:000 Boot status=0
0:100 0:000 Running on: 'All Series' with board 'B85M-G'
0:100 0:000 === [ GetCPUProperties ] ==================================
0:100 0:000 CPU Vendor = 756E6547 Model=306C3
0:100 0:000 The CPU supported SSE4.1
0:100 0:000 The CPU supported turbo
0:100 0:000 BrandString = Intel(R) Core(TM) i5-4690 CPU @ 3.50GHz
0:100 0:000 MSR 0xE2 before patch 1E000400
0:100 0:000 MSR 0xCE 00080838_F3012300
0:100 0:000 MSR 0x1A0 00850089
0:100 0:000 corrected FLEX_RATIO = 0
0:100 0:000 MSR 0x1B0 00000000
0:100 0:000 FSBFrequency = 100 MHz, DMI FSBFrequency = 100 MHz, Corrected FSBFrequency = 100 MHz
0:100 0:000 MaxDiv/MinDiv: 35.0/8
0:100 0:000 Turbo: 37/38/39/39
0:100 0:000 Features: 0xBFEBFBFF
0:100 0:000 Threads: 4
0:100 0:000 Cores: 4
0:100 0:000 FSB: 25 MHz
0:100 0:000 CPU: 3500 MHz
0:100 0:000 TSC: 3500 MHz
0:100 0:000 PIS: 100 MHz
0:100 0:000 === [ GetDevices ] ========================================
0:100 0:000 PCI (00|00:00.00) : 8086 0C00 class=060000
0:100 0:000 PCI (00|00:01.00) : 8086 0C01 class=060400
0:100 0:000 PCI (00|00:02.00) : 8086 0412 class=030000
0:100 0:000 - GFX: Model=Intel HD Graphics 4600 (Intel)
0:100 0:000 PCI (00|00:03.00) : 8086 0C0C class=040300
0:100 0:000 PCI (00|00:14.00) : 8086 8C31 class=0C0330
0:100 0:000 PCI (00|00:16.00) : 8086 8C3A class=078000
0:100 0:000 PCI (00|00:16.01) : FFFF FFFF class=FFFFFF
0:100 0:000 PCI (00|00:1A.00) : 8086 8C2D class=0C0320
0:100 0:000 PCI (00|00:1B.00) : 8086 8C20 class=040300
0:100 0:000 PCI (00|00:1C.00) : 8086 8C10 class=060400
0:100 0:000 PCI (00|02:00.00) : 10EC 8168 class=020000
0:100 0:000 - LAN: 0 Vendor=Realtek
0:100 0:000 PCI (00|00:1C.01) : 8086 8C12 class=060400
0:100 0:000 PCI (00|03:00.00) : 14E4 43A0 class=028000
0:100 0:000 - WIFI: Vendor=Broadcom
0:100 0:000 PCI (00|00:1C.02) : 8086 8C14 class=060400
0:100 0:000 PCI (00|04:00.00) : 10EC 8168 class=020000
0:100 0:000 - LAN: 1 Vendor=Realtek
0:100 0:000 PCI (00|00:1D.00) : 8086 8C26 class=0C0320
0:100 0:000 PCI (00|00:1F.00) : 8086 8C50 class=060100
0:100 0:000 PCI (00|00:1F.02) : 8086 8C02 class=010601
0:100 0:000 PCI (00|00:1F.03) : 8086 8C22 class=0C0500
0:100 0:000 PCI (00|00:1F.06) : FFFF FFFF class=FFFFFF
0:100 0:000 === [ GetDefaultSettings ] ================================
0:100 0:000 Clover load options size = 0 bytes
0:105 0:005 EFI\CLOVER\OEM\B85M-G\UEFI\config.plist loaded: Success
0:105 0:000 === [ GetListOfThemes ] ===================================
0:106 0:000 - [00]: applestyle
0:110 0:003 - [01]: black_green
0:113 0:003 - [02]: BOOTCAMP
0:115 0:002 === [ Found config plists ] ===============================
0:115 0:000 - config.plist
0:115 0:000 === [ GetEarlyUserSettings ] ==============================
0:115 0:000 timeout set to 8
0:115 0:000 Custom boot CUSTOM_BOOT_DISABLED (0x0)
0:115 0:000 ForceKextsToLoad: 1 requested
0:115 0:000 - [0]: System\Library\Extensions\AppleHDA.kext
0:115 0:000 KextsToPatch: 7 requested
0:115 0:000 - [00]: AppleIntelFramebufferAzul (HDMI Connector 0300220D) :: BinPatch :: data len: 36
0:115 0:000 - [01]: AppleHDA (Replace xml to Zml) :: BinPatch :: data len: 6
0:115 0:000 - [02]: AppleHDA (AppleHDA Hex-Patch) :: BinPatch :: data len: 4
0:115 0:000 - [03]: AppleHDA (AppleHDA ASCII-Patch) :: BinPatch :: data len: 8
0:115 0:000 - [04]: AppleHDAController (HDMI Patch1) :: BinPatch :: data len: 5
0:115 0:000 - [05]: AppleHDAController (HDMI Patch2) :: BinPatch :: data len: 5
0:115 0:000 - [06]: AppleHDAController (HDMI Patch3) :: BinPatch :: data len: 4
0:115 0:000 Default theme: black_green
0:115 0:000 === [ LoadDrivers ] =======================================
0:117 0:001 Loading FSInject-64.efi status=Success
0:118 0:000 Loading HFSPlus-64.efi status=Success
0:118 0:000 - driver needs connecting
0:118 0:000 Loading OsxAptioFixDrv-64.efi status=Success
0:119 0:000 Loading PartitionDxe-64.efi status=Success
0:120 0:000 - driver needs connecting
0:120 0:000 Loading FirmwareVolume-64.efi status=Success
0:121 0:001 Loading AppleImageCodec-64.efi status=Success
0:122 0:001 Loading AppleUITheme-64.efi status=Success
0:123 0:000 Loading SMCHelper-64.efi status=Success
0:124 0:000 Loading AptioInputFixB2.efi status=Success
0:167 0:043 2 drivers needs connecting ...
0:167 0:000 PlatformDriverOverrideProtocol->GetDriver overriden
0:167 0:000 Partition driver loaded: CD disconnect Success
0:167 0:000 HFS+ driver loaded
0:167 0:000 Searching for invalid DiskIo BY_DRIVER connects: not found, all ok
0:266 0:098 === [ InitScreen ] ========================================
0:266 0:000 SetMaxResolution: found best mode 0: 1600x1200
0:457 0:191 Video mode change to mode #0: Success
0:457 0:000 - set
0:457 0:000 Console modes reported: 3, available modes:
0:457 0:000 - [01]: 80x25 (current mode)
0:457 0:000 - [02]: 80x50
0:457 0:000 - [03]: 100x31
0:558 0:101 reinit: self device path=PciRoot(0x0)\Pci(0x1F,0x2)\Sata(0x1,0xFFFF,0x0)\HD(1,GPT,7A728088-88F0-49F6-8830-C2DD60C6D0E2,0x28,0x64000)
0:559 0:000 Using embedded font: Success
0:559 0:000 === [ GetMacAddress ] =====================================
0:559 0:000 === [ ScanSPD ] ===========================================
0:559 0:000 SMBus device : 8086 8C22 class=0C0500 status=Success
0:559 0:000 SMBus CmdReg: 0x3
0:559 0:000 Scanning SMBus [8086:8C22], mmio: 0xF7D19004, ioport: 0xF040, hostc: 0x1
0:559 0:000 Slots to scan [8]...
0:560 0:000 SPD[0]: Type 11 @0x50
0:578 0:017 Not using XMP because it is not present
0:578 0:000 DDR speed 1600MHz
0:578 0:000 Slot: 0 Type 24 8192MB 1600MHz Vendor=Kingston PartNo=KHX1600C10D38G SerialNo=060D010600070408
0:578 0:000 SPD[1]: Type 11 @0x51
0:596 0:017 Not using XMP because it is not present
0:596 0:000 DDR speed 1600MHz
0:596 0:000 Slot: 1 Type 24 8192MB 1600MHz Vendor=Kingston PartNo=KHX1600C10D38G SerialNo=0608010600090408
0:597 0:000 SPD[2]: Type 11 @0x52
0:614 0:017 Not using XMP because it is not present
0:614 0:000 DDR speed 1600MHz
0:614 0:000 Slot: 2 Type 24 8192MB 1600MHz Vendor=Kingston PartNo=KHX1600C10D38G SerialNo=060601060F030407
0:615 0:000 SPD[3]: Type 11 @0x53
0:633 0:017 Not using XMP because it is not present
0:633 0:000 DDR speed 1600MHz
0:633 0:000 Slot: 3 Type 24 8192MB 1600MHz Vendor=Kingston PartNo=KHX1600C10D38G SerialNo=060501060F040407
0:633 0:000 === [ GetAcpiTablesList ] =================================
0:633 0:000 Get Acpi Tables List from RSDT:
0:633 0:000 - [00]: FACP A M I len=132
0:633 0:000 - [01]: APIC A M I len=114
0:633 0:000 - [02]: FPDT A M I len=68
0:633 0:000 - [03]: LPIT A M I len=92
0:633 0:000 - [04]: SSDT Cpu0Ist len=1337
0:633 0:000 - [05]: SSDT CpuPm len=2776
0:633 0:000 - [06]: MCFG A M I len=60
0:633 0:000 - [07]: HPET A M I len=56
0:633 0:000 - [08]: SSDT SataTabl len=877
0:633 0:000 - [09]: SSDT SaSsdt len=13537
0:633 0:000 - [10]: BGRT A M I len=56
0:633 0:000 Calibrated TSC frequency =3491915362 =3491MHz
0:633 0:000 === [ GetUserSettings ] ===================================
0:633 0:000 USB FixOwnership: no
0:633 0:000 Dropping 6 tables:
0:633 0:000 - [00]: Drop table signature="DMAR" (52414D44)
0:633 0:000 - set table: 52414D44, 0 to drop: no
0:633 0:000 - [01]: Drop table signature="SSDT" (54445353) table-id="Cpu0Ist" (0074734930757043)
0:633 0:000 - set table: 54445353, 74734930757043 to drop: yes
0:633 0:000 - [02]: Drop table signature="SSDT" (54445353) table-id="CpuPm" (0000006D50757043)
0:633 0:000 - set table: 54445353, 6D50757043 to drop: yes
0:633 0:000 - [03]: Drop table signature="SSDT" (54445353) table-id="ApIst" (0000007473497041)
0:633 0:000 - set table: 54445353, 7473497041 to drop: no
0:633 0:000 - [04]: Drop table signature="SSDT" (54445353) table-id="SaSsdt" (0000746473536153)
0:633 0:000 - set table: 54445353, 746473536153 to drop: no
0:633 0:000 - [05]: Drop table signature="SSDT" (54445353) table-id="SataTabl" (6C62615461746153)
0:633 0:000 - set table: 54445353, 6C62615461746153 to drop: yes
0:634 0:000 - final DSDT Fix mask=00000050
0:634 0:000 PatchesDSDT: 11 requested
0:634 0:000 - [00]: (Cosmetic patch B0D3 to HDAU) lenToFind: 4, lenToReplace: 4
0:634 0:000 - [01]: (Cosmetic patch GFX0 to IGPU) lenToFind: 4, lenToReplace: 4
0:634 0:000 - [02]: (Cosmetic patch TPMX to MEM2) lenToFind: 4, lenToReplace: 4
0:634 0:000 - [03]: (Cosmetic patch SAT0 to SATA) lenToFind: 4, lenToReplace: 4
0:634 0:000 - [04]: (Cosmetic patch XHC_ to XHC1) lenToFind: 4, lenToReplace: 4
0:634 0:000 - [05]: (Cosmetic patch COPR to MATH) lenToFind: 4, lenToReplace: 4
0:634 0:000 - [06]: (instead of Darwin) lenToFind: 4, lenToReplace: 4
0:634 0:000 - [07]: (Corrections warning 0x0FFF to 0xFFFF) lenToFind: 3, lenToReplace: 3
0:634 0:000 - [08]: (PTS Clean) lenToFind: 796, lenToReplace: 56
0:634 0:000 - [09]: (Warning fix _T_0 to T_0_) lenToFind: 4, lenToReplace: 4
0:634 0:000 - [10]: (Warning fix _T_1 to T_1_) lenToFind: 4, lenToReplace: 4
0:636 0:002 === [ ScanVolumes ] =======================================
0:636 0:000 Found 5 volumes with blockIO
0:636 0:000 - [00]: Volume: PciRoot(0x0)\Pci(0x1F,0x2)\Sata(0x1,0xFFFF,0x0)
0:637 0:000 - [01]: Volume: PciRoot(0x0)\Pci(0x1F,0x2)\Sata(0x2,0xFFFF,0x0)
0:637 0:000 Found optical drive
0:637 0:000 - [02]: Volume: PciRoot(0x0)\Pci(0x1F,0x2)\Sata(0x1,0xFFFF,0x0)\HD(1,GPT,7A728088-88F0-49F6-8830-C2DD60C6D0E2,0x28,0x64000)
0:638 0:000 Result of bootcode detection: bootable unknown (legacy)
0:643 0:005 This is SelfVolume !!
0:643 0:000 - [03]: Volume: PciRoot(0x0)\Pci(0x1F,0x2)\Sata(0x1,0xFFFF,0x0)\HD(2,GPT,7656590C-8E2B-4468-96E7-6C812081C25E,0x64028,0xDDFAC40)
0:643 0:000 Result of bootcode detection: bootable unknown (legacy)
0:643 0:000 - [04]: Volume: PciRoot(0x0)\Pci(0x1F,0x2)\Sata(0x1,0xFFFF,0x0)\HD(3,GPT,D68A6B3C-6855-4998-AE69-EFB275F55936,0xDE5EC68,0x135F20)
0:644 0:000 === [ InitTheme ] =========================================
0:645 0:001 Using theme 'black_green' (EFI\CLOVER\themes\black_green)
0:645 0:000 OS main and drive as badge
0:647 0:001 Loading font from ThemeDir: Success
0:647 0:000 Choosing theme black_green
0:647 0:000 found boot-args in NVRAM:, size=1
0:647 0:000 after NVRAM boot-args=kext-dev-mode=1
0:647 0:000 === [ Dump SMC keys from NVRAM ] ==========================
0:647 0:000 found AppleSMC protocol
0:658 0:011 === [ ScanLoader ] ========================================
0:658 0:000 - [02]: 'EFI'
1:690 1:031 - [03]: 'Mac'
1:691 0:001 AddLoaderEntry for Volume Name=Mac
1:694 0:002 Check if volume Is Hibernated:
1:694 0:000 Check sleep image 'by signature':
1:697 0:003 using default sleep image name = \private\var\vm\sleepimage
1:699 0:002 no valid sleep image offset was found
1:699 0:000 sleepimage offset could not be acquired
1:699 0:000 hibernated: no - sign
1:700 0:000 [!] Icon 17 (icons\vol_internal_hfs.icns) not found (path: EFI\CLOVER\themes\black_green)
1:715 0:014 - [04]: 'Recovery HD'
1:717 0:002 AddLoaderEntry for Volume Name=Recovery HD
1:718 0:000 Check if volume Is Hibernated:
1:718 0:000 Check sleep image 'by signature':
1:718 0:000 using default sleep image name = \private\var\vm\sleepimage
1:718 0:000 sleepimage not found -> Not Found
1:718 0:000 hibernated: no - sign
1:719 0:001 AddLoaderEntry for Volume Name=Recovery HD
1:734 0:015 === [ AddCustomTool ] =====================================
1:737 0:002 === [ GetEfiBootDeviceFromNvram ] =========================
1:737 0:000 - found entry 0. 'Boot macOS from Mac', Volume 'Mac', DevicePath 'PciRoot(0x0)\Pci(0x1F,0x2)\Sata(0x1,0xFFFF,0x0)\HD(2,GPT,7656590C-8E2B-4468-96E7-6C812081C25E,0x64028,0xDDFAC40)\System\Library\CoreServices\boot.efii'
1:737 0:000 DefaultIndex=0 and MainMenu.EntryCount=7
1:919 0:181 GUI ready
27:777 25:858 Boot option Boot0000 not found
27:777 0:000 === [ StartLoader ] =======================================
27:777 0:000 Finally: Bus=99769kHz CPU=3492MHz
27:777 0:000 Loading boot.efi status=Success
27:840 0:062 GetOSVersion: 10.10.5 (14F27)
27:840 0:000 Filtering KextPatches:
27:840 0:000 - [00]: AppleIntelFramebufferAzul (HDMI Connector 0300220D) :: BinPatch :: [OS: 10.10.5 | MatchOS: All | MatchBuild: All] ==> allowed
27:840 0:000 - [01]: AppleHDA (Replace xml to Zml) :: BinPatch :: [OS: 10.10.5 | MatchOS: All | MatchBuild: All] ==> allowed
27:840 0:000 - [02]: AppleHDA (AppleHDA Hex-Patch) :: BinPatch :: [OS: 10.10.5 | MatchOS: All | MatchBuild: All] ==> allowed
27:840 0:000 - [03]: AppleHDA (AppleHDA ASCII-Patch) :: BinPatch :: [OS: 10.10.5 | MatchOS: All | MatchBuild: All] ==> allowed
27:840 0:000 - [04]: AppleHDAController (HDMI Patch1) :: BinPatch :: [OS: 10.10.5 | MatchOS: All | MatchBuild: All] ==> allowed
27:840 0:000 - [05]: AppleHDAController (HDMI Patch2) :: BinPatch :: [OS: 10.10.5 | MatchOS: All | MatchBuild: All] ==> allowed
27:840 0:000 - [06]: AppleHDAController (HDMI Patch3) :: BinPatch :: [OS: 10.10.5 | MatchOS: All | MatchBuild: All] ==> allowed
27:840 0:000 === [ PatchSmbios ] =======================================
27:840 0:000 insert table 9 for dev 0:0
27:840 0:000 insert table 9 for dev 0:0
27:840 0:000 Channels: 2
27:840 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
27:840 0:000 SMBIOS Type 17 Index = 0 => 0 0:
27:840 0:000 BANK 0 DIMM0 1600MHz 8192MB
27:840 0:000 SMBIOS Type 17 Index = 1 => 2 2:
27:840 0:000 BANK 1 DIMM0 1600MHz 8192MB
27:840 0:000 SMBIOS Type 17 Index = 2 => 1 1:
27:840 0:000 BANK 0 DIMM1 1600MHz 8192MB
27:840 0:000 SMBIOS Type 17 Index = 3 => 3 3:
27:840 0:000 BANK 1 DIMM1 1600MHz 8192MB
27:840 0:000 mTotalSystemMemory = 32768
27:840 0:000 NumberOfMemoryDevices = 4
27:840 0:000 Type20[0]->End = 0x7FFFFF, Type17[0] = 0x2000
27:840 0:000 Type20[1]->End = 0x17FFFFF, Type17[2] = 0x8000
27:840 0:000 Type20[2]->End = 0xFFFFFF, Type17[1] = 0xC000
27:840 0:000 Type20[3]->End = 0x1FFFFFF, Type17[3] = 0x14000
27:840 0:000 Table 131 is present, CPUType=35
27:840 0:000 Change to: 605
27:840 0:000 === [ PatchACPI ] =========================================
27:840 0:000 RSDT 0xD8714028
27:840 0:000 FADT from RSDT: 0xD8714110
27:840 0:000 XSDT 0xD8714080
27:840 0:000 FADT from XSDT: 0xD8721678
27:840 0:000 Xsdt reallocation done
27:840 0:000 old FADT length=10C
27:843 0:003 Apply DsdtFixMask=0x00000050
27:843 0:000 drop _DSM mask=0x0000
27:844 0:000 === [ FixBiosDsdt ] =======================================
27:844 0:000 VideoCard devID=0x4128086
27:844 0:000 DisplayADR1[0] = 0x20000, DisplayADR2[0] = 0xFFFE
27:945 0:101 Audio HDA (addr:0x30000) setting specified layout-id=86 (0x56)
27:946 0:000 USBADR[0] = 0x140000 and PCIe = 0xFFFE
27:946 0:000 USBADR[1] = 0x1A0000 and PCIe = 0xFFFE
28:048 0:102 Audio HDA (addr:0x1B0000) setting specified layout-id=86 (0x56)
28:048 0:000 Found Airport BCM at 0x1C0001, 0x0
28:048 0:000 USBADR[2] = 0x1D0000 and PCIe = 0xFFFE
28:048 0:000 Patching DSDT:
28:048 0:000 - [Cosmetic patch B0D3 to HDAU]: pattern 42304433, patched at: [ (87A9) (1D) (17) (F) ]
28:048 0:000 - [Cosmetic patch GFX0 to IGPU]: pattern 47465830, patched at: [ (881A) (67) (1B) (13) (19) (98) (1B) (13) (19) (1AB) (1B) (148) (1D) (E15) (30) (16B) (373) (51C) (92F) (14) (56) (22E7) ]
28:048 0:000 - [Cosmetic patch TPMX to MEM2]: pattern 54504D58, patched at: [ (188F) ]
28:048 0:000 - [Cosmetic patch SAT0 to SATA]: pattern 53415430, patched at: [ (6F5E) (23) (2E) (12) (2B5D) (35) (172) (1B) (21) (21) (21) (13D) (29) (2E) (2E) (2E) (E5) ]
28:048 0:000 - [Cosmetic patch XHC_ to XHC1]: pattern 5848435F, patched at: [ (1683) (8) (1E) (42CA) (4B9) (11B) (3040) (6C3) (10) (11D2) (F) (10) ]
28:048 0:000 - [Cosmetic patch COPR to MATH]: pattern 434F5052, bin not found / already patched!
28:048 0:000 - [instead of Darwin]: pattern 0BD0074F, patched at: [ (9703) ]
28:048 0:000 - [Corrections warning 0x0FFF to 0xFFFF]: pattern FF0F7000, patched at: [ (24D6) ]
28:048 0:000 - [PTS Clean]: pattern 144A335F, bin not found / already patched!
28:048 0:000 - [Warning fix _T_0 to T_0_]: pattern 5F545F30, patched at: [ (32F7) (9) (4) (385) (9) (4) (385) (9) (4) (385) (9) (4) (385) (9) (4) (385) (9) (4) (D28) (22) (3) (17) (15) (6D) (22) (3) (17) (15) (6D) (22) (3) (17) (15) (6D) (22) (3) (17) (15) (1E4) (22) (3) (17) (15) (96) (22) (3) (17) (15) (1D0) (17) (3) (9) ( ( ( (C) (C) (C) (C) ( ( ( ( (A) (A) (1F24) (E) (3) (C) (C) (D) (C) (C) (C) (C) (13) (A) (3) (2A) (2A) (3F) (31) (38) (38) (24) (24) (35) (22E2) (48) (3) (1E) (24) (1A9B) (A) (3) (11) (11) (11) (11) (11) (10) (F) (10) (50) (A) (3) (11) (11) (10) (10) (10) (A26) (22) (3) (21) (22) (22) (22) (22) (22) (22) (22) (23) (23) (23) (23) (23) (23) (23) (23) (25) (25) (24) (3EC) (18) (3) (11) (11) (3) (E) (14) (14) ]
28:049 0:000 - [Warning fix _T_1 to T_1_]: pattern 5F545F31, patched at: [ (32F1) (37) (3) (3F) (41) (2D0) (37) (3) (3F) (41) (2D0) (37) (3) (3F) (41) (2D0) (37) (3) (3F) (41) (2D0) (37) (3) (3F) (41) (2D0) (37) (3) (3F) (41) (1462) (10A) (3) (9) ( ( ( (A) (A) (A) (A) (6AF0) (34D) (3) (29) (29) (29) (29) (29) (29) (29) (29) (29) (29) (29) (29) (29) (29) (29) (29) (29) (29) (28) ]
28:049 0:000 first CPU found at 7E8F offset 7E93
28:049 0:000 score candidate at 7E8B
28:049 0:000 score inserted in acpi_cpu_score _PR_
28:049 0:000 Found ACPI CPU: CPU0 | CPU1 | CPU2 | CPU3 | CPU4 | CPU5 | CPU6 | CPU7 , within the score: _PR_
28:049 0:000 Found PCIROOTUID = 0
28:049 0:000 Start PIC Fix
28:049 0:000 PIC size=A5 at 200F
28:049 0:000 found CRS at 2023 size 8D
28:049 0:000 found PIC had IRQNoFlag will move -3 bytes
28:049 0:000 Fix Device PIC size -3
28:049 0:000 Start HPET Fix
28:049 0:000 === [ ACPIDropTables ] ====================================
28:049 0:000 Drop tables from Xsdt, SIGN=SSDT TableID=SataTabl Length=877
28:049 0:000 Xsdt has tables count=11
28:049 0:000 Table: SSDT SataTabl 877 dropped
28:049 0:000 Drop tables from Xsdt, SIGN=SSDT TableID=CpuPm Length=2776
28:049 0:000 Xsdt has tables count=10
28:049 0:000 Table: SSDT CpuPm 2776 dropped
28:049 0:000 Drop tables from Xsdt, SIGN=SSDT TableID=Cpu0Ist Length=1337
28:049 0:000 Xsdt has tables count=9
28:049 0:000 Table: SSDT Cpu0Ist 1337 dropped
28:049 0:000 === [ PatchAllSSDT ] ======================================
28:049 0:000 Patch table: SSDT SaSsdt len=0x34E1
28:049 0:000 0. [Cosmetic patch B0D3 to HDAU]: pattern 42304433, patched at: [ (89E) (27E9) (F) (10) (F) (F) (F) ]
28:049 0:000 1. [Cosmetic patch GFX0 to IGPU]: pattern 47465830, patched at: [ (D8A) (17) (17) (1A) (18EC) (B3E) (1D) ]
28:049 0:000 2. [Cosmetic patch TPMX to MEM2]: pattern 54504D58, bin not found / already patched!
28:049 0:000 3. [Cosmetic patch SAT0 to SATA]: pattern 53415430, bin not found / already patched!
28:049 0:000 4. [Cosmetic patch XHC_ to XHC1]: pattern 5848435F, bin not found / already patched!
28:049 0:000 5. [Cosmetic patch COPR to MATH]: pattern 434F5052, bin not found / already patched!
28:049 0:000 6. [instead of Darwin]: pattern 0BD0074F, bin not found / already patched!
28:049 0:000 7. [Corrections warning 0x0FFF to 0xFFFF]: pattern FF0F7000, bin not found / already patched!
28:049 0:000 8. [PTS Clean]: pattern 144A335F, bin not found / already patched!
28:049 0:000 9. [Warning fix _T_0 to T_0_]: pattern 5F545F30, patched at: [ (347) (9) (4) (205) (9) (4) (1E8) (9) (4) ]
28:049 0:000 10. [Warning fix _T_1 to T_1_]: pattern 5F545F31, patched at: [ (341) (37) (3) (3F) (41) (150) (37) (3) (3F) (41) (133) (37) (3) (3F) (41) ]
28:049 0:000 Drop tables from Xsdt, SIGN=XXXX TableID= Length=0
28:049 0:000 Xsdt has tables count=8
28:049 0:000 === [ ACPIPatchedAML ] ====================================
28:049 0:000 Unsorted
28:049 0:000 Inserting SSDT.AML from EFI\CLOVER\OEM\B85M-G\UEFI\ACPI\patched ... Success
28:051 0:001 Inserting SSDT-3.AML from EFI\CLOVER\OEM\B85M-G\UEFI\ACPI\patched ... Success
28:051 0:000 CPUBase=0 and ApicCPUBase=1 ApicCPUNum=4
28:051 0:000 Maximum control=0x23
28:051 0:000 Turbo control=0x27
28:051 0:000 P-States: min 0x8, max 0x27
28:052 0:000 SSDT with CPU P-States generated successfully
28:052 0:000 === [ RestSetup macOS ] ===================================
28:052 0:000 EdidDiscovered size=128
28:052 0:000 | EDID Table
28:052 0:000 000 | 00 FF FF FF FF FF FF 00 10 AC
28:052 0:000 010 | 70 D0 4C 51 37 30 13 19 01 03
28:052 0:000 020 | 80 37 1F 78 EE 44 55 A9 55 4D
28:052 0:000 030 | 9D 26 0F 50 54 A5 4B 00 B3 00
28:052 0:000 040 | D1 00 71 4F A9 40 81 80 77 80
28:052 0:000 050 | 01 01 01 01 56 5E 00 A0 A0 A0
28:052 0:000 060 | 29 50 30 20 35 00 29 37 21 00
28:052 0:000 070 | 00 1A 00 00 00 FF 00 39 58 32
28:052 0:000 080 | 56 59 35 35 37 30 37 51 4C 0A
28:052 0:000 090 | 00 00 00 FC 00 44 45 4C 4C 20
28:052 0:000 100 | 55 32 35 31 35 48 0A 20 00 00
28:052 0:000 110 | 00 FD 00 38 56 1E 71 1E 00 0A
28:052 0:000 120 | 20 20 20 20 20 20 01 06
28:052 0:000 Intel HD Graphics 4600 [8086:0412] :: PciRoot(0x0)\Pci(0x2,0x0)
28:052 0:000 ig-platform-id = 0D220003
28:052 0:000 Intel GFX revision = 0x6
28:052 0:000 setting specified layout-id=86 (0x56)
28:052 0:000 setting specified layout-id=86 (0x56)
28:052 0:000 stringlength = 3300
28:052 0:000 CurrentMode: Width=1600 Height=1200
28:052 0:000 Beginning FSInjection
FSInjectionInstall ...
- Our FSI_SIMPLE_FILE_SYSTEM_PROTOCOL installed on handle: CCC62718
FSInjectionInstall ...
- Our FSI_SIMPLE_FILE_SYSTEM_PROTOCOL installed on handle: CCC62718
28:061 0:009 Use origin smbios table type 1 guid.
28:061 0:000 MSR 0x1B0 set to 00000000
28:066 0:004 Force kext: System\Library\Extensions\AppleHDA.kext
28:073 0:006 Force PlugIn kext: System\Library\Extensions\AppleHDA.kext\Contents\PlugIns\AppleHDAController.kext
28:077 0:004 Force PlugIn kext: System\Library\Extensions\AppleHDA.kext\Contents\PlugIns\AppleHDAHardwareConfigDriver.kext
28:081 0:004 Force PlugIn kext: System\Library\Extensions\AppleHDA.kext\Contents\PlugIns\AppleMikeyDriver.kext
28:084 0:003 Force PlugIn kext: System\Library\Extensions\AppleHDA.kext\Contents\PlugIns\DspFuncLib.kext
28:090 0:005 Force PlugIn kext: System\Library\Extensions\AppleHDA.kext\Contents\PlugIns\IOHDAFamily.kext
28:093 0:002 Force PlugIn kext: System\Library\Extensions\AppleHDA.kext\Contents\PlugIns\LegacyHDA.kext
28:096 0:002 Preparing kexts injection for arch=x86_64 from \EFI\CLOVER\kexts\Other
28:096 0:000 Preparing kexts injection for arch=x86_64 from EFI\CLOVER\OEM\B85M-G\UEFI\kexts\10.10
28:097 0:000 Extra kext: EFI\CLOVER\OEM\B85M-G\UEFI\kexts\10.10\AppleHDA.kext
28:115 0:018 Extra PlugIn kext: EFI\CLOVER\OEM\B85M-G\UEFI\kexts\10.10\AppleHDA.kext\Contents\PlugIns\AppleHDAController.kext
28:120 0:005 Extra PlugIn kext: EFI\CLOVER\OEM\B85M-G\UEFI\kexts\10.10\AppleHDA.kext\Contents\PlugIns\AppleHDAHardwareConfigDriver.kext
28:128 0:007 Extra PlugIn kext: EFI\CLOVER\OEM\B85M-G\UEFI\kexts\10.10\AppleHDA.kext\Contents\PlugIns\AppleMikeyDriver.kext
28:133 0:005 Extra PlugIn kext: EFI\CLOVER\OEM\B85M-G\UEFI\kexts\10.10\AppleHDA.kext\Contents\PlugIns\DspFuncLib.kext
28:151 0:017 Extra PlugIn kext: EFI\CLOVER\OEM\B85M-G\UEFI\kexts\10.10\AppleHDA.kext\Contents\PlugIns\IOHDAFamily.kext
28:155 0:004 Extra PlugIn kext: EFI\CLOVER\OEM\B85M-G\UEFI\kexts\10.10\AppleHDA.kext\Contents\PlugIns\LegacyHDA.kext
28:158 0:003 Extra kext: EFI\CLOVER\OEM\B85M-G\UEFI\kexts\10.10\CodecCommander.kext
28:166 0:007 Extra kext: EFI\CLOVER\OEM\B85M-G\UEFI\kexts\10.10\FakeSMC.kext
28:174 0:008 Extra kext: EFI\CLOVER\OEM\B85M-G\UEFI\kexts\10.10\RealtekRTL8111.kext
28:185 0:010 Custom boot is disabled
28:185 0:000 Closing log
Link to comment
Share on other sites

Hmmm.....

 

Really not sure what is going wrong, the UsbKbDxe loads, but needs to connect to the device. Am I wrong in assuming I need a working set of Usb drivers for Clover to make this work?

 

I've built Duet, but the CreateBootDisk.sh seems to be out of date, when I try to run it I get:[/size]

/Users/jam2/EDK7/edk2/DuetPkg/CreateBootDisk.sh usb /dev/disk1 /dev/disk1 FAT16 X64
Format /dev/disk1 ...
Create boot sector ...
ERROR: It's not a floppy disk!
GnuGenBootSector: ERROR 1003: Invalid option value
  Input file can't be found.
Path = Bs16-1.com
ERROR: It's not a floppy disk!
GnuGenBootSector: ERROR 1003: Invalid option value
  Output file can't be found.
Path = /Users/jam2/EDK7/edk2/DuetPkg/BootSector/bin/Mbr.com
ERROR: It's not a floppy disk!
GnuGenBootSector: ERROR 1003: Invalid option value
  Output file can't be found.
Done.
PLEASE UNPLUG USB, THEN PLUG IT AGAIN TO DO STEP2!
Same thing on Linux.

 

Can anyone offer any help on how to create a Duet USB Stick on OS X?

 

I spent a year making DUET working with Hackintosh. Now this is a part of Clover project named CloverEFI resulting "boot6" file.

cat $BOOTSECTOR_BIN_DIR/$startBlock $BOOTSECTOR_BIN_DIR/efi64.com3 "${BUILD_DIR}"/FV/Efildr64 > "${BUILD_DIR}"/FV/boot

  • Like 1
Link to comment
Share on other sites

I spent a year making DUET working with Hackintosh. Now this is a part of Clover project named CloverEFI resulting "boot6" file.

cat $BOOTSECTOR_BIN_DIR/$startBlock $BOOTSECTOR_BIN_DIR/efi64.com3 "${BUILD_DIR}"/FV/Efildr64 > "${BUILD_DIR}"/FV/boot

 

Slice, I tried the boot6 file, and my system failed to boot, got stuck loading the second stage( boot6 ). So I tried a USB Stick with the same boot6 on another PC, with Legacy Bios, and it worked. I was able to pull the drive from my main system, that I have FileVault2 enabled on, and both USB Keyboard and Mouse worked just fine.

 

I was able to login to FileVault and boot the OS.

 

The DevTree command from the EFI Shell, showed my USB KB and M as USB devices, and as Primary Console Input Devices. Tho I still had an entry for the Bios [init16] Keyboard.

 

I tried it on another Legacy Bios system I have, and it worked on that too.

 

My main system is an MCP79 GF9300 Motherboard, so I assume it uses the boot-MCP79 file from Clover. I tried to build Clover with the OhciDxe enabled in the build, to build it into the boot( FV? ) file, rather than as a separate .efi file. Because when I load the OhciDxe.efi, or the EhciDxe.efi in Clover's Drivers64 folder, I get a Exception State in Clover.

 

But, I don't seem to get that driver builtin to the boot-MCP79 file, when I compare the file with one I built without enabling Ohci, they are the same binary. So I'm doing something wrong.

 

The Clover.fdf has:

 # Usb Support
!ifndef DISABLE_USB_SUPPORT

!ifndef DISABLE_USB_CONTROLLERS
  INF  MdeModulePkg/Bus/Pci/UhciDxe/UhciDxe.inf
!ifndef DISABLE_USB_MASS_STORAGE
  INF  MdeModulePkg/Bus/Pci/EhciDxe/EhciDxe.inf
!endif
!endif

!ifdef ENABLE_USB_OHCI
  INF  Clover/Drivers/OhciDxe/OhciDxe.inf
!endif
!ifdef ENABLE_USB_XHCI
  #INF  MdeModulePkg/Bus/Pci/XhciDxe/XhciDxe.inf
  INF  Clover/Drivers/XhciDxe/XhciDxe.inf
!endif

  #INF  MdeModulePkg/Bus/Usb/UsbBusDxe/UsbBusDxe.inf
  INF  Clover/Drivers/UsbBusDxe/UsbBusDxe.inf
  #INF  MdeModulePkg/Bus/Usb/UsbKbDxe/UsbKbDxe.inf
  INF  Clover/Drivers/UsbKbDxe/UsbKbDxe.inf
  INF  MdeModulePkg/Bus/Usb/UsbMouseDxe/UsbMouseDxe.inf
!ifndef DISABLE_USB_MASS_STORAGE  
  INF  MdeModulePkg/Bus/Usb/UsbMassStorageDxe/UsbMassStorageDxe.inf
!endif  

!endif 

So I assume I need to somehow pass the ENABLE_USB_OHCI to the Clover build script. How would I do that?

 

Something like?

./ebuild.sh -D EXIT_USBKB=1 ENABLE_USB_OHCI 

Also, does the boot-MCP79 have a build script of it's own I need to edit?

 

Any advice is appreciated, I know how hard people have worked on Clover, it really does a lot. Keeps my old hardware working great, I'm getting close to fixing this issue with FV2 on my main system, just need a little help getting over the finish line, please.

Link to comment
Share on other sites

Your proposition is all Clover drivers are perfect. They aren't.

You should debug them and find workaround to do they working.  I can't do this because I have no such hardware.

Link to comment
Share on other sites

Your proposition is all Clover drivers are perfect. They aren't.

You should debug them and find workaround to do they working.  I can't do this because I have no such hardware.

 

I lack any real programing skills, I can hack a few lines of C, but really don't know how to set breakpoints to debug efi drivers.

 

Would you be so kind and to give me the build command for Clover to enable Ohci driver?

Link to comment
Share on other sites

Thanks Slice, but it seems the boot7-MCP79 file comes with Clover, pre-built. That is the file I need to boot on my motherboard.

 

Are there any sources for this boot7-MCP79 file?

 

Any way to rebuild it with Ohci support?

 

Just poking around a bit, seems there is a boot6, boot7, and boot7-MCP79, boot files for Clover, but when I build Clover I only get the pre-built boot7-MCP79 and the boot6 file is built with my build commands. I think my system can also use the boot7 file, but it is not being built.

 

Is there a command to build the boot7 file?

Link to comment
Share on other sites

Thanks Slice, but it seems the boot7-MCP79 file comes with Clover, pre-built. That is the file I need to boot on my motherboard.

 

Are there any sources for this boot7-MCP79 file?

 

Any way to rebuild it with Ohci support?

 

Just poking around a bit, seems there is a boot6, boot7, and boot7-MCP79, boot files for Clover, but when I build Clover I only get the pre-built boot7-MCP79 and the boot6 file is built with my build commands. I think my system can also use the boot7 file, but it is not being built.

 

Is there a command to build the boot7 file?

boot7-MCP79 is ordinary boot7 file but old version. This is the version that occasionally works on MCP79 motherboard. Something goes wrong in later revision and nobody debugs it.

I have no such platform so I decided just distribute those working revision and wait for new developer wanted to study the problem.

Link to comment
Share on other sites

×
×
  • Create New...