68 replies to this topic

[akmedia]

Donk, on Oct 13 2011, 03:02 PM, said:

Decided to put this in one place so everyone can see what to do. Firstly thanks Zenith432 for finding the offending extension and showing 10.7.1 still works. The post is here.

http://www.insanelym...p...t&p=1758947

If you have yet to upgrade then follow these simple steps to avoid the problem.

1. Take a snapshot, backup or do something to make sure you can always get back if something goes wrong.
2. Start the Lion guest and the open a Terminal under Applications Utilities
3. Copy the existing AppleLSIFusionMPT.kext to the current directory:

cp -rv /System/Library/Extensions/AppleLSIFusionMPT.kext .

4. Now run the 10.7.2 update package but stop and do not reboot - if you do go find that backup or snapshot as you will have to start again! See the attached image.
5. Go back to the terminal prompt and run these 2 commands. You will be prompted for your password.

sudo rm -rfv /System/Library/Extensions/AppleLSIFusionMPT.kext
 sudo cp -rv AppleLSIFusionMPT.kext /System/Library/Extensions

6. Now you can reboot.

If everything is done correctly should reboot successfully using the older SCSI driver.

Thanks for this post. I was able to successfully upgrade to 10.7.2. Now installing mac OS X server

[primal51]

Any chance there is a full walk through for how to do this including all required steps? I've got 10.7.1 setup and working but I'm not entirely sure how to do this process.

[bookemdano]

primal51, on Oct 14 2011, 11:08 AM, said:

Any chance there is a full walk through for how to do this including all required steps? I've got 10.7.1 setup and working but I'm not entirely sure how to do this process.

What are you unclear on? Donk's post is pretty thorough. The only detail that isn't clear is that you should download the 10.7.2 update from Apple's web site and not use software update to do it. The reason for that is so you can copy back the old version of the problematic file prior to the reboot.

But the most important part of the whole thing is to take that snapshot prior to doing anything! That way if you screw up you can always revert to that snapshot.

[DeathWok]

The problem I'm having and I suspect some others above is following the install, osx will automatically reboot, there is no option to choose when you want to reboot. I've tried auto update which doesn't work since the 10.7.2 updated files are only copied during the shutdown sequence, I've tried the OS X Lion Update 10.7.2 Client Combo and also the OS X Lion Update 10.7.2 (Client) which prompts you before the install with this:



If you choose cancel the update will cancel, if you choose continue, the system will automatically reboot without a prompt so there is no time to restore the old AppleLSIFusionMPT.kext

[Donk]

DeathWok, on Oct 14 2011, 08:52 PM, said:

The problem I'm having and I suspect some others above is following the install, osx will automatically reboot, there is no option to choose when you want to reboot. I've tried auto update which doesn't work since the 10.7.2 updated files are only copied during the shutdown sequence, I've tried the OS X Lion Update 10.7.2 Client Combo and also the OS X Lion Update 10.7.2 (Client) which prompts you before the install with this:



If you choose cancel the update will cancel, if you choose continue, the system will automatically reboot without a prompt so there is no time to restore the old AppleLSIFusionMPT.kext

Go and download the update from Support site DO NOT use Software Update.

[sebus]

Make a copy of your 10.7.1, upgrade one copy
Use the other one later & attach the upgraded disk, copy the kext

After all the VMs are only plain files, so you can do whatever you want with them

sebus

[Schamsen]

Hmmm any ideas when there is no such file/driver ? i mean i can't find the AppleLSIFusionMPT.kext (nowhere on the disk !). I know this might be a stupid question but i have no clue why i should not have this file ? Running 10.7.1 under Workstation 8.0

edit: is it possible that somebody could upload the working file, that i can try to put it in the folder, or would this method not work ?

[kup]

I found the easiest way to fix the problem was to

1: Copy the 10.7.1 (or .0) version of the offending KEXT to your desktop.

2: Install the update (not software update).

3: Before rebooting use Kext Wizard to reinstall the older KEXT and then update/fix KEXTS and permissions in Kext Wizard.

4: Reboot. Fixed.

[Schamsen]

omfg i think it was too late yesterday night, the problematic file has just another name ! its called AppleLSIFusionMPT.kext. Tried it today and it worked.

[Zenith432]

BTW, AppleLSIFusionMPT.kext was the same in OS 10.7.0 and OS 10.7.1, so if you have the Lion install DVD, you can get it from there.  It's inside BaseSystem.dmg.

Added: I figured out how to boot the Lion recovery partition in VMware.  Boot into the EFI shell and then

fsX:\com.apple.recovery.boot\boot.efi -v npci=0x2000

where X is the number of the recovery partition (use "map -b" to find it).
However there's a catch - if you install the 10.7.2 Lion Recovery Update, it will update AppleLSIFusionMPT.kext on the recovery partition, and you won't be able to boot it anymore.
The recovery partition can be mounted on a regular system by doing "diskutil list", (look for Recovery HD) and then "diskutil mount <device name>".  If you copy over kernelcache from the Lion Install DVD to com.apple.recovery.boot on the recovery partition, it will boot even if you've installed 10.7.2 recovery.

[Goja]

It worked, thanks! Everyone, make you you don't forget the . at the end of the command > cp -rv /System/Library/Extensions/AppleLSIFusionMPT.kext .

[shawken]

Just to add on to what was said earlier, here is another alternate write up on performing the repairs if you HAVE updated to 10.7.2 and are stuck at the moment, the key is having the original installer file/hard disk you first used to actually install the OS.

If you are like me, when you updated your VMWare installation of Lion to 10.7.2 it started all sorts of problems, including no longer booting at all.  If this is the case where you receive a grey screen on boot with an abort logo, and you may notice there is no activity on the HDD LEDs at the bottom of VMWare you simply have to replace some files that are preventing the boot of Lion.  

Follow these steps and hopefully you will be back up and running:

1) Change the boot order of your hard drives in VMWare, you should still have the original installation file(vmdk) listed as a Hard Disk device; if not, Add it again to the Virtual Machine.

Edit Virtual Machine Settings
Select your 5GB drive of the Mac OS X Lion.vmdk
Advanced button
Change to device SCSI 0:0 so it will boot to the installer again
You may be prompted to "switch" the drives, that is fine.

2) Turn the machine back on and you should load into the Mac OSX Installer for Lion

3) From the Utilities section choose Terminal and perform the following:

cd /Volumes

ls
-now you should see a couple listings, one for the installer which you can ignore, and the one we want being your Mac HD name-

cd [Name of your Mac HD]/System/Library/Extensions/
rm -r AppleLSIFusionMPT.kext
cp /System/Library/Extensions/AppleLSIFusionMPT.kext/ .
chmod -R 444 AppleLSIFusionMPT.kext

4) Shutdown the installer, edit virtual machine hard drives back to the normal settings with your larger partition being the main boot drive SCSI 0:0

5) Reboot

Thanks to Zenith432 and cruptorix for their intel!

[SirJohn2024]

I want to thank you all for the fix, but for me it doesn't work, even if my installation is quite standard (VMWK 8 on W7 64 & Lion 10.7.1)...
What I had to do is to reverse to a previous version also for the IOPCIFamily.kext...
I post just in case someone else found the fix not working...

Sound strange, but I try the first fix several times before trying something different.

Anyway great job

[elnekis]

Worked Perfect!

I have a Lion VM running on VMWare Workstation 8 on Windows 7 64 bit.  THanks!

[Joe Tikal]

thx for the great work!

Running also fine 10.7.2 on my VMWare Workstation 8 on Windows 7 64 bit. :-)

[mfred]

Thanks to shawken's post for helping me get back up and running.  I do have another problem... after I replaced the AppleLSIFusionMPT.kext file and brought my dead VM back up, I rebooted to make sure all was good.  This time it hung in the same exact place as before.  I followed shawken's procedures once again and found that the AppleLSIFusionMPT.kext file was now 0 bytes.  Any idea why this is happening to this file?

[GnatGoSplat]

I have the same problem, worked once after I put the older .kext in, but no longer works in subsequent reboots.

[Giovanni Stefani]

This is the procedure that I used and it worked perfectly:

1. Downloaded the MacOSXUpdCombo10.7.2.dmg from torrent site
2. Ran the first Terminal command line to make a backup of AppleLSIFusionMPT.kext to the current directory
3. Ran the MacOSXUpdCombo10.7.2.dmg to update to 10.7.2. NO REBOOT
4. Ran the second/third Terminal command lines to delete the new AppleLSIFusionMPT.kext in the Extensions folder and replace the old copy (current directory) to the Extensions directory.
5. Rebooted. Everything came up fine.  Made a VM Snapshot.

The issue with using Apple Update is it doesn't apply the update until you specify reboot and then there is no way to overwrite the new AppleLSIFusionMPT.kext with the old one in your current directory.

Thanks Donk for posting the procedure here.

[Diodak]

For those who don't like the command line, I prepared a package installer with the necessary extension. Just run attached installer before hitting restart button in 10.7.2 update.

Attached Files

•  AppleLSIFusionMPT_3.0.0.pkg.zip   104.12K   455 downloads

[morgan565634982]

Greetings,

Not sure if this question is in the right topic, feel free to move it in a more suitable place.

I installed Lion and updated to 10.7.2 according to this tutorial and added the vmware SVGA II driver supplied here. Works perfectly now.

Just wanted to let you know that iWork does not seem to function properly. Whatever I try to type does not appear (and yes I use the Word Processing Empty template). I tried opening all the templates and all I get each time is juste a white page. I know the text is here becasuse when I randomly click on the document, page setup changes (margins etc.).

Looks like a bug linked to graphics. I read somewhere on another forum that some guy had the same problem on an old mac and had tu change his graphics card.