Recent content by SteveEvans

  1. SteveEvans

    System shutdown initiated by: shutdown.200

    Replacing FakeSMC with VirtualSMC results in my CMOS being corrupted every time I reboot Catalina. Having removed all those kexts I get the following shutdown "reason". Wed Nov 25 00:26:19 2020 SteveMacPro.scevans.com com.apple.xpc.launchd[1] (com.apple.xpc.launchd.domain.system) <Notice>...
  2. SteveEvans

    System shutdown initiated by: shutdown.200

    10.15.7 working fine. Running the Big Sur installer keels over as shown below. No panic. The turning point appears to be: System shutdown initiated by: shutdown.200<-macOS Update As.193<-Language Choose.180<-recoveryos_agen.177 Any ideas? disk5s3: device is write locked. disk5: device is...
  3. SteveEvans

    << Solved >> OC: Shutdown works, but restart hangs

    Fixed by enabling the FadtEnableReset quirk.
  4. SteveEvans

    << Solved >> OC: Shutdown works, but restart hangs

    I've just switched from Clover to OC in preparation for upgrading to Big Sur. Everything has gone amazingly smoothly having followed the excellent documentation covering a Westmere installation. I needed to apply the DisableRtcChecksum quirk after my CMOS was getting trashed on every boot, but...
  5. SteveEvans

    macOS 10.15.4 Supplemental Update

    When I restart to apply the supplemental update I get the expected black screen with Apple logo, but the progress bar only gets to about 5% before the computer resets. Clover then only displays the normal boot selections, not those I'd expect to see during an update. When I proceed to boot, I...
  6. SteveEvans

    macOS 10.15.4 Update

    v5109 working OK for me with USB/bluetooth but no sound yet using VoodooHDA on first boot. Fixed by a reboot. All golden! I noticed that CleanMyDrive2, Dymo etc were missing from the toolbar on the first boot too, so perhaps a number of services simply didn't start first time.
  7. SteveEvans

    Dell Precision T7500 with RX 580!!! White Screen!!! Please Help!!!

    I'm using the attached EFI booting 10.14.3. There's a DisableDrivers section in the config.plist that I'm not sure is doing anything, but apart from that I think it's quite clean. Steve
  8. SteveEvans

    macOS 10.14.3 Update

    Now works on a Xeon too, which 10.14.1 didn't.
  9. SteveEvans

    AMD9500Controller@0 failed to access hardware!

    Well, who'd have guessed... I upgraded to 10.14.3 and decided, just on the off chance, to remove the Quadro 2000 graphics cards.... and it boots! Happy days! :)
  10. SteveEvans

    AMD9500Controller@0 failed to access hardware!

    I tried an update to Mojave, but it crashed on reboot. I was able to boot to the recovery image, and move the kexts as per the previous post... all seems to be working now! :)
  11. SteveEvans

    AMD9500Controller@0 failed to access hardware!

    I moved the IONDRVSupport.kext and all the NVDA*.kext drivers out of /System/Library/Extensions and that had the desired effect, but that seems rather clumsy and might not survive an OS upgrade. Steve
  12. SteveEvans

    AMD9500Controller@0 failed to access hardware!

    A breakthrough! I figured that the issue may be that the AMD driver doesn't expect to be the sole driver and so if I had another primary display used by the BIOS, things might work better. I installed an old Nvidia Quadro 2000 card which MacOS will only use as a dumb frame buffer with no...
  13. SteveEvans

    AMD9500Controller@0 failed to access hardware!

    Thanks for the reply @Gigamaxx I've tried tried your suggestion, with the Sensor kexts removed and the additional boot arg. Booting the 14.2.2 bootloader from USB, which is probably more reproducible than my High Sierra installation, I got the attached failure. I know that people have got the...
  14. SteveEvans

    AMD9500Controller@0 failed to access hardware!

    I never managed to get any further with the RX560, so I just bought a Sapphire Pulse RX580 8GB thinking "Well, this is known to work, surely". Oh dear... attempting to boot Mojave or the 10.13.6 2019-001 security update fails in the same way as before... --> GPU register c0500198 read failed...
Back
Top