acidanthera / bugtracker

Acidanthera Bugtracker
374 stars 42 forks source link

Issues with Hibernation Mode 3 or 25, using HibernationFixup kext. #2337

Closed Vorshim92 closed 6 months ago

Vorshim92 commented 9 months ago

Hello everyone! I apologize for the inconvenience, but I've been going crazy for a month trying to get Hibernation Mode 3 (or 25) working again on my Dell 2in1 7390. In August, I had succeeded, and it worked great. HibernationFixup is amazing with its settings, allowing you to choose the minimum battery percentage to trigger direct entry into S4, and it worked wonderfully. I even have old logs from August showing successful hibernation and everything recorded in the logs.

for this log I follow another post here in bugtracker and put in nvram debug=0x100 keepsyms=1 msgbuf=10485760 -liludbgall igdebug=0xff liludump=60 -hbfxdbg This might be the only log I have from when it was working, which makes me think that if I managed to get it to work once, there must be a way to get it working again. (It worked throughout the month of August until I switched back to Ventura). We just need to figure out what is preventing it and I need your help hibernationfixup debug sleepimage proof.txt

The settings I have are these(And they were the same settings in the EFI that I was using before when it was working): Booter -> Quirk -> DiscardeHibernateMap; Misc -> HibernateMode -> NVRAM; Misc -> HibernateSkipsPicker; hbfx-ahbm=933 in NVRAM;

This is my power setting: Screenshot 2023-10-08 alle 11 22 46

Now, honestly, I don't know what has changed! I'm not sure if it could be an issue with the operating system or something else. I tried using the EFI I had in August with OpenCore 0.9.4 that worked on SONOMA Beta 5, but it doesn't work either. It didn't work on Ventura, and it still doesn't work on Sonoma Release. I am trying to investigate to understand the nature of the reason why it no longer enters S4. ACPI? Bios? Operating System? Config (OpenCore), Kext? I really don't know... I'll provide some logs and the settings I'm using.

new test and log. S4 still not working, not even a trace of SLEEPIMAGE.

Screenshot 2023-10-08 alle 12 19 54 sudo dmesg > ~/desktop/hbfx_615.txt hbfx_615.txt log show --style syslog --source --debug --start '2023-10-08 11:34:00' --end '2023-10-08 12:20:00' > ~/desktop/log_complete.txt log_complete.txt.zip log show --predicate 'process == "kernel"' --style syslog --source --debug --start '2023-10-08 11:34:00' --end '2023-10-08 12:20:00' > ~/desktop/sys_log_hbfx.txt sys_log_hbfx.txt

p.s. if there is a better way to extract the log let me know. and let me know also if you want to see my EFI. I would really appreciate a hand from you; unfortunately, I'm not very good at reading these logs. I look forward to hearing from you, hoping to receive support :)

Vorshim92 commented 8 months ago

Hello everyone! I apologize for the spam, but in the end, I couldn't get anything to work. I can't figure it out. RTC is working, NVRAM is working. What else does it need to go into S4? I even tried the old EFI where it used to work; it worked for a whole month in August, but after I formatted and fixed some things, it no longer worked. Is there any specific BIOS setting or something that can be checked through debugging with logs to see why it's not entering S4? It goes into S3 normally, but not S4.