1666 replies to this topic

[kyndder]

alexanderq, on 04 October 2012 - 03:42 PM, said:

i tried in chameleon whith pithecia and graphicsenabler=yes it worked i had qe/ci i can open dvd player and it detect it as hd6450

Use the command below to get the video string using Chameleon...

ioreg -lw0 -p IODeviceTree -n efi -r -x | grep device-properties | sed 's/.*<//;s/>.*//;'}

Copy the output and use as "DeviceProperties"...

<key>PCI</key>
<dict>
<key>StringInjector</key>
<string>Yes</string>
<key>DeviceProperties</key>
<string>[color=#ff0000]PLACE THE OUTPUT HERE[/color]</string>
<key>PCIRootUID</key>
<string>0</string>
</dict>

[alexanderq]

polkaholga, on 04 October 2012 - 04:56 PM, said:

Ati connector patch is not enough on it's own !!

To make HDMI audio of your descrete graphics card working you have to make the necessary edits to your DSDT too !!

But all this is going OT here, so please use the search !!!

But of course i have done the DSDT edits i have one week reading remember

[e60]

Hey Guys,

first of all I want to thank you for the great work and all your attainments regarding to Clover! I was testing some stuff and ran into different issues, so for that reason I really need your help.

So let's beginn with my system specs:

- CPU: Intel i5 3570K
- Motherboard: Gigabyte GA-H77-DS3H latest F7 AMI Alaska UEFI Bios
- GPU: Onboard Intel HD 4000
- OS: Only Mountain Lion 10.8.2 (12C54)
- Identifier: Mac Book Pro 9.2 because of the Chipset - Also tried iMac12.2 but it gave me AGPM issues
- Custom DSDT: Yes

First I've installed the non UEFI version for testing and everything seemed to work flawless. I could boot into OS X, had full CI/QE etc. Then I've tested my USB 3.0 ports but they were not working properly. When I plugged in a USB 2.0 device, nothing happened at all. Setting the ports to USB 2.0 in Bios lets them work in 2.0 mode at least.

This would be ok for me, because I don't own any USB 3.0 products at this time. The more annoying thing is that my screen won't wake up when I set the machine to sleep and try to wake it up if I'm using my custom DSDT. What surprises me very much, is the fact that this is not happening every time!

For example: I can go to sleep for about ten times without any issues. Then, the eleventh time the screen won't wake up from sleep. Without DSDT sleep seems to work well. By the way, I'm running into the same issues using the latest version of Chameleon and don't have ANY idea how to solve it!  

So far so good. After the whole testing I decided to install the UEFI version. Unfortunately it isn't even booting. I have the following stuff in "drivers64UEFI":

- DataHubDxe-64.efi
- FSInject-64.efi
- OsxAptioFixDrv-64.efi
- OsxFatBinaryDrv-64.efi
- OsxLowMemFixDrv-64.efi
- PartitionDxe-64.efi
- VBoxHfs.64.efi - also tried HFSPlus.efi, but it has no effect.

I've attached Clover's config.plist, my custom DSDT and the preboot.log. So if anybody could help me to solve my problems, especially the sleep issue, I would be the happiest man on Planet Earth! Many thanks in advance!

By the way... is there any quiet boot option in Clover and is it possible to wake the system via keyboard?


*Edit*


Adding "darkwake=0" into <key>boot-args</key> isn't changing anything.

Attached Files

•  Clover stuff.zip   57.75K   18 downloads

[kyndder]

e60, on 04 October 2012 - 06:49 PM, said:

First I've installed the non UEFI version for testing and everything seemed to work flawless. I could boot into OS X, had full CI/QE etc. Then I've tested my USB 3.0 ports but they were not working properly. When I plugged in a USB 2.0 device, nothing happened at all. Setting the ports to USB 2.0 in Bios lets them work in 2.0 mode at least.

You should use the non-UEFI Clover because you don't have a UEFI BIOS...

e60, on 04 October 2012 - 06:49 PM, said:

This would be ok for me, because I don't own any USB 3.0 products at this time. The more annoying thing is that my screen won't wake up when I set the machine to sleep and try to wake it up if I'm using my custom DSDT. What surprises me very much, is the fact that this is not happening every time!

For example: I can go to sleep for about ten times without any issues. Then, the eleventh time the screen won't wake up from sleep. Without DSDT sleep seems to work well. By the way, I'm running into the same issues using the latest version of Chameleon and don't have ANY idea how to solve it!  

Did you patched your AppleRTC.kext???

e60, on 04 October 2012 - 06:49 PM, said:

So far so good. After the whole testing I decided to install the UEFI version. Unfortunately it isn't even booting. I have the following stuff in "drivers64UEFI":

- DataHubDxe-64.efi
- FSInject-64.efi
- OsxAptioFixDrv-64.efi
- OsxFatBinaryDrv-64.efi
- OsxLowMemFixDrv-64.efi
- PartitionDxe-64.efi
- VBoxHfs.64.efi - also tried HFSPlus.efi, but it has no effect.

As I told above you should use Clover for BIOS boot , BTW, leave only the divers below inside of your "/EFI/drivers64UEFI" folder...

FSInject-64.efi
USBMouseDXE-64.efi

e60, on 04 October 2012 - 06:49 PM, said:

By the way... is there any quiet boot option in Clover and is it possible to wake the system via keyboard?

Set timeout to 0 at "refit.conf" file...

[EDIT]

Sorry, I did not saw that you had placed your MOBO specs...

[dmazar]

kyndder, on 04 October 2012 - 08:17 PM, said:

BTW, leave only the divers below inside of your "/EFI/drivers64UEFI" folder...

FSInject-64.efi
USBMouseDXE-64.efi

No, no. For UEFI boot definately needed in /efi/drivers64UEFI: HFSPlus (or VboxHfs) and FatBin. Then try to boot.

If this does not work, then add LowMemFix and try to boot.

If still does not work, then remove LowMemFix and add AptioFix (so, HFS, FatBin and AptioFix). aptioFix requires adding "slide=0" to boot args in config.plist.

If this does not work, then there is a problem.

[kyndder]

dmazar, on 04 October 2012 - 08:54 PM, said:

No, no. For UEFI boot definately needed in /efi/drivers64UEFI: HFSPlus (or VboxHfs) and FatBin.

Thanks for correcting me dmazar ...

I had not seen that he had UEFI BIOS, only saw when I had already answered...

I've never used the Clover on real UEFI...

[e60]

Hey guys,

thank you very much for your help!

@kyndder

Quote

Did you patched your AppleRTC.kext???

Nope, not yet. If you're meaning the perl script.

Quote

Set timeout to 0 at "refit.conf" file...

Thank you for the info. This parameter is for quiet boot, right?

Quote

Sorry, I did not saw that you had placed your MOBO specs...

No problem! I've just updated my signature too.


@dmazar

Quote

No, no. For UEFI boot definately needed in /efi/drivers64UEFI: HFSPlus (or VboxHfs) and FatBin. Then try to boot.

If this does not work, then add LowMemFix and try to boot.

If still does not work, then remove LowMemFix and add AptioFix (so, HFS, FatBin and AptioFix). aptioFix requires adding "slide=0" to boot args in config.plist.

If this does not work, then there is a problem.

Thank you for your advise. I'll try this after work and report the results later.

[linzhouyu]

Clover cannot boot my windows 7 installed with gpt-mbr hybrid partition tables, it detects windows partition as Legacy OS but freeze in "Booting OS...". I tried to set LegacyBoot key from PBR to MBR, but it doesn't make any sense. I wonder if the Clover can only boot Windows EFI?
BTW, can I manually set a proper resolution for Clover just like Chameleon(with Graphic Mode key)?
Thanks.

[alexanderq]

kyndder, on 04 October 2012 - 05:14 PM, said:

Use the command below to get the video string using Chameleon...

ioreg -lw0 -p IODeviceTree -n efi -r -x | grep device-properties | sed 's/.*<//;s/>.*//;'}

Copy the output and use as "DeviceProperties"...

<key>PCI</key>
<dict>
<key>StringInjector</key>
<string>Yes</string>
<key>DeviceProperties</key>
<string>[color=#ff0000]PLACE THE OUTPUT HERE[/color]</string>
<key>PCIRootUID</key>
<string>0</string>
</dict>

It gave me      sed: 1: "s/.*<//;s/>.*//;}": unexpected }

[Mohamed Khairy]

my microsoft wireless mouse 4000 worked
but my alps touchpad not worked

[kyndder]

alexanderq, on 05 October 2012 - 10:08 AM, said:

It gave me   sed: 1: "s/.*<//;s/>.*//;}": unexpected }

Sorry, my bad, corrected below...

ioreg -lw0 -p IODeviceTree -n efi -r -x | grep device-properties | sed 's/.*<//;s/>.*//;'

[EDIT]

You always can use DarwinDumper > http://www.insanelym...howtopic=282794

e60, on 05 October 2012 - 08:20 AM, said:

Nope, not yet. If you're meaning the perl script.

Yes, you can patch manually or you can let Clover do this...

<key>AppleRTC</key>
<string>Yes</string>

e60, on 05 October 2012 - 08:20 AM, said:

Thank you for the info. This parameter is for quiet boot, right?

Yes...

[e60]

@dmazar

Quote

No, no. For UEFI boot definately needed in /efi/drivers64UEFI: HFSPlus (or VboxHfs) and FatBin. Then try to boot.

If this does not work, then add LowMemFix and try to boot.

If still does not work, then remove LowMemFix and add AptioFix (so, HFS, FatBin and AptioFix). aptioFix requires adding "slide=0" to boot args in config.plist.

If this does not work, then there is a problem.

Seems like there is a problem. I've tried everything you mentioned, but still can't boot with UEFI.

Quote

Yes, you can patch manually or you can let Clover do this...

<key>AppleRTC</key>
<string>
Yes
</string>

@kyndder

Tried both. Pearl script ...

sudo perl -pi -e 's|\x75\x30\x89\xd8|\xeb\x30\x89\xd8|' /System/Library/Extensions/AppleRTC.kext/Contents/MacOS/AppleRTC

and ...

<key>KernelAndKextPatches</key>
<dict>
	 <key>AppleRTC</key>
	 <string>Yes</string>
</dict>

​... unfortunately with the same result, no screen after sleep. Without DSDT everything works fine. So is this something DSDT related or could it be something hardware related?

[kyndder]

e60, on 05 October 2012 - 04:34 PM, said:

@kyndder

Tried both. Pearl script ..

​... unfortunately with the same result, no screen after sleep. Without DSDT everything works fine. So is this something DSDT related or could it be something hardware related?

Did you have SBUS fix on your DSDT???

If yes, did you already tried to wake your machine using the power button instead of moving the mouse or pressing some keyboard key???

[Slice]

e60, on 05 October 2012 - 04:34 PM, said:

Without DSDT everything works fine. So is this something DSDT related or could it be something hardware related?

Yes, it is DSDT related. Why you need your quirky DSDT if without it "all works fine"?

[STLVNUB]

@Slice
about the rc.local, can you use this instead please.

#!/bin/bash
ioreg -lw0 -pIODeviceTree | grep boot-log > /log.txt
logdump=$(cat /log.txt)
modified1=${logdump#*'boot-log'}
modified2=${modified1#*'<'}
modified3=${modified2%%'>'*}
echo $modified3 > /boot-log.txt
date "+DATE: %Y-%m-%d TIME: %H:%M:%S%n" > /boot.log
xxd -r -p /boot-log.txt >> /boot.log
rm /log.txt
rm /boot-log.txt

Makes checking /boot.log more sensible.

[shiecldk]

It showed "There is a problem with TSC detection and calibration! Assume calibrated one" before getting into the harddrive-selecting screen.
How can I do to fix this error?
I remember it didn't have this problem when I was using Clover r718.

I'm using r732 now.

[e60]

@kyndder

Quote

Did you have SBUS fix on your DSDT???

If yes, did you already tried to wake your machine using the power button instead of moving the mouse or pressing some keyboard key???

Yes, I have. I'm only able to wake my computer from sleep using power button. Pressing keybord keys won't work for me in Clover.


@Slice

Quote

Yes, it is DSDT related. Why you need your quirky DSDT if without it "all works fine"?

Thank you for the info. Why do I need my DSDT ... this is a good question! My "old" machine wasn't able to boot without DSDT and editing DSDT brought me some benefits, so I decided to create a DSDT for my new machine.

I guess I'll have to check whats wrong with my edits and meanwhile work without DSDT. But my primary goal is to get Clover booting with UEFI.

[kyndder]

e60, on 06 October 2012 - 05:43 PM, said:

I'm only able to wake my computer from sleep using power button. Pressing keybord keys won't work for me in Clover.

For me works the same way... I really don't know if there's a fix for this... In true, I do not usually use sleep function...

Why you don't give a try (if you already not) to Clover's automatic DSDT fix ??? >             #7      

But Slice is right, if you have everything working fine without DSDT, you should not use it...

About Clover's direct UEFI boot I can't tell you anything, you will have to wait till someone with the needed
knowledge to answer...

[Slice]

shiecldk, on 06 October 2012 - 04:55 PM, said:

It showed "There is a problem with TSC detection and calibration! Assume calibrated one" before getting into the harddrive-selecting screen.
How can I do to fix this error?
I remember it didn't have this problem when I was using Clover r718.

I'm using r732 now.

This is a bug but not influence on functionality. Hope will be resolved soon.

[STLVNUB]

So what is wrong with ProjectOSX site??
Seems to be getting harder to access.