Search results

Interesting. See my post here. H265/HEVC is enabled on my system with Catalina and Big Sur. I did not figure out why this might not be enabled. @fontanero - Can you please post your latest EFI and your IORegistryExplorer dump (captured with IORegistryExplorer 2.1)? Thanks. @fontanero can...

Nothing about graphics jumps out at me in your IOReg dump. Could it be that Big Sur is treating an Intel i3 differently than Catalina did? I see you're spoofing device-id 0x3e92 (same as my i7-8700). The IOReg dump from my rig running Catalina (with i7-8700) is attached. Maybe this will...

I saw that you're using WhateverGreen 1.4.7. I haven't been testing any "unofficial" Acidanthera kexts, so I can't comment on any behavior you might observe with Alpha or Beta releases. I do have a few comments: I learned from @viorel78 that DRM does not work on hacks with UHD630. See...

Please post your sanitized EFI with each request for help. Thanks.

I installed the free version of VideoProc.app on my rig running Big Sur 11.1 (see here) and ran its hardware detection with the results below. I think my results below indicate that VideoProc detects H265, so we know that H265 is possible with Big Sur and UHD630. My CPU is i7-8700 (CoffeeLake)...

That's good to know. FakeSMC is just a personal preference. I have used it for as long as I've been hacking and never had a reason to change. I'm always open to learning and improving. Is there something better about VirtualSMC? EDIT: @fontanero - you previously mentioned here that you were...

Congratulations if this means you solved it. Which power management option did you need to change?

I'll let you keep guessing about RM, since I know you'll remember... I was hoping that something would jump out at me for H265 and to be honest - it doesn't. What tool are you using to determine your rig's support for H265?

@fontanero Thanks for posting your problem reporting files. While I'm reviewing, could you run 'log show --style syslog | fgrep "Wake reason' in a terminal and post those results along with your IORegistryExplorer 2.1 dump? Thank you.

I'd be happy to look when you post your full EFI as requested in Post #1.

I am looking now - you clearly know what you are doing and I may be learning from you. I have a few observations/questions: I like your patching sense of humor! I never knew what AWAC stood for! :) You could eliminate DTGP, but I suspect you already know that Have you found that SSDT-NVME1 is...

I think you've sanitized it too much ;)

I think you'd get more constructive responses if you shared your sanitized EFI.

Glad this thread has helped you. Please include your EFI with your request for help as described in Post #1.

One thing is certain: if you don't have any USB2 devices, then a TypeC+Sw Connector will never matter for you. All of my USB3 devices also change logical port when I flip them. Reminds me of the blind guys in a room with an elephant and each describes a different animal as they are touching...

Glad this guide is working for you! Are you referring to the 512mb memory setting in BIOS? If so, I'm not aware of a way to increase this. If you want macOS to report more or less video memory, you can play with DeviceProperty framebuffer-unifiedmem as described here. I have seen...

@viorel78 That shows how much of a DRM-noob I am. I must have been playing a preview. I'll correct my original post. Thanks!

Ok - maybe I'm misunderstanding you. Are you saying that you think a logical port is "TypeC+Sw" if it has the same identity (e.g. HS10) when both a USB2 and a USB3 is plugged into the port? If so, that is where we don't agree on the interpretation. I think that a USB3 device plugged into a...

I didn't interpret the Hackintool help that way. Did you read the Hackintool help screen (here)? I read "TypeC+Sw" to be used for ports that retain the same HS/SS identity when the connector orientation is switched. When a USB2 device orientation is switched in our USB-C port, the port...

A couple of comments about future revisions to my OC EFI: I do plan to upgrade to OC 0.6.6 because of the switch from HfsPlus.efi (and VBoxHfs.efi) to FswHfsPlus.efi. You can follow the reasoning by viewing the OC 0.6.6 commits here. I think that individual USB patching strategies will need to...