Contribute
Register

Asus A52JU - Shutdown-Problem

Status
Not open for further replies.
Joined
Oct 23, 2015
Messages
19
Motherboard
Odense2-K
CPU
I7 7700
Graphics
GTX 1060
Mac
  1. Mac Pro
Mobile Phone
  1. Android
Hallo, at first sorry about my english. Im from Germany.

I have installed High Sierra on Asus A52JU Notebook. It works fine. There is only a shutdown problem.

When i click on shutdown, osx shutdown but not the Notebook. Cooler is running and Displaylight is on.

In Clover i use "Fix Shutdown" but no luck. Then i use Evoreboot.kext and Osx can't boot. I used the Installerstick to repair.

I need help for the shutdown problem.


Hardware
Model: Asus A52JU
Mainboard: Asus K52JU
CPU: I3 370M
GPU: ATI Radeon HD 6370M
Chipset: HM55
Sound: Conexant CX...
WLAN: Broadcom
LAN: jMicron
Bios: AMI (mod BIOS)
OSX: 10.13.2
Bootloader: Clover (newest Version)
 
Hallo, at first sorry about my english. Im from Germany.

I have installed High Sierra on Asus A52JU Notebook. It works fine. There is only a shutdown problem.

When i click on shutdown, osx shutdown but not the Notebook. Cooler is running and Displaylight is on.

In Clover i use "Fix Shutdown" but no luck. Then i use Evoreboot.kext and Osx can't boot. I used the Installerstick to repair.

I need help for the shutdown problem.


Hardware
Model: Asus A52JU
Mainboard: Asus K52JU
CPU: I3 370M
GPU: ATI Radeon HD 6370M
Chipset: HM55
Sound: Conexant CX...
WLAN: Broadcom
LAN: jMicron
Bios: AMI (mod BIOS)
OSX: 10.13.2
Bootloader: Clover (newest Version)

No "Problem Reporting" files attached.
Read FAQ, "Problem Reporting" again. Carefully. Attach all requested files/output.
https://www.tonymacx86.com/threads/faq-read-first-laptop-frequent-questions.164990/
Use the tool mentioned in the FAQ, that way it is less likely you'll omit something.
 
Sorry, I did not read that.

Attached is the system report from the tool.
 

Attachments

  • debug_5798.zip
    7.7 MB · Views: 94
Sorry, I did not read that.

Attached is the system report from the tool.

Did you need to drop all the OEM SSDTs, or is that just something you did without testing whether it was necessary?

Your kextcache output proves kexts are not installed correctly.
All kexts you need must be installed to the system volume.
Read post #2 of the Clover guide for details:
https://www.tonymacx86.com/threads/guide-booting-the-os-x-installer-on-laptops-with-clover.148093/

And: Bad idea to put system kexts on EFI/Clover/kexts.

Try with HaltEnabler=false.

Your ioreg is corrupt (was not IORegistryExplorer v2.1), so I didn't look at anything else.
 
I just tried it; FixUSB inserts Method(_DSM for EHC1/2 power properties. So it is obsolete when using Sierra+ systems.
I use this DSDT patch https://github.com/Maromi-/G73JH-OSX/tree/master/Patches
and config.plist EC rename patch and everything works fine. (I know it is not needed if EC is used but I did create a SSDT-USBX.aml for testing on El Capitan.)



clover added this with FixUSB enabled
Code:
                Method (_DSM, 4, NotSerialized)  // _DSM: Device-Specific Method
                {
                    Store (Package (0x0D)
                        {
                            "device-id",
                            Buffer (0x04)
                            {
                                 0x34, 0x3A, 0x00, 0x00                        
                            },

                            "built-in",
                            Buffer (0x01)
                            {
                                 0x00                                          
                            },

                            "device_type",
                            Buffer (0x05)
                            {
                                "EHCI"
                            },

                            "AAPL,current-available",
                            0x05DC,
                            "AAPL,current-extra",
                            0x03E8,
                            "AAPL,current-in-sleep",
                            0x0BB8,
                            Buffer (0x01)
                            {
                                 0x00                                          
                            }
                        }, Local0)
                    DTGP (Arg0, Arg1, Arg2, Arg3, RefOf (Local0))
                    Return (Local0)
                }

Which USB patch are you referring to?
The USB guide mentions config.plist/ACPI/DSDT/Fixes/FixUSB=true
https://www.tonymacx86.com/threads/guide-10-11-usb-changes-and-solutions.173616/

I've never looked into what exactly FixUSB does, as I have no 5-series chipset hardware.
 
I just tried it; FixUSB inserts Method(_DSM for EHC1/2 power properties. So it is obsolete when using Sierra+ systems.
I use this DSDT patch https://github.com/Maromi-/G73JH-OSX/tree/master/Patches
and config.plist EC rename patch and everything works fine. (I know it is not needed if EC is used but I did create a SSDT-USBX.aml for testing on El Capitan.)



clover added this with FixUSB enabled
Code:
                Method (_DSM, 4, NotSerialized)  // _DSM: Device-Specific Method
                {
                    Store (Package (0x0D)
                        {
                            "device-id",
                            Buffer (0x04)
                            {
                                 0x34, 0x3A, 0x00, 0x00                       
                            },

                            "built-in",
                            Buffer (0x01)
                            {
                                 0x00                                         
                            },

                            "device_type",
                            Buffer (0x05)
                            {
                                "EHCI"
                            },

                            "AAPL,current-available",
                            0x05DC,
                            "AAPL,current-extra",
                            0x03E8,
                            "AAPL,current-in-sleep",
                            0x0BB8,
                            Buffer (0x01)
                            {
                                 0x00                                         
                            }
                        }, Local0)
                    DTGP (Arg0, Arg1, Arg2, Arg3, RefOf (Local0))
                    Return (Local0)
                }

You're referring to this patch then:
Code:
#Original by: RehabMan for: Laptop Patches
#add _STA to avoid instant wake
into device label EHC1 insert begin Name(_STA, 0) end;
into device label EHC2 insert begin Name(_STA, 0) end;
# remove _PRW methods to prevent instant wake
# if _PRW objects are methods
into method label _PRW parent_adr 0x001D0000 remove_entry;
into method label _PRW parent_adr 0x001A0000 remove_entry;
into method label _PRW parent_adr 0x001B0000 remove_entry;
# some other LAN cards use 0x00190000
into method label _PRW parent_adr 0x00190000 remove_entry;
# if _PRW methods are stuffed into a separate scope
into method label _PRW parent_label _SB.PCI0.EHC1 remove_entry;
into method label _PRW parent_label _SB.PCI0.EHC2 remove_entry;
into method label _PRW parent_label \_SB.PCI0.EHC1 remove_entry;
into method label _PRW parent_label \_SB.PCI0.EHC2 remove_entry;
# if _PRW objects are names
into device name_adr 0x001D0000 code_regex Name.*_PRW.*\n.*\n.*\n.*\n.*\}\) remove_matched;
into device name_adr 0x001A0000 code_regex Name.*_PRW.*\n.*\n.*\n.*\n.*\}\) remove_matched;
into device name_adr 0x001B0000 code_regex Name.*_PRW.*\n.*\n.*\n.*\n.*\}\) remove_matched;
into device name_adr 0x00190000 code_regex Name.*_PRW.*\n.*\n.*\n.*\n.*\}\) remove_matched;
# some _PRW have three entries in the Package
into device name_adr 0x001D0000 code_regex Name.*_PRW.*\n.*\n.*\n.*\n.*\n.*\}\) remove_matched;
into device name_adr 0x001A0000 code_regex Name.*_PRW.*\n.*\n.*\n.*\n.*\n.*\}\) remove_matched;
into device name_adr 0x001B0000 code_regex Name.*_PRW.*\n.*\n.*\n.*\n.*\n.*\}\) remove_matched;
into device name_adr 0x00190000 code_regex Name.*_PRW.*\n.*\n.*\n.*\n.*\n.*\}\) remove_matched;
# seems to work better if _PRW is present, but returns 0 (original was 3) for sleep state
into device name_adr 0x001D0000 insert begin Name(_PRW, Package() { 0x0D, 0 }) end;
into device name_adr 0x001A0000 insert begin Name(_PRW, Package() { 0x0D, 0 }) end;
into device name_adr 0x001B0000 insert begin Name(_PRW, Package() { 0x0D, 0 }) end;
into device name_adr 0x00190000 insert begin Name(_PRW, Package() { 0x0D, 0 }) end;

First the _STA part: Making _STA return zero will disable the ACPI identity (and all code associated with it). It is a bit of a strange thing to do. Better to determine what part of the ACPI code is causing a problem and edit it as opposed to eliminating it entirely.

After that (_STA=0), the rest of the edits related to EHC1/EHC2 don't matter, as the ACPI code there will never have any effect.

The rest is just "_PRW 0x0d" patch... (for instant wake).
 
according to ACPI no _STA means all bits are set which is how my DSDT was set before the patch
I found errata Bogus USB ports will be detected by mobile PCH equipped with 6 USB ports (HM55) on the first EHCI controller
Apple used 3rd party hardware attached to the controller to circumvent the issue
this is all HM55 so this would definitely be a diagnostics fail causing bit 3 to need to be clear
when i set _STA to < 3, all ports work, sleep and shutdown work
when i set _STA to a least 3 or no _STA, all ports work, sleep and shutdown broke

the rest of the patch
_PRW 0x0d" patch... (for instant wake)because original patch was not compatible with 5-series device name_adr 0x00140000 is not xhc

 
Last edited:
according to ACPI no _STA means all bits are set which is how my DSDT was set before the patch

Yes, default is "present". If you set _STA=0, it is now "not present".
Using _STA=0 essentially disconnects all ACPI code from that PCIe device.

the rest of the patch
_PRW 0x0d" patch... (for instant wake)because original patch was not compatible with 5-series device name_adr 0x00140000 is not xhc

The patch in my repo does not account for non-Intel hardware (as you imply you have non-Intel USB3).
 
Status
Not open for further replies.
Back
Top