Jump to content
5539 posts in this topic

Recommended Posts

1 hour ago, pkdesign said:

 

 

 

Perhaps this is a Mojave thing or something else in my configuration, but this does not work. I must set it to "disabled" in order to boot. This is what I get if I use "Default" or "j137":

IMG_4460.thumb.jpg.82c8213280558f59a85275b93c3d43a5.jpg

 

Anyone else with iMac19,1 and using Mojave that cans set this to something other than "Disabled?"

Likely some missing manifests, idk why Mojave has that issue. But once it's installed, it's possible to fix it so that secure boot can be enabled. There are more details about it under the "Troubleshooting" drop-down here: https://dortania.github.io/OpenCore-Post-Install/universal/security/applesecureboot.html#special-notes-with-securebootmodel

7 hours ago, AudioGod said:

Yeah any of the above will work too but some peoples PCI devices don’t inject under big sur and it seems kinda random to what works and what doesn’t so to save the hassle use the boot argument instead.

It seems to be the most universally working method of the three.

Right on. fruitMusic in its own app and Netflix in Firefox both seem to work with unfairgva=1 as a boot arg (or without), but Netflix in Safari & the fruitTV app seem still not to work even with unfairgva=1 (see RX 580 brand/model in my .sig file below, if you think it's relevant). It's possible the fruitTV content isn't working because it's not downloaded, though letting it get started doing so doesn't seem to affect matters either; either way, the app just takes the screen to a blank, black fullscreen in a different workspace for a moment, and then back to the original workspace.

 

Not a big deal; I hadn't been actively trying to stream video on the thing, as I do on other devices. Just followed the path that the removal of shikigva=80 from your 19,1 config.plist led me on. If there's a known fix* for full functionality on my setup, that's great. In any event, thanks, as always, for all your help!

 

*PS I also experimented with switching over to your latest OC 067 1,1 EFI, but an old SN/MLB/UUID I had generated for it was acting funny (SN not showing up in About This Mac, purchased apps no longer registered), so I'm back to 19,1 for now. I'm wondering if it's worth re-generating new versions of those for 1,1 and making a full-scale switch. I know you've covered the 19,1 vs 1,1 functionality pros/cons list before; are there any recent salient updates to that pros/cons list? Thanks again!

11 hours ago, AudioGod said:


To correct DRM for Apple TV plus Netflix and Amazon on Safari all you got to do is add unfairgva=1 to your boot arguments and off you go.

 

Actually thought you were taking the {censored} with this one :)

  • Like 1
  • Haha 1
24 minutes ago, AudioGod said:

 

Interesting ... does not work for me with a 580 ..  well Netflix and Amazon don't, TV+ always has ... I have not bothered doing the pci injection thing as i dont really care that much about it working these days ... Just found it funny it was called notfair and given the drama over it on here in the past i thought you where poking some fun at that, boohoo  :)

 

Cheers

Edited by Cass67
spelling
2 hours ago, Cass67 said:

 

Interesting ... does not work for me with a 580 ..  well Netflix and Amazon don't, TV+ always has ... I have not bothered doing the pci injection thing as i dont really care that much about it working these days ... Just found it funny it was called notfair and given the drama over it on here in the past i thought you where poking some fun at that, boohoo  :)

 

Cheers

Have to agree, though my symptoms are opposite: I just added the PCI DeviceProperties for my GPU that I got out of Hackintool, following your recommendation on the other forum, and it had as little effect as unfairgva=1 did as a boot arg (which I removed to try this). Netflix still works in Firefox & not in Safari, Music still works in its own app, and TV doesn't work.

 

Happy to keep experimenting with other options, if you like.

8 hours ago, juan e. jot said:

Have to agree, though my symptoms are opposite: I just added the PCI DeviceProperties for my GPU that I got out of Hackintool, following your recommendation on the other forum, and it had as little effect as unfairgva=1 did as a boot arg (which I removed to try this). Netflix still works in Firefox & not in Safari, Music still works in its own app, and TV doesn't work.

 

Happy to keep experimenting with other options, if you like.

Your both using 19,1 I take it?

sorry I should of specified but this is a 1,1 or 7,1 work around. 

Edited by AudioGod

@eSaF Whats ODC? Is that some special form of OCD? LoL

Shiki values are broken and no more under big sur so using 19,1 there is no fix available and by the sound of it the OC Devs have no intention of bringing shiki back to working.

1,1 and 7,1 are the only solutions for DRM and even then some people will need the unfair command to get it working properly.


To much time and energy has been waisted on this topic now over the years and if I had the power on here I would ban any more use of this convo but I don’t so I can’t stop it but Zzzzzzzzzzzzzzzzzzzzzzzzzzz people. :thumbsdown_anim:

Edited by AudioGod
  • Like 1
3 minutes ago, eSaF said:

You get an itch that you just need to scratch and before you know it, you're looking around for a band-aid because you didn't know when to stop scratching. :hysterical:


You might as well come over to my house and search my carpet for gold cos your have more chance of finding it then getting DRM working under 19,1 with Big Sucks  lol

Edited by AudioGod
  • Haha 1
On 3/3/2021 at 1:16 AM, AudioGod said:

Your both using 19,1 I take it?

sorry I should of specified but this is a 1,1 or 7,1 work around. 

Right on; my mention that I was on 19,1 must have gotten lost in the sheer volume of all that I had said about it. I'll consider how important the DRM is for me vs. generating new SN/MLB/UUID for 1,1 & re-registering paid apps. I had suspected it was a 1,1 vs 19,1 issue where unfairgva might work only with the former, thanks for confirming.

 

Off to use my rig as currently configured for other stuff. Thanks again!

 

UPDATE later that day: I bit the bullet & made the switch, and with the unfairgva=1 boot arg, your 1,1 EFI is working just fine for Netflix in Safari & TV in its own app. Thanks!

 

UPDATE that weekend: I've moved back for now to SMBIOS 19,1, because

  1. anecdoctally (not rigorously tested), it seemed like turning the iGPU off and running absolutely everything destined for the screen through the dGPU was bringing up my power usage a little bit,
  2. Both sleep & Night Shift in ongoing testing were proving a bit more finicky under SMBIOS 1,1, than the reliability they have shown over the past few 19,1 AG EFIs. Not impossible to achieve automatically, just hard to predict under what conditions they might not work & have to be invoked manually, and
  3. Probably not on a personal mission to irk afficianados of The Hack, but rather to move the product stack further along toward their own silicon, the fruit company stopped selling any but "while supplies last" of the base model SMBIOS 1,1's today. I had already been a bit iffy about having a completely different generation/class of processor (Coffee Lake S) than what SMBIOS 1,1 said it had (HEDT Skylake); today's product announcement just pushed me back over toward what had been working well & more accurately emulates a "later model" (the 2019 19,1, rather than the 2017 1,1; that hopefully enjoys software support, in the form of putting anything out for it, for longer).

 

Luckily, if you too are on SMBIOS 19,1, the "DRM Compatibility on macOS 11" heading near the bottom of this page https://github.com/acidanthera/WhateverGreen/blob/master/Manual/FAQ.Chart.md has defaults you can write that, as long as you've got unfairgva=1 in your boot args, show all the video I've tried in the TV app. Unlike the full support of DRM from the 1,1 SMBIOS, you can't play all music videos in the Music app. I haven't tried Netflix through Safari, because I'm fine with it through Firefox.

 

Be aware though, writing & (if you decide to backstep from them) deleting defaults is a serious business & is outside the "Vanilla" Hack philosophy of prepping your machine in the EFI to function as much as possible like a real one of the target machines, without any other tweaks to the main OS or data parts of the drive's file system. Not only could it be considered bad form, but it could also mess up your other defaults if not done very carefully.

 

Any editing of defaults you do is at your own risk.

 

Upon completion of the above testing, I myself have put all my defaults back to what the system wrote for itself, meaning I've removed (very carefully, only) those defaults suggested by the page linked above. If I have a later need to watch a video on my rig, it's a lot quicker (as long as I am, again, very careful) to update the defaults to get them to play, than it is to switch back to SMBIOS 1,1. In the meantime, Vanilla.

Edited by juan e. jot
Update on update: Back to 19,1 with unfairgva=1, defaults
  • Like 2
On 3/2/2021 at 12:28 PM, AudioGod said:

Ouch, that’s not fun bud.

from your description I would look at the PSU first of all and then the CPU second.
I doubt very much that’s motherboard related personally.

 

Hmm... the PSU is a Corsair RMX850, that shouldn't really have any issue, on the other side all components are new so who knows.. looks like a single rail design, so switching power consumption to different outputs might not change anything. Switching the PSU would be easier than replacing the mobo. Hmm... I hate ordering and returning products that I used.

 

4 minutes ago, eSaF said:

There is quite a simple method to test a PSU with a paper clip, Youtube has a few easy to follow videos on how to.

hmm. as the system is running fine AFTER finally not booting into the bios because of init issues I doubt using a paperclip will help :lol:

46 minutes ago, dredhorse said:

hmm. as the system is running fine AFTER finally not booting into the bios because of init issues I doubt using a paperclip will help :lol:

Put it in the oven at gas mark 7 for 45mins, That will sort it right out :hysterical: (jokes do not do that...lol)

  • Haha 1

Well, I don't know if it is PSU / CPU / Motherboard. Problem is that everything is running fine after some issue for days.. And it is a custom water cooled system. And how can I check if the PSU is the problem without replacing the PSU? I will try to switch the powerlines on the PSU to see if I pull to much power from a line during boot but IIRC tests correctly the PSU doesn't has several lines as old ones have. I could also check to see if I could keep the fans down during boot, atm the will spin up in the beginning for full. BUT.... sometimes even a reboot (which doesn't change anything on the fans and lights IIRC) can cause sometimes a boot into the bios :worried_anim:

6 minutes ago, dredhorse said:

Well, I don't know if it is PSU / CPU / Motherboard. Problem is that everything is running fine after some issue for days.. And it is a custom water cooled system. And how can I check if the PSU is the problem without replacing the PSU? I will try to switch the powerlines on the PSU to see if I pull to much power from a line during boot but IIRC tests correctly the PSU doesn't has several lines as old ones have. I could also check to see if I could keep the fans down during boot, atm the will spin up in the beginning for full. BUT.... sometimes even a reboot (which doesn't change anything on the fans and lights IIRC) can cause sometimes a boot into the bios :worried_anim:

Go into windows and run HWINFO and stress that system out hard for a while and watch HWINFO for fluctuations in the power and HW Errors.

If somethings up then HWINFO will probably catch it.

Hey guys!

 

So this isn't anything major, but I find if I leave my computer asleep for more than a day or two there is a sleep wake failure in the EFI, below is the error. Any ideas for a fix?

 

Sleep Wake failure in EFI

Failure code:: 0x00000000 0x0000001f

7 minutes ago, stavidawg said:

Hey guys!

 

So this isn't anything major, but I find if I leave my computer asleep for more than a day or two there is a sleep wake failure in the EFI, below is the error. Any ideas for a fix?

 

Sleep Wake failure in EFI

Failure code:: 0x00000000 0x0000001f

Reset your nvram

Hmm, so I did when I installed 0.6.6, but just about to installs your new 0.6.7 EFI and was going to reset the NVRAM & ensure clover is selected as the boot disk again. I'll write back in a couple days and see if this fixed it :)

Thanks for the update @AudioGod!

 

One question, can I set csr-active-config to ZwAAAA== in NVRAM->Add->7C436110-AB2A-4BBB-A880-FE41995C9F82 to disable SIP?

 

Thanks! 

27 minutes ago, panosru said:

Thanks for the update @AudioGod!

 

One question, can I set csr-active-config to ZwAAAA== in NVRAM->Add->7C436110-AB2A-4BBB-A880-FE41995C9F82 to disable SIP?

 

Thanks! 

Go for it.

I followed OpenCore guide here, it recommends to add FF0F0000 instead of 67000000 for NVRAM->Add->7C436110-AB2A-4BBB-A880-FE41995C9F82

 

In addition, the guide says that you have to add in NVRAM->Delete->7C436110-AB2A-4BBB-A880-FE41995C9F82 a String element with csr-active-config as a value.

 

1418644922_Screenshot2021-03-05at14_36_02.png.9f52a0af17ab7f35a696edb3b87b523a.png

 

I tried both FF0F0000 and 67000000, reboot -> reset nvram but csrutil status returns this:

 

System Integrity Protection status: unknown (Custom Configuration).

Configuration:
	Apple Internal: disabled
	Kext Signing: disabled
	Filesystem Protections: disabled
	Debugging Restrictions: disabled
	DTrace Restrictions: disabled
	NVRAM Protections: disabled
	BaseSystem Verification: enabled

This is an unsupported configuration, likely to break in the future and leave your machine in an unknown state.

I expected to see System Integrity Protection status: disabled message.

 

What I am doing wrong here? :/ 

Edited by panosru

Hey guys, before I go and format my SSD and start over I thought I'd see if anyone has any suggestions here first..

 

Currently my pc fails to boot 99% of the time on first attempt and I have to hit the power button to restart the cycle then it boots to the OS picker screen. none of the mobo LEDs are indicating some sort of boot failure.

Maybe related but recently I'm also finding I need to plug in my apple keyboard at the login screen or its not detected (magic mouse is) once unplugged the keyboard functions as normal.

 

OC 0.66 with EFI from here - Big Sur 11.2.

I don't recall the issue being there prior to 0.66 maybe not before Big Sur all together so Im just wondering if anyone else has suffered boot issues with that or OC 0.66?

My other issue which has been around for a while now is my Icons being too big on boot up and Aorus Logo, no matter what I put in the resolution field on config.. the issue Ive found is not present when booting into recovery mode as I found today..

I've got cloud storage for documents and I suspect a clean sheet without using a time machine backup might be my best solution, but just holding off to see if anyone chimes in with something I've missed recently regarding booting issues.

 

Maybe I can enable logging some how to see what's failing at boot? I've plugged in HDMI instead of DP for now to see if its simply a display issue.

 

Thanks

 

Edit* was just about to create a new USB with OC0.67 but the links are dead, anyone have a link please?

Edited by rob1980
×
×
  • Create New...