Jump to content
You are a guest user Click to join the site

iGPU

Donator
  • Content Count

    378
  • Joined

  • Last visited

  • Days Won

    9

iGPU last won the day on September 6

iGPU had the most liked content!

Community Reputation

197 Excellent

1 Follower

About iGPU

  • Rank
    Senior Member

Recent Profile Visitors

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

  1. @fojerhar is correct, we would have really cluttered the thread last weekend. It took many emails and various file exchanges to solve. Once in the correct slots (when we trouble-shoot, we rarely think to try a single GPU in anything other than slot 1), and with an adjusted DSDT, the Firewire card now works well.
  2. Yes, disabling these 4 patches, still allows booting into Big Sur ß6 and ß9 (I have no ß7 or 8 to test), as well as Catalina.
  3. I initially tried booting TRX40 with Clover (both VM and bare metal) and had no success. OpenCore works so well, I don't see why to use Clover any longer (except for nostalgia). A couple of weeks ago, I spent time converting other builds (X299 and Z390) completely over to latest OpenCore from Clover. I only go forward with OpenCore.
  4. I would concentrate on getting the Firewire drive to mount in macOS (before working on the UAD device). Have you tested booting into macOS with the Firewire drive already connected before turning on computer?
  5. I've spent some time trying to investigate our BIOS for Thunderbolt locations. For the MSI TRX40 Creator, using a combination of UEFITool and ifrextract, I could localize Thunderbolt sites and extract a text file. Locate sites: Extract bin file: The resulting text file (extraction from above "THUNDRBOLT" search): If this file is searched for "THUNDERBOLT", excerpted and re-arranged, the following is seen (included are proposed actions for each site, such as 0x0 to turn off or 0x1 to turn on; some are values for size): Next, using this data and running a special modified GRUB in an EFI, one should be able to check out these sites and adjust. (I used this tool to modify CFG Lock on Intel BIOS, so it does work.) However, this is where everything fails on this TRX40 BIOS. I get an error when simply trying to verify the status of the sites in GRUB. I think everything is accurate up to using the modified GRUB tool. (As I could not load nor verify a site, I could change nothing as proposed in the above text file.) I can only assume we need a different modified GRUB. *** I also studied the BIOS from GB TRX40 Designare. This was decidedly different from the MSI TRX40 Creator, not only in address location, but also the variables. For example, it allows selection between Alpine and Titan Ridge cards. Detailed extraction from GB TRX40 Designare:
  6. Firewire is natively loaded with macOS (at least through Big Sur); there are no extra kexts to load and there is no impact by usual SMBIOS that we use (I'd recommend iMacPro1,1 as any SMBIOS with an internal GPU is not a good idea with the TRX40 build). I've used Firewire AIC on each of my builds without issue (Intel X99, Z390, X299 and AMD X570, TRX40 with macOS ranging from Mtn Lion to Big Sur). In other words, Firewire just works with macOS. Further, the OC boot loader has little influence aside from injecting properties via an SSDT or DevProp (well, if you want to boot from a Firewire device, then you must re-calculate the ScanPolicy; but you shouldn't try this until the Firewire port is actually working). Further, an inoperable Firewire device will have nothing to do with AMD or patches. As long as you're booting into macOS, your patches are fine. I think your problem is related to the type of device you're trying to connect to the Firewire port. And what exactly is/are the Firewire device(s) that you're trying to connect? (Testing with a Firewire hard drive is the most certain method to verify the Firewire connection.) To clarify so that I understand you, when you boot into Windows, you can connect a Firewire device and use it? If the Windows response is 'yes, I can connect a device to the Firewire port and it works', then it should work in macOS, but with some caveats. Again, I would suggest connecting an external Firewire hard drive to test. However, If you don't have a hard drive and you're using an audio device, it will require a software driver, supplied by the manufacturer of the audio device, to interface between macOS and the Firewire audio device. If the software driver is not present or not working, then this device will not work under macOS (despite working under Windows because the proper Windows driver was installed). This is why I'd trouble shoot with an external Firewire hard drive, not a complicated audio device. If you insist on testing with an audio device, and you're certain that the driver was installed and the Firewire device won't connect, then it must be a problem with that macOS and the manufacturer's driver. At that point, you'd need to contact the manufacturer of the audio device. If the driver cannot work with Catalina or later, you might have to revert to Mojave or an earlier macOS for compatibility.
  7. D0A1...D1B1 are devices seen in the DSDT file: I don't see such a listing of devices. When I run the same command, after running Sleep, then awakening again, I see the following (sleep was enabled for about 15 sec, which is what is shown in an excerpt of the results, below).
  8. I don't think an SSDT will help. It sounds more like a Logitech, macOS driver problem. I'd try a powered hub as a work-around; this is the one I use.
  9. I too installed ß9 bare metal, but over ß6 (I never installed ß8). Since I'd removed the Snapshot partition, it is not possible to install the partial update (only a full installer can do this). So, I booted into Recovery, re-installed ß6, then updated with the partial ß9 installer downloaded from Apple. I have 2 Big Sur drives, the other one I'm leaving at ß7 (Snapshot was removed on this drive too).
  10. I'm using the Logitech C920 without issues. I do have it and most things on my desktop connected to an USB Hub which has it's own power. Your OS (whether Mojave, Catalina or BS) should have no bearing on this issue. I don't even think your EFI should much matter on this build, esp if you're using few SSDTs. Can you plug your old C920 into the same port to verify that it works? Next, I'd look at Logitech driver issues: are there any special drivers required by Logitech for the BRIO (and did you need to uninstall old drivers for the C920)?
  11. The DeviceProperties injection is working. I would expect functionality since drivers are loaded in yours as well as mine: What does it show when you select Firewire in same SystemInfo section? Mine shown below: The above image changes to the following after a Firewire device is connected and turned on (in this case an RME Fireface 800):
  12. Your card looks like it should be fine. The one I'm using is here. I've attached an OpenCore DevProp that may help inject some function for your Firewire card (copy and paste it into your DevProp section; then reboot). You'll need to adjust the address using Hackintool as I shown below (I'm including the instructions as I don't know if you've used Hackintool before). Based on your IORE file, it looks like you're using the card in slot-3. I'm using in slot-2 (but I'm using water-cooled GPUs that expose slot-2, which would otherwise be obscured by the GPU in slot-1). I don't recall whether you tried in different slots, but if slot 2 (D0A2/D0A9) is not available, perhaps try in slot-4, repeating the instructions below to re-calculate the address for slot-4. In slot-4, it will probably appear at D2A2 in IORE. *** 1) Use Hackintool to extract PCIe data into a text file: 2) From pcidevices.txt, look for and copy the address for your Firewire card: 3) Use this data to adjust the DevProp address in OpenCore for your build (replacing the high-lighted blue section with the correct address; once done, re-boot and see if it works): DevProp-FireWire.plist.zip
  13. The drivers are being ported from Linux (here) with OpenIntelWireless/itlwm for Wifi drivers and ~/IntelBluetoothFirmware for BT drivers. I've been using the drivers on/off as they've progressed over the past year. BT has been working from the start with a gradual expansion of supported chips (read the site for models). Wifi has become better supported than it was a year ago and is simpler to use. I swapped out the BT/Wifi chip and so do not use these drivers on the TRX40 build. I've used them thru VM (where I made posts some months ago on this forum) and on Mojave, Catalina and Big Sur.
  14. Agreed: no audio from USB. But curiously, the USB Audio interface does light up as if responding to varying audio levels, but nothing is going to the speakers. Meanwhile, Firewire audio is good, but completely out of sync with the video (on YouTube for example). Earlier today, I tried the disabling of UpdateDataHub on both Z390 and X299 systems and found little improvement in speed. But I did not check audio on those systems. (I'll recheck later.) I just read Pavo's post above; this would explain the difference between AMD and Intel when disabling UpdateDataHub. Sigh... back to usual speed.
×
×
  • 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.