Jump to content
Welcome to InsanelyMac Forum

Register now to gain access to all of our features. Once registered and logged in, you will be able to contribute to this site by submitting your own content or replying to existing content. You'll be able to customize your profile, receive reputation points as a reward for submitting content, while also communicating with other members via your own private inbox, plus much more! This message will be removed once you have signed in.


  • Content count

  • Joined

  • Last visited

About jgauthier

  • Rank
    InsanelyMac Protégé
  1. Mountain Lion - Dell e6510 - couple issues

    I'll take a look at patching AppleHDA. I realized that I have alerts, but no other sounds play (ie music). I don't really understand why.. audio is audio.
  2. Mountain Lion - Dell e6510 - couple issues

    I got sound working... I outlined what I did, but mysteriously not that much, in my two updates! Would there be any gain in dumping the codes, pci, and DSDT now? I 'll certainly do it, and appreciate the help!
  3. Mountain Lion - Dell e6510 - couple issues

    Well, that's frustrating. I've been doing a fair amount of reading, but not really anywhere. I stumbled into this thread: http://forum.osxlatitude.com/index.php?/topic/1617-mountain-lion-anyone/ and this one: http://forum.osxlatitude.com/index.php?/topic/1100-dell-e64006500-research-thread/?hl=6500 I grabbed the kext for the wireless and installed it with kextutility, then I reinstalled the voodoohda package. I rebooted, and I have an audio, icon and some sounds! volume doesn't work, but eh. On to the restart issue!
  4. Mountain Lion - Dell e6510 - couple issues

    Audio> So, I downloaded the voodooHDA package (2.8.4) and installed it. I went into pfino.list and changed the Vendor and Device ID based on this reading: http://www.insanelymac.com/forum/topic/267905-voodoohda-common-problems/ I rebooted, and the control panel still tells me "No voodooHDA devices." I also used DSDT editor to extract my DSDT and saved it into /Extra. I haven't done any patching yet, as i'm not sure how. Still chugging on these.
  5. Mountain Lion - Dell e6510 - couple issues

    My other post was actually completely different. Mac OSX 10.8.5 won't work on this system. My other post was uncovering that. It won't get beyond the "waiting on root device". This thread is still applicable. I have re-installed and have updated to 10.8.4. So, I'm back at it these 3 problems now. I did try voodooHDA for sound. I had mixed results. in one scenario, my first install it would not load, and the control panel would say there were no devices. In another install, It loaded, the control panel worked, but after rebooting I suffered from a Kernel Panic. I have tried to remove hibernate. (pmset0-a hibernatemode 0). every time I step away the dang thing is "off" and unwakeable. So, I am back at these three issues, and I have given up on 10.8.5 for now. I would like to spend more time using this system than trying to get it to work! haha
  6. Mountain Lion - Dell e6510 - couple issues

    I used a guide similar to that, but I will go ahead and reinstall. The OS seems to be nearly non-functional now, anyway! I will report back in a few hours (or more!)
  7. Not booting... sometimes?

    I upgraded from 10.8.2 to 10.8.5 (app store) last night, and since my Dell e6510 would not boot. I discovered the cause was the "npci=0x02000" flag. Once I was able to supply boot flags I removed it, and it stopped hanging at the PCI scan. All was well, so I thought. I got up this morning, to a machine that won't wake from sleep (I think.. not important right now) and when I boot it, it just sits at "No interncal dound for . using 8000000", which is the last thing I see. However, a few lines up I see it's most likely waiting for the root device. Waiting on ... boot-uuid-media The crazy thing is, I can get it to boot sometimes. I'm not sure yet HOW I've done it. I keep trying a mixture of flags, coupled with peripherals in and out (usb mouse/keyboard). I will get it to boot, then reboot and it will revert back to this scenario. I have tried many boot flag combination with PCIRootUID, and always boot with -v. I don't seem to be able to make any headway into the scenario in which it does boot successfully. Any tips? ----------------------------------------- Update: Well, I reinstalled. Everything was working. I ran through software updates to which it reported "None of the selected software was able to be installed." Upon rebooting, I am waiting for the root device again. Puzzling. ------------------------------------------ Another Update: I reinstalled again. I applied the update for 10.8.5. This is definitely related to the upgrade to 10.8.5. Maybe I shouldn't do it, but I hate having updates that I cannot apply I am still trying to figure out if I can get passed the root device issue. I'm reading through this: http://www.insanelymac.com/forum/topic/278075-about-still-waiting-for-root-device/ But haven't figured out what do yet. ------------------------------------------------- Update: I stumbled into this interesting tidbit: http://www.insanelymac.com/forum/topic/291822-1085-out/page-5 I went ahead and pulled the kexts mentioned from 10.8.2. That did not help. I removed npci=0x2000 from the kernel options. 10.8.5 really doesn't like that, and hangs at PCI configuration (it doesn't like 0x3000 either) I booted with -v -x and it's sitting at PCI configuration. There seems to be no winning this war Perhaps I need to stick with 10.8.2 for the time being.
  8. Greetings! I've installed iAtkos Mountain Lion on a Dell e6510. Things are going pretty well. I have three annoying issues I would love to get some help with. I'm pretty new at all this, so I might have missed some things. 1) No Audio. This has an IDT 92HDxxx chip in it. I've done a ton of reading, but I can't seem to get anything to work. 2) The system will not reboot. When it gets to that point it just stops. I read somewhere that this happens when you don't have a DSDT or you need to use EvOreBoot. Neither seems to work. I used DSDT Editor and extracted the DSDT. I applied a patch a found somewhere on the internet for an e6510. 3) After I come back to the system for awhile it's dark and non-responsive. I am assuming this is power saving. I have no problem disabling this. I would really like to get 1) and 2) resolved to make this more useful. Thanks very much!