More bugs... #1
Comments
Only thing that needs to be updated are images, add chapter on Security Section and the sample config.plists |
Sample config.plists is probably a bad idea as config.plist change a lot. But the rest makes some sense. Will ping you when I found more flaws… |
|
Second pass: Current issues section is probably mislabeled. An issue is something that needs to be resolved, but we do not plan to make changes here. Kext ordering is a design decision, Z97 and NVMe are unrelated to OC. Last two are mostly fixed by now. This probably wants to be named Highlights or Things to Keep in Mind. Regarding mountEFI, is it not easier to just use diskutil from Terminal? It is really just diskutil list and then sudo diskutil mount /dev/disk0s1, where 0s1 is the ESP partition as seen in first command output. MacOS Journaled → HFS+ macOS Journaled is more clear drivers → Drivers, kexts → Kexts, TOOLS → Tools case matters for vaulting. Also makes sense to fix Sample.plist, although it matters little. usb map the way it is presented is a bad idea. This kext, UsbInjectAll, reimplements builtin macOS functionality without proper current tuning. It is much cleaner to just describe your ports in a single plist-only kext, which will not waste runtime memory and such. A good idea to add there is CPU PM SSDT (we have it in Docs) and EHC switch off. Every time clover configurator is mentioned, god decapitates a kitty, please do not. Never ever put files unused for booting (like create_vault.sh or Docs) to EFI/OC. They may get vaulted. Tools must contain efi files (and their dependencies) only. s/This section allows us to dynamically rename parts of the DSDT via OpenCore. Since we're not running a real mac, and macOS is pretty particular with how things are named but the maojority of the time these patches are only cosmetic and can be more damadging that useful./This section allows us to dynamically modify parts of the ACPI (DSDT, SSDT, etc.) via OpenCore. macOS usually does not care much about ACPI, so in the majority of the cases you need to do nothing here./ For NormalizeHeaders replace irrelevant for macOS Mojave 10.14 and higher with only relevant for macOS High Sierra 10.13. Attempt to heuristically relocate ACPI memory regions, not needed unless custom DSDT is used. Workaround for OEM Windows logo not drawing on systems with BGRT tables. We also add 2 more properties, which are usually unnecessary, as this can be configured in BIOS this is where you would add USB port… just remove, it is builtin in Quirks. ExternalDiskIcons makes USB disks internal sometimes, and today is not really needed. For NVMe on Z87 and below you just add built-in property via DeviceProperties. UIScale 10 is most likely wrong, should be 02 I believe. UpdateSMBIOSMode add: Use Custom on Dell laptops requiring CustomSMBIOSGuid quirk. ConnectDrivers, Disabling the quirk makes booting slightly faster Typos:
|
Switched to “Things to note about OpenCore”
Personal preference, users on the r/hackintosh subreddit show that anywhere you can remove terminal commands can alleviate a lot of accidental issues. (Also I just realized I have “either mountEFI or Clover Configurator.”, will remove Clover Configurator)
Reason I have it as “macOS Journaled with GUID partition map” is because that’s what the Disk utility screen shows. Swapping to “HFS+ macOS Journaled” I feel could confuse more users but I'll add a note
Fixed, also already removed mention of sample config.plist
So how I'm misinterpreting this: You want me to explain more why a USB map is prefered over UsbInjectAll, correct? If so I have fixed this
Most if not all mentions should be removed
Fixed
Fixed
Fixed
Fixed
My main concern is that generally every new version of macOS requires a new port limit patch wich users may prefer to use over a USB map. Unless how OpenCore implements the port limit patch will always work even on newer versions of macOS, I will add a note that the quirk is the prefered option
Fixed
Fixed
Fixed
Fixed
Fixed
Fixed
Fixed
Fixed
Thats how I construct the paragraphs, just personal preference but the inconsistency is likely your issue. Will go through and try to address this issue
Glean means to collect/extract
Fixed |
|
@vit9696 I've also added a section on emulated NVRAM if you want to check to see any issues |
|
Thanks, the changes are mostly satisfying, making one more pass. — s/Order of kexts matter/Order of kexts matters/ — s/example ca be/example can be/ — Please note that UEFI drivers are not supported with OpenCore! — base EFI folder photo has TOOLS instead of Tools, and this error remains on many photos/lines — NVRAM guide needs logout hook installation, check the readme. Ping me when all the issues are addressed as the guide is a bit messed up at the moment. |
Personally don’t see an issue
Fixed
Incorrect wording on my part, meant to be “UEFI drivers from Clover are not supported with OpenCore!(ie: EmuVariableUEFI-64)”
There was only 1 photo I could find which was under “Creating a USB” base EFI. And there was only 1 mention of TOOLS which has been fixed. If you do see anywhere else I will gladly fix
Fixed but slight issue on my end with interpretation. Do you still need to run the LogoutHook.command separately or can you just run |
|
UEFI drivers and UEFI drivers from Clover are completely different things. UEFI drivers is a general term, and OpenCore.efi or AppleUiSupport.efi are UEFI drivers (surprise). We do nit recommend the use of Clover UEFI drivers due to various incompatibilities, but it has nothing to do with what you wrote. You just run sudo defaults write com.apple.loginwindow LogoutHook /location/LogoutHook/LogoutHook.command and it adds the nvram.plist automatically when you power down. This, yes. |
|
Hi @khronokernel |
|
@khronokernel I think emulated NVRAM part wants:
|
|
@vit9696 Thank you for catching the
Main reason was that most users who are already using this boot flag shouldn't need to be told to use it for OpenCore as well, but the more I think about it I feel it would make sense to add it. Especially if this guide becomes the defacto for new users(but at that point a lot more info would need to be added but that's a talk for another day). So appreciate the suggestion, will be added to the guide shortly
I do apologize but slightly confused on wording, are you saying that even when setting |
with FwRuntimeServices : |
|
@khronokernel, @Gengik84 is right that this is obviously not enough for most systems. I would strongly suggest you to read the documentation, particularly you need to play closest attention to ConsoleBehaviourOs, ConsoleBehaviourUi, IgnoreTextInGraphics, and SanitiseClearScreen. Documentation for the first one even contains the list of values to try on different firmwares. |
|
@vit9696 Thx :)
For all case, this is not right |
|
@Gengik84 Sorry for the late response, forgot to message saying it's been updated. If there's any other issues, feel free to send it my way |
|
@khronokernel Hi, dont worry :) |
Oh wow, nice catch on that one. Completely flew over me, will update shortly but images will be a bit longer |
|
@khronokernel Thx for your work
Maybe an image for default config.plist is enough, you can inform, explaining to change path because:
|
|
@khronokernel You and others are really doing a good job with this. It is really valuable to those like me that are new to OpenCore. The things you people are doing is really amazing. Dennis |
|
Hi, @khronokernel, none of these are needed in OC, as quirks implement all the functionality. |
|
@vit9696 Thank you for that, they're meant to be removed once I clean up a bit more of the guide, I noticed the additional info added for AppleXcpmExtraMsrs and the Emulate section. That was my reason for not adding X79/X99/etc to the guide when I added Skylake-X, so holding off on them for now until I correct it. Thank you for the heads up though, appreciated.
|
|
@khronokernel I believe on most firmwares it should be resolvable through |
|
Ah, also, we got several reports on your other guide. For SSDs I am not positive what is wrong with Samsung 970 series. I own both 970 Pro and 970 EVO Plus (yes, it does require a firmware update) and they are quite stable. For any non-apple NVMe SSD you are recommended to use 07151129's NVMeFix, as it reduces heat and energy consumption. For Intel SSDs, I own both 520 and 530, and they work properly. There was a bug with APFS trim, but it is fixed in some 10.14 release. For CPUs Catalina still has support for dual-socket chipsets, and there is no change with it. However, there is a bug with AppleIntelMCEReporter driver, which apparently is still being resolved. Currently there is a plist-only kext workaround for it. |
|
I really appreciate the work you are doing with the Guide. I consult it several times a week.
I don’t know if this mod can be done or maybe it is a part of the gitbook framework.
At the bottom of each page there is:
"Last updated xxxx days ago”
If you could also have that at the top of the page it would help. No need to scroll down to check when the last changes were done.
Thanks for listening.
Dennis
|
|
@vit9696 Has been corrected with proper info, thank you @DWomack Yeah that's gitbook's framework and I can't seem to change the location, but instead I can manually add it to the page at the top under the title. So for every time the specific page has been updated, just update the "last edited" part. Is that what you were thinking or having the "last edited" always be the most recent of all pages? |
|
I would like to see when each page was last updated. If it is a lot more work, don’t worry about it. I’ll put my button on happy.
Again, thank you for making the guide.
Dennis
…Sent from my iPhone
On Jan 13, 2020, at 3:45 PM, Mykola Grymalyuk ***@***.***> wrote:
@vit9696 Has been corrected with proper info, thank you
@DWomack Yeah that's gitbook's framework and I can't seem to change the location, but instead I can manually add it to the page at the top under the title. So for every time the specific page has been updated, just update the "last edited" part. Is that what you were thinking or having the "last edited" always be the most recent of all pages?
—
You are receiving this because you were mentioned.
Reply to this email directly, view it on GitHub, or unsubscribe.
|
|
This is probably a gitbook framework issue, but when I look at the pages on an iPhone with latest iOS, I see:
Last updated -3 or such.
Dennis
…Sent from my iPhone
On Jan 13, 2020, at 4:11 PM, Dennis Womack ***@***.***> wrote:
I would like to see when each page was last updated. If it is a lot more work, don’t worry about it. I’ll put my button on happy.
Again, thank you for making the guide.
Dennis
Sent from my iPhone
>> On Jan 13, 2020, at 3:45 PM, Mykola Grymalyuk ***@***.***> wrote:
>>
>
> @vit9696 Has been corrected with proper info, thank you
>
> @DWomack Yeah that's gitbook's framework and I can't seem to change the location, but instead I can manually add it to the page at the top under the title. So for every time the specific page has been updated, just update the "last edited" part. Is that what you were thinking or having the "last edited" always be the most recent of all pages?
>
> —
> You are receiving this because you were mentioned.
> Reply to this email directly, view it on GitHub, or unsubscribe.
|
|
Hi, newbie here! Could you please specify in your guide what's the recommended value for "WriteFlash" in legacy BIOS computers (using emulated nvram)? Kind regards. |
|
@vit9696 Sounds good to me, my idea is to have DRM stuff on a separate page and setup an issues tab in the guide for users to report in(I'm sure you don't want random people to be flooding the bug tracker). I can also add the recommendation of I do have some questions:
Thanks for any pointers you can give. Also kinda related but not really, have you heard much about Sidecar support on iGPU-less systems? 10.15.0 or .1 broke support partially(iMac19,x boardID was fine) but now it's outright broken. Not really that important but curious if you've heard much or have some tips |
|
@khronokernel we did a bit more research on the matter, and there actually is no change with the DRM. We indeed can load Apple SpringBoard firmware on IGPUs on at least 9th generation of Intel mobile chipsets (and likely newer), and that dramatically improves IGPU performance. Older chipsets will be unsupported almost certainly due to old ME version. However, PAVP support is still not there and will likely never be: acidanthera/bugtracker#586 (comment). Also, it is best to inject igfxfw rather than use a boot-arg just as usual. Regarding DRM testing, you can go with this guide. It is a bit outdated, as we were able to figure out that Apple TV can actually be decoded programmatically if forced to run in compatibility mode (FairPlay 1.x) but other than that it is all the same. For IGPU-based configurations you can always use the standard guides (here and here). For the rest just refer to the chart. I know absolutely nothing about SideCar and am yet to try it. UPDATE: Actually we can confirm that it works on desktops too and even with 8th gen CPUs. You just need a new chipset (e.g. Z390, B360, H370, H310, etc). |
|
@vit9696 I think, this GuC thing works better on 10.15.4+ right? Cause, I already tried on 10.15.3 and still Safari freezes and the system locks continue. Note: Yes I have Polaris Card RX560, Asus Z390 TUF and 9900K |
|
Just a answer? Will DRM playback ever work on a only-iGPU laptop as my Dell Inspiron 5370 with i5-8250U? I can't watch Netflix in 1080p :'( |
|
@telepati it does not matter. @dreamwhite unlikely. |
that's not correct. DRM (in HDCP mode) is not supported on any IGPU-only configuration, be that old or new, starting from 10.12.3 or so. The only IGPU-only supported DRM configuration was HD 4000 in 10.12.x days.
Should have a note, that FairPlay 1.x encrypted trailers play on any configuration if WhateverGreen patches are properly applied, including IGPU-only configurations. However, FairPlay 1.x encrypted iTunes movies will not play on IGPU-only configurations for longer than 3-5 seconds. They will error soon after that HDCP is unsupported.
It is not necessarily hardware, so better change to
You can just open TV.app, choose TV+ → Free Apple TV+ Premieres → Click on any episodes. This will let you test DRM without starting the trial or any kind of registration at all.
This is not directly related. While Apple's GuC is required for hardware DRM to work, you also need to provision PAVP with Apple certificates. We cannot do this, as OEM vendors (e.g. Dell) already provision their devices with their own (or likely Intel) certificates, and provisioning can be done only once. In theory reprovisioning is possible on Z390 and alike, but you will have to clean the ME region (requires SPI flasher and a lot of thought), and then use a tool named named PavpProvision from OpenCorePkg. To use the tool you will also need to manually edit the source code with provisioning certificates from Apple firmware. I.e. this is pretty much impossible for even advanced users.
This is wrong. It will not disable Shiki patches. shikigva=80 (aka 0x50) forces the use of AMD GPU for iTunes/TV.app (bit 16) and for Safari (bit 64). All in all, you should not inject anything related to shikigva with IGPU-only configurations. Disabling Shiki patches is shikigva=128 (<80 00 00 00>), but this will not work on anything but Xeons with AMD GPUs.
That's garbage, you can inject shikigva in any GPU, IGPU or dGPU. The only thing is that you must ensure that you do that into one GPU, otherwise the first found will be used, and it is indeterministic. Basically, what you have for IGPU-only (shikigva=80, igfxfw=2) actually applies to AMD+IGPU Z390+. And for < Z390 it will be shikigva=80 without igfxfw=2. |
I was referencing boot-args specifically as to throwing a bunch in there, but has been cleared up Everything should be good now but I'll omit it from the gitbook for now and wait for validation just to be safe: DRM page |
This is not correct. It has never worked on systems with HSW+. It was possible to fix it with IVB CPUs till 10.12.2 via Shiki. Afterwards it became permanently broken for them too.
This is not correct. The only setup it works with are AMD GPUs Polaris+. IGPU has nothing to do with it. There were some 7th generation AMD GPUs with hardware DRM decoding, but from what I remember none worked with streaming services, only iTunes movies.
Requires physically absent IGPU (Xeon CPU) or newer AMD GPU to work (Polaris+). When IGPU is physically absent it is possible to force Apple TV+ into FairPlay 1.x mode.
Do not include this. Firstly because it is theorising, though likely, secondly because no single user will be able to make any sense of it, putting aside doing.
In my opinion, it is mixing up unrelated things. Write something like below. Find your configuration in the chart. If none fits, you are out of luck. If You do not need to use
In my opinion, do not mix igfxfw with the DRM stuff, they are related on ME side, but not really helpful to the user. |
With latest weg commits and boot arg igfxfw=2 doesn't seem to load GUG. |
|
@vit9696 is it correct that the chart was made with Vega in mind? If I understand correctly, if you have Polaris Ellesmere+IGPU and you are using an iMac/Mac Mini SMBIOS, you should use |
|
@dhinakg depends, starting with 10.15.4 shikigva=80 works fine on Polaris, at least for me. |
It works for me too with RX560+IGPU enabled on BIOS SMBIOS 19,1. No freezing or system lock too. |
|
Interesting - would the best course of action just be to link to the chart and provide a brief explanation on how to use it, or provide an example for a sample hardware configuration too? |
|
Yes, I believe it is the best route to do it. A brief explanation on how to use and 1-2 example hardware configurations. |
|
@dhinakg here is mine maybe this not right way cause I don't know how to inject shikigva that's why I am using as a boot-args; Asus TUF Z390, 9900K, RX560 BIOS setting; --> IGPU enabled
With these settings Apple TV and Netflix (on Safari of course) working without any problem. |
|
@dhinakg first picture does not show exactly which PciRoot? |
|
Also, you can add the guide this for the people can easily find their Device Locations IGPU device locations PciRoot, gfxutil may be used: gfxutil -f IGPU |
|
@dhinakg looks more or less good to me. Maybe fix some grammar, and done. |
|
Hey, @vit9696 what is for these two; is it for everyone? Cause on my system if I add 'agdpmode' I can't make a boot monitor goes to sleep. I don't think 'agdpmode' useful for everyone.
I am using this way and everything working. Boot Ok. Netflix on Safari Ok. AppleTV Ok.
|
|
Why either of the two should be for everyone? First is a comment, second is for myself. Use the docs to help you. |
|
@vit9696 Just pushed some grammar changes. If there are no technical issues with this I'll merge into master. |
|
Yes, that's the requirement, but even that is not a guarantee. Better make it clear, as we already got a false alarm (acidanthera/bugtracker#790). Looks good otherwise. |
|
With 0.5.7 you will need to update several properties in
|
|
Oh thank you for the info, much appreciated |
|
In my case my MB: Gigabyte Z370 AORUS Gaming K3 (with latest firmware) wont boot with EnableWriteUnprotector disabled and RebuildAppleMemoryMap & SyncRuntimePermissions enabled My question is: Do i only enable EnableWriteUnprotector and leave RebuildAppleMemoryMap and SyncRuntimePermissions disabled or do i enable all 3 quirks? Thank you all |
|
Can @vit9696 briefly explain how is CPU PM handled with the AppleCpuPmCfgLock and AppleXcpmCfgLock kernel quirks enabled? My laptop has CFG-Lock and seems I will never be able to get it unlocked so I wonder if cpu pm is worse than with write access to msr 0xe2 and I am curious how is it managed with the register locked. |
|
Gigabyte Z370 HD3P, 8700K, OC5.7, 10.15.3 boots just fine but having the system hangs right after startup disk changed in the system settings |
|
This repo is no longer used. |
I have just run through Ivy section, and that's what I found:
Renaming ACPI devices is dangerous, and you just stepped on the rake. Using Count = 1 will only replace the first occurrence of the value, effectively breaking most of ACPI tables. This will make Windows unbootable at the very least, and may cause severe issues on macOS as well. Basically this advice is not only wrong, but it violates the recommendations from OpenCore configuration manual:
The "correct" approach is not to rename anything as it is cosmetics with the only exception of IMEI, IGPU, HDEF, and HDAU, which are handled by WhateverGreen and AppleALC. This will produce much less problems with all operating systems.
can interfere with Firmware so avoid when possiblethis comment for DisableIOMapping is wrong. On the contrary it does not interfere with the firmware. Should better say use this when you need VT-d support in other operating systems.not needed for AHCI or NVMe SSDs. It depends. AHCI usually need it, so best to check Trim Status in About Mac → Details → SATA/SAS (check English locale for macOS to be sure with the names).Needed for seeing your availble drives. Better to reword it show OpenCore UI when booting. Setting to NO will boot the default option. This option is a hack until "Opt" button support is implemented.ScanPolicy
This allow youI suppose it should be0 allows you. Honestly, it will be better to properly document Security section. Perhaps in a separate chapter, as it is not the best idea for a "quick" setup.dart=0does not function with System Integrity Protection enabled, so it is kind of useless.-xcpmis no longer relevant on 10.12 or newer.Forcibly rewrites NVRAM variables, not needed for us as sudo nvram is prefered but useful for those edge casesClarify that: Note thatAddwill not overwrite values already present in NVRAM.when newer versions are available from OpenCorethat's garbage. It just updates, and no version comparison happens.Forces .efi drivers, change to NO for faster. Should be Automatically connects added UEFI drivers. This is slightly faster, but not all drivers connect themselves. E.g. certain file system drivers may not load.ConsoleControlset to YES is needed on most APTIO firmwares, otherwise you may see text output during booting instead of nice Apple logo.SanitiseClearScreenis really needed on select AMD GPUs on Z370.RequestBootVarRoutingis recommended to be enabled on all systems for correct update installation, Startup Disk control panel functioning, etc.The text was updated successfully, but these errors were encountered: