Micky1979 Posted December 26, 2015 Share Posted December 26, 2015 How can we extract it from the Apple Firmware for a newer version of HFSPlus.efi? because it is now old? Link to comment Share on other sites More sharing options...
smolderas Posted December 26, 2015 Share Posted December 26, 2015 because it is now old? Mine is from 2011. Is there any way to check the version? Link to comment Share on other sites More sharing options...
Micky1979 Posted December 26, 2015 Share Posted December 26, 2015 I just know that the Clover installer won't install VBoxHFS if it detects HFSPlus. Yea, also is why I have asked : if [[ -f "$EFI_ROOT_DIR/EFI/CLOVER/$driver_dir"/HFSPlus.efi || \ -f "$EFI_ROOT_DIR/EFI/CLOVER/$driver_dir"/HFSPlus-32.efi || \ -f "$EFI_ROOT_DIR/EFI/CLOVER/$driver_dir"/HFSPlus-64.efi ]]; then echo >> "$install_log" echo "Removing $driver_dir/$driver_name driver because HFSPlus driver present" >> "$install_log" rm -f "$EFI_ROOT_DIR/EFI/CLOVER/$driver_dir/$driver_name" fi ..but Donwload Fritz has has provided a good explanation: possible = yes Link to comment Share on other sites More sharing options...
mhaeuser Posted December 26, 2015 Share Posted December 26, 2015 Possible != good idea, because best practise is only one of them. 2 Link to comment Share on other sites More sharing options...
Micky1979 Posted December 26, 2015 Share Posted December 26, 2015 Mine is from 2011. Is there any way to check the version? no idea, but if contains: 0000000000003a9a db "Apple_Boot", 0 ; XREF=sub_cf5+400 0000000000003aa5 db "Apple_HFS", 0 ; XREF=sub_cf5+434 0000000000003aaf db "Apple_HFSX", 0 ; XREF=sub_cf5+468 0000000000003aba db "Apple_Recovery", 0 maybe is up-to-date Possible != good idea, because best practise is only one of them. Ok: automatic remove of one of the two if someone need it, this is the assembly code decompiling the binary:HFSPlus.efi.asm.zip 64 bit Link to comment Share on other sites More sharing options...
smolderas Posted December 27, 2015 Share Posted December 27, 2015 no idea, but if contains: 0000000000003a9a db "Apple_Boot", 0 ; XREF=sub_cf5+400 0000000000003aa5 db "Apple_HFS", 0 ; XREF=sub_cf5+434 0000000000003aaf db "Apple_HFSX", 0 ; XREF=sub_cf5+468 0000000000003aba db "Apple_Recovery", 0 maybe is up-to-date Ok: automatic remove of one of the two if someone need it, this is the assembly code decompiling the binary:HFSPlus.efi.asm.zip 64 bit I would like to check it myself. How did you decompile it? Link to comment Share on other sites More sharing options...
Micky1979 Posted December 27, 2015 Share Posted December 27, 2015 Hopper Disassembler v3 1 Link to comment Share on other sites More sharing options...
Slice Posted December 28, 2015 Share Posted December 28, 2015 Hi all and happy Christmas holidays! There is no problem to have both HFSPlus.efi and VBoxHFS.efi. I don't remember which one will be a winner but both works fine. VBoxHFS.efi understands symlinks vs Apple's driver but it is slower if it does matter. No more differences. 1 Link to comment Share on other sites More sharing options...
Codinger Posted December 28, 2015 Share Posted December 28, 2015 Hopper Disassembler v3 Link to comment Share on other sites More sharing options...
Andres ZeroCross Posted December 28, 2015 Share Posted December 28, 2015 Hi, anybody have same problem with me??I get kernel panic about FakeSMC.kext several times, after pres "reset button" to reboot for once or twice then i can get desktop.I used Latest FakeSMC and Clover.Thanks before Link to comment Share on other sites More sharing options...
Slice Posted December 28, 2015 Share Posted December 28, 2015 I have not latest FakeSMC and it works without problems. See my signature. Link to comment Share on other sites More sharing options...
magnifico Posted December 28, 2015 Share Posted December 28, 2015 Hi, anybody have same problem with me?? I get kernel panic about FakeSMC.kext several times, after pres "reset button" to reboot for once or twice then i can get desktop. I used Latest FakeSMC and Clover. Thanks before wich version? I have not latest FakeSMC and it works without problems. See my signature. me too Link to comment Share on other sites More sharing options...
chris1111 Posted December 28, 2015 Share Posted December 28, 2015 wich version? me too no probleme here Link to comment Share on other sites More sharing options...
magnifico Posted December 28, 2015 Share Posted December 28, 2015 no probleme here No friend here too work perfect Link to comment Share on other sites More sharing options...
driftwood Posted December 28, 2015 Share Posted December 28, 2015 Andres, Im on 10.11.3 beta and no problems here. Gigabyte Z170X Gaming G1 Im on 618 Link to comment Share on other sites More sharing options...
analogo Posted December 28, 2015 Share Posted December 28, 2015 Hello.. because I cannot start a new topic in Clover, I post it here.. My DUAL XEON Build is working, but unresponsive and laggy like hell.. And therefore absolutely unusable.. I´m already trying for many weeks to solve the problem, and think it may be due to the CPU settings. Perhaps especially DUAL XEONs need to be particularly well configured and it occurred to me QPI and BusSpeed. http://clover-wiki.zetam.org/Configuration/CPU#cpu_qpi Which settings should I use? Because the description on Clover WIKI is confusing me.. Specs / XEON E5-2680 v3 Intel QPI Speed: 9.6 GT/s # of QPI Links: 2 http://ark.intel.com/products/81908/Intel-Xeon-Processor-E5-2680-v3-30M-Cache-2_50-GHz Specs / Asus Z10PE-D8 WS https://www.asus.com/Motherboards/Z10PED8_WS/specifications/ Another problem is, that Clover cannot correctly detect all eight 4GB RDIMMs. Therefore I had to insert them manually into the config.plist. Without, Clover only detects two RDIMMs, which is resulting in over 200000% memory pressure! In config.plist I tried Trust, FixSBUS and Halt Enabler. From the attached Boot Log file 0:102 0:002 Total Memory Slots Count = 2 0:102 0:000 Type 17 Index = 0 0:102 0:000 SmbiosTable.Type17->Speed = 2133MHz 0:102 0:000 SmbiosTable.Type17->Size = 4096MB 0:102 0:000 SmbiosTable.Type17->Bank/Device = NODE 1 DIMM_A1 0:102 0:000 Type 17 Index = 1 0:102 0:000 SmbiosTable.Type17->Speed = 2133MHz 0:102 0:000 SmbiosTable.Type17->Size = 4096MB 0:102 0:000 SmbiosTable.Type17->Bank/Device = NODE 1 DIMM_B1 0:102 0:000 Boot status=0 0:102 0:000 Clover revision: 3330 running on Z10PE-D8 WS ... 4:775 0:001 Trusting SMBIOS... 4:775 0:000 Detected alternating SMBIOS channel banks 4:775 0:000 Channels: 2 4:775 0:000 Interleave: 0 2 1 3 4 6 5 7 8 10 9 11 12 14 13 15 16 18 17 19 20 22 21 23 4:775 0:000 partNum=9ASF51272PZ-2G1A2 4:775 0:000 SMBIOS Type 17 Index = 0 => 0 0: 4:775 0:000 BANK0 DIMM0 2133MHz 4096MB 4:775 0:000 mTotalSystemMemory = 4096 4:775 0:000 partNum=9ASF51272PZ-2G1A2 4:775 0:000 SMBIOS Type 17 Index = 1 => 1 2: 4:775 0:000 BANK1 DIMM0 2133MHz 4096MB 4:775 0:000 mTotalSystemMemory = 8192 4:775 0:000 NumberOfMemoryDevices = 2 4:775 0:000 Type20[0]->End = 0x3FFFFF, Type17[0] = 0x1000 4:775 0:000 Type20[1]->End = 0x7FFFFF, Type17[1] = 0x3000 4:775 0:000 RSDT 0x7AEC7028 4:775 0:000 FADT from RSDT: 0x7AEC7170 4:775 0:000 XSDT 0x7AEC70A0 4:775 0:000 FADT from XSDT: 0x7AEEE070 4:775 0:000 Xsdt reallocation done 4:775 0:000 old FADT length=10C 4:775 0:000 Found OperationRegion(PSYS, SystemMemory, 7BD27000, ...) 4:775 0:000 Found OperationRegion(HPTC, SystemMemory, FED1F404, ...) 4:775 0:000 Found OperationRegion(MCTL, SystemMemory, 80000188, ...) 4:775 0:000 Found OperationRegion(MCTL, SystemMemory, 80008188, ...) 4:775 0:000 Found OperationRegion(MCTL, SystemMemory, 80009188, ...) 4:775 0:000 Found OperationRegion(MCTL, SystemMemory, 80010188, ...) 4:775 0:000 Found OperationRegion(MCTL, SystemMemory, 80011188, ...) 4:775 0:000 Found OperationRegion(MCTL, SystemMemory, 80012188, ...) 4:775 0:000 Found OperationRegion(MCTL, SystemMemory, 80013188, ...) 4:775 0:000 Found OperationRegion(MCTL, SystemMemory, 80018188, ...) 4:775 0:000 Found OperationRegion(MCTL, SystemMemory, 80019188, ...) 4:775 0:000 Found OperationRegion(MCTL, SystemMemory, 8001A188, ...) 4:775 0:000 Found OperationRegion(MCTL, SystemMemory, 8001B188, ...) 4:776 0:000 Found OperationRegion(MCTL, SystemMemory, 88000188, ...) 4:776 0:000 Found OperationRegion(MCTL, SystemMemory, 88008188, ...) 4:776 0:000 Found OperationRegion(MCTL, SystemMemory, 88009188, ...) 4:776 0:000 Found OperationRegion(MCTL, SystemMemory, 88010188, ...) 4:776 0:000 Found OperationRegion(MCTL, SystemMemory, 88011188, ...) 4:776 0:000 Found OperationRegion(MCTL, SystemMemory, 88012188, ...) 4:776 0:000 Found OperationRegion(MCTL, SystemMemory, 88013188, ...) 4:776 0:000 Found OperationRegion(MCTL, SystemMemory, 88018188, ...) 4:776 0:000 Found OperationRegion(MCTL, SystemMemory, 88019188, ...) 4:776 0:000 Found OperationRegion(MCTL, SystemMemory, 8801A188, ...) 4:776 0:000 Found OperationRegion(MCTL, SystemMemory, 8801B188, ...) 4:776 0:000 Found OperationRegion(MCTL, SystemMemory, 80000188, ...) 4:776 0:000 Found OperationRegion(MCTL, SystemMemory, 80008188, ...) 4:776 0:000 Found OperationRegion(MCTL, SystemMemory, 80009188, ...) 4:776 0:000 Found OperationRegion(MCTL, SystemMemory, 80010188, ...) 4:776 0:000 Found OperationRegion(MCTL, SystemMemory, 80011188, ...) 4:776 0:000 Found OperationRegion(MCTL, SystemMemory, 80012188, ...) 4:776 0:000 Found OperationRegion(MCTL, SystemMemory, 80013188, ...) 4:776 0:000 Found OperationRegion(MCTL, SystemMemory, 80018188, ...) 4:776 0:000 Found OperationRegion(MCTL, SystemMemory, 80019188, ...) 4:776 0:000 Found OperationRegion(MCTL, SystemMemory, 8001A188, ...) 4:776 0:000 Found OperationRegion(MCTL, SystemMemory, 8001B188, ...) 4:776 0:000 Found OperationRegion(MCTL, SystemMemory, 80000188, ...) 4:776 0:000 Found OperationRegion(MCTL, SystemMemory, 80008188, ...) 4:776 0:000 Found OperationRegion(MCTL, SystemMemory, 80009188, ...) 4:776 0:000 Found OperationRegion(MCTL, SystemMemory, 80010188, ...) 4:776 0:000 Found OperationRegion(MCTL, SystemMemory, 80011188, ...) 4:776 0:000 Found OperationRegion(MCTL, SystemMemory, 80012188, ...) 4:776 0:000 Found OperationRegion(MCTL, SystemMemory, 80013188, ...) 4:776 0:000 Found OperationRegion(MCTL, SystemMemory, 80018188, ...) 4:776 0:000 Found OperationRegion(MCTL, SystemMemory, 80019188, ...) 4:776 0:000 Found OperationRegion(MCTL, SystemMemory, 8001A188, ...) 4:776 0:000 Found OperationRegion(RAMW, SystemMemory, 7BD4A018, ...) 4:776 0:000 Found OperationRegion(TMMB, SystemMemory, FED40000, ...) 4:776 0:000 Found OperationRegion(CRBD, SystemMemory, FED40000, ...) 4:776 0:000 Found OperationRegion(TPMR, SystemMemory, FFFFFFFF, ...) 4:781 0:005 Apply DsdtFixMask=0x00000080 old way 4:781 0:000 drop _DSM mask=0x0000 Many thanks for your help! Boot Log.zip Link to comment Share on other sites More sharing options...
Fljagd Posted December 28, 2015 Share Posted December 28, 2015 perfect for me 0:102 0:000 Clover revision: 3330 running on All Series 0:102 0:000 ... with board X99-A 0:102 0:000 CPU Vendor = 756E6547 Model=306F2 0:102 0:000 The CPU not supported turbo 0:102 0:000 BrandString = Intel(R) Core(TM) i7-5820K CPU @ 3.30GHz Link to comment Share on other sites More sharing options...
insanelyDeepak Posted December 29, 2015 Share Posted December 29, 2015 happy Christmas holidays! to Slice and all Dev Link to comment Share on other sites More sharing options...
Andres ZeroCross Posted December 29, 2015 Share Posted December 29, 2015 Thank for the responds.Here i upload image about version of my FakeSMC / Clover.It's looks my Notebook (Asus A455LF-WX016D) has same problem too. And i use same File Maybe there is miss configurations, but i don't know what it's.What should i upload to analyze this problem, because it's random. Sometimes it boot nicely without hard reset when kernel panic about FakeSMC. Link to comment Share on other sites More sharing options...
Slice Posted December 29, 2015 Share Posted December 29, 2015 Thank for the responds. Here i upload image about version of my FakeSMC / Clover. It's looks my Notebook (Asus A455LF-WX016D) has same problem too. And i use same File Maybe there is miss configurations, but i don't know what it's. What should i upload to analyze this problem, because it's random. Sometimes it boot nicely without hard reset when kernel panic about FakeSMC. You have a version 6.18 I have a version 3.41 See the difference. Link to comment Share on other sites More sharing options...
Andres ZeroCross Posted December 29, 2015 Share Posted December 29, 2015 You have a version 6.18 I have a version 3.41 See the difference. But i have SkyLake and Broadwell system. I need sensor for my chipset,, Kozlek have built FakeSMC for SkyLake Supported. I need it Link to comment Share on other sites More sharing options...
Slice Posted December 29, 2015 Share Posted December 29, 2015 But i have SkyLake and Broadwell system. I need sensor for my chipset,, Kozlek have built FakeSMC for SkyLake Supported. I need it But it crashes? Link to comment Share on other sites More sharing options...
UNOE Posted December 29, 2015 Share Posted December 29, 2015 I think you need to manually copy the driver into the appropriate clover subfolder for where it loads its kexts in EUFI mode bootup if your planning on using Clover to boot up your system. I went as far using genffs to convert that driver into a module I plugged into my bios with mmtool. That module now is hosted on Win-Raid. If your having space problems I recommend deleting non essential modules from your bios or using tools like ozmtool to compress your bios files. Then insert it and then you can boot from EUFI mode. +1 Got my Samsung 950 pro. Install went well just updated clover. Then threw in NvmExpressDxe-64.efi into the 'drivers64UEFI' folder (even though the installer doesn't allow that, had to install it on a USB stick with BiosblockIO then get the driver NvmExpressDxe-64.efi and throw it in 'drivers64UEFI' folder). After that I threw the NVMeGeneric.kext into Kext folder for clover. Booted to a OS X installer USB stick used restore option with Disk utility to copy me oldssd install and booted up 950 pro just fine from the EFI boot loader on OldSSD. Then installed clover with EFI on the 950 pro, transferred over all my files from my clover folder under EFI partition from old SSD to 950 pro EFI partition. Now booting with just 950 pro with EFI. I'm very surprised EFI boot works with my old board with no bios update. I still have my same 4.6ghz overclock running a much older 4205 bios version on Rampage IV Extreme x79 with 3930K (Sandybridge-E). This was not support to be possible. I see threads were people are having issues with it showing up as EFI drive. Other people says it shows up as PATA. But not mine it showed as EFI drive. Again this was with no bios mods, or bios updates, just same old bios been using for years. Clover EFI doing all the work My speeds on old SSD were around 480 read and 410 write. Now doing 2050 Read and 880 write. Edit : edited post its actually even older bios 4205 released in mid 2013. I don't have much desire to update bios because the clock speeds were really nice and stable. I was doing 4.9ghz in windows. Link to comment Share on other sites More sharing options...
Slice Posted December 29, 2015 Share Posted December 29, 2015 But i have SkyLake and Broadwell system. I need sensor for my chipset,, Kozlek have built FakeSMC for SkyLake Supported. I need it OK, I also added many new hardware into revision 21. See my signature for download. 1 Link to comment Share on other sites More sharing options...
Andres ZeroCross Posted December 29, 2015 Share Posted December 29, 2015 Sometimes and random. If there is no solution then i will keep to wait, i still can use my hackie Btw, thanks Slice. I will try it. Many thanks Link to comment Share on other sites More sharing options...
Recommended Posts