Jump to content

Leaderboard

Popular Content

Showing content with the highest reputation on 05/10/2019 in all areas

  1. While @Andrey1970 is right that we do not believe automatic tools can help people improve their experience, and thus are generally anticipate them, I do not believe we can stop people from writing them, and thus will try to be as constructive as possible to avoid extra harm from any side. OpenCore Configurator is an open source application and for this very reason, despite our personal views and no official recommendations, we will try to provide some help at the very least. Substantial differences in our preferences will not help much the process anyway. Regarding configuration changes, starting from 0.0.1 release we have version reporting (exposed through NVRAM). We demand this to be verified by configuration app to ensure compatibility (this is stated in the docs). — For the released version the warning should appear when the app is unaware of the version used. — For an unreleased version the warning should always appear. — For no version present another warning should appear. We do not care much whether the user decides to continue as long as he is informed about a potential incompatibility. We believe it is very important for the user to be aware of the problem if he still decides to use a configuration app. And the fact that every release has its documentation fixed makes it possible for a configuration app to be compatible with released versions at least in theory. Additionally to that I recently added differential documentation, showing changes between the configurations [1] across the releases. The file will be bundled with the release file, and should help everyone update accordingly to the latest release. Last but not least, while I cannot promise it, but we will try to find some resources to conduct a basic validation process to give recommendations in regards to decisions taken, which we consider to be wrong or improper. Closer to a more stable release of course. For example, recently we discovered that most third party tools reformat and reorder plist files, making their changes hard to discover [2]. If OpenCore Configurator is affected, we hope this is fixed. Thanks for the hard work, and peace [1] https://github.com/acidanthera/OpenCorePkg/tree/master/Docs/Differences [2] https://github.com/corpnewt/ProperTree/issues/5
    3 points
  2. Unfortunately, this project has come to a halt, at least for now. I don't have enough time to work on the project and it's lacking behind, so please don't use it for configuring OpenCore, it will produce broken configuration files. I will leave the source code on GitHub, so in case someone wants to take over the project, they can. original post: OpenCore Configurator Source
    2 points
  3. Nvidia web driver 387.10.10.10.40.127 for High Sierra 10.13.6 (17G6030) https://images.nvidia.com/mac/pkg/387/WebDriver-387.10.10.10.40.127.pkg
    2 points
  4. macOS kext_rtsx Hi, making a new thread. This driver is for Realtek SDHC card readers on a pci/pcie bus, most commonly found in laptops. I would like to get testers. The driver is not yet finalized, but I'm making the tread now anyway since there was interest. expect this post to change in the future. [read below for current status] -- sinetek things to fix eventually - get more pci id's in plist - async task in its own thread instead of blocking the os - prealloc DMA buffer? - cards with sector_size != 512, haven't been tested at all. - clean up src. git push. - power management? what happens when you sleep the machine? - the eject button in finder is broken, do not use for now. - spams the syslog with debug messages. release config? - basic namespace pollution a bit out of hand Update 1: Power management support on the way: see post #43. Latest version from Cholonam
    1 point
  5. Version 10.14.x

    41,274 downloads

    Patched OSInstaller.framework to allow macOS 10.14 installation on MBR HFS+ partition. To use those patched files you must follow HowTo to create an USB installer. You can't just run the app downloaded from Mac App Store. The patch is made base on 落下爱@pcbeta 10.10.x MBR patch method, and more patch for 10.14 HFS Firmware check by crazybirdy. What is this patched OSInstaller doing? 1. Patch the MBR check, allow macOS 10.14 installation on MBR partition. 2. Patch the Firmware check, bypass the error of "An error occurred while verifying firmware". 3. Patch to stop auto-convert to APFS , "ConvertToAPFS=false" is no longer worked with 10.14. 4. This patched MBR OSInstaller will never convert to APFS, and will always install as HFS+ partition. 5. This patched MBR OSInstaller method works with both MBR HFS+ and GPT HFS+ partition (GPT+recovery). No longer need to set new SMbiosversion, FirmwareFeatures, and FirmwareFeaturesMask with this MBR-patch. What's the difference between createinstallmedia method, MBR-Manual-Method, and MBR-Automatic-Method? As the following.... 1. createinstallmedia method, needs stage 1, stage 2 installation process, which is worked with GUID partition only, always convert to APFS format. 2. MBR-Manual-Method (same as 10.12), install via stage 2 manually, which is worked with both MBR and GUID, HFS+ and APFS, will never convert the partition format. We can manually format as MBR or GPT, HFS+ or APFS on installation screen like as 10.12. We can manually select MBR HFS+ partition to install 10.13 and 10.14 on installation screen now. Needn't to update the MBR-Manual-Method files, it will still work on 10.13, and 10.14 future versions, I think so. It can be installed as Fresh installation on formated blank partition only, but can't be installed as update from previous version. 3. MBR-Automatic-Method (new for 10.13+), install via stage 2 automatically, which is worked with both MBR and GUID, HFS+ and APFS, will never convert the partition format. It can be installed as Fresh installation on formated blank partition, and can be installed as update from previous version. How to make 10.14 installer for MBR (MBR-Manual-Method)? Just use EasyMBR-InstallerMaker to make installer, it works with both MBR and GPT. Read HowTo inside the dmg first, same as 10.12. Read HowTo Q/A Q5. How to patch to work with CPU SSE4.1 only for Mojave? Read HowTo Q/A Q6. How to download the full installer app via swscan.apple.com, instead of App Store? Read HowTo Q/A Q7. How to update 10.14.x combo-update to MBR and GPT with installScript directly? How to make 10.14 installer for MBR (MBR-Automatic-Method)? Just use 14MBRinstallerMaker to make installer, it works with both MBR and GPT. Read HowTo inside the dmg first, same as 10.13. Read HowTo Q/A Q5. How to patch to work with CPU SSE4.1 only for Mojave? Read HowTo Q/A Q6. How to download the full installer app via swscan.apple.com, instead of App Store? Read HowTo Q/A Q7. How to update 10.14.x combo-update to MBR and GPT with installScript directly? And, need a SMBIOS supported with /System/Library/CoreServices/PlatformSupport.plist. Q6. How to download the full installer app via swscan.apple.com, instead of App Store? A6. Some people download installer app from App Store, and get only 18 MB size, not the complete installer app (5.68 GB). You should boot to 10.12, or 10.13 to download it again from App Store, or use script Q6-DownloadFullApp/installScript_1014fullapp to download the full installer app via swscan.apple.com.
    1 point
  6. scusami ma l'altra notte ho fatto confusione... se è PCI prova a cambiargli slot e controlla che non si sia modificato qualcosa nel BIOS
    1 point
  7. Giustamente... Ok dai, stasera provo a fare questa prova, e ti faccio sapere. Thanks
    1 point
  8. I have no such issue because my AMI UEFI BIOS is tuned to boot /EFI/CLOVER/CLOVERX64.EFI and nothing more. Clover may chain to \EFI\Microsoft\Boot\bootmgfw.efi to boot Windows and I can update macOS and Windows safely. Download external drivers should not be by default. That's all I want. I may place any drivers into specific places before I create new package. apfs.efi can be used from Apple. AptioMemoryfix can be replaced by Clover's OsxAptioFix3Drv.efi (yes, it is good replacement!) AptioInputFix can be replaced by Clover's AppleKeyFeeder.efi. Actually they needed only for FileVault2 interface. If the AppleKeyFeeder is not working for some setups it should be reported and fixed.
    1 point
  9. @vit9696 thanks a lot for the info. I will implement the version checks tomorrow. About the restructuring/ordering of the config: afaik OCC does not reorder any entries it isn't supposed to, I will check that thoroughly tomorrow though, since swift dictionaries like throwing values around. It does however change the format slightly, for example it saves data like this <data> T3BlbkNvcmUK </data> Instead of this <data>T3BlbkNvcmUK</data> This should not affect OC itself, but indeed does make comparison more difficult when looking at the plist in raw text. However I did not find a way to prevent this from happening, this seems to be the way plists are formatted when writing an NSDictionary to a file. I will investigate this further to see if I can somehow manage to make this work, if nothing else I'll manually strip the newlines after the file was written. I'm sure the differential documentation will be a huge help for parsing configs of different versions, since atm OCC can only reliably parse the current version. If you have any more suggestions/changes you want to be made, just let me know Thanks again and cheers
    1 point
  10. @Andrey1970 thanks for the heads up. I did not expect you to consider my app when it comes to config changes. I check the docs directory on the OpenCorePkg repo almost daily and I did my best to build OCC in such a way that it's easy to account for changes to the spec @ricoc90 honestly I don't like when applications behave like that, so I don't think I will be changing that. I've just accustomed to hitting cmd+q to quit an app
    1 point
  11. I suggest stopping to replace random firmware modules that are incompatible with the rest of the software stack and just use EmuVariable. This has nothing to do with OpenCore though.
    1 point
  12. @momoxx Try the latest development version! Good luck! Mieze
    1 point
  13. I guess the configurator will just evolve as OC does. Not all users will be able to read that manual and will reply on a Configurator to help users get the best from their Hacks. Any tool to make it easier to implement will be supported here.
    1 point
  14. I had updated my Aorus Pro bios to F9 before finding this great guide. No major problems running the new bios, though. The Auto overclock feature is greyed out in bios if that matters, and a few options slightly different in bios setup, not sure what it is like in F5, mine shipped with F7.
    1 point
  15. @Andrey1970 Yeah, I would have guessed that if you wanted to officially support any kind of configurator you'd have made one yourselves. Doesn't mean it can't be a nice addition to the community though, imho
    1 point
  16. @iCanaro @pico joe try this one please OpenCore-Configurator_alpha13.zip
    1 point
  17. windows does not overwrite or use \efi\boot\bootx64.efi. It overwrites \efi\microsoft\boot\bootmgfw.efi. It is a firmware issue - as usually the firmware will scan the ESP for boot files, and always put \efi\microsoft\boot\bootmgfw.efi before \efi\boot\bootx64.efi in the boot order. Some firware mask \efi\boot\bootx64.efi if they find \efi\microsoft\boot\bootmgfw.efi on the ESP (the former won't show up on the boot list because the firmware stops scanning). If the firmware has put both files on the boot list, the order can be edited from the bios setup. Also, boot entries can be edited/deleted/created/reordered from EFI shell "bcfg boot" command line utility. Additionally, Windows' bcdedit when run with "bcdedit /enum all" shows the EFI boot order list and all non-windows boot entries - so it may be capable of actually editing and reordering the list, but I've never tried this.
    1 point
  18. @iCanaro does it crash after doing something or just instantly at launch?
    1 point
  19. @pico joe @iCanaro can both of you upload the config that crashes the program? @chris1111 @headkaze I appreciate the efforts, but the icon is only temporary anyway until the official OC logo is published. I have actually changed the icon yesterday already, the changes aren't upstream yet though. I will publish a new build with the latest icon and fixes in a bit
    1 point
  20. HI @notiflux maybe you like this Icon ? attaching here Icon.icns 512x512 pixels Icon.icns.zip Another approach icons 512x512 pixels attaching here Icon.icns 512x512 pixels OC-Icon.icns.zip
    1 point
  21. @SavageAUS only for ACPI patches. Just open the clover config.plist in xcode or any text editor and copy either the whole Patches array or a single patch dict and paste it into the acpi>patch table
    1 point
  22. It has run just fine on legacy bios since the beginning… Presently it is tested with DuetPkg clover fork.
    1 point
  23. OpenCore Bootloader with macOS Mojave 10.14.5 Beta 4 Build 18F127a Specifications : - Processor : Intel Core i7 6700 - iGPU : Intel HD 530 - eGPU : MSI Armor RX580 4GB - Motherboard : Gigabyte Z170X Gaming 7 - Storage : 1x MSata WD 240GB + 2x SSD @120GB + 5 HDD Storage (2x 2TB + 2x 500GB) - Wifi + Bluetooth : Broadcom BCM943602CS - Audio Codec : Creative CA0132 (5.1 Audio work) - RAM : 8GB (2x4GB) PC24000 (3000Mhz) - OpenCore version : rev 0.0.2 - Boot Mode : UEFI What's work?? - Sleep, Shutdown, and Restart - Good Cpu Power Management - HEVC and H264 for IGPU and eGPU - All USB Port - Unlock limit patch USB from config.plist of OpenCore (Built-in, just enable it) - QE/CI for RX580 - Faster boot time than clover - All kext in OC/Kexts is loaded perfectly - HDMI Audio - Audio Onboard (CA0132) All ACPI patch is in DSDT only,, no patch / binary DSDT patch from config.plist of OpenCore. I can say, all device work like using Clover but better boot time and Cpu Power management (my opinion)
    1 point
  24. @smartis63 Ho spostato il topic nella sezione italiana. come ha detto @Cyberdevs nessun supporto su Mojave per nvdia serie gtx 9xx/10x0 perchè non sono stati rilasciati i webdriver, quindi o installi 10.13 o cambi scheda video.
    1 point
  25. By the way: "-nehalem_error_disable" flag solves the issue in a more elegant and future proof way (as found here: https://www.root86.com/topic/8555-how-to-disable-appletymcedriverkext/)
    1 point
×
×
  • Create New...