Jump to content

Clover problems report & features request


ErmaC
953 posts in this topic

Recommended Posts

26 minutes ago, Sherlocks said:

old clover shown gray color with cursor. but now shown white color. is it normal?

Your "bootcamp" theme uses this:

		<key>Selection</key>
		<dict>
			...
			<key>Color</key>
			<string>0xF3F3F380</string>
			...
		</dict>

#F3F3F3 should be closer to white by design.

Screenshot 7.png

 

#EDIT: So after r4728, if you wanna get prev. gray Selection Color, try with #909090FF

Edited by Badruzeus
  • Like 1
Link to comment
Share on other sites

Your "bootcamp" theme uses this:

		Selection		...Color0xF3F3F380		...

#F3F3F3 should be closer to white by design.

2057181578_Screenshot7.png.b87d9a2937ac8b90d91b5a75cab1ec1c.png

 

#EDIT: So after r4728, if you wanna get prev. gray Selection Color, try with #909090FF

 

okay. as result, old clover has selection color issue. thank you for clear.

 

나의 LG-F800S 의 Tapatalk에서 보냄

 

 

 

  • Like 2
Link to comment
Share on other sites

3 hours ago, Slice said:

Check the issue with animation on revision 4742.

I'm using r4743 currently, Banner animation is working and transparency has been fixed.. thanks.

But it won't work on disp res below 1366 (for example 1280), and still it disappears randomly after theme switch.

Link to comment
Share on other sites

7 hours ago, Slice said:

Check the issue with animation on revision 4742.

Thank you Slice everything is perfect here Thanks for your effort and your time

 

screenshot12.thumb.png.17d51c2cbf156c833f4f1aaf391f3e21.png

 

 

Edited by chris1111
  • Like 2
Link to comment
Share on other sites

Hi all developers out there.

We are some guys here on the forum using Xeon W 21xx on ASUS mobos with C422 chips.

Our problem today is that we need to use both kernel patch (xcpm_pkg_scope_msrs_PMhart) and FakeCPUID (0x0506E4) to boot our rigs otherwise we get stucked at:

random seed ++++++++++.

This with unlocked MSR 0xE2 register in the last bios 0702.

Even the not native Skylake X299 is running without kernel patch and FakeCPUID so there must be something odd with our setup.

Why do we need to patch and use FakeCPUID when both processor an chipset is the same as in the new iMacPro1.1 and should be recognised as more or less native?

With the patch we use today Mac OS is running smooth and stable but we would like to run everything as vanilla as possible and that's why we asking for help.

 

We are all noobs and need help to solve this problem if it's all possible.

Any help appreciated.

Link to comment
Share on other sites

Clover or script issue?


build.py...

/Users/shane/src/edk2/MdePkg/Library/BaseLib/BaseLib.inf(350): error 000E: File/directory not found in workspace

/Users/shane/src/edk2/MdePkg/Library/BaseLib/X64/Lfence.nasm

 

 

- Failed -

Build end time: 19:30:39, Nov.15 2018

Build total time: 00:00:02

 

 

o_Ops, ./ebuild.sh exited with error(s), aborting..

Link to comment
Share on other sites

install clover to a usb then boot off that till you can get back into your os and correct the error. if you cant use the clover package because of not having a mac available then use the clover iso and modify it to your needs. like config plist and kexts/ clover drivers.

  • Like 1
Link to comment
Share on other sites

2 hours ago, bronxteck said:

install clover to a usb then boot off that till you can get back into your os and correct the error. if you cant use the clover package because of not having a mac available then use the clover iso and modify it to your needs. like config plist and kexts/ clover drivers.

ahh, I forgot that I still have my High Sierra USB Installer.

it fixed now, thanks.

  • Like 1
Link to comment
Share on other sites

Fix for 32-bit builds:

diff a/rEFIt_UEFI/Platform/Settings.c b/rEFIt_UEFI/Platform/Settings.c
--- a/rEFIt_UEFI/Platform/Settings.c
+++ b/rEFIt_UEFI/Platform/Settings.c
@@ -7586,7 +7586,10 @@ SetDevices (LOADER_ENTRY *Entry)
                         MsgLog ("  Read default Framebuffer LEVX: 0x%x\n", FBLEVX);
                       }
 
-                      LEVD = (UINT64)FBLEVX * (UINT64)LEVX / 0xFFFFLL;
+                      LEVD = DivU64x32 (
+                               MultU64x32 (FBLEVX, LEVX),
+                               0xFFFF
+                               );
                       MsgLog ("  Write new LEVD: 0x%x\n", LEVD);
 
                       /*Status = */PciIo->Mem.Write(

 

  • Like 3
Link to comment
Share on other sites

  • 3 weeks later...

Is there any reason why my keyboard no longer works in Clover GUI? It used too but now i have to use mouse. Once i boot into macOS or Windows it works just fine, it's only in clover GUI. I have tried AptioInputFix-64.efi with no luck.

Desktop in sig

Clover 4808


Corsair STRAFE RGB Gaming Keyboard:

 

  Product ID: 0x1b20

  Vendor ID: 0x1b1c  (CORSAIR MEMORY INC.)

  Version: 3.08

  Serial Number: xxxxxxxxxxxx

  Speed: Up to 12 Mb/sec

  Manufacturer: Corsair

  Location ID: 0x14300000 / 2

  Current Available (mA): 500

  Current Required (mA): 500

  Extra Operating Current (mA): 0

Edited by SavageAUS
Link to comment
Share on other sites

2 hours ago, SavageAUS said:

Is there any reason why my keyboard no longer works in Clover GUI? It used too but now i have to use mouse. Once i boot into macOS or Windows it works just fine, it's only in clover GUI. I have tried AptioInputFix-64.efi with no luck.

Desktop in sig

Clover 4808

When it happens? With 4808 or early? What about officially released Clover?

Link to comment
Share on other sites

When it happens? With 4808 or early? What about officially released Clover?

Was happening almost every boot/reboot for a while. I’ll try clover for SF after I change USB ports around. Apparently my keyboard has problems on USB 3.0 ports.


Sent from my iPhone using Tapatalk
Link to comment
Share on other sites

13 hours ago, zxv said:

Clover not detecting XMP profiles anymore it seems (no mention of XMP in bdmesg). Not sure if something changed on newer boards (Z390). 

The message just excluded from release. If you want to see it then compile own version with more debug messages.

Link to comment
Share on other sites

On 12/18/2018 at 4:33 AM, Slice said:

The message just excluded from release. If you want to see it then compile own version with more debug messages.

Cool. Good to know we're removing useful information from standard builds.

Link to comment
Share on other sites

×
×
  • Create New...