Contribute
Register

HP Probook 450 G2 (Haswell) - issues after upgrade to El Capitan

Status
Not open for further replies.
Power led on, not blinking, can't be woke up

Instant wake, perhaps?

Download patchmatic: https://bitbucket.org/RehabMan/os-x-maciasl-patchmatic/downloads/RehabMan-patchmatic-2015-0107.zip
Extract the 'patchmatic' binary from the ZIP. Copy it to /usr/bin, such that you have the binary at /usr/bin/patchmatic.

In terminal,
Code:
if [ -d ~/Downloads/RehabMan ]; then rm -R ~/Downloads/RehabMan; fi
mkdir ~/Downloads/RehabMan
cd ~/Downloads/RehabMan
patchmatic -extract

Note: It is easier if you use copy/paste instead of typing the commands manually.

Post contents of Downloads/RehabMan directory (as ZIP).

Also, post ioreg: http://www.tonymacx86.com/audio/58368-guide-how-make-copy-ioreg.html. Please, use the IORegistryExplorer v2.1 attached to the post! DO NOT reply with an ioreg from any other version of IORegistryExplorer.app.

And output from:
Code:
kextstat|grep -y acpiplat
kextstat|grep -y appleintelcpu
kextstat|grep -y applelpc

Also, post EFI/Clover folder (press F4 at main Clover screen before collecting).

Also post output of:
Code:
sudo touch /System/Library/Extensions && sudo kextcache -u /
 
Hi,neamuu.Did you solve sleep issue ? I have the same problem with this laptop.

Hi eleron,

No, a fresh install, as RehabMan suggested, didn't fix the problem, so for me the solution was a downgrade to Yosemite, where sleep works.
 
Hello

From 10 days im trying install osx el cap on g2 450 core i3 4400 and im stuck here can you help me pls.
 

Attachments

  • IMG_0517.jpg
    IMG_0517.jpg
    1 MB · Views: 111
Problem now i have only windows laptop :(

Two choices:
- install Snow Leopard using iBoot Haswell after purchasing a retail SL DVD from Apple, use it to download a newer version
- borrow a Mac from someone you know
 
You probably have instant wake. It is covered in the ACPI patching guide.

http://www.tonymacx86.com/el-capitan-laptop-support/152573-guide-patching-laptop-dsdt-ssdts.html

I thought that the PBI did apply the PWR patch, but apparently only partially. This is what it does during installation (for a PB 4x0 G1/G2):

Code:
# set _PRW methods to return 0

into method label _PRW parent_adr 0x001D0000 code_regex Return[^(]*\([^(]*\(([^,]*)[^)]*[^,]* replace_matched
begin
Return (Package(){%1,0})
end;
into method label _PRW parent_adr 0x001A0000 code_regex Return[^(]*\([^(]*\(([^,]*)[^)]*[^,]* replace_matched
begin
Return (Package(){%1,0})
end;
into method label _PRW parent_adr 0x00140000 code_regex Return[^(]*\([^(]*\(([^,]*)[^)]*[^,]* replace_matched
begin
Return (Package(){%1,0})
end;
into method label _PRW parent_adr 0x00190000 code_regex Return[^(]*\([^(]*\(([^,]*)[^)]*[^,]* replace_matched
begin
Return (Package(){%1,0})
end;
into method label _PRW parent_adr 0x00190000 code_regex (Return\s+\(.*) replace_matched
begin
Store (0x00, Index (Local0, 0x01))\n
%1
end;

Source: 4x0G1.txt from PBI

I guess that this is not enough and we should apply all the other lines from "usb_prw_0x0d_xhc.txt", right? For now I have applied this patch manually and will report back about any sleep issues.
 
I thought that the PBI did apply the PWR patch, but apparently only partially. This is what it does during installation (for a PB 4x0 G1/G2):

Code:
# set _PRW methods to return 0

into method label _PRW parent_adr 0x001D0000 code_regex Return[^(]*\([^(]*\(([^,]*)[^)]*[^,]* replace_matched
begin
Return (Package(){%1,0})
end;
into method label _PRW parent_adr 0x001A0000 code_regex Return[^(]*\([^(]*\(([^,]*)[^)]*[^,]* replace_matched
begin
Return (Package(){%1,0})
end;
into method label _PRW parent_adr 0x00140000 code_regex Return[^(]*\([^(]*\(([^,]*)[^)]*[^,]* replace_matched
begin
Return (Package(){%1,0})
end;
into method label _PRW parent_adr 0x00190000 code_regex Return[^(]*\([^(]*\(([^,]*)[^)]*[^,]* replace_matched
begin
Return (Package(){%1,0})
end;
into method label _PRW parent_adr 0x00190000 code_regex (Return\s+\(.*) replace_matched
begin
Store (0x00, Index (Local0, 0x01))\n
%1
end;

Source: 4x0G1.txt from PBI

I guess that this is not enough and we should apply all the other lines from "usb_prw_0x0d_xhc.txt", right? For now I have applied this patch manually and will report back about any sleep issues.

You should look at your patched DSDT to see if the result is what is expected.
 
The patch will make six changes to the stock PBI DSDT (after installation):

It will remove two _PRW methods (for devices LANC and XHC) and add these four statements for the addresses that match:

begin Name(_PRW, Package() { 0x0D, 0 }) end;

As you pointed out in your FAQ the two _PRW methods that were removed could be the culprit. I will do some more testing tonight.
 
Status
Not open for further replies.
Back
Top