Contribute
Register

I've two strange issues

Status
Not open for further replies.
how to check SystemMemory?

Disassemble each ACPI/patched and ACPI/origin and compare:
Code:
# use Clover F4 to extract current ACPI/origin
# make copy of ACPI/patched and ACPI/origin from EFI somewhere convenient
# the disassemble/compare
cd ACPI/origin
iasl -da -dl DSDT.aml SSDT*.aml
cd ../patched
iasl -da -dl DSDT.aml SSDT*.aml
diff ../origin ../patched | grep SystemMemory
 
Disassemble each ACPI/patched and ACPI/origin and compare:
Code:
# use Clover F4 to extract current ACPI/origin
# make copy of ACPI/patched and ACPI/origin from EFI somewhere convenient
# the disassemble/compare
cd ACPI/origin
iasl -da -dl DSDT.aml SSDT*.aml
cd ../patched
iasl -da -dl DSDT.aml SSDT*.aml
diff ../origin ../patched | grep SystemMemory
thank you :)
SystemMemory is ok?
Code:
SHAIZUs-MacBook-Pro:patched shaizu$ diff ../origin ../patched | grep SystemMemory
<     OperationRegion (OGNS, SystemMemory, 0x9AF88F98, 0x0000000C)
>     OperationRegion (OGNS, SystemMemory, 0x9AF88F98, 0x0C)
<     OperationRegion (MDBG, SystemMemory, 0x9AF84018, 0x00001004)
>     OperationRegion (MDBG, SystemMemory, 0x9AF84018, 0x1004)
<         OperationRegion (COMP, SystemMemory, 0x9AF8CC98, 0x00000200)
>         OperationRegion (COMP, SystemMemory, 0x9AF8CC98, 0x0200)
<             OperationRegion (HNVS, SystemMemory, 0x9AF8A000, 0x000012E8)
>             OperationRegion (HNVS, SystemMemory, 0x9AF8A000, 0x12E8)
<         OperationRegion (SGOP, SystemMemory, 0x9AC8DF98, 0x00000030)
>         OperationRegion (SGOP, SystemMemory, 0x9AC8DF98, 0x30)
<         OperationRegion (AOPR, SystemMemory, 0x9AF88F18, 0x00000005)
>         OperationRegion (AOPR, SystemMemory, 0x9AF88F18, 0x05)
<         OperationRegion (PNVS, SystemMemory, 0x9AF87F18, 0x0053)
>         OperationRegion (PNVS, SystemMemory, 0x9AF87F18, 0x53)
SHAIZUs-MacBook-Pro:patched shaizu$
 
thank you :)
SystemMemory is ok?
Code:
SHAIZUs-MacBook-Pro:patched shaizu$ diff ../origin ../patched | grep SystemMemory
<     OperationRegion (OGNS, SystemMemory, 0x9AF88F98, 0x0000000C)
>     OperationRegion (OGNS, SystemMemory, 0x9AF88F98, 0x0C)
<     OperationRegion (MDBG, SystemMemory, 0x9AF84018, 0x00001004)
>     OperationRegion (MDBG, SystemMemory, 0x9AF84018, 0x1004)
<         OperationRegion (COMP, SystemMemory, 0x9AF8CC98, 0x00000200)
>         OperationRegion (COMP, SystemMemory, 0x9AF8CC98, 0x0200)
<             OperationRegion (HNVS, SystemMemory, 0x9AF8A000, 0x000012E8)
>             OperationRegion (HNVS, SystemMemory, 0x9AF8A000, 0x12E8)
<         OperationRegion (SGOP, SystemMemory, 0x9AC8DF98, 0x00000030)
>         OperationRegion (SGOP, SystemMemory, 0x9AC8DF98, 0x30)
<         OperationRegion (AOPR, SystemMemory, 0x9AF88F18, 0x00000005)
>         OperationRegion (AOPR, SystemMemory, 0x9AF88F18, 0x05)
<         OperationRegion (PNVS, SystemMemory, 0x9AF87F18, 0x0053)
>         OperationRegion (PNVS, SystemMemory, 0x9AF87F18, 0x53)
SHAIZUs-MacBook-Pro:patched shaizu$

Yes.
Like I already wrote... I had already checked it.
 
Yes.
Like I already wrote... I had already checked it.
actually I re-extracted and re-patched DSDT and SSDTs because I updated to macOS 10.13.1
but the issue still there, don't know what is causing this.
 
actually I re-extracted and re-patched DSDT and SSDTs because I updated to macOS 10.13.1
but the issue still there, don't know what is causing this.

As #129...
"No further ideas."
 
As #129...
"No further ideas."
yeah, I think I'll have to live with this annoying issue
but because of this issue I've learned a lot from you :)
I was just thinking what would happen to this forum without you
just because of you this forum is alive
thank you @RehabMan for always helping and guiding us to the right path :)
 
yeah, I think I'll have to live with this annoying issue
but because of this issue I've learned a lot from you :)
I was just thinking what would happen to this forum without you
just because of you this forum is alive
thank you @RehabMan for always helping and guiding us to the right path :)

Unfortunately, not all problems are easily solved.
 
I have the same issue as well with my almost same HP laptop. I believe it's a power supply circuit issue. Not really a big problem. My main issue is the QE acceleration not working. As I stated in another thread, I won't go any further on that. I will just buy a new laptop once I have time and money...
 
I have the same issue as well with my almost same HP laptop. I believe it's a power supply circuit issue. Not really a big problem. My main issue is the QE acceleration not working. As I stated in another thread, I won't go any further on that. I will just buy a new laptop once I have time and money...

Your problem is completely different.
 
Your problem is completely different.
actually he's a same power button issue like my laptop
he also has to press power button twice to turn-on his laptop
 
Status
Not open for further replies.
Back
Top