"ThunderboltDROM",
Buffer (0x65)
{
0x88, 0x00, 0x11, 0x11, 0x11, 0x11, 0x11, 0x00,
0x00, 0xC5, 0x0A, 0x25, 0xCB, 0x01, 0x49, 0x00,
0x49, 0x18, 0x04, 0x00, 0x62, 0x02, 0x08, 0x81,
0x80, 0x02, 0x80, 0x00, 0x00, 0x00, 0x08, 0x82,
0x80, 0x02, 0x80, 0x00, 0x00, 0x00, 0x02, 0x83,
0x0B, 0x84, 0x20, 0x01, 0x00, 0x3C, 0x00, 0x00,
0x00, 0x00, 0x00, 0x05, 0x85, 0x50, 0x00, 0x00,
0x09, 0x01, 0x41, 0x53, 0x52, 0x6F, 0x63, 0x6B,
0x00, 0x15, 0x02, 0x5A, 0x33, 0x37, 0x30, 0x20,
0x47, 0x61, 0x6D, 0x69, 0x6E, 0x67, 0x2D, 0x49,
0x54, 0x58, 0x2F, 0x61, 0x63
},
Please try the SSDT in the micro-guide above. I've changed some device-property information.
Have you checked whether hardware acceleration is enabled for HEVC and H.264? We can use VideoProc to check this. Simply search this thread for posts from me containing the keyword 'VideoProc'.
Have you seen posts 18 and 20 here:
www.tonymacx86.com
What you're describing in the first paragraph is the need to pressing 2 or 3 keys to wake from sleep. I always press 3 keys (space bar) with a few seconds between each. Have you tried setting darkwake=0 in Boot Arguments? That may allow wake with single keypress.
The screenshot shows normal behavior. Are you experiencing any technical problems with Thunderbolt?
Update on Damaged Asus ThunderboltEX 3
Last week I damaged the Winbond chip on my Asus ThunderboltEX 3 add-in-card while attempting to force-flash a modified Thunderbolt firmware. This was before creating the circuit with a 47uF capacitor and 2K Ohm resistor. Had I used that circuit at the time, I would not have damaged the chip.
Nevertheless, to turn the loss into a gain I decided to desolder and replace the damaged chip. First step: to order a set of replacement chips and desoldering materials, all of which arrived over the past couple of days.
Status update:
The Winbond W25Q80DV comes in two package sizes:
The following boards use the larger W25Q80DVSIG:
- W25Q80DVNIG
- W25Q80DVSIG
View attachment 457579
- Gigabyte Designare Z390
- Gigabyte Z390 AORUS Xtreme
- Gigabyte GC-Titan Ridge
- Asus ThunderboltEX 3
It was easy to flash the standalone chip, but it could only be gripped properly by the Pomona 5250. The cheap clip that accompanies most CH341a Programmers placed too much pressure, bending some of the pins.
Next the existing flash chip on the Asus add-in-card had to be desoldered:
View attachment 457583
- A clean solder tip is essential. I had to replace a worn tip that was merely evaporating the solder instead of melting it into tiny beads.
- Applied liquid flux and used ChipQuik at a temperature of about 250 C. After about 4 or 5 strokes on each side, the chip glided off easily. No hot air this time.
Soldering the replacement was fairly easy because of the relatively wide spacing between pins.
View attachment 457584
So after all that, did it work? No!
The soldered-on chip does work and is readable and writable by the Raspberry Pi, but it's possible that other components were damaged. Will make one more attempt to repair the board.
Meanwhile, the replacement Asus ThunderboltEX 3 arrived today and it's easily readable and programmable with the 47uF / 2K Ohm circuit.
i have same problem even my installation
Native NVRAM is the way to go! But keep in mind that MSR 0xE2 will get locked each time new BIOS is flashed to the motherboard. It may also get locked under some circumstances when CMOS Reset is performed. So be sure to keep the "grub" USB flash disk handy in case it's necessary to unlock MSR 0xE2 in the future.
