L0n3S7arW0lf Posted July 18, 2011 Share Posted July 18, 2011 I used this guide seems to work for others, after install I booted from snow leopard (10.6.8) and copied over my Extra folder with extentions folder: ACPIMonitor.kext ElliottForceLegacyRTC.kext EvOreboot.kext FakeSMC.kext LegacyAppleRTC.kext NullCPUPowerManagement.kext SuperIOFamily.kext Also my com.apple.boot plist, dsdt.aml, and smbios! All from [url="http://www.insanelymac.com/forum/topic/279450-why-insanelymac-does-not-support-tonymacx86/"]#####[/url] 3.8 I then installed Chimera to the Lion disk and replaced the AppleACPIPlatform.kext and IOPCIFamily.kext (system/library/extensions) with ones from 10.6.7 shut down removed SL HDD Then I boot into New Lion (safe mode -x -v -f) I get this I press the power button once and BAM this shows up! Can anyone give me a fix please? Link to comment Share on other sites More sharing options...
CooSee Posted July 18, 2011 Share Posted July 18, 2011 you can't just copy all your kext to your new Lion HD without repairing the permissions, etc.! did you do that ? boot to your SL again and use ' KextWizard ', to repair the permissions on the Lion HD and by the way, all the kexts, maybe except for ' NullCPU .... ', won't work, you need kexts for Lion, especially, IMHO! and the guide you used to install Lion, is messed up a little bit. try this one MaLd0n's USB Method ! or use tonymacx86's [url="http://www.insanelymac.com/forum/topic/279450-why-insanelymac-does-not-support-tonymacx86/"]#####[/url] ! CooSee ' Ya Link to comment Share on other sites More sharing options...
L0n3S7arW0lf Posted July 18, 2011 Author Share Posted July 18, 2011 They are Lion compatable kext from [url="http://www.insanelymac.com/forum/topic/279450-why-insanelymac-does-not-support-tonymacx86/"]#####[/url] 3.8 (the newest) and yes I repaired my permissions!! Link to comment Share on other sites More sharing options...
CooSee Posted July 19, 2011 Share Posted July 19, 2011 remove all the kexts, except NullCPU... and FakeSMC and put them to /S/L/E and not /E/E/. and why you unplug your SL HD at all? you don't have to! i assume your MainBoard has a BootMenu, e.g. F12; you can choose from which HD you want boot. if you got a dsdt.aml for your system, why using NullCPU... at all? i only use FakeSMC and RealtekRTL81xx in /S/L/E, fewer are better CooSee ' Ya Link to comment Share on other sites More sharing options...
L0n3S7arW0lf Posted July 19, 2011 Author Share Posted July 19, 2011 remove all the kexts, except NullCPU... and FakeSMC and put them to /S/L/E and not /E/E/. and why you unplug your SL HD at all? you don't have to! i assume your MainBoard has a BootMenu, e.g. F12; you can choose from which HD you want boot. if you got a dsdt.aml for your system, why using NullCPU... at all? i only use FakeSMC and RealtekRTL81xx in /S/L/E, fewer are better CooSee ' Ya First the dsdt.aml is one from using DSDT Auto-Patcher and it's not fully edited! Two F12 nor F8 work for boot slection on my mobo or I would use it. Lastly I deleted all in /e/e and installed FakeSMC to /S/L/E the repaired permissions again. Still get stuck at DSMOS has arrived F718x: Fintek: Found unsupported chip ID=0xb3 REVISION=0x53 I know thats the Firewire chip! Now does anyone know a real fix? Link to comment Share on other sites More sharing options...
CooSee Posted July 19, 2011 Share Posted July 19, 2011 I know thats the Firewire chip! deactivate FireWire in your BIOS! Now does anyone know a real fix? WHAT i'am trying to help! if you're not pleased, i will call ' Mr. Heisenberg ' CooSee ' Ya Link to comment Share on other sites More sharing options...
L0n3S7arW0lf Posted July 19, 2011 Author Share Posted July 19, 2011 NO no the help is appreciated, I have disabled the firewire but it still finds the chip and gives same error. I know the chip is the same as on all P7P55D type boards and other have had no issues so I am kinda lost Link to comment Share on other sites More sharing options...
CooSee Posted July 19, 2011 Share Posted July 19, 2011 that's really odd, your Board is working with SL but not with Lion!? did you try to boot with ' arch=x86_64 ' ? CooSee ' Ya Link to comment Share on other sites More sharing options...
L0n3S7arW0lf Posted July 19, 2011 Author Share Posted July 19, 2011 yes -arch=i386 then -arch=x86_64 Also should state it says waiting for DSMOS now (after disabling Firewire in BIOS), just stops nothing else happens let it sit for 20 mins Link to comment Share on other sites More sharing options...
Rackers Posted July 19, 2011 Share Posted July 19, 2011 Remove the F178x kext from SuperIOFamily (don't just remove SuperIOFamily) in your Extras folder, I believe it is Lion incorrectly detecting a chip. See my post, exact same symptoms as yours, my Lion is fine now. http://www.insanelymac.com/forum/index.php...p;#entry1712277 Link to comment Share on other sites More sharing options...
Recommended Posts