Jump to content
8 posts in this topic

Recommended Posts

I know many people have this problem, and they are all able to correct it (usually at least) But I cant seem to figure out what I need to do based on other peoples success since they are using different hardware than me and everything.

 

I had this exact install working on my old computer perfectly. I really wish the mainboard didnt fry on it, because it was VERY mac-friendly (even if it was pentium 4). Anyway my system specs are as follows

 

AsRock Wolfdale1333-D667 Revision 2.0 (Which is on the hardware compatibility list)

1gb DDR2-667 RAM

Celeron Dual Core E2610 @ 1.6ghz

Nvidia Geforce 8500gt

 

It goes through the entire installation, but at bootup it just shows the apple logo, no spinning circle. I have tried -x and -f with no fix. I also tried cpus=1, which made the spinning circle appear, but it would just spin forever and never boot up.

 

I booted into verbose, and I don't exactly know how to read it to tell you what its frozen on, but it says

 

 

 

npvhas=4095

hi mem tramps at 0xffe00000

PAE enabled

64 bit mode enabled

Darwin Kernel Version 9.6.0: Mon Nov 24 17:37:00 PST2008; root :xnu-1228.9.59~1/release_I386

standard timeslicing quantum is 10000 us

vm_page_bootstrap: 255460 free pages and 6684 wired pages

mig_table_max_displ = 79}

Extension "com.apple.drive.AppleACPIPlatform" nhas immediate dependencies on both com.apple.kernel and com.apple.kpi componets use only one style.

AppleDecrypt: Copyright © 2008 Dale Walsh

AppleDecrypt: Starting...

AppleACPICPU: ProcessorApicId=1 LocalApicId=0 Enabled

AppleACPICPU: ProcessorApicId=2 LocalApicId=1 Enabled

AppleACPICPU: ProcessorApicId=3 LocalApicId=130 Disabled

AppleACPICPU: ProcessorApicId=4 LocalApicId=131 Disabled

Loading Security extension com.apple.security.TMSafetyNet

calling mpo_policy_init for TMSafetyNet

Security policy loaded: Safety net for Time Machine (TMSafetyNet)

Loading security com.apple.security.seatbelt

calling mpo_policy_int for mb

Seatbelt MACF policy initialized

Security policy loaded: Seatbelt Policy (mb)

Loading security extension com.apple.nke.applicationfirewall

 

Then all the copyright information...

 

 

 

Mac Framework Successfully Initialized

 

using 5242 buffer headerse and 4096 cluster IO buffer headers

 

 

 

For what it's worth the Hardware Compatibility list says to use Vanilla 9.5.0 Kernel on iDeneb 1.4, but the only one offered in the install is Voodoo 9.5.0

 

This install was a bare install, just the core OSx86, and default kernel (Because i thought maybe i was having hardware incompatibility problems)

 

 

 

Let me know what you guys think i should do!

Link to comment
https://www.insanelymac.com/forum/topic/209855-ideneb-14-freezes-at-bootup/
Share on other sites

i will try to locate that, and get it. Every other disk I have tried (iATKOS, iPC) have all just had the infinite boot loop and wont even make it into setup. I'll try 1.6 and get back to you. Thanks

 

drivers are pretty self explanatory, but what patches should I choose in the installer?

 

 

 

thanks

okay so the iDeneb 1.6 install finished, and I am having the same problem. It freezes at the apple logo. How do I correct this problem..is it a hardware problem? i am using an AsRock Wolfdale 1333-D667 r 2.0 which IS on the compatibility list, but it says you need to have bios version 1.50 modified..and it has a downlaod link to a file that is a .50 file? I dont know that file extension and i Googled it, andnothing came up. I am running bios 1.50 from AsRock right now.

 

 

 

Is there anything I can do, i really need to get this working.

  • 2 weeks later...
  • 1 month later...
okay so the iDeneb 1.6 install finished, and I am having the same problem. It freezes at the apple logo. How do I correct this problem..is it a hardware problem? i am using an AsRock Wolfdale 1333-D667 r 2.0 which IS on the compatibility list, but it says you need to have bios version 1.50 modified..and it has a downlaod link to a file that is a .50 file? I dont know that file extension and i Googled it, andnothing came up. I am running bios 1.50 from AsRock right now.

 

 

 

Is there anything I can do, i really need to get this working.

 

OK, So I have the same problem with this mobo . Ditto problem as yours. And the .50 file extension for the BIOS modded or otherwise is puzzling me no end. How do we flash the BIOS with a .50 file extension. AFUDOS says it can;t read the rom file.

 

 

 

Please help somebody.

  • 3 weeks later...
×
×
  • Create New...