1638 replies to this topic

[tdtran1025]

magnifico, on 13 March 2013 - 12:00 PM, said:

  

If you don't have motherboard with UEFI Bios, I can't help you

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.

[theconnactic]

Hi, tdtran1025!

Out of curiosity, is it the HD5450?

Best regards!

[bobstrike]

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.c...3709/hd4000.jpg

[ruki250]

bobstrike, on 15 March 2013 - 09:08 AM, said:

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.c...3709/hd4000.jpg

In Graphics section add this

<key>DualLink</key>
<string>0</string>

[bobstrike]

ruki250, on 15 March 2013 - 11:01 AM, said:

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]

bobstrike, on 15 March 2013 - 11:33 AM, said:

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]

ruki250, on 15 March 2013 - 12:41 PM, said:

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]

tdtran1025, on 15 March 2013 - 06:16 AM, said:

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]

jlfilms, on 16 March 2013 - 03:44 AM, said:

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.

Eps, on 11 March 2013 - 06:26 AM, said:

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]

jlfilms, on 18 March 2013 - 02:10 AM, said:

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>

Quote

and how do i transfer clover to hd?

thanks

 Screen Shot 2013-03-18 at 6.48.31.png   129.7K   33 downloads  Screen Shot 2013-03-18 at 6.48.57.png   167.11K   29 downloads

[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]

dmazar, on 19 March 2013 - 01:32 PM, said:

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.