kgp
Retired
- Joined
- May 30, 2014
- Messages
- 6,743
- Motherboard
- ASUS WS X299 Sage 10G
- CPU
- i9-7980XE
- Graphics
- Vega 64
- Mac
- Mobile Phone
@kgp I'm not gonna reinstate again how grateful I am for the contribution you gave to this community. Pretty sure I expressed it many times. This being said, challenging you is not always easy. Even if what you write is incorrect.
I have no doubt that your quick responses intimidate many people and block them from bringing valuable informations to us. You ll understand why I'm saying this in a minute...
As a response to your last post, I can only state what I experienced for myself. Few months ago, when I was still a young Padawan, I did not know anything about SSDTs. Looking at mi IOReg , you thought I had changed my GPU PCIe slot which was never the case. ( Threads are below ) Only the Firewire card removal created the changes in IOReg. Thankfully some people evolve so I find out on my own what was the issue with sleep, ( and the changes in IoReg ) after many hours of study & debugging. It was neither GPU, USB Kext, SSDT or Bios related. Ever more, the solution for wake after sleep, was the complete opposite of something you stated in your guide and reaffirmed many times in last past months in several threads. I know you don't like to be challenged, that's why I'm waiting for all your tests and SSDTs with @nmano to be over ( they are essential to debugging his issue) before I'll bring a solution that I believe will work for him as it did for me.
I do not agree with your ways of diminishing the work of others, I do not find it constructive or emotionally intelligent. Only my opinion.
Good day to you.
My friend. Going trough your post #10,856, in all IOREG.saves either your Vega or RX580 appear under PC02.BR2A.
It is obvious, that when replacing a Vega with a RX580 in the same slot, the amount of PCI bridges changes. The same happens when you use a Nvidia. If you look to the Github library, and you inspect SSDT-X299-RX560.aml, SSDT-X299-RX580.aml, SSDT-X299-Vega56.aml, SSDT-X299-Vega64.aml, SSDT-X299-Vega-Fontier.aml and SSDT-X299-Radeon-VII.aml for Slot-1 of my ASUS Prime X299 Deluxe, you will see that I carefully account for respective changes in implemented PCI bridges.
Thus, so far in the recent posts above we two are talking about two different things, I guess. While I am referring to
PC02.BR2A, which does not change, you might refer to the varying bridges.
Now, as @nmano continues using the same Vega in the same slot all the time, neither PC02.BR2A nor the amount of implemented PCI bridges do vary. The same BTW also states for all other hardware and respective SSDTs we already removed for testing purposes.
If you carefully compare the GPU ACPI table of his last IOREG save in post #2,071 with my original X299-SL05-GFX0-HDAU-ARPT.aml, you will see that the latter is still fully valid but @nmano apparently committed some error by removing the ARPT part from the X299-SL05-GFX0-HDAU-ARPT.aml implementation, thus the latter is not even loaded at boot, which is clearly visible in both IOREG.save and PCI screenshot!
So far we removed firewire, additional USB and BT/WIFI adapter and all respective SSDT implementations and sleep/wake is still not working, although @nmano also seems not able to explicitly state what with sleep/wake is exactly not working.
Thus, if after fixing @nmanos actual error in X299-SL05-GFX0-HDAU-ARPT.aml, sleep/wake is still not working despite a proper ACPI and PCI implementation, I would not know what else to change.
We then would have reached a minimum system configuration where sleep/wake does not work either although also with the firewire, additional USB and BT/WIFI adapter everything was properly implemented and fully working, despite the supposed sleep/wake problem. I verified all his IROEG.saves and PCI snapshots, where everything was fully implemented as expected.
Thus, if you think that in case his system would not even sleep/wake with the minimum hardware configuration (firewire, additional USB and BT/WIFI adapter removed) once X299-SL05-GFX0-HDAU-ARPT.aml is properly implemented, and you would be able to make it sleep/wake by once more adding firewire, additional USB and BT/WIFI adapters and respective SSDTs, please go ahead.
Anyway.. awesome progress you made from a young Padawan on 7 October 2018 to somebody who questions, examines and teaches Yoda in February 2019. Although, you should not commit the same mistake as Darth Vader and think that you are now Yoda and I am now the Padawan.
I am convinced that I properly implemented all SSDTs for @nmano, and I repeatedly and iteratively verified all SSDT implementations by his resulting IOREG.save and PCI screenshots and it was definitely not a change in the ACPI path or ACPI replacements I would not have considered at any time. Carefully read all recent related posts before jumping permanently in here with wild assumptions, disturbing my work. I would prefer if my work here else could remain uncommented until it is finished. It is difficult enough to make @nmano do what I am asking for. Any useful precise corrections and comments are highly welcome though, if really adequate and necessary at the time being.
If I could have managed his system insitu or at least via TV, the system would be already perfectly working, I am sure. But as everything has to be done here in this forum by writing only, I have to deal with a somehow limited information and I depend on the necessity that @nmano also does and only does what I ask for, actually everything becomes much more difficult.
Thus please, let me peacefully finish my work here with @nmano without further comments, and as soon I finish, you can do what you ever want. Anyway, I only started to help him in his current issue to avoid any further escalation of the already ongoing and not very helpful discussion between you and him at this time. BTW.. If you think that I have nothing else or anything better to do with my real life than permanently helping people along my threads, you are definitely wrong. I would have appreciated if you would have taken my workload also in this issue right from the very beginning but you didn't.. Thus please, my friend ....
KGP
P.S. Only this apparently necessary justification took me another hour of my time. Not only that I try to permanently help others instead of just distributing theoretical and hypothetical discussions, it seems that I have now also to justify and defend each of my individual attempts and approaches or related skills and knowhow. Appreciated.
Last edited:
