Contribute
Register

Asus R510JK (X550JK mobo) HD4600 problem

Status
Not open for further replies.
Joined
Mar 27, 2011
Messages
95
Motherboard
Asus R510JK
CPU
i7-4710HQ
Graphics
HD 4600/GTX 850M
Mobile Phone
  1. iOS
Hi,

I recently bought a new notebook - R510JK and I can't get HD4600 working. After booting with Clover I'm getting AGPM Controller: Unknown platform error no matter if I add ig-platform-id to the config.plist or not. I also tried booting with UniBeast, no luck either. I think the problem is Device (GFX0) is located in SSDT-7, not in DSDT. Could someone help me out with that? I am attaching all ACPI tables.

My best,
djseban
 

Attachments

  • tables.zip
    49.9 KB · Views: 122
Hi,

I recently bought a new notebook - R510JK and I can't get HD4600 working. After booting with Clover I'm getting AGPM Controller: Unknown platform error no matter if I add ig-platform-id to the config.plist or not. I also tried booting with UniBeast, no luck either. I think the problem is Device (GFX0) is located in SSDT-7, not in DSDT. Could someone help me out with that? I am attaching all ACPI tables.

My best,
djseban


Haswell Brightness Fix:

You will need to extract all DSDT/SSDT from Linux. Your GFX0 device is in one of the SSDTs not DSDT and to get a proper disassembly of your DSDT (and the SSDT that has GFX0) you will need all of them. They are available in /sys/firmware/acpi/tables and /sys/firmware/acpi/tables/dynamic. Place them on USB for transfer to OS X.

Place all SSDT/DSDT in a single directory and use a recent build of iasl to disassemble:
http://www.tonymacx86.com/attachmen...5-buggy-dsdt-asus-q501la-help-needed-iasl.zip
Code:
cd "to directory where you placed all SSDT/DSDT"
iasl -da *.aml

Then search the resulting *.dsl so you know where GFX0 is defined. Search for "Device (GFX0)"...

Laptop repo: https://github.com/RehabMan/Laptop-DSDT-Patch
Apply: "Rename GFX0 to IGPU" (to both DSDT and the SSDT that has your GFX0 device)
Apply: "Brightness Fix (Haswell)" to the file (SSDT or DSDT) with GFX0 device definition.
install: https://github.com/RehabMan/OS-X-ACPI-Backlight

Place patched DSDT.aml in /Extra/dsdt.aml. Place patched SSDT in /Extra/ssdt-1.aml (assuming you have already generated SSDT.aml for CPU). Obviously different locations for Clover (EFI/Clover/ACPI/patched).

Result: Working brightness slider in SysPrefs->Displays (mapping of keyboard keys is a separate issue), possible LID sleep, and IGPU power management.
 
Haswell Brightness Fix:

You will need to extract all DSDT/SSDT from Linux. Your GFX0 device is in one of the SSDTs not DSDT and to get a proper disassembly of your DSDT (and the SSDT that has GFX0) you will need all of them. They are available in /sys/firmware/acpi/tables and /sys/firmware/acpi/tables/dynamic. Place them on USB for transfer to OS X.

Place all SSDT/DSDT in a single directory and use a recent build of iasl to disassemble:
http://www.tonymacx86.com/attachmen...5-buggy-dsdt-asus-q501la-help-needed-iasl.zip
Code:
cd "to directory where you placed all SSDT/DSDT"
iasl -da *.aml

Then search the resulting *.dsl so you know where GFX0 is defined. Search for "Device (GFX0)"...

Laptop repo: https://github.com/RehabMan/Laptop-DSDT-Patch
Apply: "Rename GFX0 to IGPU" (to both DSDT and the SSDT that has your GFX0 device)
Apply: "Brightness Fix (Haswell)" to the file (SSDT or DSDT) with GFX0 device definition.
install: https://github.com/RehabMan/OS-X-ACPI-Backlight

Place patched DSDT.aml in /Extra/dsdt.aml. Place patched SSDT in /Extra/ssdt-1.aml (assuming you have already generated SSDT.aml for CPU). Obviously different locations for Clover (EFI/Clover/ACPI/patched).

Result: Working brightness slider in SysPrefs->Displays (mapping of keyboard keys is a separate issue), possible LID sleep, and IGPU power management.

Thanks for the reply. Will HD4600 be working after I apply only these 2 patches? Addding DSM Method to the Device (GFX0) isn't necessary?

My best
 
Thanks for the reply. Will HD4600 be working after I apply only these 2 patches? Addding DSM Method to the Device (GFX0) isn't necessary?

My best

HD4600 will work if you inject the correct ig-platform-id. Usually 0a260006. It is automatic if you're using Chimera3. Otherwise, specifics depend on the bootloader you're using. Or you can use DSDT patches as you mention.
 
Ok. So I extracted ACPI tables with the newest Ubuntu. As a result of the iasl command I got multiple DSL files. And it seems like Device (GFX0) is in SSDT5.dsl, but the problem is I can't compile it due to errors. What to do now? Try to fix the errors?
 
Ok. So I extracted ACPI tables with the newest Ubuntu. As a result of the iasl command I got multiple DSL files. And it seems like Device (GFX0) is in SSDT5.dsl, but the problem is I can't compile it due to errors. What to do now? Try to fix the errors?

No idea without the files... Post your files and I'll look at them.
 
Okay. Thanks for help. I am attaching all dsls.

My best
 

Attachments

  • Archive.zip
    100.1 KB · Views: 106
Okay. Thanks for help. I am attaching all dsls.

My best

No. Attach native files extracted from Linux.

FYI: You disassembled your files incorrectly. Read post #2 carefully.
 
Ahh, my mistake. Here they go.

@edit: I disassembled every file separately, if i tried by one command I got this out and in result no files w:
Code:
Intel ACPI Component Architecture
ASL Optimizing Compiler version 20140627-64 [Jul  9 2014]
Copyright (c) 2000 - 2014 Intel Corporation

Loading Acpi table from file   APIC.aml - Length 00000146 (000092)
Loading Acpi table from file  SSDT9.aml - Length 00001450 (0005AA)
ACPI: SSDT 0x0000000000000000 0005AA (v01 PmRef  ApIst    00003000 INTL 20120711)
Acpi table [SSDT] successfully installed and loaded
Pass 1 parse of [SSDT]
Pass 2 parse of [SSDT]
Loading Acpi table from file  SSDT8.aml - Length 00000979 (0003D3)
ACPI: SSDT 0x0000000000000000 0003D3 (v01 PmRef  Cpu0Cst  00003001 INTL 20120711)
Acpi table [SSDT] successfully installed and loaded
Pass 1 parse of [SSDT]
Pass 2 parse of [SSDT]
Loading Acpi table from file  SSDT7.aml - Length 00005122 (001402)
ACPI: SSDT 0x0000000000000000 001402 (v01 OptRef OptTabl  00001000 INTL 20120711)
Acpi table [SSDT] successfully installed and loaded
Pass 1 parse of [SSDT]
Pass 2 parse of [SSDT]
Loading Acpi table from file  SSDT6.aml - Length 00006106 (0017DA)
ACPI: SSDT 0x0000000000000000 0017DA (v01 SgRef  SgPeg    00001000 INTL 20120711)
Acpi table [SSDT] successfully installed and loaded
Pass 1 parse of [SSDT]
Pass 2 parse of [SSDT]
Loading Acpi table from file  SSDT5.aml - Length 00017658 (0044FA)
ACPI: SSDT 0x0000000000000000 0044FA (v01 SaSsdt SaSsdt   00003000 INTL 20091112)
Acpi table [SSDT] successfully installed and loaded
Pass 1 parse of [SSDT]
Pass 2 parse of [SSDT]
Loading Acpi table from file  SSDT4.aml - Length 00000664 (000298)
ACPI: SSDT 0x0000000000000000 000298 (v01 SataRe SataTabl 00001000 INTL 20120711)
Acpi table [SSDT] successfully installed and loaded
Pass 1 parse of [SSDT]
Pass 2 parse of [SSDT]
Loading Acpi table from file  SSDT3.aml - Length 00002776 (000AD8)
ACPI: SSDT 0x0000000000000000 000AD8 (v01 PmRef  CpuPm    00003000 INTL 20120711)
Acpi table [SSDT] successfully installed and loaded
Pass 1 parse of [SSDT]
Pass 2 parse of [SSDT]
Loading Acpi table from file  SSDT2.aml - Length 00001337 (000539)
ACPI: SSDT 0x0000000000000000 000539 (v01 PmRef  Cpu0Ist  00003000 INTL 20120711)
Acpi table [SSDT] successfully installed and loaded
Pass 1 parse of [SSDT]
Pass 2 parse of [SSDT]
Loading Acpi table from file SSDT10.aml - Length 00000281 (000119)
ACPI: SSDT 0x0000000000000000 000119 (v01 PmRef  ApCst    00003000 INTL 20120711)
Acpi table [SSDT] successfully installed and loaded
Pass 1 parse of [SSDT]
Pass 2 parse of [SSDT]
Loading Acpi table from file  SSDT1.aml - Length 00000413 (00019D)
ACPI: SSDT 0x0000000000000000 00019D (v01 Intel  zpodd    00001000 INTL 20120711)
Acpi table [SSDT] successfully installed and loaded
Pass 1 parse of [SSDT]
Pass 2 parse of [SSDT]
Loading Acpi table from file   MSDM.aml - Length 00000085 (000055)
Pass 1 parse of [MSDM]
ACPI Warning: Invalid character(s) in name (0x38562D50), repaired: [P*V8] (20140627/utstring-711)
ACPI Warning: Invalid character(s) in name (0x374B2D59), repaired: [Y*K7] (20140627/utstring-711)
Pass 2 parse of [MSDM]
ACPI Error: Unknown opcode 0x1D at table offset 0x0034, ignoring (20140627/psobject-183)
/*
Error: Unknown opcode 0x1D at table offset 0x0034, context:
  0024: 01 00 00 00 00 00 00 00 01 00 00 00 00 00 00 00  ................
  0034: 1D 00 00 00 4E 54 46 48 50 2D 56 38 34 4A 32 2D  ....XXXXX-XXXXX-
  0044: 51 39 4D 54 4A 2D 54 59 37 36 59 2D 4B 37 34 57  XXXXX-XXXXX-XXXX
 */
ACPI Warning: Invalid character(s) in name (0x38562D50), repaired: [P*V8] (20140627/utstring-711)
ACPI Warning: Invalid character(s) in name (0x374B2D59), repaired: [Y*K7] (20140627/utstring-711)
Loading Acpi table from file   MCFG.aml - Length 00000060 (00003C)
Pass 1 parse of [MCFG]
Pass 2 parse of [MCFG]
ACPI Error: Unknown opcode 0xF8 at table offset 0x002F, ignoring (20140627/psobject-183)
/*
Error: Unknown opcode 0xF8 at table offset 0x002F, context:
  001F: 54 97 00 00 00 00 00 00 00 00 00 00 00 00 00 00  T...............
  002F: F8 00 00 00 00 00 00 00 3F 00 00 00 00 00 00 04  ........?.......
  003F: 00 00 00 00 00 00 00 00 00 0E 08 01 00 00 00 02  ................
 */
ACPI Error: Unknown opcode 0x3F at table offset 0x0037, ignoring (20140627/psobject-183)
/*
Error: Unknown opcode 0x3F at table offset 0x0037, context:
  0027: 00 00 00 00 00 00 00 00 F8 00 00 00 00 00 00 00  ................
  0037: 3F 00 00 00 00 00 00 04 00 00 00 00 00 00 00 00  ?...............
  0047: 00 0E 08 01 00 00 00 02 00 00 00 00 00 00 00 00  ................
 */
Loading Acpi table from file   HPET.aml - Length 00000056 (000038)
Pass 1 parse of [HPET]
Pass 2 parse of [HPET]
ACPI Error: Unknown opcode 0x40 at table offset 0x0029, ignoring (20140627/psobject-183)
/*
Error: Unknown opcode 0x40 at table offset 0x0029, context:
  0019: 20 07 01 41 4D 49 2E 05 00 00 00 01 A7 86 80 00   ..AMI..........
  0029: 40 00 00 00 00 D0 FE 00 00 00 00 00 EE 37 00 00  @............7..
  0039: 00 00 00 00 00 04 00 B0 31 23 00 01 00 00 00 0F  ........1#......
 */
ACPI Error: Unknown opcode 0xD0 at table offset 0x002E, ignoring (20140627/psobject-183)
/*
Error: Unknown opcode 0xD0 at table offset 0x002E, context:
  001E: 49 2E 05 00 00 00 01 A7 86 80 00 40 00 00 00 00  I..........@....
  002E: D0 FE 00 00 00 00 00 EE 37 00 00 00 00 00 00 00  ........7.......
  003E: 04 00 B0 31 23 00 01 00 00 00 0F 01 00 05 42 43  ...1#.........BC
 */
ACPI Error: Unknown opcode 0xFE at table offset 0x002F, ignoring (20140627/psobject-183)
/*
Error: Unknown opcode 0xFE at table offset 0x002F, context:
  001F: 2E 05 00 00 00 01 A7 86 80 00 40 00 00 00 00 D0  ..........@.....
  002F: FE 00 00 00 00 00 EE 37 00 00 00 00 00 00 00 04  .......7........
  003F: 00 B0 31 23 00 01 00 00 00 0F 01 00 05 42 43 4D  ..1#.........BCM
 */
ACPI Error: Unknown opcode 0xEE at table offset 0x0035, ignoring (20140627/psobject-183)
/*
Error: Unknown opcode 0xEE at table offset 0x0035, context:
  0025: A7 86 80 00 40 00 00 00 00 D0 FE 00 00 00 00 00  ....@...........
  0035: EE 37 00 00 00 00 00 00 00 04 00 B0 31 23 00 01  .7..........1#..
  0045: 00 00 00 0F 01 00 05 42 43 4D 44 00 A8 20 00 01  .......BCMD.. ..
 */
Loading Acpi table from file   FPDT.aml - Length 00000068 (000044)
Pass 1 parse of [FPDT]
Could not parse external ACPI tables, AE_AML_NO_OPERAND
 

Attachments

  • tables.zip
    46.6 KB · Views: 85
Ahh, my mistake. Here they go.

SSDT5 does have GFX0 device definition. If disassembled correctly, it compiles without errors.

DSDT will compile without error with only two common fixes...
Patches from here: https://github.com/RehabMan/Laptop-DSDT-Patch
Apply: "Fix PARSEOP_ZERO Error"
Apply: "Fix ADBG Error"

I downloaded your ZIP, extracted it, then disassembled:
Code:
cd ~/Downloads/tables
iasl -da DSDT SSDT*
 
Status
Not open for further replies.
Back
Top