- Joined
- May 15, 2020
- Messages
- 1,306
- Motherboard
- Gigabyte Z390 Designare
- CPU
- i9-9900KF
- Graphics
- RX 5700 XT
- Mac
-
exactly!How do I add the agdpmod=pikera? Like after the alcid=1?
exactly!How do I add the agdpmod=pikera? Like after the alcid=1?
!!! DSM2 dropped the Alpine Ridge Thunderbolt Data Sheet at #1,319Thanks for this. Too often I see these magical firmware patches with no explanation of what changed or why. With proper documentation of each change like this, these patches can be built upon by others.
For my Mac Pro and other cases, my current plan is to work on a software only solution that doesn't require flashing. First step is trying to boot Ubuntu after enabling Alpine Ridge in EFI Shell.
Yes I was afraid that was going to happen because Apple has introduced new capabilities in APFS.
@byteminer — have you tried installing Big Sur public beta?
@CaseySJ Thansk for looking into it.If you post the IOReg file from your system and the Thunderbolt SSDT, I can get a better idea of what may be happening.
Please try the slightly modified SSDT attached. IOReg shows that the previous SSDT was not loaded because it's referring to a non-existent PXSX device. On PEG2 we have instead PEGP. The attached version makes this change.@CaseySJ Thansk for looking into it.
First here is my IOReg screenshot
View attachment 485682
Next attachment is my SSDT
Thank you very very much!
That checksum is correct....
Running it under Mojave, I have the following:
sha256sum -b DESIGNARE-Z390-NVM33-Elias64Fr.bin
02427ca11e3ea155db5bbfac6ecc0b76d467f05678436b8b6b375bf35acdd222 *DESIGNARE-Z390-NVM33-Elias64Fr.bin
...
Please try the following:Thank your for getting back! Here are the answers to your questions:
- The system enters sleep. Upon key press or mouse move it does a partial wake (fans spin up, lights turn on, but monitor(s) remain black)
- This does happen under Windows as well (after I send the PC in hibernation)
- No, I have not tried a CMOS Reset
- Unfortunately, I no longer have the old 19" monitor
- The old monitor (Dell 1909W) had a DVI-D connector. I used a DVI-to-HDMI cable, that was plugged in the video card.
- The new monitor is Philips 278E1A 27". It's exactly the same make/model as my other one, that I used from day one. I'm plugging it in the same HDMI port that was used for the old monitor. And I'm using the original HDMI cable that came with the monitor. It is certified.
I tried the scenario, without removing it, and then after removing it. The outcome was the same - Monitors do not light up. And yes, I did replace the original USB SSDT (SSDT-UIAC-DESIGNARE-Z390-V7.aml)
Hello, sorry the update isn't ready for today, but im giving you a little screenshot. This will be the final version of HackinDROM...
Good observation. It is correct, however. When we specify strings in quotes, we add one extra byte to the buffer because strings are terminated with a hidden 0x00 (or NULL). But when we enumerate the bytes one by one, then we are responsible for specifying the final 0x00 if needed.@casey & Co: the buffer 0x7b have exact 123 bytes, but other (0x17, 02d, etc) buffers always have 1 byte less. Is this ok?