Waiting for DSMOS

Question

Level 4

1,985 points

Waiting for DSMOS

I am posting a follow up in this section because all I have to go on at this time are Command Lines. I have a MacBook 2.4 that will not boot up fully in Snow Leopard. Here is the end of the Verbose boot sequence using the same hard drive for both computers. First the MacBook 2.4 that does not reach the blue screen.

Waiting for DSMOS…

systemShutdown false

Previous Shutdown cause:0

BTCOEXIT off

wL0: Broadcom BCM4328802.11 Wireless Controller

5.10.131.42

DSMOS has arrived

IntelMemory::intit

InititPool: offset=0x08000000 size = 0x08000000

I think the last linemay read AirPort: RSN handshake complete on en1, but anyway the computerfreezes here.

Now here is the samesequence from a working MacBook 2.0 that boot up fully…

Waiting for DSMOS…

systemShutdown false

Previous Shutdown cause:0

Atheros: mac 12.2 phy8.1 radio 12.0

DSMOS has arrived

AirPort_ArthrFusion21:Ethernet address 00.19:e3:01:31:ac

I080211Controller::dataLinkLayerAttachComplete():adding AppleEFINVRAM notification

AirPort:Link Down onen1. Reason 1 (Unspecified).

En1: 882.11d countrycode set to ‘US’.

En1: Supported channels1 2 3 4 5 6 7 8 9 18 11 36 44 48 52 56 68 64 149 153 161 165

AirPort: Link Up on en1

AirPort: RSN handshadecomplete on en1

My question is this; after DSMOS arrives is it finding the wrong files (IntelMemory::intit), are there missing files, or is this normal and the problem is elsewhere? Any help what so ever is welcomedand you see my first post here…

https://discussions.apple.com/thread/3322897?answerId=16151045022#16151045022

MacBook, Mac OS X (10.6.8)

Posted on Sep 13, 2011 12:02 PM

Reply

Answer 1

Linc Davis

Level 10

209,739 points

Sep 13, 2011 2:24 PM in response to Joe Gordon

I'd attach no significance at all to the output of "TechTool." I know Apple distributes it to AppleCare customers, or used to do so, but that was just to give them something tangible to hold onto, not because it's good for anything.

If you carry out all the following steps and still can't boot, then you have a hardware failure:

Reset the SMC and NVRAM.
Disconnect all wired peripherals.
Boot from the installation disc
Partition the internal drive with the default options.
Run the Installer.
Reboot without importing anything.
Connect to Ethernet.
Run Software Update.
Boot again.

Reply

Answer 2

Joe Gordon Author

Level 4

1,985 points

Sep 13, 2011 1:37 PM in response to Linc Davis

Linc the Mac would fully Safe Boot when I first got it. I reinstalled Snow Leopard thinking that it was a systems problem, however, after the reinstall the problem remained. Now, after doing a Safe Boot and checking all of the loaded features I ran TechTool Deluxe and all of the point passed (ram, hard drive, vram, volume, etc., then I was prompted for a Software Update, apparently this was the wrong move. Because after the up dates it will not boot up fully at all. Everything is normal in both sight and sound until the "DSMOS has arrived". Also as stated in the first post if you are resetting the SMU with the battery out and the AC power connected the machine does not give the usual beep.

Reply

Answer 3

g_wolfman

Level 4

3,472 points

Sep 13, 2011 1:41 PM in response to Joe Gordon

Alternatively, if you can boot from the installation disk, then it may mean that the dsmos.kext has somehow become corrupted. In which case you should ensure your backups were up to date (for safety's sake) and reinstall the OS (but you shouldn't need to erase and install...just reinstall over the existing OS).

dsmos.kext (Don't Steal Mac OS X) is responsible for decrypting some important system resources to ensure the OS only runs on Apple hardware...if it's corrupted and not working, then boot failure is pretty much a given.

Reply

Answer 4

Joe Gordon Author

Level 4

1,985 points

Sep 13, 2011 2:14 PM in response to g_wolfman

g_wolfman, I am being to think that you both may be correct. What ever is suppose to be there to say that this is Mac hardware may not be there or it my not be functioning. Because the MacBook will not boot from the DVD after the updates, so unless installing updates in the Safe Boot Mode is a no-no, that is my take.

I did notice that when I reinstall Snow Leopard to this MacBook that the file System/Library/Caches/com.apple.bootstamps/57F99138-70CA-2FBF-AC48-FFBA105CC539 /usr/standalone/i386/Firmware.scap

did not get installed as it did on my other MacBook. So, does it sill sound like hardware or could it be firmware?

Reply