Clover General discussion

esmith1977 · January 11, 2013

I have a 975xBX2 motherboard...

I have it booting into ML from the USB stick...

ML works fine when booting from the USB stick...

I installed it to the HD OS X partition, but when I reboot all I get is a flashing curser...

Can someone give me step-by-step instructions on how to install Clover Bootloader to my HD.

I understand that it should be installed to the EFI partition... but should I reformat that partition...

What exactly do I need to do?

primalair · January 11, 2013

I try to figure out how to boot with both, my HD4000 and my GTX670 active. Has anybody this configuration running with Clover? My config is very basic:

<?xml version="1.0" encoding="UTF-8"?>
<!DOCTYPE plist PUBLIC "-//Apple//DTD PLIST 1.0//EN" "http://www.apple.com/DTDs/PropertyList-1.0.dtd">
<plist version="1.0">
<dict>
<key>SystemParameters</key>
<dict>
 <key>boot-args</key>
 <string>-v npci=0x2000</string>
 <key>prev-lang:kbd</key>
 <string>en:0</string>
 <key>InjectSystemID</key>
 <string>Yes</string>
 <key>LegacyBoot</key>
 <string>PBR</string>
</dict>
<key>Pointer</key>
<dict>
 <key>Speed</key>
 <string>8</string>
</dict>
<key>Graphics</key>
<dict>
 <key>GraphicsInjector</key>
 <string>No</string>
 <key>PatchVBiosBytes</key>
 <dict>
  <key>Find</key>
  <data>gAeoAqAF</data>
  <key>Replace</key>
  <data>gAeoAjgE</data>
 </dict>
</dict>
<key>RtVariables</key>
<dict>
<key>MLB</key>
<string>12345678123456789</string>
</dict>

</dict>
</plist>

collac432 · January 12, 2013

FSInjection is one way of injecting kexts from /efi/kexts/{censored} - not for vars.

But - it's clear - your RT variable services are not working properly from OSX. It's strange since it's American Megatrends EFI and I did not see such case so far. Only guys with Phoenix UEFI have similar issue, but it's worse then your case - their OSX is almost blocked for 10 minutes after boot. The solution for them is to use EmuVariableUEFI-64.efi, but this gives you KP (which is strange). I do not know ... if it works fine like this, I would not bother too much.

I know, but I'd like to get iMessages running, besides the fact that this can be the first of others comming needing RT variables.

I've used your DumpUefiCalls.efi and boot/runtime services gets variables requested ok.

With InjectSystemID=no, SmUUID=EB 9D 2D 31 2D 88 11 D3 9A 16 78 45 C4 06 xx xx:

...
->GetVariable(ROM, gEfiAppleNvramGuid, 0/6, 6, CC167258) = Success
78 45 C4 06 xx xx | xE..xx
->GetVariable(MLB, gEfiAppleNvramGuid, 0/6, 11, CC1671D0) = Success
57 38 30 43 xx xx xx 41 44 48 4A 46 31 32 33 34 | W80CxxxADHJF1234
35 | 5
...
Variables:
00000006 BS+RT+ gEfiAppleNvramGuid:MLB, DataSize = 11
57 38 30 43 xx xx xx 41 44 48 4A 46 31 32 33 34 | W80CxxxADHJF1234
35 | 5
00000006 BS+RT+ gEfiAppleNvramGuid:ROM, DataSize = 6
78 45 C4 06 xx xx | xE..xx
00000006 BS+RT+ gEfiAppleBootGuid:platform-uuid, DataSize = 10
EB 9D 2D 31 2D 88 11 D3 9A 16 78 45 C4 06 xx xx | ..-1-.....xE..xx

As you can see, the platform-uuid is set correctly, but my profile system shows me "UUID de hardware: 00000000-0000-1000-8000-7845C406xxxx" (7845C406xxxx is my ethernet mac address).

Same with nvram -p:

Davids-iMac:~ David$ nvram -p
platform-uuid %00%00%00%00%00%00%10%00%80%00xE%c4%06xx
fmm-computer-name David%e2%80%99s iMac

For some reason, those variables are ignored, may be when userland launched? It makes you any sense?

382jsl881 · January 12, 2013

Hello,

I have installed Clover manually on an USB drive (fat32, no UEFI), but Clover doesn't show up.

It stops with an _ (underscore) and nothing happening anymore. The _ doesn't flash which seems to be unusual in comparison to other posts (Brett Whinnen).

Chameleon does work by pressing [1] at startup.

There is no different result with Clover 32bit (pressing [3]) or Clover 64bit (pressing [6]).

32bit: shows "3" -> "_"

64bit: shows "7" -> "_"

Is my assumption correct, that it's not a problem of the boot0 and boot1 headers of the disk (wrong installation), but a problem with Covers 32bit/64bit files (boot3/6).

Just guessing, perhaps the EFI files can't be loaded or there is a problem with graphics (x3100)?

Can I switch on a on-screen debug log somehow? There are no signs of Clover in the boot-log from ioreg after booting Chameleon.

I use the following code (extracted from rc.local) to read my log

#!/bin/bash
ioreg -lw0 -pIODeviceTree | grep boot-log > ./chameleonLog1.txt
logdump=$(cat ./chameleonLog1.txt)
modified1=${logdump#*'boot-log'}
modified2=${modified1#*'<'}
modified3=${modified2%%'>'*}
echo $modified3 > ./chameleonLog2.txt
xxd -r -p ./chameleonLog2.txt >> chameleonLog3.txt
cat chameleonLog3.txt
rm chameleonLog*.txt

Best regards

-edit: seems to be a bug imho, see #834, #191

-edit: To enable debug output, change in CloverGrower-master/src/edk2/Clover/rEFIt_UEFI/Platform/Platform.h

//#define DEBUG_ALL 2

to

#define DEBUG_ALL 2

dmazar · January 12, 2013

For some reason, those variables are ignored, may be when userland launched? It makes you any sense?

Yes, it's not working properly. Your RT vars work fine up until boot.efi (plus AptioFix) relocates them into kernel image (as one of the last steps before jumping to kernel) - and then it does not work any more when kernel starts. Although that relocation should work fine if firmware code is written as per UEFI spec, this is obviously not the case with your firmware code that implements RT vars. This is the similar stuff as in some Phoenix UEFi implementations.

Unfortunately firmwares contains various bugs and and we can only try to find the workaround. But this is very very hard to debug and fix that if I do not have access to the board.

Can you try booting with EmuVar driver again and make a screenshot of a KP?

Slice · January 12, 2013

@collac432

May be you have AppleEFIRUNTIME.kext disabled? I know such solutions like %^&****.

Check

iHack:~ Slice$ sudo kextstat | grep EFI
Password:
  34    1 0xffffff7f81b5b000 0x4000	 0x4000	 com.apple.driver.AppleEFIRuntime (1.6.1) <7 6 5 4 3>
  39    0 0xffffff7f81b5f000 0x7000	 0x7000	 com.apple.driver.AppleEFINVRAM (1.6.1) <34 7 6 5 4 3>
iHack:~r Slice$

Can I switch on a on-screen debug log somehow? There are no signs of Clover in the boot-log from ioreg after booting Chameleon.

You can switch on debugging to EFI/misc/system.log by correcting EFI/BOOT/refit.conf

Uncomment string systemlog

# Enable the use of the log file (for debug purpose)
#systemlog

If you are able to compile the clover then I can propose you to make more debug messages at early boot.

collac432 · January 13, 2013

Can you try booting with EmuVar driver again and make a screenshot of a KP?

Sure. I attach ShellEFILogs by the way

SellEFILogs.zip

@collac432

May be you have AppleEFIRUNTIME.kext disabled? I know such solutions like %^&****.

Check

iHack:~ Slice$ sudo kextstat | grep EFI
Password:
34 1 0xffffff7f81b5b000 0x4000 0x4000 com.apple.driver.AppleEFIRuntime (1.6.1) <7 6 5 4 3>
39 0 0xffffff7f81b5f000 0x7000 0x7000 com.apple.driver.AppleEFINVRAM (1.6.1) <34 7 6 5 4 3>
iHack:~r Slice$

Hi Slice. Yes, both kexts are loaded.

Thank you for your help guys.

Alex009988 · January 13, 2013

People talk that real Macs have sound when the system is switching on. I though why don't we do it with Clover. All we have to do is write a sound-driver for EFI.

n3ph · January 13, 2013

Hi all,

This is my first post, so I'll do some introduction here.

I built my first and only Hackintosh so far in Oct 2011. Had been reading forums and so on in order to maintain my build. I've built this system using a popular setup (Chimera, ######, etc). I first know about Clover when my iMessage stopped working on 11 Jan 2013 and while looking for a solution.

After following much of the instructions, the most I've ever managed to accomplish is to boot my PC via Clover into a white screen. I'm using Radeon 6870. My suspicion is on Frame Buffer patching, but I do not understand the patching process well enough to make it work. I realise that the white screen phenomenal is similar to the white screen I will get while running the Mountain Lion installer.

As much as I would like to solve the problem myself, I think I require guidance to make this work.

Can anyone help guide me with this?

collac432 · January 13, 2013

@n3ph

For my experience with graphics drivers, white screen is due to graphics accelerator (AppleIntelHDx000GLDriver.kext on Intel HD case). Try to removing the corresponding kext for ati. If you can get desktop, you will have to deal with this kext.

Alex009988 · January 13, 2013

The best solution for Graphics - it's correct ATIFrambuffer +VideoBios in your DSDT(injector in your DSDT). Bootloaders inject Graphics worse than DSDT. Maybe I mistake.

Taruga · January 13, 2013

With Clover, Wake from sleep in Mountain Lion is kind of random for me. Sometimes it works, but most of the time it doesn't and just gives me a black screen.

I get best results by disabling XHCI

Is there any way do diagnose this ? (I'm using 10.8.3)

Funny thing is that with Lion is always works, it never failed.

With Chameleon, wake from sleep works fine in Mountain Lion and Lion also.

n3ph · January 13, 2013

Thanks for the tips collac432, Alex009988

Apologise for not stating earlier, I'm using UEFI without DSDT. I am able to boot using Chimera into OS X without additional configuration.

With regards to what collac432 said, I removed ATI6000Controller.kext for Mountain Lion installation, then installed it back after installing the OS. I am able to boot properly using Chimera, so I believe it's only a Clover configuration issue?

With regards to Alex009988, I did both ati_personality dump and radeon_bios_decode. I tried reading the guide @ /forum/topic/282787-clover-v2-instructions/ for patching ATIConnector, but since it was for 6670 while mine is 6870, the instruction's patch does not work with mine. I tried to understand ErmaC's instructions and do the patching myself using Duckweed, but a blank white screen is all I got.

It was actually an improvement from before I attempted the patch, as previously, I was able to see OS X's verbose output (up until macosx_swapon success) but I couldn't get into the GUI.

Will it help if I post my Radeon BIOS information?

Alex009988 · January 13, 2013

n3ph

<key>Graphics</key>

<dict>

<key>GraphicsInjector</key>

<key>InjectEDID</key>

<key>LoadVBios</key>

<key>FBName</key>

<string>yourFramebuffer</string>

If you want use clover, you should use these parameters. And correct Framebuffer

Will it help if I post my Radeon BIOS information?

Yes it help, if your graphics doesn't work.

n3ph · January 13, 2013

Hi guys, I came back defeated. This is my config.plist:

...
<plist version="1.0">
<dict>
   <key>SystemParameters</key>
   <dict>
       <key>boot-args</key>
       <string>-v npci=0x3000 slide=0 darkwake=0</string>
       <key>prev-lang:kbd</key>
       <string>en:0</string>
       <key>InjectSystemID</key>
       <string>Yes</string>
       <key>LegacyBoot</key>
       <string>PBR</string>
   </dict>
   <key>Pointer</key>
   <dict>
       ...
   </dict>
   <key>Graphics</key>
   <dict>
       <key>GraphicsInjector</key>
       <string>Yes</string>
       <key>InjectEDID</key>
   <string>Yes</string>
       <key>LoadVBios</key>
   <string>Yes</string>
       <key>PatchVBios</key>
       <string>Yes</string>
       <key>FBName</key>
       <string>Duckweed</string>
   </dict>
   <key>RtVariables</key>
   <dict>
       <key>MLB</key>
       <string>RM9MYSERIAL234567</string>
   </dict>
   <key>KernelAndKextPatches</key>
   <dict>
   <key>ATIConnectorsController</key>
   <string>6000</string>
   <key>ATIConnectorsData</key>
   <string>00040000040300000001000012040401000400000403000000010000220505020008000004020000000100001102030400020000140200000001000000000605</string>
   <key>ATIConnectorsPatch</key>
   <string>04000000040300000001000012040401040000000403000000010000220505020008000004020000000100001102030400020000140200000001000000000605</string>
   <key>SMBIOS</key>
   <dict>
   ...
   </dict>
 </dict>
</plist>

Using the above, I got OS X to boot, and then the screen goes totally blank (as opposed to white screen).

I thought there should be a

</dict>

just before

<key>SMBIOS</key>

, but when I inserted that line, OS X didn't even attempt to load GUI at all (stopped at verbose output)

As for kext patch, I attempted it as per ErmaC's instructions instructions but I am not clear. These are my personality dump and BIOS:

Personality: Duckweed
ConnectorInfo count in decimal: 4
Disk offset in decimal 179744
0000000    00  04  00  00  04  03  00  00  00  01  00  00  12  04  04  01
0000010    00  04  00  00  04  03  00  00  00  01  00  00  22  05  05  02
0000020    00  08  00  00  04  02  00  00  00  01  00  00  11  02  03  04
0000030    00  02  00  00  14  02  00  00  00  01  00  00  00  00  06  05
0000040

ATOM BIOS Rom:
   SubsystemVendorID: 0x1462 SubsystemID: 0x2450
   IOBaseAddress: 0xe000
   Filename: V245ELPIDAB.
   BIOS Bootup Message: 113-
MSITV245MS.1C0 BARTS XT ELPIDA B DIE 32MX32 1G                            
PCI ID: 1002:6738
Connector at index 0
   Type [@offset 44281]: DisplayPort (10)
   Encoder [@offset 44285]: INTERNAL_UNIPHY2 (0x21)
   i2cid [@offset 44409]: 0x90, OSX senseid: 0x1
Connector at index 1
   Type [@offset 44291]: DisplayPort (10)
   Encoder [@offset 44295]: INTERNAL_UNIPHY2 (0x21)
   i2cid [@offset 44436]: 0x91, OSX senseid: 0x2
Connector at index 2
   Type [@offset 44301]: HDMI-A (11)
   Encoder [@offset 44305]: INTERNAL_UNIPHY1 (0x20)
   i2cid [@offset 44463]: 0x93, OSX senseid: 0x4
Connector at index 3
   Type [@offset 44311]: DVI-D (3)
   Encoder [@offset 44315]: INTERNAL_UNIPHY1 (0x20)
   i2cid [@offset 44490]: 0x95, OSX senseid: 0x6
Connector at index 4
   Type [@offset 44321]: DVI-I (2)
   Encoder [@offset 44325]: INTERNAL_UNIPHY (0x1e)
   i2cid [@offset 44527]: 0x94, OSX senseid: 0x5
Connector at index 5
   Type [@offset 44331]: DVI-I (2)
   Encoder [@offset 44335]: INTERNAL_KLDSCP_DAC1 (0x15)
   i2cid [@offset 44527]: 0x94, OSX senseid: 0x5

Somebody tell me if I've edited it correctly? =(

Alex009988 · January 13, 2013

n3ph

Do dump with it

http://nologic.com/redsock_bios_decoder.zip

Slice · January 13, 2013

With Clover, Wake from sleep in Mountain Lion is kind of random for me. Sometimes it works, but most of the time it doesn't and just gives me a black screen.

I get best results by disabling XHCI

Is there any way do diagnose this ? (I'm using 10.8.3)

Funny thing is that with Lion is always works, it never failed.

With Chameleon, wake from sleep works fine in Mountain Lion and Lion also.

With legacy Clover boot sleep/wake works also on ML and Lion.

The problem only with UEFI boot into ML.

Taruga · January 13, 2013

yeah, I 'm using UEFI boot

So, are you guys close to a fix or it´s one of those weird to understand thing ?

el_charlie · January 13, 2013

With legacy Clover boot sleep/wake works also on ML and Lion.

The problem only with UEFI boot into ML.

I'm not following this.

What do you mean by UEFI boot??

My mobo doesn't have UEFI, just a regular BIOS. And clover boots fine. I managed to work boot into legacy Windows 8, too.

My computer doesn't wake from sleep and when I restart it, the BIOS settings are messed up and I have to configure it all over again.

Cheers!

EDIT:

Sleep actually is not an issue for me because I never let my PC sleep because I'm always doing something (downloading, etc). The only thing that bothers me right now it to set a custom RAM speed. Can somebody help me with that?? My system is overclocked an it detects only the stock speed even if the boot.log says different.

n3ph · January 14, 2013

Hi Alex009988,

V245ELPIDAB.:
113-
MSITV245MS.1C0 BARTS XT ELPIDA B DIE 32MX32 1G						
Subsystem Vendor ID: 1462
 Subsystem ID: 2450
Object Header Structure Size: 407
Connector Object Table Offset: 52
Router Object Table Offset: 0
Encoder Object Table Offset: 12a
Display Path Table Offset: 12
Connector Object Id [19] which is [DISPLAY_PORT]
encoder obj id [0x21] which is [iNTERNAL_UNIPHY2 (osx txmit 0x12 [duallink 0x2] enc 0x4)] linkb: false
Connector Object Id [19] which is [DISPLAY_PORT]
encoder obj id [0x21] which is [iNTERNAL_UNIPHY2 (osx txmit 0x22 [duallink 0x2] enc 0x5)] linkb: true
Connector Object Id [12] which is [HDMI_TYPE_A]
encoder obj id [0x20] which is [iNTERNAL_UNIPHY1 (osx txmit 0x11 [duallink 0x1] enc 0x2)] linkb: false
Connector Object Id [3] which is [DVI_D]
encoder obj id [0x20] which is [iNTERNAL_UNIPHY1 (osx txmit 0x11 [duallink 0x1] enc 0x2)] linkb: false
Connector Object Id [2] which is [DVI_I]
encoder obj id [0x1e] which is [iNTERNAL_UNIPHY (osx txmit 0x10 [duallink 0x0] enc 0x0)] linkb: false
Connector Object Id [2] which is [DVI_I]
encoder obj id [0x15] which is [iNTERNAL_KLDSCP_DAC1 (osx txmit 0x00 enc 0x10?)] linkb: false

Edit: I made some progress. One of the reasons why I had white screen is because I had PatchVBios to Yes. Another unexpected reason was because I set the ProductName to be Macmini5,3 in the SMBIOS section!

I was able to make it boot with the Mac12,2 definition found @ http://www.tonymacx86.com/general-help/84047-imessage-wont-work-56.html. I was able to get iMessage to sign in, but when I rebooted using Chimera with my usual Macmini5,3, I got logged out of iMessage. Either I have to make the Macmini definition work or I'll have to use iMac from now on. I'm reluctant to use iMac as Macmini definition has more stepping for my 2600k. I'm looking around for more information on making it work with Clover..

Edited January 14, 2013 by n3ph

Alex009988 · January 14, 2013

What the main port does you use?

And How many ports you have? 5 or 6.

You shoul use Berlushes FB. For 6 ports

Don't use it. It just for you to more easier search at hex edit.

0000000 00 04 00 00 04 03 00 00 00 01 00 00 11 02 01 01

0000010 00 04 00 00 04 03 00 00 00 01 00 00 21 03 02 02

0000020 00 04 00 00 04 03 00 00 00 01 00 00 12 04 03 03

0000030 00 04 00 00 04 03 00 00 00 01 00 00 22 05 04 04

0000040 00 04 00 00 04 03 00 00 00 01 00 00 10 00 05 05

0000050 00 04 00 00 04 03 00 00 00 01 00 00 20 01 06 06

ConnectorType

02 00 00 00 LVDS

04 00 00 00 DVI DL(Dual Link)

00 02 00 00 DVI SL(Single Link)

10 00 00 00 VGA

80 00 00 00 S-V

00 04 00 00 DP

00 08 00 00 HDMI

Encoder, Transmitter and SenseID you do right.

But you ought to use FB adequate the number of ports.

Slice · January 14, 2013

yeah, I 'm using UEFI boot

So, are you guys close to a fix or it´s one of those weird to understand thing ?

It's a pity it is weird to understand :wallbash:

Alex009988 · January 14, 2013

Hi, slice

How do you feel about this to make clover more better? More exactly,

The real mac have sound when this one is swithing on. And it come from EFI.

All you need is to write a sound's EFI driver.

How do you look at my offer? It would really better make the clover.

And then it will be visible difference versus Chameleon.

el_charlie · January 14, 2013

Hi, slice

How do you feel about this to make clover more better? More exactly,

The real mac have sound when this one is swithing on. And it come from EFI.

All you need is to write a sound's EFI driver.

How do you look at my offer? It would really better make the clover.

And then it will be visible difference versus Chameleon.

If you're using a motherboard with UEFI, probably you can set a custom boot picture and sometimes a custom boot sound.

I'm more interested in changing the name of the partitions you can select to boot. Like in chameleon. Also, how to set a custom RAM speed because it's detecting my RAM at stock speed but I have them overclocked.

Another thing that annoys me is that my mouse (Cyborg R.A.T. 5) doesn't work properly. It can even move to the left. Maybe it's because it's made differently and even on OSX I need its drivers to work fine. It has high DPI.

Cheers!

Alex009988 · January 14, 2013

el_charlie

Wait!

Clover is a real EFI. Only one difference is that Clover boots to Random Access Memory. And real EFi installed onto Read-Only Memory,

So that, it's teorically possible. Need sound-driver.

At Chamellion this thing looks more difficultly as Chamellion have just shown the system that EFI had worked yet. And do it super a lot sucsesfully.

So that, Slice we demand and ask start up sounds at Clover

Clover General discussion

Recommended Posts

Link to comment

Share on other sites

Link to comment

Share on other sites

Link to comment

Share on other sites

Link to comment

Share on other sites

Link to comment

Share on other sites

Link to comment

Share on other sites

Link to comment

Share on other sites

Link to comment

Share on other sites

Link to comment

Share on other sites

Link to comment

Share on other sites

Link to comment

Share on other sites

Link to comment

Share on other sites

Link to comment

Share on other sites

Link to comment

Share on other sites

Link to comment

Share on other sites

Link to comment

Share on other sites

Link to comment

Share on other sites

Link to comment

Share on other sites

Link to comment

Share on other sites

Link to comment

Share on other sites

Link to comment

Share on other sites

Link to comment

Share on other sites

Link to comment

Share on other sites

Link to comment

Share on other sites

Link to comment

Share on other sites