Jump to content

deeveedee

Members
  • Content Count

    17
  • Joined

  • Last visited

Community Reputation

0 Neutral

About deeveedee

  • Rank
    Private First Class
  1. I switched to this "Refined VoodooPS2Controller" from the "original." With the original kext, I was using SSDT-DisableTrackpadProbe.aml to disable search for the unused Synaptics and Sentelic devices. Does this "Refined" version also benefit from the SSDT-DisableTrackpadProbe.aml? EDIT: My Refined VoodooPS2Controller configuration on my E6410 is as follows: Kext release 5 VoodooPS2Controller.kext installed in CLOVER/kexts/other and /L/E with CLOVER > Inject Kexts > Detect CLOVER boot flag vps2_findmousedelay=500 (left over from original kext) SSDT-DisableTrackpadProbe.aml in CLOVER > ACPI > patched with only ALPS Glidepoint enabled (left over from original kext) Command and Option keys switched (System Preferences > Keyboard > Modifier Keys) (to compensate for key switch caused by the new kext)
  2. Using this VoodooPS2Controller.kext on my Latitude E6410 dual-booting High Sierra and Mojave. Outstanding!
  3. I traced the _PTS shutdown fix back to the beginning of Hackintosh time. I should have noticed that the same fix appears on my Thinkpad T61 (also running Mojave). The fix was only ever intended to be for shutdown (to be conditional on LEqual (Arg0, 0x05)). SLPE appears to be a register that controls NVidia dGPU and can be in one of two places on older laptops: On the Latitude E6410 (NVS 3100m): OperationRegion (PMRS, SystemIO, 0x0430, One) Field (PMRS, ByteAcc, NoLock, Preserve) { , 4, SLPE, 1 } On the Thinkpad T61 (NVS 140m) OperationRegion (PMRS, SystemIO, 0x1030, One) Field (PMRS, ByteAcc, NoLock, Preserve) { , 4, SLPE, 1 }
  4. @Hervé Thanks for your patience with me. My digging indicates that you are clearly one of the experts in this area. Do you know how the E6410 _PTS shutdown patch was discovered and do you know where I might look to learn more about it? Also, in this thread you don't reference the _PRW 0x0D patch. Do you stil believe that the _PRW 0x0D patch is necessary (I've implemented it, but not sure I did it correctly given that _PRW generates its returns with Method (GPRW). Thanks for any help / advice / insight.
  5. @Jake Lo Thanks for your help, but I'm reluctant to try your suggestion, because the _OFF and _ON methods work with registers/memory locations that are very different from the Latitude E6410 / 3100m. I did some digging and believe that @v3ct0r 's Yosemite thread was the first to implement the _PTS shutdown patch. If I can understand how this shutdown patch was determined, it would help. EDIT: @Hervé also provided this _PTS shutdown patch in this thread.
  6. @Jake Lo - Thank you for your reply. I will look at your solution before applying, since I can already see I need to make one change (PEG0 -> AGP in my DSDT). It will also help me to refine my AGP.VID._DSM. While I'm digesting your solution, do you know how duduclx came up with his _PTS shutdown fix? He identified a register (SLPE) which he defined as: OperationRegion (PMRS, SystemIO, 0x0430, One) Field (PMRS, ByteAcc, NoLock, Preserve) { , 4, SLPE, 1 } and then he set SLPE to Zero in _PTS Store (Zero, SLPE) I'm guessing that he found this in an SSDT from another system? It would help me to know how he discovered this, since I'd like to understand the solution in addition to implement it. Thank you.
  7. @Jake Lo - You suggested duduclx's _PTS patch for working sleep. It turns out that with a minor modification, his patch almost addresses shutdown and sleep. If I remove the conditional in _PTS (as shown below), the E6410 sleeps and then wakes immediately with a black screen. I suspect that duduclx's _PTS logic requires some minor modification and that the "inverse" logic is required in _WAK. Method (_PTS, 1, NotSerialized) { Store (Zero, SLPE) Sleep (0x10) }
  8. @Jake Lo This thread suggests that adding _OFF and _ON method calls was the trick to working sleep for another Dell Latitude. I couldn't find _OFF and _ON methods in DSDT or any SSDTs (nor could I find any analogous methods, but I don't know what I'm looking for). I'd be open to trying the _OFF / _ON trick if anyone can suggest how to find or create these methods.
  9. @Jake Lo If I should start a new thread for this, let me know. My system files are attached. Note some differences from other E6410 configs that you may have seen: LPCB._DSM patched with device-id "3b09" for native Nehalem power management with MacBookPro 6,2 ECDV renamed to EC so that AppleBusPowerController loads AGP.VID._DSM patched with device-id "0a29" so that AppleGraphicsPowerManagement loads No CLOVER option to Generate P or Generate C States (With the correct LPCB._DSM and MacBookPro 6,2, these CLOVER are NOT necessary for this architecture and only result in reduced number of P states and lower max multiplier). Note that sleep still doesn't work if Generate C and Generate P states is enabled in config.plist. EDIT: Added HDAU device to PCI0.AGP (device-id 0x0be3) which is not currently reflected in the attached debug files. Note that my DSDT patches include Rehabman's _PRW 0x0D patch suggested by @Hervé and duduclx's _PTS shutdown patch. Shutdown works great, but sleep does not. When attempting to sleep, screen goes black and system enters a frozen (still on) state that can only be recovered by forcing power-off with the power button. Also note that I started patching AGP.VID._DSM for backlight slider. The slider appears in Display Settings, but moving the slider doesn't change brightness. Will look at this again when I have time. debug_7519.zip
  10. @Jake Lo Thank you for the reply! duduclx's prepare-to-sleep patch resolves the shutdown problem (can't use CLOVER's on-the-fly shutdown patch), but it doesn't resolve sleep. I'd love to know how he figured out that patch. In that same thread on page 9, duduclx indicated that @Hervé recommended Rehabman's _PRW 0x0D patch, but I have not found that that changes my laptop behavior in any way (including sleep). Since the fix is intended to fix the instant wake problem, it just might work (if I can get my laptop to sleep ). I really appreciate your help / suggestions. Thank you! EDIT: I'm dual-booting the E6410 with High Sierra and Mojave. Sleep behavior is identical in both. Other than sleep, performance on this laptop is outstanding. Since my Mojave solution is based on DosDude's Mojave patcher (a solution I've found to be surprisingly controversial even though it works great), I'm doing all my testing in High Sierra.
  11. I know this is an old thread, but I'm trying to solve the same sleep problem on my Latitude E6410. Attempts to sleep result in black screen, but system is still on and can't wake back up. Must force shutdown by holding power button. My E6410 thread is here: https://www.insanelymac.com/forum/topic/339102-mojave-on-dell-latitude-e6410/
  12. I'm using DosDude's Mojave Patcher on 4 systems with Nvidia (non-metal) graphics and video is working perfectly on all with Mojave 10.14.5: Dell Latitude E6410 (Nvidia NVS 3100M), Thinkpad T61 (Nvidia NVS 140m), DIY Desktop Socket 1156 / (GeForce 9800GT), DIY Desktop Socket 775/771 (GeForce 8600GT). DosDude's patcher (currently using version 1.3.3) has extended the life of these old system. All running Xcode 10.2 and graphics acceleration works perfectly.
  13. For anyone installing Mojave on a system with previous generation Intel HD Graphics, this might give you some hope... I am installing Mojave on an old Biostar TH55HD (Socket 1156) with Intel I5-660 CPU (Clarkedale) and 8GB DDR3. I created a Mojave Installer USB and installed CLOVER Bootloader (Legacy) R4769. I extracted the DSDT (CLOVER F4) and performed minor edits to resolve compile errors. I then applied some very basic DSDT patches and saved the DSDT in the USB EFI/CLOVER/ACPI/patched folder. Without any kexts or CLOVER flags, Mojave recognized the I5-660 HD Graphics. My display resolution is 1280x1024. I plan to install a Radeon Graphics Card, but to get started, I am using the Intel HD Graphics on the I5-660.
×
×
  • Create New...