Jump to content

shrisha

Members
  • Posts

    105
  • Joined

  • Last visited

Everything posted by shrisha

  1. Hey Fabio, just want to report here. Problem with this nvme: "3rd party NVMe controller. Loss of MMIO space." kernel panic is 95% cases physical. not with System OS. I just took the M.2 drive out cleaned the contacts with pencil eraser and kernel panics stoped right away. So, if you have this issue try to clean it and see if it helps. Cheers.
  2. I found this yesterday: https://www.insanelymac.com/forum/topic/358947-possible-solution-loss-mmio-space/ Seems like this can help. Will see how it goes for few days. Will report here after. Thank you.
  3. Hey Fabio, hope you doing well. Sorry to bother you but again I need your help. I'm having kernel panic for a few days after I installed Davinci Resolve 19. According to report it's related to com.apple.iokit.IOPCIFamily kext. I don't know if it is Resolve done something, I doubt, also it didn't started after I updated opencore and kexts to latest two weeks ago. Everything was fine all this time but two days ago this start happening. What do you thing could be a cause of this? Thank you. crash_report.txt.zip
  4. I convert rest three into decimal and add them to whitelist now I have like this: 18:490 00:022 OCABC: VMware Mac installed on A39A7998 - Success 18:492 00:001 OCABC: Patching safe mode sur-2 at off 1F0B 18:494 00:002 OCABC: MMIO devirt start 18:495 00:001 OCABC: MMIO devirt 0xD2100000 (0x81 pages, 0x8000000000000001) skip 1 18:496 00:001 OCABC: MMIO devirt 0xD3180000 (0x81 pages, 0x8000000000000001) skip 1 18:498 00:001 OCABC: MMIO devirt 0xD9180000 (0x81 pages, 0x8000000000000001) skip 1 18:499 00:001 OCABC: MMIO devirt 0xD9300000 (0x100 pages, 0x8000000000000001) skip 1 18:500 00:001 OCABC: MMIO devirt 0xDA100000 (0x181 pages, 0x8000000000000001) skip 1 18:502 00:001 OCABC: MMIO devirt 0xFEA00000 (0x100 pages, 0x8000000000000001) skip 1 18:503 00:001 OCABC: MMIO devirt 0xFEC00000 (0x1 pages, 0x8000000000000001) skip 1 18:504 00:001 OCABC: MMIO devirt 0xFEC10000 (0x1 pages, 0x8000000000000001) skip 1 18:505 00:001 OCABC: MMIO devirt 0xFED00000 (0x1 pages, 0x8000000000000001) skip 1 18:506 00:001 OCABC: MMIO devirt 0xFED40000 (0x5 pages, 0x8000000000000001) skip 1 18:508 00:001 OCABC: MMIO devirt 0xFED80000 (0x10 pages, 0x8000000000000001) skip 1 18:509 00:001 OCABC: MMIO devirt 0xFEDC2000 (0xE pages, 0x8000000000000001) skip 1 18:511 00:001 OCABC: MMIO devirt 0xFEDD4000 (0x2 pages, 0x8000000000000001) skip 1 18:512 00:001 OCABC: MMIO devirt 0xFEE00000 (0x100 pages, 0x8000000000000001) skip 1 18:514 00:001 OCABC: MMIO devirt 0xFF000000 (0x1000 pages, 0x8000000000000001) skip 1 18:515 00:001 OCABC: MMIO devirt 0x10000000000 (0x10400 pages, 0x8000000000000001) skip 0 18:516 00:001 OCABC: MMIO devirt 0x3CB80000000 (0x10400 pages, 0x8000000000000001) skip 0 18:517 00:001 OCABC: MMIO devirt 0x3CBB0000000 (0x10400 pages, 0x8000000000000001) skip 0 18:519 00:001 OCABC: MMIO devirt 0x69730000000 (0x10400 pages, 0x8000000000000001) skip 0 18:520 00:001 OCABC: MMIO devirt end, saved 1064960 KB 18:521 00:001 OCABC: Only 176/256 slide values are usable! 18:522 00:001 OCABC: Valid slides - 80-255 Is it ok that last 4 still "skip 0"? If I convert and add them too than I can't boot. Computer just restarting constantly from boot chooser. Also now in my config .plist 4 lines in whitelist is not what appeared in boot txt. Should I delete them?
  5. only first line is ok now 19:342 00:023 OCABC: VMware Mac installed on A3621518 - Success 19:345 00:002 OCABC: Patching safe mode sur-2 at off 1F0B 19:347 00:002 OCABC: MMIO devirt start 19:349 00:002 OCABC: MMIO devirt 0xD2100000 (0x81 pages, 0x8000000000000001) skip 1 19:351 00:002 OCABC: MMIO devirt 0xD3180000 (0x81 pages, 0x8000000000000001) skip 0 19:354 00:002 OCABC: MMIO devirt 0xD9180000 (0x81 pages, 0x8000000000000001) skip 0 19:356 00:001 OCABC: MMIO devirt 0xD9300000 (0x100 pages, 0x8000000000000001) skip 0 19:358 00:002 OCABC: MMIO devirt 0xDA100000 (0x181 pages, 0x8000000000000001) skip 1 19:360 00:001 OCABC: MMIO devirt 0xFEA00000 (0x100 pages, 0x8000000000000001) skip 1 19:362 00:002 OCABC: MMIO devirt 0xFEC00000 (0x1 pages, 0x8000000000000001) skip 1 19:364 00:002 OCABC: MMIO devirt 0xFEC10000 (0x1 pages, 0x8000000000000001) skip 1 19:366 00:002 OCABC: MMIO devirt 0xFED00000 (0x1 pages, 0x8000000000000001) skip 1 19:368 00:002 OCABC: MMIO devirt 0xFED40000 (0x5 pages, 0x8000000000000001) skip 1 19:371 00:002 OCABC: MMIO devirt 0xFED80000 (0x10 pages, 0x8000000000000001) skip 1 19:373 00:002 OCABC: MMIO devirt 0xFEDC2000 (0xE pages, 0x8000000000000001) skip 1 19:375 00:001 OCABC: MMIO devirt 0xFEDD4000 (0x2 pages, 0x8000000000000001) skip 1 19:377 00:001 OCABC: MMIO devirt 0xFEE00000 (0x100 pages, 0x8000000000000001) skip 1 19:379 00:002 OCABC: MMIO devirt 0xFF000000 (0x1000 pages, 0x8000000000000001) skip 1 19:381 00:002 OCABC: MMIO devirt 0x10000000000 (0x10400 pages, 0x8000000000000001) skip 0 19:383 00:002 OCABC: MMIO devirt 0x3CB80000000 (0x10400 pages, 0x8000000000000001) skip 0 19:386 00:002 OCABC: MMIO devirt 0x3CBB0000000 (0x10400 pages, 0x8000000000000001) skip 0 19:389 00:002 OCABC: MMIO devirt 0x69730000000 (0x10400 pages, 0x8000000000000001) skip 0 19:391 00:002 OCABC: MMIO devirt end, saved 1067016 KB 19:393 00:002 OCABC: Only 176/256 slide values are usable! 19:395 00:002 OCABC: Valid slides - 80-255
  6. Ok, done. Attached. opencore-2023-01-20-160214.txt.zip
  7. Hi @fabiosun Seems like I have to disturb you again 🙂 Sorry but I can't figured this out by myself. After I installed new GPU as I mentioned in an other thread I disable Resizable bar in BIOS for stability but still I have random reboots once or twice a day. I don't know but may be since there is some changes my Mmio Whitelist values have to be adjusted again? Could you please take a look at my config and crash report? Archive.zip
  8. Want to share my good news with you guys. I've got RX 6950XT and successfully spoofed as 6900XT. Had to disable Resizable bar since it created instability, computer was rebooting as soon as any GPU intensive task happen. After that everything is great. Metal score is attached. 🙂 Thank you.
  9. Hello good people, I have a question. Trying to find any tiny bits of info if Apple will support RDNA3 cards in MacOS but I'm starting doubt that. Might be it will never happen since they fully moved to own silicon. I was planing to get new graphics card in a next few weeks. Was considering RX 7900 XTX or RTX 4090. So if there is no chance to get AMD card supported in MacOS then 7900 XTX not make much sense since it will be inferior then 4090 in all respects. And getting 4090 means no more hackintoshing 😞 but I really want to stay on MacOS. So I'm thinking what would be the best case for me. I might will buy 6900XT and wait if Apple will supporting RDNA3 cards in future. So the question is 🙂 Can I use RX 6950 XT in hackintosh? Can it be spoofed like 6900XT? Thank you.
  10. Guys, I can't boot into safe mode. Holding shift in OC canopy menu selecting disk, just showing apple URL and kick back to selecting menu. Is there anything have to be adjusted in config.plist? Thank you.
  11. One thing I want to mention, in Ventura everything is super smooth. Before in Monterey I had occasional stutters in Desktop animations and webpages scrolling. Especially with Twitter. Now is totally gone! Just for MacOS I removed my Titan RTX from PC and putted old Vega 64 card sitting on a shelf for past three years and never being happier. According to Ventura release notes new METAL 3 is still supported by Vega cards but polaris hit EOL. Just checked with Geekbench Metal test and got for 1000 points more then in Monterey. Actually I'm impatiently waiting for Nov 3d. I'm definitely will get new AMD card at the end of the next month. Planing for Radeon RX 7900 XT. What do you think guys, will Apple support RDNA3 cards in next Ventura updates? Otherwise I think I will go for two RX 6900 XTs.
  12. Here is my EFI folder https://mega.nz/file/4Ex31AzR#0j8vTCpKlIsr7MrbzkGX_yfcUtXS2UrejhP00qf6qf8 Fully functional Ventura except build-in lan adapters for Gigabyte TRX40 AORUS MASTER (rev. 1.0) with 3970X CPU. BIOS settings are: First load defaults. Activate XMP profile for RAM. CSM support disabled, obviously 🙂 Secure boot disabled, Fast boot disabled, Both lan adapters disabled, in Advance CPU settings SVM Mode enabled. Platform power, Wake on Lan disabled. Above 4G decoding enabled. Resizable bar - auto. AMD CPU fTPM enabled. And whatever I didn't mentioned stays default. Hope it will be useful.
  13. Yay! I'm online on Ventura! I used itlwm.kext instead of AirportItlwm with heliport app. Got quite stable connection. Didn't try Ethernet yet.
  14. Well, I never had such smooth hackintosh installation in my life 🙂 Ventura installed with zero problems except there is no any networks. WiFi kext which is working fine in Monterey in Ventura makes computer restart after 5 - 10 seconds of fully booted system. And no Intel or Aquantia ethernet adapters obviously. So AirportItlwm.kext have to be fixed or some extra quirks in OC have to be done? And I can share my EFI and BIOS settings for anyone interested.
  15. Sorry, I thought it is same as "SVM Mode" on AMD boards "Virtualization enhanced by Virtualization Technology"
  16. I will try installation tomorrow. Meanwhile try this: https://elitemacx86.com/threads/common-problems-in-macos-ventura-13-0.924/ just remembered, I found this post on that forum. I didn't read it but may be you can find some useful info there.
  17. Ok 🙂 Since I don't need Windows anymore I can use that NVMe drive to install Ventura there to try it out. I just use my working EFI or something extra should be done? New patches?
  18. Got notification this morning 🙂 Fabio, can you please tell if there is any difference in graphics performance compare to Monterey? Since Ventura is introducing Metal 3 I'm curious if it will worth to upgrade.
  19. Hey Fabio! Just want to report. I fixed this USB error. AppleUSB20HubPort@20430000: AppleUSBHostPort::disconnect: persistent enumeration failures After our attempt to fixed I kinda gave up, but one week ago I've some free time and decide to find what could be a solution for this. I was googling this error for days and was trying one thing after another. I tried different BIOS versions, different BIOS settings, I mapped USB ports, created SSDTs for my motherboards, tried SSDTs from other boards from this forum, tried different kexts, etc... 🙂 And EVERYTHING what I tried didn't fix this issue. Still booting time was 5 - 7 minutes. And DMESG was flooded with this error constantly. I had to install MS Windows to make SSDTs and map USB ports and I noticed that windows all the time gives me error that USB device not recognized even nothing is plugged in. So I start to suspect that it's maybe something related to hardware. When I was reading motherboard manual, in description of the USB ports was mentioned that some of the USB ports are integrated into CPU and some in Chipset. I took motherboard out of the case, also decide to change thermal paste AND..... when I took CPU out I noticed that oil from thermal paste gets leaked and cover contacts of the CPU on a back and oxidized it! So I cleaned them with alcohol and with pencil eraser. Some of the contacts of the CPU was very dark colored and after cleaning they become bright and shinny. So, that's what was cause of the problem! After I assembled everything back, this error disappeared. Finally! Now Monterey is booting in 15 seconds! So, problem was with old and bad thermal paste. I hope my experience will help to others who might stuck in similar situation. 🙂 Thank you for helping me anyway in a beginning and sorry I wasted your time since problem was not related to system. 🙏
  20. No worries Fabio. It is not that crucial just annoying, I can live with that. May be in Ventura it will go away 🙂 Or I can downgrade to Big Sur for the last 🙂 I mapped USB ports by the way. It didn't help though.
×
×
  • 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.