Clover General discussion

[toleda]

Because in your config

 

This is a question. Why "onboard-2" if there must be "onboard-1"? What is the rule?

As I see iMac12,2 uses onboard-1.

 

Only CpuPm set to drop

1:620  0:008  Dropping 3 tables
1:635  0:015  Drop table 0 signature="SSDT" (54445353) table-id="SaSsdt" (0000746473536153)
1:769  0:134  set table: 54445353,         73536153 to drop:
1:786  0:016  Drop table 1 signature="SSDT" (54445353) table-id="CpuPm" (0000006D50757043)
1:912  0:126  set table: 54445353,         50757043 to drop:  true
1:929  0:016  
1:937  0:008  Drop table 2 signature="SSDT" (54445353) table-id="Cpu01st" (0074733130757043)
2:135  0:197  set table: 54445353,         30757043 to drop:

Forgot.

 

No rule. In practice, integrated graphics is onboard-1 and discrete graphics is onboard-2. Supports integrated only, discrete only and both for HDMI audio.  iMac12,2 does not connect integrated graphics to the display, QuickSync only.

1. HD3000/HD4000 (HDEF@1B) and HD4600 (HDAU@3) use onboard-1 with IGPU@2 (GFX0@2)

2. AMD/Nvidia use onboard-2 with GFX0@0 and HDAU@0,1.

 

For onboard-2, config.plist/Devices/AddProperties (2570 Folder)

	<key>Devices</key>
	<dict>
		<key>AddProperties</key>
		<array>
			<dict>
				<key>Device</key>
				<string>ATI</string>
				<key>Key</key>
				<string>hda-gfx</string>
				<key>Value</key>
				<string>onboard-2</string>
			</dict>
	</dict>

config.plist/ACPI/DropTables (2570-1 Folder)

<key>ACPI</key>
	<dict>
		<key>DropTables</key>
		<array>
			<dict>
				<key>Signature</key>
				<string>SSDT</string>
				<key>TableId</key>
				<string>SaSsdt</string>
			</dict>
			<dict>
				<key>Signature</key>
				<string>SSDT</string>
				<key>TableId</key>
				<string>CpuPm</string>
			</dict>
			<dict>
				<key>Signature</key>
				<string>SSDT</string>
				<key>TableId</key>
				<string>Cpu01st</string>
			</dict>
		</array>
	</dict>

Why is only CpuPm set to true with the above property injection?

[blackosx]

...This is where the problem starts, all I get at boot is boot0af: error.

../snip/..

Also, does it matter that my new disk is a seagate hybrid sshd?

 

Hi ZenGiga

 

Does your new drive use 4K sectors?

[ZenGiga]

Hi ZenGiga

 

Does your new drive use 4K sectors?

 

Yes, it's a Seagate ST1000DX001 - 4096 Bytes per sector (4K physical emulated at 512-byte sectors) as the manual says.

 

I noted posts suggesting that boot1 needs manually copied into place specifying 4k sector size so I tried that already (made no difference):

 

 

sudo -s
dd if=/dev/rdisk0s1 count=1 bs=4096 of=/tmp/origbs

- gives result:
1+0 records in
1+0 records out
4096 bytes transferred in 0.000695 secs (5893609 bytes/sec)

cp /Volumes/osten/usr/standalone/i386/boot1f32 /tmp/newbs
dd if=/tmp/origbs of=/tmp/newbs skip=3 seek=3 bs=1 count=87 conv=notrunc

- gives result
87+0 records in
87+0 records out
87 bytes transferred in 0.000351 secs (247897 bytes/sec)

dd if=/tmp/newbs of=/dev/rdisk1s1
- give result
1+0 records in
1+0 records out
512 bytes transferred in 0.000276 secs (1856079 bytes/sec)

 

 

That last line of 512 bytes transferred in seemed odd since we started copying out 4096 so I repeated it specifying 4096:

 

dd if=/tmp/newbs of=/dev/rdisk1s1 count=1 bs=4096

But the result still said '512 bytes transferred'!

 

Maybe I've done something wrong there, but 'man dd' doesn't suggest anything to me.

 

 

Here's the clover install log fwiw:

 

Clover EFI installer log - Wed Feb 5 11:48:58 GMT 2014

Installer version: v2k r2563 EFI bootloader

======================================================

/dev/disk0

#: TYPE NAME SIZE IDENTIFIER

0: GUID_partition_scheme *1.0 TB disk0

1: EFI EFI 209.7 MB disk0s1

2: Apple_HFS osten - old 797.7 GB disk0s2

3: Apple_Boot Recovery HD 650.0 MB disk0s3

4: Apple_HFS boxes - old 201.5 GB disk0s4

/dev/disk1

#: TYPE NAME SIZE IDENTIFIER

0: GUID_partition_scheme *1.0 TB disk1

1: EFI EFI 209.7 MB disk1s1

2: Apple_HFS osten 799.6 GB disk1s2

3: Apple_Boot Recovery HD 650.0 MB disk1s3

4: Apple_HFS boxes 199.6 GB disk1s4

/dev/disk2

#: TYPE NAME SIZE IDENTIFIER

0: GUID_partition_scheme *500.1 GB disk2

1: EFI EFI 209.7 MB disk2s1

2: Bios Boot Partition 1.1 GB disk2s2

3: Apple_HFS vmdisks 382.5 GB disk2s3

4: Apple_Boot Recovery HD 650.0 MB disk2s4

5: Microsoft Basic Data 100.0 GB disk2s5

6: Linux Swap 15.3 GB disk2s6

/dev/disk3

#: TYPE NAME SIZE IDENTIFIER

0: FDisk_partition_scheme *164.7 GB disk3

1: Windows_NTFS 82.3 GB disk3s1

2: Windows_FAT_32 82.3 GB disk3s2

======================================================

Backing up EFI files

 

Backing up stage2 file /Volumes/osten/EFIROOTDIR/boot to /Volumes/osten/EFI-Backups/r2547/2014-02-05-11h48/boot

Backing up /Volumes/osten/EFIROOTDIR/EFI folder to /Volumes/osten/EFI-Backups/r2547/2014-02-05-11h48/EFI

======================================================

Installing BootSectors/BootLoader

 

No Active Partition

 

Stage 0 - Writting boot0af to /dev/disk1

/usr/local/bin/fdisk440 -u -f /Volumes/osten/usr/standalone/i386/boot0af -y /dev/disk1

 

Stage 1 - Writting boot1f32 to /dev/rdisk1s1

File system is Fat32.

dd if=/dev/rdisk1s1 count=1 bs=512 of=/tmp/origbs

cp /Volumes/osten/usr/standalone/i386/boot1f32 /tmp/newbs

dd if=/tmp/origbs of=/tmp/newbs skip=3 seek=3 bs=1 count=87 conv=notrunc

dd if=/tmp/newbs of=/dev/rdisk1s1

 

Stage 2 - Written boot6 (x64) to /Volumes/ESP/boot

======================================================

Installing RC Scripts

 

Installing RC scripts in '/' volume

Installing RC scripts in '/Volumes/osten - old' volume

Installing RC scripts on target volume '/Volumes/osten'

 

Activating /etc/rc.boot.d/70.disable_sleep_proxy_client.local rc script

Activating /Volumes/osten - old/etc/rc.boot.d/70.disable_sleep_proxy_client.local rc script

Activating /Volumes/osten/etc/rc.boot.d/70.disable_sleep_proxy_client.local rc script

 

======================================================

=========== Clover EFI Installation Finish ===========

======================================================

 

[blackosx]

I think I remember reading you need to make sure the disk is unmounted from OS X before writing and/or use a different (linux?) dd binary as OS X's version doesn't work. That's all I can think of as I've never had a 4K sector drive so not had to try it. Hope it gives you something to go on.

 

EDIT: Here's a link

http://forge.voodooprojects.org/p/chameleon/issues/129/

[Slice]

Forgot.

 

No rule. In practice, integrated graphics is onboard-1 and discrete graphics is onboard-2. Supports integrated only, discrete only and both for HDMI audio.  iMac12,2 does not connect integrated graphics to the display, QuickSync only.

1. HD3000/HD4000 (HDEF@1B) and HD4600 (HDAU@3) use onboard-1 with IGPU@2 (GFX0@2)

2. AMD/Nvidia use onboard-2 with GFX0@0 and HDAU@0,1.

Sure?

 

    | |   |   | |   "ATY,TileInfo" = <010000000000000000000000000000000500000000000000>
    | |   |   | |   "ATY,Rom#" = <"113-C0170F-175">
    | |   |   | |   "hda-gfx" = <"onboard-1">
    | |   |   | |   "AAPL00,blackscreen-preferences" = <00000008>
    | |   |   | |   "pci-bus-number" = 1
    | |   |   | |   "ATY,vram_base" = <00000000>
    | |   |   | |   "IOInterruptSpecifiers" = (<1000000007000000>,<0200000000000100>)
    | |   |   | |   "PP_R600RaisingLowPercentage" = 10
    | |   |   | |   "PP_R600LoweringMediumPercentage" = 10
    | |   |   | |   "ATY,EFIHWInitStatus" = <0000000000000000>
    | |   |   | |   "revision-id" = <00000000>
    | |   |   | |   "ATY,VendorID" = <0210>
    | |   |   | |   "device_type" = <"ATY,HydrillaParent">

Why is only CpuPm set to true with the above property injection?

This is that I didn't understand. Must work.

 

This is my own test

1:711  0:000  Dropping 4 tables
1:711  0:000  Drop table 0 signature="DMAR" (52414D44)
1:711  0:000  set table: 52414D44,                0 to drop:
1:711  0:000  Drop table 1 signature="BGRT" (54524742)
1:711  0:000  set table: 54524742,                0 to drop:
1:711  0:000  Drop table 2 signature="SSDT" (54445353) table-id="CpuPm" (0000006D50757043)
1:711  0:000  set table: 54445353,         50757043 to drop:  true
1:711  0:000  
1:711  0:000  Drop table 3 signature="SSDT" (54445353) table-id="Cpu0Ist" (0074734930757043)
1:711  0:000  set table: 54445353,         30757043 to drop:  true
1:711  0:000  

Compare hex for Cpu0Ist

my 0074734930757043

your 0074733130757043

[toleda]

Please test my version

2574 results:

dsdt fixes/old_way/AddDTGP, FixDisplay, FixHDA - not working

dsdt fixes/new_way/NewWay, Fix_INTELGFX, AddHDMI - not working - ATI/dsdt/HDAU, no HDAU in IOReg

    Fix_INTELGFX/PEG0@2 has an error, suggest IGPU@2 for native PM.

dsdt fixes/new_way+addprops/NewWay, AddHDMI, add HDAU and B0D3 - not working - HDA and B0D3 in IOReg, hda-gfx missing

 

One hda-gfx injection shows in edited dsdt should be 4 with my system.

Please clarify the correct dsdt fixes for integrated graphics and discrete graphics.

2574-old_way.zip

2574-new_way.zip

2574-new_way+addprops.zip

[FranticJohny]

This is how I understand hdmi sound edits:

 

In order to have HDMI sound we have to logically bind an audio device and a graphics card. 

 

1 case: If we have onboard graphics, the connection is hda-gfx, onboard-1 for iGPU and hda-gfx, onboard-1 for HDEF.

 

2. case: If we have only dedicated graphics, we must have a HDAU device with hda-gfx, onboard-1 and GFX device with hda-gfx, onboard-1.

 

3. case: If we have both onboard graphics and dedicated graphics, we must have  hda-gfx, onboard-1 for iGPU and hda-gfx, onboard-1 for HDEF and additionally a HDAU device with hda-gfx, onboard-2 and GFX device with hda-gfx, onboard-2.

[naiclub]

2574 results:

dsdt fixes/old_way/AddDTGP, FixDisplay, FixHDA - not working

dsdt fixes/new_way/NewWay, Fix_INTELGFX, AddHDMI - not working - ATI/dsdt/HDAU, no HDAU in IOReg

    Fix_INTELGFX/PEG0@2 has an error, suggest IGPU@2 for native PM.

dsdt fixes/new_way+addprops/NewWay, AddHDMI, add HDAU and B0D3 - not working - HDA and B0D3 in IOReg, hda-gfx missing

 

One hda-gfx injection shows in edited dsdt should be 4 with my system.

Please clarify the correct dsdt fixes for integrated graphics and discrete graphics.

DSDT.aml.zip

Hello toleda 

Try this for me 

SSDT.aml remove patches on patches might. 

I'm sorry that I do not know Just leave me

 

[toleda]

Try this for me 

Not correct.  The dsdt edits are different from the ssdts.  

See toleda/audio_hdmi_8series.

Use DSDT - Haswell HDMI Audio (with dsdt edits).

Download [Guide]-Haswell-hdmi_audio_(dsdt_or_ssdt)_v1.2.pdf.  

To add MaciASL/8series repo, see MaciASL Repo "general"

 

Apply two MaciASL/8series patches (Patch/Apply/Close/Compile):

1. 8series-Clean Compile

2. Desktop-HD5K/AMD/Nvidia-A1

 

Reply with edited dsdt.

3. case: If we have both onboard graphics and dedicated graphics, we must have  hda-gfx, onboard-1 for iGPU and hda-gfx, onboard-1 for HDEF and additionally a HDAU device with hda-gfx, onboard-2 and GFX device with hda-gfx, onboard-2.

Case 3. addresses all 3 scenarios.

[FranticJohny]

 

Case 3. addresses all 3 scenarios.

 

Well I wanted to make clear: If we use only dedicated graphics (case 2), we do not use onboard-2 for HDAU and GFX, we use onboard-1. And in this case we don't need any gfx-hda in HDEF.

[toleda]

Well I wanted to make clear: If we use only dedicated graphics (case 2), we do not use onboard-2 for HDAU and GFX, we use onboard-1. And in this case we don't need any gfx-hda in HDEF.

It only matters to the user trying to figure out what to do.  I favor simple, clear and easy; the system does not care. No need to inject onboard-1 if you don't need it, as well, onboard-1 does not need to be present to use onboard-2. Back to your original question, are three different answers better than one?

[naiclub]

Not correct.  The dsdt edits are different from the ssdts.  

See toleda/audio_hdmi_8series.

Use DSDT - Haswell HDMI Audio (with dsdt edits).

Download [Guide]-Haswell-hdmi_audio_(dsdt_or_ssdt)_v1.2.pdf.  

To add MaciASL/8series repo, see MaciASL Repo "general"

 

Apply two MaciASL/8series patches (Patch/Apply/Close/Compile):

1. 8series-Clean Compile

2. Desktop-HD5K/AMD/Nvidia-A1

 

Reply with edited dsdt.

 

I prefer this method

I have tried to come up with a SSDT.aml of your way. 

I have a feeling that it lacks something essential. Such as wifi and it's not different. 

I need patches sound. https://github.com/toleda/audio_hdmi_8series is no different to doing 

But I thank you as well Gurus to educate people on this.

[toleda]

Such as wifi and it's not different.

I need patches sound. 

Reply with edted dsdt and ioreg.

For WiFi, toleda/airport_pcie-hm

Regarding patching, Azul patching, same for AppleHDA, etc.  You know method 1 and 2. try 3 (Post #3818).

 

3 way to patch: AppleIntelFramebufferAzul.kext

 

1. HexEdit/Open/System/Library/Extensions/AppleIntelFramebufferAzul.kext/Contents/Mac OS/AppleIntelFramebufferAzul

Find: 03 06 08 00 00 04 00 00 11 00 00 00

Replace: 03 06 08 00 00 08 00 00 06 00 00 00

 

2. Terminal/audio_hdmi_hd5k-azul-90_patch.command

sudo perl -pi -e 's|x03\x06\x08\x00\x00\x04\x00\x00\x11\x00\x00\x00|x03\x06\x08\x00\x00\x08\x00\x00\x06\x00\x00\x00\|g' /System/Library/Extensions/AppleIntelFramebufferAzul.kext/Contents/MacOS/AppleIntelFramebufferAzul

 

3. Clover/config.pilst/KextsToPatch (Clover Configurator or .plist)

Find: <03060800 00040000 11000000>  or <data>AwYQAAAEAAARAAAA</data>

Name: AppleIntelFramebufferAzul

Replace: <03060800 00080000 06000000> or <data>AwYQAAAIAAAGAAAA</data>

 

The result is the same. The difference is Clover patches cache rather than the kext; kext remains native.

[toleda]

Compare hex for Cpu0Ist

my 0074734930757043

your 0074733130757043

Why is Clover calculating my Cpu01st hex wrong?

 

2574 with DropOEM no and yes.

2574
DropOEM=NO

1:602  0:008  Dropping 3 tables
1:611  0:008  Drop table 0 signature="SSDT" (54445353) table-id="SaSsdt" (0000746473536153)
1:748  0:137  set table: 54445353,     746473536153 to drop:
1:772  0:024  Drop table 1 signature="SSDT" (54445353) table-id="CpuPm" (0000006D50757043)
1:901  0:128  set table: 54445353,       6D50757043 to drop:  true
1:919  0:017  
1:927  0:008  Drop table 2 signature="SSDT" (54445353) table-id="Cpu01st" (0074733130757043)
2:074  0:146  set table: 54445353,   74733130757043 to drop:

9:916  0:008  Attempting to drop "SSDT" (54445353) "   CpuPm" (0000006D50757043) L=2776
9:931  0:015  Drop tables from Xsdt, SIGN=SSDT TableID=CpuPm Length=2776
9:940  0:008   Xsdt has tables count=9 
9:949  0:009   Table: SSDT  CpuPm  2776 dropped
9:958  0:008  corrected XSDT length=100
9:966  0:008  Patch table: SSDT  Cpu0Ist
9:975  0:008   SSDT len = 0x539
9:983  0:008  Patch table: SSDT  SataTabl
9:992  0:008   SSDT len = 0x36D
10:001  0:008  Patch table: SSDT  SaSsdt 
10:009  0:008   SSDT len = 0x329E
10:018  0:008  Drop tables from Xsdt, SIGN=XXXX TableID= Length=0
10:027  0:008   Xsdt has tables count=8 
10:042  0:015  corrected XSDT length=100


DropOEM=YES

1:602  0:008  Dropping 3 tables
1:611  0:008  Drop table 0 signature="SSDT" (54445353) table-id="SaSsdt" (0000746473536153)
1:748  0:137  set table: 54445353,     746473536153 to drop:
1:772  0:024  Drop table 1 signature="SSDT" (54445353) table-id="CpuPm" (0000006D50757043)
1:901  0:128  set table: 54445353,       6D50757043 to drop:  true
1:919  0:017  
1:927  0:008  Drop table 2 signature="SSDT" (54445353) table-id="Cpu01st" (0074733130757043)
2:074  0:146  set table: 54445353,   74733130757043 to drop:

9:685  0:008  Attempting to drop "SSDT" (54445353) "   CpuPm" (0000006D50757043) L=2776
9:694  0:008  Drop tables from Xsdt, SIGN=SSDT TableID=CpuPm Length=2776
10:582  0:887   Xsdt has tables count=9 
10:590  0:008   Table: SSDT  CpuPm  2776 dropped
10:599  0:008  corrected XSDT length=100
10:607  0:008  Drop tables from Xsdt, SIGN=SSDT TableID= Length=0
10:616  0:008   Xsdt has tables count=8 
10:625  0:008   Table: SSDT  Cpu0Ist  1337 dropped
10:633  0:008   Table: SSDT  SataTabl  877 dropped
10:642  0:008   Table: SSDT  SaSsdt   12958 dropped
10:650  0:008  corrected XSDT length=76

2574-4.zip

[blackosx]

 

Why is Clover calculating my Cpu01st hex wrong?

Hi toleda

 

Looking at your 2570-1.zip from post #3829 I see under the DropTables part of your config.plist you have the TableId set to Cpu01st where it needs to be Cpu0Ist (letter I and not number 1). 

[alexanderq]

Has anyone hdmi sound  with latest clover and no custom dsdt or am i doing something wrong?

[toleda]

you have the TableId set to Cpu01st where it needs to be Cpu0Ist (letter I and not number 1). 

blackosx, that was the problem for Cpu0Ist; thanks.

SaSsdt is now solved as well, space after the name.

DefinitionBlock ("iASLydKEAz.aml", "SSDT", 1, "SaSsdt", "SaSsdt ", 0x00003000)

19:099  0:008  Attempting to drop "SSDT" (54445353) " SaSsdt " (0020746473536153) L=12958
19:108  0:008  Drop tables from Xsdt, SIGN=SSDT TableID=SaSsdt  Length=12958
19:117  0:008   Xsdt has tables count=9 
19:125  0:008   Table: SSDT  SaSsdt   12958 dropped
19:134  0:008  corrected XSDT length=100
19:143  0:008  Attempting to drop "SSDT" (54445353) "   CpuPm" (0000006D50757043) L=2776
19:151  0:008  Drop tables from Xsdt, SIGN=SSDT TableID=CpuPm Length=2776
19:167  0:015   Xsdt has tables count=8 
19:175  0:008   Table: SSDT  CpuPm  2776 dropped
19:184  0:008  corrected XSDT length=92
19:193  0:008  Attempting to drop "SSDT" (54445353) " Cpu0Ist" (0074734930757043) L=1337
19:201  0:008  Drop tables from Xsdt, SIGN=SSDT TableID=Cpu0Ist Length=1337
19:210  0:008   Xsdt has tables count=7 
19:219  0:008   Table: SSDT  Cpu0Ist  1337 dropped
19:227  0:008  corrected XSDT length=84
19:236  0:008  Patch table: SSDT  SataTabl
19:245  0:008   SSDT len = 0x36D
19:260  0:015  Drop tables from Xsdt, SIGN=XXXX TableID= Length=0
19:269  0:008   Xsdt has tables count=6 
19:278  0:008  corrected XSDT length=84
19:286  0:008  Inserting SSDT.aml from EFI\CLOVER\ACPI\patched ... Success
19:307  0:020  Inserting SSDT-1.aml from EFI\CLOVER\ACPI\patched ... Success
19:327  0:020  Inserting SSDT-2.aml from EFI\CLOVER\ACPI\patched ... Success

[ZenGiga]

I think I remember reading you need to make sure the disk is unmounted from OS X before writing and/or use a different (linux?) dd binary as OS X's version doesn't work. That's all I can think of as I've never had a 4K sector drive so not had to try it. Hope it gives you something to go on.

 

EDIT: Here's a link

http://forge.voodooprojects.org/p/chameleon/issues/129/

 

Positive progress, just managed two successful boots. So the actual commands on that thread are out of date, and apply to chameleon in a normal HFS+ partition not EFI, using them on EFI leeds to corrupt EFI partition, no surprise really.

 

I just erased the hybrid disk again, and partitioned with gparted (parted magic version) - which leaves the EFI partition as fat32 and isn't recognised as a proper OSX EFI partition but still works.

Then did a full linux manual install of boot0af and boot1f32 as per clover wiki installation section.

Finally, restored my working EFI partition to the new one with disk utility (to copy over the other clover files, fakesmc and my config.plist).

 

And it works at last.

 

About to try one last thing, and repartition the disk with Disk Utility before doing a another linux manual install of boot0/1, should work I think.

[Slice]

 

Roger that.

It seems that this is the only way at right now.

Hope it will fix soon,thanks for reply.  

 

 

I hope I corrected this in my binary 2577 (not tested yet). And waiting for edk2 development team to correct in repository.

[ZenGiga]

About to try one last thing, and repartition the disk with Disk Utility before doing a another linux manual install of boot0/1, should work I think.

 

Success with disk utility format and partition, followed by linux manual install of boot0af and boot1f32. No need to specify bs=4096, presumably because the drive firmware is emulating 512b sectors anyway.

To summarize for anyone else that has a boot0af: error after running clover installer on a Seagate hybrid SSHD serial ST1000DX001 aiming for legacy bios boot.

First partitioned the disk with disk utility so there was at least the osx efi partition and an hfs+ partition to install OSX into.

Second I ran the clover installer and pointed it towards that new hfs+ partition on the hybrid.

Third, with clover having previously installed on another non-hybrid disk linux sees as /dev/sdb3, I was able to do the following in parted magic (1):

Linux is seeing the hybrid disk as /dev/sda in my case, and the efi partition on that as /dev/sda1

dd if=/dev/sda count=1 bs=512 of=origMBR
cp origMBR newMBR
dd if=/media/sdb3/usr/standalone/i386/boot0af of=newMBR bs=1 count=440 conv=notrunc
dd if=newMBR of=/dev/sda count=1 bs=512

dd if=/dev/sda1 count=1 bs=512 of=origbs
cp /media/sdb3/usr/standalone/i386/boot1f32 newbs
dd if=origbs of=newbs skip=3 seek=3 bs=1 count=87 conv=notrunc
dd if=newbs of=/dev/sda1 count=1 bs=512

To install boot0af and boot1f32 respectively.

 

(1) you could also extract the boot0 and boot1 files you need and put them on a usb, anything you can read from parted magic once you're booted into that.

 

BUT I'm not sure its worth the effort for me. I presume that now every time I want to upgrade Clover with the installer it will screw up the PBR and I'll have to manually upgrade with linux?

Might be more sensible for me to just use the non-hybrid disk for boot with clover and shift the grub2 boot partition currently on there onto the hybrid instead...or at least less hassle.

 

EDIT Spoke too soon! The hybrid drive is now not even responding to bios, completely invisible. Sigh. Giving up trying to boot osx from it, thats for sure.

Edit2 And came back after a full power off and on. It seems the hybrid drive will sometimes fail to restart properly if you need to do a hardware reset. No harm, just not terribly reliable as a technology I think.

[naiclub]

Reply with edted dsdt and ioreg.

For WiFi, toleda/airport_pcie-hm

Regarding patching, Azul patching, same for AppleHDA, etc.  You know method 1 and 2. try 3 (Post #3818).

 

3 way to patch: AppleIntelFramebufferAzul.kext

 

1. HexEdit/Open/System/Library/Extensions/AppleIntelFramebufferAzul.kext/Contents/Mac OS/AppleIntelFramebufferAzul

Find: 03 06 08 00 00 04 00 00 11 00 00 00

Replace: 03 06 08 00 00 08 00 00 06 00 00 00

 

2. Terminal/audio_hdmi_hd5k-azul-90_patch.command

sudo perl -pi -e 's|x03\x06\x08\x00\x00\x04\x00\x00\x11\x00\x00\x00|x03\x06\x08\x00\x00\x08\x00\x00\x06\x00\x00\x00\|g' /System/Library/Extensions/AppleIntelFramebufferAzul.kext/Contents/MacOS/AppleIntelFramebufferAzul

 

3. Clover/config.pilst/KextsToPatch (Clover Configurator or .plist)

Find: <03060800 00040000 11000000>  or <data>AwYQAAAEAAARAAAA</data>

Name: AppleIntelFramebufferAzul

Replace: <03060800 00080000 06000000> or <data>AwYQAAAIAAAGAAAA</data>

 

The result is the same. The difference is Clover patches cache rather than the kext; kext remains native.

Hello toleda 

I wanted to do method 3. 

But what I do not get results, it is recommended that you do it or not.

 

** We are not going to deal with the 1 and 2. 

We give Clover a target on our behalf. 

This is what I want.

[toleda]

But what I do not get results, 

No idea what you did; attach config.plist, debug.log and ioreg.

[blackosx]

Positive progress, just managed two successful boots. 

Great. Well done

 

So the actual commands on that thread are out of date, and apply to chameleon in a normal HFS+ partition not EFI, using them on EFI leeds to corrupt EFI partition, no surprise really.

Yeah. That link was just food for thought.

 

I just erased the hybrid disk again, and partitioned with gparted (parted magic version) - which leaves the EFI partition as fat32 and isn't recognised as a proper OSX EFI partition but still works.

I don’t think you need to do that as by default an Apple ESP (EFI system partition) created by Disk Utility, while not exactly a FAT32 format can be treated as so without any further formatting.

 

Then did a full linux manual install of boot0af and boot1f32 as per clover wiki installation section.

Boot0 can be written as normal from OS X terminal using fdisk440.

 

The issue with 4K sector drives is only for boot1 and looking at Cosmosis Jones’ comment #71 in the voodooprojects issue 129 that I pointed to previously, it looks like you don’t need to use linux and can issue the command to /dev/diskXsY and not /dev/rdiskXsY from OS X Terminal. For this to happen you will need the target drive unomunted first, so either boot in to an OS X system on a separate drive or your recovery partition if you have one, select Disk Utility and unmount the drive.

 

So for the manual install procedure of boot1f32, or boot1f32alt if preferred, as shown in the Clover wiki, the revised commands would be something like:

dd if=/dev/rdiskXsY count=1 bs=512 of=origbs
cp boot1f32alt newbs
dd if=origbs of=newbs skip=3 seek=3 bs=1 count=87 conv=notrunc
dd if=newbs of=/dev/diskXsY count=1 bs=512

Which I think I'm right in saying translates as:

line 1 - make working copy of the existing 512bytes of the first sector

line 2 - copy boot1f32alt to a file named newbs

line 3 - write original bytes 3-90 (From the OEM ID to the end of the extended BIOS parameter block, before the executable boot code) of original sector to the new sector file, leaving the remainder as it was.

line 4 - write the complete new sector file to the drive.

 

BUT I'm not sure its worth the effort for me. I presume that now every time I want to upgrade Clover with the installer it will screw up the PBR and I'll have to manually upgrade with linux?

No. The installer has an option to not update the MBR/PBR sectors.

 

Having said all that, I don't have a 4K sector drive and have not tried the above so I can't guarantee it will work.

[Maniac10]

Slice, could you explain what "AddHDMI_8000000" does? I'm guessing it adds HDAU and GFX0 with hda-gfx and some other properties but don't know for sure.

[Slice]

Slice, could you explain what "AddHDMI_8000000" does? I'm guessing it adds HDAU and GFX0 with hda-gfx and some other properties but don't know for sure.

It adds HDAU device if absent with some default properties. You may customize these properties at your will

	<key>Devices</key>
	<dict>
		<key>AddProperties</key>
		<array>
			<dict>
				<key>Device</key>
				<string>HDMI</string>
				<key>Key</key>
				<string>Sample</string>
				<key>Value</key>
				<data>AQAAAA==</data>
			</dict>