arsradu Posted September 19, 2019 Share Posted September 19, 2019 25 minutes ago, ori said: I understand that other forums are blocked here, but I found only one example in this forum. Google has shown more. I tried 2x16GB, 4x16GB and no problem. I have 128GB of RAM on X299 and no problem with Clover. It seems to me an allocation error when configuring the Z390 and 32GB of RAM. Ok, so it is a problem with this specific configuration. I'm guessing the RAM sticks are in the correct slots according to the motherboard's user manual, right? Just trying to exclude the most common mistakes. Cause if everything is done correctly (and my guess is that it is)...then the most unlikely possibility becomes the only logical one. 1 Link to comment Share on other sites More sharing options...
iCanaro Posted September 19, 2019 Share Posted September 19, 2019 tested boot arguments slide=0 Link to comment Share on other sites More sharing options...
ori Posted September 19, 2019 Share Posted September 19, 2019 11 minutes ago, Matgen84 said: What BIOS version? Set DVMT Pre-Allocated to 32M. This single change enabled the use of the standard driver OsxAptioFix3Drv.efi BIOS: Driver: ApfsDriverLoader.efi DataHubDxe.efi FSInject.efi OsxAptioFix3Drv.efi PartitionDxe.efi SMCHelper.efi VBoxHfs.efi Still the same. I tried the same drivers as I have in Open Core (ApfsDriverLoader.efi HfsPlus.efi OsxAptioFix2Drv-free2000.efi) and it also doesn't work on Clover 1 minute ago, arsradu said: Ok, so it is a problem with this specific configuration. I'm guessing the RAM sticks are in the correct slots according to the motherboard's user manual, right? Just trying to exclude the most common mistakes. Cause if everything is done correctly (and my guess is that it is)...then the most unlikely possibility becomes the only logical one. I tried singly, twice in each slot. The effect is the same. 3 minutes ago, iCanaro said: tested boot arguments slide=0 slide=0 dart=0 darkwake=no keepsyms=1 debug=0x100 The effect is the same. 1 Link to comment Share on other sites More sharing options...
Matgen84 Posted September 20, 2019 Share Posted September 20, 2019 11 hours ago, ori said: BIOS: Driver: ApfsDriverLoader.efi DataHubDxe.efi FSInject.efi OsxAptioFix3Drv.efi PartitionDxe.efi SMCHelper.efi VBoxHfs.efi Still the same. I tried the same drivers as I have in Open Core (ApfsDriverLoader.efi HfsPlus.efi OsxAptioFix2Drv-free2000.efi) and it also doesn't work on Clover I tried singly, twice in each slot. The effect is the same. slide=0 dart=0 darkwake=no keepsyms=1 debug=0x100 The effect is the same. Multiple time, I asked you to post your EFI Folder??? Try to contact @MaLd0n here or on olarila.com, he have the same mobo but with i9-9900K 1 Link to comment Share on other sites More sharing options...
Sherlocks Posted September 21, 2019 Share Posted September 21, 2019 @Slice real mac smbios info from system profiler like this https://forums.macrumors.com/threads/macos-10-15-catalina-on-unsupported-macs.2183772/post-27749989 but we always include apple rom info can we choice enable/disable to hide this apple rom info part? Link to comment Share on other sites More sharing options...
Slice Posted September 21, 2019 Share Posted September 21, 2019 2 hours ago, Sherlocks said: @Slice real mac smbios info from system profiler like this https://forums.macrumors.com/threads/macos-10-15-catalina-on-unsupported-macs.2183772/post-27749989 but we always include apple rom info can we choice enable/disable to hide this apple rom info part? It is also hackintosh, see Lilu on screens. Real Mac doesn't show this info if it has SMBIOS 3.0. To do this in Clover we have to remake a huge part of codes. 2 Link to comment Share on other sites More sharing options...
Sherlocks Posted September 21, 2019 Share Posted September 21, 2019 27 minutes ago, Slice said: It is also hackintosh, see Lilu on screens. Real Mac doesn't show this info if it has SMBIOS 3.0. To do this in Clover we have to remake a huge part of codes. i think if apple rom info shown on t2 chip or each model smbios version, we just divide part according to model. Link to comment Share on other sites More sharing options...
Badruzeus Posted September 21, 2019 Share Posted September 21, 2019 Still curious how VMWare did this uhmmb... 1 Link to comment Share on other sites More sharing options...
Slice Posted September 21, 2019 Share Posted September 21, 2019 5 hours ago, Sherlocks said: i think if apple rom info shown on t2 chip or each model smbios version, we just divide part according to model. We can't produce smbios3 until we will know all details what is allowed and what influences on system. 1 Link to comment Share on other sites More sharing options...
Matgen84 Posted September 22, 2019 Share Posted September 22, 2019 Hi @vector sigma @Slice Thanks a lot for last commit on Clover Template It is possible to have: Clover v2.5 RELEASE (nb_commits-last-commits) both in Installer and Read Info (Version line). Link to comment Share on other sites More sharing options...
vector sigma Posted September 22, 2019 Share Posted September 22, 2019 53 minutes ago, Matgen84 said: It is possible to have: Clover v2.5 RELEASE (nb_commits-last-commits) both in Installer and Read Info (Version line). No because breaks Clover updater 1 Link to comment Share on other sites More sharing options...
artur_pt Posted September 22, 2019 Share Posted September 22, 2019 hello with new Xcode 11 buildme is giving me this error compiling gettext gettext.make.log.txt.zip thanks Link to comment Share on other sites More sharing options...
vector sigma Posted September 22, 2019 Share Posted September 22, 2019 56 minutes ago, artur_pt said: hello with new Xcode 11 buildme is giving me this error compiling gettext gettext.make.log.txt.zip thanks Hi, what's the result of 'which libtool'? Link to comment Share on other sites More sharing options...
artur_pt Posted September 22, 2019 Share Posted September 22, 2019 30 minutes ago, vector sigma said: Hi, what's the result of 'which libtool'? hello i set to buildme xcode8 thanks Link to comment Share on other sites More sharing options...
vector sigma Posted September 22, 2019 Share Posted September 22, 2019 3 minutes ago, artur_pt said: hello i set to xcode8 thanks Anyway I've just chaged buildgettext.sh to use default PATH enviroment variable, so it should use default and expected command lines. P.S. at github atm 1 Link to comment Share on other sites More sharing options...
artur_pt Posted September 22, 2019 Share Posted September 22, 2019 3 hours ago, vector sigma said: Anyway I've just chaged buildgettext.sh to use default PATH enviroment variable, so it should use default and expected command lines. P.S. at github atm hello sorry not solved thanks 1 Link to comment Share on other sites More sharing options...
Matgen84 Posted September 22, 2019 Share Posted September 22, 2019 (edited) Hi @artur_pt @vector sigma All works fine here: XCode11/ Builme (Github) on my Mojave rig option 7: update Clover option 2: make pkg gettext 0.20.1 installed correctly Edited September 22, 2019 by Matgen84 Link to comment Share on other sites More sharing options...
artur_pt Posted September 22, 2019 Share Posted September 22, 2019 (edited) hello not here gettext 0.20.1 error compiling Catalina last beta with Xcode 11 anyway if I use opt folder from Mojave, works good thanks Edited September 22, 2019 by artur_pt 1 Link to comment Share on other sites More sharing options...
fusion71au Posted September 22, 2019 Share Posted September 22, 2019 On 9/21/2019 at 9:15 PM, vector sigma said: ' I got this: ------------------------------------------------------------------------ cat: vers.txt: No such file or directory buildme, Clover v2.5k r (SHA: not a git repo) Anyway we can ask Mr. @fusion71au if can test the chage in Linux.... Well on my system it worked even when not symlink, but it doesn't matter really. Your version: On 9/21/2019 at 3:55 AM, vector sigma said: cd "$(dirname $([ -L $0 ] && readlink $0 || echo $0))" is probably better as it works on both of our system. Remains to be tested in linux... @vector sigma and @Pene, Either cd "$(dirname "$(readlink "$0")")" or cd "$(dirname $([ -L $0 ] && readlink $0 || echo $0))" works in Linux Mint 19.1, running buildme script from link (in secondary location) to actual script in ~/src/CloverBootloader... fusion71au@GA-P55A-UD3:~$ cd src fusion71au@GA-P55A-UD3:~/src$ ./buildme ------------------------------------------------------------------------ buildme, Clover v2.5k r5089 (SHA: 0f1bca80) TOOLCHAIN: GCC53 (override example: './buildme XCODE8') 1) build Clover 2) make pkg 3) make iso 4) build all 5) test build (no autogen, no boot files) 6) status 7) update Clover 8) update Clover (reset changes) 9) show diff 10) open drivers directory 11) clean BaseTools 12) quit Please enter your choice: 1 Loading previous configuration from /home/fusion71au/src/CloverBootloader/Conf/BuildEnv.sh WORKSPACE: /home/fusion71au/src/CloverBootloader EDK_TOOLS_PATH: /home/fusion71au/src/CloverBootloader/BaseTools CONF_PATH: /home/fusion71au/src/CloverBootloader/Conf [BUILD CLOVER] TOOLCHAIN_DIR: /home/fusion71au/src/CloverBootloader/../opt/local No clover toolchain found ! Install on your system or define the TOOLCHAIN_DIR variable. Notice the buildme script in Linux is not fully automatic since I still need to run source edksetup.sh in order to set correct TOOLCHAIN_DIR in /usr... Spoiler fusion71au@GA-P55A-UD3:~/src$ cd CloverBootloader fusion71au@GA-P55A-UD3:~/src/CloverBootloader$ source edksetup.sh Loading previous configuration from /home/fusion71au/src/CloverBootloader/Conf/BuildEnv.sh WORKSPACE: /home/fusion71au/src/CloverBootloader EDK_TOOLS_PATH: /home/fusion71au/src/CloverBootloader/BaseTools CONF_PATH: /home/fusion71au/src/CloverBootloader/Conf fusion71au@GA-P55A-UD3:~/src/CloverBootloader$ ./ebuild.sh -fr -mc --no-usb -D NO_GRUB_DRIVERS_EMBEDDED -D USE_APPLE_HFSPLUS_DRIVER -t GCC53 TOOLCHAIN_DIR: /usr NASM_PREFIX: /usr/bin/ NASM_VER: 2.13.02 Building from: /home/fusion71au/src/CloverBootloader Running edk2 build for CloverX64 using the command: build -D DISABLE_USB_SUPPORT -D NO_GRUB_DRIVERS_EMBEDDED -D USE_APPLE_HFSPLUS_DRIVER --conf=/home/fusion71au/src/CloverBootloader/Conf -D USE_BIOS_BLOCKIO -D USE_LOW_EBDA -p Clover.dsc -a X64 -b RELEASE -t GCC53 -n 5 Build environment: Linux-4.15.0-64-generic-x86_64-with-LinuxMint-19.1-tessa Build start time: 08:37:29, Sep.23 2019 WORKSPACE = /home/fusion71au/src/CloverBootloader EDK_TOOLS_PATH = /home/fusion71au/src/CloverBootloader/BaseTools CONF_PATH = /home/fusion71au/src/CloverBootloader/Conf Architecture(s) = X64 Processing meta-data .Build target = RELEASE Toolchain = GCC53 Active Platform = /home/fusion71au/src/CloverBootloader/Clover.dsc .... done! Building ... /home/fusion71au/src/CloverBootloader/Library/MemLogLibDefault/MemLogLibDefault.inf [X64] Building ... /home/fusion71au/src/CloverBootloader/MdePkg/Library/BaseReportStatusCodeLibNull/BaseReportStatusCodeLibNull.inf [X64] Building ... /home/fusion71au/src/CloverBootloader/MdePkg/Library/UefiDriverEntryPoint/UefiDriverEntryPoint.inf [X64] Building ... /home/fusion71au/src/CloverBootloader/MdePkg/Library/UefiLib/UefiLib.inf [X64] Building ... /home/fusion71au/src/CloverBootloader/MdePkg/Library/BasePciLibCf8/BasePciLibCf8.inf [X64] PS: I can't reply in original thread since I am not a developer 1 Link to comment Share on other sites More sharing options...
LockDown Posted September 23, 2019 Share Posted September 23, 2019 (edited) what is the pros of having clover compiled in GCC53? Edited September 23, 2019 by ellaosx Link to comment Share on other sites More sharing options...
Slice Posted September 23, 2019 Share Posted September 23, 2019 2 hours ago, ellaosx said: what is the pros of having clover compiled in GCC53? Size only. Developers have new testing for eliminate internal errors but users didn't see them. 2 Link to comment Share on other sites More sharing options...
LockDown Posted September 23, 2019 Share Posted September 23, 2019 (edited) @vector sigma A suggestion to your buildme. If i made a typo: ./buildme XCODE9 build: : warning: Tool chain [XCODE9] is not defined build.py... : error 4000: Not available [XCODE9] not defined. No toolchain available for build! - Failed - Build end time: 16:20:41, Sep.23 2019 Build total time: 00:00:00 then the script goes back to main selection screen. ------------------------------------------------------------------------ buildme, Clover v2.5k r5089 (SHA: 0f1bca8) TOOLCHAIN: XCODE9 (override example: './buildme XCODE8') 1) build Clover 2) make pkg 3) make iso 4) build all 5) test build (no autogen, no boot files) 6) status 7) update Clover 8) update Clover (reset changes) 9) show diff 10) open drivers directory 11) clean BaseTools 12) quit Please enter your choice: but still, the typo (XCODE9) is still defined as the current flag. I think it's better to exit the script and start over again, isnt it? Edited September 23, 2019 by ellaosx 1 Link to comment Share on other sites More sharing options...
Matgen84 Posted September 23, 2019 Share Posted September 23, 2019 19 minutes ago, ellaosx said: @vector sigma A suggestion to your buildme. If i made a typo: ./buildme XCODE9 build: : warning: Tool chain [XCODE9] is not defined build.py... : error 4000: Not available [XCODE9] not defined. No toolchain available for build! - Failed - Build end time: 16:20:41, Sep.23 2019 Build total time: 00:00:00 then the script goes back to main selection screen. ------------------------------------------------------------------------ buildme, Clover v2.5k r5089 (SHA: 0f1bca8) TOOLCHAIN: XCODE9 (override example: './buildme XCODE8') 1) build Clover 2) make pkg 3) make iso 4) build all 5) test build (no autogen, no boot files) 6) status 7) update Clover 8) update Clover (reset changes) 9) show diff 10) open drivers directory 11) clean BaseTools 12) quit Please enter your choice: but still, the typo (XCODE9) is still defined as the current flag. I think it's better to exit the script and start over again, isnt it? Just my opinion: Why do you want to use XCODE9? Buildme works with MYTOOLCHAIN=XCODE8 to build Clover: take a look in the script. Link to comment Share on other sites More sharing options...
LockDown Posted September 23, 2019 Share Posted September 23, 2019 (edited) @Matgen84 I was referring for a possibility of users chance of a "typo". It doesnt mean i use XCODE9 Edited September 23, 2019 by ellaosx 1 Link to comment Share on other sites More sharing options...
arsradu Posted September 23, 2019 Share Posted September 23, 2019 Hi guys, Could anyone, please, replace all ftp:// calls in buildgcc with https:// calls? I can't build Clover since I can't download GCC (port restricted). Link to comment Share on other sites More sharing options...
Recommended Posts