Waiting For Dsmos Mac

Posted on by

Are you facing the error of waiting for DSMOS or DSMOS has arrived on your Hackintosh PC that leads to not run macOS X? Then your plane is landed at the right place.

Hi, I have a problem with booting to the installer of the latest version of OS X El Capitan. After booting into OS X from the Unibeast USB stick I get a blackscreen after 'Waiting for DSMOS'. I tried using 'nvdisable=1' and '-x -f -v' but get stuck with a black screen after 'Waiting for DSMOS'. That fixed my issue on a skylake system. If it hard reboots on DSMOS has arrived, it's FakeSMC. Nvdisable will fix your screen going black, not a hard reboot. Just had the same issue yesterday. 1 point 3 years ago. When I use nvdisable, it still holds on waiting for DSMOS. It doesn't look possible for me to get into the OS to.

What is DSMOS

As we have read the article that defined what is DSMOS or DSMOS X clearly and in simple word.

DSMOS is abbreviation for Don’t Steal Mac OS X.kext, sometimes error occurs as “Waiting for DSMOS” or “DSMOS has arrived” is a file present in Intel-capable versions of the Mac OS X operating system which allow installation on one piece of Apple hardware only

How to fix “Waiting for DSMOS” or “DSMOS has arrived”

Mostly Hackintosh users have to go with this error “Waiting for DSMOS” or “DSMOS has arrived”. This are the common issues for every Hackintosh System. The issue is caused most of the time by FakeSMC.kext and it’s a Graphics issue too. On this guide, we will show you how to solve this error with just a few steps.

2 Methods for Fixing DSMOS Error

There are 2 solutions for you that will fix your DSMOS Hackintosh error. Let’s begin the process.

Waiting for dsmos hangs

Fixing DSMOS with FakeSMC (Method 1)

Download the latest FakeSMC.kext and replace with the old one. Just boot from mac drive or from USB installer and Boot with Following flag “GraphicsEnaber=No”.

Alternative

If that doesn’t fix your problem, boot your mac into Single User Mode with the following boot flag “-s” and type:

/sbin/mount -uw
mkdir ~/backup
cd /System/Library/Extensions Double commander for mac os x.

If you have NVIDIA graphics then type:

mv -R NVD*.kext ~/backup

If you have AMD/ATI Graphics then type:

mv -R ATI*.kext ~/backup

If you have IntelGraphics then type:

Mac

mv -R AppleIntelGMA* ~/backup
mv -R AppleIntelHD* ~/backup
mv -R AppleIntelSNB* ~/backup
mv -R AppleIntelIntegratedFramebuffer.kext ~/backup

Fixing DSMOS error (Method 2)

Boot your mac into Single User Mode along with Verbose mode with just typing this flags “-v -s” and type:

fsck -fy
mount -uw /
mkdir /backup
cd /System/Library/Extensions
mv AppleIntelHD* AppleIntelSNB* AMDRadeon* ATI* GeForce* NVDA* /backup
rm ./Caches/com.apple.kext.caches/Startup/kernelcache
reboot Wireless game controller for mac.

Note: If your system have AppleIntelCPUPowerManagement then save it in backup.

So how was this guide? was it helpful and did your error fix? let me know in comment section.

  • Supported version: 0.6.2

So with troubleshooting a hackintosh, it can be a bit difficult to really understand where you're getting stuck as the exact keyword you're trying to search for may not match anything on google. While this page won't solve all your issues, it should at least help better understand where in the macOS boot-process you're getting stuck and hopefully give some ideas as to why you're stuck.

# OpenCore Booting

This section will be brief, as OpenCore boot issues are fairly rare and usually simple user error:

Recovery android for mac. To perform Android data recovery for Mac, you will need to: Stop using the device. Connect it to your Mac via USB and allow Disk Drill to perform operations. Confirm your rights to the device so that the utility can perform all operations as quickly and as accurate as possible.Programs can be.

  • System powers on and searches for boot devices
  • System locates BOOTx64.efi on your OpenCore USB under EFI/BOOT/
  • BOOTx64.efi is loaded which then chain-loads OpenCore.efi from EFI/OC/
  • NVRAM Properties are applied
  • EFI drivers are loaded from EFI/OC/Drivers
  • Graphics Output Protocol(GOP) is installed
  • ACPI Tables are loaded from EFI/OC/ACPI
  • SMBIOS Data is applied
  • OpenCore loads and shows you all possible boot options
  • You now boot your macOS installer

If you're having issues booting at this point, main things to check for:

Waiting For Desmos Machine

For the rest of the possible issues, see here:

# boot.efi Handoff

This is where macOS's bootloader(boot.efi) comes onto the scene, specifically what it does is prep the environment for the kernel to load and where OpenCore injects kexts. If you're getting stuck at this point, there's likely an issue with loading the kernel, main culprits:

For the rest of the possible issues, see here:

Note: In macOS 10.15.4, Apple changed the boot.efi debugging protocol, so things will look quite a bit different from before but all the same rules still apply

# XNU/Kernel Handoff

Now that boot.efi has setup everything for us, we now get to watch the kernel do it's thing. This section is commonly referred as the Rooting phase:

This section is where SMBIOS data is verified, ACPI tables/Kexts are loaded and macOS tries to get everything in order. Failures here are generally a result of:

  • Corrupted SSDTs
  • Corrupted kexts(or incorrectly setup under your config.plist -> Kernel -> Add)
  • Messed up memory map

See here for more troubleshooting info:

Now here we have [ PCI configurations begin ], this section can be seen as a hardware test for our systems, kexts and SSDTs we injected, and where IOKit starts hardware probs to find devices to attach to.

The main things that are tested here:

  • Embedded Controllers
  • Storage(NVMe, SATA, etc)
  • PCI/e
  • NVRAM
  • RTC
  • PS2 and I2C

For more specific info on how to get around this area, see here:

This is where the 15 port limit and USB mapping comes into play, and where the infamous 'Waiting for Root Device' errors pops in, main things to check for:

This is where our FakeSMC/VirtualSMC come into the scene and do their magic, DSMOS itself is a kext that verifies if your system has an SMC and will request a key. If this key is missing, then DSMOS will not decrypt the rest of the binaries and you'll get stuck here. You may also get stuck at AppleACPICPU which is just the same error.

Source: Dont Steal Mac OS X.kext

This is where Apple's audio driver comes in, and where AppleALC shines. Generally rare to see issues here but if you do, try disabling AppleALC and any other audio related kexts.

And here we get to the GPU driver initialization, and where WhateverGreen also does its magic. Generally errors here are due to the GPU and not WhateverGreen itself, main culprits:

# macOS Handoff

Waiting For Dsmos Hangs

And you've finally got past all that verbose! If you're getting stuck at the Apple logo after all that verbose, then there's a couple things to check for: