Clover General discussion

[ruki250]

Please help !

Does anyone know how to convert the instruction from ocBp <key>HD4000PlatformId</key>

<string>3</string> in

Clover

?

I am trying to obtain native resolution with the <key>DeviceProperties</key>

<string>xxxxxxxxxxxx........xxxx</string> string but with some strings i have 1024x768 with other black screen.

I would like to reach native resolution on HD4000 like with the abovementioned command in ocBp.

I am using

clover

in UEFI mode on Asus n56vm

 

 

with the string

<string>8800000001000000010000007c0000000200000002010c 00d041030a000000000101060000027fff040010000000 6d006f00640065006c0000001a000000496e74656c2048 4420477261706869637320343030302c00000041004100 50004c002c00690067002d0070006c006100740066006f 0072006d002d006900640000000800000004006601</string>

i reach native resolution but duplicated four times .

How to correct this ?

https://dl.dropbox.com/u/48963709/hd4000.jpg

 

 

In Graphics section add this

 

<key>DualLink</key>

<string>0</string>

[bobstrike]

In Graphics section add this

 

<key>DualLink</key>

<string>0</string>

thank you for the suggestion but no success.

is there any alternative in Clover than using a EFI string ?

GFX0 is patched in dsdt and in ocBp (I had the same problem with chameleon) i solved with

 

<key>HD4000PlatformId</key>

<string>3</string>

I need a similar solution in Clover

[ruki250]

 

thank you for the suggestion but no success.

is there any alternative in Clover than using a EFI string ?

GFX0 is patched in dsdt and in ocBp (I had the same problem with chameleon) i solved with

 

<key>HD4000PlatformId</key>

<string>3</string>

I need a similar solution in Clover

 

post your gfx0-dsdt section

[bobstrike]

post your gfx0-dsdt section

 

Because the patch is complicated i post the whole dsdt

https://dl.dropbox.c...963709/dsdt.aml

 

 

Problem Solved

 

Thank you !

[magnifico]

 

 

Magnifico,

I played with it for about 1 hour (10 or 20 reboots to test) and finally figured it out on BIOS mother board.

The set up is very much like what your instruction says, maening install Clover's /EFI to EFI partitions of the RAID0 volumes.

Then all I need is copy "Boot" into both Boot OS X partitions. Now that I think about it, Slice has mentioned something like it before but I did not understand the boot process. Now it makes sense.

I had to switch to Clover for 1 reason even if my board is BIOS based. I have a off-brand ATI card. After every update, Chamelon refuses to boot. I would have to boot from another partition, change the device ID of the card in 2 kexts. Clover boots without a fuss, gives me unaccelerated screen to work it. This is the game changer for me.

Thank you for your response.

 

Man ...i dont unterstand your problem....but you have or not mainboard with bios UEFI .?

 

[jlfilms]

im having trouble with my wake sleep i thnk, when screen saver goes on the monitor says no signal but when i move mouse it works. Im using clover , is there a kext to fix this

'?

 

 

z77 ds3h

i5 3570k 3.4ghz

evga geforce gtx 650 ti 1gb

8gb ddr3 ram

thanks

[Slice]

im having trouble with my wake sleep i thnk, when screen saver goes on the monitor says no signal but when i move mouse it works. Im using clover , is there a kext to fix this

'?

 

 

z77 ds3h

i5 3570k 3.4ghz

evga geforce gtx 650 ti 1gb

8gb ddr3 ram

thanks

<key>PCI</key>
<dict>
 <key>USBInjection</key>
 <string>Yes</string>
 <key>USBFixOwnership</key>
 <string>Yes</string>
 <key>InjectClockID</key>
 <string>Yes</string>
</dict>

[jlfilms]

i just add that in my config.plist?

[bobstrike]

How to fix Usb 3.0 with Clover UEFI ?

To make it work USB 3.0 natively, in Bios->USB settings->Legacy USB Disabled; Bios-> USB Settings -> XHCI Pre Boot Mode Enabled

It works in Chameleon!

In Clover if no USB plugged the machine boots ok, when any USB is plugged the machine freezes.

If I try to Boot with USB plugged in the machine doesn'n boot.

How to fix this ?

Thank you

[RobertX]

...as suggested by theconnactic, i'm posting this prob here....i have installed 10.8.3 from usb hdd...on a separate hdd from windows 8...the second hdd is partitioned ntfs(for storage), fat32(for sharing), hfs journaled for mac(on e-sata) after installing chameleon on new hfs partition i cannot start from mac hdd partition(boot0:error) i have to start from the usb in safe mode to reach desktop... if i use clover on the usb installer hdd to boot, "system hangs at "waitforsystemmapper" then a backtrace(same using chameleon from usb)only safe boot...i may try reinstall but just sayin'

 

edit: this is probably not clover related...more likely graphics...moderator can move this post....

[Ritz Carltn]

Hey, Eps, long time no chat n irc.

Clover had kernel patcher feature credited by pcj already.

I use HP MiniNote 2140 post this thread with CPU ATOM N270 in IA32 architecture in Clover + Snow Leopard.

[jlfilms]

My Id for graphics card is wrong, how do i fix that,?

and how do i transfer clover to hd?

 

thanks

[Slice]

My Id for graphics card is wrong, how do i fix that,?

<key>KernelAndKextPatches</key>
<dict>
 <key>Debug</key>
 <string>Yes</string>
 <dict>
   <key>0</key>
   <dict>
     <key>Name</key>
     <string>ATI6000Controller</string>
     <key>InfoPlistPatch</key>
     <string>Yes</string>
     <key>Find</key>
     <string>0x67501002 </string>
     <key>Replace</key>
     <string>0x67521002 </string>
   </dict>
 </dict>
</dict>

 

and how do i transfer clover to hd?

 

thanks

[riverscn]

Hi Slice,

 

I want to patch ATI kexts with KextsToPatch, like this:

 

<key>0</key>
<dict>
<key>Find</key>
<string>0x68001002 0x68061002 0x68081002 0x68181002</string>
<key>InfoPlistPatch</key>
<string>Yes</string>
<key>Name</key>
<string>AMDRadeonAccelerator</string>
<key>Replace</key>
<string>0x68001002 0x68061002 0x68081002 0x68191002</string>
</dict>
<key>1</key>
<dict>
<key>Find</key>
<string>0x68001002 0x68061002 0x68081002 0x68181002</string>
<key>InfoPlistPatch</key>
<string>Yes</string>
<key>Name</key>
<string>ATI7000Controller</string>
<key>Replace</key>
<string>0x68001002 0x68061002 0x68081002 0x68191002</string>
</dict>

 

But it won't work.

 

What is wrong? Help me please.

[dmazar]

They are probably not in kernelcache yet since they are not used. Try booting with blocking kernelcache (space on OSX icon in Clover and then choose blocking cache option). If this works, then you need to rebuild kernel cache with:

> sudo touch /System/Library/Extensions

 

If all is ok, you can then reboot normally (with kernelcache) and patching will work.

[riverscn]

They are probably not in kernelcache yet since they are not used. Try booting with blocking kernelcache (space on OSX icon in Clover and then choose blocking cache option). If this works, then you need to rebuild kernel cache with:

> sudo touch /System/Library/Extensions

 

If all is ok, you can then reboot normally (with kernelcache) and patching will work.

 

don't work, either.

[ZenGiga]

2 hours after starting and many reboots later I finally managed to get Clover UI to show up \o/

 

It's slick, I like it

 

For some reason doing F12 Boot to select the USB stick as boot device was utterly failing (at boot it just kept skipping directly to the Chameleon install on the HD). Despite the fact that I've always done that before when testing chameleon from a USB stick. Some oddity of my mobo and FAT32 format perhaps? No idea.

 

What finally worked was going into BIOS and setting USB as first in boot device priority, before HD or CD.

 

Successfully booted into my test OSX install -- which promptly spontaneously rebooted after about a minute, but hey it's a start, now to working on all the dsdt fixes etc.

 

Bottom line: if you've come across this post because you're failing to even reach the Clover UI during a legacy BIOS boot, try changing the BIOS boot device priority settings.

[Lordadmiral Drake]

How would I change graphics card model displayed in SysProfiler?

 

With Chameleon it was correctly identified as Radeon HD6850M

 

With Clover its reported as Radeon HD 5770 series

 

The card is working as intended, it's just a cosmetic issue.

 

 

Also I got a problem with AICPM.kext

 

Before switching to Clover it worked fine, but now it's failing to load with the following messages in console:

 

19.03.13 21:18:28,000 kernel[0]: kxld[com.apple.driver.AppleIntelCPUPowerManagement]: The following symbols are unresolved for this kext:
19.03.13 21:18:28,000 kernel[0]: kxld[com.apple.driver.AppleIntelCPUPowerManagement]: _pm_init_lock
19.03.13 21:18:28,000 kernel[0]: Can't load kext com.apple.driver.AppleIntelCPUPowerManagement - link failed.
19.03.13 21:18:28,000 kernel[0]: Failed to load executable for kext com.apple.driver.AppleIntelCPUPowerManagement.
19.03.13 21:18:28,000 kernel[0]: Kext com.apple.driver.AppleIntelCPUPowerManagement failed to load (0xdc008016).
19.03.13 21:18:28,000 kernel[0]: Failed to load kext com.apple.driver.AppleIntelCPUPowerManagement (error 0xdc008016).

 

Another cosmetic problem is RAM:

 

My laptop has 4 memory slots where 1 and 3 are equipped with a 4GB module each.

All 8GB are detected correctly by the system.

But in About this Mac/SysProfiler only the first 2 slots are shown

 

I use MacBook Pro 8,3 as system identifier

[jlfilms]

I did this yesterday because my system was still mac mini server 6,2 profile for my sysytem to be fully functional.

 

I followed guide on youtube that showed me how to edit all my specs, its very easy. also put picture of my case where the mac mini pic was

and changed name to Mac Pro Early 2013.

 

youtube it , or i can post it if you cant find it

[rd8111]

Hello All,

 

I have been trying to have Clover simply launch on my FX-8350, Gigabyte GA-990FXA-UD5, ATI FirePro v4900. I have enabled the DEBUG_ALL macro in Platform.h, re-compiled with cloverpro, copied the resulting 64-bit EFI files over to my flash drive and booted. The resulting debug messages tell me that Clover is having fits with the FirePro (Device ID 6749, Vendor ID 1002). I have also noticed that ati.c has this FirePro version and many other cards in the same graphics family commented out. The final PCI message sent to the display says:

 

73:095 0:000 PCI (00 | 03:00.00) : 1002 6749 class=030000

 

Then the Clover startup stops dead in its tracks.

 

Any suggestions on which file(s) to modify? Is there something specific to enable within ati.c? I can successfully launch Snow Leopard with the r726 Chameleon, but have discovered that others highly recommend Clover for FX systems. I have tried the 1050 Clover, the 1175, and 1179 builds, before enabling the source code macro. Since I have the same black screen behavior for all three versions, I assume that all three do not like the FirePro. Isn't there VESA sensing, such that the commented out cards in ati.c would use VESA data to display? In 10.6.8 SL, I added the 6749 to the ATI6000Controller kext and have a fully functional FirePro (see here for the procedure). Is a similar solution needed within ati.c?

 

I have a spare ancient Radeon 9600 Pro that I will try in my FX system sometime Saturday morning. Anyone try using that video card with recent Clover builds?

[kantok]

I did this yesterday because my system was still mac mini server 6,2 profile for my sysytem to be fully functional.

 

I followed guide on youtube that showed me how to edit all my specs, its very easy. also put picture of my case where the mac mini pic was

and changed name to Mac Pro Early 2013.

 

youtube it , or i can post it if you cant find it

 

Wow! Do you have new macpro identifier? Could you share us the youtube URL?

 

Thanks,

[rd8111]

Hello All,

 

I have been trying to have Clover simply launch on my FX-8350, Gigabyte GA-990FXA-UD5, ATI FirePro v4900. I have enabled the DEBUG_ALL macro in Platform.h, re-compiled with cloverpro, copied the resulting 64-bit EFI files over to my flash drive and booted. The resulting debug messages tell me that Clover is having fits with the FirePro (Device ID 6749, Vendor ID 1002). I have also noticed that ati.c has this FirePro version and many other cards in the same graphics family commented out. The final PCI message sent to the display says:

 

73:095 0:000 PCI (00 | 03:00.00) : 1002 6749 class=030000

 

Then the Clover startup stops dead in its tracks.

 

Any suggestions on which file(s) to modify? Is there something specific to enable within ati.c? I can successfully launch Snow Leopard with the r726 Chameleon, but have discovered that others highly recommend Clover for FX systems. I have tried the 1050 Clover, the 1175, and 1179 builds, before enabling the source code macro. Since I have the same black screen behavior for all three versions, I assume that all three do not like the FirePro. Isn't there VESA sensing, such that the commented out cards in ati.c would use VESA data to display? In 10.6.8 SL, I added the 6749 to the ATI6000Controller kext and have a fully functional FirePro (see here for the procedure). Is a similar solution needed within ati.c?

 

I have a spare ancient Radeon 9600 Pro that I will try in my FX system sometime Saturday morning. Anyone try using that video card with recent Clover builds?

 

Hello All,

 

After reviewing the ati.c source some more and looking hard at the other ATI graphics cards with Device IDs around 6749 (e.g. the HD6570, Device ID 0x6759, and HD6670, Device ID 0x6758, most closely match the three connector output style of the v4900), I estimated that the Pithecia chip family is highly likely correct for the v4900. Note that the Device IDs listed for the 6570 and 6670 do indeed have odd looking values (out of sequence relative to model number).

 

Anyhow, after determining this, I decided to test this by adding the FirePro to the ati.c listing right before 0x674A, setting everything up appropriately, compiling, creating a test 1179 build package, installing on my flash drive, and booting again. After waiting about 90 seconds while the Clover booting system inspected the system, I have finally reached the Main Clover GUI screen. I will test this more and see what happens next.

 

When I am pleased with the results, I would like to update the ati.c source code. What is the proper procedure to add this change to the Clover source? Should the exact line be posted for someone else to add the change? The line is:

 

{ 0x6749, 0x00000000, CHIP_FAMILY_TURKS, "ATI Radeon FirePro V4900", kPithecia },

 

Sincerely,

 

rd8111

[theconnactic]

Congratulations not only to have it working by yourself, but also to have made a contribution that potentially will benefit other Clover users. Hope Slice & the Clover dev. team update the source code soon.

 

All the best!

[rd8111]

Congratulations not only to have it working by yourself, but also to have made a contribution that potentially will benefit other Clover users. Hope Slice & the Clover dev. team update the source code soon.

 

All the best!

 

Thanks, theconnactic

[Andy Vandijck]

@Clover dev team:

Just installed OS X 10.8.3 for a friend of mine.

Ofcourse I used Clover as the booter of choice.

It was an Asus board and everything works great.

From me and my buddy Joris:

A big thank you for all the hard work involved in Clover.

It's awesome ...