Jump to content
cheneyveron

new possibilities for X79 AppleACPIPlatform panic

63 posts in this topic

Recommended Posts

Hi guys,

My computer hardware is i signature.
Currently, 10.12.6 is perfect and my EFI is here.

Problem Description:
When I tried to boot 10.13 DP5, I encountered AppleACPIPlatform problem:


Typical Causes and Solutions:
After searching google for couple of days and with the help of @PMheart I found Alext James (@TheRacerMaster)'s article : http://alextjam.es/debugging-appleacpiplatform/

Because signed char become negative when bigger than 0x7f, Apple rewrote isprint method but seems to forget to cast char to unsigned. Thus, if OemId, Signature、OemId、OemTableId or AslCompilerId in any ACPI table contains a char greater than 0x7f, it will cause a memory overflow.

Most people can solve by:

  • dropping MATS/BGRT table( or other table )
  • add FixHeaders_20000000 in clover ACPI patch
  • Modify MATS/BGRT/other table and change that char to lower than 0x80

But sadly none worked for me :(

  1. I dropped all of my ACPI tables except DSDT and APIC, cuz I cannot boot without these two
  2. I searched for APIC and DSDT, none of their OemId, Signature、OemId、OemTableId or AslCompilerId contains char greater than 0x7f

Untypical Situation:
I took a video of my boot process using -verbose, debug=0x100, keepsyms=1 :
see online : https://www.dropbox.com/s/p4eztglltdtqxyb/boot.mp4?dl=0
In the trace, the boot process stuck at isspace other than isprint.
Out to curiosity, I decompiled AppleACPIPlatform and saw isspace looks like this:

                     _isspace:
000000000001f5cf         push       rbp                                         ; CODE XREF=_AcpiUtStrtoul64+71, _AcpiUtStrtoul64+89
000000000001f5d0         mov        rbp, rsp
000000000001f5d3         lea        rax, qword [__ctype]
000000000001f5da         mov        al, byte [rdi+rax]
000000000001f5dd         and        al, 0x20
000000000001f5df         shr        al, 0x5
000000000001f5e2         pop        rbp
000000000001f5e3         ret

And in C language it looks like this:

int _isspace(int arg0) {
    rax = (int)__ctype[arg0];
    return (rax & 0x20) >> 5;
} 

It uses __ctype as an array and rdi, which acts as argument in assembly language, as a pointer to find some char and put it into al
I checked the length of __ctype is 256, thus any normal byte, which is 16 bits, won't caus overflow.
However, Apple didn't cast arg0 to unsigned char. Thus, any char that's greater than 0x7f will also cause an overflow.
 
Follw the trace, I found _AcpiUtStrtoul64 the source code is here. Looks like it just uses a loop to judge whether it's a space. No other useful information were found during further dig.
 

New Discovery and Dilemma

Occasionally, i decompiled two programs written to test signed and unsigned char, and were surprised to find,

the only difference between 'cast to unsigned' and 'stay signed' in assembly language is that when delivering argument, unsigned used 'movzx' and singed used 'movsx'.

In assembly language, arguments are delivered by register rdi. So, I think, if I change 'movsx' to 'movzx' then this problem can be solved. Here's where isspace is called inside _AcpiUtStrtoul64:

0000000000001153         mov        qword [r14], 0x0
000000000000115a         movsx      edi, byte [r15]
000000000000115e         test       edi, edi
0000000000001160         je         loc_12b5

0000000000001166         mov        dword [rbp+var_2C], esi
0000000000001169         xor        eax, eax
000000000000116b         call       _isspace
0000000000001170         lea        rbx, qword [r15+1]
0000000000001174         test       eax, eax
0000000000001176         je         loc_118d

                     loc_1178:
0000000000001178         movsx      edi, byte [rbx]                             ; argument #1 for method _isspace, CODE XREF=_AcpiUtStrtoul64+99
000000000000117b         xor        eax, eax
000000000000117d         call       _isspace
0000000000001182         inc        rbx
0000000000001185         test       eax, eax 

Note that edi is the lower 32 bit of rdi .

However, after patching in Clover, it stucks that line 0000000000001178 . And checking the register printed, register edi is empty. That means something's wrong when executing movzx .

 

If I do not change movsx to movzx, at the panic scene we can see in the above video that register rdi is 0x00000000 ffffffa4 , thus edi is 0xffff ffa4 .

Obviously, the char that caused the problem should be A4. However, I searched APIC but didn't find A4. There is a A4 in DSDT but I have no idea how to modify.

BIOS rom, all of my ACPI tables and modified dsdt/ssdt can be found in attachment.

 

Need Someone's Help

So, here I'm at a very embarrassed stage don't know where's wrong even what to do next... Maybe something's wrong with one of my ACPI tables? Or with AppleACPIPlatform? Or with AppleSMCRTC?

I'm pretty sure I'm not alone with this question, someone willing to dig into it please check my raw ACPI tables, BIOS ROM, modified DSDT/SSDT and my current EFI folder. Thanks very much.

 

BIOS ROM:

x7946.rom.zip

Modified DSDT/SSDT, perfect on 10.10 - 10.12.6:

dsdt+ssdt.zip

Original ACPI Tables:

OriginACPI.zip

Share this post


Link to post
Share on other sites
Advertisement

hey, you can try record your screen and see where it stucked at?

I'm stuck too. Until today I could not pass this part with any version of the clover I tested, and none Beta version of the High Sierra.

I do not know what to test anymore. :(

 

boot with debug=0x100 and -keepsyms=1 and see what exactly caused this problem?

Share this post


Link to post
Share on other sites

Hi Cheneyveron,

 

I feel less alone after your excellent article. Thanks.

I have the same ACPIPlatform problem and I've never succeeded to install High Sierra since the beginning.

 

My system : GA-Z97MX-D3H, i7-4770S and Nvidia GT 640

 

jcds83

Share this post


Link to post
Share on other sites

Hi Cheneyveron,

 

I feel less alone after your excellent article. Thanks.

I have the same ACPIPlatform problem and I've never succeeded to install High Sierra since the beginning.

 

My system : GA-Z97MX-D3H, i7-4770S and Nvidia GT 640

 

jcds83

Sorry to hear and glad to be helpful  :)

Share this post


Link to post
Share on other sites

This screen appeared. I'm not very good with codes, is it the same problem?

attachicon.gifIMG_3020.jpg

hi, from this pic we can't see where's wrong cuz the detailed information was overwritten. You may record your screen and replay to see the error from start

Share this post


Link to post
Share on other sites

hi, from this pic we can't see where's wrong cuz the detailed information was overwritten. You may record your screen and replay to see the error from start

The codes go down very fast, I can not see right with the camera I have. Is there any way to slow down or navigate up and down?

Link vídeo: https://1drv.ms/v/s!AicXim8xlQdCg60TPltyWzBKAP4rBw

 

If there's no other way, I'll try get a better camera tomorrow.

Share this post


Link to post
Share on other sites

The codes go down very fast, I can not see right with the camera I have. Is there any way to slow down or navigate up and down?

Link vídeo: https://1drv.ms/v/s!AicXim8xlQdCg60TPltyWzBKAP4rBw

 

If there's no other way, I'll try get a better camera tomorrow.

Well I see your problem is "isprint".

The cause is that some of the OemId, Signature、OemId、OemTableId or AslCompilerId in your ACPI table contains a char greater than 0x7f.

You can try these methods:

  • drop MATS/BGRT table( or other table ) in Clover "ACPI" -> "Table Dropping"
  • add FixHeaders_20000000 in clover ACPI patch. <- this requires the latest Clover.
  • Modify MATS/BGRT/other table and change the char to lower than 0x80.<- this can be done using a hex editor. Remeber to correct the checksum with the latest Rehabman's Maciasl.

Share this post


Link to post
Share on other sites

@cheneyveron from your video seems you forgot to drop CpuPm table before loading external pm SSDT / auto generate by Clover?

<key>DropTables</key>
<array>
  <dict>
    <key>Signature</key>
    <string>SSDT</string>
    <key>TableId</key>
    <string>CpuPm</string>
  </dict>
</array>

@viniciusmi00, I see you are trying to load another AppleIntelCPUPowerManagement kext (from Clover?), while its already presented on prelinked. 

Share this post


Link to post
Share on other sites

@cheneyveron from your video seems you forgot to drop CpuPm table before loading external pm SSDT / auto generate by Clover?

<key>DropTables</key>
<array>
  <dict>
    <key>Signature</key>
    <string>SSDT</string>
    <key>TableId</key>
    <string>CpuPm</string>
  </dict>
</array>
Ah thanks for mentioning, I realized it too. However After dropping CpuPm the error continues...

Share this post


Link to post
Share on other sites

Have you tried this kext patch? Please follow the links for more detail :) I dont have such of bad tables, so difficult for me to reproduces that issues sorry..

hi! Thanks for your advice~

Sadly I'm not getting "isprint" error, so patch "isprint" may not be helpful :(

I tried to patch "isspace" to force it search in _AcpiGbl_Ctypes instead of __ctype, and modified 0x20 to 0x08 to let "isspace" behave like the function in acpia but it doesn't work cuz I still can't cast it to unsigned char.

My expression is poor, hope you can understand :P

I'm now trying to fix my acpi tables. I'm almost sure that the problem happens inside APIC table.

Share this post


Link to post
Share on other sites

First I thought it was a RAM problem; I kept only two modules. Same crash.

Here my screen capture:

post-319285-0-89194800-1502984129_thumb.jpg

Share this post


Link to post
Share on other sites

 

Well I see your problem is "isprint".

The cause is that some of the OemId, Signature、OemId、OemTableId or AslCompilerId in your ACPI table contains a char greater than 0x7f.

You can try these methods:

  • drop MATS/BGRT table( or other table ) in Clover "ACPI" -> "Table Dropping"
  • add FixHeaders_20000000 in clover ACPI patch. <- this requires the latest Clover.
  • Modify MATS/BGRT/other table and change the char to lower than 0x80.<- this can be done using a hex editor. Remeber to correct the checksum with the latest Rehabman's Maciasl.

I did several tests here. I was able to enter the installer only with "FixHeaders_20000000", did not have to drop tables.

Now the problem is that after installing, when I start the HD is giving an error

"The path /System/Installation/Packages/OSInstall.mpkg appears to be missing or damaged" Shut down the installer ...
I'll try to fix this, and I'll bring more news later.

 

Edit 1: I was able to install the High Sierra. I needed to remove the "EmuVariableUefi.efi". I'm doing some testing now.

Edit 2: My HDs containing Windows 10 are not working. Every time I start Higher Sierra, a warning appears that could not be mounted, and asks if I want to eject or format. (2 HDs in raid and 1 normal).

 

@viniciusmi00, I see you are trying to load another AppleIntelCPUPowerManagement kext (from Clover?), while its already presented on prelinked. 

Yep, now I've removed "AppleIntelCPUPowerManagement.kext" from Clover.

Share this post


Link to post
Share on other sites

I did several tests here. I was able to enter the installer only with "FixHeaders_20000000", did not have to drop tables.

Now the problem is that after installing, when I start the HD is giving an error

"The path /System/Installation/Packages/OSInstall.mpkg appears to be missing or damaged" Shut down the installer ...
I'll try to fix this, and I'll bring more news later.

 

Edit 1: I was able to install the High Sierra. I needed to remove the "EmuVariableUefi.efi". I'm doing some testing now.

Edit 2: My HDs containing Windows 10 are not working. Every time I start Higher Sierra, a warning appears that could not be mounted, and asks if I want to eject or format. (2 HDs in raid and 1 normal).

 

Yep, now I've removed "AppleIntelCPUPowerManagement.kext" from Clover.

Check here:https://pikeralpha.wordpress.com/2017/08/05/osinstall-mpkg-appears-to-be-missing-or-damaged/

First I thought it was a RAM problem; I kept only two modules. Same crash.

Here my screen capture:

hi, have you tried the solution here:http://www.insanelymac.com/forum/topic/326200-new-possibilities-for-x79-appleacpiplatform-panic/?p=2480719

Share this post


Link to post
Share on other sites

Hi Cheneyveron,

 

Thanks for your advices.

  • drop MATS/BGRT table( or other table ) in Clover "ACPI" -> "Table Dropping"   -> Done
  • add FixHeaders_20000000 in clover ACPI patch. <- this requires the latest Clover. -> Done
  • Modify MATS/BGRT/other table and change the char to lower than 0x80.<- this can be done using a hex editor. Remeber to correct the checksum with the latest Rehabman's Maciasl. -> How and where do you modify MATS/BGRT table?

I try whatever to install High Sierra; the installer went a bit further but stalled on disk4s1: the USB key.

 

jcds83

Share this post


Link to post
Share on other sites

Hi Cheneyveron,

 

Thanks for your advices.

  • drop MATS/BGRT table( or other table ) in Clover "ACPI" -> "Table Dropping"   -> Done
  • add FixHeaders_20000000 in clover ACPI patch. <- this requires the latest Clover. -> Done
  • Modify MATS/BGRT/other table and change the char to lower than 0x80.<- this can be done using a hex editor. Remeber to correct the checksum with the latest Rehabman's Maciasl. -> How and where do you modify MATS/BGRT table?

I try whatever to install High Sierra; the installer went a bit further but stalled on disk4s1: the USB key.

 

jcds83

glad it helped. As for USB, I would check the driver for update or seek if the dsdt fits the system :)

U can use a Hex editor or Maciasl to edit MATS/BGRT table.

Share this post


Link to post
Share on other sites

Guys,

 

I'm currently running an X9DAi (Supermicro) with dual Xeons Sandy Bridge and 32Gb, it is working perfectly under 10.12.6... alas for 10.13 I'm getting the same problem with AppleACPIPlatform as you guys.

 

I've already done steps 1 and 2, and I've edited the AppleACPIPlatform binary following Pike's guide but still no dice. So what I did is install High Sierra (last PB) from my Sierra install, then proceeded to replace AppleACPIPlatform with the one from 10.12.6. I know this is not optimal but it gets me passed the Kernel Panic and the _isprint error.

 

Problem is that then I stumble on another problem, screen gets garbled and then the stop sign appears... Maybe some of you have a clue about this ? I'm attaching here my SSD and my config.plist.

 

Any help would be greatly appreciated, thank you already for all the research you guys have been doing.

 

 

 

 

config.plist.zip

SSDT.aml.zip

Share this post


Link to post
Share on other sites

Guys,

 

I'm currently running an X9DAi (Supermicro) with dual Xeons Sandy Bridge and 32Gb, it is working perfectly under 10.12.6... alas for 10.13 I'm getting the same problem with AppleACPIPlatform as you guys.

 

I've already done steps 1 and 2, and I've edited the AppleACPIPlatform binary following Pike's guide but still no dice. So what I did is install High Sierra (last PB) from my Sierra install, then proceeded to replace AppleACPIPlatform with the one from 10.12.6. I know this is not optimal but it gets me passed the Kernel Panic and the _isprint error.

 

Problem is that then I stumble on another problem, screen gets garbled and then the stop sign appears... Maybe some of you have a clue about this ? I'm attaching here my SSD and my config.plist.

 

Any help would be greatly appreciated, thank you already for all the research you guys have been doing.

It is very likely you're facing ACPI tables problems. If you're really stucking at isprint, then method 1 and 2 should work. Since they do not work, you may need to check your ACPI tables.

Share this post


Link to post
Share on other sites

Thank you for the reply, any advice on how to do that and what to look for ?

 

Guess I can extract those with MacIASL I suppose ? but then what should I do ?

 

P.S: Any idea when replacing the AppleACPI why the screen gets garbled ? I looks like the old USB problem, but I'm already fixing that in the SSDT normally...  Here are the screenshots:

 

 

image1.jpg

 

image2.jpg

 

Share this post


Link to post
Share on other sites

Thank you for the reply, any advice on how to do that and what to look for ?

 

Guess I can extract those with MacIASL I suppose ? but then what should I do ?

There're many docs on extracting, decompiling and editing ACPI tables, which you can search on your own. After decompiling, you may find the unprintable char in whatever table.

Share this post


Link to post
Share on other sites

Sure I've already found docs for extracting and such, I'm just a little clueless on what to look exactly for and with what should I replace it.

 

My daily bread is design not code ;) , so I'm cautious on this and prefer to ask.

Share this post


Link to post
Share on other sites

Sure I've already found docs for extracting and such, I'm just a little clueless on what to look exactly for and with what should I replace it.

 

My daily bread is design not code ;) , so I'm cautious on this and prefer to ask.

Even if you daily bread was code, you wouldn't know what to look for and what to replace it with without several hours if not days of research on the ACPI standard and how Apple's ACPI conventions differ. This is not a problem with a 'replace x with y' solution, nor is it a problem that's even been fixed yet really. It's still a strictly programmers problem until it's understood because there are people here that have done things that should fix it but didn't. Right now they are doing the Hackintosh equivalent of prodding the strange x79 High Sierra creature with a stick to see if it moves so you are right to be cautious lol.  :lol:

 

It takes some studying of Apple's existing stuff to learn what youre doing, on top of programming ability... because you're not going to get their own whitepaper specification. A DSDT is in every computer AND Mac, but much like EFI is in every computer, Apple lays waste to the public spec in order to ensure compatibility issues, adds plenty of it's own stuff, and keeps their own private spec to ensure that OSX stays (mostly) on Macs. To make matters worse, your x79/C600 DSDT is likely 3 to 10 times bigger and more complex than Apple's equivalent for whatever Mac is in your SMBIOS... And is practically the only chipset that ever came out and was entirely ignored by Apple, giving vanilla OSX very little knowledge of your device off the bat... with more logic being done by the DSDT (this is just how Intel made X79) to access your much bigger array of connectivity and features... This is why everyone here is using a DSDT when most Hackintoshes in the wild can run 100% DSDT free with kexts. X79 needs a lot of actually reprogramming.

 

Anyway, this is not a stable, functional set of changes that are being made with full understanding of their effects.... this is bare metal 'try it and see even if I may break my computer' reverse engineering, and it's more than likely that by DP2 or release the changes needed will be entirely different and may break hacks with this change implemented anyway. Apple does a lot between DPs, and rolls back half of the changes they make later. 

 

Oh and FYI, anywhere you see people talking about Assembler, run. Run and don't look back, for there is serious geekery afoot.  :hysterical: To read even 1 kext entirely in assembler would probably take a week and you'll only see it when those far more hardcore than I are reverse engineering and researching.

Share this post


Link to post
Share on other sites

Create an account or sign in to comment

You need to be a member in order to leave a comment

Create an account

Sign up for a new account in our community. It's easy!

Register a new account

Sign in

Already have an account? Sign in here.

Sign In Now

  • Recently Browsing   0 members

    No registered users viewing this page.

  • Similar Content

    • By noisegate
      Hi all,
       
      I use this setup (X79 Deluxe - 4930K - HD6870) as an audio rig. It all works fine, I'm only experiencing stability issues with everything USB (audio sound card, MIDI controllers). Logic Pro X keeps randomly losing sync with them.
       
      I installed GenericUSBXHCI (v1.2.11) from the rampagedev X79 dmg. Has anyone successfully used other USB kexts? I mostly use USB 2 ports.
       
      Thanks!
    • By necros
      Hi all, new user here.
      I followed the shilohh guide i7-4930k-asus-rampage-iv-extreme-32gb-ram-gtx-770-4gb-success(and some other guides fresh installing) and everything works great but my cpu is flat at 1.2Mhz. 
      I tried every guide here, in olarila and in "others" but nothing works. Surely I'm doing something wrong but I cannot guess what it is. Also tried nullcpu etc..
      My specs are:
      Rampage IV Extreme
      i7 3930k
      Gtx 980
      Mac OS X 10.12.6
      I made my own SSDT too.
      C1E is enabled.
      I leave my Clover Folder here in case someone can shed some light because I'm starting to be desperate.
      Thank you in advance
      Cheers
       
      CLOVER.zip
    • By yehia2amer
      I want to patch AppleHDA but I cannot find any post talking about ALC3220, I Tried AppleALC (ALC280 - layout-id 11), and AppleHDA Patcher v1.9  (ALC280 - layout-id 5) with no luck.
      I Also Tried VodooHDA but it is very buggy an unstable !
       
      So Now Please find my Codec details below
      ------
      Linux codec_dump.txt 
       
      Codec: Realtek ALC3220 Address: 0 AFG Function Id: 0x1 (unsol 1) Vendor Id: 0x10ec0280 Subsystem Id: 0x102805d4 Revision Id: 0x100003 No Modem Function Group found Default PCM: rates [0x5f0]: 32000 44100 48000 88200 96000 192000 bits [0xe]: 16 20 24 formats [0x1]: PCM Default Amp-In caps: N/A Default Amp-Out caps: N/A State of AFG node 0x01: Power states: D0 D1 D2 D3 CLKSTOP EPSS Power: setting=D0, actual=D0 GPIO: io=5, o=0, i=0, unsolicited=1, wake=0 IO[0]: enable=0, dir=0, wake=0, sticky=0, data=0, unsol=0 IO[1]: enable=0, dir=0, wake=0, sticky=0, data=0, unsol=0 IO[2]: enable=0, dir=0, wake=0, sticky=0, data=0, unsol=0 IO[3]: enable=0, dir=0, wake=0, sticky=0, data=0, unsol=0 IO[4]: enable=0, dir=0, wake=0, sticky=0, data=0, unsol=0 Node 0x02 [Audio Output] wcaps 0x41d: Stereo Amp-Out Control: name="Speaker+LO Playback Volume", index=0, device=0 ControlAmp: chs=3, dir=Out, idx=0, ofs=0 Device: name="ALC3220 Analog", type="Audio", device=0 Amp-Out caps: ofs=0x57, nsteps=0x57, stepsize=0x02, mute=0 Amp-Out vals: [0x3d 0x3d] Converter: stream=5, channel=0 PCM: rates [0x560]: 44100 48000 96000 192000 bits [0xe]: 16 20 24 formats [0x1]: PCM Power states: D0 D1 D2 D3 EPSS Power: setting=D0, actual=D0 Node 0x03 [Audio Output] wcaps 0x41d: Stereo Amp-Out Control: name="Headphone Playback Volume", index=0, device=0 ControlAmp: chs=3, dir=Out, idx=0, ofs=0 Amp-Out caps: ofs=0x57, nsteps=0x57, stepsize=0x02, mute=0 Amp-Out vals: [0x00 0x00] Converter: stream=5, channel=0 PCM: rates [0x560]: 44100 48000 96000 192000 bits [0xe]: 16 20 24 formats [0x1]: PCM Power states: D0 D1 D2 D3 EPSS Power: setting=D0, actual=D0 Node 0x04 [Vendor Defined Widget] wcaps 0xf00000: Mono Node 0x05 [Vendor Defined Widget] wcaps 0xf00000: Mono Node 0x06 [Audio Output] wcaps 0x611: Stereo Digital Converter: stream=0, channel=0 Digital: Digital category: 0x0 IEC Coding Type: 0x0 PCM: rates [0x5f0]: 32000 44100 48000 88200 96000 192000 bits [0xe]: 16 20 24 formats [0x1]: PCM Power states: D0 D1 D2 D3 EPSS Power: setting=D3, actual=D3 Node 0x07 [Vendor Defined Widget] wcaps 0xf00000: Mono Node 0x08 [Audio Input] wcaps 0x10051b: Stereo Amp-In Control: name="Capture Volume", index=0, device=0 ControlAmp: chs=3, dir=In, idx=0, ofs=0 Control: name="Capture Switch", index=0, device=0 ControlAmp: chs=3, dir=In, idx=0, ofs=0 Device: name="ALC3220 Analog", type="Audio", device=0 Amp-In caps: ofs=0x17, nsteps=0x3f, stepsize=0x02, mute=1 Amp-In vals: [0x27 0x27] Converter: stream=1, channel=0 SDI-Select: 0 PCM: rates [0x560]: 44100 48000 96000 192000 bits [0xe]: 16 20 24 formats [0x1]: PCM Power states: D0 D1 D2 D3 EPSS Power: setting=D0, actual=D0 Connection: 1 0x23 Node 0x09 [Audio Input] wcaps 0x10051b: Stereo Amp-In Amp-In caps: ofs=0x17, nsteps=0x3f, stepsize=0x02, mute=1 Amp-In vals: [0x97 0x97] Converter: stream=0, channel=0 SDI-Select: 0 PCM: rates [0x560]: 44100 48000 96000 192000 bits [0xe]: 16 20 24 formats [0x1]: PCM Power states: D0 D1 D2 D3 EPSS Power: setting=D3, actual=D3 Connection: 1 0x22 Node 0x0a [Vendor Defined Widget] wcaps 0xf00000: Mono Node 0x0b [Audio Mixer] wcaps 0x20010b: Stereo Amp-In Control: name="Front Mic Playback Volume", index=0, device=0 ControlAmp: chs=3, dir=In, idx=2, ofs=0 Control: name="Front Mic Playback Switch", index=0, device=0 ControlAmp: chs=3, dir=In, idx=2, ofs=0 Control: name="Rear Mic Playback Volume", index=0, device=0 ControlAmp: chs=3, dir=In, idx=0, ofs=0 Control: name="Rear Mic Playback Switch", index=0, device=0 ControlAmp: chs=3, dir=In, idx=0, ofs=0 Amp-In caps: ofs=0x17, nsteps=0x1f, stepsize=0x05, mute=1 Amp-In vals: [0x80 0x80] [0x80 0x80] [0x80 0x80] [0x80 0x80] [0x80 0x80] Connection: 5 0x18 0x19 0x1a 0x1b 0x1d Node 0x0c [Audio Mixer] wcaps 0x20010b: Stereo Amp-In Amp-In caps: ofs=0x00, nsteps=0x00, stepsize=0x00, mute=1 Amp-In vals: [0x00 0x00] [0x80 0x80] Connection: 2 0x02 0x0b Node 0x0d [Audio Mixer] wcaps 0x20010b: Stereo Amp-In Amp-In caps: ofs=0x00, nsteps=0x00, stepsize=0x00, mute=1 Amp-In vals: [0x00 0x00] [0x80 0x80] Connection: 2 0x03 0x0b Node 0x0e [Vendor Defined Widget] wcaps 0xf00000: Mono Node 0x0f [Audio Mixer] wcaps 0x20010a: Mono Amp-In Amp-In caps: ofs=0x00, nsteps=0x00, stepsize=0x00, mute=1 Amp-In vals: [0x80] [0x00] Connection: 2 0x02 0x03 Node 0x10 [Vendor Defined Widget] wcaps 0xf00000: Mono Node 0x11 [Vendor Defined Widget] wcaps 0xf00000: Mono Node 0x12 [Pin Complex] wcaps 0x40040b: Stereo Amp-In Amp-In caps: ofs=0x00, nsteps=0x03, stepsize=0x2f, mute=0 Amp-In vals: [0x00 0x00] Pincap 0x00000020: IN Pin Default 0x4008c000: [N/A] Line Out at Ext N/A Conn = DIN, Color = UNKNOWN DefAssociation = 0x0, Sequence = 0x0 Pin-ctls: 0x00: Power states: D0 D1 D2 D3 EPSS Power: setting=D3, actual=D3 Node 0x13 [Pin Complex] wcaps 0x40040b: Stereo Amp-In Amp-In caps: ofs=0x00, nsteps=0x03, stepsize=0x2f, mute=0 Amp-In vals: [0x00 0x00] Pincap 0x00000020: IN Pin Default 0x411111f0: [N/A] Speaker at Ext Rear Conn = 1/8, Color = Black DefAssociation = 0xf, Sequence = 0x0 Misc = NO_PRESENCE Pin-ctls: 0x00: Power states: D0 D1 D2 D3 EPSS Power: setting=D3, actual=D3 Node 0x14 [Pin Complex] wcaps 0x40058d: Stereo Amp-Out Control: name="Speaker Playback Switch", index=0, device=0 ControlAmp: chs=3, dir=Out, idx=0, ofs=0 Amp-Out caps: ofs=0x00, nsteps=0x00, stepsize=0x00, mute=1 Amp-Out vals: [0x00 0x00] Pincap 0x00010010: OUT EAPD EAPD 0x2: EAPD Pin Default 0x90170110: [Fixed] Speaker at Int N/A Conn = Analog, Color = Unknown DefAssociation = 0x1, Sequence = 0x0 Misc = NO_PRESENCE Pin-ctls: 0x40: OUT Unsolicited: tag=00, enabled=0 Power states: D0 D1 D2 D3 EPSS Power: setting=D0, actual=D0 Connection: 2 0x0c* 0x0d Node 0x15 [Pin Complex] wcaps 0x40058d: Stereo Amp-Out Control: name="Headphone Playback Switch", index=0, device=0 ControlAmp: chs=3, dir=Out, idx=0, ofs=0 Amp-Out caps: ofs=0x00, nsteps=0x00, stepsize=0x00, mute=1 Amp-Out vals: [0x80 0x80] Pincap 0x0001001c: OUT HP EAPD Detect EAPD 0x2: EAPD Pin Default 0x0221401f: [Jack] HP Out at Ext Front Conn = 1/8, Color = Green DefAssociation = 0x1, Sequence = 0xf Pin-ctls: 0xc0: OUT HP Unsolicited: tag=02, enabled=1 Power states: D0 D1 D2 D3 EPSS Power: setting=D3, actual=D3 Connection: 2 0x0c 0x0d* Node 0x16 [Pin Complex] wcaps 0x40058d: Stereo Amp-Out Amp-Out caps: ofs=0x00, nsteps=0x00, stepsize=0x00, mute=1 Amp-Out vals: [0x80 0x80] Pincap 0x00010014: OUT EAPD Detect EAPD 0x2: EAPD Pin Default 0x411111f0: [N/A] Speaker at Ext Rear Conn = 1/8, Color = Black DefAssociation = 0xf, Sequence = 0x0 Misc = NO_PRESENCE Pin-ctls: 0x00: Unsolicited: tag=00, enabled=0 Power states: D0 D1 D2 D3 EPSS Power: setting=D3, actual=D3 Connection: 2 0x0c* 0x0d Node 0x17 [Pin Complex] wcaps 0x40050c: Mono Amp-Out Amp-Out caps: ofs=0x00, nsteps=0x00, stepsize=0x00, mute=1 Amp-Out vals: [0x80] Pincap 0x00000010: OUT Pin Default 0x411111f0: [N/A] Speaker at Ext Rear Conn = 1/8, Color = Black DefAssociation = 0xf, Sequence = 0x0 Misc = NO_PRESENCE Pin-ctls: 0x00: Power states: D0 D1 D2 D3 EPSS Power: setting=D3, actual=D3 Connection: 1 0x0f Node 0x18 [Pin Complex] wcaps 0x40058f: Stereo Amp-In Amp-Out Control: name="Rear Mic Boost Volume", index=0, device=0 ControlAmp: chs=3, dir=In, idx=0, ofs=0 Amp-In caps: ofs=0x00, nsteps=0x03, stepsize=0x2f, mute=0 Amp-In vals: [0x00 0x00] Amp-Out caps: ofs=0x00, nsteps=0x00, stepsize=0x00, mute=1 Amp-Out vals: [0x80 0x80] Pincap 0x00003734: IN OUT Detect Vref caps: HIZ 50 GRD 80 100 Pin Default 0x01a13040: [Jack] Mic at Ext Rear Conn = 1/8, Color = Blue DefAssociation = 0x4, Sequence = 0x0 Pin-ctls: 0x24: IN VREF_80 Unsolicited: tag=04, enabled=1 Power states: D0 D1 D2 D3 EPSS Power: setting=D3, actual=D3 Connection: 2 0x0c* 0x0d Node 0x19 [Pin Complex] wcaps 0x40048b: Stereo Amp-In Amp-In caps: ofs=0x00, nsteps=0x03, stepsize=0x2f, mute=0 Amp-In vals: [0x00 0x00] Pincap 0x00000024: IN Detect Pin Default 0x411111f0: [N/A] Speaker at Ext Rear Conn = 1/8, Color = Black DefAssociation = 0xf, Sequence = 0x0 Misc = NO_PRESENCE Pin-ctls: 0x00: Unsolicited: tag=00, enabled=0 Power states: D0 D1 D2 D3 EPSS Power: setting=D3, actual=D3 Node 0x1a [Pin Complex] wcaps 0x40058f: Stereo Amp-In Amp-Out Control: name="Front Mic Boost Volume", index=0, device=0 ControlAmp: chs=3, dir=In, idx=0, ofs=0 Amp-In caps: ofs=0x00, nsteps=0x03, stepsize=0x2f, mute=0 Amp-In vals: [0x00 0x00] Amp-Out caps: ofs=0x00, nsteps=0x00, stepsize=0x00, mute=1 Amp-Out vals: [0x80 0x80] Pincap 0x0000373c: IN OUT HP Detect Vref caps: HIZ 50 GRD 80 100 Pin Default 0x02a19030: [Jack] Mic at Ext Front Conn = 1/8, Color = Pink DefAssociation = 0x3, Sequence = 0x0 Pin-ctls: 0x24: IN VREF_80 Unsolicited: tag=03, enabled=1 Power states: D0 D1 D2 D3 EPSS Power: setting=D3, actual=D3 Connection: 2 0x0c* 0x0d Node 0x1b [Pin Complex] wcaps 0x40058f: Stereo Amp-In Amp-Out Control: name="Line Out Playback Switch", index=0, device=0 ControlAmp: chs=3, dir=Out, idx=0, ofs=0 Amp-In caps: ofs=0x00, nsteps=0x03, stepsize=0x2f, mute=0 Amp-In vals: [0x00 0x00] Amp-Out caps: ofs=0x00, nsteps=0x00, stepsize=0x00, mute=1 Amp-Out vals: [0x00 0x00] Pincap 0x00003734: IN OUT Detect Vref caps: HIZ 50 GRD 80 100 Pin Default 0x01014020: [Jack] Line Out at Ext Rear Conn = 1/8, Color = Green DefAssociation = 0x2, Sequence = 0x0 Pin-ctls: 0x40: OUT VREF_HIZ Unsolicited: tag=01, enabled=1 Power states: D0 D1 D2 D3 EPSS Power: setting=D3, actual=D3 Connection: 2 0x0c* 0x0d Node 0x1c [Vendor Defined Widget] wcaps 0xf00000: Mono Node 0x1d [Pin Complex] wcaps 0x400400: Mono Pincap 0x00000020: IN Pin Default 0x40400001: [N/A] SPDIF Out at Ext N/A Conn = Unknown, Color = Unknown DefAssociation = 0x0, Sequence = 0x1 Pin-ctls: 0x20: IN Power states: D0 D1 D2 D3 EPSS Power: setting=D3, actual=D3 Node 0x1e [Pin Complex] wcaps 0x400781: Stereo Digital Pincap 0x00000014: OUT Detect Pin Default 0x411111f0: [N/A] Speaker at Ext Rear Conn = 1/8, Color = Black DefAssociation = 0xf, Sequence = 0x0 Misc = NO_PRESENCE Pin-ctls: 0x40: OUT Unsolicited: tag=00, enabled=0 Power states: D0 D1 D2 D3 EPSS Power: setting=D3, actual=D3 Connection: 1 0x06 Node 0x1f [Vendor Defined Widget] wcaps 0xf00000: Mono Node 0x20 [Vendor Defined Widget] wcaps 0xf00040: Mono Processing caps: benign=0, ncoeff=107 Node 0x21 [Vendor Defined Widget] wcaps 0xf00000: Mono Node 0x22 [Audio Selector] wcaps 0x300101: Stereo Connection: 8 0x18* 0x19 0x1a 0x1b 0x1d 0x0b 0x12 0x13 Node 0x23 [Audio Selector] wcaps 0x300101: Stereo Connection: 6 0x18* 0x19 0x1a 0x1b 0x1d 0x0b Node 0x24 [Vendor Defined Widget] wcaps 0xf00000: Mono  
      Jarvis report:
      Hardware info: - ATI R6xx HDMI (1002:aa01) - Controller 1002:aa30 (sub-ven:174b:aa30) - Driver: VoodooHDA SSDT-4.aml succesfully extracted! DSDT.aml succesfully extracted! SSDT.aml succesfully extracted! SSDT-1.aml succesfully extracted! SSDT-3.aml succesfully extracted! SSDT-2.aml succesfully extracted! Found "Device (HDEF)" in DSDT.aml Found property "layout-id" in DSDT.aml Found 1 occurennces of "layout-id" in ioreg, not sure what's will be for HDEF.. Found unsupported "layout-id = 11" in ioreg, will not work using Mirone's patches!!! No "Device (HDAU)" was found inside your ACPI tables. That is normal w/o a PCI Video card or w/o an HDMI connector on it! AppleHDA Patcher.app only supports (if patched by Mirone): layout-id 2 for laptop's, layout-id 5 for Desktop's with 3 connectors (pink, green and blue), layout-id 7 for Desktop's with 5/6 connectors (gray, black, orange, pink, green and blue), layout-id 9 for Desktop's with 5/6 connectors (gray, black, orange, pink, green, blue, CodecAddress:2) aDummyHDA.kext works only is /System/Library/Extensions. Laptop's may be need the provided ACPI Patch such system_IRQ.txt to be functional. HDAEnabler.kext maybe usefull if you don't want to edit your ACPI table or the Clover's config, or the org.Chameleon.Boot.plist. CodecCommander.kext is usefull in the case you have no sound after waking from sleep. Generated kexts should be installed in a proper way, repairing its permissions and rebuilding the cache: dragging kexts into Pandora's Box.app window will help you to do that!  
      Chipset Name: Intel Corporation C600/X79 series chipset High Definition Audio Controller (rev 06)
      Codec Name: Realtek ALC3220
      Linux Codec Dump : codec_dump.txt
      codec_dump.txt.svg
      Patched DSDT: DSDT.aml
       
       
      Thanks
       
    • By murvold
      GA-X79-UP4; i7 3820; 32gb RAM; Nvidia 970   Trying to upgrade my working Sierra 10.12.6 to High Sierra 10.13.3. My previous hack is based on Rampagedevs x79.dmg. I've tried several combinations of dropping MATS/BGRT table from ACPI fixes which is recommended for Gigabyte boards and also checked the "fix headers" option there. I've included my zipped Clover folder from EFI. Each try ends with Mach Reboot. Any help appreciated and thank you in advance.
    • By Peerke
      (Mistakenly posted in 'Installation Guides' at first)
       
      Hi,
       
      A couple of weeks back I took the plunge and upgraded my system from Yosemite (10.10.5) to Sierra 10.12.6. Reason for doing that was that I wanted to upgrade my graphics card from a GTX 960 to a GTX 1060. I followed Rampagedev's procedure and used his DMG to upgrade. I also installed the nvidia web driver 378.05.05, and I installed an Intel 750 PCIe NVME SSD, using Pikeralpha's NVME patch and included the NVME drivers from a Gigabyte Z97 board on the GA-X79-UD3, as the X79 board originally does not support NVME. 
       
      So, I can boot from the Intel SSD, but it takes about 3 or random 4 kernel panics and reboots before I get to a login prompt. Once logged in everything works fine and the system is stable. I saw the same behaviour when everything was still on a SATA SSD, so I do not suspect the NVME drivers and patches to be the culprit. The KPs can happen at different stages during boot, sometimes even when I am logging in. But once logged in, everything is ok.
       
      Another thing that bothers me is USB3. I installed USBXHCI_FL1009.kext, also from the Rampagedev DMG, but the results are flaky. A USB3 USB-stick is recognised, as is my card reader, but an external (bus-powered) USB3 drive from Seagate is completely ignored when inserted. I did turn off USB3 during the upgrade, but it is switched back on now.
       
      The original install was with Mavericks, and I upgraded that too to Yosemite. I never tried a clean install as that would take a lot of work to migrate and relicense all my apps. 
       
      So, in terms of system goodies:
      Mobo: Gigabyte GA-X79-UD3
      CPU: Intel 4930k
      OS: Sierra 10.12.6
      Nvidia web driver: 378.05.05
      GPU: MSI GTX1060 3GB
      Boot drive: Intel 750 NVME PCIe SSD
      Clover: 4220
       
      Anyone that can help to solve the kernel panics and the USB3 issue?
       
      Enclosed my complete EFI folder, IOreg, ACPI tables and kextstat.txt.
       
      Any help is appreciated. Thanks.
        Toms MacPro.ioreg.zip
      EFI.zip
      Send me Toms MacPro.zip
×