Contribute
Register

HD4000 Internal Display + HDMI out Framebuffer Issue

Status
Not open for further replies.

Attachments

  • 0x0166000A.zip
    497.7 KB · Views: 64
  • 0x0166000B.zip
    650.5 KB · Views: 55
metsarono said:
Thank you for the friendly reminder. I do now recall you outlining this in other threads. Please see attached.
Click to expand...

Implement backlight control. See if it helps.
 
RehabMan said:
Implement backlight control. See if it helps.
Click to expand...

I have injected ACPIBacklight.kext along with the following DSDT/SSDT patches:

DSDT
audio_HDEF-layout12
graphics_EDID
graphics_HD4K_high
graphics_PNLF_ivy_sandy
graphics_REG-disable
graphics_Rename-GFX0
remove_DSM
system_IMEI
system_IRQ
system_OSYS_win8
system_RTC
system_SMBUS
system_WAK2
usb_prw_0x6d_xhc

SSDT
graphics_SSDT-disable-cleanup

SSDT-1
fix_PSS

SSDT-2

I have tried reverting back to AppleBacklight.kext. Nothing I have tried so far has resulted in a brightness slider in display preferences.
 
metsarono said:
I have injected ACPIBacklight.kext along with the following DSDT/SSDT patches:

DSDT
audio_HDEF-layout12
graphics_EDID
graphics_HD4K_high
graphics_PNLF_ivy_sandy
graphics_REG-disable
graphics_Rename-GFX0
remove_DSM
system_IMEI
system_IRQ
system_OSYS_win8
system_RTC
system_SMBUS
system_WAK2
usb_prw_0x6d_xhc

SSDT
graphics_SSDT-disable-cleanup

SSDT-1
fix_PSS

SSDT-2

I have tried reverting back to AppleBacklight.kext. Nothing I have tried so far has resulted in a brightness slider in display preferences.
Click to expand...

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

If using Clover, post EFI/Clover folder.

--

Please provide complete details in your profile/signature
(Profile/Settings link in upper right corner of this site)

System: manufacturer/model + bootloader(Clover/Chameleon/Chimera)
CPU: detailed CPU model + motherboard chipset
Graphics: all graphics devices + laptop internal screen resolution

For example, typical Ivy laptop:
System: HP ProBook 4540s (Clover)
CPU: i5-3320m/HM76
Graphics: HD4000, 1366x768

Use CPU-Z on Windows to find CPU (Core iX-xxx) and motherboard chipset (HMxx), and graphics capabilities. For a laptop, these details are important and affect critical installation procedures.
 
RehabMan said:
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

If using Clover, post EFI/Clover folder.

--

Please provide complete details in your profile/signature
(Profile/Settings link in upper right corner of this site)
Click to expand...

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

[FONT=Helvetica]kextstat|grep -y appleintelcpu[/FONT][FONT=Helvetica]  
21    0 0xffffff7f81f18000 0x2b000    0x2b000    com.apple.driver.AppleIntelCPUPowerManagement (218.0.0) <7 6 5 4 3 1>[/FONT]
[FONT=Helvetica]   30    0 0xffffff7f81f13000 0x3000     0x3000     com.apple.driver.AppleIntelCPUPowerManagementClient (218.0.0) <7 6 5 4 3 1>[/FONT]

[FONT=Helvetica]kextstat|grep -y applelpc[/FONT][FONT=Helvetica]  
88    0 0xffffff7f81d2c000 0x3000     0x3000     com.apple.driver.AppleLPC (1.7.3) <84 12 5 4 3>[/FONT]

Thank you for your help so far RehabMan :)
 

Attachments

  • CLOVER.zip
    4.3 MB · Views: 73
  • IOReg.ioreg
    3.3 MB · Views: 82
  • RehabMan.zip
    16.8 KB · Views: 72
metsarono said:
Code: 
[FONT=Helvetica]kextstat|grep -y acpiplat[/FONT][FONT=Helvetica]  
13    2 0xffffff7f82025000 0x5f000    0x5f000    com.apple.driver.AppleACPIPlatform (3.1) <12 11 7 6 5 4 3 1>[/FONT]

[FONT=Helvetica]kextstat|grep -y appleintelcpu[/FONT][FONT=Helvetica]  
21    0 0xffffff7f81f18000 0x2b000    0x2b000    com.apple.driver.AppleIntelCPUPowerManagement (218.0.0) <7 6 5 4 3 1>[/FONT]
[FONT=Helvetica]   30    0 0xffffff7f81f13000 0x3000     0x3000     com.apple.driver.AppleIntelCPUPowerManagementClient (218.0.0) <7 6 5 4 3 1>[/FONT]

[FONT=Helvetica]kextstat|grep -y applelpc[/FONT][FONT=Helvetica]  
88    0 0xffffff7f81d2c000 0x3000     0x3000     com.apple.driver.AppleLPC (1.7.3) <84 12 5 4 3>[/FONT]

Thank you for your help so far RehabMan :)
Click to expand...

The bootlog extracted from ioreg shows you're booting from USB:
Code: 
5:110  0:000  Starting Clover rev 3241 on CLOVER EFI
5:110  0:000  SelfDevicePath=PcieRoot(0x0)\Pci(0x1D,0x0)\USB(0x0,0x0)\USB(0x0,0x0)\HD(2,GPT,809B2C00-18E2-4602-B07C-0B3436B2289A,0x64028,0x1D357B0) @1F4D3618

And only SSDTs are present, no patched DSDT.

Code: 
16:052  0:046  Inserting table[0]:SSDT.aml from EFI\CLOVER\ACPI\patched ... Success
16:202  0:149  Inserting table[2]:SSDT-1.aml from EFI\CLOVER\ACPI\patched ... Success
16:305  0:103  Inserting table[3]:SSDT-2.aml from EFI\CLOVER\ACPI\patched ... Success

In other words, you're not booting via the EFI/Clover you just provided...
 
RehabMan said:
The bootlog extracted from ioreg shows you're booting from USB:
Code: 
5:110  0:000  Starting Clover rev 3241 on CLOVER EFI
5:110  0:000  SelfDevicePath=PcieRoot(0x0)\Pci(0x1D,0x0)\USB(0x0,0x0)\USB(0x0,0x0)\HD(2,GPT,809B2C00-18E2-4602-B07C-0B3436B2289A,0x64028,0x1D357B0) @1F4D3618

And only SSDTs are present, no patched DSDT.

Code: 
16:052  0:046  Inserting table[0]:SSDT.aml from EFI\CLOVER\ACPI\patched ... Success
16:202  0:149  Inserting table[2]:SSDT-1.aml from EFI\CLOVER\ACPI\patched ... Success
16:305  0:103  Inserting table[3]:SSDT-2.aml from EFI\CLOVER\ACPI\patched ... Success

In other words, you're not booting via the EFI/Clover you just provided...
Click to expand...

The Clover folder I sent you is from the USB I'm currently booting from. I'm currently using it to test changes in case I break something I can still boot from the internal EFI partition or boot into Linux and load up a Yosemite VMWare install, mount the USB and launch Clover Configurator.

Is there any difference in what is injected when booting from USB?
Might this be a reason why the DSDT is not currently being loaded?
 
metsarono said:
The Clover folder I sent you is from the USB I'm currently booting from. I'm currently using it to test changes in case I break something I can boot in from the internal EFI partition or boot into Linux and load up a Yosemite VMWare install, mount the USB and launch Clover Configurator.
Click to expand...

An ioreg not matching the reported problem configuration is not helpful.

Is there any difference in what is injected when booting from USB?
Click to expand...

Differences are completely dependent on the Clover configuration difference with respect to USB vs. HDD EFI/Clover.

Might this be a reason why the DSDT is not currently being loaded?
Click to expand...

You evidently don't have a DSDT on your USB EFI/Clover/ACPI/patched. No expectations for it to load when not present.
 
RehabMan said:
An ioreg not matching the reported problem configuration is not helpful.



Differences are completely dependent on the Clover configuration difference with respect to USB vs. HDD EFI/Clover.



You evidently don't have a DSDT on your USB EFI/Clover/ACPI/patched. No expectations for it to load when not present.
Click to expand...

If you check the zip I uploaded you will find the DSDT.aml file is in the correct folder.

I have now booted from the internal EFI partition and followed your instructions.

Code: 
kextstat|grep -y acpiplat
   13    2 0xffffff7f82025000 0x65000    0x65000    com.apple.driver.AppleACPIPlatform (3.1) <12 11 7 6 5 4 3 1>

kextstat|grep -y appleintelcpu
   21    0 0xffffff7f81f18000 0x2b000    0x2b000    com.apple.driver.AppleIntelCPUPowerManagement (218.0.0) <7 6 5 4 3 1>
   30    0 0xffffff7f81f13000 0x3000     0x3000     com.apple.driver.AppleIntelCPUPowerManagementClient (218.0.0) <7 6 5 4 3 1>

kextstat|grep -y applelpc
   89    0 0xffffff7f81d2c000 0x3000     0x3000     com.apple.driver.AppleLPC (1.7.3) <83 12 5 4 3>
 

Attachments

  • CLOVER.zip
    4.2 MB · Views: 76
  • IOReg.ioreg
    3.4 MB · Views: 90
  • RehabMan.zip
    16.4 KB · Views: 71
metsarono said:
If you check the zip I uploaded you will find the DSDT.aml file is in the correct folder.
Click to expand...

Evidently not on your USB. If you want me to check what you have on your USB, provide the EFI/Clover folder from USB. If you're booting from USB, then you're getting all the configuration from EFI on the USB, none of it from HDD EFI.

It is either that or read below...

I have now booted from the internal EFI partition and followed your instructions.

Code: 
kextstat|grep -y acpiplat
   13    2 0xffffff7f82025000 0x65000    0x65000    com.apple.driver.AppleACPIPlatform (3.1) <12 11 7 6 5 4 3 1>

kextstat|grep -y appleintelcpu
   21    0 0xffffff7f81f18000 0x2b000    0x2b000    com.apple.driver.AppleIntelCPUPowerManagement (218.0.0) <7 6 5 4 3 1>
   30    0 0xffffff7f81f13000 0x3000     0x3000     com.apple.driver.AppleIntelCPUPowerManagementClient (218.0.0) <7 6 5 4 3 1>

kextstat|grep -y applelpc
   89    0 0xffffff7f81d2c000 0x3000     0x3000     com.apple.driver.AppleLPC (1.7.3) <83 12 5 4 3>
Click to expand...

DSDT.aml is not loading because you have config.plist/ACPI/DSDT/Name="" (you have it set to blank string).

Clover only does what you tell it to do. If you tell it the name of your DSDT file is "", then that's what it looks for.
 
Status
Not open for further replies.
Copyright © 2010 - 2024 tonymacx86 LLC
Back
Top