Are other Telegram and Reason users reporting similar problems even when running them on real Macs? In other words, perhaps those apps need to be updated by their developers?
Good information about Logitech Gaming Software and glad to see the Focusrite Clarett 2Pre is working properly!
Many thanks for your answer.
Yes, maybe you are right, I think everything happened after the last Telegram update. I'll be waiting for the next one.
I am also running an old 2012 15" Retina Macbook Pro on the same version of Mojave and never had those issues with Telegram nor Reason. The kernel panic didn't happen again and Telegram was not running, so I'll see if it happens again in the next days and keep you posted.
Hello @dolgarrenan,
Many thanks for the info about Telegram using hardware acceleration. Does "disabling GPU hardware acceleration" means disabling the animations in the "Performance" settings?
1. My SSD is a Samsung 970 nvme 1TB that I got a week ago , it is definitely not broken
2. Why?
3. you cannot install Catalina on a non apfs formatted drive so of course it is
4. 10.15.4 is the cause of these problems the best solution is to find 10.15.3 and follow the CaseySJ Catalina fresh install mini guide , what I did worked for me , it might not work for others , someone might feel funny about continuing despite the errors , I am experiencing no problems
1. My SSD is a Samsung 970 nvme 1TB that I got a week ago , it is definitely not broken
2. Why?
3. you cannot install Catalina on a non apfs formatted drive so of course it is
4. 10.15.4 is the cause of these problems the best solution is to find 10.15.3 and follow the CaseySJ Catalina fresh install mini guide , what I did worked for me , it might not work for others , someone might feel funny about continuing despite the errors , I am experiencing no problems
I have this problem with a broken format apfs. With a new format with another computer in external I have solve to install correctly I hope it is same for you. It is not sure.
I'd like to create a Thunderbolt DROM Micro-Guide for Gigabyte Z390 AORUS Xtreme. Can you please share your Thunderbolt SSDT? You may replace the first 9 bytes of ThunderboltDROM with this (to protect your UID):
If System Information --> Thunderbolt says No drivers are loaded, then this does not apply to you.
Benefits / Purpose:
Just as your Mac's serial number is unique and your Ethernet card's MAC address is unique, we need to assign a unique ID to the Thunderbolt controller.
Thunderbolt Ethernet Bridge and Target Disk Mode require this procedure.
Most eGPUs require this procedure.
QNAP Thunderbolt-based NAS units require this procedure.
Other Thunderbolt-based storage and NAS systems may require this procedure as well.
This procedure may improve overall compatibility with a wider set of Thunderbolt devices.
Procedure:
There are two options for configuring Thunderbolt DROM. Choose one of the two methods.
Option 1: Web GUI Method (credit: @Inqnuam)
This method is the easiest to use.
Thunderbolt DROM will be customized for you using a randomly generated Unique ID (UID) and all checksums will be auto-computed.
A complete Thunderbolt SSDT (with the new DROM) will be presented on screen and it will also be copied to the clipboard for you.
Download and run MaciASL, create new file (File --> New) and paste the clipboard.
Then save the file in ACPI Machine Language (AML) format: File --> Save As... and choose ACPI Machine Language from the pop-up menu.
Give the file an appropriate name such as: SSDT-TB3-DROM-HOTPLUG.aml.
Any name is okay as long as it begins with SSDT-
However, download SSDT-DTPG.aml from the bottom of this guide.
Both SSDT files must be copied to the CLOVER/ACPI/patched folder (for CLOVER users) or OC/ACPI folder (for OpenCore users).
Option 2: Superuser Method (credit: @joevt)
Please see this guide for advanced users.
Option 3: Manual Method
Specify a new Unique ID (UID) in the 5 green bytes below (0x11).
Replace the 5 green numbers below with 5 randomly selected hex numbers.
Now click here to visit an online CRC calculator and configure it as shown:
Copy the boldfaced bytes below (bytes 2-9 after replacing the green bytes with your own values) to clipboard and paste them into the Bytes field as shown and click CRC button:
Enter the CRC-8 checksum into the 1st byte of Thunderbolt DROM as shown in red below.
Save this into your Thunderbolt SSDT, in the NHI0._DSM method.
Optional: Byte #2 below (between 0x88 and 0x11) represents the Thunderbolt Bus ID. If you have multiple Thunderbolt controllers, assign a different bus to each one. If you change this byte, please re-compute the CRC-8 checksum.
The first byte of ThunderboltConfig should then be changed to the same Bus ID.
"ThunderboltDROM",
Buffer (0x65)
{
0x88,0x00, 0x11, 0x11, 0x11, 0x11, 0x11, 0x00,
0x00, 0x2D, 0xEA, 0x01, 0xBD, 0x01, 0x58, 0x00,
0x01, 0x00, 0x10, 0x00, 0x01, 0x00, 0x08, 0x81,
0x82, 0x02, 0x82, 0x00, 0x00, 0x00, 0x08, 0x82,
0x92, 0x01, 0x82, 0x00, 0x00, 0x00, 0x08, 0x83,
0x82, 0x04, 0x82, 0x01, 0x00, 0x00, 0x08, 0x84,
0x92, 0x03, 0x82, 0x01, 0x00, 0x00, 0x05, 0x85,
0x09, 0x01, 0x00, 0x05, 0x86, 0x09, 0x01, 0x00,
0x02, 0x87, 0x03, 0x88, 0x20, 0x03, 0x89, 0x80,
0x02, 0xCA, 0x02, 0xCB, 0x0D, 0x01, 0x41, 0x70,
0x70, 0x6C, 0x65, 0x20, 0x49, 0x6E, 0x63, 0x2E,
0x00, 0x0C, 0x02, 0x4D, 0x61, 0x63, 0x69, 0x6E,
0x74, 0x6F, 0x73, 0x68, 0x00
},
CRITICAL WARNING:
Do not copy and paste the text above into MaciASL. Instead, copy-and-paste from the spoiler below. Failure to do so will be catastrophic.
If you see 2 "receptacles" listings and both show Link Speed of 40 Gbps, then everything is okay and there's nothing more to do.
However, if you see 4 "receptacle" listings, please use the secondary ThunderboltDROM in the spoiler below and replace the first 9 bytes with the bytes you modified by following the above "Procedure".
@CaseySJ it's so good seeing the repository and DROM guides growing. Great work here!
I have a new Apollo x16 coming in today and I'm going to test daisy chaining it with my Apollo Twin mk2. I'm not sure if thats been confirmed yet but I see no reason for it not to work. Exciting!
CaseySJ, as part of my upgrade to 10.15.4 I decided to go ahead and bring my system up to snuff with a couple of the items that have been added in the past recent months. These are enabling native NVRAM and move from using AptioMemoryFix.efi to OcQuirks.efi.
The move to native NVRAM went off without a problem. No issues
However testing OcQuirks has produced less than favorable effects.
My test was to build a USB stick with my current Clover EFI on it. (this is all that is on this USB stick). I then tested to make sure I could boot and get to Clover and select my "Macintosh HD" for booting MacOS, this all works no problem. I then modified the USB stick EFI by removing AptioMemoryFix.efi and adding OcQuirks.plist, OcQuirks.efi, and FwRuntimeServices.efi to my EFI (clover/drivers/efi). Booting off this stick now hangs at the Gigabyte "Insist on Ultra Durable" Logo (2nd display of the Logo without the menu options at the bottom of the screen for entering the BIOS or boot menu). I have also tried the OcQuirks-4.efi and corresponding FwRuntimeServices.efi file and these too produce a hung machine.
Any thoughts as to why I might be failing where so many others have had great success?
This site uses cookies to help personalise content, tailor your experience and to keep you logged in if you register.
By continuing to use this site, you are consenting to our use of cookies.
