scram69

On 6/15/2024 at 9:43 PM, hidematu5310 said:

Update 3:

hibernatemode 3 battery drain test for 1 hour.

Set standbydelay to about 5 minutes(300).

100% -> 98%

 

Update 4:

Fixed a potential problem where trackpad would stop working after rebooting from Windows or after Wake.

 

Update 5:

probably fixed instant wake on AC

recommended to add darkwake=0

 

SSDT-S3_upd5.zip 819 B · 1 download

 

I tried the "update 5" SSDT, but would get a wake on AC that triggered the Dell Diagnostic menu to run a test on the hard drive, causing the fan to spin at full speed.

"Update 2" SSDT still works for hibernatemode 25 (direct to hibernate), but for hibernatemode 3, I get video glitches after S3 sleep.

Would it be possible for you to re-post update 3?  Thanks!

I did pmset restoredefaults again, and added your SSDT-S3 from the above post ("deepsleep_off").

I also disabled Low Power S0 Idle Capability in BIOS as you recommended:

>setup_var.efi 0x14 0x0 -n Setup

Using hibernatemode 25 the machine now hibernates with no battery discharge, and I can wake from the power button.

Thank you again for your work solving sleep for this model!

17 hours ago, hidematu5310 said:

S3,hibernatemode 3 is now tentatively functional.

If it does not work, try enabling S3 (Suspend to RAM) above.

Question: do you still have "Block Sleep" checked in BIOS?

I disabled RTC Memory Lock and CFG Lock using setup_var.efi (modGRUBshell is deprecated):

setup_var.efi 0x16 0x0 -n PchSetup

setup_var.efi 0x3E 0x0 -n CpuSetup

However, with "Block Sleep" checked, HibernationFixup.kext, Misc>Hibernatemode = NVRAM and pmset hibernatemode 25, the laptop still refuses to hibernate.

With "Block Sleep" unchecked, I get KP Sleep Wake Failure in EFI and the laptop reboots.

hidematu,

Thank you for posting this interesting update!

Were you following this page  describing fixing sleep on an XPS 9500?

It is not clear to me how to accomplish disabling RTC Memory Lock: "setup_var PchSetup 0x16 00 (RTC Memory Lock ->Disabled)"

Where do you enter this command?

Update: it looks like this tool may be useful

I followed the instructions here and downgraded the BIOS from 1.22 to 1.19.

I was still not able to get S3 sleep to work.

I also was unable to get hibernate to work using your pmset settings with HibernationFixup.kext.  I also tried various settings for Hibernatemode under Misc: NVRAM and Auto.

Choosing sleep from the apple menu turns the screen dark, but the battery continues to discharge.

Have you looked at downgrading the BIOS?

According to Dell, you cannot downgrade the BIOS to version 1.18.0 or earlier.

Thank you again for this useful information.

Were you following the instructions for setting ASPM from the OC-Little-Translated page?

Hi hidematu,

Earlier today I came across this post, which had unfortunately been placed in something called "The Archive", meaning I didn't find it in the regular form sections as I read through them two weeks ago.

Like you indicate above, this poster (Eddar_Stark) (first of his name?) had also enabled "Disable Sleep" in BIOS, by which I took to mean "Block Sleep".

Checking "Block Sleep" in the BIOS is what finally un-Blocked sleep on this Latitude.  A bit counter-intuitive for me...

Your posts on the trackpad and brightness fixes for the 5310 were incredibly helpful - thank you!

I notice you are using hibernatemode=3, but you don't have the hbfx-ahbm boot arg set to enable the HibernationFixup.kext.  Are you getting your 5310 to achieve native hibernation?

Also, I would be very interested in what the following boot args you are using are for:

-noht40

io80211.awdl=0

-nvmefaspm

Thanks again!

Since there was no dedicated guide for the 5310, I took bios settings from this post.

USB Wake support is disabled.

In the later BIOS versions, there is no longer a Legacy ROM option in the boot section.

Additionally, I have disabled "Trusted Platform Management"

I've tried a number of Whatevergreen boot args without any success fixing the problem, but everything I read points to "Sleep Wake Failure in EFI" being an issue with CPU power management.

I've also tried alternate SMBIOS (16,1 and 16,2) but neither fixed the problem.  Another poster (hidematu5310) seems to have sleep working on his 5310 with 16,3.

At this point I'm really at a loss...

Specs:

Core i5-10310U

UHD 620

13.3 FHD

16GB RAM

Intel AX201

ALC295/ALC3254

macOS Ventura 13.6.6

Opencore 0.99

I believe I have everything working on this laptop except sleep.  I mostly followed the opencore guide, and used the files helpfully provided in hidematu5310's post for the trackpad, which is working fine.

Unfortunately, the laptop KPs when I try to get it to sleep.

In troubleshooting this Sleep problem, I have tried:

-setting the pmset variables per Dortania's guide

-removing and renaming hibernate file to /dev/null

-re-did the usb mapping using corpnewt's USBMap, and verified in IOReg explorer that the designated ports had the correct comments, and the unused ports are gone

-verified Power Management is working (X86PlatformPlugin attached)

-double checked GPRW patch applied (although this issue isn't instant wake)

-built SSDT-PLUG manually

-built SSDT-AWAC-DISABLE manually

-tried CPUFriend/CPUFriendDataProvider per Dortania's guide

None of these have resolved the KP.

I would very much appreciate any suggestions.  I've attached my OC folder (kexts removed)-

OC.zip

Instead of Voodoo, try the ApplePS2 kext that is also in Jake's EFI.  You will need to disable Voodoo in the config.plist and add in entries for ApplePS2.  Don't forget to add an entry for AppleACPIPS2Nub.kext.

Herve,

Thanks for the update.  I do like the convenience of all the peripherals connected via the dock.  However, with the e7270 there is plenty of room behind the laptop when it is connected in the PR02X/3X.  So I have ended up using the DP on the dock connected to one monitor (con2) together with an HDMI cable from the 2nd monitor directly connected to the laptop while still in the dock (con1).  It's a compromise that minimizes the number of cables that need to be disconnected/reconnected when I move away from the desk.

On 5/10/2021 at 6:25 AM, Hervé said:

I don't know what you meant by "adding an additional port/busID (0306) to both con1 (results in kernel panic) or con2 (nothing happens)", probably just an error of vocabulary because you cannot add anything to con1 or con2, you can only change their settings

I was referring to the example in dortania's OpenCore guide for the IvyBridge Laptop config.plist, where he adds 0304 and 0406 entries to the "alldata" entry for 0205 for framebuffer 04006601.

Unfortunately I had no luck with either method you suggested (adding con3 to 0x19160000 or booting with 0x193B0005).  Either way, I could only get the 2nd DVI port to act as a mirror of the first.  For either attempt Hackintool also reported only the two external connectors - con1 and con2, never a con3.

So I will try your other suggestion and see if I can scrounge up a monitor that still has a VGA port.

Right, then starting with those files, including the Intel wifi kexts and modified config.plist, you can follow the procedure here to update the EFI from 0.6.8 to 0.6.9.

You can try using the EFI from Jake Lo's guide (0.6.8) along with the intel wifi kexts from this post.

I am attempting to patch the Whatevergreen Framebuffer for my E7270 (Skylake, 0x19160000) in BigSur/Opencore to support both DVI connectors on the E-port plus PR02X dock.

I have tried to follow Herve's example for the same dock, but his post is for Haswell under HighSierra/Clover.

The default for this Framebuffer has the internal display as con0 on busID 00, a DP connector as con1 on busID 05, and a DP connector as con2 on busID 04.

Jake Lo's config.plist for the e7270 changes the display type from DP to HDMI for con1, enabling the HDMI connector on the laptop itself.

The problem is that either DP on the dock shows up as busID 04; plugging DP monitors into both dock ports will not get two separate displays, only one display that is mirrored.

As Herve did in his post, I tried adding an additional port/busID (0306) to both con1 (results in kernel panic) or con2 (nothing happens).  I tried changing con1 back to DP, but that still did not enable the 2nd dock DP as a separate display.

Has anyone been successful in enabling both dock DP ports as separate displays under OpenCore?

All,

I see this question raised a lot in various OSXL forums, so I thought I would add my experience.  I just successfully set up my Latitude E7270 to dual boot Windows 10 and Big Sur partitions on the same drive under OpenCore 0.68.

The original guide is from a post on reddit (Credit: u/junkieslip_6).

Then, there is a very good you tube video that walks you through the steps from that guide.

Two important notes:

-It took me a few tries in Disk Utility to make sure I had a separate NTFS partition for Windows, and not another Volume in the same APFS container for MacOS

-I needed to make my Windows 10 install USB using Rufus on a Windows 10 machine (neither Win 7 nor Linux/gparted worked for me)

...well three important notes:

-there is a typo in the text instructions under the video on the you tube pages: "partition efi size=100" should be "create partition efi size=100"

Hope this helps-

Sorry - my mistake.  I misread the BIOS version; my E6340 is at A24.

Could using MBP11,1 instead of an ivy bridge ID may be causing the boot-to-sleep issue?

If I revert to 10,2, do I need to generate new serial numbers/UUID's etc in order for Messages to work?

Specs:

BIOS: ver A22

CPU: i5-3340M @ 2.7 GHz

RAM: 6BG 1600MHz DDR3

Graphics: HD 4000 1366x768

Catalina 10.15.7

Attached is the EFI.  The SSDT-PM.aml comes from running ssdtPRGen.sh on this laptop.

However, the config uses MacBookPro11,1 as that was what Jake Lo had used in his config.plist (presumably for Big Sur compatibility).  That generates a mis-match warning when ssdtPRGen.sh is run, but the script still generates the aml file.

EFI.zip

My E6430 runs Catalina 10.15.7 on OC 0.6.3.  The built-in display goes dark following the apple logo on boot, and eventually the machine goes to sleep.  Once I wake it from sleep by pressing the power button, everything seems to work fine.  I have tried both the E6430 low-res DSDT posted here by Jake Lo as well as the one posted by Herve in this thread. Both give the same results.

I have found that if I boot in the dock (Dell port replicator) with an external display connected, the machine boots fine and the display stays on.

An update - 

I did the Hackintool/USBInjectAll.kext thing to generate a new USBPorts.kext as well as the SSDT-UIAC.aml and SSDT-EC-USBX.aml.

I removed what you had and installed those into OC/Kexts and config.plist.  Unfortunately, that didn't help.

However, I found others with the same "sleep wake failure" issue fixed the problem by disabling the serial port in the BIOS.  This seems to be working for my E6430 as well.

Hope this helps anyone else who runs into this issue-

OK - I tried that, and reset NVRAM.  Unfortunately the issue persists.

Should I try and create my own USBPorts.kext using Hackintool with the laptop in the dock and use that to replace USBInjectAll.kext?

I am using Jake Lo's OpenCore 0.6.3 EFI for my E7270, plus the ssdt.aml that I generated for this machine and added to /EFI/OC/ACPI as SSDT-PM.aml.

Whenever I dock or remove the laptop from the dock, it reboots, with the following "System Sleep Wake Problem Report":

Sleep Wake failure in EFI

Failure code:: 0xffffffff 0x0000001f

Please IGNORE the below stackshot

================================================================
Date/Time:        2020-12-06 22:13:57 -0800
OS Version:       ??? ??? (Build ???)
Architecture:     x86_64
Report Version:   29

Data Source:      Stackshots
Shared Cache:     0xa638000 FEAD5445-3395-35A9-8514-928F530B3939

Event:            Sleep Wake Failure
Duration:         0.00s
Steps:            1

Boot args:        darkwake=0 keepsyms=1 debug=0x100 -v

Time Awake Since Boot: 15s

Process:          swd [243]
Architecture:     x86_64
Footprint:        400 KB
Start time:       2020-12-06 22:13:57 -0800
End time:         2020-12-06 22:13:57 -0800
Num samples:      1 (1)

  Thread 0x706    1 sample (1)    priority 4 (base 4)
  <thread QoS background (requested background), thread darwinbg, process darwinbg, IO tier 2>
  1  start + 1 (libdyld.dylib + 109769) [0x7fff7181bcc9] 1
    1  ??? [0x10b582454] 1
      1  ??? [0x10b5821dd] 1
        1  __stack_snapshot_with_config + 10 (libsystem_kernel.dylib + 135862) [0x7fff7197d2b6] 1
         *1  ??? [0xffffff80002c1206] 1
           *1  ??? [0xffffff8000984c37] 1
             *1  ??? [0xffffff800089d7c1] 1
               *1  ??? [0xffffff80002e49e7] (running) 1

  Binary Images:
        0x7fff71801000 -     0x7fff71837fff  libdyld.dylib (750.6)               <789A18C2-8AC7-3C88-813D-CD674376585D>  /usr/lib/system/libdyld.dylib
        0x7fff7195c000 -     0x7fff71988fff  libsystem_kernel.dylib (6153.141.1) <2B6311E6-6240-3EF7-8C87-475B66F7452C>  /usr/lib/system/libsystem_kernel.dylib
Model: MacBookPro13,1, BootROM 429.40.5.0.0, 2 processors, Dual-Core Intel Core i5, 2.5 GHz, 16 GB, SMC 2.36f101
Graphics: Intel HD Graphics 520, Intel HD Graphics 520, spdisplays_builtin
Memory Module: BANK 0/DIMM A, 8 GB, DDR4, 2133 MHz, Micron, 16ATF1G64HZ-2G1B1
Memory Module: BANK 2/DIMM B, 8 GB, DDR4, 2133 MHz, 1315, CT8G4SFS824A.M8FE
AirPort: spairport_wireless_card_type_airport_extreme (0x14E4, 0x117), Broadcom BCM43xx 1.0 (7.77.111.1 AirPortDriverBrcmNIC-1615.1)
Bluetooth: Version 7.0.6f7, 3 services, 27 devices, 1 incoming serial ports
Network Service: Wi-Fi, AirPort, en3
Serial ATA Device: SanDisk SD8SN8U-256G-1006, 256.06 GB
USB Device: USB 3.0 Bus
USB Device: BRCM20702 Hub
USB Device: Bluetooth USB Host Controller
USB Device: Integrated_Webcam_HD
Thunderbolt Bus: 

This issue only started with open core 0.6.3.  I've attached my EFI folder.

Has anyone else had problems with E7270 and the dock?

EFI.zip

Thanks to Herve's physical description I was able to identify the tiny DW380 module in my e6230.

Based on a post elsewhere, I had been mislead into believing that the BCM20702A0 that was showing up in IOReg Explorer was actually a part of the BCM94322HM8L card.

I should have known to come here first - you guys have knowledge of these laptops that is unparalleled anywhere else...