Jump to content

Clover General discussion

ErmaC

By ErmaC,
in Clover

 Share
29,866 posts in this topic

Recommended Posts

Slice
Slice
Posted
Posted

If that is the "Exit Clover" button, all it does is throw me to a black screen till I manually reset. I'm booted with CSM disabled and secure boot disabled. If that is a dedicated "Reboot into Firmware" button I do not have it o.o I checked the clover revisions at sourceforge and didn't see any commit after my currently installed revision about adding that feature. I'm running 3320 installed from the official package on sourceforge. I know my system supports OsIndications since A. Windows uses it fine and B. manually setting it in OS X via "sudo nvram 8BE4DF61-93CA-11D2-AA0D-00E098032B8C:OsIndications=%01%00%00%00%00%00%00%00 && sudo reboot" reboots into my UEFI setup properly. I see EFI_OS_INDICATIONS_BOOT_TO_FW_UI ​referenced in OsxDxeCore, however I didn't take the time to trace it back extensively and I didn't see how it could be connected to the "Exit Clover" button(I only looked for like 5 minutes, you know your source better than I could glean in a short amount of time :P).

preboot.log:

https://gist.github.com/winsock/2ff689f810b141e68fec

In the case of legacy boot when loading DUET first and then CloverX64.efi this button will exit CloverX64.efi and return to DUET. It is real EFI "firmware".

But in the case of UEFI boot it doesn't happen, just black screen. We have no sources of a UEFI firmware and nobody made debug of this.

I can do something like set the variable and then reboot instead of exit. Moreover, Clover knows if it is legacy boot (then exit) or it is UEFI boot (then restart).

Link to comment
Share on other sites
D-an-W
D-an-W
Posted
Posted

Thanks Chris, did you use CGP to build? I use it with that modified file you posted a few days ago to fix the error I was getting.

 

Is it all down to the Clover.prefPane, mine is 923 KB could you perhaps share yours so I can test with it?

Link to comment
Share on other sites
chris1111
chris1111
Posted
Posted

Thanks Chris, did you use CGP to build? I use it with that modified file you posted a few days ago to fix the error I was getting.

 

Is it all down to the Clover.prefPane, mine is 923 KB could you perhaps share yours so I can test with it?

See your PM

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

Slice, I got a little problem here. My friend has an audio interface that only works with Snow Leopard, but he has a Haswell computer. I compiled one mach_kernel with the necessary changes to works with Haswell CPU. With Chameleon works perfect, but when we tried to boot with clover instantly get a kernel panic.

Link to comment
Share on other sites
Slice
Slice
Posted
Posted

Slice, I got a little problem here. My friend has an audio interface that only works with Snow Leopard, but he has a Haswell computer. I compiled one mach_kernel with the necessary changes to works with Haswell CPU. With Chameleon works perfect, but when we tried to boot with clover instantly get a kernel panic.

Your message doesn't contain an information about the reason of the problem. Clover works with Haswell computers.

Link to comment
Share on other sites
liujianwei
liujianwei
Posted
Posted

Slice, I got a little problem here. My friend has an audio interface that only works with Snow Leopard, but he has a Haswell computer. I compiled one mach_kernel with the necessary changes to works with Haswell CPU. With Chameleon works perfect, but when we tried to boot with clover instantly get a kernel panic.

You could install Disabler.kext from Chameleon when you use Clover,weirdly I have installed Disabler.kext and I still see power management activity through HWMonitor,maybe it's illusion?

Link to comment
Share on other sites
chris1111
chris1111
Posted
Posted

Slice I am really happy and surprise of my Beast ; my DELL Precision 690 Workstation  the rigs in my sign

 

I have buying two adaptor last week PATA to SATA 

from the web; today I receive my package

hot-se10.jpg

I order this because I don't used the PATA connection  for my DVD Whiter

I put my DVD on SATA port and today I connect my Internal windows 10 drive

to the Pata  connector

OS X  have a great support for PATA :P  :lol:

00010.png

 

 end big surprise thats boot perfect on Windows 10 from Clover ESP menu  :D

No f12 for entering in Windows :hysterical:

 

Edit today***

But its Slow start up Windows SH..... !

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

I would like to make an official public request to Slice's team, that developed the great boot loader that we all know as Clover.

We all love their work, and it's thanks to them that we can do what we do in a much easier and reliable way.

I have three different requests in mind at this time for the team, and it's things that I've noticed that could improve this piece of software by a lot:

 

1st. Maybe we could have a section in Clover Configurator for AMD builds, and AMD processors. Just like we patch the kernel on the fly for locked MSR we could maybe patch it for AMD support, taking knowledge of the amazing AMD forums we have here.

 

2nd. Wouldn't it be nicer to have simply a black or white screen in Clover entry, instead of that little ugly font text saying

"Welcome to Clover.. rev 3338" before the Clover Gui begins?

 

3rd. Could we figure out why can't we on a Hackintosh with El Capitan or Yosemite get the Grey on Grey apple logo at start up to work properly like it does in a Mac, even with kext patches on the fly being used and fixes tried but it doesn't work ok with Custom Logo: Apple ,instead of the white on black one that works perfectly when applying one little fix?

 

I feel everyone should be free to speak their mind, and even if no-one is here to listen, i spoke my mind.

thanks for all your work Clover devs.. ;)

Link to comment
Share on other sites
RehabMan
RehabMan
Posted
Posted

2nd. Wouldn't it be nicer to have simply a black or white screen in Clover entry, instead of that little ugly font text saying

"Welcome to Clover.. rev 3338" before the Clover Gui begins?

config.plist/Boot/NoEarlyProgress=true.

  • Like 3
Link to comment
Share on other sites
mhaeuser
mhaeuser
Posted
Posted

1st. Maybe we could have a section in Clover Configurator for AMD builds, and AMD processors. Just like we patch the kernel on the fly for locked MSR we could maybe patch it for AMD support, taking knowledge of the amazing AMD forums we have here.

 

Clover Configurator is developed by another team and it's closed source. Also, AMD support is not patching the kernel, but replacing it.

 

3rd. Could we figure out why can't we on a Hackintosh with El Capitan or Yosemite get the Grey on Grey apple logo at start up to work properly like it does in a Mac, even with kext patches on the fly being used and fixes tried but it doesn't work ok with Custom Logo: Apple ,instead of the white on black one that works perfectly when applying one little fix?

 

What you describe is 'proper', the black vs grey is chosen based on SMBIOS as far as I know. In my opinion, boot.efi's decisions is not a business for Clover.

  • Like 4
Link to comment
Share on other sites
Mork vom Ork
Mork vom Ork
Posted
Posted

Sorry to disturb your discussion:

 

just want to know, if it is possible with clover to patch 2 different frambuffers for two different gfx-cards in just one way.

For example:

 

i have one Sapphire HD6570 in slot#1, which use AMD6000Controller for FB-patching ("Gibba" will make it work).

and i have R9 380X in slot#2, which use AMD9000Controller for FB-patching ("Greyhound" will make it work).

 

when i use CLOVER Configurator, i set "Gibba" on FB Name and select Inject ATI in Graphic section.

i use two patches under KextsToPatch in Kernal and Kext Patches section to patch the given framebuffers to their desired values.

 

now when i start cloaver bootloader, i will get the following screen:

post-598588-0-30344600-1454692909_thumb.jpg

 

as you can see, GIBBA as FB for the HD6570 will be correct, but it is also selected for the R9 380X, which will be wrong.

as i boot now without to change the FBConfig: entry, the system will boot and HD6570 will use GIBBA as correct Framebuffer, while R9 380X uses AMD, RadeonFramebuffer.

if i put GREYHOUND into FBConfig for the R9 380X and boot the System, R9 380X uses the correct Framebuffer Greyhound, while HD6570 now uses AMD, RadeonFramebuffer.

 

so for me, it seems, that clover is not able to put each different framebuffer to each different card. seems to use allways one Framebuffer for any amount of detected gfx-cards.

 

is there an way to solve this missbehavior? or is it just me, doing something wrong here...

 

regards,

 

Mork vom Ork

 

PS: these are my setting within "info.plist":

	<key>Graphics</key>
	<dict>
		<key>FBName</key>
		<string>Gibba</string>
		<key>Inject</key>
		<dict>
			<key>ATI</key>
			<true/>
			<key>Intel</key>
			<false/>
			<key>NVidia</key>
			<false/>
		</dict>
		<key>LoadVBios</key>
		<true/>
		<key>NvidiaSingle</key>
		<false/>
	</dict>
	<key>KernelAndKextPatches</key>
	<dict>
		<key>AppleRTC</key>
		<true/>
		<key>AsusAICPUPM</key>
		<true/>
		<key>Debug</key>
		<false/>
		<key>KernelCpu</key>
		<false/>
		<key>KernelHaswellE</key>
		<false/>
		<key>KernelLapic</key>
		<false/>
		<key>KernelPm</key>
		<true/>
		<key>KextsToPatch</key>
		<array>
			<dict>
				<key>Comment</key>
				<string>AMD 380X Greyhound</string>
				<key>Disabled</key>
				<false/>
				<key>Find</key>
				<data>
				AAQAAAQDAAAAAQEHEAABAwAEAAAEAwAAAAECByABAgQA
				BAAABAMAAAABAwcRAgMBAAQAAAQDAAAAAQQHIQMEAgAE
				AAAEAwAAAAEFBxIEBQUABAAABAMAAAABBgciBQYG
				</data>
				<key>Name</key>
				<string>AMD9000Controller</string>
				<key>Replace</key>
				<data>
				AAQAAAQDAAAAAQEHEQIEAQAIAAAEAgAAAAECByEDBQME
				AAAABAAAAAABAwcQAAEFBAAAABQAAAAAAQQHEgQGBgAE
				AAAEAwAAAAEFBxIEAgIABAAABAMAAAABBgciBQME
				</data>
			</dict>
			<dict>
				<key>Comment</key>
				<string>Gibba</string>
				<key>Disabled</key>
				<false/>
				<key>Find</key>
				<data>
				AAQAAAQDAAAAAQAAEgQFAQAEAAAEAwAAAAEAACIFBAIA
				CAAABAIAAAABAAARAgYEAAIAABQCAAAAAQAAAAADBQQA
				AAAEAgAAAAEAABECAQM=
				</data>
				<key>Name</key>
				<string>AMD6000Controller</string>
				<key>Replace</key>
				<data>
				AAgAAAQCAAAAAQAAEgQEAwACAAAUAgAAAAEAABAAAQQQ
				AAAAEAAAAAABAAAAEAIBAAIAABQCAAAAAQAAIgADBQQA
				AAAEAgAAAAEAABECAQM=
				</data>
			</dict>
		</array>
	</dict>
Link to comment
Share on other sites
Mork vom Ork
Mork vom Ork
Posted
Posted

Use Devices-->Arbitrary 

more info here:             #8            

 Thanx for the hint, but seems not to work for me.

 

This is what i tried so far:

    <key>Devices</key>
    <dict>
        <key>Arbitrary</key>
        <array>
            <dict>
                <key>Comment</key>
                <string>ATI Radeon HD 6570</string>
                <key>PciAddr</key>
                <string>05:00.00</string>
                <key>CustomProperties</key>
                <array>
                    <dict>
                        <key>Key</key>
                        <string>name</string>
                        <key>Value</key>
                        <string>Radeon Graphics Controller</string>
                    </dict>
                    <dict>
                        <key>Key</key>
                        <string>model</string>
                        <key>Value</key>
                        <string>AMD Radeon HD 6570 Series</string>
                    </dict>
                    <dict>
                        <key>FBName</key>
                        <string>Gibba</string>
                    </dict>
                    <dict>
                        <key>Key</key>
                        <string>Inject</string>
                        <key>Key</key>
                        <string>ATI</string>
                        <key>Value</key>
                        <true/>
                    </dict>
                </array>
            </dict>
            <dict>
                <key>Comment</key>
                <string>ATI Radeon HD 6570</string>
                <key>PciAddr</key>
                <string>05:00.01</string>
                <key>CustomProperties</key>
                <array>
                    <dict>
                        <key>Key</key>
                        <string>name</string>
                        <key>Value</key>
                        <string>Radeon Graphics Controller</string>
                    </dict>
                    <dict>
                        <key>Key</key>
                        <string>model</string>
                        <key>Value</key>
                        <string>AMD Radeon HD 6570 Series</string>
                    </dict>
                    <dict>
                        <key>FBName</key>
                        <string>Gibba</string>
                    </dict>
                    <dict>
                        <key>Key</key>
                        <string>Inject</string>
                        <key>Key</key>
                        <string>ATI</string>
                        <key>Value</key>
                        <true/>
                    </dict>
                </array>
            </dict>
            <dict>
                <key>Comment</key>
                <string>ATI Radeon R9 380X</string>
                <key>PciAddr</key>
                <string>06:00.00</string>
                <key>CustomProperties</key>
                <array>
                    <dict>
                        <key>Key</key>
                        <string>name</string>
                        <key>Value</key>
                        <string>Radeon Graphics Controller</string>
                    </dict>
                    <dict>
                        <key>Key</key>
                        <string>model</string>
                        <key>Value</key>
                        <string>ATI Radeon R9 M295X</string>
                    </dict>
                    <dict>
                        <key>FBName</key>
                        <string>Labrador</string>
                    </dict>
                    <dict>
                        <key>Key</key>
                        <string>Inject</string>
                        <key>Key</key>
                        <string>ATI</string>
                        <key>Value</key>
                        <true/>
                    </dict>
                </array>
            </dict>
            <dict>
                <key>Comment</key>
                <string>ATI Radeon R9 380X</string>
                <key>PciAddr</key>
                <string>06:00.01</string>
                <key>CustomProperties</key>
                <array>
                    <dict>
                        <key>Key</key>
                        <string>name</string>
                        <key>Value</key>
                        <string>Radeon Graphics Controller</string>
                    </dict>
                    <dict>
                        <key>Key</key>
                        <string>model</string>
                        <key>Value</key>
                        <string>ATI Radeon R9 M295X</string>
                    </dict>
                    <dict>
                        <key>FBName</key>
                        <string>Labrador</string>
                    </dict>
                    <dict>
                        <key>Key</key>
                        <string>Inject</string>
                        <key>Key</key>
                        <string>ATI</string>
                        <key>Value</key>
                        <true/>
                    </dict>
                </array>
            </dict>
        </array>
        <key>Audio</key>
        <dict>
            <key>Inject</key>
            <string>No</string>
        </dict>
        <key>FakeID</key>
        <dict>
            <key>ATI</key>
            <string>0x0</string>
            <key>IMEI</key>
            <string>0x0</string>
            <key>IntelGFX</key>
            <string>0x0</string>
            <key>LAN</key>
            <string>0x0</string>
            <key>NVidia</key>
            <string>0x0</string>
            <key>SATA</key>
            <string>0x0</string>
            <key>WIFI</key>
            <string>0x0</string>
            <key>XHCI</key>
            <string>0x0</string>
        </dict>
        <key>USB</key>
        <dict>
            <key>AddClockID</key>
            <true/>
            <key>FixOwnership</key>
            <true/>
            <key>Inject</key>
            <true/>
        </dict>
    </dict>

and this is what i get in the bootlog after next restart:

13:205  0:000  SSDT with CPU P-States generated successfully
13:205  0:000  SSDT with CPU C-States generated successfully
13:205  0:000  EdidDiscovered size=128
13:205  0:000  00 | 00 FF FF FF FF FF FF 00 26 CD 03 71 01 01 01 01 
13:205  0:000  16 | 00 18 01 03 80 3E 22 78 2A 08 A5 A2 57 4F A2 28 
13:205  0:000  32 | 0F 50 54 BF EF 80 E1 C0 D1 C0 A9 C0 D1 00 A9 40 
13:205  0:000  48 | B3 00 81 80 81 C0 E6 73 00 30 F2 70 5A 80 B0 58 
13:205  0:000  64 | 8A 00 6D 55 21 00 00 1E 00 00 00 FF 00 30 0A 20 
13:205  0:000  80 | 20 20 20 20 20 20 20 20 20 20 00 00 00 FD 00 17 
13:205  0:000  96 | 4C 1E 5C 1E 00 0A 20 20 20 20 20 20 00 00 00 FC 
13:206  0:000  112 | 00 50 4C 32 38 38 38 55 48 0A 20 20 20 20 01 C6 
13:206  0:000  custom properties for device 00:00.00 injected, continue
13:206  0:000  custom properties for device 00:01.00 injected, continue
13:206  0:000  custom properties for device 00:01.01 injected, continue
13:206  0:000  custom properties for device 00:03.00 injected, continue
13:206  0:000  custom properties for device 03:00.00 injected, continue
13:206  0:000  custom properties for device 04:10.00 injected, continue
13:206  0:000  custom properties for device 05:00.00 injected, continue
13:206  0:000  custom properties for device 05:00.01 injected, continue
13:206  0:000  custom properties for device 04:08.00 injected, continue
13:206  0:000  custom properties for device 06:00.00 injected, continue
13:206  0:000  custom properties for device 06:00.01 injected, continue
13:206  0:000  custom properties for device 00:02.00 injected, continue
13:206  0:000  custom properties for device 07:00.00 injected, continue
13:206  0:000  custom properties for device 08:10.00 injected, continue
13:206  0:000  custom properties for device 09:00.00 injected, continue
13:206  0:000  custom properties for device 08:08.00 injected, continue
13:206  0:000  custom properties for device 0A:00.00 injected, continue
13:206  0:000  custom properties for device 08:09.00 injected, continue
13:206  0:000  custom properties for device 0B:00.00 injected, continue
13:206  0:000  custom properties for device 00:05.00 injected, continue
13:206  0:000  custom properties for device 00:05.01 injected, continue
13:206  0:000  custom properties for device 00:05.02 injected, continue
13:206  0:000  custom properties for device 00:05.04 injected, continue
13:206  0:000  custom properties for device 00:05.06 injected, continue
13:206  0:000  custom properties for device 00:11.00 injected, continue
13:206  0:000  custom properties for device 00:14.00 injected, continue
13:206  0:000  custom properties for device 00:16.00 injected, continue
13:206  0:000  custom properties for device 00:16.01 injected, continue
13:206  0:000  custom properties for device 00:16.02 injected, continue
13:206  0:000  custom properties for device 00:16.03 injected, continue
13:206  0:000  custom properties for device 00:19.00 injected, continue
13:206  0:000  custom properties for device 00:1C.00 injected, continue
13:206  0:000  custom properties for device 00:1C.03 injected, continue
13:206  0:000  custom properties for device 0D:00.00 injected, continue
13:206  0:000  custom properties for device 0E:01.00 injected, continue
13:206  0:000  custom properties for device 0F:00.00 injected, continue
13:206  0:000  custom properties for device 0E:05.00 injected, continue
13:206  0:000  custom properties for device 10:00.00 injected, continue
13:206  0:000  custom properties for device 00:1C.06 injected, continue
13:206  0:000  custom properties for device 11:00.00 injected, continue
13:206  0:000  custom properties for device 00:1D.00 injected, continue
13:206  0:000  custom properties for device 00:1F.00 injected, continue
13:206  0:000  custom properties for device 00:1F.02 injected, continue
13:206  0:000  custom properties for device 00:1F.03 injected, continue
13:206  0:000  custom properties for device 00:1F.06 injected, continue
13:206  0:000  stringlength = 216
13:206  0:000  CurrentMode: Width=1280 Height=1024
13:206  0:000  Beginning FSInjection
FSInjectionInstall ...

Both cards than using AMD, RadeonFramebuffer as their default FB. Any tip is much appreciated.

Regards...

 

Mork vom Ork

Link to comment
Share on other sites
kosakgroove
kosakgroove
Posted
Posted

Clover Configurator is developed by another team and it's closed source. Also, AMD support is not patching the kernel, but replacing it.

 

 

What you describe is 'proper', the black vs grey is chosen based on SMBIOS as far as I know. In my opinion, boot.efi's decisions is not a business for Clover.

 

Alright that's my bad. thanks for making my ideas more clear.

What about the 2nd suggestion, how could one remove that annoying little text, Clover rev 3380 in the early stages of Clover loading. Wouldn't it be nicer to have just a black or white screen?

Link to comment
Share on other sites
Slice
Slice
Posted
Posted

Done,wifi posts moved here: http://www.insanelymac.com/forum/topic/310779-about-bcm943142-in-osx/ 

Later I'll delete mine and your latest post. Do you need any other posts to be moved somewere?

Thanks! No more at now.

 

 

for AMD builds, and AMD processors. Just like we patch the kernel on the fly for locked MSR we could maybe patch it for AMD support, taking knowledge of the amazing AMD forums we have here.

Clover supports AMD CPU. At least for those who provided me reports.

 

 

Alright that's my bad. thanks for making my ideas more clear.

What about the 2nd suggestion, how could one remove that annoying little text, Clover rev 3380 in the early stages of Clover loading. Wouldn't it be nicer to have just a black or white screen?

 

As fas as I know latest Clover revision is 3347.

Link to comment
Share on other sites
Mork vom Ork
Mork vom Ork
Posted
Posted

Hallo guys, once more it's me with my "FBName"-problem. I try to use the "Arbitrary"-Array to get two different Framebuffers for two different AMD gfx-cards injected.

This is what i solved so far with "try and error" method:

 

post-598588-0-87966200-1454806749_thumb.png

 

Screen only shows settings for Radeon HD6570, cause settings in "Item 2" will be the same for Radeon R9 380X (except the PciAddr value, name and model, device-id).

ATI-Injection works so far, cause i can verify it through Systeminformation, which will show 8-channel HDMI-Audio if ATI boolean is disabled. If it is enabled, HDMI-Audio is just 2-channel cause of missing correct frambuffer to set connectors in the right order.

 

Spend the whole day to make correct settings to setup the right FBName key commands w/o any luck. No matter what i tried, Framebuffer allways show as ATY,AMD,RadeonFramebuffer. Now i am out of ideas what else to set (and in which order) to make the FBName key work. Any help appreciated...

 

if any questions, don't hesitate to ask... i will do my best to you to help me getting this problem solved.

Link to comment
Share on other sites
oSxFr33k
oSxFr33k
Posted
Posted

I have an Asus Laptop G74Sx that I thought the Bios/Motherboard was UEFI but Clover will only boot with legacy install boot0af, will not boot for UEFI booting only option.   The bios has enable/disable UEFI boot as a setting but i'm guessing that does not mean its a UEFI bios? How can I troubleshoot to see why it will not boot UEFI?  Right now I have dual boot legacy/UEFI since I am swapping out my SSD Drive between two devices for testing purposes.

Link to comment
Share on other sites
Slice
Slice
Posted
Posted

I have an Asus Laptop G74Sx that I thought the Bios/Motherboard was UEFI but Clover will only boot with legacy install boot0af, will not boot for UEFI booting only option.   The bios has enable/disable UEFI boot as a setting but i'm guessing that does not mean its a UEFI bios? How can I troubleshoot to see why it will not boot UEFI?  Right now I have dual boot legacy/UEFI since I am swapping out my SSD Drive between two devices for testing purposes.

Did you have a file /EFI/BOOT/BOOTX64.EFI ?

Some UEFI BIOSes may start only from this.

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

Did you have a file /EFI/BOOT/BOOTX64.EFI ?

Some UEFI BIOSes may start only from this.

 

 

Yes, there is also the BOOTIA32.efi file there to.  After some google searching there was one post claiming that this particular Bios may have some UEFI simulation setting and may not be a true UEFI Motherboard.  I can verify it does not have secure boot or enable/disable CSM which I thought was needed for true UEFI motherboard/bios no?

Link to comment
Share on other sites
 Share
Go to topic listing
×
×
  • Create New...