Cyberdevs Posted July 3, 2018 Share Posted July 3, 2018 (edited) @apianti Hi man, First of all thanks for all your efforts on Clover V3. I booted my system from the Clover V3 and here is the log. I hope it helps. BOOTX64.EFI.log.zip Edited July 3, 2018 by Cyberdevs 2 Link to comment Share on other sites More sharing options...
apianti Posted July 3, 2018 Author Share Posted July 3, 2018 4 hours ago, Matgen84 said: Ok for FAT32. In Parallels, output files (log.txt) is empty What type of VM in Parallels: macOS or windows? It shouldn't matter which type of VM, I usually choose other to test. You set up the serial output file for Parallels from the link I gave above? It's empty? Are you sure? Does it say it's zero bytes in Finder? What about the log from the USB? Should be \EFI\BOOT\BOOTX.efi.log. Link to comment Share on other sites More sharing options...
apianti Posted July 3, 2018 Author Share Posted July 3, 2018 3 hours ago, Cyberdevs said: @apianti Hi man, First of all thanks for all your efforts on Clover V3. I booted my system from the Clover V3 and here is the log. I hope it helps. Sure does. Here's some good stuff: 1 | Available | 0x000000000003cfd5 | 0x0000000000100000-0x000000003d0d4fff | 0x0000000000000000 | 0x000000000000000f Completely available memory for kernelspace. Still there later: 1 | Available | 0x000000000003cfd5 | 0x0000000000100000-0x000000003d0d4fff | 0x0000000000000000 | 0x000000000000000f There's a tiny problem, should not be detected as virtual machine but the rest looks great: Firmware: American Megatrends 2.50 Virtual machine: Yes Architecture: X64 Multiprocessing: Yes CPU: Intel(R) Core(TM) i7-6700K CPU @ 4.00GHz CPU signature: 0x000506e3 CPU family: 0x6 CPU model: 0x5e CPU stepping: 0x3 Found CPU000 at 0:0:0, Boot services, Enabled, Healthy Found CPU001 at 0:0:1, Enabled, Healthy Found CPU002 at 0:1:0, Enabled, Healthy Found CPU003 at 0:1:1, Enabled, Healthy Found CPU004 at 0:2:0, Enabled, Healthy Found CPU005 at 0:2:1, Enabled, Healthy Found CPU006 at 0:3:0, Enabled, Healthy Found CPU007 at 0:3:1, Enabled, Healthy CPU logical processors: 8 CPU physical processors: 4 CPU packages: 1 This is the good stuff right here, seems that most AMI firmware actually correctly implements MP services, ran a separate thread here: GUI: 2018-07-03 17:27:4294967336.000 Found CPU000 at 0:0:0, Boot services, Enabled, Healthy Found CPU001 at 0:0:1, Enabled, Healthy Found CPU002 at 0:1:0, Enabled, Healthy Found CPU003 at 0:1:1, Enabled, Healthy Found CPU004 at 0:2:0, Enabled, Healthy Found CPU005 at 0:2:1, Enabled, Healthy Found CPU006 at 0:3:0, Enabled, Healthy Found CPU007 at 0:3:1, Enabled, Healthy GUI starting in multithreaded mode ... Thread starting on processor CPU001 ... Success GUI multithread start ... Success Looks good, I already see the mistake I made in the virtual machine detection. I'm going to update the ISO and put it in the the first post from now on. I wonder why your log started with zeros though.... That's a mystery. 2 Link to comment Share on other sites More sharing options...
Cyberdevs Posted July 3, 2018 Share Posted July 3, 2018 10 minutes ago, apianti said: Sure does. Here's some good stuff: Completely available memory for kernelspace. Still there later: There's a tiny problem, should not be detected as virtual machine but the rest looks great: This is the good stuff right here, seems that most AMI firmware actually correctly implements MP services, ran a separate thread here: Looks good, I already see the mistake I made in the virtual machine detection. I'm going to update the ISO and put it in the the first post from now on. I wonder why your log started with zeros though.... That's a mystery. I'm glad it was helpful. But if that's a mystery to you my friend I have nothing to say I will post another log from my IvyBridge (Asus P8H77 -M LE) and another legacy Asus P7H55 (if legacy booting is supported) later. 1 Link to comment Share on other sites More sharing options...
apianti Posted July 3, 2018 Author Share Posted July 3, 2018 3 minutes ago, Cyberdevs said: I'm glad it was helpful. But if that's a mystery to you my friend I have nothing to say I will post another log from my IvyBridge (Asus P8H77 -M LE) and another legacy Asus P7H55 (if legacy booting is supported) later. You would have to use clover firmware to boot legacy and put either \EFI\BOOT\BOOTX64.efi or \EFI\CLOVER\X64\GUI.efi at \EFI\CLOVER\CLOVERX64.efi. But yes that would be helpful. 2 Link to comment Share on other sites More sharing options...
droples Posted July 4, 2018 Share Posted July 4, 2018 CloverV3,Asus Z170m-Plus 2BOOTX64.EFI.txt 1 Link to comment Share on other sites More sharing options...
Pavo Posted July 4, 2018 Share Posted July 4, 2018 Here you go @apianti Asus z9pe-d8 ws BOOTX64.EFI.log 1 Link to comment Share on other sites More sharing options...
Slice Posted July 4, 2018 Share Posted July 4, 2018 Tested on QEMU booted by legacy Clover Gui.efi.log.zip Link to comment Share on other sites More sharing options...
Cyberdevs Posted July 4, 2018 Share Posted July 4, 2018 Here a log with the latest ISO you posted on my Asus P8H77 BOOTX64.EFI.Asus.P8H77M.LE.log.zip Link to comment Share on other sites More sharing options...
Matgen84 Posted July 4, 2018 Share Posted July 4, 2018 Hi Strangely with latest ISO, I've two entries in my UEFI BIOS for USB pendrive First, I've got black screen Second, the system does not take it into account. It starts on clover GUI for High Sierra (my HDD) USB pen drive seems to be unbootable? I don't understand why. Link to comment Share on other sites More sharing options...
apianti Posted July 4, 2018 Author Share Posted July 4, 2018 Thanks everyone, these are helpful. I still messed up the virtual machine detection, because it says you all have virtual machines.... 3 hours ago, Matgen84 said: Hi Strangely with latest ISO, I've two entries in my UEFI BIOS for USB pendrive First, I've got black screen Second, the system does not take it into account. It starts on clover GUI for High Sierra (my HDD) USB pen drive seems to be unbootable? I don't understand why. Seems you maybe made the USB wrong? I'm unsure... Did you have legacy on the drive before? 1 Link to comment Share on other sites More sharing options...
Matgen84 Posted July 4, 2018 Share Posted July 4, 2018 (edited) 18 minutes ago, apianti said: Thanks everyone, these are helpful. I still messed up the virtual machine detection, because it says you all have virtual machines.... Seems you maybe made the USB wrong? I'm unsure... Did you have legacy on the drive before? I use two different USB (FAT32/GUID) with same issue. All my hard drive is in UEFI mode and USB Installer works perfectly. How to make USB correctly on macOS? Edited July 4, 2018 by Matgen84 Link to comment Share on other sites More sharing options...
apianti Posted July 4, 2018 Author Share Posted July 4, 2018 10 minutes ago, Matgen84 said: I use two different USB (FAT32/GUID) with same issue. All my hard drive is in UEFI mode and USB Installer works perfectly. How to make USB correctly on macOS? You should just need to restore the image on to the usb formatted as FAT32. The ISO is already correct structure for EFI. Was it detected it as legacy or UEFI? Link to comment Share on other sites More sharing options...
Matgen84 Posted July 4, 2018 Share Posted July 4, 2018 (edited) 4 minutes ago, apianti said: You should just need to restore the image on to the usb formatted as FAT32. The ISO is already correct structure for EFI. Was it detected it as legacy or UEFI? I try again and report. Since first test, USB is detected as UEFI. Et: I've this message when restore ISO. Edited July 4, 2018 by Matgen84 Link to comment Share on other sites More sharing options...
Pavo Posted July 4, 2018 Share Posted July 4, 2018 6 minutes ago, Matgen84 said: I try again and report. Since first test, USB is detected as UEFI. Et: I've this message when restore ISO. Just take a normal Installer USB, mount the ESP and delete the EFI folder in it, mount the ISO and take EFI folder in the ISO and put it in the mounted ESP of the installer, that's all I did Link to comment Share on other sites More sharing options...
Matgen84 Posted July 4, 2018 Share Posted July 4, 2018 (edited) 23 minutes ago, Pavo said: Just take a normal Installer USB, mount the ESP and delete the EFI folder in it, mount the ISO and take EFI folder in the ISO and put it in the mounted ESP of the installer, that's all I did OK I try with Installer USB EDIT: Same issue "black screen" if I use working High Sierra USB Installer with CloverV3-expermiental.. Edited July 4, 2018 by Matgen84 Link to comment Share on other sites More sharing options...
apianti Posted July 4, 2018 Author Share Posted July 4, 2018 2 minutes ago, Matgen84 said: I use this method for previous test. With no success: I can't boot from USB Hmmm, I've updated the ISO, try that. But there is no log being created? Link to comment Share on other sites More sharing options...
Matgen84 Posted July 4, 2018 Share Posted July 4, 2018 (edited) 16 minutes ago, apianti said: Hmmm, I've updated the ISO, try that. But there is no log being created? I try and report Edit: it's better. a few lines scroll quickly before the black screen. But still no log Edited July 4, 2018 by Matgen84 Link to comment Share on other sites More sharing options...
apianti Posted July 4, 2018 Author Share Posted July 4, 2018 3 hours ago, Matgen84 said: I try and report Edit: it's better. a few lines scroll quickly before the black screen. But still no log Oh, can you try this. Create \EFI\CLOVER\CLOVER.plist and put this inside: <?xml version="1.0" encoding="utf-8"?> <!DOCTYPE plist PUBLIC "-//Apple//DTD PLIST 1.0//EN" "http://www.apple.com/DTDs/PropertyList-1.0.dtd"> <plist version="1.0"> <dict> <key>Boot</key> <dict> <key>Console</key> <false /> </dict> </dict> </plist> There seems to be a problem maybe with the console display switch. Hmmmm... 1 Link to comment Share on other sites More sharing options...
Matgen84 Posted July 4, 2018 Share Posted July 4, 2018 (edited) 43 minutes ago, apianti said: Oh, can you try this. Create \EFI\CLOVER\CLOVER.plist and put this inside: <?xml version="1.0" encoding="utf-8"?> <!DOCTYPE plist PUBLIC "-//Apple//DTD PLIST 1.0//EN" "http://www.apple.com/DTDs/PropertyList-1.0.dtd"> <plist version="1.0"> <dict> <key>Boot</key> <dict> <key>Console</key> <false /> </dict> </dict> </plist> There seems to be a problem maybe with the console display switch. Hmmmm... I try and report Edit: It's a little bit better. A few lines scroll already quickly before the black screen. But I saw one loading success loading default configuration lines. No log Edited July 4, 2018 by Matgen84 Link to comment Share on other sites More sharing options...
apianti Posted July 4, 2018 Author Share Posted July 4, 2018 2 hours ago, Matgen84 said: I try and report Edit: It's a little bit better. A few lines scroll already quickly before the black screen. But I saw one loading success loading default configuration lines. No log I can't reproduce this at all... Can you please try the newest ISO I've uploaded in the first post? How are you making the USB? Also I notice that copy and pasting the code above gives some random characters at the end for some reason. They were there when I pasted it, lol. 2 Link to comment Share on other sites More sharing options...
Matgen84 Posted July 5, 2018 Share Posted July 5, 2018 (edited) 8 hours ago, apianti said: I can't reproduce this at all... Can you please try the newest ISO I've uploaded in the first post? How are you making the USB? Also I notice that copy and pasting the code above gives some random characters at the end for some reason. They were there when I pasted it, lol. Hi 1. recreate USB FAT32/ GUID on Disk Utility 2. Copy/Paste EFI folder from Clover-3.0-experimental 3. create manually Clover.plist from your code 4. Copy Clover.plist /EFI/CLOVER 5. Boot on USB pendrive The log file is attached: Asus p8z77-v Pro - Corei7 3770K - Chipset Intel 7 series Great job Thanks BOOTX64.EFI.log Edited July 5, 2018 by Matgen84 1 Link to comment Share on other sites More sharing options...
apianti Posted July 5, 2018 Author Share Posted July 5, 2018 2 hours ago, Matgen84 said: Hi 1. recreate USB FAT32/ GUID on Disk Utility 2. Copy/Paste EFI folder from Clover-3.0-experimental 3. create manually Clover.plist from your code 4. Copy Clover.plist /EFI/CLOVER 5. Boot on USB pendrive The log file is attached: Asus p8z77-v Pro - Corei7 3770K - Chipset Intel 7 series Great job Thanks BOOTX64.EFI.log Okay cool, does it work without the Clover.plist I gave? Or still no? 1 Link to comment Share on other sites More sharing options...
Matgen84 Posted July 5, 2018 Share Posted July 5, 2018 (edited) 27 minutes ago, apianti said: Okay cool, does it work without the Clover.plist I gave? Or still no? I test and report EDIT: still don't work without Clover.plist Edited July 5, 2018 by Matgen84 Link to comment Share on other sites More sharing options...
apianti Posted July 5, 2018 Author Share Posted July 5, 2018 6 hours ago, Matgen84 said: I test and report EDIT: still don't work without Clover.plist I wonder why the console mode switch is failing. I have changed the setting default so the user has to select changing the console mode. 1 Link to comment Share on other sites More sharing options...
Recommended Posts