Jump to content

Red Five

  • Content Count

  • Joined

  • Last visited

About Red Five

  • Rank
    InsanelyMac Protégé

Contact Methods

  • ICQ
  • Skype

Profile Information

  • Gender
  • Location
    Tri Cities, TN
  1. Red Five

    Patching DSDT for HP Elitebook 8540w

    I know this thread is at least 5 years old, but I have the same configuration as kossak: 8540p, i7 620m dual-core, 4GB RAM, and NVidia NVS 5100M, and the latest BIOS which I think is F.60 at this point. I'm running El Capitan pretty successfully (had several growing pains, but got it to install finally). Here's what works: Audio (using VoodooHDA 2.8.4 with a couple tweaks to its plist file to enable volume and mute controls) Clover bootloader (v3438), injecting several kexts and NVidia driver (I've tried the web driver several times, boots to a KP and immediately reboots) VoodooPS2Controller.kext: keyboard and trackpad work great, with 2-finger scroll and taps. I can even use the Trackpad prefpane to adjust most things. The capacitive mute and volume controls even work, as does the WiFi switch. USB2.0: Needed a minor tweak to replace the DSDT reference to the internal USB2 channel. DSDT presents it as ECHI, it needs to change to ECH1. I think GenericUSBXHCI.kext can handle that. USB3.0 seems to be detected, and I think I can use the ports on my docking station, but the internal ports on the right are dead (but they were dead in Windows, too; I think a picofuse blew in the internal USB3 hub) WiFi: Replaced the default WiFi card with an eBay HP Broadcom unit. I also had to inject ProBookARPT.kext via clover Webcam!! Yes, the internal USB webcam works! External displays (I think): had to tweak Clover config to add an NVCAP value and some other config strings. At the least I can now use AirPlay and AirParrot (for my Chromecast) What doesn't work: Sleep: goes to sleep and immediately reawakens, with some audio crackle just before sleep. Kbd and trackpad work perfectly fine, audio and everything else works perfectly fine after wake. Backlight brightness: Injected ACPIBrightness.kext. That makes the brightness fn keys trigger a response in the OS (brightness bezel/meter pops up on screen), but no actual brightness change Battery/charging status: I've tried injecting ACPIBattery, VoodooBattery, modified AppleBattery, and one other, and none of them work. They all cause the OS to recognize that a battery can be installed on the system, but none of them recognize the battery that is present nor indicate charging/AC or battery level. Installation was really odd. I built an El Capitan USB installer, modified it with Clover, and it would boot to the point where the kernel started looking for the main installer partition. Due to the DSDT presenting the internal USB2 hub as ECHI, install boot would die at that point. It might have worked with the internal USB3 ports, but mine are dead. I ended up using the USB3 ports on my dock station, no further boot issues and install worked fine. If I had known at that point about GenericUSBXHCI.kext, that might have allowed me to use the internal 2.0 ports for install, but it worked out OK. This laptop is sort of odd. It has 2 variations: mine is the dual-core model, with 2 RAM slots, and they have a quad-core variation with 4 RAM slots, 2 different motherboards. Both support i5/i7 and maybe i3, but the dual mobo won't support quad, and the quad mobo probably won't support the dual core CPU. The quad-core model does support at least 16GB RAM (possibly 32 with the right modules); the dual version might do 16GB with the right modules, but will definitely support 8GB. I would be interested in getting the list of "not working" items fixed, particularly sleep and battery. I've seen various things for the 8540w, including this very thread (and apparently p and w models only differ in the installed NVidia card), so maybe something here will work for me, too.
  2. I believe that the reason why the OS updates claim to have failed at the very end is due to one of the update steps. The way I figure it, the updater is trying to write some updates to OpenFirmware or PRAM, but neither of those things exist on a PC-based Hackintosh, so they return failures. The rest of the update consists of file and setting updates, and those are generally successful, which is why the update ultimately succeeds.