Jump to content

iGPU

Moderators
  • Content Count

    572
  • Joined

  • Last visited

  • Days Won

    16

iGPU last won the day on March 22

iGPU had the most liked content!

Community Reputation

385 Excellent

2 Followers

About iGPU

  • Rank
    Senior Member

Recent Profile Visitors

The recent visitors block is disabled and is not being shown to other users.

  1. 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 t
  2. As I recall it had to do with the original DSDT files for each mono being a little different. The mobos with internal TB had that device declared in the DSDT and I tried to add similar declarations to out mobos but it didn't work. On another topic, when items are defined for RestrictEvents in the NVRAM section, the same items need to be Deleted. I'd over-looked that step and recently caught the resulting error. See image below. RestrictEvents works better when set up this way, deleting all items that were added.
  3. The USB-C mounting just got more confusing. I have a couple other USB-C drives, all by different companies and each with different macOSes on them. My initial tests were performed with the SSK Media drive that contains Monterey. It turns out that the different drives all behave differently between Big Sur and Ventura. The differences are summarized in the table below. There are differences between Big Sur vs Ventura but fortunately the Z690 and TRX40 mobos behave the same. So there are some differences with Ventura, as shown in red box above. The ASMedia dr
  4. I've been having issues with USB-C drives not mounting (appearing) on the desktop under Ventura. There are zero problems with previous macOSes. See this post here and here for my initial comments. I posted on the InsanelyMac forum as I thought it was a Z690 issue but when testing on the TRX40, I had the same problem (again, only with Ventura). As shown below in the Hackintool USB section, the USB stick does appear on the desktop, while the external USB-C drive, whether I use a USB-C to USB-C or USB-C to USB-3 cable, does not appear on the desktop. Since the USB-C drive
  5. I've used that AIC and the Fenvi T919, both in the TRX40 and Z690 builds, and each build seems to worksbest if I used extra kexts, esp to get AirDrop working.
  6. Despite people saying these cards work OOB, I've never found that to be true. The Fenvi T919 works just fine in Mojave through Ventura, but you need different kext files based on the OS version. For Monterey and Ventura you need the following:
  7. Thanks for your hope: I got it to work. using the latest kexts and OC commits, and by setting Platforminfo/Generic/ProcessorType to 0. Your config file showed me the main difference of the ProcessorType value. I had been using 3841. Before this fix, the same error was occurring in the latest Big Sur update 11.6.7. (So whatever changes were in Ventura causing this broken RestrictEvents issue, were also added to 11.6.7.) I also was able to inject my specific verbiage using these arguments:
  8. Strange, but despite using latest RestrictEvents and Lilu (and re-setting NVRAM), my processor still shows up as Unknown (works okay in Big Sur).
  9. I've done all these things (aside from patches, same set up for Z690). I looked over your config file and we have the same Patches and Quirks. It continues to fail at about the same point (which is just before log-in; shown in Spoiler below). I'll try to re-install and if that fails, then I'll do a fresh install. Re-formatting and a fresh install did not help: things still got stuck at the final boot heading to login. More investigation... ***** Success! The key was adding AppleMCEReporterDisabler kext (which I noted in
  10. I'm not able to yet test TB on the TRX40 as I cannot manage to log into Ventura. (Update on the Z690 was ok, but not yet for the TRX40). I decided on the TRX40, instead of a fresh install, to update the Monterey drive for Ventura (I'm presently writing this from the BS drive). The update process seemed to go well, but I believe cannot complete the final boot into Ventura. From the OC menu, I do have the option to boot into Recovery, but that too fails as shown in Spoiler below, where I think many Ventura updates fail. I usually do not have Above 4G enabled, so
  11. Same: I too was never able to clean install Windows on the TRX40.
  12. I got the Z690 working in Ventura tonight (here) doing a fresh install. It went very smoothly and installed really fast (no 10-30 min count downs on any re-boots during the install). I'll give the TRX40 a go tomorrow night (I've already adjusted a TRX40 config file for Ventura with updated patches, etc).
  13. There are 2 updates to Lilu and VirtualSMC that are supposed to help with 13 (and the "-lilubetaall" boot argument is not required). Maybe these will help you?
  14. Even if the I221 and Aquantia ports go wonky with macOS updates, there is another option as I described in an earlier post here. This AIC card is fast, inexpensive and does not depend on BIOS settings.
×
×
  • Create New...

Important Information

We have placed cookies on your device to help make this website better. You can adjust your cookie settings, otherwise we'll assume you're okay to continue.