Contribute
Register

Acer Aspire V Nitro VN7-591G Issues

Joined
Dec 11, 2011
Messages
168
Motherboard
HP ProBook 4440s-Clover
CPU
i5-3360M
Graphics
HD 4000, 1366x768
Classic Mac
iMac, Power Mac
Mobile Phone
Android, iOS
So I got a hold of a VN7-591G Acer Aspire V Nitro laptop and so far got everything working except proper Power Management and sleep.

Currently macOS is using Power Management using the X86PlatformPlugin.kext instead of AppleIntelCPUPowerManagement.kext, but I read that it's because of the Haswell architecture. Currently here is what works:
  • Native Power Management via X86PlatformPlugin
    • CPU clocks down to 800MHz, and turbos up to 3.6GHz as expected
    • nVidia GPU properly disabled via SSDT patching
    • iGPU Power Management - Unsure if this is fully functional or not, as it is reported that it should clock down to 200MHz and it does not.
      • Lowest Clock: 750MHz
      • Highest Clock: 1.2GHz (Turbo Frequency)
  • Brightness control
  • Audio (via AppleALC and CodecCommander)
    • Unsure if headphone jack works, mainly use Bluetooth headphones so not my concern
  • Ethernet
  • ACPI Battery
  • Webcam
  • Sleep (partial)
  • Touchpad
    • No multi-gesture
    • Only single-tap for primary click works
    • No scrolling gesture
  • Keyboard
What doesn't work or I have not tested:
  • HDMI
  • Sleep (see below)
  • Built-in Microphone
  • Wifi (Atheros chipset currently, and not my primary concern)
  • Bluetooth
Sleep currently works, but whenever it comes out of sleep, power management glitches and the CPU runs at maximum power (and only partially throttles down), and currently the TouchPad does not re-enable on some occasions, and I have not been able to replicate why, and so far it is random.

Here is my problem reporting files
 

Attachments

Last edited:
Joined
Dec 11, 2011
Messages
168
Motherboard
HP ProBook 4440s-Clover
CPU
i5-3360M
Graphics
HD 4000, 1366x768
Classic Mac
iMac, Power Mac
Mobile Phone
Android, iOS
Anyone have any ideas? Still have Power Management issues, and even looked into _OSI calls in SSDT but unable to tell if I missed anything or not.
 
Top