Jump to content

Leaderboard

Popular Content

Showing content with the highest reputation on 10/25/2020 in all areas

  1. 10.16 X99 OC 0.6.3 EFI sample https://www.insanelymac.com/applications/core/interface/file/attachment.php?id=359564
    3 points
  2. In Opencore (OC) 0.6.3, still in beta phase, a change has been made to SampleCustom.plist file, a new Memory section has been added within PlatformInfo, it describes a series of RAM memory parameters such as as defined in the SMBIOS specification. Note: article useful only for those cases where memory has errors in SMBIOS and it is convenient to define its parameters manually. Most users start from Sample.plist file (instead of SampleCustom.plist file) and Memory section is absent from it, this article is not necessary for them. The difference is the new CustomMemory key which, if set to true, requires filling the Memory section but, if set to false, allows that section to be completely omitted. Changes in OC 0.6.3 config.plist OC 0.6.3 presents significant changes in its operating characteristics, several of them aimed at improving its integration with Big Sur. It also presents changes in the structure of SampleCustom.plist. All of these changes are inside PlatformInfo. Removed SMBIOS key - MemoryFormFactor Added a new key called CustomMemory Added a new key called PlatformNVRAM with 5 subkeys: BID, FirmwareFeatures, FirmwareMask, MLB and ROM, some of these keys are still present in the SMBIOS section Added a new key called Memory with several subkeys related to RAM: DataWidth: bandwidth in bits of the bus, usually has the value of 64 ErrorConnection: primary method of error detection or correction (none, parity, ECC ...) FormFactor: type of used module (DIMM, SODIMM ...) MaxCapacity: maximum memory capacity, in bytes, supported by the motherboard TotalWidth: total value of bus width, in bits, including error correction channels if any; if they do not exist, TotalWidth value is identical to DataWidth Type: memory type (DDR3, DDR4 ...) DetailType: additional information about memory (Synchronous, Buffered, Unbuffered ...) Devices: this section describes the memory banks, occupied or not, and specifies characteristics of each one: AssetTag: memory module property tag BankLocator: name of the memory bank in which the module is housed DeviceLocator: description of the bank position on the motherboard Manufacturer: memory manufacturer PartNumber: code corresponding to the memory model SerialNumber: serial number of each module Size: size in MB, 0 indicates it is empty Speed: maximum memory speed in MT / s (megatransfers per second). How to know characteristics of RAM? In Linux world there has long been a tool called dmidecode that provides information about hardware as described in the BIOS according to SMBIOS / DMI standard. Acidanthera has a specific version for macOS, the current version is 3.2c (dmidecode-mac-3.2c.zip). It is downloaded as an executable dmidecode file that should be copied to the / usr / local / bin folder so that it is accessible in the PATH variable. With this tool we obtain information about the SMBIOS parameters of the computer through the I / O Registry. In this case, we are interested in the memory section, specifically regarding the 4 memory slots. For this we use dmidecode with -t memory modifier. This code, for example, is from my PC (only the data of the first memory bank is shown): > dmidecode -t memory # dmidecode 3.2c Scanning I/O Registry for entry point. SMBIOS 3.2 present. Physical Memory Array Location: System Board Or Motherboard Use: System Memory Error Correction Type: None Maximum Capacity: 0 kB Error Information Handle: No Error Number Of Devices: 4 Memory Device Array Handle: 0x009D Error Information Handle: No Error Total Width: 64 bits Data Width: 64 bits Size: 8 GB Form Factor: DIMM Locator: ChannelA-DIMM0 Bank Locator: BANK 0 Type: DDR4 Type Detail: Synchronous Speed: 3200 MT/s Manufacturer: Corsair Serial Number: 200400138487908 Asset Tag: 9876543210 Part Number: CMK16GX4M2B3200C16 (here goes on with parameters of the other 3 memory banks). With dmidecode we can find out some of the data to write in config.plist: DataWidth, ErrorConnection, FormFactor, TotalWidth, Type, TypeDetail, BankLocator, DeviceLocator, Speed, PartNumber, AssetTag and Manufacturer. The value of MaxCapacity is specified by the motherboard manufacturer. SerialNumber can be seen on the label attached to each memory module.Fill in the config.plist dataWith the data obtained from dmidecode, motherboard specifications, and memory module label, fields in config.plist can be filled in correctly. These data are from my system, you have to change them for yours if they are different.DataWidth: 64 (current RAM usually is 64-bit)ErrorCorrection: 3 (none)FormFactor: 9 (DIMM)MaxCapacity: 128 GB (137438953472 bytes)TotalWidth: 64 (matches DataWidth)Type: 26 (DDR4)TypeDetail: 128 (Synchronous, bit 7)AssetTag: 9876543210 (dmidecode)BankLocator: BANK 0 / BANK 1 / BANK 2 / BANK 3DeviceLocator: ChannelA-DIMM0 / ChannelA-DIMM1 / ChannelB-DIMM0 / ChannelB-DIMMManufacturer: CorsairPartNumber: CMK16GX4M2B3200C16 (manufacturer's label)SerialNumber: 200400138487908 / 200400138487909 (manufacturer's label)Size: 8 Gb per module (8000 MB)Speed: 3200 MT / s.Note: see the OpenCore Reference Manual (0.6.3) [2020.10.24] for allowed values in these keys.
    2 points
  3. So here is a 0.6 : CloverConfigPlistValidator0.6
    2 points
  4. Thanks a lot. I will try on my designare ex and let you (all) know. Best regards
    2 points
  5. No problem, I just quickly copied things from signature, just to have some content. You can delete the line. Basically, everyone manages his tab in this spreadsheet. If you add column, some formulas may have to be fixed, but I can do that. I was anyway thinking of adding a column for CPU generation (sandy bridge, Kaby Lake, etc.) just to have a quick overview of what hardware diversity we have. If the Clevo will come back very soon, you can keep it in the list and put N/A in result. If you deleted, you can put back the line anytime. The idea is to have a test "campaign" when we think we have a "Release candidate". For example, I'm currently solving a small thing about partition naming when there is more than one installation in the same container. No need for you to test that now. Let's say the next days I'm solving one or 2 other small things and then, nobody report anything. At this time, I'll ask for everyone to test the latest commit for regression. If there's none, we'll put a tag and have a new "version". If you find something, we fix and we'll go for another round. That's why I think it'll be less work also for you if we get organized. Sometime maybe you'll just have to test the RC commit and that's it. Knowing there sometimes few dozens of commits between versions, it'll save you time. There is also commits that we know are "intermediary" and doesn't work. Just a way of passing work between devs. These commits of course shouldn't be tested. So basically, I'll tell you here when we think we have a RC and when it's time for a round of tests.
    2 points
  6. @WizeMan - 'Teach dem so dat de gospel can reach dem' - A serious lack of research me thinks.
    2 points
  7. https://github.com/ic005k/Xplist Features include but are not limited to: * Lightweight and high performance * Automatic detection of OpenCore configuration files with corresponding operation prompts * Support multi-select operations (including copy, cut, delete, etc.) * Open source, cross-platform (currently supports win, mac, linux) * Humanized search function (a. Keyboard initial character search for each column of key, data type, and value within the expanded node range; b. Search box global search, one-time display of search results) * Fully comply with and conform to the technical specifications of plist files, data types are displayed exactly the same as plist text, without any escaping * Multi-tab view or edit files * Multi-language support (currently supports Chinese, Russian, English) * Drag and drop files to the software interface to open files, double-click to open files, file open history display, automatically load the last opened file * Add, remove, paste, cut, edit entries, etc., all included in Undo, Redo policy group, support undo and restore * Expand and collapse entries right-click menu, in different columns, with different effects * For values of data type, the hover window automatically displays the corresponding ASCII and Base64 values * When changing the data type, the value is automatically converted with it * Free to select the children under a node for A->Z sorting (currently no sorting of arrays) * Drag and drop to adjust the order of sibling items, up or down button to adjust the order of sibling items * Rich shortcut keys * Built-in update checking * If the currently opened file is modified by other programs, it automatically prompts whether to reload * Software UI adapts to various resolutions, supports winpe, linux livecd, etc. ...
    1 point
  8. Hey everyone, I'd like to organize a bit more the testing in Clover. The idea is have a "team" of people who agree to make some tests just before a release is about to created. A test is a combination of hardware/macOs version/Clover commit. By macOs version, I imply the latest minor of a major version. I don't think there is a need of keeping track of 10.15.1, 10.15.2 etc. for example. I've looked into few software, but they are a big too big for what we need. You have to create test plan, test cases, test steps, then plan runs... Instead, I'm thinking about a shared spreadsheet (Google docs, I guess), where everyone has a tab with a list of all their combination (hardware/macOs version). When we think about a release, I'll send you a message and you test each combination and report it in the spreadsheet. I think that is simple enough, and efficient for what we need. Of course, there is no commitment of keeping a hardware or a macOs. If you'd like to join with just your current configuration, that's fine. And you can stop after a while, no question will be asked. To go with that, maybe we can have a forum for beta-testers. There is a some intermediary commits that doesn't really need testing. So I think that if we are getting a little bit organized, it'll be also less work for you. Any idea are welcomed. Anyone up for that ? Send me, in private, an email address you've just created (with your insanely name if possible) so I can start a shared spreadsheet. Cheers.
    1 point
  9. BLUETOOTH INFO UPDATE: After updating all kexts in Clover today, the 2 Bluetooth firmware files do not cause anymore boot problems, so feel free to use them, replacing also your SSDT with this one. I am still on Clover 5122 Aorus Pro WiFi f12j REMEMBER TO UPDATE YOUR KEXTS, otherwise you may have boot problems. SSDT-6-A M I.aml IntelBluetooth.zip
    1 point
  10. Works as expected, many many thanks. Your plist looks so wonderful. Well done!
    1 point
  11. I confirm that "KernelCpu" disappear in April 2020. I can't find any trace of SlpSmiAtWake in March 2019. So it probably disappeared before that. Yes, false positive. I fixed it. Did I send you the wrong version ? Can't find a key "Connectors". I confirm it does nothing. In top of that, the array was empty. So I safely guess that this key can be deleted Mistake I guess. We have to validate that sample config.plist ! Doesn't exist. It's "AppleRTC" in "KernelAndKextPatches" section. Does the false positive warning still there with : CloverConfigPlistValidator0.5
    1 point
  12. Below "From here and below, use at your convience", I just copied your signature. You can reformat it, take way more space if you want, to describe better your configuration. You put as much or as little info you want. In short : this is your tab. There is just few rules that I'll write in a "Documentation tab". One for example is "Do not change the data validation that impose Pass/Fail/N/A". Well, that's almost it !. Put borders, change font, Change colum title, etc. etc. Make it clear and easy for you. Me ? I'll mainly check dashboard... Oh non, there an other rule : "Do not remove the total at the bottom of the "Config name" column, it's used in a formula.". Saying that, there's another one "You have to put something in the "Config name" column, because it's used to calculate the total of tests". Is that too many ? (kidding).
    1 point
  13. It's not very tidy and pretty now but this is how it looks inside. I'll probably put a bunch of SSD's in there but don't want to use the original HD rack so I'll make a new, simple one with better air flow. Plenty of fans at low speed gives pretty silent operation. The CPU coolers are actually a bit big but they fit perfectly when I kinda slid them together so the fins are interlaced.
    1 point
  14. Dude, ROM is not string type, it’s data. https://github.com/acidanthera/OpenCorePkg/blob/master/Docs/Sample.plist
    1 point
  15. My machine is very stable but I haven't managed to get proper power management or built in USB working. I haven't even bothered with audio since I'm using USB audio that's connected to the USB3 card. I'm using NullCPUPowerManagement.kext and it's switching the whole packages between 1596 MHz and 3591 MHz (one multiplier higher than X5690 specs). I have Enhanced Turbo turned on in BIOS. It stays cool with cores around 30-35 C under "idle" load with normal background tasks and around 68-70 C under Prime95 24 thread torture test with small FFT for maximum CPU stress/heat. I'm using MacPro6,1 SMBIOS. I will share a cleaned up OC EFI folder but also include the ssdt files I have for power management and USB map even though I can't make them work. I'm just not knowledgeable enough to get it to work fully but would love it if someone else want to give it a try. Including pics of the temps, frequencies and speed test of the NVME boot drive in the PCIe slot. If I run the speed test for a long time it can start throttling down due to higher temps. Also, this NVME drive should but be bootable by BIOS but I haven't gotten this to work so I'm using a regular SSD for OC (much preferred over USB). I might look into getting the factory overclocked RX 580 to perform better but I'm not too concerned.
    1 point
  16. I'd probably add that with CustomMemory set to false, that the memory section is not needed - and in fact can be completely gone similar to how various PlatformInfo children can not be filled in when Automatic is set to true.
    1 point
  17. @Jief_Machak wanted to bring to your attention, this strange bug, which happened to me, in the same way, as well as on the X570 and Z370, now also on the Z68 I was creating debug logs with all macOS on board, BS beta9, Catalina, Mojave and high sierra catalina start and rename its debugging Z68_5125 (master, commit 1934a83d8)_Catalina_OK_debug.log start mojave and rename its debug Z68_5125 (master, commit 1934a83d8)_Mojave_OK_debug.log start high sierra and rename its debug Z68_5125 (master, commit 1934a83d8)_HS_OK_changed_BS_debug.log all 3 times, started correctly without delay or apparent problems when I restart and then debug with BS, in the Clover GUI I find BS with high sierra icon; then I decide to start catalina using OpenCore, at the desktop I mount the preboot of big sur. the SystemVersion I found SystemVersion.plist the systemversion that I had previously backed up SystemVersion.plist-20A5384c.zip Having previously backed up SystemVersion, restoring is easy, but it's a very strange event this. Today on the X570 I started high sierra about ten times and there was no problem, the same applies to the Z370; now I'll see if the same thing happens on the Z68 to see if this bug only manifests itself the first time you start high sierra or figure out what the circumstances might be The version of Clover used is now the same for all hacks CLOVERX64--5125--1934a83d8.efi.zip after restoring the systemversion.plist i started high sierra 4 times but no bug happened i then tried to continue installing bs beta 9 update to beta 10 but the first time you restart it freezes, here's the debug log debug.log
    1 point
  18. Im sending via PM in the next few seconds. I just had to convert it to 19,1 for you.
    1 point
  19. I am using 19.1 but I have moved to Big Sur { if that matters }. So I am using your OC 0.6.3 with your favourite fenvi card - which works fine on Big Sur.
    1 point
  20. @photom Are you using smbios 19,1 or 1,1? Im going to send you a new EFI to use and test out for me if that ok? ive done a major rework of the ACPI and USB and would love a second opinion. That ok buddy?
    1 point
  21. jmackie, after many days of testing I found that this guide is not very well done. If I find out where I report to help this guide, I do that. This guide tells to use the SSDT-PLUG, but it doesn't work because it only takes the core 0 of the CPU, this makes the clock not go over 1.2GHz. Already, if you use SSDT-PM (which is said to use on Sandy and Ivy desktop but not for HEDT (Sandy-E, Ivy-E)) it works well, as the PM directs all colors of the CPU. But there is a catch ... Power Managemente only worked using SSDT-PM, if and only if the following Patch is used, both in Clover and OC: I'm thinking that to make BS work, have to find the right Patch for it. Can you tell me if you have this? Note: I don't know where I got this Patch that worked perfectly for me, I did it a long time ago, but Power Managemente in Catalina only works with this Patch.
    1 point
  22. I have exactly the same issue. I have been trying everything (I think) and I’m desperate to see if someone has found the way to get over this. thanks in advance!!
    1 point
  23. 1 point
  24. Could you please share your EFI for the X99 board with a different or no serial number? Thanks in advance!
    1 point
  25. that's not true, I installed it on a 55 GB partition. The installer shows different error for that (not enough space)
    1 point
  26. bluemac 2020 Screenshot: Animation: I have used this theme since I started using cl0ver. So though the years I have updated it accordingly and cause I have not been really active in the InsanelyMac community, as of recent, I figured I would share this for whomever is interested...updated to up to Big Sur and tested on Clover current version (r5122 at time of posting) Download: bluemac_2020.zip
    1 point
  27. I am Big Sur plus my tribute to Chadwick Boseman.
    1 point
  28. I'm not Big Sur but, OK.. fine. BigSur-Sunset-Retouched-1080.jpg.zip
    1 point
  29. Looking for an SArtFile.bin from either Leopard or Snow Leopard
    1 point
  30. Here is my humble effort.
    1 point
  31. http://www.wallpapermaiden.com/wallpaper/24582/grand-teton-national-park-sunset-hills/download/4096x2304
    1 point
  32. what's your problem ? here I found the BigSur beta10 installer solution to stay on the gray screen with the mouse pointer! - Solution Language to be used is US English in my case I use FR "french" where even in OpenCore it was the same but with the US language the installation goes without having this error! here I have several Hackintosh and where several HP between Laptop and All IN One I tested the installation and got it without problems even on a SandyBridge Laptop HD3000 that certainly still doesn't have a formula to activate this Graph my only problem is with the two All In One HP Envy Recline that neither with the OpenCore nor with the Clover I can install the BigSur directly through the USB installer, I was only successful in opening the Beta10 Installer in the Beta9 system and sending the installation to another SSD and then I managed to do everything for Clover! the error is that when i launch the USB installer i get the first phase after it restarts and at the second boot where there should be a 29 minute count it just restarts without a kernel panic! always getting this syntoma
    0 points
×
×
  • Create New...