bobdamnit

Sweet. Thanks Bronx. As an update, I managed to get this 3520 up and running OS X 10.8. Its dirty, but so far its working. No DSDT. I'm planning on pulling out the DSDT and using a generic patcher just so I have one. I'm hoping this will help me from needing a graphics fix in /Extra. But QE/CI works. So does HDMA out. Sound is working good with VoodooHDA 2.7.3. Anything higher breaks audio. Wifi/webcam were both supported out of the box, but wifi/bluetooth card doesn't work in 64-bit. Touchpad is an ALPS pad with extended gesture support in Windows. (Three-finger flick for back/forward, two-finger scroll, pinch to zoom, etc...) I can get none to work in OS X, but I haven't really tried that hard yet. Some of these I got from source. Some from various random hackintosh communities. Will keep tweaking and eventually release an /Extra that has been slimmed down as much as I can and see if it helps anyone else out.

Also, using newest EDP I cannot toggle hibernation/sleep. Option is there, but it just keeps refreshing a blank screen. Command using pmset to disable works just fine. (Allows "Sleepless" to function as properly as I can make it operate.)

I have looked into that. Most of the time, artifacts are experienced. I know the GMA 950 (What I am used to) also had artifacts, so that really isn't a big deal. But a lot of users are reporting heavy artifacts. (Screen unusable.) I'd like to avoid this. Graphics and audio are the only thing stopping me from doing OS X on this machine. I'm not exactly sure how Intel audio works with OS X. I have heard that Maverick's is supposed to support the Intel HD 3000. Not sure if thats a DP, or includes native support. I'm hoping for native, as that would only mean that I have to inject ID's. Herve is saying that its supported natively with correct DSDT patches in previous OS X builds, but I've never been a DSDT person. Don't have any inclination to try either. Nor do I know which "patches" that includes. (For those of you willing, I will definitely give stock DSDT.aml file!) I'm relatively positive that I can get OS X running on this machine. I'm also fairly positive that I can get 90% of this machine working just fine with OS X. My only concerns are the audio card and the graphics card. If I can get this supported, fully, can we submit this to EDP? I'm willing to go as far as possible to get this machine supported with EDP and fully documented. But I need some help. I can't do DSDT modifications. I need someone for that. (Don't know or care who, all I can do is use a default patcher to boot with DSDT. Example: DSDT patcher.) I do know that the Vostro 2520/2420 are almost identical with slight version changes. (Both have i3, both have the same Wifi, both have same sound, as well as chipset.) But neither are very supported in OS X. I'd like to get these machine supported by OSXLatitude.

D520 is running smooth. If I use Joe's DSDT with the VGA out fix, its almost perfect. Sleep/Hibernation works. Display won't wake up after sleep/hibernation, even with a hotcorner display sleep setting. However, tapping "Enter" seems to wake the display back up. Still see "Refusing" errors after running EDP, but they don't seem to make any difference. They are all kexts I know to be running. Not a big deal. All in all, a decent running D520.

Ouch. I've never been any good at DSDT.

Ok, so then I'll start with a myHack generic just to give it a shot. I've already got a Lion boot stick made, so I'll just stick with that and the generic /extra. I'm pretty confident that will at least get me booted. I was looking at the boot packs, and none of them seem to support the Intel HD 3000. A cursory Google search shows that most users are able to get it to work, but with random success as to how much artifacting is shown and what resolution you end up with. Haven't looked into the Intel audio. Wifi is the 1704 Wifi+Bluetooth Here are the specs of mine, in case it helps: http://en.community.dell.com/cfs-file.ashx/__key/communityserver-discussions-components-files/3518/5707.info.jpg An extremely similar model to mine: Vostro 2520 (Can't get anything from Google about OS X on this machine either.)

I have a similar model. Its a 3520. Specs are: Core i3 2.4Ghz 8Gb DDR 3 Intel HD 3000 (Dont see this anywhere in the boot packs, sadly) Intel audio Going to try getting something going on this machine. Anything out of other machine boot packs I can use?

Seems to be working fine on my old D520. Using the D520 as a refresher to get my new Dell Inspiron 3520 running anything lol.

All of this happens after I install EDP. Updating Chameleon doesnt help, so I reinstalled EVERYTHING and left it at EDP Chameleon. Problem is consistent. As soon as I install EDP, I lose the ability to shutdown, I get those "Refusing" errors, and sleep stops working. As soon as the machine goes to sleep, it wakes back up. Immediately! It doesn't really matter. I've got Slackware up and running perfectly and have no ambition to put OS X back on it.

Neither worked, and this stupid fucking operating system has got me furious. I'm blowing away OS X and just putting Linux on the machine. Its been a great run guys, but I'm done fucking with shit that doesn't work. (Or that I have to configure insanely hard to make work.) Toodles.

Ok, whats the deal? Restart works great, but shutdown doesn't work at all. I've tried different DSDT's (joe82's and EDP's) and both operate the exact same. Then I grabbed Chameleon Wizard and made sure that "Restart Fix" was checked. (It was.) That didn't help any at all, and removing "Restart Fix" from Chameleon Wizard made the system not able to restart properly. So I removed SleepEnabler and NullCPU, no help and now the system won't sleep at all. (I expected this.) I guess I'm going to look into EvoReboot or OpenHaltRestart. I just don't know what else to do.

Definitely reproducible. I never see these "Refusing" errors until EDP is installed and ran to configure my machine. I skipped work today because my kid has pneumonia, and in between taking care of her I've reinstalled 3 times and can always reproduce these errors after EDP is installed and configured. What I don't understand is that its refusing most of my kexts in /Extra/Extensions, however upon OS X booting, I find that they've all loaded just fine. Interestingly enough, its not refusing I8k.kext or the patched AppleHDA.kext that is also in /Extra/Extensions. Also, once EDP is installed and configured I lose the ability to shut down. The OS shuts off, however the machine does not. The power LED stays lit, the fans spin at full blast and it never shuts off. Don't know whats up, but I can reproduce this error consistently after EDP is installed as well. As for the constant verbose booting... Well, stupid me didn't realize Chameleon remembers your last boot option, so if you boot verbose, it will remember that until you boot to Chameleon and remove the last typed boot flag.

You can try downloading the Broadcom43XXFamilyRev2.kext from the D520 guide I wrote up. Its in the D5X0 sub forum. If you try it, be sure to remove IO80211Family.kext from /System/Library/Extensions and install Broadcom43XXFamilyRev2.kext into /System/Library/Extensions.

The DW1390 is a 4311 card, and should be supported natively in Mountain Lion. Not sure why its not picking up. Have you looked in System Preferences>Networking and tried to create a new location?

Mouse shouldn't lag when you install if you are using the proper boot pack.

What WiFi card? Broadcom 4311, 4312, 4315, etc... Some Broadcom cards require you to remove IO80211Family.kext and install Broadcom43XXFamilyRev2.kext instead into /System/Library/Extensions. Alternatively, you can remove 80211Family.kext from /System/Library/Extensions and move IONetworkingFamily.kext into /Extra/Extensions and then instal Broadcom43XXFamilyRev2.kext into /Extra/Extensions and it will work the exact same.

Ok, the "refuse" errors came back, and are as follows (Seen in console): 1/27/13 7:06:36.000 PM kernel: Refusing new kext com.kext.HDAEnabler, v1.0d1: already have prelinked v1111.0. 1/27/13 7:06:36.000 PM kernel: Refusing new kext com.apple.driver.AppleSmartBatteryManager, v161.0: already have prelinked v1111.0. 1/27/13 7:06:36.000 PM kernel: Refusing new kext com.apple.driver.AppleRTC, v1.5: already have prelinked v1111.0. 1/27/13 7:06:36.000 PM kernel: Refusing new kext com.apple.driver.AppleIntelIntegratedFramebuffer, v7.0.4: already have prelinked v1111.0. 1/27/13 7:06:36.000 PM kernel: Refusing new kext com.apple.driver.AppleACPIPlatform, v1.3.5: already have prelinked v1111.0. 1/27/13 7:06:36.000 PM kernel: Refusing new kext com.apple.driver.AppleACPIButtons, v1.3.5: already have prelinked v1111.0. 1/27/13 7:06:36.000 PM kernel: Refusing new kext com.apple.driver.AppleACPIEC, v1.3.5: already have prelinked v1111.0. 1/27/13 7:06:36.000 PM kernel: Refusing new kext com.yourcompany.driver.AppleACPIPS2Nub, v1.0d1: already have prelinked v1111.0. 1/27/13 7:06:36.000 PM kernel: Refusing new kext com.apple.driver.AppleBCM440XEthernet, v1.2: already have prelinked v1111.0. 1/27/13 7:06:36.000 PM kernel: Refusing new kext com.apple.driver.ApplePS2Controller, v1.1.5: already have prelinked v1111.0. 1/27/13 7:06:36.000 PM kernel: Refusing new kext com.Apple.driver.PS2Keyboard, v1.1: already have prelinked v1111.0. 1/27/13 7:06:36.000 PM kernel: Refusing new kext org.voodoo.driver.PS2Trackpad, v1.1: already have prelinked v1111.0. 1/27/13 7:06:36.000 PM kernel: Refusing new kext com.apple.driver.AppleSmartBatteryManager, v1.29.1: already have prelinked v1111.0. 1/27/13 7:06:36.000 PM kernel: Refusing new kext org.netkas.FakeSMC, v4.2: already have prelinked v1111.0. 1/27/13 7:06:36.000 PM kernel: Refusing new kext org.mozodojo.IntelCPUMonitor, v1.0.1: already have prelinked v1111.0. 1/27/13 7:06:36.000 PM kernel: Refusing new kext org.tgwbd.driver.NullCPUPowerManagement, v1.0d2: already have prelinked v1111.0. 1/27/13 7:06:36.000 PM kernel: Refusing new kext com.apple.driver.AppleRTC, v9.9: already have prelinked v1111.0. 1/27/13 7:06:36.000 PM kernel: Refusing new kext sk.triaxis.kext.SleepEnabler, v1.0: already have prelinked v1111.0. 1/27/13 7:06:36.000 PM kernel: Refusing new kext org.voodoo.driver.VoodooTSCSync, v1.1: already have prelinked v1111.0. Also, it seems as though every time I boot verbose through Chameleon, it boots verbose every time after that. I can fix this by reinstalling a previous version of Chameleon and removing FileNVRam from /Extra/modules. I'm calling this a Chameleon problem, and don't think the latest EDP is at fault. (I don't use the app the new Chameleon fixes anyway, so I'm not too worried about it right now.) Anyone have any ideas?

Got it all sorted. Blew away the Windows, myHack installer, and OS X partition. Then I grabbed a flash drive and recreated the myHack installer. Install went great. After that, I deleted IO80211Family.kext and used Kext Wizard to install the Broadcom43XXFamilyRev2.kext. Then I ran myFix-Full and rebooted. Sure enough, WiFi came up and was "not configured". But this time, I could configure it in System Preferences. Then I ran EDP and rebooted. I got a bunch of "refuse" lines while it was loading /Extra kexts, but nothing seems to be wrong when it boots. So I updated to 10.7.5 and re-ran EDP. After a reboot, the "refuse" lines pertaining to /Extra kexts do not come back. Booting now works awesome. It appears as though EDP hasn't been updated to the "mirror fix" DSDT for the D520, so VGA mirroring doesn't work but extended mode does. As such, when the display goes to sleep, it comes back "pixelated". If your display has the same problem after ONLY the display goes to sleep and you wake it back up, I'm attaching user "Joe82" modified DSDT that fixes both "pixelation" and mirroring. dsdt_d520_gma_md2.tar.gz

Thats what I was afraid of. Thanks Herve. I'll keep diggin at it.

Might this explain why my D520 boots verbose, even though its not set to boot verbose in the Chameleon plist? Its also refusing all kexts in /Extra.

I'd try re-running EDP and choosing another PS/2 option before I reinstalled OS X.

Support for your setup ceased to exist when you typed "unifail" We do not support unifail here. Support for unifail can be found at the unifail website: http://www.tonycrapx86.com/forum.php If you'd like to create a myHack USB installer and follow the EDP method, then we can help you. Until then, good luck!

Newest version doesn't work with GUI. Works great with pre-defined values in plist. Would be excellent if original GUI could be reworked to work, or if we could find a way to make it work with Some other fan control app.

I loaned my D50 to my sister for a few weeks. Because she had never used OS X, I blew away that partition and left Windows alone. No big deal, I can (and probably needed to) reinstall simply enough. So, I reinstall 10.7. Installer was on my hard drive, and had been left untouched. Chameleon was still on the machine, and was initializing Windows with no problem. So I could make Chameleon load the myHack installer that was on its own partition on the hard drive no problem. And it went great. 10.7 installed just fine, or so I thought. I'm not sure whats up, but I cannot get the DW1395 to recognize. It shows up in System Profiler and also shows up in LSPCI. The Airport icon shows up in the Finder menu bar, however it just says "Airport not configured". So I made sure that the Bcm4311 kext had my device/vendor ID's. It did. So, on a different computer, I grabbed KextWizard and the BCM43XXFamilyRev2 and installed the kext into /S/L/E like you are supposed to. Ran a full myHack and rebooted. Same "Airport not configured". Cant run EDP without internet. The only spare (non-USB) card I have is an Intel Pro card. I'll keep digging and post what I find to be a definitive answer to this. On a much happier note, I did find a guaranteed way to bypass the Setup Assistant needing a keyboard. I know. If you plug in a USB keyboard, it somehow makes the internal keyboard work. But I don't have one of those anymore. (Thanks kids!) I couldn't make "USBBusFix=No" work. I was getting pretty frustrated. After some digging, I find that if you disable the hardware check for Setup Assistant, the keyboard actually works but for some reason Setup Assistant just doesn't want to use it. I'm pretty sure Setup Assistant knows the PS/2 keyboard is there and that it works, but it wants a USB keyboard. Disabling the hardware check will force the PS/2 keyboard to be used. To disable Setup Assistant's hardware check, do the following... Reboot into single user mode (-s) and at the prompt, run the following commands fsck -fy mount -uw / nano /System/Library/CoreServices/Setup\ Assistant.app/Contents/Info.plist When that file opens, use the arrow keys to scroll (it scrolls half pages at a time!) down until you find the following lines: <string>DeviceSection</string> <string>KeyboardTypeSection</string> Remove those lines. Hit Control+O to write out the file. It will ask you if you are sure and if you would like to change the file name. Tap enter to tell it to save with the same name. Then hit Control+X at the same time to close Nano. Back at the single user prompt, type the following to reboot: reboot now This should bring Setup Assistant back up, without the keyboard check. The keyboard should work perfectly after this.

Have you set a "Master Password" in BIOS? Did you perform the "Fix Sleep" fix in EDP?