Jaidy
-
Posts
219 -
Joined
-
Last visited
Content Type
Profiles
Forums
Events
Downloads
Posts posted by Jaidy
-
-
20 hours ago, Ploddles said:
Monterey RC2 is out. That was quick!
nice to see a post from you, perhaps after a while. Hope everything is going well with you.
-
-
7 hours ago, fabiosun said:
I do not know if Apple will pass
tomorrowtoday from beta 10 to a release or a release candidate (RC/GM)Some problem could occur if you use an old EFi with old kext and OpenCore
If you use i211 ethernet in beta 10 it doesn't work
If you do not see in update Monterey Release (or beta if you use developer seed catalog) you have to update opencore to latest 075 and put in SecureBootModel Default value*
You can also follow all said above plus add RestrictEvents.kext (1.05)
*Many combination could help to fail your task..in some cases also TPM parameter used in BIOS could give improper update and problem
If you read in this thread you could find problems and (often) solutions we applied to solve this problem
Thank you. I shall try them when the time comes
-
hello everyone,
with the rumors that the Monterey would be released tomorrow, are there some special settings that needs to be done to boot that on our TRX40s or would the same EFI as I currently use to boot Big Sur work just fine?
-
8 hours ago, iGPU said:
I'm unaware of any Pro Hackintoshes. Here is a good overview of the feature set between Threadripper, Threadripper Pro and EPYC.
The price point for the Pro 3975X is not too much more than the 3970X most of us are using, at $2790 (there is a typo in the 32-Core table where they say the 3970X costs $3990; the MSRP is $1999). However, the price point for the Pro 3995WX over the 3990X is significantly more: $5490 vs $3990.
This price difference doesn't reflect the need for a new mobo since the socket is different for the new Pro models (so there's no swapping of the CPUs for a quick test). And then there's the ECC memory (in the referenced review, read the Comments section, users have found that the number of used DIMM slots affect performance and explain why).
In terms of performance, both use Zen 2 and little advantage was found except in memory performance. My guess is that except for the 3995WX (which uses 4 chiplets), the other Pro versions will have little improvement over our current CPUs in a Hackintosh. The next generation of Threadripper using Zen 3 will probably be a different story; they're supposedly due to arrive later this year.
I work with huge matrices. So far the limiting factor for me is the cap @ 256GB of RAM. Therefore I would like to get a TR pro, not for performance but for memory size. However I prefer staying on macOS, that’s why I asked..
- 1
-
Is there someone who’ve experimented hackintoshing on a TR pro platform? Or know of any?
-
16 hours ago, fabiosun said:
@Jaidyi did only davinci candle benchmark for graphic
gpu is about 5% slower than latest Big Sur
cinebench23 is the same as previous os
I see. Thanks so much for the info.
-
for people running Monterey, have you done any benchmarking to compare with Big Sur? Just curious...
-
2 hours ago, iGPU said:
I answered this already, here. Change your scan policy, yours is 3481 (try to carefully read the thread). And "SecureBootModel" is best left "Disabled".
Your should also look at the Quirk settings I posted on same page here.
AppleMCEReporterDisabler.kext is not necessary. I still use AppleALC.kext and WEG (but limit with "agdpmod=pikera"on the 6900XT). I've not seen anyone use "RtWlanU.kext" or "RtWlanU1827.kext" on the TRX40 builds, but perhaps you have add-on hardware of which I'm unaware.
Thank you very much. I have a usb wifi that gives me faster speeds.
-
hello you wonderful people,
I am facing an interesting problem. My EFI, while boots just fine, does not show me the macOS installer, (the external one) to boot from to do an installation from scratch at the OC's picker menu. Can some one please take a look at my EFI and fix the config.plist? I would be eternally grateful.
Here is the link to the EFI.
-
7 hours ago, Ploddles said:
If it boots back to the previous one then on the reboot during update it picked the wrong part to boot from.
Reboot again and see if there is an extra entry in the picker. If there is then boot that and it will probably complete the update. If there isn’t then try the update again and keep an eye out for the extra picker option and choose that. Remember you only have 4-5 seconds if you leave it to choose itself. It happens occasionally. Just arrow across to another choice to stop the timer.
there indeed is another entry, titled Macintosh HD or something. But that simply reboots the system when selected. Right now when I try updating using the system preferences' Software Update option, it says "The software update download failed. Please check your network connection and try again".
Furthermore, I got a kernel panic:
panic(cpu 32 caller 0xffffff8017698a66): [data.kalloc.8192]: element modified after free (off:64, val:0x0000000000000020, sz:8192, ptr:0xffffff94eac63000, prot:zero)
64: 0x0000000000000020
Backtrace (CPU 32), Frame : Return Address
0xffffffa44f85b460 : 0xffffff8016e870cd
0xffffffa44f85b4b0 : 0xffffff8016fcde93
0xffffffa44f85b4f0 : 0xffffff8016fbe48a
0xffffffa44f85b540 : 0xffffff8016e2ba2f
0xffffffa44f85b560 : 0xffffff8016e868ed
0xffffffa44f85b680 : 0xffffff8016e86be3
0xffffffa44f85b6f0 : 0xffffff8017696a3a
0xffffffa44f85b760 : 0xffffff8017698a66
0xffffffa44f85bbe0 : 0xffffff8016ee5a7a
0xffffffa44f85bc50 : 0xffffff8016e966dc
0xffffffa44f85bca0 : 0xffffff8016e61cac
0xffffffa44f85bcd0 : 0xffffff801763af67
0xffffffa44f85bd60 : 0xffffff801763acdc
0xffffffa44f85bd90 : 0xffffff8016e8c637
0xffffffa44f85be00 : 0xffffff8016e62d75
0xffffffa44f85be60 : 0xffffff8016e7a2d2
0xffffffa44f85bef0 : 0xffffff8016fa278d
0xffffffa44f85bfa0 : 0xffffff8016e2c216Process name corresponding to current thread: com.apple.AppleUserHIDDrivers
Boot args: chunklist-security-epoch=0 -chunklist-no-rev2-devMac OS version:
20G5042cKernel version:
Darwin Kernel Version 20.6.0: Mon Jun 7 19:29:33 PDT 2021; root:xnu-7195.140.29.131.1~1/RELEASE_X86_64
Kernel UUID: BD602B86-E76B-3B80-AE97-AE7E3EC2354A
KernelCache slide: 0x0000000016c00000
KernelCache base: 0xffffff8016e00000
Kernel slide: 0x0000000016c10000
Kernel text base: 0xffffff8016e10000
__HIB text base: 0xffffff8016d00000
System model name: MacPro7,1 (Mac-27AD2F918AE68F61)
System shutdown begun: NO
Panic diags file available: YES (0x0)
Hibernation exit count: 0System uptime in nanoseconds: 13150957515475
Last Sleep: absolute base_tsc base_nano
Uptime : 0x00000bf5f226b62f
Sleep : 0x0000000000000000 0x0000000000000000 0x0000000000000000
Wake : 0x0000000000000000 0x000000254236aa43 0x0000000000000000Can someone please tell me what happened here? It say AppleUserHIDDrivers, which probably means keyboard/mouse/trackpad driver issue?
-
2 hours ago, Ploddles said:
New Big Sur 11.5 beta 4 (20G5052c) is out. Let's hope the new Monterey patch list plays nicely with it - I probably won't get a chance to play with either until the weekend.
I tried updating to the latest beta 4, but it somehow is stuck. Boots back to the beta 3 for me. Hopefully you would have better luck..
-
6 hours ago, Ploddles said:
I've always read on here that you cannot run a Windows Virtual Machine on macOS on our Bare Metal Threadrippers.
As I was on day release from hospital today, I updated my machine to the latest OC release (0.7.0) and the latest BS Beta (11.5 beta 3). Whilst in hospital I had fixed a friends laptop that was continually crashing be wiping it and loading the latest Windows, Win10_21H1. As I had the ISO on a USB drive I decided to try a VM on the Threadripper, thinking it wouldn't work.
My copy of VM Fusion was very old, V6, so I downloaded the latest VirtualBox to play with. I know it isn't the best VM software but it is free.
It was with great surprise then that a Windows VM was up and running in a matter of minutes. No having to try and patch anything or anything else. I have always had SVM enabled in my BIOS setup so I didn't even have to change anything in there either.
So it works. I haven't tried passing through the RX 6900 XT or RX 6800 XT through to it yet, I was just astonished that it worked straight away.
glad you're back home!
- 2
-
@Allubz @Arrakis Which BIOS version are you two using? I have a TRX40 Aorux Extreme, F4q BIOS. I can not shutdown my system. It always restarts when I shut down. Previously this problem was solved by disabling "Wakeup on LAN access" option in the BIOS, but not for this one. If shutdown is working for you, would you have any suggestions?
-
1 hour ago, Rox67er said:
Just installed with no issue, also running MacPro7.1 but do not use WEG anymore. I miss display in 2nd boot stage but after drivers load all is well.
Exactly the same here.
- 1
-
5 hours ago, fabiosun said:
Did you get it directly from AMD or off of eBay? If the former, then how did you manage to get one so fast? I run a 6800 XT which is nice but it’d be cool to get a 6900XT
-
-
for the people running Gigabyte motherboards using F4q bios, do you have the problem we previously had when shutdown would lead to a restart? I have set the "Wake on LAN" to be disabled in the bios, but it still restarts when I shutdown.
-
On 5/1/2021 at 3:07 PM, iGPU said:
I've finally figured out how to correctly use the Memory section in OC. I decided to work on this since I've now changed to using MacPro7,1 instead of iMacPro1,1 due to the former apparently being a better match for going forward with AMD 6x00XT GPUs.
If you follow this guide carefully, you will not need the kext "RestrictEvents.kext" file, and you will no longer see a memory error. I've only tested in Big Sur, but it should work under Catalina as well.
Here's the guide (I've paralleled posted on another forum):
OC's "BANK" numbers were re-arranged to better match the memory upgrade instructions per Apples's docs. The Bank numbers in their order of appearance are slots: 7, 8, 9, 10, 11, 12, 6, 5, 4, 3, 2, and 1. These correspond to the slot numbers on the memory board. In Apple's docs, the slots are arranged into Channels, A-F. Channel A are Banks/slots 7, 8; Channel B are 9,10; C are 11, 12; D are 5,6; E are 3,4; and F are 1,2 (see spoiler below).
If properly arranged, below is what is seen with 8 DIMMs installed on my mobo. An actual MacPro7,1 has 12 slots, so our 8 DIMM slotted mobos will always have at least 4 banks empty. Now, should you only be using 4 memory sticks, then set to empty the following slots: 1, 2, 3, 5, 8, 10, 11, 12. In other words, if you are using 4 DIMMs, only slots 4, 6, 7 and 9 will be populated (thanks djlild7hina!).
Note: this does not mean you physically move your DIMMs about on your mobo; this whole process is to map your DIMMs into software locations where the macOS is expecting them to be positioned. Keep your DIMMs physically where the mobo manual recommends.
The code within OC is shown in excerpt below (the full code is downloadable as an attachment). Add it enbloc as the "Memory" section within the PlatformInfo section (also make sure to enable "CustomMemory"). The SNs are arbitrary (add your actual ones if you're more OCD than me). The part numbers are mine as used, made by Cosair; change these values as you wish. The AssetTag is also arbitrary but only entered if that memory slot is populated. Finally, change the Size and Speed values to better match your DIMM.
If SystemInformation is run, the following is seen:
In the attachment, I included the 8 DIMMs as well as one for 4 DIMMs (4 DIMM verified and fixed by djlild7hina on another forum). Inactivate either one with "#" symbol or activate by removing "#" and editing heading label to "Memory":
shifted to MacPro7,1, removed the Whatevergreen kext, and it boots without agdpmod=pikera argument. Thank @iGPU for this guide, works perfectly for me! 🙂
-
is there anyone using a non-reference RDNA 2 card and is able to get to desktop without using agdpmod=pikera boot argument?
-
2 minutes ago, Ploddles said:
You can add -wegoff to the boot arguments to test it or disable/remove whatevergreen.kext in the config.plist
everything works well now after disabling HDR. Now just waiting for OC 0.6.9 😛
- 1
-
for the people running RDNA2 cards, is there a problem with the display properties? I have a Benq EW3280 monitor, with a Power Color Red Devil 6800 XT. I am using agdpmod=pikera boot argument. The display is fed via a DisplayPort. It turns out that the picture is much less brighter than previously. Furthermore, on the On Screen Display (OSD) menu for the monitor, the Brightness and Contrast options are disabled. This seems to be a macOS thing, since when I boot into the BIOS configuration, then the brightness is fine, and also the aforementioned options are enabled in the monitor OSD.
Is anyone else facing this issue? Can some one advise me how to address it? I tried using Mac Pro 7,1 SMBIOS. That would boot to black screen too without the agdpmod=pikera argument. On another forum, it was mentioned that Mac Pro 7,1 definitions along with -wegoff works. I have not tried that. Is -wegoff a boot argument?
Never mind, HDR was enabled.
-
@Ploddles Is your system stable with 11.4's beta? Mine is my work machine so in the past I have avoided beta versions, though if its stable then I am getting impatient to use my 6800 xt. Also, can you please upload your EFI that works with 11.4, also OC 0.6.8? Finally can I update to 11.4 beta from 11.3, rather than a full install which would require me installing all my programs again too.
-
7 hours ago, valmeida said:
11.4 Beta 1 is out .
And it has the drivers for RDNA 2!! Woohoo!
[Discussion] - TRX40 Bare Metal - Vanilla Patches
in General
Posted · Edited by Jaidy
I could boot to the installer setup using an EFI provided very kindly by @Ploddles . Initially when I got to the screen where the installer setup is seen (i.e. a screen with a window with macOS Utilities), the options were not in English. I did a bit of digging around the web and someone suggested I remove whatever value is in the setting prev-lang:kbd, and reset NVRAM. I did both these, and now I boot to a gray screen which is supposed to show macOS utilities windows but nothing happens, it is sort of just stuck at the gray screen. Can someone please help me get past this point and on to the installer?