Clover General discussion

[magnifico]

 

Then make full DarwinDumper report. We want to see the origin of the error.

 

but i see good on System Profile

 

 

Hardware Overview:
 
      Model Name: iMac
      Model Identifier: iMac14,2
      Processor Name: Intel Core i5
      Processor Speed: 4,7 GHz

[wern apfel]

While booting i have a tiny loading bar and apple logo on an UHD-res monitor, i've tried with booterconfig bit 1 (0x2) other values too but no changes, isn't that the right value ?

 

#define kBootArgsFlagRebootOnPanic (1 << 0)

#define kBootArgsFlagHiDPI (1 << 1)
#define kBootArgsFlagBlack (1 << 2)
#define kBootArgsFlagCSRActiveConfig    (1 << 3)
#define kBootArgsFlagCSRPendingConfig    (1 << 4)
#define kBootArgsFlagCSRBoot (1 << 5)
#define kBootArgsFlagBlackBg (1 << 6)
#define kBootArgsFlagLoginUI (1 << 7)

 

Is that not a HiDPI boot mode ?

[MaLd0n]

Great Work! Thank u very much! 

[magnifico]

Great Work! Thank u very much!

Hey how are you. ..lol

The Man of B&W

[Andres ZeroCross]

Hi,, i want to ask
 

If i boot legacy bios with Clover why my Graphics Injection won't effect. I still need to tick Inject Nvidia to get desktop.
But if i use boot UEFI mode with clover, i can use my Graphics Injection with DSDT.

Any help?

[Slice]

Hi,, i want to ask

 

If i boot legacy bios with Clover why my Graphics Injection won't effect. I still need to tick Inject Nvidia to get desktop.

But if i use boot UEFI mode with clover, i can use my Graphics Injection with DSDT.

 

Any help?

A help is possible if reports provided.

[Multisaft]

could someone redirect me to any text where booting into a x58 not uefi motherboard (asus p6t-se) is described? i've reading a lot around the clover wiki: http://clover-wiki.zetam.org/What-is-what#MBR-sector
what I understood as of now is, that my bios does not support UEFI Boot, therefore its the legacy boot way. So I use the clover installer of the newest 3220 version, and I have managed to boot into the Yosemite installation using the ssecond installation option in the bootloader tap (boot0af in MBR). I've didnt used the "Install for UEFI booting only" and I've also unchecked "Install Clover in the ESP". In addition I'm using the kexts recommended in the clover-wiki for my Bios (HFSPlus.efi, OsxFatBinaryDrv-64.efi, OsxAptioFixDrv-64.efi)  Is it correct, that clover will use the option A described in the clover-wiki? therefore booting (with my computer configuration described and in my signature) into the CloverX64.efi? And in this procedure, it uses the drivers installed in the folder \drivers64UEFI\ ??
 
So what I dont understand is my problem described in the framebuffer patch thread for amd radeon graphics.

I've managed to boot into my Yosemite installation by letting the computer go to sleep, waking it up afterwards got me full 4k 60fps through my display port 1.2 (I've added the framebuffer patch, ati-injektion, framebuffer name into the clover configuration). Therefore I thought ok, the FB patch must have been correct.
 
But now, I'm not able to boot into the Yosemite installation on my SSD using my USB Installer. Its alway the 'black screen' issue (inject ati), or 'white screen' issue (do not inject ati). I'm using the fakesmc, when I use the debug mode, it tells me, that clover is using the fakesmc, and it managed to inject the fb into the AMD7000 kext, but it also tells me, that it didnt patched (or failed?) to patch the AMDFramebuffer kext. Hm and then there is the black screen again. Also, the computer does not go to sleep - I thought, maybe I can just let it go to sleep, waking up will give me 4k 60fps from display port again. But that does not work. I would love to get some advice plz!! And plz to the moderator, I hope that this is not a crosspost. Maybe I should put my questions Ive written down in the FB Patching thread here and delete it in the ATI board (I think I'm failing to use clover, and not fb-patching).[/size]
 
and last: I dont have a debug outputto /EFI/CLOVER/misc/debug.log
what could cause that problem? is it the failed boot up and my hard power reset, that clover is not able to write the debug output into the specified folder?

[Micky1979]

@Multisaft, ErmaC was (is?) using that Mobo, but always need to patch the AppleACPIPlatforms.kext's Info.plist adding a property to prevent a problem called "long boot". Not sure this info can be of help..

[Slice]

could someone redirect me to any text where booting into a x58 not uefi motherboard (asus p6t-se) is described? i've reading a lot around the clover wiki: http://clover-wiki.zetam.org/What-is-what#MBR-sector

what I understood as of now is, that my bios does not support UEFI Boot, therefore its the legacy boot way. So I use the clover installer of the newest 3220 version, and I have managed to boot into the Yosemite installation using the ssecond installation option in the bootloader tap (boot0af in MBR). I've didnt used the "Install for UEFI booting only" and I've also unchecked "Install Clover in the ESP". In addition I'm using the kexts recommended in the clover-wiki for my Bios (HFSPlus.efi, OsxFatBinaryDrv-64.efi, OsxAptioFixDrv-64.efi)  Is it correct, that clover will use the option A described in the clover-wiki? therefore booting (with my computer configuration described and in my signature) into the CloverX64.efi? And in this procedure, it uses the drivers installed in the folder \drivers64UEFI\ ??

 

1.   (HFSPlus.efi, OsxFatBinaryDrv-64.efi, OsxAptioFixDrv-64.efi)

2.  "Install Clover in the ESP" check if you have ESP.

3.  it uses the drivers installed in the folder \drivers64UEFI\ ? No,  \drivers64\

Read instructions in this forum.

[Slice]

By default, when Clover scans your partitions for loaders, each volume found is checked for Linux installations. This check takes a short time, but becomes more noticeable with the more volumes you have. And using a theme with larger icons, for example BGM256, takes even longer.

 

Commit #3325 adds the option for you to disable the scan for Linux installations if you know you don’t have any.

 

To disable the scan, you can now add Linux=false to the GUI->Scan section of your config.plist.

<key>GUI</key>
<dict>
  <key>Scan</key>
  <dict>
    <key>Linux</key>
    <false/>
  </dict>
</dict>

Legacy booting now loads the GUI 2 seconds faster for me.

 

I move your post to "Clover change explanations"

[illuminarias]

Hello,

I got my hackintosh up and running fine. However, I noticed that my SMBIOS never loads "MacBookAir6,2", but it loads as "MacBookAir6". I've done multiple EFI wipes and reinstalls, full wipe and reinstall, reinstall with different method (manually creating the boot drive and using [url=&quot;http://www.insanelymac.com/forum/topic/279450-why-insanelymac-does-not-support-tonymacx86/&quot;]#####[/url]), different config.plist during install, different config.plist after install, but nothing ever works. 

 

If I change my SMBIOS to "MacBook6,2" or "iMac 11,3" , it would load properly. It's as if it's running into a character limit and wouldn't load the last 2 characters of "MacBookAir6,2".

Does anyone have any idea?

[LockDown]

Fill this:

 

ProductName

Family

SerialNumber

BiosVersion

[Ramalama]

Does anyone know any way to write into nvram from windows?

to boot into OS X...

 

Cheers :-)

[WinstonAce]

Boot to shell

You can add entry to clover shell with easyuefi for windows

[Multisaft]

1.   (HFSPlus.efi, OsxFatBinaryDrv-64.efi, OsxAptioFixDrv-64.efi)

2.  "Install Clover in the ESP" check if you have ESP.

3.  it uses the drivers installed in the folder \drivers64UEFI\ ? No,  \drivers64\

Read instructions in this forum.

 

Hi Slice,

 

1) and 3) if Clover legacy boot (boot0af in MBR) does not use the drivers in /drivers64UEFI/ and instead needs the drivers installed in /drivers64/, then I don't even need the drivers in /drivers64UEFI/ right? In my drivers folder /drivers64/ I've descided to go with the minimal configuration, therefore: HFSPlus.efi and FSInject-64.efi (the last one is added every time when I install clover to my usb installer).

 

2) I've tried to use the ESP Installation for 2 days in a row, but that doesn't even gives me any possible boot up. It just gives me two rows of information:

b1f: init
b1f: error_

and after that, the next boot sequence is used with is boot0af (the second clover installation). And I don't think, that this is the problem in my case. I think it is the graphics injection.

 

 

___

 

4) next questions: even with 

<key>Debug</key>
<true/>

in my boot flags, clover doesn't put the debug output into the /misc/ folder. Could that be because I need to hard reset my computer as I'm stuck with the 'black screen' issue after my AMD7000Controller injection?

 

5) In addition to my explizit AMD7000Controller patching for my Futomaki FB (I'm using the Powercolor AMD R9 270x PCS+), the debug log when clover starts tells me, that the AMD7000 Framebuffer is correctly patched, but in front of this FB-patching, clover debug mode tells me, that the AMDFramebuffer is not being patched. How to find out, which framebuffer Clover or OS X Yosemite tries to use when it boots up (like i said, just the black screen issue is around). Behind that, I think everything is fine and will work without so many problems, but this disgusting graphics card. 

<key>Graphics</key>
	<dict>
		<key>FBName</key>
		<string>Futomaki</string>
		<key>Inject</key>
		<dict>
			<key>ATI</key>
			<true/>
			<key>Intel</key>
			<false/>
			<key>NVidia</key>
			<false/>
		</dict>
		<key>InjectEDID</key>
		<true/>
		<key>NvidiaSingle</key>
		<false/>
		<key>VideoPorts</key>
		<integer>4</integer>
	</dict>
	<key>KernelAndKextPatches</key>
	<dict>
		<key>ATIConnectorsController</key>
		<string>7000</string>
		<key>ATIConnectorsData</key>
		<string>00040000040300000001010112040401000400000403000000010201220505020400000014020000000103000000060600080000040200000001040011020103</string>
		<key>ATIConnectorsPatch</key>
		<string>00040000040300000001020112040101000200000402000000010101100003060400000014020000000103001102050500080000000200000001040022050203</string>
		<key>AppleRTC</key>
		<true/>
		<key>AsusAICPUPM</key>
		<false/>
		<key>Debug</key>
		<true/>
		<key>KernelCpu</key>
		<false/>
		<key>KernelHaswellE</key>
		<false/>
		<key>KernelLapic</key>
		<false/>
		<key>KernelPm</key>
		<false/>
	</dict>

[Slice]

 

 

2) I've tried to use the ESP Installation for 2 days in a row, but that doesn't even gives me any possible boot up.

You should know how it works and what is the condition to successful boot.

boot1f32 located at ESP partition seems to be started (b1f:init...).

Then it searches file BOOT in the root of the partition. Is it present? (b1f:error...)

Is it true that this partition formatted to FAT32 and not to FAT16, not HFS+?

 

 

 

 And I don't think, that this is the problem in my case. I think it is the graphics injection

This step is much before any injection.

 

 

 

in my boot flags, clover doesn't put the debug output into the /misc/ folder. Could that be because I need to hard reset my computer as I'm stuck with the 'black screen' issue after my AMD7000Controller injection?

Debug key works before any injection and it really works.

The problem is your case may be ESP formatted not to FAT32.

 

 

 

AMDFramebuffer is not being patched

It is normal. For your case it shouldn't be patched. 7000Controller must be patched instead.

[Multisaft]

You should know how it works and what is the condition to successful boot.

boot1f32 located at ESP partition seems to be started (b1f:init...).

Then it searches file BOOT in the root of the partition. Is it present? (b1f:error...)

Is it true that this partition formatted to FAT32 and not to FAT16, not HFS+?

 

This step is much before any injection.

 

Debug key works before any injection and it really works.

The problem is your case may be ESP formatted not to FAT32.

 

It is normal. For your case it shouldn't be patched. 7000Controller must be patched instead.

 

Hey, OK its going forward

 

I've made a mistake in my own reasoning. I've managed to boot with my usb-stick where Clover is installed in the EFI partition, boot0af is selected, FakeSMC.kext in the 10.10 kexts folder, nothing else installed. Now Clover scans every entity, when I now choose my Yosemite SSD where the installation procedure has taken place, I'm getting debug/verbose information. So that does work like a charm. Thank you for setting me back on track Slice!!!

 

In addition Clover gives me the boot log. Does it help, when I add it here (see below for the debug log with ATI graphics injection - I'm not permitted to upload log files - therefore I've pasted it below).

 

Now I'm still stucked at the white screen/black screen issue.

 

I've made a list where you can see my results in different configurations of my config.plist and video outputs (DP, DVI-D to HDMI) used.

 

1. ATI Inject true, patched AMD7000 Framebuffer, DP 1.2 used: boots up (Log below), but after boot verbose information -> Black screen (monitor switch to standby).
2. ATI Inject true, patched AMD7000 Framebuffer, DVI-D to HDMI 1.2 (the Philips 40" 4k Monitor does not offer DVI Inputs): boots up (Log below), but after boot verbose information -> White screen (monitor does not switch to standby, it stays on).
3. ATI Inject false, not patched AMD7000 Framebuffer, DP 1.2: boots up, but after boot verbose information -> White Screen for one second, then back to Black screen (monitor switch to standby).
4. ATI Inject false, not patched AMD7000 Framebuffer, DVI-D to HDMI 1.2: boots up, but after boot verbose information -> White Screen for one second, then back to Black screen (monitor switch to standby).

Ok

 

and here is the boot.log of my ATI Inject true, and patched AMD7000FB (case 1):

0:100  0:100  MemLog inited, TSC freq: 3400016813
0:100  0:000  LegacyRegion2: Chipset/proc: 0x34058086
0:100  0:000   Core i7 processors (PAM 0x40-0x47)
0:100  0:000   Test PAM1=(0x41=11, 0x5a=00, 0x81=0B, 0x91=33) at chipset 34058086
0:100  0:000  , Install = Success
0:115  0:015  BiosVideoDriverBindingStart!
0:115  0:000  BiosVideoCheckForVbe
0:115  0:000  EdidOverride not found
0:115  0:000   Edid1+
0:115  0:000   found Detail Timing 3840x2160
0:115  0:000   found Detail Timing 3840x2160
0:115  0:000   Edid0+
0:115  0:000   found Detail Timing 3840x2160
0:115  0:000  ... already present
0:115  0:000   found Detail Timing 3840x2160
0:115  0:000  ... already present
0:127  0:012     0 1280x960 attr=BB - ok, edid+, working, highest, pref=0
0:128  0:000     1 640x480 attr=BB - ok, edid+, 640x480, working
0:129  0:000     2 800x600 attr=BB - ok, edid+, 800x600, working
0:129  0:000     3 1024x768 attr=BB - ok, edid+, 1024x768, working
0:130  0:000     4 1280x1024 attr=BB - ok, edid+, working, highest, pref=4
0:133  0:003     5 1400x1050 attr=BB - ok, edid-
0:136  0:003     6 1600x1200 attr=BB - ok, edid-
0:138  0:002  BV new mode: 4 1280x1024
0:206  0:067   SetMode pref 4 (4) = Success
3:082  2:876  
3:082  0:000  Now is 30.11.2015,  17:45:27 (GMT+2047)
3:082  0:000  Starting Clover rev 3320 on CLOVER EFI
3:082  0:000  SelfDevicePath=PcieRoot(0x0)\Pci(0x1A,0x7)\USB(0x0,0x0)\HD(1,GPT,8146553F-44AE-43D0-9061-6CCE768DDC91,0x28,0x64000) @BDAB5418
3:082  0:000  SelfDirPath = \EFI\CLOVER
3:082  0:000  Total Memory Slots Count = 6
3:082  0:000  Type 17 Index = 0
3:082  0:000  SmbiosTable.Type17->Speed = 1333MHz
3:082  0:000  SmbiosTable.Type17->Size = 4096MB
3:082  0:000  SmbiosTable.Type17->Bank/Device = BANK0 DIMM0
3:082  0:000  Type 17 Index = 1
3:082  0:000  Ignoring insane frequency value 0MHz
3:082  0:000  SmbiosTable.Type17->Speed = 0MHz
3:082  0:000  SmbiosTable.Type17->Size = 0MB
3:082  0:000  SmbiosTable.Type17->Bank/Device = BANK1 DIMM1
3:082  0:000  Type 17 Index = 2
3:082  0:000  SmbiosTable.Type17->Speed = 1333MHz
3:082  0:000  SmbiosTable.Type17->Size = 4096MB
3:082  0:000  SmbiosTable.Type17->Bank/Device = BANK2 DIMM2
3:082  0:000  Type 17 Index = 3
3:082  0:000  Ignoring insane frequency value 0MHz
3:082  0:000  SmbiosTable.Type17->Speed = 0MHz
3:082  0:000  SmbiosTable.Type17->Size = 0MB
3:082  0:000  SmbiosTable.Type17->Bank/Device = BANK3 DIMM3
3:082  0:000  Type 17 Index = 4
3:082  0:000  SmbiosTable.Type17->Speed = 1333MHz
3:082  0:000  SmbiosTable.Type17->Size = 4096MB
3:082  0:000  SmbiosTable.Type17->Bank/Device = BANK4 DIMM4
3:082  0:000  Type 17 Index = 5
3:082  0:000  Ignoring insane frequency value 0MHz
3:082  0:000  SmbiosTable.Type17->Speed = 0MHz
3:082  0:000  SmbiosTable.Type17->Size = 0MB
3:082  0:000  SmbiosTable.Type17->Bank/Device = BANK5 DIMM5
3:082  0:000  Boot status=0
3:082  0:000  Clover revision: 3320  running on System Product Name
3:082  0:000  ... with board P6T SE
3:082  0:000  CPU Vendor = 756E6547 Model=206C2
3:082  0:000  The CPU not supported turbo
3:082  0:000  BrandString = Intel(R) Xeon(R) CPU           X5660  @ 2.80GHz
3:082  0:000  FSBFrequency=161MHz DMIvalue=161000kHz
3:082  0:000  Corrected FSBFrequency=161MHz
3:082  0:000  Vendor/Model/Stepping: 0x756E6547/0x2C/0x2
3:082  0:000  Family/ExtFamily: 0x6/0x0
3:082  0:000  MaxDiv/MinDiv: 21.0/12
3:082  0:000  Turbo: 0/0/0/0
3:082  0:000  Features: 0xBFEBFBFF
3:082  0:000  Threads: 12
3:082  0:000  Cores: 6
3:082  0:000  FSB: 161 MHz
3:082  0:000  CPU: 3400 MHz
3:082  0:000  TSC: 3400 MHz
3:082  0:000  PIS: 644 MHz
3:082  0:000  PCI (00|00:00.00) : 8086 3405 class=060000
3:082  0:000  PCI (00|00:01.00) : 8086 3408 class=060400
3:082  0:000  PCI (00|00:03.00) : 8086 340A class=060400
3:082  0:000  PCI (00|00:07.00) : 8086 340E class=060400
3:082  0:000  PCI (00|03:00.00) : 1002 6810 class=030000
3:082  0:000  Found Radeon model=AMD Radeon R9 270X
3:082  0:000  PCI (00|03:00.01) : 1002 AAB0 class=040300
3:082  0:000  PCI (00|00:14.00) : 8086 342E class=080000
3:082  0:000  PCI (00|00:14.01) : 8086 3422 class=080000
3:082  0:000  PCI (00|00:14.02) : 8086 3423 class=080000
3:082  0:000  PCI (00|00:14.03) : 8086 3438 class=080000
3:082  0:000  PCI (00|00:1A.00) : 8086 3A37 class=0C0300
3:082  0:000  PCI (00|00:1A.01) : 8086 3A38 class=0C0300
3:082  0:000  PCI (00|00:1A.02) : 8086 3A39 class=0C0300
3:082  0:000  PCI (00|00:1A.07) : 8086 3A3C class=0C0320
3:082  0:000  PCI (00|00:1B.00) : 8086 3A3E class=040300
3:082  0:000  PCI (00|00:1C.00) : 8086 3A40 class=060400
3:082  0:000  PCI (00|00:1C.01) : 8086 3A42 class=060400
3:083  0:000  PCI (00|07:00.00) : 1912 0014 class=0C0330
3:083  0:000  PCI (00|00:1C.02) : 8086 3A44 class=060400
3:083  0:000  PCI (00|06:00.00) : 10EC 8168 class=020000
3:083  0:000  LAN 0, Vendor=10EC, MMIO=E800
3:083  0:000  PCI (00|00:1C.03) : 8086 3A46 class=060400
3:083  0:000  PCI (00|05:00.00) : 1106 3403 class=0C0010
3:083  0:000  PCI (00|00:1C.04) : 8086 3A48 class=060400
3:083  0:000  PCI (00|04:00.00) : 197B 2363 class=010185
3:083  0:000  PCI (00|00:1D.00) : 8086 3A34 class=0C0300
3:083  0:000  PCI (00|00:1D.01) : 8086 3A35 class=0C0300
3:083  0:000  PCI (00|00:1D.02) : 8086 3A36 class=0C0300
3:083  0:000  PCI (00|00:1D.07) : 8086 3A3A class=0C0320
3:083  0:000  PCI (00|00:1E.00) : 8086 244E class=060401
3:083  0:000  PCI (00|00:1F.00) : 8086 3A16 class=060100
3:083  0:000  PCI (00|00:1F.02) : 8086 3A22 class=010601
3:083  0:000  PCI (00|00:1F.03) : 8086 3A30 class=0C0500
3:083  0:000  PCI (00|FF:00.00) : 8086 2C70 class=060000
3:083  0:000  PCI (00|FF:00.01) : 8086 2D81 class=060000
3:083  0:000  PCI (00|FF:02.00) : 8086 2D90 class=060000
3:083  0:000  PCI (00|FF:02.01) : 8086 2D91 class=060000
3:083  0:000  PCI (00|FF:02.02) : 8086 2D92 class=060000
3:083  0:000  PCI (00|FF:02.03) : 8086 2D93 class=060000
3:083  0:000  PCI (00|FF:02.04) : 8086 2D94 class=060000
3:083  0:000  PCI (00|FF:02.05) : 8086 2D95 class=060000
3:083  0:000  PCI (00|FF:03.00) : 8086 2D98 class=060000
3:083  0:000  PCI (00|FF:03.01) : 8086 2D99 class=060000
3:083  0:000  PCI (00|FF:03.02) : 8086 2D9A class=060000
3:083  0:000  PCI (00|FF:03.04) : 8086 2D9C class=060000
3:083  0:000  PCI (00|FF:04.00) : 8086 2DA0 class=060000
3:083  0:000  PCI (00|FF:04.01) : 8086 2DA1 class=060000
3:083  0:000  PCI (00|FF:04.02) : 8086 2DA2 class=060000
3:083  0:000  PCI (00|FF:04.03) : 8086 2DA3 class=060000
3:083  0:000  PCI (00|FF:05.00) : 8086 2DA8 class=060000
3:083  0:000  PCI (00|FF:05.01) : 8086 2DA9 class=060000
3:083  0:000  PCI (00|FF:05.02) : 8086 2DAA class=060000
3:083  0:000  PCI (00|FF:05.03) : 8086 2DAB class=060000
3:083  0:000  PCI (00|FF:06.00) : 8086 2DB0 class=060000
3:083  0:000  PCI (00|FF:06.01) : 8086 2DB1 class=060000
3:083  0:000  PCI (00|FF:06.02) : 8086 2DB2 class=060000
3:083  0:000  PCI (00|FF:06.03) : 8086 2DB3 class=060000
3:083  0:000  Clover load options size = 0 bytes
3:141  0:057  Using OEM config.plist at path: EFI\CLOVER\config.plist
3:141  0:000  EFI\CLOVER\config.plist loaded: Success
3:141  0:000  Found theme directory: embedded
3:141  0:000  Found theme directory: random
3:156  0:014  Loading early settings
3:156  0:000  timeout set to 5
3:156  0:000  Custom boot CUSTOM_BOOT_DISABLED (0x0)
5:756  2:600  Default theme: embedded
5:874  0:117  LoadDrivers() start
5:991  0:117  Loading FSInject-64.efi  status=Success
6:362  0:370  Loading VBoxHfs-64.efi  status=Success
6:717  0:355   - driver needs connecting
6:835  0:117  1 drivers needs connecting ...
6:952  0:117  PlatformDriverOverrideProtocol->GetDriver overriden
8:371  1:418  LoadDrivers() end
8:489  0:117  SetScreenResolution: 1920x1080 - not found!
8:724  0:235  Console modes reported: 4, available modes:
8:842  0:117    Mode 1: 80x25
8:962  0:119    Mode 2: 80x50
9:081  0:119    Mode 3: 100x31
9:199  0:117    Mode 4: 160x53 (current mode)
9:317  0:117  SetScreenResolution: 1280x1024 - already set
9:554  0:237  reinit: self device path=PcieRoot(0x0)\Pci(0x1A,0x7)\USB(0x0,0x0)\HD(1,GPT,8146553F-44AE-43D0-9061-6CCE768DDC91,0x28,0x64000)
10:904  1:349   get legacy LAN MAC, 1 card found
11:021  0:117  Legacy MAC address of LAN #0= 00:26:18:5B:C0:88:
11:967  0:945  ScanSPD() start
12:085  0:118  SMBus CmdReg: 0x103
12:205  0:119  Scanning SMBus [8086:3A30], mmio: 0xFB9FD004, ioport: 0x400, hostc: 0x1
12:325  0:119  Slots to scan [8]...
12:468  0:142  SPD[0]: Type 11 @0x50 
12:595  0:127  Found module with XMP version 1.2DDR speed 1333MHz 
12:830  0:235  Slot: 0 Type 24 4096MB 1333MHz Vendor=Kingston PartNo=9905403-197.A00LF SerialNo=0504030C0E02080A 
13:046  0:215  SPD[2]: Type 11 @0x52 
13:173  0:127  Found module with XMP version 1.2DDR speed 1333MHz 
13:425  0:252  Slot: 2 Type 24 4096MB 1333MHz Vendor=Kingston PartNo=9905403-197.A00LF SerialNo=0504030C0D0E080A 
13:565  0:139  SPD[4]: Type 11 @0x54 
13:692  0:127  Found module with XMP version 1.2DDR speed 1333MHz 
13:927  0:235  Slot: 4 Type 24 4096MB 1333MHz Vendor=Kingston PartNo=9905403-197.A00LF SerialNo=0504030C0E07080A 
14:063  0:135  ScanSPD() end
14:256  0:192  Get Acpi Tables List from RSDT:
14:508  0:252   Found table: FACP  FACP1134 len=132
14:628  0:119   Found table: APIC  APIC1134 len=216
14:746  0:117   Found table: MCFG  OEMMCFG  len=60
14:863  0:117   Found table: OEMB  OEMB1134 len=114
14:981  0:117   Found table: HPET  OEMHPET  len=56
15:099  0:117   Found table: OSFR  OEMOSFR  len=176
15:216  0:117   Found table: SSDT  CpuPm len=867
15:334  0:117  Calibrated TSC frequency =3400016813 =3400MHz
15:469  0:134  Loading main settings
15:662  0:193  USB FixOwnership: true
15:780  0:117  Dropping 3 tables
15:897  0:117  Drop table 0 signature="SSDT" (54445353) table-id="CpuPm" (0000006D50757043)
17:698  1:800  set table: 54445353,       6D50757043 to drop:  true
17:933  0:235  
18:051  0:117  Drop table 1 signature="DMAR" (52414D44)
19:018  0:966  set table: 52414D44,                0 to drop:
19:254  0:236  Drop table 2 signature="SSDT" (54445353) table-id="Cpu0Ist" (0074734930757043)
21:296  2:041  set table: 54445353,   74734930757043 to drop:
21:615  0:319  Config set Fixes will override FixMask mask!
21:741  0:125     final mask=9FC2F9D7
21:859  0:118  found 22 volumes with blockIO
21:976  0:117   0. Volume:
22:094  0:117    PcieRoot(0x0)\Pci(0x1A,0x7)\USB(0x0,0x0)
22:223  0:129    Result of bootcode detection: bootable unknown (legacy)
22:341  0:117    USB volume
22:467  0:126   1. Volume:
22:585  0:117    PcieRoot(0x0)\Pci(0x1A,0x7)\USB(0x0,0x0)\HD(1,GPT,8146553F-44AE-43D0-9061-6CCE768DDC91,0x28,0x64000)
22:789  0:204    Result of bootcode detection: bootable Clover (clover)
22:915  0:126    USB volume
23:041  0:126    This is SelfVolume !!
23:159  0:117   2. Volume:
23:277  0:117    PcieRoot(0x0)\Pci(0x1A,0x7)\USB(0x0,0x0)\HD(2,GPT,979E3B42-AED4-42D1-AE9C-D41589358EF1,0x64028,0xE4BFB0)
23:414  0:137    USB volume
23:532  0:117   3. Volume:
23:650  0:117    PcieRoot(0x0)\Pci(0x1F,0x2)\Sata(0x0,0x0,0x0)
23:769  0:119   4. Volume:
23:895  0:126    PcieRoot(0x0)\Pci(0x1F,0x2)\Sata(0x1,0x0,0x0)
24:013  0:117    Result of bootcode detection: bootable unknown (legacy)
24:237  0:224   5. Volume:
25:532  1:295    PcieRoot(0x0)\Pci(0x1F,0x2)\Sata(0x2,0x0,0x0)
25:650  0:117   6. Volume:
25:768  0:117    PcieRoot(0x0)\Pci(0x1F,0x2)\Sata(0x3,0x0,0x0)
25:886  0:118   7. Volume:
26:004  0:118    PcieRoot(0x0)\Pci(0x1F,0x2)\Sata(0x4,0x0,0x0)
26:123  0:118    Result of bootcode detection: bootable unknown (legacy)
26:249  0:126   8. Volume:
26:367  0:117    PcieRoot(0x0)\Pci(0x1F,0x2)\Sata(0x5,0x0,0x0)
26:485  0:117    found optical drive
26:691  0:206  Detected name Bluebirds
26:817  0:126    Result of bootcode detection: bootable unknown (legacy)
26:935  0:117   9. Volume:
27:053  0:117    PcieRoot(0x0)\Pci(0x1F,0x2)\Sata(0x0,0x0,0x0)\HD(1,GPT,532552A0-0860-430F-8BED-539737C52383,0x28,0x64000)
27:173  0:119    Result of bootcode detection: bootable unknown (legacy)
27:301  0:128  10. Volume:
27:419  0:117    PcieRoot(0x0)\Pci(0x1F,0x2)\Sata(0x0,0x0,0x0)\HD(2,GPT,02F83038-3F89-4D5F-A030-71E74BA66F67,0x64028,0x1D02BA00)
27:623  0:203  11. Volume:
27:741  0:117    PcieRoot(0x0)\Pci(0x1F,0x2)\Sata(0x0,0x0,0x0)\HD(3,GPT,A9B5F873-CF65-43FF-852F-3A17679C0DCF,0x1D08FA28,0x135F20)
27:860  0:119  12. Volume:
27:978  0:117    PcieRoot(0x0)\Pci(0x1F,0x2)\Sata(0x1,0x0,0x0)\HD(1,GPT,2C9154F9-8A8D-4B50-8F08-39281F2E6DEA,0x28,0x64000)
28:096  0:118    Result of bootcode detection: bootable unknown (legacy)
28:215  0:118  13. Volume:
28:333  0:117    PcieRoot(0x0)\Pci(0x1F,0x2)\Sata(0x1,0x0,0x0)\HD(2,GPT,32C9EF73-4C90-44C0-9FCF-D4FE9F0472F6,0x64028,0xDEF0B60)
28:543  0:210    Result of bootcode detection: bootable unknown (legacy)
28:661  0:117  14. Volume:
28:779  0:117    PcieRoot(0x0)\Pci(0x1F,0x2)\Sata(0x2,0x0,0x0)\HD(1,GPT,E91F4946-1447-4BD3-B0DE-BD3C5D27DDDC,0x28,0x64000)
28:897  0:118    Result of bootcode detection: bootable unknown (legacy)
29:033  0:135  15. Volume:
29:151  0:117    PcieRoot(0x0)\Pci(0x1F,0x2)\Sata(0x2,0x0,0x0)\HD(2,GPT,A94D0D96-0DF8-49FA-87D4-799E3A552472,0x64028,0x49201BC8)
29:269  0:117  16. Volume:
29:471  0:201    PcieRoot(0x0)\Pci(0x1F,0x2)\Sata(0x2,0x0,0x0)\HD(3,GPT,1B766DD0-4CAC-4C6A-8DC8-E6127428E7C0,0x492A5BF0,0x1E00000)
29:598  0:126  17. Volume:
29:715  0:117    PcieRoot(0x0)\Pci(0x1F,0x2)\Sata(0x2,0x0,0x0)\HD(4,GPT,8DC3CD71-564F-456C-A079-2AF5639B637F,0x4B0E5BF0,0x295E1198)
29:833  0:118  18. Volume:
29:951  0:117    PcieRoot(0x0)\Pci(0x1F,0x2)\Sata(0x3,0x0,0x0)\HD(1,GPT,C34153CC-FD39-4B60-AC48-930A478F1CD8,0x28,0x64000)
30:069  0:118    Result of bootcode detection: bootable unknown (legacy)
30:306  0:236  19. Volume:
30:424  0:118    PcieRoot(0x0)\Pci(0x1F,0x2)\Sata(0x3,0x0,0x0)\HD(2,GPT,2624FDF4-9E72-43C3-843D-AF7A490FBA79,0x64028,0x74662D60)
30:542  0:117  20. Volume:
30:669  0:126    PcieRoot(0x0)\Pci(0x1F,0x2)\Sata(0x4,0x0,0x0)\HD(1,GPT,E1C86820-9400-4F5F-8EE1-EB7ABE3163AB,0x28,0x64000)
30:795  0:126    Result of bootcode detection: bootable unknown (legacy)
30:914  0:118  21. Volume:
31:034  0:120    PcieRoot(0x0)\Pci(0x1F,0x2)\Sata(0x4,0x0,0x0)\HD(2,GPT,938F9E0A-5020-478C-B8CE-949085D5987A,0x64028,0xEDD8260)
31:319  0:285  PutNvramPlistToRtVars: nvram.plist not found
31:446  0:126   using embedded theme
31:564  0:118  Choosing theme <null string>
31:682  0:118  Custom entries start
31:800  0:117  Custom entries finish
31:926  0:126  Scanning loaders...
32:044  0:117   0: 'Whole Disc Boot' no file system
32:280  0:235   1: 'EFI'
32:634  0:354   2: 'Installer'
32:885  0:251   3: 'Whole Disc Boot' no file system
33:130  0:244   4: 'Whole Disc Boot' no file system
33:449  0:319   5: 'Whole Disc Boot' no file system
33:685  0:235   6: 'Whole Disc Boot' no file system
33:921  0:235   7: 'Whole Disc Boot' no file system
34:165  0:244   8: 'Bluebirds' no file system
34:409  0:244   9: 'EFI'
34:654  0:244  10: 'OS X Yosemite'
34:892  0:238      AddLoaderEntry for Volume Name=OS X Yosemite
35:012  0:119      Check if volume Is Hibernated:
35:130  0:117      Check sleep image 'by signature':
35:260  0:129      read prefs \Library\Preferences\SystemConfiguration\com.apple.PowerManagement.plist status=Not Found
35:462  0:201      using default sleep image name = \private\var\vm\sleepimage
35:582  0:120      sleepimage not found -> Not Found
35:700  0:117       hibernated: no - sign
35:821  0:120  11: 'Recovery HD'
36:058  0:237      AddLoaderEntry for Volume Name=Recovery HD
36:180  0:121  12: 'EFI'
36:424  0:244  13: 'Mac OS X'
36:672  0:247      AddLoaderEntry for Volume Name=Mac OS X
36:791  0:119      Check if volume Is Hibernated:
36:909  0:117      Check sleep image 'by signature':
37:105  0:195      read prefs \Library\Preferences\SystemConfiguration\com.apple.PowerManagement.plist status=Success
37:223  0:117      SleepImage name from pref: ImageVolume = 'Mac OS X', ImageName = '\private\var\vm\sleepimage'
37:343  0:119      sleepimage not found -> Not Found
37:478  0:134       hibernated: no - sign
37:610  0:131  14: 'EFI'
37:846  0:236  15: 'Data'
38:091  0:245  16: 'Kally'
38:328  0:236  17: 'Misc'
38:582  0:253  18: 'EFI'
38:894  0:311  19: 'Medien'
39:131  0:237  20: 'EFI'
39:375  0:244  21: 'Mac OS X 10.9.5 Backup'
39:622  0:246      AddLoaderEntry for Volume Name=Mac OS X 10.9.5 Backup
39:741  0:119      Check if volume Is Hibernated:
39:859  0:117      Check sleep image 'by signature':
39:980  0:120      read prefs \Library\Preferences\SystemConfiguration\com.apple.PowerManagement.plist status=Success
40:098  0:117      SleepImage name from pref: ImageVolume = 'Mac OS X 10.9.5 Backup', ImageName = '\private\var\vm\sleepimage'
40:296  0:197      sleepimage not found -> Not Found
40:422  0:126       hibernated: no - sign
40:552  0:129  Custom legacy start
40:678  0:126  Custom legacy end
40:796  0:117  Scanning legacy ...
40:914  0:117   0: 'Whole Disc Boot' (legacy) not legacy
41:150  0:235   1: 'EFI' (clover) add legacy
41:395  0:245   added 'Boot Clover from EFI' OSType=3 Icon=clover
41:513  0:117   2: 'Installer' (legacy) not legacy
41:766  0:252   3: 'Whole Disc Boot' (legacy) not legacy
42:004  0:238   4: 'Whole Disc Boot' (legacy) not legacy
42:324  0:319   5: 'Whole Disc Boot' (legacy) not legacy
42:560  0:235   6: 'Whole Disc Boot' (legacy) not legacy
42:804  0:244   7: 'Whole Disc Boot' (legacy) not legacy
43:039  0:235   8: 'Bluebirds' (legacy) not legacy
43:275  0:235   9: 'EFI' (legacy) not legacy
43:520  0:244  10: 'OS X Yosemite' (legacy) not legacy
43:756  0:235  11: 'Recovery HD' (legacy) not legacy
44:000  0:244  12: 'EFI' (legacy) not legacy
44:236  0:235  13: 'Mac OS X' (legacy) not legacy
44:555  0:319  14: 'EFI' (legacy) not legacy
44:791  0:235  15: 'Data' (legacy) not legacy
45:035  0:244  16: 'Kally' (legacy) not legacy
45:280  0:244  17: 'Misc' (legacy) not legacy
45:524  0:244  18: 'EFI' (legacy) not legacy
45:760  0:235  19: 'Medien' (legacy) not legacy
46:004  0:244  20: 'EFI' (legacy) not legacy
46:240  0:235  21: 'Mac OS X 10.9.5 Backup' (legacy) not legacy
46:485  0:244  Custom tool start
46:602  0:117  Custom tool end
46:736  0:133  found tool \EFI\CLOVER\tools\Shell64U.efi
46:929  0:193  Checking EFI partition Volume 1 for Clover
47:055  0:126   Found Clover
47:174  0:118  Checking EFI partition Volume 9 for Clover
47:300  0:126  Checking EFI partition Volume 12 for Clover
47:420  0:120  Checking EFI partition Volume 14 for Clover
47:538  0:117  Checking EFI partition Volume 18 for Clover
47:656  0:117  Checking EFI partition Volume 20 for Clover
47:775  0:118  GetEfiBootDeviceFromNvram: efi-boot-device-data not found
48:011  0:235  EfiBootVolume not found
48:221  0:210  Default boot entry not found
48:339  0:117  DefaultIndex=-1 and MainMenu.EntryCount=11
48:653  0:313  GUI ready
61:056  12:403  BootOption of the entry is empty
61:183  0:126  StartLoader() start
61:300  0:117  Entry->Settings: <null string>
61:418  0:117  Finally: Bus=161905kHz CPU=3400MHz
61:536  0:117  Kernel and Kext Patches at BE8D30F0:
61:663  0:126  	Allowed: y
61:789  0:126  	Debug: y
61:907  0:117  	KernelCpu: n
62:025  0:117  	Lapic: n
62:143  0:118  	Haswell-E: n
62:336  0:193  	AICPUPM: n
62:454  0:117  	AppleRTC: y
62:572  0:118  	KernelPm: n
62:699  0:126  	FakeCPUID: 0x0
62:825  0:126  	ATIController: 7000
62:943  0:117  	ATIDataLength: 64
63:061  0:117  	0 Kexts to load
63:179  0:117  	0 Kexts to patch
63:296  0:117  Loading boot.efi  status=Success
63:844  0:547  GetOSVersion: : 10.10.4
64:097  0:252  insert table 9 for dev 0:0
64:215  0:117  insert table 9 for dev 0:1
64:333  0:117  insert table 9 for dev 0:0
64:451  0:117  insert table 9 for dev 0:0
64:645  0:194  Channels: 3
64:763  0:117  Interleave: 0 2 4 1 3 5 6 8 10 7 9 11 12 14 16 13 15 17 18 20 22 19 21 23
67:906  3:142  SMBIOS Type 17 Index = 0 => 0 0:
68:024  0:117   DIMM1 1333MHz 4096MB
68:150  0:126  mTotalSystemMemory = 4096
68:268  0:118  SMBIOS Type 17 Index = 1 => 2 2:
68:394  0:126   DIMM2 1333MHz 4096MB
68:513  0:118  mTotalSystemMemory = 8192
68:630  0:117  SMBIOS Type 17 Index = 2 => 4 4:
68:748  0:118   DIMM3 1333MHz 4096MB
68:866  0:117  mTotalSystemMemory = 12288
69:101  0:234  SMBIOS Type 17 Index = 3 => 1 1:
69:218  0:117   DIMM4 EMPTY
69:344  0:126  NumberOfMemoryDevices = 4
69:462  0:117  Type20[0]->End = 0x0, Type17[0] = 0x1000
69:588  0:125  Type20[1]->End = 0x0, Type17[1] = 0x3000
69:706  0:117  Type20[2]->End = 0x0, Type17[2] = 0x6000
69:823  0:117  RSDT 0xBF780000
69:949  0:126  FADT from RSDT: 0xBF780200
70:067  0:117  Xsdt is not found! Creating new one
70:185  0:117  RsdPointer is Acpi 1.0 - creating new one Acpi 2.0
70:311  0:125  RsdPointer Acpi 2.0 installed
70:504  0:193  RSDT entries = 7
70:621  0:117  Xsdt reallocation done
70:739  0:117  old FADT length=84
70:865  0:126  Found OperationRegion(BIOS, SystemMemory, BF798064, ...)
70:983  0:117  Found OperationRegion(RAMW, SystemMemory, BF7DC000, ...)
71:100  0:117  Found OperationRegion(PCFG, SystemMemory, 0, ...)
71:218  0:117  Found OperationRegion(PCFG, SystemMemory, 0, ...)
71:335  0:117  Found OperationRegion(PCFG, SystemMemory, 0, ...)
71:461  0:125  Found OperationRegion(PCFG, SystemMemory, 0, ...)
71:654  0:193  Found OperationRegion(PCFG, SystemMemory, 0, ...)
71:788  0:134  Found OperationRegion(PCFG, SystemMemory, 0, ...)
71:906  0:117  Found OperationRegion(PCFG, SystemMemory, 0, ...)
72:024  0:117  Found OperationRegion(TVID, SystemMemory, FED40F00, ...)
72:141  0:117  Output DSDT before patch to /EFI/CLOVER/ACPI/origin/DSDT-or.aml
72:491  0:350  Apply DsdtFixMask=0x9FC2F9D7 new way
72:617  0:125     drop _DSM mask=0x0000
72:743  0:126  ========= Auto patch DSDT Starting ========
72:954  0:210  VideoCard devID=0x68101002
73:072  0:117  DisplayADR1[0] = 0x70000, DisplayADR2[0] = 0x0
73:189  0:117  USBADR[0] = 0x1A0000 and PCIe = 0xFFFE
73:307  0:117  USBADR[1] = 0x1A0001 and PCIe = 0xFFFE
73:425  0:117  USBADR[2] = 0x1A0002 and PCIe = 0xFFFE
73:542  0:117  USBADR[3] = 0x1A0007 and PCIe = 0xFFFE
73:669  0:126  USBADR[4] = 0x1C0001 and PCIe = 0x0
73:803  0:134  USBADR[5] = 0x1D0000 and PCIe = 0xFFFE
73:921  0:117  USBADR[6] = 0x1D0001 and PCIe = 0xFFFE
74:114  0:192  USBADR[7] = 0x1D0002 and PCIe = 0xFFFE
74:231  0:117  USBADR[8] = 0x1D0007 and PCIe = 0xFFFE
74:349  0:117  first CPU found at 2B offset 2E
74:467  0:117  score candidate at 27
74:593  0:126  score inserted in acpi_cpu_score _PR_
74:710  0:117  Found ACPI CPU: P001 And P002 And P003 And P004 And P005 And P006 And P007 And P008 And P009 And P010 And P011 And P012 And P013 And P014 And P015 And P016 
  within the score: _PR_
76:753  2:042  Found PCIROOTUID = 0
76:879  0:126  Start RTC Fix
77:072  0:193  found RTC had IRQNoFlag will move -3 bytes
77:190  0:117  ...len=C396
77:307  0:117  new size written to 19D5 shift=0 len=C396
77:425  0:117  len after correct outers C396
77:551  0:126  Start PIC Fix
77:669  0:117  PIC size=2B at 1931
77:787  0:117  found PIC had IRQNoFlag will move -3 bytes
77:904  0:117  Fix Device PIC size -3
78:039  0:134  Start HPET Fix
78:157  0:118  Start Display0 Fix
78:275  0:117  add device GFX0
78:392  0:117  Creating DSM for ATI card
78:510  0:117  now inserting Video device
78:712  0:201  ... into existing bridge
78:829  0:117  patch Display #0 of Vendor=0x1002 in DSDT new way
78:947  0:117  Start NetWork Fix
79:074  0:126  have no Network device while NetworkADR2=0
79:191  0:117  NetworkADR1=1C0002 NetworkADR2=0
79:309  0:117  network DSM created, size=8A
79:427  0:118  Start SBUS Fix PCI=14F9 len=C419
79:553  0:126  SBUS absent, adding to the end of PCI0 at 6188
79:671  0:117  patch FRWR in DSDT 
79:789  0:118  Start Firewire Fix
79:907  0:117  patch HDEF in DSDT 
80:100  0:193  Start HDA Fix
80:235  0:134  Start Add Device HDEF
80:353  0:117  Start HDMI143 Fix
80:479  0:126  have no HDMI device while HDMIADR2=1
80:597  0:117  HDMIADR1=70000 HDMIADR2=1
80:714  0:117    with default properties
80:832  0:117  Start USB Fix
80:950  0:117  USB bridge[1A0000] at 34DD, size = 71
81:067  0:117  USB bridge[1A0001] at 35B6, size = 71
81:194  0:126  USB bridge[1A0002] at 368F, size = 71
81:312  0:117  USB bridge[1A0007] at 3768, size = 1F
81:513  0:201  USB bridge[1C0001] at 3879, size = 36
81:631  0:117  USB bridge[1D0000] at 32F0, size = 71
81:749  0:117  USB bridge[1D0001] at 33C9, size = 71
81:867  0:117  USB bridge[1D0002] at 34A2, size = 71
81:984  0:117  USB bridge[1D0007] at 35EE, size = 1F
82:102  0:117   deleting device CRT_
82:220  0:117   deleting device DVI_
82:355  0:134   deleting device SPKR
82:481  0:126   deleting device ECP_
82:599  0:117   deleting device LPT_
82:717  0:117   deleting device FDC0
82:835  0:117   deleting device ECP1
83:028  0:193   deleting device LPT1
83:146  0:117  NewName OCST already present, renaming impossibble
83:264  0:118  Start PNLF Fix
83:399  0:134  found PWRB at 6AEC
83:516  0:117  Start _S3D Fix
83:634  0:117  OperationRegion (BIOS...) corrected to addr=0xBF798064
83:752  0:117  OperationRegion (RAMW...) corrected to addr=0xBF7DC000
83:869  0:117  OperationRegion (PCFG...) corrected to addr=0x0
83:987  0:117  OperationRegion (PCFG...) corrected to addr=0x0
84:105  0:117  OperationRegion (PCFG...) corrected to addr=0x0
84:306  0:201  OperationRegion (PCFG...) corrected to addr=0x0
84:424  0:117  OperationRegion (PCFG...) corrected to addr=0x0
84:558  0:134  OperationRegion (PCFG...) corrected to addr=0x0
84:676  0:117  OperationRegion (PCFG...) corrected to addr=0x0
84:793  0:117  OperationRegion (TVID...) corrected to addr=0xFED40F00
84:911  0:117  Start ADP1 fix
85:029  0:117  no device(AC) exists
85:147  0:117  Start Darwin Fix
85:264  0:117  Name _OSI present at 0x4E5, renaming to OOSI
85:466  0:201  Name _OSI present at 0x4EC, renaming to OOSI
85:592  0:126  Name _OSI present at 0x504, renaming to OOSI
85:709  0:117  Name _OSI present at 0x51C, renaming to OOSI
85:827  0:117  Name _OSI present at 0x538, renaming to OOSI
85:945  0:117  Name _OSI present at 0x554, renaming to OOSI
86:063  0:117  Name _OSI present at 0x56E, renaming to OOSI
86:180  0:117  Name _OSI present at 0x58C, renaming to OOSI
86:306  0:126  Start SHUTDOWN Fix len=CB8D
86:424  0:117  ========= Auto patch DSDT Finished ========
86:866  0:441  Drop tables from Xsdt, SIGN=SSDT TableID=CpuPm Length=867
86:984  0:117   Xsdt has tables count=7 
87:110  0:126   Table: SSDT  CpuPm  867 dropped
87:228  0:117  corrected XSDT length=84
87:345  0:117  Drop tables from Xsdt, SIGN=XXXX TableID= Length=0
87:463  0:117   Xsdt has tables count=6 
87:580  0:117  corrected XSDT length=84
87:698  0:117   CPUBase=1 and ApicCPUBase=1 ApicCPUNum=16
87:824  0:125  Maximum control=0x15
87:942  0:117  P-States: min 0xC, max 0x15
88:161  0:219  SSDT with CPU P-States generated successfully
88:278  0:117  SSDT with CPU C-States generated successfully
88:396  0:117  Framebuffer @0xD0000000  MMIO @0xFBA80000	I/O Port @0x0000B000 ROM Addr @0xFBAC0000
88:514  0:117  ATI card POSTed, 
88:758  0:243  Set VRAM for Cedar=2048Mb
88:875  0:117  ATI: get_vram_size returned 0x80000000
89:001  0:126  ATI Radeon EVERGREEN family
89:127  0:126  Users config name Futomaki
89:245  0:117   use N ports setting from config.plist: 4
89:438  0:192  (AtiPorts) Nr of ports set to: 4
89:556  0:117  ATI Pitcairn AMD Radeon R9 270X 2048MB (Futomaki) [1002:6810] (subsys [148C:2336]):: PcieRoot(0x0)\Pci(0x7,0x0)\Pci(0x0,0x0)
89:673  0:117  USB Controller [8086:3A37] :: PcieRoot(0x0)\Pci(0x1A,0x0)
89:791  0:117  USB Controller [8086:3A38] :: PcieRoot(0x0)\Pci(0x1A,0x1)
89:909  0:117  USB Controller [8086:3A39] :: PcieRoot(0x0)\Pci(0x1A,0x2)
90:043  0:134  USB Controller [8086:3A3C] :: PcieRoot(0x0)\Pci(0x1A,0x7)
90:161  0:117  HDA Controller [8086:3A3E] :: PcieRoot(0x0)\Pci(0x1B,0x0) => detected codec: 10EC:0888
90:472  0:310  USB Controller [1912:0014] :: PcieRoot(0x0)\Pci(0x1C,0x1)\Pci(0x0,0x0)
90:590  0:117  USB Controller [8086:3A34] :: PcieRoot(0x0)\Pci(0x1D,0x0)
90:707  0:117  USB Controller [8086:3A35] :: PcieRoot(0x0)\Pci(0x1D,0x1)
90:825  0:117  USB Controller [8086:3A36] :: PcieRoot(0x0)\Pci(0x1D,0x2)
90:960  0:134  USB Controller [8086:3A3A] :: PcieRoot(0x0)\Pci(0x1D,0x7)
91:078  0:117  stringlength = 7448
91:280  0:201  CurrentMode: Width=1280 Height=1024
91:397  0:117  Beginning FSInjection
91:530  0:132  Preparing kexts injection for arch=x86_64 from EFI\CLOVER\kexts\Other
91:648  0:117  Preparing kexts injection for arch=x86_64 from EFI\CLOVER\kexts\10.10
91:765  0:117    Extra kext: EFI\CLOVER\kexts\10.10\FakeSMC.kext
91:938  0:172  SetStartupDiskVolume:
92:041  0:103    * Volume: 'OS X Yosemite'
92:159  0:117    * LoaderPath: '<null string>'
92:285  0:125    * DevPath: OS X Yosemite
92:402  0:117    * GUID = 02F83038-3F89-4D5F-A030-71E74BA66F67
92:595  0:193    * efi-boot-device: <array><dict><key>IOMatch</key><dict><key>IOProviderClass</key><string>IOMedia</string><key>IOPropertyMatch</key><dict><key>UUID</key><string>02F83038-3F89-4D5F-A030-71E74BA66F67</string></dict></dict></dict></array>
92:713  0:117  Custom boot screen not used because entry has unset use graphics
92:839  0:126  Closing log

[=)(=]

I found a HFSPlus driver here: http://efi.akeo.ie/

 

Is it based on VboxHFS or is it different and can be used for Clover instead of Apple's HFS driver?

[Slice]

I found a HFSPlus driver here: http://efi.akeo.ie/

 

Is it based on VboxHFS or is it different and can be used for Clover instead of Apple's HFS driver?

I don't know what is the driver at your link. 

You may use any driver you found just to check if it works.

One of them VboxHFS.efi provided with Clover works good enough.

[Multisaft]

I'm getting mad around here. I've restarted my FB patching, following Vladas Instructions most closely and still, verbose tells me that the FB is patched successful, but still black screen after boot up. 

 

what other issues are related to this black screen problem?

[FranticJohny]

@Slice

 

Is this work in progress or ready for test? http://sourceforge.net/p/cloverefiboot/code/3326/

 

How can I set DisableFunctions? 

[Slice]

@Slice

 

Is this work in progress or ready for test? http://sourceforge.net/p/cloverefiboot/code/3326/

 

How can I set DisableFunctions? 

It is for good testers.

0xA000

will disable EHCI 1 and 2

[Andres ZeroCross]

It is for good testers.

<string>0xA000</string>

will disable EHCI 1 and 2

Sorry,, i don't understand. Can you give me more detail about this update log and why i need this this feature?

[cecekpawon]

Slice, instead of renaming filename in KextsToPatch / DSDT Patches to disable some patches, maybe we can implement "Disabled" key for each patch like below? I dont know if it could reduce boot time

 

From:

<key>KextsToPatch</key>
<array>
  <dict>
    <key>Comment</key>
    <string>ZZZ</string>
    <key>Find</key>
    <data>
    XXX
    </data>
    <key>Name</key>
    <string>$$$AppleHDA</string>
    <key>Replace</key>
    <data>
    YYY
    </data>
  </dict>
</array>

To:

<key>KextsToPatch</key>
<array>
  <dict>
    <key>Comment</key>
    <string>ZZZ</string>
    <key>Find</key>
    <data>
    XXX
    </data>
    <key>Name</key>
    <string>AppleHDA</string>
    <key>Replace</key>
    <data>
    YYY
    </data>
    <key>Disabled</key>
    <true/>
  </dict>
</array>

--- /Users/yod/Desktop/Settings.c 2015-12-02 23:23:09.000000000
+++ /Users/yod/Downloads/Settings.c 2015-12-02 23:15:57.000000000
@@ -897,17 +897,10 @@
            DBG (" %a (%a)", Patches->KextPatches[Patches->NrKexts].Name, Dict->string);
         } else {
       DBG (" %a", Patches->KextPatches[Patches->NrKexts].Name);
}
// check disabled patch
Dict = GetProperty (Prop2, "Disabled");
if ((Dict != NULL) && IsPropertyTrue (Dict)) {
  DBG("patch disabled, skipped\n");
  continue;
    -
-
-
- -}
      // check if this is Info.plist patch or kext binary patch
Dict = GetProperty (Prop2, "InfoPlistPatch");
Patches->KextPatches[Patches->NrKexts].IsPlistPatch = IsPropertyTrue (Dict);
if (Patches->KextPatches[Patches->NrKexts].IsPlistPatch) {

[Slice]

 

Slice, instead of renaming filename in KextsToPatch / DSDT Patches to disable some patches, maybe we can implement "Disabled" key for each patch like below? I dont know if it could reduce boot time

 

From:

<key>KextsToPatch</key>
<array>
  <dict>
    <key>Comment</key>
    <string>ZZZ</string>
    <key>Find</key>
    <data>
    XXX
    </data>
    <key>Name</key>
    <string>$$$AppleHDA</string>
    <key>Replace</key>
    <data>
    YYY
    </data>
  </dict>
</array>

To:

<key>KextsToPatch</key>
<array>
  <dict>
    <key>Comment</key>
    <string>ZZZ</string>
    <key>Find</key>
    <data>
    XXX
    </data>
    <key>Name</key>
    <string>AppleHDA</string>
    <key>Replace</key>
    <data>
    YYY
    </data>
    <key>Disabled</key>
    <true/>
  </dict>
</array>

--- /Users/yod/Desktop/Settings.c 2015-12-02 23:23:09.000000000
+++ /Users/yod/Downloads/Settings.c 2015-12-02 23:15:57.000000000
@@ -897,17 +897,10 @@
            DBG (" %a (%a)", Patches->KextPatches[Patches->NrKexts].Name, Dict->string);
         } else {
       DBG (" %a", Patches->KextPatches[Patches->NrKexts].Name);
}
// check disabled patch
Dict = GetProperty (Prop2, "Disabled");
if ((Dict != NULL) && IsPropertyTrue (Dict)) {
  DBG("patch disabled, skipped\n");
  continue;
    -
-
-
- -}
      // check if this is Info.plist patch or kext binary patch
Dict = GetProperty (Prop2, "InfoPlistPatch");
Patches->KextPatches[Patches->NrKexts].IsPlistPatch = IsPropertyTrue (Dict);
if (Patches->KextPatches[Patches->NrKexts].IsPlistPatch) {

Why you disable patches written into config.plist? 

Create a copy like config-1.plist.

Delete unused patches from config.plist

If anytime it will be needed revert files.

OK, committed to 3327.

And 3328 for DSDT binary patches.