magnifico Posted June 29, 2017 Share Posted June 29, 2017 strange problem on terminal not exit bdmesg why? Link to comment Share on other sites More sharing options...
Badruzeus Posted June 29, 2017 Share Posted June 29, 2017 strange problem on terminal not exit bdmesg why? Uhmmb, same here.. with Clover r4099 under 10.13 Beta 2 on Legacy-GPT... Link to comment Share on other sites More sharing options...
chris1111 Posted June 29, 2017 Share Posted June 29, 2017 Uhmmb, same here.. with Clover r4099 under 10.13 Beta 2 on Legacy-GPT... try this Clover bdmesg Log.zip 2 Link to comment Share on other sites More sharing options...
arsradu Posted June 29, 2017 Share Posted June 29, 2017 @Badruzeus, @magnifico, I also encountered this issue. All I did to fix it was the old Windows-like fix: restart. I guess it could be a bug..? 1 Link to comment Share on other sites More sharing options...
Badruzeus Posted June 29, 2017 Share Posted June 29, 2017 try this Uhmmb, I get an empty *.txt log Link to comment Share on other sites More sharing options...
chris1111 Posted June 29, 2017 Share Posted June 29, 2017 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" Link to comment Share on other sites More sharing options...
arsradu Posted June 29, 2017 Share Posted June 29, 2017 Depending on what you need (which, right now, I'm not sure exactly what it is), you could probably use the boot.log instead? It's just an idea. Link to comment Share on other sites More sharing options...
Badruzeus Posted June 29, 2017 Share Posted June 29, 2017 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.. Link to comment Share on other sites More sharing options...
cecekpawon Posted June 29, 2017 Share Posted June 29, 2017 Uhmmb, same here.. Its an efi app btw, download working binary here and install. Or take this as the finest replacement. 2 Link to comment Share on other sites More sharing options...
chris1111 Posted June 29, 2017 Share Posted June 29, 2017 But 10.11.6 on my "Macintosh HD" volume has.. here Me I only put bdmesg for my High Siera because this drive is boot by other drive 1 Link to comment Share on other sites More sharing options...
Badruzeus Posted June 29, 2017 Share Posted June 29, 2017 Its an efi app btw, download working binary here and install. Or take this as the finest replacement. Thanks @cecekpawon, now it works.. #Edit: yeah @christ1111.. I then manually installed it on /usr/local/bin 1 Link to comment Share on other sites More sharing options...
chris1111 Posted June 29, 2017 Share Posted June 29, 2017 Thanks @cecekpawon, now it works.. #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 1 Link to comment Share on other sites More sharing options...
Badruzeus Posted June 29, 2017 Share Posted June 29, 2017 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... 1 Link to comment Share on other sites More sharing options...
magnifico Posted June 29, 2017 Share Posted June 29, 2017 old Windows-like fix what is this ? You mean OS windows? Link to comment Share on other sites More sharing options...
arsradu Posted June 29, 2017 Share Posted June 29, 2017 what is this ? You mean OS windows? Yeah. It's an analogy. Remember how everything seems to be fixed after a restart in Windows? Same here with that weird bdmesg issue. It was meant as a joke... Sorry, maybe it wasn't the best one. Link to comment Share on other sites More sharing options...
magnifico Posted June 29, 2017 Share Posted June 29, 2017 Its an efi app btw, download working binary here and install. Or take this as the finest replacement. work here now thz...but this is a bug clover ? Link to comment Share on other sites More sharing options...
cecekpawon Posted June 29, 2017 Share Posted June 29, 2017 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.. 1 Link to comment Share on other sites More sharing options...
magnifico Posted June 29, 2017 Share Posted June 29, 2017 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 ? Link to comment Share on other sites More sharing options...
Slice Posted June 29, 2017 Share Posted June 29, 2017 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] 1 Link to comment Share on other sites More sharing options...
PMheart Posted June 29, 2017 Share Posted June 29, 2017 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. Link to comment Share on other sites More sharing options...
gujiangjiang Posted June 30, 2017 Share Posted June 30, 2017 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... 从我的 iPhone 发送,使用 Tapatalk Link to comment Share on other sites More sharing options...
D-an-W Posted June 30, 2017 Share Posted June 30, 2017 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? Link to comment Share on other sites More sharing options...
arsradu Posted June 30, 2017 Share Posted June 30, 2017 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 2 Link to comment Share on other sites More sharing options...
D-an-W Posted June 30, 2017 Share Posted June 30, 2017 Thanks, was missing -lilubeta Link to comment Share on other sites More sharing options...
Badruzeus Posted June 30, 2017 Share Posted June 30, 2017 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 1 Link to comment Share on other sites More sharing options...
Recommended Posts