Jump to content
Welcome to InsanelyMac Forum

Register now to gain access to all of our features. Once registered and logged in, you will be able to contribute to this site by submitting your own content or replying to existing content. You'll be able to customize your profile, receive reputation points as a reward for submitting content, while also communicating with other members via your own private inbox, plus much more! This message will be removed once you have signed in.


  • Content count

  • Joined

  • Last visited

About pmfcmmak

  • Rank
    InsanelyMac Protégé
  1. I created a snapshot at 10.7.1, installed 10.7.2 and shut down the VM, booted into the 10.7.1 snapshot with the 10.7.2 disk mounted and copied the .kext. However, to me there was no need to make the .kext read-only. Make sure you set up the permissions correctly and reubild the caches: chown -R 0:0 /System/Library/Extensions/AppleLSIFusionMPT.kext touch -c /System/Library/Extensions kextcache -system-prelinked-kernel kextcache -system-caches I assume that the 10.7.2 is copied from the recovery partition if there are any cache misses or permission errors.
  2. You are probably running into this problem: http://www.insanelymac.com/forum/index.php...t&p=1759872
  3. Does anyone coincidentally known on how to change to keyboard layout in Mac OS X to reflect a PC-like (german) layout, not Apple-like (german) layout? For example @ should be AltGr+Q, not AltGr+L and so on.
  4. I'm not quite sure but it seems like kextcache -system-prelinked-kernel kextcache -system-caches did the trick. Thanks to Zenith432.
  5. Is it possible that the AppleLSIFusionMPT.kext is replaced by the 10.7.2 automatically when replaced with the 10.7.1? I have replaced the .kext with the 10.7.1 and I could successfully boot into 10.7.2 but after shutting down I'm stuck at next boot. I have to replace the .kext again with the 10.7.1 (and again, and again). Is there any way to make this change persistent? Do I have to deleted any caches or disable any "automatic .kext update" feature?
  6. Accidental regression or on purpose - what do you think?
  7. Yes (at least it does for me). Anyone already upgraded to 10.7.2? I'm stuck again when not specifiying npci=0x2000 (didn't happen after upgrade to 10.7.1). However, if I now boot the Mac OS X installation using the EFI shell (Boot VM -> ESC -> Boot Manager -> Internal Shell -> fs1:\System\Library\CoreServices\boot.efi npci=0x2000 -v) I'm stuck on ... rooting via boot-uuid from /chosen: 39CACFF3-96... Waiting on <dict ID="0"><key>IOProviderClass</key><string ID="1">IOResources</string><key>IOResourceMatch</key><string ID="2">boot-uuid-media</string></dict> Still waiting for root device Still waiting for root device ... Any thoughts on that?
  8. Thanks for your suggestion. It looks like adding npci=0x2000 did the trick! I just wonder why some people obviously do not need it and others do need it ...
  9. Is there any way to track down the problem (boot loader log file or something like that)? Can some please post a working VMX file, preferably with virtualHW.version = "8" and guestOS = "darwin11-64"? In addition, can someone please verify these hashes? fciv -md5 InstallESD.dmg b5d3753c62bfb69866e94dca9336a44a installesd.dmg fciv -md5 InstallESD.dmg (InstallESD.dmg/InstallMacOSX.pkg/InstallESD.dmg) 4c2bda281dd39b562e478dc94895b9be installesd.dmg fciv -md5 InstallESD.img (dmg2img InstallESD.dmg InstallESD.img) 20a43e3d614c638928d663070c47b7aa installesd.img fciv -md5 InstallESD.iso (UltraISO InstallESD.dmg -> InstallESD.iso) 9d673c53b800d3df9154e0d83f7784bf installesd.iso Any further thoughts on the problem?
  10. I ran install.cmd in a elevated command line and after completing with no errors I ended up with the following files: VMware Backup vmwarebase.dll 4.298 KB 4.298 KB vmware-vmx.exe 16.078 KB 14.736 KB vmware-vmx-debug.exe 18.702 KB 18.702 KB vmware-vmx-stats.exe 17.239 KB 17.239 KB x64/vmware-vmx.exe 16.078 KB 16.078 KB x64/vmware-vmx-debug.exe 20.307 KB 20.307 KB x64/vmware-vmx-stats.exe 18.605 KB 18.605 KB fciv -md5 -r "VMware Workstation" 28d0c2e389198e694a6c3a8fea4a3089 vmware workstation\vmware-vmx-debug.exe bfd605acdfde6afe1af1f85288175123 vmware workstation\vmware-vmx-stats.exe e51a6cb763538ce59ddfe3bdbf285b2d vmware workstation\vmware-vmx.exe c4a64b55212e51582fc8e80b39c04d4d vmware workstation\vmwarebase.dll 1e131e01f7f4fb71f27db2df22a2dcf4 vmware workstation\x64\vmware-vmx-debug.exe e81e4a2a3293d2294dd8422e1d07363a vmware workstation\x64\vmware-vmx-stats.exe 9bd2b5c5463a98226190dd80c0057a54 vmware workstation\x64\vmware-vmx.exe fciv -md5 -r backup 47417606f94ebc9cb97710753f3c5a24 backup\vmware-vmx-debug.exe 6bb89997e5c57fcedd5e5b44caf5f3c6 backup\vmware-vmx-stats.exe be72b605b23e415ba0690bf1f94dcd3c backup\vmware-vmx.exe bd624c7e5420affa169daaea42d21cce backup\vmwarebase.dll 4c69c56de2e41e2eda505e19ed9c4ada backup\x64\vmware-vmx-debug.exe 2dabcaa317b8881f4bdfb0413a14d4c2 backup\x64\vmware-vmx-stats.exe 208b36a90152967d5bfb1c27e3caa335 backup\x64\vmware-vmx.exe According to the hashes all the files have been obviously patched (and I could select the "OS X 10.7" option). As said I'm stuck right at the gray screen with the apple logo with moderate CDROM and HD activity which drops to occasional activity fast. Using an unpatched version of VMware Workstation and a preconfigured VMX it went through the gray screen but stuck at the following spinning rainbow screen. VMX and log beeing attached to this post. vmware.log.txt Mac_OS_X_10.7__x86_64_.vmx.txt
  11. I'm stuck at the Apple logo too. This is what I've done: 1) Installed VMware Workstation 8 on Windows 7 x86_64 2) Applied Donks VMware patch linked at the top of this thread. 3) Created an ISO file out of the original InstallESD.dmg 4) Created a new VM using "OS X 10.7" type, default hardware, CD/DVD changed to SCSI 1:0, using the ISO created in the previous step 5) Booted the VM - stuck at the Apple logo I also tried to disable the SMC by setting smc.isPresent to "false" in the VMX, but no luck. br pmf