Jump to content

Clover General discussion


ErmaC
30,155 posts in this topic

Recommended Posts

Both work for me  :yes:

 

attachicon.gifpreboot.log.p3.zip

 

attachicon.gifpreboot.log.p4.zip

Both work for me  :yes:

 

attachicon.gifpreboot.log.p3.zip

 

attachicon.gifpreboot.log.p4.zip

@tluck @ricoc90 @Badruzeus Er... I think the problem maybe the compile tool. What compile tool you use to compile Clover?

 

P4 is the build from r4211(directly)!! Because p1 p2 and p3 change different irrelevant places but they all work! So I built r4211 from source and it work as expected. 

 

P.S. I never use third party tool to build Clover, I use official guide to build Clover(./ebuild.sh) on macOS 10.12.6 on both MacBookPro141 and Precision M3800.

 

syscl

  • Like 2
Link to comment
Share on other sites

Please try this one @tluck @Badruzeus @ricoc90

 

attachicon.gifr4211-p3.zip

 

and this one

attachicon.gifr4211-p4.zip

 

Thank you in advance,

syscl

OK, both r4211-p3 & P4 work on my legacy. But on my last test, -p4 gives better results for my 2nd gen mach with Nvidia GF119 << it solves non-saved brightness values on every boot (even after sudo nvram -c) with r4210.

 

Also some notes about "r4211-p2", it caused my installed 3rd party kext named "AsusNBFnKeys v2.6" gives "No graphics found" message on verbose logs << not a mandatory though, thanks @syscl.  :)

preboot.log_nb_a43sj_r4211-p3.zip

preboot.log_nb_a43sj_r4211-p4.zip

AsusNBFnKeys.kext.zip

  • Like 1
Link to comment
Share on other sites

Er... I think the problem maybe the compile tool. What compile tool you use to compile Clover?

 

 P4 is the build from r4211(directly)!! Because p1 p2 and p3 change different irrelevant places but they all work! So I built r4211 from source and it work as my guess. 

 

P.S. I never use third party tool to build Clover, I use official guide to build Clover.

 

syscl

Hmmm :lol: . I'm using the build_clover.command (v4.5.3) method. I'll manually compile and report back. 

Link to comment
Share on other sites

OK, both r4211-p3 & P4 work on my legacy. But on my last test, -p4 gives better results for my 2nd gen mach with Nvidia GF119 << it solves non-saved brightness values on every boot (even after sudo nvram -c) with r4210.

 

Also some notes about "r4211-p2", it caused my installed 3rd party kext named "AsusNBFnKeys v2.6" gives "No graphics found" message on verbose logs << not a mandatory though, thanks @syscl.  :)

Thank you, actually p4 is r4211. They(p4 and r4211) are identical. I just build Clover use official way and never use any other tool to build it.

 

What's your build tool for Clover?

 

syscl

  • Like 1
Link to comment
Share on other sites

@tluck @ricoc90 @Badruzeus Er... I think the problem maybe the compile tool. What compile tool you use to compile Clover?

 

P4 is the build from r4211(directly)!! Because p1 p2 and p3 change different irrelevant places but they all work! So I built r4211 from source and it work as expected. 

 

P.S. I never use third party tool to build Clover, I use official guide to build Clover(./ebuild.sh) on macOS 10.12.6 on both MacBookPro141 and Precision M3800.

 

syscl

@syscl

My build tools on OS X El Capitan 10.11.6 (15G1611) are:

 

~ Build_Clover script v4.5.3

~ XCode 8.3 version 8C38

~ Apple LLVM version 8.0.0 (clang-800.0.42.1)

~ NASM version 2.13.01. 

  • Like 2
Link to comment
Share on other sites

@tluck @ricoc90 @Badruzeus Er... I think the problem maybe the compile tool. What compile tool you use to compile Clover?

 

P4 is the build from r4211(directly)!! Because p1 p2 and p3 change different irrelevant places but they all work! So I built r4211 from source and it work as expected. 

 

P.S. I never use third party tool to build Clover, I use official guide to build Clover(./ebuild.sh) on macOS 10.12.6 on both MacBookPro141 and Precision M3800.

 

syscl

 

 

When I compile r4211 with Build_Clover script v4.5.3 (which uses default XCODE8 settings), get red screen error after selecting OSX Volume on my legacy desktop GA-P55aUD3/i5-750/ATI 5770.

 

Boots OK with r4211 compiled with XCODE5 settings in Lion (ebuild.sh & Xcode 4.6.3)

and boots OK with r4211 compiled with XCODE5 settings in High Sierra (ebuild.sh & Xcode 8.3.3)... 

 

 

# boot6
./ebuild.sh -fr -x64 -D NO_GRUB_DRIVERS_EMBEDDED -D CHECK_FLAGS -D USE_APPLE_HFSPLUS_DRIVER 

# boot7
./ebuild.sh -fr -mc --no-usb -D NO_GRUB_DRIVERS_EMBEDDED -D CHECK_FLAGS -D USE_APPLE_HFSPLUS_DRIVER

 

 

 

 

 

OK, please try this one @tluck @ricoc90 @Badruzeus @fusion71au. Build with 

./ebuild.sh -t XCODE8 -fr -D NO_GRUB_DRIVERS_EMBEDDED -D NO_GRUB_DRIVERS --x64

attachicon.gif r4211-xcode8-p5.zip

 

syscl

 

CloverX64 r4211 built with ebuild.sh -t XCODE8 option ---> red screen as before

BootLog_r4211_XCODE5.zip

Clover r4211_XCODE5.zip

Link to comment
Share on other sites

When I compile r4211 with XCODE8 settings using Build_Clover script v4.5.3, get red screen error after selecting OSX Volume on my legacy desktop GA-P55aUD3/i5-750/ATI 5770.

 

Boots OK with r4211 compiled with XCODE5 settings in Lion (ebuild.sh & Xcode 4.6.3)...

OK, please try this one @tluck @ricoc90 @Badruzeus @fusion71au. Build with 

./ebuild.sh -t XCODE8 -fr -D NO_GRUB_DRIVERS_EMBEDDED -D NO_GRUB_DRIVERS --x64

r4211-xcode8-p5.zip

 

syscl

Link to comment
Share on other sites

×
×
  • Create New...