waiting for DSMOS after installing legacy audio kexts

[fmillion]

I'm trying to get os x running on a msi wind PC with the intel NM10 chipset, GMA3150, Atom D510.

 

I was unable in the end to get the OS installed directly on the machine and I was not up to creating a custom boot image, so I simply restored a prepared osx vanilla install on my real mac. I then formatted the efi partition, manually installed kexts and Chameleon, replaced the kernel with the Atom compatible 10.4.0 on this forum, moved the disk to the Wind PC, and booted. The system booted fine, but with no ethernet and audio. (No accelerated video either, but as I understand it, there's as of now no support for the GMA3150...)

 

It seems the box has an aLC888, so I installed the enabler for it and also downgraded from 10.6.4 to the 10.6.2 apple audio driver. I also installed the r10000 ethernet driver for ethernet support. I repaired kext caches and all that jazz.

 

Now on reboot I get stuck at waiting for DSMOS...

 

Installing the ethernet support did work, because right before the DSMOS message it says AppleRTL8169Ethernet and prints my card's MAC address so I'm guessing that part worked. No word on if the audio did.

 

Just not sure why installing these kexts caused me to get stuck at waiting for DSMOS

 

Any ideas?

 

Thanks

 

fm

[westwaerts]

boot with -s argument , special kexts are not loaded then, and see if it comes up.

 

did you install the kexts right ? ( repair permissions, rebuild mkexts, etc.)

if not do this and reboot.

[fmillion]

Booting with -s works, brings me to the root prompt, and things work from there as i'd expect. The problem occurs on normal boot, stuck at waiting for DSMOS. I'll try removing the drivers I added and see if it'll boot up that way.

 

Still just unsure as to what would have caused this.

 

FM

[westwaerts]

Booting with -s works, brings me to the root prompt, and things work from there as i'd expect. The problem occurs on normal boot, stuck at waiting for DSMOS. I'll try removing the drivers I added and see if it'll boot up that way.

 

Still just unsure as to what would have caused this.

 

FM

 

and if everything is fine booted with -s

run kextutility to fix all extension-permissions, rebuilds etc.

should even boot normally or you have a kext installed or twice installed your system dislikes.