Jump to content

alidarbac

Members
  • Content count

    6
  • Joined

  • Last visited

About alidarbac

  • Rank
    InsanelyMac Protégé
  1. 10.6.2 Released!

    I ended up fixing it by installing PCEFI 10.5 to my softraid and replacing sleepenabler and nullcpupowermanagement from netkas's site. I had a similar experience with random kexts that I didn't install myself. Did you once have a Leopard install with dsmos.kext? If you did and used Migration Assistant to copy it over, it'll copy over any non-vanilla stuff in your /S/L/E
  2. 10.6.2 Released!

    I'm having the same exact problem as you are (instant KP upon boot). Booting in verbose doesn't seem to indicate anything about any kext problems, only some gibberish about panic(cpu 0, caller)... and a bunch of hex strings. Also, I can boot normally when I plug in my back-up 10.6.1 install on my USB. When I boot successfully and check Console, I notice that it seems to be loading Darwin Kernel 10.0.0 from the back-up and doesn't try to load Darwin kernel 10.2.0. I thought I had a pretty vanilla install (did blackosx's method on a EP45-DS3L with Q6600) except two minor differences. - I installed with PCEFI 10.1 and never bothered to update it. Moreover, I manually edited the CPU information as per aquamac's guide here (this was before PCEFI 10.5 came out.) After the update to 10.6.2, I noticed the file that I modified to put in the CPU info looked like it reverted, but About this Mac still shows the string that I entered. So perhaps somewhere this CPU string is messing with the kernel? - After getting my vanilla install up, I moved it over to a 2-disk software RAID. Maybe there's something about this softraid that's screwing it up. Also, my Vmware 3.0, which worked perfectly in 64-bit mode, gives me an instant KP upon trying to launch a vm. I'm thinking of reinstalling on another drive, this time using PCEFI 10.5 to autodetect the CPU and not mess with the About this Mac string.
  3. This was the method that eventually got me sound. I installed SL as vanilla as I could on a new drive. The DSDT.aml I originally built was fine, but I had the wrong LegacyHDA in my /E/E. The first step that I did to try to get sound working was what I used to do in Leopard when sound stopped working after a system update: re-apply the Tauruga patch. Not only didn't it work, I think it also borked my vanilla AppleHDA so that every other method in this thread couldn't work either. I spent days building and rebuilding my DSDT.aml (hint: from what I can tell, if your audio hardware is showing up in System Profiler but no input or output devices are showing up in Audio MIDI Setup, your DSDT.aml is fine and it's a kext problem), trying VoodooHDA and all the other legacy kexts in this thread and nothing worked. I finally thought screw it and completely re-installed SL. The first thing I did was to try another LegacyHDA in my /E/E and it worked right off the bat. So the moral of the story is not to use the Tauruga patch in SL and nuke your install if you still can't solve your problem.
  4. I ended up fixing this problem. Before installing SL, I was running a Leopard install with a bunch of the kexts (Disabler.kext, JMicronATA.kext, etc.) directly in /S/L/E. After installing SL on another drive, I used the Migration Assistant utility to copy my data over and that copied all those old custom kexts over into my SL's /S/L/E. It was one of those kexts that were preventing me from booting in 32-bit mode; I could boot in 64-bit mode just fine since the system recognized them as not being compatible with the 64-bit kernel and didn't even try to load them. After deleting (after backing up) all the kexts that my Console said wouldn't load in 64-bit mode and rebuilding Extensions.mkext, I was able to reboot in 32-bit mode fine.
  5. Just wanted to say that I'm having the SAME exact problem. I installed on a EP45-DS3L with a nVidia 9400 exactly per this guide. I swear that I was able to boot -v -x32 when I first installed 10.6, but after I installed and re-installed a bunch of things (I'm thinking possible culprits are the Developer's tools or Vmware Fusion 2), I couldn't boot into -x32. When I boot 64-bit mode in verbose, I see that same exact message about AppleIntelCPUManagement timing out but it boots up fine anyway. I only care about booting 32-bit mode so that I can run Vmware and from what I can tell Vmware Fusion 3, which comes out in October, works in 64-bit mode. But there's something nagging me about my otherwise perfect vanilla set-up.
  6. I have a EP45-DS3L and I was able to get ls8's guide here (http://forum.insanelymac.com/index.php?showtopic=77165) working pretty easily even though that guide says it's for P35-DS4. Installed using a 10.5 retail DVD, upgraded to 10.5.5 with the combo updater, and then added audio and graphics by searching here for drivers. The hardest thing for me was generating a working EFI string for my nVidia 9400 GT, which isn't supported by EFIStudio.
×