Contribute
Register

Guide To Install Yosemite on HP Laptops with Clover UEFI

Same crash. I don't think a bug in ACPIBacklight.kext, but rather problem in lower level... The only thing I can think of changing in this code is to do the ACPI call in the workloop thread instead of whatever thread doIntegerSet is called on. I don't have time to make the required code changes right now though...

SystemMemory addresses match between origin and patched, so must be some other issue.

Given that you're the only one with this issue... and your machine is the only Ivy machine that we use -xcpm on...

Suspect power management problem/ XCPM...

I followed your instructions, and it is almost working. The kernel panics has gone, but my cpu's frequency is locked at 792 MHz. The good news is that the fan is really quiet.:lol:

> - install all kexts to /S/L/E (using injection for the main install is not a good idea)
Yes, this step is done
> - change config.plist/SSDT/DropOem=false (this will inject the OEM SSDTs, resulting in a more complete PM setup)
Yes, this step is done
> - remove -xcpm from config.plist/Boot/Arguments
Yes, this step is done
> - you may need to change SMBIOS (try MacBookPro9,1 or MacBookPro9,2)
This seems not affect much. Change it or not is the same.

As this is a rare case on rare machines, I think there is no need to take up your time to work on this. But if you are interested in this, I will offer any help.

For my laptop, so for the ultimate solution is to remove ACPIBacklight.kext from EFI partition. But, how to explain that brightness adjustment works fine without that kext? Is my laptop working with Apple's native kext (AppleBacklight.kext) ???

Very very confused...

By the way, I learned how you analyse kernel panic backtrace. Great!!!
 
I followed your instructions, and it is almost working. The kernel panics has gone, but my cpu's frequency is locked at 792 MHz. The good news is that the fan is really quiet.:lol:

> - install all kexts to /S/L/E (using injection for the main install is not a good idea)
Yes, this step is done
> - change config.plist/SSDT/DropOem=false (this will inject the OEM SSDTs, resulting in a more complete PM setup)
Yes, this step is done
> - remove -xcpm from config.plist/Boot/Arguments
Yes, this step is done
> - you may need to change SMBIOS (try MacBookPro9,1 or MacBookPro9,2)
This seems not affect much. Change it or not is the same.

As this is a rare case on rare machines, I think there is no need to take up your time to work on this. But if you are interested in this, I will offer any help.

For my laptop, so for the ultimate solution is to remove ACPIBacklight.kext from EFI partition. But, how to explain that brightness adjustment works fine without that kext? Is my laptop working with Apple's native kext (AppleBacklight.kext) ???

Very very confused...

By the way, I learned how you analyse kernel panic backtrace. Great!!!

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:
rm -R ~/Downloads/RehabMan
mkdir ~/Downloads/RehabMan
cd ~/Downloads/RehabMan
patchmatic -extract

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
 
After a clean 10.10.3 installation, the result is the same: no battery info!

There are error crashes, generated at each +/- 30 seconds:
Apr 13 15:10:29 hp9470m com.apple.xpc.launchd[1] (com.apple.SystemUIServer.agent[502]): Service exited due to signal: Segmentation fault: 11
Apr 13 15:10:29 hp9470m.lan ReportCrash[501]: Saved crash report for SystemUIServer[502] version 1.7 (410.2) to /Users/fred/Library/Logs/DiagnosticReports/SystemUIServer_2015-04-13-151029_hp9470m.crash
Apr 13 15:10:29 hp9470m.lan ReportCrash[501]: Removing excessive log: file:///Users/fred/Library/Logs/DiagnosticReports/SystemUIServer_2015-04-13-150041_hp9470m.crash
Apr 13 15:10:29 hp9470m.lan Spotlight[294]: spot: agent checkin
Apr 13 15:10:29 hp9470m.lan SystemUIServer[505]: Cannot find executable for CFBundle 0x7fa8daf00260 </System/Library/CoreServices/Menu Extras/Clock.menu> (not loaded)
Apr 13 15:10:30 hp9470m.lan SystemUIServer[505]: Menu Extra: <BatteryExtra: 0x7fa8dae23eb0> is over retained.

The crash report: https://cld.pt/dl/download/25e9cd08...ystemUIServer_2015-04-13-151029_hp9470m.crash


Hello everybody

i have the same Problems :(
no Batterie Info
 
Do a fresh install and report back.

hey RehabMan

this is my 2. fresh installation with 10.10.3 and the new Probook installer

and i create the Stick 2x new with download 10.10.3 from the app store

Before I install new I had no Problems with 10.10.2.
 
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.

I have uploaded relative files.

1. View attachment Cocoa’s MacBook Pro.ioreg
2. View attachment RehabMan.zip

> kextstat|grep -y acpiplat
Code:
[FONT=Menlo]13    2 0xffffff7f82878000 0x65000    0x65000    com.apple.driver.AppleACPIPlatform (3.1) <12 11 7 6 5 4 3 1>[/FONT]


> kextstat|grep -y appleintelcpu
Code:
[FONT=Menlo]   24    0 0xffffff7f82505000 0x2b000    0x2b000    com.apple.driver.AppleIntelCPUPowerManagement (218.0.0) <7 6 5 4 3 1>
[/FONT][FONT=Menlo]   32    0 0xffffff7f82500000 0x3000     0x3000     com.apple.driver.AppleIntelCPUPowerManagementClient (218.0.0) <7 6 5 4 3 1>[/FONT]
 
hey RehabMan

this is my 2. fresh installation with 10.10.3 and the new Probook installer

and i create the Stick 2x new with download 10.10.3 from the app store

Before I install new I had no Problems with 10.10.2.

Sorry, I don't understand what you're saying. Either you did a fresh install (to erased partition) or you didn't.
 
I have uploaded relative files.

1. View attachment 134148
2. View attachment 134149

> kextstat|grep -y acpiplat
Code:
[FONT=Menlo]13    2 0xffffff7f82878000 0x65000    0x65000    com.apple.driver.AppleACPIPlatform (3.1) <12 11 7 6 5 4 3 1>[/FONT]


> kextstat|grep -y appleintelcpu
Code:
[FONT=Menlo]   24    0 0xffffff7f82505000 0x2b000    0x2b000    com.apple.driver.AppleIntelCPUPowerManagement (218.0.0) <7 6 5 4 3 1>
[/FONT][FONT=Menlo]   32    0 0xffffff7f82500000 0x3000     0x3000     com.apple.driver.AppleIntelCPUPowerManagementClient (218.0.0) <7 6 5 4 3 1>[/FONT]

I don't see anything wrong...

Note: My configuration is very similar, except I have patched my DSDT according to my own wiki at my DSDT patch repo: https://github.com/RehabMan/HP-ProBook-4x30s-DSDT-Patch

It is different than from how PBI-CE patches...
 
Hi,
what do you reckon makes more sense to get a Dual Boot Win7 and Yosemite to work on my probook 6560b -

Should I migrate my current Win7 64bit to uefi? Apparently os x can install in addition to a Win7 if there is only one uefi partition larger than 200MB and the NTFS Win7 partition plus one free partition for os x. I'd need to remove the HP/Win7 restore partitions for this to work from what I read.

Or should I stay with mbr and use the legacy bootloader?

(Ok third option would be to buy and install a second hard disk)

Thanks for any advice.

mymac999
 
Back
Top