Jump to content

Clover General discussion


ErmaC
30,171 posts in this topic

Recommended Posts

I had newer kabylake refresh that can boot uefi with clover and extract dsdt and several ssdt there when booting clover.

 

question: my old sandy bridge u36sd support Mbr and partial uefi (no csm option). I want to extract dsdt and ssdt using clover. I had install clover ESP on USB GUID flash disk with Mbr boot0af wrote in USB.

but I can't find the f2 f4 menu to extract dsdt .

AIDA64 extract dsdt and several ssdt that I need to compare.

aipcdump and old iasl -g can't dump ssdt.

I had newer kabylake refresh that can boot uefi with clover and extract dsdt and several ssdt there when booting clover.

 

question: my old sandy bridge u36sd support Mbr and partial uefi (no csm option). I want to extract dsdt and ssdt using clover. I had install clover ESP on USB GUID flash disk with Mbr boot0af wrote in USB.

but I can't find the f2 f4 menu to extract dsdt/ssdt.

AIDA64 extract dsdt and several ssdt that I need to compare.

aipcdump and old iasl -g can't dump ssdt.

Link to comment
Share on other sites

6 hours ago, Maniac10 said:

 

I'll test the newer version (tried it a while ago) but AptioMemoryFix is the only driver capable of booting my system.

 

He is talking about AptioMemoryFix, the installer apparently does not correctly select the driver when upgrading or something as some previous options were removed, I think.

  • Like 2
Link to comment
Share on other sites

9 hours ago, apianti said:

 

He is talking about AptioMemoryFix, the installer apparently does not correctly select the driver when upgrading or something as some previous options were removed, I think.

Can be true. From a certain commit I've added a suffix for them and the identifier can be different. If that is the case, next time will be fine.

  • Like 2
Link to comment
Share on other sites

I'm just curious about this, so...

<key>BooterConfig</key>
	<string>0x28</string>
	<key>CsrActiveConfig</key>
	<string>0x67</string>

^ does it fully disable SIP, or not? Thanks.

Screenshot 85.png

Edited by Badruzeus
Link to comment
Share on other sites

30 minutes ago, Badruzeus said:

I'm just curious about this, so...


<key>BooterConfig</key>
	<string>0x28</string>
	<key>CsrActiveConfig</key>
	<string>0x67</string>

^ does it fully disable SIP, or not? Thanks.

As far as I know 0x67 disables SIP but it won't allow for untrusted kexts to be loaded, if you run "csrutil status" in terminal you can see which part of SIP is disabled, I guess with 0x3e7 SIP will be totally disabled and it will expose macOS even more.

 

Addition:

Take a look at this for more info

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

So I just downloaded the 10.13.6 installer from the app store so I can update my usb stick and after the installer downloaded it opened and it said "To install mac os high sierra a firmware update is required."  I'm not wanting to go through the installation or anything, I'm just curious on this message.

 

My clover boot log shows:

 

2:912  0:000  Using ProductName from config: MacPro5,1
2:912  0:000  BiosVersion: not set, Using BiosVersion from clover
2:912  0:000  BiosVersion: MP51.88Z.0087.B00.1804181525
2:912  0:000  BiosReleaseDate: 04/18/18
2:912  0:000  Using FirmwareFeatures from clover: 0xE80FE137
2:912  0:000  Using FirmwareFeaturesMask from clover: 0xFF1FFF3F
2:912  0:000  PlatformFeature will not set in SMBIOS
 

 

Is this bios version correct?  I'm using the clover autogenerated one.  Clover 4586 is what I am on.

Link to comment
Share on other sites

On 7/14/2018 at 1:11 AM, Badruzeus said:

I'm just curious about this, so...


<key>BooterConfig</key>
	<string>0x28</string>
	<key>CsrActiveConfig</key>
	<string>0x67</string>

^ does it fully disable SIP, or not? Thanks.

Screenshot 85.png

how about 0x77?

  • Like 3
Link to comment
Share on other sites

7 minutes ago, Alpha22 said:

Thanks, resolved

I installed Clover on the hard drive but when I restart my black screen

boot only from usb

 

advice

Unknown.  

Add your complete hardware information to your signature. Upload the EFI folder from your EFI partition of the Hard Drive (remove any serial numbers from SMBIOS and RTvariables from config beforehand)

Compare with the EFI folder on the USB drive.

If you can boot with the USB but not from the Hard Drive, something is most likely different either in the installation method (UEFI vs Legacy mode), drivers, or config.

Edited by arsradu
Link to comment
Share on other sites

18 minutes ago, arsradu said:

Unknown.  

Add your complete hardware information to your signature. Upload the EFI folder from your EFI partition of the Hard Drive (remove any serial numbers from SMBIOS and RTvariables from config beforehand)

Compare with the EFI folder on the USB drive.

If you can boot with the USB but not from the Hard Drive, something is most likely different either in the installation method (UEFI vs Legacy mode), drivers, or config.

hardware:
Asus P5Q Deluxe
Intel Q9550
Video GT240

installation in legasy

the EFI folder of the usb is the same as the EFI folder on the hard disk

Edited by Alpha22
Link to comment
Share on other sites

1 minute ago, arsradu said:

Compare with the EFI folder on the USB drive.

If you can boot with the USB but not from the Hard Drive, something is most likely different either in the installation method (UEFI vs Legacy mode), drivers, or config.

Waiting for the second part.

the EFI folder of the usb is the same as the EFI folder on the hard disk

Link to comment
Share on other sites

1 minute ago, Alpha22 said:

the EFI folder of the usb is the same as the EFI folder on the hard disk

I would double check that first. Something has to be different. Just to be sure, I would try to replace the EFI folder of the Hard Drive with the one from the USB drive and see if it makes any difference.

Link to comment
Share on other sites

13 minutes ago, arsradu said:

I would double check that first. Something has to be different. Just to be sure, I would try to replace the EFI folder of the Hard Drive with the one from the USB drive and see if it makes any difference.

I copied the EFI folder of usb to the hard disk

version of Clover 4558

the problem remains not booting from hard disk

Link to comment
Share on other sites

7 minutes ago, Alpha22 said:

I copied the EFI folder of usb to the hard disk

version of Clover 4558

the problem remains not booting from hard disk

Upload your EFI folder here for analysis. Remove serial numbers as suggested before.

Also, check your BIOS.

Link to comment
Share on other sites

7 minutes ago, arsradu said:

Upload your EFI folder here for analysis. Remove serial numbers as suggested before.

Also, check your BIOS.

this is the EFI folder of the hard disk

I had the same problem if I remember correctly in El Capitan and they suggested me to format the hard disk EFI

but I do not remember how to do this

EFI.zip

Edited by Alpha22
Link to comment
Share on other sites

20 minutes ago, Alpha22 said:

this is the EFI folder of the hard disk

I had the same problem if I remember correctly in El Capitan and they suggested me to format the hard disk EFI

but I do not remember how to do this

EFI.zip

 

Disk Utility -> select the Hard Drive (not the partition) -> click Erase -> make sure the Scheme is set to GUID partition map and Format is MacOS Extended (Journaled).

 

233805444_Screenshot2018-07-15at23_40_13.png.69b4e1e09d54d592c103492559c378ff.png

 

Edited by arsradu
Link to comment
Share on other sites

8 hours ago, arsradu said:

 

Disk Utility -> select the Hard Drive (not the partition) -> click Erase -> make sure the Scheme is set to GUID partition map and Format is MacOS Extended (Journaled).

 

233805444_Screenshot2018-07-15at23_40_13.png.69b4e1e09d54d592c103492559c378ff.png

 

I did not understand, but I have to redo a new installation setting the disk as reported

Link to comment
Share on other sites

 

Hi guys,

 

Is anyone else having Error 65 in MainMenu when compiling Clover on Mojave (using UDK2018)?

 

========= Translating Resources ========
/Users/jimmy/src/UDK2018/Clover/CloverPackage/package/../../../../opt/local
Updating 'en' strings file for CloverUpdater... done
Updating 'en' strings file for Clover Preference Panel... done
Updating strings file for Clover Preference Panel... done
 (170 entries)
Building CloverUpdater application...
** BUILD FAILED **


The following build commands failed:
	CompileXIB /Users/jimmy/src/UDK2018/Clover/CloverPackage/CloverUpdater/src/zh_TW.lproj/MainMenu.xib
	CompileXIB /Users/jimmy/src/UDK2018/Clover/CloverPackage/CloverUpdater/src/zh_CN.lproj/MainMenu.xib
	CompileXIB /Users/jimmy/src/UDK2018/Clover/CloverPackage/CloverUpdater/src/uk.lproj/MainMenu.xib
(3 failures)
make: *** [CloverUpdater] Error 65
logout
Saving session...
...copying shared history...
...saving history...truncating history files...
...completed.

[Process completed]

 

 

 

 

  • Like 1
Link to comment
Share on other sites

8 hours ago, arsradu said:

 

Hi guys,

 

Is anyone else having Error 65 in MainMenu when compiling Clover on Mojave (using UDK2018)?

 


========= Translating Resources ========
/Users/jimmy/src/UDK2018/Clover/CloverPackage/package/../../../../opt/local
Updating 'en' strings file for CloverUpdater... done
Updating 'en' strings file for Clover Preference Panel... done
Updating strings file for Clover Preference Panel... done
 (170 entries)
Building CloverUpdater application...
** BUILD FAILED **


The following build commands failed:
	CompileXIB /Users/jimmy/src/UDK2018/Clover/CloverPackage/CloverUpdater/src/zh_TW.lproj/MainMenu.xib
	CompileXIB /Users/jimmy/src/UDK2018/Clover/CloverPackage/CloverUpdater/src/zh_CN.lproj/MainMenu.xib
	CompileXIB /Users/jimmy/src/UDK2018/Clover/CloverPackage/CloverUpdater/src/uk.lproj/MainMenu.xib
(3 failures)
make: *** [CloverUpdater] Error 65
logout
Saving session...
...copying shared history...
...saving history...truncating history files...
...completed.

[Process completed]

 

 

 

 

 

Same issue here with r4606 using UDK2018 on Mojave.

 

[SOLVED] Remove previous version, Install Xcode 10 Beta 4 and reinstall command lines tools (I'm not sure is necessary)

In cvad's script: I comment make pkg (line 502),  uncomment ./makepkg (line 501)

All work fines

 

Edited by Matgen84
Link to comment
Share on other sites

×
×
  • Create New...