Waiting for DSMOS...

KariNeko · August 23, 2009

Aug 22 18:19:18 localhost kernel[0]: Got boot device = IOService:/AppleACPIPlatformExpert/PCI0@0/AppleACPIPCI/SATA@1F,2/AppleIntelPIIXATARoot/CHN0@0/AppleIntelICHxSATA/ATADeviceNub@1/AppleATADiskDriver/IOATABlockStorageDevice/IOBlockStorageDriver/ST31500341AS ST31500341AS/IOGUIDPartitionScheme/Untitled@2
Aug 22 18:19:18 localhost kernel[0]: BSD root: disk2s2, major 14, minor 8

Aug 22 18:19:18 localhost kernel[0]: Kernel is LP64

Aug 22 18:19:18 localhost kernel[0]: USBMSC Identifier (non-unique): 000223223223 0x424 0x223a 0x360

Aug 22 18:19:18 localhost kernel[0]: kxld[com.apple.kernel.iokit]: The Mach-O file is malformed: Invalid magic number: 0xfeedface.

Aug 22 18:19:18 localhost kernel[0]: Can't load kext com.apple.kernel.iokit - link failed.

Aug 22 18:19:18 localhost kernel[0]: Failed to load executable for kext com.apple.kernel.iokit.

Aug 22 18:19:18 localhost kernel[0]: Kext com.apple.kernel.iokit failed to load (0xdc008016).

Aug 22 18:19:18 localhost kernel[0]: Failed to load kext com.apple.kernel.iokit (error 0xdc008016).

Aug 22 18:19:18 localhost kernel[0]: AppleIntelCPUPowerManagement: Turbo Ratios 1112

Aug 22 18:19:18 localhost kernel[0]: AppleIntelCPUPowerManagement: initialization complete

Aug 22 18:19:18 localhost kernel[0]: [bluetooth::CSRHIDTransition] switchToHCIMode (legacy)

Aug 22 18:19:18 localhost kernel[0]: [bluetooth::CSRHIDTransition] transition complete.

Aug 22 18:19:24 localhost kernel[0]: systemShutdown false

Aug 22 18:19:26 localhost kernel[0]: Waiting for DSMOS...

I'm stuck at this point.

My steps where:

1 Installed Snow Leopard to another drive from within Leopard.

2 Installed Chameleon-2.0-r431 to that drive.

3 Replaced boot file at that volume with PCEfi 10.2 ones.

4 Placed DSDT.aml at / of that partition. Also tried on /Extra.

5 Placed fakesmc.kext first at /S/L/E. Then at /E. Tried both versions of fakesmc.kext, and also dsmos Snow build.

6 chmod 775, chown 0:0 those files.

System doesn't go any further than "Waiting for DSMOS...".

Does it happened to anyone else? Any advice?

Thanks in advance!

demonfox13x · August 23, 2009

try adding your video driver. had the same probelm before

KariNeko · August 23, 2009

Thanks for you advice demonfox13x, but I already did it and nothing changes.

First I wanted to boot as safe as posible so I didn't add it.

Later I added my EFI string but it's still the same.

The contents of my boot.plist are

<key>Kernel</key>
<string>mach_kernel</string>
<key>Kernel Flags</key>
<string>-v</string>
<key>Timeout</key>
<string>5</string>
<key>boot-uuid</key>
<string>19BC4CD7-0EEB-302D-AB94-2876891D50DB</string>
<key>device-properties</key>
<string>6c0200000100000001000000600200000d00000002010c00d041030a00000000010106000003
0101060000007fff04000e0000004e00560050004d00000020000000010000000000000000000000
0
0000000000000000000000000000000220000005600520041004d002c0074006f00740061006c007
3
0069007a006500000008000000000000101c0000006400650076006900630065005f007400790070
0
0650000000f0000004e5644412c506172656e740e0000006e0061006d00650000000b00000064697
3
706c617922000000400030002c006400650076006900630065005f00740079007000650000000b00
0
000646973706c617922000000400031002c006400650076006900630065005f00740079007000650
0
00000b000000646973706c6179100000006d006f00640065006c0000001a0000006e566964696120
4
765466f726365203733303020475420000000400031002c0063006f006d007000610074006900620
0
6c00650000000e0000004e5644412c4e564d616314000000400030002c006e0061006d0065000000
1
20000004e5644412c446973706c61792d4114000000400031002c006e0061006d006500000012000
0
004e5644412c446973706c61792d4220000000400030002c0063006f006d00700061007400690062
0
06c00650000000e0000004e5644412c4e564d6163100000004e00560043004100500000001800000
0
04000000000003000c00000000000007000000001e00000072006f006d002d007200650076006900
7
30069006f006e0000002e0000006e5669646961204765466f7263652037333030204754204f70656
e
474c20456e67696e65205b4546495d</string>

Graphic cards string looks like this in readable form

<plist version="1.0">
<dict>
<key>PciRoot(0x0)/Pci(0x3,0x0)/Pci(0x0,0x0)</key>
			<dict>
			<key>@0,compatible</key>
			<string>NVDA,NVMac</string>
			<key>@0,device_type</key>
			<string>display</string>
			<key>@0,name</key>
			<string>NVDA,Display-A</string>
			<key>@1,compatible</key>
			<string>NVDA,NVMac</string>
			<key>@1,device_type</key>
			<string>display</string>
			<key>@1,name</key>
			<string>NVDA,Display-B</string>
			<key>NVCAP</key>
			<data>
			BAAAAAAAAwAMAAAAAAAABwAAAAA=
			</data>
			<key>NVPM</key>
			<data>
			AQAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAA==
			</data>
			<key>VRAM,totalsize</key>
			<string>0x10000000</string>
			<key>device_type</key>
			<string>NVDA,Parent</string>
			<key>model</key>
			<string>nVidia GeForce 7300 GT</string>
			<key>name</key>
			<string>display</string>
			<key>rom-revision</key>
			<string>nVidia GeForce 7300 GT OpenGL Engine [EFI]</string>
			</dict>
</dict>
</plist>

This "Waiting for DSMOS..." thing is happening when I try to boot in safe mode, else I get a kernel panic

riws · August 23, 2009

Created mkext? Dont use -f or -x, its possible it f* up Extensions Cache.

Don Quijote · August 23, 2009

delete dsmos.kext. it's conflicting with fakesmc.kext. then in terminal run

sudo kextcache -v 1 -t -l -m /System/Library/Caches/com.apple.kext.caches/Startup/Extensions.mkext /System/Library/Extensions /System/Library/Extensions

reboot and post results

KariNeko · August 23, 2009

delete dsmos.kext. it's conflicting with fakesmc.kext. then in terminal run
sudo kextcache -v 1 -t -l -m /System/Library/Caches/com.apple.kext.caches/Startup/Extensions.mkext /System/Library/Extensions /System/Library/Extensions 
reboot and post results

Hi Don Quijote, sorry if I wasn't clear, I didn't mix dsmos and fakesmc kexts, I was trying to say that neither worked

Also when I boot with single user mode and 32 bits and try to create the mkext cache

 sudo kextcache -v 1 -t -l -m /System/Library/Caches/com.apple.kext.caches/Startup/Extensions.mkext /System/Library/Extensions /Extra/Extensions

I got the following error:

No kexts found for architecture x86_64; skipping architecture
No mkext archives created

So I ran the same command adding the parameter "arch i386" and the mkext was created successfully, but when I type exit, I'm back at "Waiting for DSMOS..."

Don Quijote · August 23, 2009

Sorry, I thought you forgot to delete dsmos.

I was getting that message to before using fakesmc, but only at first boot after deleting caches. To fix it I was booting with -v flag (using chameleon 1 + snow boot file), waited a little longer until I saw the message DSMOS has arrived, and then replaced boot file with PC EFI 10.2 and rebooted again without any flag and all was ok. Oh, and this in 32 bit (my ASUS 1000H - see my sig - doesn't support 64 bit). With fakesmc didn't had any problems until now.

And onether thing, I always put all my extensions in /S/L/E, I never used /E/E on SL (actually tried to use it, but I got random KP wich stopped after moving all in /S/L/E). Try with the kexts in /S/L/E (at least dsmos a=or fakesmc), maybe will help.

KariNeko · August 23, 2009

Sorry, I thought you forgot to delete dsmos.
I was getting that message to before using fakesmc, but only at first boot after deleting caches. To fix it I was booting with -v flag (using chameleon 1 + snow boot file), waited a little longer until I saw the message DSMOS has arrived, and then replaced boot file with PC EFI 10.2 and rebooted again without any flag and all was ok. Oh, and this in 32 bit (my ASUS 1000H - see my sig - doesn't support 64 bit). With fakesmc didn't had any problems until now.

And onether thing, I always put all my extensions in /S/L/E, I never used /E/E on SL (actually tried to use it, but I got random KP wich stopped after moving all in /S/L/E). Try with the kexts in /S/L/E (at least dsmos a=or fakesmc), maybe will help.

Don Quijote thanks for the answer. I already tried fakesmc at /S/L/E as I didn't have any /Extra/Extensions.mkext so I wanted to be sure that it was going to be loaded. Later I decided to move it to /E/E to see also if it is going to load without the /Extra/Extensions.mkext and it did, so I leaved it there.

I suppose that I have to wait more time to see if DSMOS arrives, but I doesn't look it will.

Crawley · August 23, 2009

which version of fakesmc did you use? netkas released new version. old version worked with 64bit dsmos only (at least for my setup), when I updated to new fakesmc it boots without dsmos. i can still see waiting for dsmos... but it disappears almost immediatly

KariNeko · August 23, 2009

which version of fakesmc did you use? netkas released new version. old version worked with 64bit dsmos only (at least for my setup), when I updated to new fakesmc it boots without dsmos. i can still see waiting for dsmos... but it disappears almost immediatly

I'm using the one from 22 August, it's the last one.

Don Quijote · August 23, 2009

One more thing. I saw something about bluetooth in your log. For me my bluetooth stick didn't worked under SL, and with it stucked the boot took over 2 minutes sometimes (was working fine under Leopard, but I didn't bother with it on my desktop as I never used it since I have my lappy). After I removed it my system is booting under 30 sec. Try removing or disable the bluetooth, maybe it makes any difference.

And you didn't said what bootloader you are using

Crawley · August 23, 2009

sorry to ask this, but could it be that you downloaded leopard version by mistake?

KariNeko · August 23, 2009

Hello to everyone!

Don Quijote I was using at first Chameleon-2.0-r431 with PCEfi 10.2 as I said on my first post. :rolleyes:

Later I updated then (well downgraded) to 10.1 and it was better as I didn't get any more Kernel Panics at 32 bit, I was "only" getting "Waiting for DSMOS..." thing.

luk1985 told me on the other thread to run Kext Utility, so I did it to the Snow Leopard from within Leopard, it took a lot of time, don't know why.

Then I booted with -x32 -v and a little after the Desktop came up.

A few minutes later I ran Kext Utility from Snow Leopard 32bit and then I could boot in -x64 mode without any KP or "Waiting for DSMOS..."

So I really don't know what did the trick, if it was running Kext Utility at first or it simply was using -x32 with EFI 10.1 and not 10.2.

Now I can run Snow Leopard in -x32 and in -x64 modes, I need to test it more time to see if it's stable.

Files I'm using are

/DSDT.aml

/Extra/com.apple.Boot.plist

/Extra/smbios.plist

/Extra/Extensions/AppleIntelPIIXATA.kext

/Extra/Extensions/PlatformUUID.kext

/Extra/Extensions/fakesmc.kext

I'll try to install Snow Leopard again because I'm getting many weird stuff like:

a ) Terminal not working, it load but I don't get the command prompt as it complains about audit something and the it stays there with text displaying [Process Completed]

b ) Disk Utility doesn't work repairing permissions, complains about Installer package not found.

c ) Weird permissions at many directories: Kext Utility couldn't change permissions at files/directories, also I couldn't make changes to many kext files using Path Finder and using administrative rights.

Thanks to all of you for your help!

PD: Don Quijote the bluetooth dongle seems to work fine at both modes

Don Quijote · August 24, 2009

Your error with disk utility and permissions is already a classic one for SL already (when installed from working Leopard).

Try reinstalling from within Snow BaseSystem.pkg (you will find it in the directory System/Installation/Packages/ on the SL disk, you need to mount it and make hidden files visible to access it). Then you will be able to use disk utility to fix permissions and I think that many of your error will dissapear then.

If you still want to reinstall SL on a new partition or disk, do it from your already functioning SL install, so you won't get this error again.

Good luck.

Crawley · August 24, 2009

Your error with disk utility and permissions is already a classic one for SL already (when installed from working Leopard).
Try reinstalling from within Snow BaseSystem.pkg (you will find it in the directory System/Installation/Packages/ on the SL disk, you need to mount it and make hidden files visible to access it). Then you will be able to use disk utility to fix permissions and I think that many of your error will dissapear then.

If you still want to reinstall SL on a new partition or disk, do it from your already functioning SL install, so you won't get this error again.

Good luck.

I did reinstall of basesystem.pkg and ended up with system that can't recognize my user name and password when i need to enter it as admin. can't sudo in terminal either, but no biggie, i'll just reinstall it

KariNeko · August 24, 2009

Thanks guys for the answers

I Reinstalled using PC EFI 10.1 instead of 10.2 and zero problems since first boot :wacko:

So we don't have to use 10.2 it seems.

I want to try the BaseSystem.pkg fix for Disk Utility but now I'm afraid to what happened to Crawley.

userx · August 24, 2009

Thanks guys for the answers

I Reinstalled using PC EFI 10.1 instead of 10.2 and zero problems since first boot

So we don't have to use 10.2 it seems.

I want to try the BaseSystem.pkg fix for Disk Utility but now I'm afraid to what happened to Crawley.

A word of advise to everyone.

DO NOT INSTALL SNOW LEOPARD FROM WIHIN LEOPARD USING THE OSINSTALL.MPKG!!!

This is a sure way to get a install that will fail in someway. For instance not being able to repair permissions, and many other errors, on your install.

Do it the proper way. Use an external source like a 8GB thumb drive or an external USB drive.

Crawley · August 24, 2009

here is what i did after the s**t happend:

1. restored SL install image to another partition,

2. copied /extra folder to the restored partition

3. started installation from hdd

additionaly, i used migration assistant and have all my software working in 15min :rolleyes:

* i used pcefi 10.2beta in addition to chameleon 2 rc2

** you have to have working leopard system in order to restore disk image to hdd and 2 spare partitions(one for installation disk and one for new snow install), which shouldn't be a problem if you installed on a guid partition. you can go and format your existing sl partition, but in that case you lose all of your installed software

*** used carbon copy cloner to restore install dmg, for some reason, couldn't do it with disk utility in leopard

KariNeko · August 24, 2009

So I can?

1_ Partition a hard drive with GUID partition scheme in 2 partitions. For example Snow and SnowInstaller.

2_ Restore Snow Leopard DVD / DMG image to SnowInstaller volume.

3_ Put at SnowInstaller volume:

/Volumes/SnowInstaller/DSDT.aml
/Volumes/SnowInstaller/Extra/com.apple.Boot.plist
/Volumes/SnowInstaller/Extra/smbios.plist
/Volumes/SnowInstaller/Extra/Extensions/AppleIntelPIIXATA.kext
/Volumes/SnowInstaller/Extra/Extensions/PlatformUUID.kext
/Volumes/SnowInstaller/Extra/Extensions/fakesmc.kext
/Volumes/SnowInstaller/"any other necessary kexts"

com.apple.Boot.plist containing boot-uuid for SnowInstaller volume.

4_ Now install to SnowInstaller Chameleon 2 and then overwrite boot file with PCEfi's one.

5_ Boot with that hard drive and select SnowInstaller from Chameleron bootloader, then install.

6_ Boot with that hard drive and select Snow now, boot with -x32.

7_ Run Kext Utility.

8_ Install to Snow volume Chameleon 2 and then overwrite boot file with PCEfi's one

9_ Copy now all the files that I previously copied to SnowInstaller volume to Snow.

10_ Edit /Extra/com.apple.Boot.plist (corresponding to Snow) with Snow UUID.

Now we can boot either the installed OS and the installer DVD? so if we need to reinstall Snow Leopard we only have to boot choosing SnowInstaller volume?

Will step 6 work?

Thanks in advance

Crawley · August 24, 2009

it should, but wouldn't hurt if you have chameleon and pcefi isntalled on another harddrive, if you a spare one (that was my case, I have some old 80gig antique)

KariNeko · August 24, 2009

I'll try it now. I'll keep you posted.

Finished restoring Snow Leopard image to the second partition (SnowInstaller). Installed Chameleon, PCEfi 10.1 boot file. Copied DSDT and files contained in Extra. Edited com.apple.Boot.plist with SnowInstaller UUID. Now going I'm going to restart.

[Edit]

Update 1:

I had to install Chameleon before restoring the install image to the partition because I Chameleon installer hang when it started copying files. Not really hang, but it stays there and the progress bar didn't move.

Then I copied boot file, DSDT.aml, files in /Extra.. everything I mentioned on the previous post.

Installer started fine but I got kernel panics :rolleyes: in either 32 and 64 bit modes.

thread: Mac OS X Install

thread: kextcache

thread: fsck_hfs

...

ronalith · September 2, 2009

I'm having the exact same problem.

I'll try it now. I'll keep you posted.
Finished restoring Snow Leopard image to the second partition (SnowInstaller). Installed Chameleon, PCEfi 10.1 boot file. Copied DSDT and files contained in Extra. Edited com.apple.Boot.plist with SnowInstaller UUID. Now going I'm going to restart.

[Edit]

Update 1:

I had to install Chameleon before restoring the install image to the partition because I Chameleon installer hang when it started copying files. Not really hang, but it stays there and the progress bar didn't move.

Then I copied boot file, DSDT.aml, files in /Extra.. everything I mentioned on the previous post.

Installer started fine but I got kernel panics in either 32 and 64 bit modes.

thread: Mac OS X Install

thread: kextcache

thread: fsck_hfs

...

c0rk007hck · September 10, 2009

Try to boot with maxmem=1995, maybe a Viaata or Jmicron driver crashes

Waiting for DSMOS...

Recommended Posts

Link to comment

Share on other sites

Link to comment

Share on other sites

Link to comment

Share on other sites

Link to comment

Share on other sites

Link to comment

Share on other sites

Link to comment

Share on other sites

Link to comment

Share on other sites

Link to comment

Share on other sites

Link to comment

Share on other sites

Link to comment

Share on other sites

Link to comment

Share on other sites

Link to comment

Share on other sites

Link to comment

Share on other sites

Link to comment

Share on other sites

Link to comment

Share on other sites

Link to comment

Share on other sites

Link to comment

Share on other sites

Link to comment

Share on other sites

Link to comment

Share on other sites

Link to comment

Share on other sites

Link to comment

Share on other sites

Link to comment

Share on other sites

Link to comment

Share on other sites