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
    Sorry, my mistake, I just looked at the patch number. 😇
  2. Ploddles
    I have not had your patch 11 enabled in my config.plist for many many months now. Have you tried without it?
  3. Ploddles
    Monterey Beta 2 has just landed, lets hope that the patches come out soon.
  4. Ploddles
    Yes, that is what I was doing, getting things ready for Monterey, and I had set the Min & Max Kernel section for all 3 kexts, ie it wasn’t set to load the BluetoolFixup.kext with Big Sur. However the new IntelBluetoothFirmware.kext was halting the boot with a critical error. Replacing that kext with the old (v 1.1.2) one and I was back to normal. I’ll retry on the next update of these kexts.
  5. Ploddles
    @fabiosun disabling patch 12 boots to a black screen, nothing displayed on the monitor.
  6. Ploddles
    Sorry, I did not explain fully. Disabling the patch only stops Big Sur loading but the latest Bluetooth kexts stop Big Sur and Catalina loading. I now have an updated bluetoolfix kexts to try with the new Monterey enabling kexts. I will try disabling the other patch later as I am now away from home. I will be back in a few hours time.
  7. Ploddles
    BS 11.4, BS 11.5 Beta and Catalina
  8. Ploddles
    Unfortunately my system immediately hangs at the Apple logo when I disable the patch. Anyone using the internal Bluetooth module, on a Gigabyte motherboard, please be aware that the new kexts that are meant to add Monterey compatibility do not work, on my motherboard at least, and cause the system to hang and not boot into macOS. On the plus side I have now fixed the shutdown issue where the system would reboot about 5 seconds after shutdown - it now finally shuts down and stays shut down.😀
  9. Ploddles
    @fabiosun I can't remember exactly where it came from but I think it was needed mid way through the Catalina updates, probably about 10.15.3 or 10.15.4. I have enough trouble remembering my own name never mind something like this 🤪 My latest EFI (OC 0.7.0) for the Gigabyte Xtreme can be downloaded from HERE for you to update the OP.
  10. Ploddles
    I get the same error using Fusion. It looks like VirtualBox is the only one that works on AMD cpus.
  11. Ploddles
    I only used the single core as an initial install to see if it would work. It is good that we now have another option to run a Windows program without rebooting. I understand that Fusion Player 12 is free for home use so I will give that a try as well when I get the chance. I didn't realise at first that you can't pass through a graphics card, such as the RX6900XT, using VirtualBox as that option was removed a while back. I presume we still can with Fusion, and Parallels. Let's hope they work as well. The last time I used Fusion was about 6 years ago, and I have never used Parallels, so things will have changed a bit since then.
  12. Ploddles
    I've always read on here that you cannot run a Windows Virtual Machine on macOS on our Bare Metal Threadrippers. As I was on day release from hospital today, I updated my machine to the latest OC release (0.7.0) and the latest BS Beta (11.5 beta 3). Whilst in hospital I had fixed a friends laptop that was continually crashing be wiping it and loading the latest Windows, Win10_21H1. As I had the ISO on a USB drive I decided to try a VM on the Threadripper, thinking it wouldn't work. My copy of VM Fusion was very old, V6, so I downloaded the latest VirtualBox to play with. I know it isn't the best VM software but it is free. It was with great surprise then that a Windows VM was up and running in a matter of minutes. No having to try and patch anything or anything else. I have always had SVM enabled in my BIOS setup so I didn't even have to change anything in there either. So it works. I haven't tried passing through the RX 6900 XT or RX 6800 XT through to it yet, I was just astonished that it worked straight away.
  13. Ploddles
  14. Ploddles
    So who is going to be the first to try it? I'd love to but can't ATM. As soon as I get home I'll give it a play.
  15. Ploddles
    BS 11.5 beta 1 has been released.
  16. Ploddles
    At 11.3 stage the RC came out and then further betas were released before the final release. Let's hope this doesn't continue like that one did.
  17. Ploddles
    That could be your problem, without the plist macOS can't connect to your network cards. If it doesn't exist when the system starts up then it scans your interfaces and creates the file. From then on it just reads the plist without having to fully scan and configure your system again.
  18. Ploddles
    @Arrakis This is a long shot but have you tried deleting your NetworkInterfaces.plist file and then rebooting. cd /Library/Preferences/SystemConfiguration sudo rm NetworkInterfaces.plist
  19. Ploddles
    @valmeida HERE is a debug EFI. It is a few months old but that doesn't matter. Nor does it matter if your system boots or fails along the way. Copy it onto a USB stick and boot with it. If the system doesn't go into macOS after a minute or so reboot with your normal EFI to get into your system. In the root of the USB stick there will be a text file, with todays date in it, and the MMIO values will be somewhere in that text file. You then need to convert the hex values to base10 for your whitelist.
  20. Ploddles
    I've just had a look at your update and am now a bit confused, easily done though 😀 Whenever I have extracted the values via the debug version of OC, every single entry has skip 0, not a single skip 1. I must be doing something wrong as this would suggest that I don't need any values in the mmiowhitelist section. In the config file I had no entries in the whitelist whilst I extracting them to the text file. The debug version I use is a good few months old so I will download the latest and test again. There was also no difference between having Above 4G enabled/disabled.
  21. Ploddles
    You can add -wegoff to the boot arguments to test it or disable/remove whatevergreen.kext in the config.plist
  22. Ploddles
    If you are booting multiple OS then it is often necessary to remove power to the machine (for about 10 seconds), ie turn off or remove the power cable not just shutdown from the OS. Each OS will upload its own firmware to the BT & Wifi chips that is only cleared by completely removing power. Just shutting down still leaves power to the MB so power must be completely removed.
  23. Ploddles
    @iGPU are there any particular benefits to running as MacPro7,1 rather than iMacPro1,1? Do we gain or lose anything by using one over the other? I use iMacPro1,1 atm but only because that is what was recommended when we started on this journey.
  24. Ploddles
    I haven't used it a great deal but it seems very stable atm, in other words it hasn't crashed on me. I updated the BIOS to F4Q and some of the MMIO values changed and these have been incorporated into the EFI. If you therefore use it as is you will need to update to F4Q, or copy the MMIO section from the previous 0.6.7 EFI to stick with F4P. I also haven't got round to changing it to the nice icons yet so it is using the text mode picker. As OC 0.6.9 will be release next week I was leaving it until then to change the picker mode to the icons whilst I am making the other changes that will be necessary. As for the install, you can either register your machine in the beta program and update that way, or my preferred way, you can download the full installer and run that. With the full installer you could either upgrade your current install (just select your 11.3 drive when it asks where you want to install it) or do a full new install to another drive or container.
  25. Ploddles
    @iGPU I seem to remember a few days ago, on another forum, that a number of people started having a similar issue when they updated from 11.2.3 to the official 11.3. They all had Intel CPUs though and not AMD. The issue was to do with USB port mapping and some having more than 15 ports mapped. I think the issue was solved for them by redoing their USBPorts.kext and/or disabling XhciPortLimit in the kernel section of their config.plist.
×
×
  • 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.