Jump to content

Clover General discussion


ErmaC
29,866 posts in this topic

Recommended Posts

Hi everyone,

I have successful use the EFI partition with Fusion drive and UEFI MB but, I can't boot with UEFI mode :( It stuck with this:

741359IMG0064.jpg

I juste have to reboot.

Have you an idea?

In EFI mode, nothing! just boot like a charm :(

 

EDIT: Problem solved

Link to comment
Share on other sites

You must install manually depend on what disk or stick you are using

 

BootSectors:

boot0

boot0hfs

boot0md

boot1altV2

boot1f32

boot1f32alt

boot1h

boot1h2

fdisk440

 

boot0 - MBR sector that search for active partition in MBR table. Origin from Apple's boot132 project. This version of boot0 implements hybrid GUID/MBR partition scheme support. Written by TamΓ΅s KosΓ΅rszky on 2008-03-10

 

boot0hfs - MBR sector that search for HFS+ partition even thou it is not active. Good for Windows that wants to have its partition active. (origin?)

 

boot0md - MBR sector that search for active HFS+ partiton on all disks. Modified by dmazar.

 

boot1h - PBR sector for HFS+ formatted partition. Search for file "boot" in the root of the partiton. Origin from Apple's boot132 project. Written by TamΓ΅s KosΓ΅rszky on 2008-04-14. This is mod by Slice to support large boot file. Not 440kb as origin but 472k needed to boot Clover-64.

 

boot1h2 - PBR sector for HFS+ formatted partition with alternative booting with choice of key pressed. File to boot = "boot{key}". Coded by dmazar based on boot1h.

 

boot1altV2 - same but "This boots Chameleon if 'c' pressed OR boot3 if '3' pressed, any other key OR timeout boot6." - modded by STLVNUB.

 

boot1f32 - PBR sector for FAT32 formatted partition. Search for file "boot" in the root of the partiton. Useful for EFI partition or USB stick. Written by mackerintel on 2009-01-26.

 

boot1f32alt - PBR sector for FAT32 formatted partition with alternative booting with choice of key pressed. File to boot = "boot{key}". Modded by Slice based on

boot1f32 and boot1h2.

 

Thinking about it a 2nd time, i'd say manual installation changes nothing ! Tried it and still there's waiting time.

I'm pretty sure ( n00b as i am :wink2: ) that there needs to be changed sth in boot1h (?)... But i have no idea how to do that.

 

Maybe one of the devs can help here please.

Link to comment
Share on other sites

Thinking about it a 2nd time, i'd say manual installation changes nothing ! Tried it and still there's waiting time.

I'm pretty sure ( n00b as i am :wink2: ) that there needs to be changed sth in boot1h (?)... But i have no idea how to do that.

 

Maybe one of the devs can help here please.

Basically,

Please do DarwinDump with all Disk*** reports selected and then we could tell more.

Link to comment
Share on other sites

@polkaholga, you have Chameleon (/boot1) and Clover (/boot) installed to your SSD disk EFI partition (HFS+ formatted?). Partition booter (PBR) is Clover's boot1h2 which waits for 2 seconds and gives you ability to boot Chameleon (by pressing 1 to start /boot1) or Clover (not pressing anything to start /boot).

 

You can install Clover's version of boot1h (here) to PBR of that EFI partition and that one will start /boot and will not wait for 2 seconds any more. But that also means that you will not be able to select between Chameleon and Clover.

Link to comment
Share on other sites

@polkaholga, you have Chameleon (/boot1) and Clover (/boot) installed to your SSD disk EFI partition (HFS+ formatted?). Partition booter (PBR) is Clover's boot1h2 which waits for 2 seconds and gives you ability to boot Chameleon (by pressing 1 to start /boot1) or Clover (not pressing anything to start /boot).

 

You can install Clover's version of boot1h (here) to PBR of that EFI partition and that one will start /boot and will not wait for 2 seconds any more. But that also means that you will not be able to select between Chameleon and Clover.

 

I tried it with that boot1h as i mentioned in my previous post ( sorry for not being clear ) and because i couldn't see any difference while booting i thought about that sth maybe needs to be

changed... :unsure:

 

 

By the way found sth odd in boot.log compared to older one.

 

r944 ➔ 8:613 0:000 Turbo: 36/38/38/39

r1059 ➔ 7:775 0:000 Turbo: 36/12/12/39

 

...and a new message i have not seen before ➔ 11:882 0:000 Error! Xsdt is not found!!! Creating new one

Link to comment
Share on other sites

REAL Apple Hardware tested again;-)

 

*MacPro 2.1

-Software TestCase 1:clover 1000 biosmode

-Hardware:mp2.1 16GB both risers 4x2GB, 2x XEON 5365 and ATI 5770, expension cards=esata, usb2/fw800

 

Version 1000 of clover efi finally makes the macpro 2.1 run Mountain Lion 10.8.2, without any patched DSDT and default bootloader settings except for SMBIOS MacPro3.1, GraphicsInjection for ATI/AMD 5770 must be set to Hoolock with native monitor resolution in refit.conf and HDAInjection must be set layout id 12 accompanied with the DSDTmask setting for HDA fix.

 

By default Clover injects the wrong Framebuffer for the Apple ATI5770 and when HDAInjection is also on auto it detects both alc885 and hdmi audio but none work.

 

What still won't work is "shutdown", it always ends in a restart just like the chameleon bootloader did. Geekbench speed and performance is fine so the machine is almost usable!

 

-Software TestCase 2:clover 1000 AppleEFI mode with modified RefiT

-Hardware:idem

 

Using the simple howto to replace refit by clover on realmac's I was able to boot clover on the MacPro2.1 only with the CLOVERIA32.efi not the CLOVERX64.efi. The clover GUI looks fine on native resolution and mouse also works. The machine runs SnowLeopard with the Clover Bootloader fine with default settings used (all patching disabled). No need for FakeSMC.kext in this mode because it uses the Apple Hardware in its own EFI mode. When not changing SMBIOS it will show Imac in about this Mac. But the needed 64 bit mode boot doesn't show up as selectable in the popup menu of clover so Mountain Lion won't even start booting.

 

*MacBookPro 3.1/5.1

-Software Testcase 1:clover 1000 efi mode

-Hardware:both both machines have 4GB ram, MBP5.1 uses two videocards

 

Doing the same replace trick for refit, these machines only boot the CLOVERX64.efi. The bootloader GUI shows fine in native Resolution and mouse works properly, booting a OS for instance Snow Leopard or Mountain Lion it will also show booting in 64 bit modes beside 32bit (MacPro didn't do this). Both modes work for both OS on both devices. Funny thing is, clover indeed detects two video card to inject on the MacBookPro 5.1.

 

What info do we need to get clover EFI 64 boot working on the MacPro 2.1 32 bit efi mode, and wath is needed to make shutdown work in bios mode. Does it has something to do that clover only shows one XEON with 4 cores?

Link to comment
Share on other sites

About shutdown fix. Did you change Reset registers?

 <key>ResetAddress</key>
 <string>0x0CF9</string>
 <key>ResetValue</key>
 <string>0x06</string>

It also depends on Mac model.

 

About 64 bit.

EFI32 -> CloverIA32.efi

EFI64 -> CloverX64.efi

If you want to replace your EFI32 by CloverEFI64 then you should start legacy boot to Clover. BootCamp?

 

And about AMD HD5770 tell me your DeviceID and I change default framebuffer to Hoolock


 { 0x68A0, 0x00000000, CHIP_FAMILY_JUNIPER, "ATI Radeon HD 5770 Series",  kHoolock },
 { 0x68A1, 0x00000000, CHIP_FAMILY_JUNIPER, "ATI Radeon HD 5850 Series",  kHoolock },
 { 0x68A8, 0x00000000, CHIP_FAMILY_JUNIPER, "ATI Radeon HD 5770 Series",  kHoolock },

Link to comment
Share on other sites

how do I put this efi string in the config file of Colver?

 

<key>device-properties</key>
<string>7f0000000100000001000000730000000200000002010c00d041030a000000000101060000027fff04002c0000004100410050004c002c00690067002d0070006c006100740066006f0072006d002d006900640000000800000003006601140000006800640061002d0067006600780000000d0000006f6e626f6172642d31</string>

Link to comment
Share on other sites

how do I put this efi string in the config file of Colver?

 

<key>device-properties</key>
<string>7f0000000100000001000000730000000200000002010c00d041030a000000000101060000027fff04002c0000004100410050004c002c00690067002d0070006c006100740066006f0072006d002d006900640000000800000003006601140000006800640061002d0067006600780000000d0000006f6e626f6172642d31</string>

There's another thread with more information about Clover's configuration and installation. There you'll find your answer.

Link to comment
Share on other sites

Developers, you should inform that leaving empty strings in the config.plist may lead to strange issues, like the FIXME error in the console when boot-args is empty (there was another similar issue I can't recall). Don't know if this affects any other string but it is safer to delete them instead of leaving them empty.

Link to comment
Share on other sites

Hi Slice

 

Is there a way to enable DualLink using clover?

 

aka

 

"AAPL00,DualLink",
Buffer (0x04)
{
0x01, 0x00, 0x00, 0x00

Sorry, it is not documented yet

<key>Graphics</key>
<dict>
 <key>GraphicsInjector</key>
 <string>Yes</string>
 <key>DualLink</key>
 <string>1</string>

  • Like 1
Link to comment
Share on other sites

how do I put this efi string in the config file of Colver?

 

<key>device-properties</key>
<string>7f0000000100000001000000730000000200000002010c00d041030a000000000101060000027fff04002c0000004100410050004c002c00690067002d0070006c006100740066006f0072006d002d006900640000000800000003006601140000006800640061002d0067006600780000000d0000006f6e626f6172642d31</string>

Link to comment
Share on other sites

how do I put this efi string in the config file of Colver?

 

<key>device-properties</key>
<string>7f0000000100000001000000730000000200000002010c00d041030a000000000101060000027fff04002c0000004100410050004c002c00690067002d0070006c006100740066006f0072006d002d006900640000000800000003006601140000006800640061002d0067006600780000000d0000006f6e626f6172642d31</string>

<key>PCI</key>
<dict>
 <key>StringInjector</key>
 <string>Yes</string>
 <key>DeviceProperties</key>
 <string>7f0000000100000001000000730000000200000002010c00d041030a000000000101060000027fff04002c0000004100410050004c002c00690067002d0070006c006100740066006f0072006d002d006900640000000800000003006601140000006800640061002d0067006600780000000d0000006f6e626f6172642d31</string>

  • Like 1
Link to comment
Share on other sites

Updated: subsys id ATI5770

 

About shutdown fix. Did you change Reset registers?

<key>ResetAddress</key>
<string>0x0CF9</string>
<key>ResetValue</key>
<string>0x06</string>

It also depends on Mac model.

 

I haven't set the ResetRegisters, so clover is autopatching them to 0x64 and 0xFE? (didn't knew that was auto patched by default). Currently looking at the FACP from the darwindump running in native efi mode indeed shows the values you just advised being 0x0CF9 0x06. I will try them as soon as possible. Thanks for pointing in this direction.

 

About 64 bit.

EFI32 -> CloverIA32.efi

EFI64 -> CloverX64.efi

If you want to replace your EFI32 by CloverEFI64 then you should start legacy boot to Clover. BootCamp?

CloverX64 is indeed already working in BootCamp which I revered as Bios-mode. In native EFI mode it will not start Cloverx64. Is there no way of letting the native Apple EFI32 transform into a CloverX64 EFI? The Lion Boot.efi can load the Mountain Lion 10.8 kernel in 64bit but has a 8GB ram limit? Also EFI booting is so much faster ;-)

 

Also Refit uses a single EFI file on a USB-stick which makes one single USB-stick bootable on both 32 and 64 capable efi Mac's without changing files or folder names. With the "rEFIt > clover transform" a single USB-stick will only work on a 32 or 64 bit efi system depending on which file was renamed. Can this also be made automated? So if the bootloader detects 32 bit EFI Mac's it will use CLOVERIA32 and if it detects 64bits efi Mac's it will use CLOVERX64.efi this make it a fully capable rEFIt replacement.

 

And about AMD HD5770 tell me your DeviceID and I change default framebuffer to Hoolock


{ 0x68A0, 0x00000000, CHIP_FAMILY_JUNIPER, "ATI Radeon HD 5770 Series", kHoolock },
{ 0x68A1, 0x00000000, CHIP_FAMILY_JUNIPER, "ATI Radeon HD 5850 Series", kHoolock },
{ 0x68A8, 0x00000000, CHIP_FAMILY_JUNIPER, "ATI Radeon HD 5770 Series", kHoolock },

 

The PCI-id is 1002:68b8 subsys 106B:00CF, it is the real Apple 5770 1024MB ATI card with 2x minidisplay port and 1x DVI-D, it uses Hoolock but clover autodetects a different FB and therefor not all ports work correctly but with Hoolock it does.

Link to comment
Share on other sites

Mine is also an ATI HD5770 1002:68b8 but uses Vervet instead of Hoolock. What you need to differentiate the model is the subsys (1682:2991 in my case) It should be listed in clover's boot log like this:

11:885  0:000  ATI Juniper ATI Radeon HD 5770 Series -1MB (Vervet) [1002:68B8] (subsys [1682:2991]):: PcieRoot(0x0)/Pci(0x1,0x0)/Pci(0x0,0x0)

 

And yes, its lacking some memory :P

Link to comment
Share on other sites

hello @slice

 

only to report that the custom edid is working with my amd 5470m, last versions resolve the issue.

 

no more need to inject the edid in file in s/l/d/o

 

thanks for u great job with Clover

 

good hack

Link to comment
Share on other sites

<key>PCI</key>
<dict>
<key>StringInjector</key>
<string>Yes</string>
<key>DeviceProperties</key>
<string>7f0000000100000001000000730000000200000002010c00d041030a000000000101060000027fff04002c0000004100410050004c002c00690067002d0070006c006100740066006f0072006d002d006900640000000800000003006601140000006800640061002d0067006600780000000d0000006f6e626f6172642d31</string>

 

Thanks

Link to comment
Share on other sites

Sorry, it is not documented yet

<key>Graphics</key>
<dict>
<key>GraphicsInjector</key>
<string>Yes</string>
<key>DualLink</key>
<string>1</string>

Thank You for the info but this doesn't seems to work.

Is there a way to check if Clover is actually triggering the DualLink=1?

In EFI/misc/system.log I can only see:

...
86:859 0:183 EdidDiscovered size=0
87:079 0:219 Intel Intel HD Graphics 3000 [8086:0126] :: PciRoot(0x0)/Pci(0x2,0x0)
87:225 0:146 Intel GFX revision =0x9
...

I'm using Clover ver 1050

Link to comment
Share on other sites

Thank You for the info but this doesn't seems to work.

Is there a way to check if Clover is actually triggering the DualLink=1?

 

You may check with IORegistryExplorer:

 

post-158318-0-92361200-1359465598_thumb.png

 

EDIT: By the way, I don't inject the key so yours may differ from mine.

  • Like 1
Link to comment
Share on other sites

×
×
  • Create New...