Jump to content
30960 posts in this topic

Recommended Posts

Uhmmb, I get an empty *.txt log

So  bdmesg is not in usr/local/bin

 

Edit

when you have bdmesg in usr/local/bin/

Edited the file manually because I put new file after you are download

 

open ~/Desktop/"Clover bdmesg Log.txt"

So  bdmesg is not in usr/local/bin

 

Edit

when you have bdmesg in usr/local/bin/

Edited the file manually because I put new file after you are download

 

open ~/Desktop/"Clover bdmesg Log.txt"

 

But 10.11.6 on my "Macintosh HD" volume has..

post-826765-0-02200000-1498754916_thumb.png

Its an efi app btw, download working binary here and install. Or take this as the finest replacement.

 

Thanks @cecekpawon, now it works..  :lol:

#Edit: yeah @christ1111.. I then manually installed it on /usr/local/bin

post-826765-0-35207000-1498755954_thumb.png

  • Like 1

Thanks @cecekpawon, now it works..  :lol:

#Edit: yeah @christ1111.. I then manually installed it on /usr/local/bin

This is the bad part of High Sierra 

Normally the Clover Package do this but now all things need install manually

  • Like 1

This is the bad part of High Sierra 

Normally the Clover Package do this but now all things need install manually

 

I use "Macintosh HD's ESP" (10.11.6) as target volume while installing Clover package...

post-826765-0-86017700-1498756924_thumb.png

  • Like 1

As previously mentioned by @chris1111, the installation may not work properly with High Sierra.. I dont know. But im preferred shell command (taken from here) to do this job..

Nahh ..i dont use hisierra..the problem does it on EL and SIERRA ..maybe is a bug clover ?

If I don't change anything in FakeSMC, then won't the smc-rev key in the default Info.plist be incorrect (for MacPro6,1)?

You may correct FakeSMC.info.plist.

But take into account that this value will be overriden by the value from Clover through the kext HWInfo.kext

Is there any link for that DumpUefiCalls driver? Thanks :)

If you compile Clover by yourself then catch

/src/edk2/Build/Clover/RELEASE_XCODE5/X64/DumpUefiCalls.efi[/size]

  • Like 1

You may correct FakeSMC.info.plist.

But take into account that this value will be overriden by the value from Clover through the kext HWInfo.kext

If you compile Clover by yourself then catch

/src/edk2/Build/Clover/RELEASE_XCODE5/X64/DumpUefiCalls.efi[/size]

Thanks! I've never tried HWInfo.kext before. I don't think this is a bad idea to test. ;)

Great. I saw the way to get it a little bit earlier but thanks anyway.

Hi folks,

I have High Sierra installed on a second partition alongside Sierra which has Clover installed and running in UEFI.

Can I please ask what needs to be added to the High Sierra install to get Clover fully setup as it seems I don't just simply install it as with previous new releases?

I will ask this bit elsewhere too but does it need anything special to get the audio working using AppleALC?

Hi folks,

 

I have High Sierra installed on a second partition alongside Sierrs which has Clover installed and running in UEFI.

 

Can I please ask what needs to be added to the High Sierra install to get Clover fully setup as it seems I don't just simply install it as with previous new releases?

 

I will ask this bit elsewhere too but does it need anything special to get the audio working using AppleALC?

Yes. Two boot flags, until the final release.

 

-alcbeta and -lilubeta

 

 

Sent from my iPhone using Tapatalk

  • Like 2

Does Clover Legacy support APFS.efi?

When i put apfs.efi into Drive64 and install the system with apfs but after reboot it shows this...

 

I'm on Clover Legacy with apfs.efi. It works..  :)

 

 

 

2:737  0:000  Starting Clover revision: 4101 on CLOVER EFI
2:737  0:000  Build with: [Args: -mc --no-usb -D NO_GRUB_DRIVERS_EMBEDDED -D CHECK_FLAGS -t XCODE8 | -D DISABLE_USB_SUPPORT -D NO_GRUB_DRIVERS_EMBEDDED -D CHECK_FLAGS -D USE_BIOS_BLOCKIO -D USE_LOW_EBDA -a X64 -b RELEASE -t XCODE8 -n 5 | OS: 10.11.6 | XCODE: 8.2]
2:737  0:000  SelfDevicePath=PcieRoot(0x0)\Pci(0x1F,0x2)\Sata(0x0,0x0,0x0)\HD(1,GPT,313A28C7-F4BF-42D0-B42E-2AD281EEB011,0x800,0x64000) @1EC4F118
2:737  0:000  SelfDirPath = \EFI\CLOVER
2:737  0:000  === [ Get Smbios ] ========================================
2:737  0:000  ...memory OK
2:737  0:000  Running on: 'K43SJ' with board 'K43SJ'
2:737  0:000  === [ GetCPUProperties ] ==================================
2:737  0:000  CPU Vendor = 756E6547 Model=206A7
2:737  0:000   The CPU supported SSE4.1
2:737  0:000  The CPU not supported turbo
2:737  0:000  BrandString = Intel(R) Core(TM) i3-2330M CPU @ 2.20GHz
2:737  0:000  FSBFrequency = 100 MHz, DMI FSBFrequency = 100 MHz, Corrected FSBFrequency = 100 MHz
2:737  0:000  Threads: 4
2:737  0:000  Cores: 2
2:737  0:000  FSB: 25 MHz
2:737  0:000  CPU: 2200 MHz
2:737  0:000  TSC: 2200 MHz
2:737  0:000  PIS: 100 MHz
2:737  0:000  === [ GetDevices ] ========================================
2:737  0:000  PCI (00|01:00.00) : 10DE 1050 class=030000
2:737  0:000   - GFX: Model=Asus GeForce GT 520M family D9 (Nvidia)
2:737  0:000  PCI (00|01:00.01) : 10DE 0E08 class=040300
2:737  0:000   - HDMI Audio: 
2:738  0:000  PCI (00|03:00.00) : 168C 002B class=028000
2:738  0:000   - WIFI: Vendor=Atheros
2:738  0:000  PCI (00|05:00.00) : 10EC 8168 class=020000
2:738  0:000   - LAN: 0 Vendor=Realtek
2:738  0:000  PCI (00|00:1F.03) : 8086 1C22 class=0C0500
2:738  0:000  === [ GetDefaultSettings ] ================================
2:757  0:019  EFI\CLOVER\config.plist loaded: Success
2:757  0:000  === [ GetListOfThemes ] ===================================
2:758  0:000  - [00]: Movies
2:772  0:014  === [ Found config plists ] ===============================
2:772  0:000  - config.plist
2:772  0:000  === [ GetEarlyUserSettings ] ==============================
2:773  0:000  === [ LoadDrivers ] =======================================
2:784  0:011  Loading AppleImageCodec-64.efi  status=Success
2:785  0:000  Loading AppleKeyAggregator-64.efi  status=Success
2:785  0:000  Loading AppleUITheme-64.efi  status=Success
2:785  0:000  Loading FirmwareVolume-64.efi  status=Success
2:785  0:000  Loading FSInject-64.efi  status=Success
2:786  0:000  Loading apfs.efi  status=Success
2:818  0:031   - driver needs connecting
2:818  0:000  Loading SMCHelper-64.efi  status=Success
2:818  0:000  1 drivers needs connecting ...
2:818  0:000  PlatformDriverOverrideProtocol->GetDriver overriden
2:818  0:000  APFS driver loaded 

 

 

  • Like 1

Hey guys,

 

I was wondering if there's a way to use "Startup Disk" in system preferences to choose the next startup disk and somehow clover manages to boot from the selected disk. Is that even possible?

 

I noticed when I change the startup disk these files change in macOS /System/Library/CoreServices/.disk_label, /System/Library/CoreServices/.disk_label_2x and some other files in /private/var/db/uuidtext

All the information used by Startup Disk is available to Clover, so it should be possible to add code to Clover and or it's scripts to do that if it doesn't already.

 

.disk_label is a graphics image of the text displayed under the disk icon in the Startup Manager UI (an EFI program on Macs that is displayed when you hold the option key at startup). .disk_label_2x is the same thing for retina displays. The bless command does some of the same things as the Startup Disk preferences panel, including creating those graphics images. The bless command affects some nvram variables. It also affects some information in the HFS header of an HFS formatted disk.

nvram -p
echo "==============================================================================="
bless --verbose --getboot
echo "==============================================================================="
bless --verbose --info
echo "==============================================================================="
ioreg -w 0 -n AppleEFINVRAM | sed -n -E "/^[ \|]+[ ]+(\".*)$/s//\1/p;"
efi-boot-device is the xml representation of the boot device. efi-boot-device-data is a binary representation (using EFI device path protocol). If this is an HFS disk, then the HFS header has the id of the boot folder and the id of the efi boot file.

 

bless --verbose will tell you which EFI boot variable that uses the efi-boot-device. GUID 8BE4DF61-93CA-11D2-AA0D-00E098032B8C is for the efi owned set of nvram variables, and Boot0080 is the name of the nvram variable in that set containing the EFI device path of the boot device. Apple owned nvram variables will use a different guid.

 

If you select a Windows disk in Startup Disk preferences panel, and it is legacy (BIOS) instead of EFI, then the efi-boot-device-data will be the path of an EFI program used for booting BootCamp (an image file in EFI). The BootCampHD nvram variable will then be the device path of the disk that should have it's MBR boot code executed by Apple's BIOS boot loader.

 

efi-boot-device-data can also be a path to an efi program like Clover.

  • Like 3

All the information used by Startup Disk is available to Clover, so it should be possible to add code to Clover and or it's scripts to do that if it doesn't already.

 

.disk_label is a graphics image of the text displayed under the disk icon in the Startup Manager UI (an EFI program on Macs that is displayed when you hold the option key at startup). .disk_label_2x is the same thing for retina displays. The bless command does some of the same things as the Startup Disk preferences panel, including creating those graphics images. The bless command affects some nvram variables. It also affects some information in the HFS header of an HFS formatted disk.

nvram -p
echo "==============================================================================="
bless --verbose --getboot
echo "==============================================================================="
bless --verbose --info
echo "==============================================================================="
ioreg -w 0 -n AppleEFINVRAM | sed -n -E "/^[ \|]+[ ]+(\".*)$/s//\1/p;"
efi-boot-device is the xml representation of the boot device. efi-boot-device-data is a binary representation (using EFI device path protocol). If this is an HFS disk, then the HFS header has the id of the boot folder and the id of the efi boot file.

 

bless --verbose will tell you which EFI boot variable that uses the efi-boot-device. GUID 8BE4DF61-93CA-11D2-AA0D-00E098032B8C is for the efi owned set of nvram variables, and Boot0080 is the name of the nvram variable in that set containing the EFI device path of the boot device. Apple owned nvram variables will use a different guid.

 

If you select a Windows disk in Startup Disk preferences panel, and it is legacy (BIOS) instead of EFI, then the efi-boot-device-data will be the path of an EFI program used for booting BootCamp (an image file in EFI). The BootCampHD nvram variable will then be the device path of the disk that should have it's MBR boot code executed by Apple's BIOS boot loader.

 

efi-boot-device-data can also be a path to an efi program like Clover.

 

That's really a great explanation on the subject, Thanks a lot :)

Hi guys!

 

Where is Clover installed on APFS volumes? Meaning, if you have an APFS formatted drive, where will Clover put its files and folders in order to boot that system?

Clover puts the files in the root of the selected drive and you have to manually move them to the esp.

 

Sent from my SM-G930F using Tapatalk

hmmm ... for some reason I can't load config.plist anymore, even with EFI mounted. I can open it in Wrangler but in CConfigurator everything is blank? I can create enteries like SMBIOS os thats working ok. Any ideas?

Seems like a corrupt config.plist.

 

Sent from my SM-G930F using Tapatalk

×
×
  • Create New...