Jump to content

backinblackx86

Members
  • Posts

    167
  • Joined

  • Last visited

  • Days Won

    6

Everything posted by backinblackx86

  1. https://elitemacx86.com/threads/how-to-fix-reboot-loop-when-installing-or-updating-to-macos-sonoma-14-4.1720/
  2. https://forum.amd-osx.com/threads/problem-with-14-4-sonoma.5038/post-34156 ”Hello I've been investigating and discovered the problem. I had all the kexts updated to their latest version. Solution: Set the SecureBootModel to Disabled instead of Default under the Misc>Security section of your config.plist.”
  3. The update shows under system preferences, it installs and asks to restart. Upon restart, “macos installer” is now shown in the Opencore picker and runs until reboot. Last the installation for update is selected by default in the opencore picker and runs for approximately ten minutes. However, upon reboot, still loads 14.3.
  4. Something isn’t quite right. After the 14.4.1 update, it rebooted back into 14.3 @Lorys89 @fabiosun
  5. The 10GbE NiC issue has been resolved and I am on F3d. I cloned my NVME and am now in the process of updating Sonoma to 14.4.1.
  6. I do believe the 10GbE LAN2 disappearance was BIOS related. After downgrading to F2, pulling the NVMe, main PSU power and the BIOS battery backup, the system posted to show LAN2 again. There is an option of maintaining to DMI data between BIOS flashes, perhaps that is the issue. I have yet to boot into MacOS yet.
  7. I checked to make sure IOMMU was disabled as was SIP…still no AQ 10GbE Odd…the BIOs reports LAN2 MAC Address as N/A
  8. I have installed a second 4TB WD850x to clone my installation onto and have updated the BIOS to F3D. Unfortunately, my 10GbE AQ Nic is no longer seeing connection… Could F3D bios have affected this patch? @Lorys89
  9. I add the boot arg “revpatch=sbvmm” and now the Sonoma update does appear. I will first clone the functioning system before any updates are made.
  10. Upgraded my setup with a Samsung Neo G9 57" display. I found HDMI did not support full resolution but Display Port did. Graphics/Displays within System Profiler shows: AMD Radeon RX 6800 XT: Chipset Model: AMD Radeon RX 6800 XT Type: GPU Bus: PCIe PCIe Lane Width: x16 VRAM (Total): 16 GB Vendor: AMD (0x1002) Device ID: 0x73bf Revision ID: 0x00c1 ROM Revision: 113-EXT800245-L02 Metal Support: Metal 3 Displays: Odyssey G95NC: Resolution: 7680 x 2160 UI Looks like: 3840 x 1080 @ 60.00Hz Framebuffer Depth: 30-Bit Color (ARGB2101010) Display Serial Number: HNTWB01398 Main Display: Yes Mirror: Off Online: Yes Rotation: Supported Connection Type: Thunderbolt/DisplayPort
  11. I did find reference on the ASUS forums to a firmware update available for the Crucial T700 via the Windows software "Crucial Storage Executive" (https://www.crucial.com/support/storage-executive). Although I have not tired the nvmefix.kext yet nor have I tuned the setapfstrimout parameter, I will more than likely use this 5.0 NVME for either Windows or Linux as MacOS TRX50 does operate well paired with the WD SN850X.
  12. I tried both and each failed to format the T700 disk as APFS or HFS. The crucial website does not provide any updates.
  13. Hello, I am writing from the Trx50 booted into Sonoma. Going to try and use this system for video editing. My system disk is the Western Digital branded SN850X, however, I do believe the secondary nvme, the Crucial T700 may be causing issues. The system reboots while Disk Utility attempts to format the T700 as HFS or APFS, only exFAT formatted successfully.
  14. my local micro-center location has the “ASUS TRX50-SAGE Pro WS WiFi AMD sTR5 CEB Motherboard” https://www.microcenter.com/product/674949/asus-trx50-sage-pro-ws-wifi-amd-str5-ceb-motherboard
  15. After those changes, Monterey will still not boot. Sonoma did however.
  16. the 6900 and 6950 are higher scores of Gigaflops, but my Vram Speed is faster! @fabiosun
  17. Disabling Gatekeeper allowed me to run the benchmark application. Attached is a screenshot of my Trx50 results.
  18. I cannot open the benchmark software on Ventura or Sonoma. I disabled SIP and the .app failed to launch with the terminal.
×
×
  • 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.