Jump to content

Clover General discussion

ErmaC

By ErmaC,
in Clover

 Share
30,171 posts in this topic

Recommended Posts

Riley Freeman
Riley Freeman
Posted
Posted

After another restart hang on the X79 I decided to try legacy Clover instead. Again the installer failed when I told it to install to the EFI partition (when I unchecked this it installed fine, putting the EFI folder on the drive root). But I want it installed to the EFI partition.

 

This time I have Mavericks installed on a second (removable) disk so I booted that and ran the installer with my Snow Leopard disk as the destination. That worked fine. I'm assuming that means there's nothing wrong with my disk config, but yet again the installer failed to find/mount the EFI partition in 10.6.8.

Link to comment
Share on other sites
magnifico
magnifico
Posted
Posted

After another restart hang on the X79 I decided to try legacy Clover instead. Again the installer failed when I told it to install to the EFI partition (when I unchecked this it installed fine, putting the EFI folder on the drive root). But I want it installed to the EFI partition.

 

This time I have Mavericks installed on a second (removable) disk so I booted that and ran the installer with my Snow Leopard disk as the destination. That worked fine. I'm assuming that means there's nothing wrong with my disk config, but yet again the installer failed to find/mount the EFI partition in 10.6.8.

 

maybe I'm saying something stupid, but I think that the bug is not on bios x79, maybe developers will investigate this issue on this chipset, the problem for me is not hardware but it will be something in the UEFI driver ...

 

 

Ps: friend relax .....I do not I'm worried most of the restart, if it works well or not, but who cares ..... I realized that after all this time that hackintosh and 'only a game to waste time.it is time to buy a real Mac.....ahhahahahah

Link to comment
Share on other sites
magnifico
magnifico
Posted
Posted

Hi slice..please.

I have a little question for you...now i am on legacy mode clover.

1) if press on keyboard F2 for boot log in MISC folder i don see this in folder .

2) if set debug log on yes in configplist , also here i dont see in MISC folder.

 

This is a normal in legacy mode ?

OMG ....my english dont is Chinese ....

Link to comment
Share on other sites
slayer2333
slayer2333
Posted
Posted

Hi Everyone, i installed 10.8.5 on my Haswell Laptop (4700MQ, 780m GTX + Intel HD 4600 optimus). So far i could get it working 100% (full acceleration) using chameleon (without DSDT, GraphicsEnabler=Yes and IntelAzulFB=11 ) but when i switched to UEFI boot with clover i am stuck at boot logo and i am not very experiencing with it.

Tried with gfxutil to run the command gfxutil -i xml -o hex device-properties.plist device-properties.hex to generate a file .hex in the user folder then copied the generated key from file .hex to config.plist but still a no-go.

Removed the graphic kexts to confirm that it is the source of the problem, and yes i could boot without them.

Attached  my config.plist for clover can anyone please give me a hand on this?

<?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>ACPI</key>
	<dict>
		<key>DSDT</key>
		<dict>
			<key>FixMask</key>
			<string>0xFFFF</string>
			<key>Name</key>
			<string>DSDT.aml</string>
			<key>ReuseFFFF</key>
			<false/>
		</dict>
		<key>DropTables</key>
		<array>
			<dict>
				<key>Signature</key>
				<string>DMAR</string>
			</dict>
		</array>
	</dict>
	<key>Boot</key>
	<dict>
		<key>Arguments</key>
		<string>Kernel=mach_kernel -v</string>
		<key>DefaultVolume</key>
		<string>MacHDD</string>
		<key>Legacy</key>
		<string>PBR</string>
		<key>Timeout</key>
		<integer>5</integer>
		<key>XMPDetection</key>
		<string>No</string>
	</dict>
	<key>Devices</key>
	<dict>
		<key>Inject</key>
		<true/>
		<key>Properties</key>
		<string>5e0000000100000001000000520000000100000002010c00d041030a000000000101060000027fff04002c0000004100410050004c002c00690067002d0070006c006100740066006f0072006d002d00690064000000080000000a260005</string>
	</dict>
	<key>DisableDrivers</key>
	<array>
		<string>Nothing</string>
	</array>
	<key>GUI</key>
	<dict>
		<key>DebugLog</key>
		<false/>
		<key>DefaultBootVolume</key>
		<string>SnowHD</string>
		<key>Hide</key>
		<array>
			<string>Windows</string>
			<string>\EFI\BOOT\BOOTX64.EFI</string>
		</array>
		<key>Language</key>
		<string>en:0</string>
		<key>Mouse</key>
		<dict>
			<key>Enabled</key>
			<false/>
		</dict>
		<key>Scan</key>
		<dict>
			<key>Entries</key>
			<true/>
			<key>Legacy</key>
			<string>First</string>
			<key>Tool</key>
			<true/>
		</dict>
		<key>ScreenResolution</key>
		<string>1920x1080</string>
		<key>Theme</key>
		<string>metal</string>
		<key>Timeout</key>
		<integer>5</integer>
	</dict>
	<key>Graphics</key>
	<dict>
		<key>Inject</key>
		<dict>
			<key>Intel</key>
			<true/>
		</dict>
		<key>InjectEDID</key>
		<true/>
	</dict>
	<key>KernelAndKextPatches</key>
	<dict>
		<key>AppleRTC</key>
		<true/>
	</dict>
	<key>RtVariables</key>
	<dict>
		<key>LogEveryBoot</key>
		<string>10</string>
		<key>LogLineCount</key>
		<integer>3000</integer>
		<key>MountEFI</key>
		<true/>
	</dict>
	<key>SMBIOS</key>
	<dict>
		<key>BiosReleaseDate</key>
		<string>10/23/12</string>
		<key>BiosVendor</key>
		<string>Apple Inc.</string>
		<key>BiosVersion</key>
		<string>MM61.88Z.0106.B00.1208091121</string>
		<key>Board-ID</key>
		<string>Mac-F65AE981FFA204ED</string>
		<key>BoardSerialNumber</key>
		<string>C02LL732DWYN</string>
		<key>ChassisManufacturer</key>
		<string>Apple Inc.</string>
		<key>Family</key>
		<string>Mac mini</string>
		<key>Manufacturer</key>
		<string>Apple Inc.</string>
		<key>ProductName</key>
		<string>Macmini6,2</string>
		<key>SerialNumber</key>
		<string>C02LL732DWYN</string>
		<key>Version</key>
		<string>1.0</string>
	</dict>
	<key>SystemParameters</key>
	<dict>
		<key>InjectSystemID</key>
		<true/>
		<key>LegacyBoot</key>
		<string>PBR</string>
	</dict>
</dict>
</plist>
Also attached my Ioreg on the working boot (with Chameleon).
Link to comment
Share on other sites
Slice
Slice
Posted
Posted

Sorry, can't get your attachment (seems to be forum problem).

Try to use most recent Clover. If you can then compile revision 2109.

And make more detailed report, upload it to external server.

Link to comment
Share on other sites
slayer2333
slayer2333
Posted
Posted

Sorry, can't get your attachment (seems to be forum problem).

Try to use most recent Clover. If you can then compile revision 2109.

And make more detailed report, upload it to external server.

Sorry, here's the ioreg from an external link: https://mega.co.nz/#!opsSzDYS!QqbvZ1yyJbGLI2hKYlxuoFIGX-gk2eHd-TwznECApRs

Been using Clover 2082 so far.

When you say more detailed report do you mean a log of my verbose mode for example? If so will attached once back home.

Thank you in advance!!

Link to comment
Share on other sites
Slice
Slice
Posted
Posted

Hi slice..please.

I have a little question for you...now i am on legacy mode clover.

1) if press on keyboard F2 for boot log in MISC folder i don see this in folder .

2) if set debug log on yes in configplist , also here i dont see in MISC folder.

 

This is a normal in legacy mode ?

OMG ....my english dont is Chinese ....

misc folder must be located on FAT32 volume. It is only condition for success.

If you can boot into system then you can save DarwinDump.

 

 

 

Sorry, here's the ioreg from an external link: https://mega.co.nz/#!opsSzDYS!QqbvZ1yyJbGLI2hKYlxuoFIGX-gk2eHd-TwznECApRs

Been using Clover 2082 so far.

When you say more detailed report do you mean a log of my verbose mode for example? If so will attached once back home.

Thank you in advance!!

OK, I got your ioreg and will think what is the problem.

I think you should update Clover and use the follow settings in config.plist

	<key>Graphics</key>
	<dict>
		<key>Inject</key>
		<dict>
			<key>Intel</key>
			<true/>
			<key>ATI</key>
			<false/>
			<key>NVidia</key>
			<false/>
		</dict>

		<key>ig-platform-id</key>
		<string>0x0a260005</string>

	</dict>
	<key>Devices</key>
	<dict>
		<key>Inject</key>
		<false/>
Link to comment
Share on other sites
slayer2333
slayer2333
Posted
Posted

 

misc folder must be located on FAT32 volume. It is only condition for success.

If you can boot into system then you can save DarwinDump.

 

 

 

OK, I got your ioreg and will think what is the problem.

I think you should update Clover and use the follow settings in config.plist

	<key>Graphics</key>
	<dict>
		<key>Inject</key>
		<dict>
			<key>Intel</key>
			<true/>
			<key>ATI</key>
			<false/>
			<key>NVidia</key>
			<false/>
		</dict>

		<key>ig-platform-id</key>
		<string>0x0a260005</string>

	</dict>
	<key>Devices</key>
	<dict>
		<key>Inject</key>
		<false/>

Thank you Slice, will give it a shot tonight and report back.

Link to comment
Share on other sites
jamiethemorris
jamiethemorris
Posted
Posted

I have a couple of questions, last time I used clover I could not get shutdown to work properly. Works fine with chameleon though. Do I just need to do #4 in "patch dsdt to get sleep working properly" for this to work? Also to update clover do I need to run clovergrower or can I just run the installer? I'm using a fusion drive with gigabyte's uefi bios.

Link to comment
Share on other sites
joace
joace
Posted
Posted

Hi Genius,

 

     I think i must need your help now. I'm trying the latest Clover (v2082)  to install and boot may Mountain Lion 10.8.4 on my HP Elitebook 8460p, but i have been stuck at installation for a while, below is some basic info about my hackintosh, can someone do me a favor? Thanks!

1. Laptop model: HP Elitebook 8460p, BIOS ver: F42, EFI boot enabled, i always boot from EFI file, then locate bootx64.efi on U disk generated by Clover package;

2. Hard disk: GPT partitioned, 1 for OS X, another for Windows (but not installed);

3. My installation U disk: InstallESD.dmg restored in Lion, without any modification;

4. Installation steps:

    a. Boot from U disk, skip cache and with Kexts (FakeSMC, NullCPU, PS2....);

    b. Partition HD;

    c. Fresh install to OSX partition (1st stage);

    d. After reboot, still boot from U disk, but switch to HD Mountain Lion just now installed;

    e. Stuck here, in -v mode, the last two messages are:

        Sound assertion in AppleHDAController at line 1294

        Waiting for DSMOS.......

 

I patched my DSDT and SSDT, but even I removed them, the result is still the same as above. I also attached my config.plist, please help me to take a look, is something wrong?

God save me!

config.zip

Link to comment
Share on other sites
Slice
Slice
Posted
Posted

Looks like it's because FakeSMC.kext not loaded, as I didn't find any message in log. And kext injection is disabled by Clover regularly, should put kexts in to S/L/E. Need to have a try.

You should place FakeSMC.kext into /kexts/Other because of a bug that corrected in revisions 2103..2110, not sure.

I have a couple of questions, last time I used clover I could not get shutdown to work properly. Works fine with chameleon though. Do I just need to do #4 in "patch dsdt to get sleep working properly" for this to work? Also to update clover do I need to run clovergrower or can I just run the installer? I'm using a fusion drive with gigabyte's uefi bios.

If you boot with legacy CloverEFI then the shutdown will work. It is AMI UEFI problem.

For update you may use installer.

  • Like 1
Link to comment
Share on other sites
jamiethemorris
jamiethemorris
Posted
Posted

If you boot with legacy CloverEFI then the shutdown will work. It is AMI UEFI problem.

For update you may use installer.

does that mean that any os booted via uefi will have that problem? Uefi is the main reason I wanted to use clover. Any other workaround, a bios patch or anything like that?

 

Edit: it's amazing what a little searching can find you... Apparently there's no solution yet. I also recall having problems with audio glitches that were specific to clover, anyone else?

Link to comment
Share on other sites
Slice
Slice
Posted
Posted

Ok working now, thank you very much Slice. Just a question, was it a problem of the bootloader itself or an error in injecting the graphic card?

 

Both. You have new hardware that I registered in new revision. And I didn't check carefully how did you made injection but looks to be not exactly as Clover did.

does that mean that any os booted via uefi will have that problem? Uefi is the main reason I wanted to use clover. Any other workaround, a bios patch or anything like that? Edit: it's amazing what a little searching can find you... Apparently there's no solution yet. I also recall having problems with audio glitches that were specific to clover, anyone else?

All computers manufacturers (except Apple) tune his hardware and BIOS to use with Windows. You agree?

Dmazar made a huge work to do UEFI booting to OSX. It was impossible without dmazar's effort. UEFI is not initially reliable to boot OSX. Axioma.

He corrected memory map and some adjusting in the whole process of OSX boot so that UEFI boot becomes possible. But it is still non-correct process.

Do you want to say Clover is bad bootloader? (audio glitches etc.) If we come to challenge then I can show you numerous glitches of other boot loader that already resolved in Clover. It is the best boot loader in the world. Just some problems exists:

1. Not all hardware will do legacy boot to WindowsXP from Clover. It's my bad, I just still can't over jump this problem.

2. Booting by UEFI you may have non-stable sleep/shutdown. The question is hot. Booting by CloverEFI all is fine.

Link to comment
Share on other sites
magnifico
magnifico
Posted
Posted

Both. You have new hardware that I registered in new revision. And I didn't check carefully how did you made injection but looks to be not exactly as Clover did.

 

All computers manufacturers (except Apple) tune his hardware and BIOS to use with Windows. You agree?

Dmazar made a huge work to do UEFI booting to OSX. It was impossible without dmazar's effort. UEFI is not initially reliable to boot OSX. Axioma.

He corrected memory map and some adjusting in the whole process of OSX boot so that UEFI boot becomes possible. But it is still non-correct process.

Do you want to say Clover is bad bootloader? (audio glitches etc.) If we come to challenge then I can show you numerous glitches of other boot loader that already resolved in Clover. It is the best boot loader in the world. Just some problems exists:

1. Not all hardware will do legacy boot to WindowsXP from Clover. It's my bad, I just still can't over jump this problem.

2. Booting by UEFI you may have non-stable sleep/shutdown. The question is hot. Booting by CloverEFI all is fine.

are flat agree with you, dmazar and 'a great developer, in fact it was he long ago to explain to me step by step how to install clover in UEFI mode, and it' been a great help to this wonderful project, but you are also a large, just that sometimes I do stress a lot .... hahaha

 

I tried both chamaleon that enoch boot, but I noticed a big difference between these boot loader in legacy mode, for me clover and 'fantastic ... I was going to try it Ozmosis, but it is to me a very foolish boot.

 

Ozmosis it is a for girl ....

Link to comment
Share on other sites
ameris_cyning
ameris_cyning
Posted
Posted

Slice, if I may be so bold to say this, it may be wise to bring Clover to the mainstream. We Hackintosh users are the only ones who are benefiting from this great boot loader. If Clover could transition to a more generic boot loader instead of focusing on us, we may be able to bring in other programmers to work on it, and some of them may actually trickle into our community.

Link to comment
Share on other sites
jamiethemorris
jamiethemorris
Posted
Posted

Both. You have new hardware that I registered in new revision. And I didn't check carefully how did you made injection but looks to be not exactly as Clover did.

All computers manufacturers (except Apple) tune his hardware and BIOS to use with Windows. You agree?

Dmazar made a huge work to do UEFI booting to OSX. It was impossible without dmazar's effort. UEFI is not initially reliable to boot OSX. Axioma.

He corrected memory map and some adjusting in the whole process of OSX boot so that UEFI boot becomes possible. But it is still non-correct process.

Do you want to say Clover is bad bootloader? (audio glitches etc.) If we come to challenge then I can show you numerous glitches of other boot loader that already resolved in Clover. It is the best boot loader in the world. Just some problems exists:

1. Not all hardware will do legacy boot to WindowsXP from Clover. It's my bad, I just still can't over jump this problem.

2. Booting by UEFI you may have non-stable sleep/shutdown. The question is hot. Booting by CloverEFI all is fine.

My intent was not to imply that clover is a bad bootloader, i love it on my x202e and i agree it is the best bootloader available. I was simply asking if anyone else had audio problems in hopes that someone else with that problem would have a solution. I realize chameleon has it's own issues as well. What are the drawbacks of cloverefi vs true uefi? Any?
Link to comment
Share on other sites
 Share
Go to topic listing
×
×
  • Create New...