Driftwood

https://audiosex.pro/threads/sip-enabled-for-steinberg-and-v-r-stuff.74681/

Wondering if these SIP workaround techniques could be used for VBox ? 

@tomnic As I'm currently using Sonoma 14.2 (23C64) apparently there was a cursor / pointing device bug with this version of the OS from what I was reading somewhere and I think its not been helping the vbox guests with sluggish 'forgetful' performance. Whats the latest version of Sonoma (14.4.1) been like with pointer control in VBox guests?

For Win 10 32-bit SYSTEM setup I'm finding this seems to work best / quickest.

3 hours ago, tomnic said:

 

Thanks for your appreciation on my guide, probably resetting the nvram parameters recreates the kext blacklist, I'm on 6.1.48 right now and I'll try with 6.1.50.

Yes the new AMFIPass doesn't require the specific bootflag, I'll update the guide.

@tomnic Ive updated the above to see if you spot any additions I need!

On 11/13/2023 at 11:06 AM, tomnic said:

But how can we get Virtualbox running on recent macOS? The prerequisite is to disable SIP and use the AMFIpass.kext with the bootflag -amfipassbeta in order to allow VirtualBox kexts to be loaded once installed, nothing more. In fact, once rebooted and allowed the kexts to run in Security section you can even disable the loading of AMFIpass.kext and remove the related bootflag, by now the kexts have bypassed the blacklist, forever!
 
After that you can also install Windows 11 as a VM, direct without any issue, and the performance is also great if you don't overdo the number of cores (my maximum is 2 then it starts to slow down)!!!

Hi Tomnic,

Nice guide.

Ive tried this with 6.1.50 and everything working installing Win 10 guest into the Box Host on Sonoma(in the process installing Win 32bit apps I needed  etc...)  but on reboot and resetting NVRAM SIP to 0000000 & removing the AMFIPass kext in config.plist its back to the kernel error cant load. Any info on this?

BTW I used AMFIPass v1.40 and didn't require the bootflag -amfipassbeta

METHODOLOGY

1. In config.plist (see image) inside your boot EFI, Add the numbers csr-active-config = 03080000 (see image)  into the NVRAM section of config.plist (to workaround security & Privacy Oracle Box kext sign problems with this partial SIP disable).

2.  Add AMFIPass.kext details (see image) into kernel section of config.plist.  Save config.plist back to the EFI /OC folder.

3. Download version 1.40 of AMFIPass.kext and copy it over onto your EFI drive's Kext folder.

4. Ensure you can reset NVRAM in Opencore when rebooting

5. Reboot, and hit space, number to reset your NVRAM.
6. Now it should boot with your SIP disabled and use AMFIpass to allow the box kernel thru.

7. Download & install Vbox v.6.1.48 or 6.1.50

8. During the installation process it should ask you to sign / allow the Oracle Virtual Box / ALLOW it inside your 'System Settings' Security & privacy section.

9. After install and the kernel of box has been signed it will ask to reboot. Go ahead and reboot.
10. After reboot, locate and download/install Oracle_VM_VirtualBox_Extension_Pack-6.1.50.vbox-extpack (if using ver 6.1.50)

11. Now grab a ISO from Microsoft and install your guest OS - in my case it was Windows 10 32 bit iso

12. Go thru the motions of installing the guest OS like you normally would.

13. Locate and download VBoxGuestAdditions_6.1.50.iso or VBoxGuestAdditions_6.1.48.iso and install them from a guest ISO storage drive.This will provide a number of addition hardware features and functionality.

14. Finally, fine tune your guest OS for display USB pointing devices etc...

15. If you get problems running virtual box - quit Vbox completely (stop any guest VMs running first if you can) and then rerun it by running it from within Applications folder and not as an alias as sometimes aliases get corrupted or lose sight of the software.

16 I tried then resetting SIP to Enabled and disabling AMFIPass kext inside config plist Kernel section, reboot, resetting NVRAM and booting up to Sonoma but the Kernel errors reappeared and I found they were no longer 'Allowed' by the OS. Subsequently, virtual box guest VM's failed to start. 😞

17. So went back to partially Disabling SIP (csr-active-config = 03080000) but didn't require AMFIPass to ON now that Ive installed vBox.

More on this soon...

useful links:

Virtual Box Old Builds: https://www.virtualbox.org/wiki/Download_Old_Builds_6_1

and https://download.virtualbox.org/virtualbox/6.1.50/ to find the Guest Additions etc...

AMFIPass kext: https://community.macmeup.com/index.php?/files/category/3-kexts/. or payloads/Kexts/Acidanthera/AMFIPass-v1.4.0-RELEASE.zip

Any news on the 7970X 32 core 64 thread working under Sonoma?

14.2 beta

ok too

Sonoma 14.1 23B74 all good on TRX40.

On 10/14/2023 at 1:20 PM, fabiosun said:

I think so

but I think price will be monster

and I would like to have a platform with the change to upgrade also the cpu without changing the motherboard

trx40 missed that part 

we will see

the future seems more interesting than recent past🥹

And you're not tempted by the Intel Core i9-14900K? 😉

On 6/6/2023 at 2:10 PM, fabiosun said:

So @fabiosun are you thinking the forthcoming 7975WX TRX50 will be viable? 

@Jaidy PCIe 5.... Looking at the random write/read speeds its probably not worth it atm. Cache problems aside the tech looks great in theory. But we wait and see. As to the T700 not being stable under MacOS seems strange. Did you try Disk Utility in macOS Recovery to format the volume?

Sonoma 14.1 beta 3 TRX40 all good.

10 hours ago, Jaidy said:

Was this problem ever solved? I just populated all of the m.2 ports on my machine, and occasionally it won’t boot, or boot to black screen, or restart midway. Though once it gets to desktop, things are solid. 
 

also I added a second GPU (7900XTX)..

You should check resources - PCIE which ones are directly connected to CPU and which are to chipset. All devices inc USB devices are taking up resources. DO a count and subtract from the total available for your motherboard. Maybe take out a device - a drive, a GPU etc... (experiment) until you see a happy compromise.

For example, The ASROCK TRX40 Creator features 88 PCIE lanes, 72 of which are useable to the end user. The Threadripper AMD CPUs utilise 56/64 PCIe 4.0 lanes.

Chipset vs. processor allocated PCIe lanes

The PCIe lanes on a motherboard originate either from the processor itself or the motherboard chipset.

Generally, the processor lanes are reserved exclusively for the graphics card x16 slots and M.2 slots for high-speed SSDs, as they require to move data without being bottlenecked by the chipset.

On the other hand, chipset lanes connect to onboard USB, other M.2 and PCIe slots, and SATA. The chipset itself transfers data to the processor via a dedicated 4-lane PCIe bus.

So, all devices connected via PCIe lanes to the chipset will have a cap on their maximum bandwidth leading to bottlenecks

Don't forget to run MMIO Opencore checks as u go.

Sonoma Beta 2 14.1 on TRX40 Asrock Creator 3970X all good.

Great to see the Fireface800 and TI Firewire PCIe card chipset still working in Sonoma! 🙂

DRIFTWOOD SONOMA 14.0 CONFIG PLIST (OC 0.9.5) for Asrock TRX40 Creator ATTACHED - not bothering with BT / Wifi in this config. Just Aquantia networking here! 

DRIFTWOOD-config.plist.zip

Old machine... still top using Davinci plugins!

Its a great performer (AMD 9 7950x) but with 32 cores, the TRX40 3970x still wins!

Out of interest @fabiosun how much did you sell your 3970x for?

@fabiosun

On 1/24/2023 at 8:05 AM, fabiosun said:

 

Yes!

LOL.

Thought I'd poke me head on here, GREAT work by @CaseySJ on the A107 patch. Cheers.

cant seem to install amdfriend. trying to get node in home-brew seems to be bad url:

Downloading https://ghcr.io/v2/homebrew/core/node/manifests/15.12.0

curl: (22) The requested URL returned error: 404   

Have you done Waves plugins? trying to demo Clarity FX and doesnt seem to open on AMD / causes crash in Davinci - others plugins work from Waves!

On 7/14/2022 at 1:24 AM, iGPU said:

Two issues.

 

First, I get the same error msg that @valmeida mentioned above even on Z690 system under Ventura when trying to use python. I'll give the RunMe_Downloader a try.

 

2nd issue: a couple of weeks ago, I updated the Big Sur drive to the latest 11.6.7 version and after it re-booted, the adjacent NVMe drive containing Ventura disappeared from the desktop. This past weekend I finally had time to investigate (I was too busy getting COVID for the 3rd time the previous week; so annoying!).

 

The Ventura drive was located in the M2_1 (CPU) slot; Big Sur is in the M2_2 (CPU) slot and Win11 is in the M2_3 (PCH) slot, as shown below on my MSI TRX40 Creator mobo:

 

 

 

To initially trouble-shoot, I swapped the Ventura and Big Sur drives with each other. The Ventura still did not show up on the desktop (nor was the Ventura drive visible within Disk Utility and it did not show up in BIOS). The faulty drive is a Sabrent Rocket Extreme 1TB NVMe SSD.

 

I removed the Ventura containing NVMe drive and placed inside an external NVMe SSD enclosure in order to test with the Z690 computer and a real Mac laptop. It did not show up on the Z690 desktop (both Big Sur and Ventura), but left connected to the laptop (Big Sur), it did appear on the desktop after 5-10 minutes. At this point, the drive tested ok, but its behavior is not normal, so I'm suspicious of it being faulty.

 

I then returned the Ventura containing drive to the MSI mobo. It still will not show in BIOS nor macOS. So I don't know if the mobo is faulty and somehow damaged the NVMe drive, or if the NVMe drive itself is the problem. The Big Sur NVMe works in either the M2_1 or the M2_2 slots, so this suggests that the mobo is working okay.

 

Lately, I've been buying WD_Black NVMe SSDs and they seem more trustworthy and seem to have more positive comments than the Sabrent drives.

 

Have any of you had similar problems?

 

Yeah I had a Sabrent Rocket 8TB m2 go down on me. I have come to the conclusion that their drives are not reliable (probably chipset and heat related). The MP600 I also use have been brilliant and 100% reliable. I wont be buying Sabrent again. Luckily, they changed ny 8tb out for a new one but not after going through weeks of backwards forwards  RMA process and a costly return to the states where you have to provide your own shipping delivery and pickup. It seems they have no support in Europe and  they will only deliver to a stateside address if you send it back to California.
Perhaps the first thing to do is confirm the drive is defo faulty - I actually bought one of their external m2 to USB C drive enclosures to confirm to them it was faulty.

 

For Camtasia 2019 you have to code sign all the files inside Camtasia 2019/Contents/Resources as well as the main app and delis to enable recording, thumbnails, audio etc.

.

Finally back up and running as my 3970x failed and was replaced / returned under warranty, thank god. Gloriously still on Monterey 12.2.1. Still the only version with Aquantia working well!

On 5/18/2022 at 6:56 PM, fabiosun said:

all is fine with kernel patches again!

 

Can you test the Aquantia onboard again?

On 3/14/2022 at 3:55 AM, iGPU said:

I'm just getting back onto the forum after a hiatus (many reasons...).

 

Due to a "gut feeling" I stopped using Monterey betas a few months ago and settled on the official releases. The one I've been running is 12.2.1. I've been heavily using the TRX40 for many tasks and for the most part, there have been no issues.

 

However, on reading recent posts on this thread, there seem to be many issues with the Aquantia and I211 ports, especially with the latest Monterey beta releases. As a means of skirting the problem, I decided to try an AIC. Of the many I've tried (and those failed), this one (here) works well and it's not expensive (< 30 USD). It should allow speeds up to 2.5 Gb (my network is only 1 Gb). Until the latest Aquantia-Marvell 10Gb AQN113 AICs are available (the AQN113 is used on the latest M2 Macs and should work OOTB), I think this AIC may be a good interim substitute.

 

This AIC does require a special kext file: Mieze's kext (LucyRTL8125Ethernet). This can be downloaded via the Kext Updater app or on the InsanelyMac site (here; which also has a discussion about the RTL8125), but to save time I've added the version I downloaded last night as an attachment.

 

Do note that I've only tested on 12.2.1, so I don't know if there will be an issue on the more recent betas, but since it's dependent on a current kext file, i rather think it will still be functional. In the next couple of days, I take a spare drive and update it to the latest beta to further test.

 

Hackintool and Network Utility:

 

And with HackCheck:

 

In case anyone is interested, I'll attach the SSDT used to re-name the D0C8 device to ETH2. But this SSDT will probably need adjustment of the device based on your mobo, which should be a trivial task using IORE.

 

 

LucyRTL8125Ethernet.kext.zip 113.38 kB · 2 downloads

SSDT-TRX40-Realtek-RTL8125A.aml.zip 800 B · 2 downloads

Hi @iGPU Yeah I saw that. However, you should know, the Aquantia works fine in 12.2.1.    Its anything newer after that doesnt work

7 hours ago, fabiosun said:

@Driftwoodit doesn’t work

tested yesterday all things available

system freezes if cable is connected

 

Did you try upgrading your Aquantiia firmware first  - what version you using?

I was reading somewhere that only the Secure version of the Aquantia 107 (107S) is now compatible with Apple OSX 12.3 onwards so no matter what we try, it may fail.