Jump to content
5539 posts in this topic

Recommended Posts

On 3/4/2022 at 9:35 AM, eSaF said:

@MaLd0n - Just finished putting the EFI Folder through some test - Beautiful Maestro!!! - Thank you very much for your expertise, Sir I salute you. :thumbsup_anim:

Could you explain what tests you've run and the differences now compared to the previous EFI?

 

Thanks :) 

39 minutes ago, rob1980 said:

Could you explain for us less technical people the advantage over what we're currently using?

Is a personal for ur hardware/mobo not a generic. All patches for one good hackintosh with all Apple/intel devices, removed unused devices(a bunch trashes for Windows), cosmetics, etc. of course the devil is in the detail.

One good hackintosh for professional things like video and audio producers. No other way since long time and with OpenCore fork these tables is not injected in other systems and we can play a lot. :yoji: btw i'm using it with official OpenCore too, just with bootkey instead. All bootloaders support override tables.

39 minutes ago, MaLd0n said:

Is a personal for ur hardware/mobo not a generic. All patches for one good hackintosh with all Apple/intel devices, removed unused devices(a bunch trashes for Windows), cosmetics, etc. of course the devil is in the detail.

One good hackintosh for professional things like video and audio producers. No other way since long time and with OpenCore fork these tables is not injected in other systems and we can play a lot. :yoji: btw i'm using it with official OpenCore too, just with bootkey instead. All bootloaders support override tables.

 

Ah ok, sounds good, less bulky with things removed that aren't used.

 

So I'm guessing its not just a case of using the EFI you posted as that would be more generic or is that tailored to the specific mob here (other than individual devices like SSD etc) or do I need to create a whole new EFI with your tools?

 

Thanks :)

Just updated to 079 without issue, and without having changed a thing in config.plist. Took a video of -v at bootup, and found (frame by frame) no nags to change anything. I'll be interested to hear whether @pkdesign or others scanned Differences.pdf better than I did, to set things up better for future versions.

 

In other news, a couple days before 079, I'd installed an RX 6600 XT, making sure to add agdpmod=pikera to my boot args, and it runs like a charm. I lost the GPU temp that it had always given me in iStat Menus/Sensei, but gained it back with RadeonSensor (at https://github.com/aluveitie/RadeonSensor).

 

The speed gains of the RX 6600 XT over the RX 580 are mostly lost on (what I do in) macOS (these days, mostly maintenance & tinkering), but man does it fly in Windows & Linux!

I hate to admit it but I have been letting OCAT do the heavy lifting at this point. It has been working very well for the last few updates. I think this has a lot to do with the fact that OC is very stable at this point and has few changes. I might go back through and check my config.plist in PlistEditPro if I feel like checking things out.

 

I update to 0.7.9 in just  a few minutes and all is well so far.

 

EDIT:

I went through manually and only saw one new entry

Misc>Debug ADD LogModules VALUE *

 

There seems to be something new for prev-lang:kbd but I'm not sure what to make of it. Previous setting works fine for me.

 

Edited by pkdesign

That really needs to be clarified in the Configuration.pdf! It isn’t clear at all. It would seem from Configuration.pdf that the format should be something like en:252.  Or en-US:252. Do you use an underscore or a dash?! 🤨

 

I also doubt that ru:252 is a US keyboard! Probably a typo.

 

So I used en_US - U.S (no period after the S) specifically from here. There seems to be a bunch of options for a U.S. keyboard. I think the first two are probably the most valid:

 

[252] en - ABC

[0] en_US - U.S

[15000] en_US - USInternational-PC

[-2] en - US Extended

On 3/8/2022 at 5:57 PM, pkdesign said:

I hate to admit it but I have been letting OCAT do the heavy lifting at this point. It has been working very well for the last few updates. I think this has a lot to do with the fact that OC is very stable at this point and has few changes. I might go back through and check my config.plist in PlistEditPro if I feel like checking things out.

 

I update to 0.7.9 in just  a few minutes and all is well so far.

 

EDIT:

I went through manually and only saw one new entry

Misc>Debug ADD LogModules VALUE *

 

There seems to be something new for prev-lang:kbd but I'm not sure what to make of it. Previous setting works fine for me.

 

New version of OCAT out? I can only find the 078 version/

Hey everyone! I noticed that after  updating to v0.7.9 if I set SetApfsTrimTimeout to 0 the trim delay (~7 minutes) with my Samsung Evo drive is eliminated and the boot is almost instantaneous, while I know that this is not a solution since Trim has to happen periodically (I believe every 3 days or once a week is sufficient), I was wondering if there is a way to somehow make the trim to happen ever n days (much like a cron tab) before booting into the system.

 

Thanks! 

12 hours ago, eSaF said:

Try here for latest version - https://github.com/ic005k/OCAuxiliaryTools - or here is the latest version attached.

OCAT_Mac.dmg.zip 24.38 MB · 1 download

Figured it out after, had to click on newest version, all good from there. Thanks man

Edited by cabal2000
20 hours ago, cabal2000 said:

New version of OCAT out? I can only find the 078 version/

You can now update from within the program https://github.com/ic005k/OCAuxiliaryTools/issues/207

 

It's not entirely intuitive yet :)

9 hours ago, jimborae said:

So used the latest version of OCAT to update to OC 0.7.9 and all went well. 

 

Tempted to try Maldon's EFI but not sure what extra that would give me. 

Yea, I've looked through that EFI and and way too confused about what is in there.

Edited by pkdesign
  • Like 2

Hi @AudioGod, just would like to ask have you disabled SuperIO (serial port) in your EFI? I am having USB audio overload problems and based on my searches it could be related to serial port, and in F12 version of the BIOS there's nowhere to disable it.

  • Like 1
7 minutes ago, eSaF said:

Hi - AG for the time being is no longer available to help with your query and the only other member that comes to mind in the audio field is @5T33Z0 Appeal to his good nature and maybe he can point you in the right direction. Good luck.

Thanks, I'll try contacting him

2 hours ago, pkdesign said:

Anybody update to 12.3? i have heard there are issues with some graphics cards even on real Macs.

In 12.3, I've only had the same problems with my relatively* new RX 6600 XT that I had had with 12.2.1 (and with Manjaro, but not with either Windows or Pop!_OS, Fedora, etc.), in that (on macOS) I really gotta mash the keys to get its attention at the login screen; if I let it go too long, it will never respond & I have to reset to get it to reboot. I had earlier thought switching from a 60MHz refresh rate to 75MHz cleared it up (after a loss of HDMI signal, it would come back after a beat or so), but that seems not to be the case. Just gotta mash.

 

On Manjaro, not that it matters here, option (or alt) F2, then F1, works to bring up the (GUI) login screen. Again, other distros (with open-source drivers) and Windows (with the latest Radeon drivers) are not so finicky with this card.

 

I have not been monitoring how well the RX 6600 XT works with all macOS versions that have drivers for it (ie. from 12.1), but the first paragraph above is my experience so far. Nicely (and anecdotally, sorry I have no screenshots with specifics) full-screen Ultra-settings Unigine Valley benchmarks at FHD get around 4300, where on Windows or Linux, they get around 4200. So the fruit company's doing something right for speed, out of the gate! Blender 3.1 renders (only with files that explicitly support GPU rendering; others may lock your system up in any OS!) are nice and tidily fast (feels faster than HIP in Windows, haven't found a driver/don't want to install AMD Radeon PRO drivers, in favor of open-source, that works in Linux) in Metal, which we Intel users had to wait for 12.3 to try out.

 

I might have tried A/B testing against my old RX 580 both for general UI use & the above testing, but that is now unavailable.

 

In a nutshell, my new card is having the same issues with 12.3 that it did with 12.2.1, which is to say login screen HDMI signal dropouts that you just have to mash at the keyboard early enough (right after either the boot progress bar or your -v text disappears) to get out of.

 

*Brand new but for having used by me for almost two weeks, though released in August.

15 hours ago, pkdesign said:

Anybody update to 12.3? i have heard there are issues with some graphics cards even on real Macs.

 

Yes, i'm in trouble with my 5700XT. Unfortunately i updated too early and now  there is no option other than downgrading to 12.2.1.

Many complaints can be found in the forums.

 

*s h i t*

 

 

 

2 hours ago, texem said:

 

Yes, i'm in trouble with my 5700XT. Unfortunately i updated too early and now  there is no option other than downgrading to 12.2.1.

Many complaints can be found in the forums.

 

*s h i t*

 

 

 

Some users on another well know forum found that injecting device properties solved most if not all the problems (either with SSDT or config.plist).

Here is what they used for the 5700XT, copied from properties of the "official" Apple card (I haven't tested myself as I'm holding off the update for now) :

<key>DeviceProperties</key>
    <dict>
        <key>Add</key>
        <dict>
            <key>PciRoot(0x0)/Pci(0x3,0x1)/Pci(0x0,0x0)/Pci(0x0,0x0)/Pci(0x0,0x0)</key>
            <dict>
                <key>@0,name</key>
                <string>ATY,Adder</string>
                <key>@1,name</key>
                <string>ATY,Adder</string>
                <key>@2,name</key>
                <string>ATY,Adder</string>
                <key>@3,name</key>
                <string>ATY,Adder</string>
                <key>device_type</key>
                <string>ATY,AdderParent</string>
                <key>AAPL00,DualLink</key>
                <data>AQAAAA==</data>
                <key>ATY,Card#</key>
                <string>102-D32200-00</string>
                <key>ATY,Copyright</key>
                <string>Copyright AMD Inc. All Rights Reserved. 2005-2019</string>
                <key>ATY,DeviceName</key>
                <string>W5700X</string>
                <key>ATY,EFIVersion</key>
                <string>01.01.190</string>
                <key>ATY,FamilyName</key>
                <string>Radeon Pro</string>
                <key>ATY,Rom#</key>
                <string>113-D3220E-190</string>
                <key>CAIL_EnableLBPWSupport</key>
                <integer>0</integer>
                <key>CAIL_EnableMaxPlayloadSizeSync</key>
                <integer>1</integer>
                <key>CFG_CAA</key>
                <integer>0</integer>
                <key>CFG_FB_LIMIT</key>
                <integer>0</integer>
                <key>CFG_FORCE_MAX_DPS</key>
                <integer>1</integer>
                <key>CFG_GEN_FLAGS</key>
                <integer>0</integer>
                <key>CFG_NO_MST</key>
                <integer>0</integer>
                <key>CFG_NVV</key>
                <integer>2</integer>
                <key>CFG_PAA</key>
                <integer>0</integer>
                <key>CFG_PULSE_INT</key>
                <integer>1</integer>
                <key>CFG_TPS1S</key>
                <integer>1</integer>
                <key>CFG_TRANS_WSRV</key>
                <integer>1</integer>
                <key>CFG_UFL_CHK</key>
                <integer>0</integer>
                <key>CFG_UFL_STP</key>
                <integer>0</integer>
                <key>CFG_USE_AGDC</key>
                <integer>1</integer>
                <key>CFG_USE_CP2</key>
                <integer>1</integer>
                <key>CFG_USE_CPSTATUS</key>
                <integer>1</integer>
                <key>CFG_USE_DPT</key>
                <integer>1</integer>
                <key>CFG_USE_FBC</key>
                <integer>0</integer>
                <key>CFG_USE_FBWRKLP</key>
                <integer>1</integer>
                <key>CFG_USE_FEDS</key>
                <integer>1</integer>
                <key>CFG_USE_LPT</key>
                <integer>1</integer>
                <key>CFG_USE_PSR</key>
                <integer>0</integer>
                <key>CFG_USE_SCANOUT</key>
                <integer>1</integer>
                <key>CFG_USE_SRRB</key>
                <integer>0</integer>
                <key>CFG_USE_STUTTER</key>
                <integer>1</integer>
                <key>CFG_USE_TCON</key>
                <integer>1</integer>
                <key>PP_DisableDIDT</key>
                <integer>1</integer>
                <key>PP_DisablePowerContainment</key>
                <integer>1</integer>
                <key>PP_DisableVoltageIsland</key>
                <integer>0</integer>
                <key>PP_FuzzyFanControl</key>
                <integer>1</integer>
                <key>hda-gfx</key>
                <string>onboard-1</string>
                <key>model</key>
                <string>Radeon Pro W5700X</string>
                <key>name</key>
                <string>ATY_GPU</string>
            </dict>
        </dict>
        <key>Delete</key>
        <dict/>
    </dict>

 

  • Thanks 1

cool ,  i'll test this later and report here 👍

 

---

 

update: it's working , no issues anymore .

 

btw: on z390 , the PCI path is     <key>PciRoot(0x0)/Pci(0x1,0x0)/Pci(0x0,0x0)/Pci(0x0,0x0)/Pci(0x0,0x0)</key>
 

 

Edited by texem

Well {censored}. Tried to turn my build on after shutting it down 2 days ago, and nothing happens when I try to turn on. No fans spinning, no bios screen, no nothing! I was looking at the new M1 MacBook Pros all day yesterday and today might be the day for the upgrade..

Its an issue with the PSU, will turn on for a few seconds then shuts off. Regardless, I think I'm just going to throw in the towel and get a MacBook Pro 14in, and give this to the little brother as a gaming computer. I really hate to see the potential of it go to waste, but as of late I really want something mobile/I can move around the house with. I've been using a remote application called "Screens 4", but its hardly the same experience.

  • Sad 1
6 hours ago, stavidawg said:

Its an issue with the PSU, will turn on for a few seconds then shuts off. Regardless, I think I'm just going to throw in the towel and get a MacBook Pro 14in, and give this to the little brother as a gaming computer. I really hate to see the potential of it go to waste, but as of late I really want something mobile/I can move around the house with. I've been using a remote application called "Screens 4", but its hardly the same experience.

Some times bios related issues, or hardware configuration / failures will cause the computer to instantly shut down.

 

if you have multiple sticks of RAM, try removing some, unplug anything not needed, USB devices, PCIe cards, graphics card, reset bios / remove replace CMOS battery and try again.. 

 

power supplies are not a huge cost to be fair if it is that. 

×
×
  • Create New...