Jump to content

Ploddles

Members
 View Profile  See their activity

  • Posts

    405

  • Joined

  • Last visited

  • Days Won

    5

 Content Type 

Everything posted by Ploddles

  1. Ploddles
    That was quick, thanks very much.
  2. Ploddles
    Hi @fabiosun, I've just updated to the latest BIOS 3205 hoping it may fix a few issues I am having with Tahoe. Sequoia seems to work fine at the moment but even after the latest update Tahoe is wonky. In Tahoe, I have no network card showing at all and my NVMEe drives are very weird. 1 of them will not show at all in System Information and another appears most of the time but sometimes won't show up. The 3rd shows all the time. Even though I can see 2 in System Information I cannot see any of the volumes, 1 of them is Sequoia the other Windows. Nor can I mount either of the EFI partitions on those drives. The one that show all the time is the Windows one. It will also only allow me to install Tahoe on an old spinning hard disk, not an NVMe or SSD. I have ordered a new, different make, NVMe drive to try that. I have had a look at the AMD discord run by CorpGhost but couldn't see the best place to ask for help with the ACPI patches. I have attached below the DSDT I have extracted with the debug version of Opencore. When you get a chance, could you please pass it on to CorpGhost to do his magic stuff and point me to it on Discord. Thank you for all your help, now and in the past. Regards, DSDT.aml.zip
  3. Ploddles
    @Xsario I updated to that BIOS and everything is still working fine as far as I can tell. It does take a little while as it also updates other firmware as well, eg the thunderbolt chip. I still haven't managed to get to install the Tahoe beta yet but I'm getting closer - probably something silly I have in my config.
  4. Ploddles
    Hi @Xsario, I haven't tried it yet. I think @fabiosunhas updated his motherboard to the latest Hero so isn't in a position now to try it. If you try it first can you update here if all is well. Have you tried Tahoe yet? I can't get mine to boot to the installer even with the latest kexts, OC and patches. I get the prohibit sign and screen corruption during part of the installation and it either freezes or reboots in a loop.
  5. Ploddles
    Has anybody got this working with the new Tahoe? I updated to the latest Opencore 1.0.5, and the latest kexts, but still cannot get past the usual [EB|LOG:EXITBS:START] followed by the Data & Time. Maxkernel set to 24.99.99 for all kexts
  6. Ploddles
    Beta 5 update runs fine.
  7. Ploddles
    That updated kext solves the issue, thank you. Are there any advantages using that rather than AppleIntelI210Ethernet.kext?
  8. Ploddles
    Thank you my genius friend. I now have it working as it should. The kext you use for the ethernet card (AppleIGC.kext) does not work for me. If I enable that kext and disable AppleIntelI210Ethernet.kext my system just hangs at a black screen. If I disable both of those kexts the same thing happens, I just get a black screen. Enabling AppleIntelI210Ethernet.kext (with the e1000=0 boot arg) and it works again, but ethernet speed is only 10% of what it should be - but that is better than nothing. The AppleIGC.kext I have is V1.5 dated 14 June 2024. I will experiment with a few things over the weekend.
  9. Ploddles
    Here is the config.plist. As far as I am aware I have all the patches. config.plist.zip
  10. Ploddles
    No change for me in Beta 4. It is still totally unusable because of the graphics glitches, e.g totally red screen in web browser windows, the same for mail messages and often the whole screen becomes unreadable or lags when you click anything..
  11. Ploddles
    Yes it is Corsair but it doesn't happen in Windows and didn't happen before updating to OC 1.0.0 and the new patches & Sequoia. I do have another power supply I could try but that won't be for a few days as I am busy.
  12. Ploddles
    Just adding the extra patches resulted in a very unstable/unusable system. So I deleted all existing patches and installed the ones from above along with the latest versions of the kexts. (I removed patches that were only for earlier versions of macOS - those before Sonoma) The system is generally OK in both Sonoma & Sequoia BUT it randomly just turns off - I hear a click and the whole system is off. This results in the power buttons on the case not working. The only way to get the system up again is to remove the power cable from the power supply and leave it for 10 seconds or so and then it will turn on again when I reconnect the power cable. Very, very strange. This happens in both Sonoma & Sequoia but a lot more often in Sequoia.
  13. Ploddles
    Mine is now installed. The main problem was I had accidentally not increased one of the max settings in the patch list. However it is very unstable even after updating Lilu. I couldn’t find updated versions of WEG or Virtualsmc.
  14. Ploddles
    Still no joy for me on my 7950X. Where do we get the updated versions of those kexts? I only have the latest release version from the acidanthera GitHub page, e.g the Lilu one is version 1.6.7 dated Aug 7, 2023.
  15. Ploddles
    Thanks, I must have missed that somewhere along the line. I'll give it a go at the weekend.
  16. Ploddles
    No joy for me at the moment, I'll have to go on the hunt for the latest kexts as I thought I had the latest release versions of them all, but obviously not. Using the latest release of Opencore 1.0.0 😞
  17. Ploddles
    Try locking your memory speed at 5200 if you haven't done that already. Mine randomly reboots if it is set any higher.
  18. Ploddles
    If you are using the Intel wifi kext make sure you use the "AirportItlwm-Sonoma14.4-v2.3.0-DEBUG-alpha-e886ebb" one (or newer) - it has to be the one comparable with Sonoma 14.4. Before you run the update disable your wifi and Bluetooth kexts and then re-enable after the update.
  19. Ploddles
    Try clearing NVRAM again. Double check that ALL the BT & WiFi kexts are disabled.
  20. Ploddles
    Go back to your original config and disable the Bluetooth and Wireless kexts. The update should then run fine. After it has finished you can re-enable the Bluetooth and Wireless kexts. If you are using the Intel wifi kext make sure you use the "AirportItlwm-Sonoma14.4-v2.3.0-DEBUG-alpha-ef2e076" or newer version - it has to be the one comparable with Sonoma 14.4.
  21. Ploddles
    Please find them attached. The first 2 are with no values set in MmioWhitelist and the system just continually reboots before the logon screen appears. These are 2 consecutive boots. The last one is with your MmioWhitelist value MMIO devirt 0xFD000000 (0x1E00 pages, 0x800000000000100D) enabled. This boots and is stable. I don't know what to make of it. Archive.zip
  22. Ploddles
    Yes, thank you very much. It works like a dream. I ran the debug version of OC to get the report and added the MMIO values listed. It then became unstable and randomly wouldn't boot. If I disabled them all it wouldn't boot. If I enable the only one you have enabled in your config it all works again. The one you have (MMIO devirt 0xFD000000) does not appear in my debug report at all. Very strange but working now with your MMIO value enabled.
  23. Ploddles
    Thank you @fabiosun
  24. Ploddles
    Thanks @Lorys89 I saw that one thanks but as it hasn't been updated in nearly 3 months, and uses 0.9.6, I assumed there would be a newer version, especially as the BIOS has been updated since then as well. I skim read the thread and saw mention that changes need to be made for the latest BIOS. When the machine is built, replacement parts should arrive tomorrow, I'll read through the thread properly.
  25. Ploddles
    Hi @fabiosun, My Threadripper machine has died and I have decided to go with the 7950X for my next build. Can you share your latest EFI for your machine to save me starting from scratch on getting it working? I have ordered the same MB that you have as well. I will update to the latest BIOS (1904). Thanks.
×
×
  • 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.