Clover General discussion

[chris1111]

I am on Clover 5107 I dont have anny mousse issue on clicking to the GUI Clover 

 

[polyzargone]

I built Clover from sources and the issue has been fixed.

 

Maybe the release version available at Releases · CloverHackyColor/CloverBootloader · GitHub should be updated?

 

Anyway, thanks @chris1111  for pointing me to the right direction :).

Edited March 29, 2020 by polyzargone

[Slice]

3 hours ago, polyzargone said:

I built Clover from sources and the issue has been fixed.

 

Maybe the release version available at Releases · CloverHackyColor/CloverBootloader · GitHub should be updated?

 

Anyway, thanks @chris1111  for pointing me to the right direction :).

Yes, this release contains a mistake.

I will create 5108 corrected.

[Pene]

11 hours ago, arsradu said:

Bios/CMOS reset? Might be stupid, but...I think it's worth a try, since the same issue occurs with older Clover versions and Clover is not actually in charge of that functionality... Looks like some weird bios issue.

Thanks, but it wasn't that.

 

14 hours ago, Slice said:

There is no relation to any Clover commit. It is wrong SimplePointerProtocol in your UEFI BIOS. Clover has nothing to do with it rather than implement somehow workarounds for your mouse.

Test with other mouse for example.

When debugging the mouse problem, I figured out that the problem is that in my case ResolutionX/ResolutionY were high values, and according to the arithmetic order that was before, it would always result in 0 for positive numbers.

So I committed a change to Clover to correct this. Now I can set a higher Pointer Speed in config.plist and mouse is working perfectly.

 

P.S. AptioInputFix is irrelevant for my case also, as my motherboard doesn't have &gAmiEfiPointerProtocolGuid, so nothing is applied by AptioInputFix.

Edited March 29, 2020 by Pene

[STLVNUB]

I've made a little script file to make compiling easier 

It's called CloverBuilderV0.1

Please run from its Folder, CloverBuilderV0.1

 

What does it do?

Creates link to itself then you only need type "clover" to run buildme

Best to check /usr/local/bin/clover is not there before hand.

Clones the repo into its CloverBuilderV0.1 Folder

runs "buildme"

 

Certaintly easier, well it is for me.

CloverBuilderV0.1.zip

[chris1111]

After one of the commits on 

Commits on Mar 29, 2020 Trying also commits from today 30 Mar and its the same issue

Black screen after booting with GeForce GT 710 HDMI the monitor goes to no signal HDMI

Edited March 30, 2020 by chris1111

[Pene]

2 hours ago, chris1111 said:

After one of the commits on 

Commits on Mar 29, 2020 Trying also commits from today 30 Mar and its the same issue

Black screen after booting with GeForce GT 710 HDMI the monitor goes to no signal HDMI

Please explain more details.

Clover loads successfully to menu, you select the entry and then black screen?

Clover doesn't load at all?

[chris1111]

15 minutes ago, Pene said:

Please explain more details.

Clover loads successfully to menu, you select the entry and then black screen?

Clover doesn't load at all?

Yes load successfully to menue boot successfully but no signal monitor juste before the second stage boot

Iam taping to my keyboard and I hear the sound but the display stay closed

[Pene]

41 minutes ago, chris1111 said:

Yes load successfully to menue boot successfully but no signal monitor juste before the second stage boot

Iam taping to my keyboard and I hear the sound but the display stay closed

I saw a mistake in one of the commits from Mar 29 regarding Nvidia injection.

Check again with the committed fix.

[LockDown]

4 hours ago, Pene said:

Clover loads successfully to menu, you select the entry and then black screen?

 

Yes, blackscreen here. not like @chris1111 that is getting NO SGNAL.

 

 

 

Compiling March 31, im getting this message. No errors though. (Using High Sierra with Xcode 10.1)

[CPP] menu
[CPP] screen
/Applications/Xcode.app/Contents/Developer/Toolchains/XcodeDefault.xctoolchain/usr/bin/libtool: file: /Users/ella/src/CloverBootloader/Build/Clover/RELEASE_XCODE8/X64/rEFIt_UEFI/refit/OUTPUT/entry_scan/secureboot.obj has no symbols
/Applications/Xcode.app/Contents/Developer/Toolchains/XcodeDefault.xctoolchain/usr/bin/libtool: file: /Users/ella/src/CloverBootloader/Build/Clover/RELEASE_XCODE8/X64/rEFIt_UEFI/refit/OUTPUT/entry_scan/securehash.obj has no symbols
/Applications/Xcode.app/Contents/Developer/Toolchains/XcodeDefault.xctoolchain/usr/bin/libtool: file: /Users/ella/src/CloverBootloader/Build/Clover/RELEASE_XCODE8/X64/rEFIt_UEFI/refit/OUTPUT/entry_scan/securemenu.obj has no symbols
/Applications/Xcode.app/Contents/Developer/Toolchains/XcodeDefault.xctoolchain/usr/bin/libtool: file: /Users/ella/src/CloverBootloader/Build/Clover/RELEASE_XCODE8/X64/rEFIt_UEFI/refit/OUTPUT/entry_scan/securevars.obj has no symbols
/Applications/Xcode.app/Contents/Developer/Toolchains/XcodeDefault.xctoolchain/usr/bin/libtool: file: /Users/ella/src/CloverBootloader/Build/Clover/RELEASE_XCODE8/X64/rEFIt_UEFI/refit/OUTPUT/libeg/XTheme.obj has no symbols
/Applications/Xcode.app/Contents/Developer/Toolchains/XcodeDefault.xctoolchain/usr/bin/libtool: file: /Users/ella/src/CloverBootloader/Build/Clover/RELEASE_XCODE8/X64/rEFIt_UEFI/refit/OUTPUT/cpp_foundation/XUINTN.obj has no symbols
[SLINK] CLOVERX64
[DLINK1] CLOVERX64
[MTOC] CLOVERX64
[GENFW] CLOVERX64

Generating DUETEFIMAINFVX64 FV

Is it ok to disregard this message?

Edited March 31, 2020 by ellaosx

[ameenjuz]

VoodooI2C.kext is not working during installation

i put kext into the Other folder and but didn't work

anyone can tell me what is this issue

[Slice]

38 minutes ago, anmool said:

VoodooI2C.kext is not working during installation

i put kext into the Other folder and but didn't work

anyone can tell me what is this issue

Check the kext info.plist if it contains lines

	<key>OSBundleRequired</key>
	<string>Console</string>

If no then add them as other kexts usually have.

[ameenjuz]

28 minutes ago, Slice said:

Check the kext info.plist if it contains lines

	<key>OSBundleRequired</key>
	<string>Console</string>

If no then add them as other kexts usually have.

1.  i changed OSBundleRequired=Root to console

i have another issue is compiling with xcode 11.4  

2.  compiling stuck with this stage [HDIUTIL] /Users/mohammad/src/CloverBootloader/CloverPackage/sym/Clover-5108-X64.iso

3, third issue is that automatically restart my laptop due to timeouts SetDPPowerState but i solved this problem in OpenCore bootloader with this option set PowerTimeoutKernelPanic=true but in clover bootoader no luck 

please slice anwser my these three issues

i attached screenshot of both issue

 

i attached screenshot of both issue

[Andres ZeroCross]

43 minutes ago, anmool said:

1.  i changed OSBundleRequired=Root to console

i have another issue is compiling with xcode 11.4  

2.  compiling stuck with this stage [HDIUTIL] /Users/mohammad/src/CloverBootloader/CloverPackage/sym/Clover-5108-X64.iso

3, third issue is that automatically restart my laptop due to timeouts SetDPPowerState but i solved this problem in OpenCore bootloader with this option set PowerTimeoutKernelPanic=true but in clover bootoader no luck 

please slice anwser my these three issues

i attached screenshot of both issue

 

i attached screenshot of both issue

IOSCSIPeripherials is about SATA,, check your SATA Power management in BIOS. Set it to Disable, clover doesn't have feature for "set PowerTimeoutKernelPanic"

[ameenjuz]

3 minutes ago, Andres ZeroCross said:

IOSCSIPeripherials is about SATA,, check your SATA Power management in BIOS. Set it to Disable, clover doesn't have feature for "set PowerTimeoutKernelPanic"

i have no such option in my bois

[Pene]

5 hours ago, ellaosx said:

Yes, blackscreen here. not like @chris1111 that is getting NO SGNAL.

Did you try after the latest commit to see if the black screen problem persists? What is your hardware?

 

5 hours ago, ellaosx said:

Compiling March 31, im getting this message. No errors though. (Using High Sierra with Xcode 10.1)

Is it ok to disregard this message?

Yes, it is safe to ignore that message. It just notifies about empty code (for example, code excluded via #ifdef, such as XTheme currently).

Edited March 31, 2020 by Pene

[chris1111]

9 hours ago, Pene said:

I saw a mistake in one of the commits from Mar 29 regarding Nvidia injection.

Check again with the committed fix.

Thanks @Pene but that's not work same problem, the monitor= no signal

my hardware is Dell Optiplex 790 / CPU i5 2500k /GeForce GT 710 2gig low profile

[Pene]

@Jief_Machak

Any chance you see something else with your snprintf / printf commits or anything else that could affect functionality of Nvidia_inject from last days? We have already two reports it is broken.

I noticed one mistake and corrected it in my latest commit, but maybe you see something else that I missed 

 

Edited March 31, 2020 by Pene

[chris1111]

@PeneNow I will compile entire source not only Update

I will report after

[Jief_Machak]

I would be surprised that I haven't introduce a bug. I tried to be thorough. I did some unit tests (that I didn't commit) to make sure how AsciiPrint works, testing format specifier etc. But hey, there always something slipping. So I'm sorry for this uneasy transition time.

 

I'm afraid I will need someone who can reproduce the bug to take time to checkout commit by commit, so we know the last working commit. 

[Jief_Machak]

I had a look at the commit "Correct mistake with nvidia inject name". So that's something that went sideways : the format specifier were corrected to %d because no cast for an integral parameter.

A good guess is that there is the same mistake somewhere else. In few hours, I'll checkout at the commit just before "Get rid of AsciiPrint." and check all the %c I might have wrongly replaced.

[chris1111]

@Pene

Ok after one of my friend testing the bad commit and confirming to me the issue on GT 710 on DVI

He will compill latest commit successfully and I do the same (I have compile entire source successfully) and NOW this is work on  GeForce 710 HDMI 

Thank you very much!

Edited March 31, 2020 by chris1111
I have compile entire source successfully

[Pene]

3 hours ago, chris1111 said:

@Pene

Ok after one of my friend testing the bad commit and confirming to me the issue on GT 710 on DVI

He will compill latest commit successfully and I do the same (I have compile entire source successfully) and NOW this is work on  GeForce 710 HDMI 

Thank you very much!

Thanks for your post but I'm confused now. Didn't you say earlier that my commit Witt the fix didn't fix it?

[Jief_Machak]

I did the search and the only %c I found was the one already corrected by asava ( @Pene is that your github name?).

So I'm curious, is it working now ?

[Pene]

 

6 hours ago, Jief_Machak said:

I would be surprised that I haven't introduce a bug. I tried to be thorough. I did some unit tests (that I didn't commit) to make sure how AsciiPrint works, testing format specifier etc. But hey, there always something slipping. So I'm sorry for this uneasy transition time.

 

I'm afraid I will need someone who can reproduce the bug to take time to checkout commit by commit, so we know the last working commit. 

Don't worry about it, you are doing great work, it's all for the best.

 

21 minutes ago, Jief_Machak said:

I did the search and the only %c I found was the one already corrected by asava ( @Pene is that your github name?).

So I'm curious, is it working now ?

Yes Jief, it is my GitHub name  

I am curious also, as I didn't find anything else wrong either.