farski Posted June 5, 2011 Share Posted June 5, 2011 My hack, 10.6.6 P5K Pro, has been working perfectly for months and months. I had to restart today because I got bit by a bug with Spaces (where it prevents the keyboard from working, not a hack thing, happens on my Macbook also), and the machine suddenly won't boot. I haven't run any significant updates recently that I can remember, but it's been up for probably 3+ weeks, so who knows what I did in that time. Getting stuck on: MAC framework successfully initialized Using 16304 buffer headers and 4096 cluster IO buffer headers IOAPIC: Version 0x20 Vectors 64:07 Any help would be greatly appreciated. I looked around for any signs that something that happened in the last couple of weeks was causing any issues, but didn't come across anything. I'm on 10.6.6 which I've been using for a long time. Link to comment https://www.insanelymac.com/forum/topic/258573-sudden-stopped-working-syndrome/ Share on other sites More sharing options...
kch0pa Posted June 5, 2011 Share Posted June 5, 2011 Have you tried the usual boot switches? First, try booting with -f, then -x, then -x cpus=1 Link to comment https://www.insanelymac.com/forum/topic/258573-sudden-stopped-working-syndrome/#findComment-1693353 Share on other sites More sharing options...
bubbaganoush Posted June 5, 2011 Share Posted June 5, 2011 Did you install a new DSDT file or run that [url="http://www.insanelymac.com/forum/topic/279450-why-insanelymac-does-not-support-tonymacx86/"]#####[/url] thing from tonymacx86 by any chance? Link to comment https://www.insanelymac.com/forum/topic/258573-sudden-stopped-working-syndrome/#findComment-1693358 Share on other sites More sharing options...
farski Posted June 6, 2011 Author Share Posted June 6, 2011 Haven't touched the DSDT, kexts, etc in months since it's been rock solid. I tried v, f, x, and single user mode all separately when it first started. I will try cpus=1 tomorrow, but I've never had to do that before. I can also try booting into the copy of 10.5 I keep around and rebuilding the kext cache manually, if anyone thinks that will help... Link to comment https://www.insanelymac.com/forum/topic/258573-sudden-stopped-working-syndrome/#findComment-1693440 Share on other sites More sharing options...
farski Posted June 7, 2011 Author Share Posted June 7, 2011 Ok, tred -f then -x cpus=1 and I'm getting to the same spot. Even with the cpus flag, though, that screen is listing 4 cpus as "Enabled", is that the expected behavior? Link to comment https://www.insanelymac.com/forum/topic/258573-sudden-stopped-working-syndrome/#findComment-1693925 Share on other sites More sharing options...
Penguin! Posted June 8, 2011 Share Posted June 8, 2011 Try booting with "arch=i386" and see if it works in 32-bit mode. Link to comment https://www.insanelymac.com/forum/topic/258573-sudden-stopped-working-syndrome/#findComment-1694672 Share on other sites More sharing options...
farski Posted June 9, 2011 Author Share Posted June 9, 2011 Nope, same result. I even stripped out a bunch of non-essential kexts and that had no effect. Link to comment https://www.insanelymac.com/forum/topic/258573-sudden-stopped-working-syndrome/#findComment-1695328 Share on other sites More sharing options...
Gringo Vermelho Posted June 10, 2011 Share Posted June 10, 2011 Hackintosh-on-ASUS-mobo syndrome. It's halting right before it should display "mbinit: done". Try a CMOS reset. Switch off or unplug the PSU from the mains, remove the battery and close the CLRCMOS jumper for 5 minutes. Don't forget to set your BIOS settings back where they were. Link to comment https://www.insanelymac.com/forum/topic/258573-sudden-stopped-working-syndrome/#findComment-1695400 Share on other sites More sharing options...
Noam AA Posted June 10, 2011 Share Posted June 10, 2011 so i had some problem like this on my asus p5k-se but it wasn't happened just like that, a friend gave me 460 gtx to try, and i got this message when inserting the card. when extracted a new dsdt, and applied the patches, i passed this IOAPIC when inserting my 220 gt, i got this massage once again (but didn't remembered i extracted the dsdt before.. lol) so i didn't know what to do, because my dusty old 8400 gs booted with the new dsdt. when remembered, i replace the dsdt and once again able to boot i suggest you, even if you didn't do anything, extract a new dsdt under windows or linux, and apply your patches again, maybe it will work Link to comment https://www.insanelymac.com/forum/topic/258573-sudden-stopped-working-syndrome/#findComment-1695432 Share on other sites More sharing options...
farski Posted June 10, 2011 Author Share Posted June 10, 2011 Thanks for the tip. I grabbed a fresh DSDT for my mb that I know I've patched before to get to a working state, applied some patches, verified my p states, etc. Still getting the same error. I haven't done a CMOS reset yet; I'm wondering how that could in any way impact this since it's getting relatively far along into the boot process. I may try it anyway, but if you have a specific reason I'd love to hear it. Link to comment https://www.insanelymac.com/forum/topic/258573-sudden-stopped-working-syndrome/#findComment-1695769 Share on other sites More sharing options...
Gringo Vermelho Posted June 10, 2011 Share Posted June 10, 2011 I'm wondering how that could in any way impact this since it's getting relatively far along into the boot process. No it isn't far at all, at that point (your screenshot) it's not done talking to your motherboard yet. http://en.wikipedia.org/wiki/Intel_APIC_Architecture A CMOS reset has worked for me (and for others, do a forum search) on two different ASUS motherboards when halting at that specific part during boot. I don't know why and I don't care. If you don't like the idea, don't do it. Link to comment https://www.insanelymac.com/forum/topic/258573-sudden-stopped-working-syndrome/#findComment-1695773 Share on other sites More sharing options...
farski Posted June 10, 2011 Author Share Posted June 10, 2011 I'm pretty much at that point, so as soon I have a chance to have my computer off long enough to do it (currently booting into a stable copy of 10.5 to get some work done) I will. I'm just wondering from a technical standpoint how CMOS can affect this process. Not doubting, just curious. Link to comment https://www.insanelymac.com/forum/topic/258573-sudden-stopped-working-syndrome/#findComment-1695776 Share on other sites More sharing options...
Gringo Vermelho Posted June 11, 2011 Share Posted June 11, 2011 If it makes you feel better about it, I'll invent something that might explain why it would work: Besides the user configurable BIOS settings, CMOS RAM stores other low level motherboard configuration data, depending on CPU used, amount of RAM installed, BIOS settings or what have you. Maybe some data got corrupted over time and Chameleon or OS X now fails to get or set some status information, and halts because of that. Whatever...it doesn't matter anyway. If it works for you, great, if not, sorry. Link to comment https://www.insanelymac.com/forum/topic/258573-sudden-stopped-working-syndrome/#findComment-1695785 Share on other sites More sharing options...
Recommended Posts