Search results

I just found this modified version of FakeSMC with GPUSensor plugin (and all the others) Confirm it works with my Radeon VII, I can see GPU Die Temp in iStat Menu now.

The performance of this card is so much BETTER with Windows, based on the FPS/stability while gaming. Since AMD already discontinued this card, I don't think  or AMD would improve the driver anymore. I wish that AMD would sell Radeon Pro Vega II directly to consumers after Mac Pro releases.

I have system freezes for a few seconds (10s-ish) when playing Dota2 (basically the only GPU heavy app I use) all the time from 10.14.5 to 10.15.0 Not sure if this is a macOS issue or it is Dota2 to blame. Geekbench 5 gives about 50,000 for OpenCL, the best I got was 60,000...

In case anyone's having issues getting HiDPI to work under 10.15, here is the link to your solution: https://egpu.io/forums/mac-setup/missing-scaled-resolution-w-vega-64-tb3-lg-34wk95u-w/ One thing worth to notice is that if you're getting Read-Only error even after csrutil disable, just do...

I don't remember having any special hacks/kexts installed. I bought the monitor and plug it directly to the DP on 1080Ti it didn't work, then I bought the Thunderbolt card and it's still not running at full resolution until last week. I saw the new updates for Webdriver and figured maybe...

Well, after sitting at the corner for three months, I finally light up this 5k2k baby successfully. It is running at 3840x1620@60hz right now. (Perfectly fine with 5120x2160 if you're curious) I have 1080ti with two DP connected to the Thunderbolt mini-DP (Gigabyte GC-ALPINE RIDGE (rev. 2.0))...

Quick update: tried Thunderbolt port but got no luck. I connect the two DP from the GPU to my thunderbolt card and connect the monitor to the Thunderbolt port, and here's what I got: system believes I have TWO monitors connected, LOL

Well, it turns out the BIOS version for GB Z370 Gaming 7 with the same description is F7. After downgrading to F7, still the same: all video output's gone if I try to connect after sleep.

Not sure if this is related to the BIOS version, I'm on F11 right now. Will try downgrade to F10 later.

I'm using the two .aml files from ssdt-z370-tb3hp.zip. Before using those, the system cannot detect my thunderbolt device after sleep. (I'm using LunaDisplay, which turns iPad into a second display.) Now the system can detect the device but when I try to connect with my iPad, my main monitor...

Got my 34WK95U today, connect with the Displayport cable came with the monitor. (FYI. It won't boot with Displayport 1.4, had to switch to 1.2 and update firmware for 1080Ti under WIndows to fix that.) I can see 5120x2160 option but can only get 30Hz with that. Lower resolutions can go up to...

High five mate! My 960 PRO's firmware version is 2B6QCXP7, and it's the latest firmware Samsung provides on their website (link: https://www.samsung.com/semiconductor/minisite/ssd/download/tools/ ).

I never had TRIM enabled via neither Clover patch nor terminal command, but since it's an NVMe SSD, TRIM is enabled by default and can not be turned off. With my old 950PRO, the verbose log will show "failed to finish all transactions in sync()! (err 16)" and then stuck there for like a minute...

I used 'dd' to clone the whole EFI partition from the old one. So that's the same as drag&drop the old one.

Okay guys, so I had this slow boot problem as well. Resolved by replacing the old 960PRO(1TB) with the new 970PRO(1TB), with exactly the same clover configs. The boot time has backed to normal: 1min30sec --> 10sec. Hope this helps. :)

So my 970PRO arrived today, transferred everything from the old 960PRO with Migration Assistant. Guess what. The boot time is now around 10s. XD So I believe the 960PRO lacks some functionalities required by APFS and causes a "long boot" time(over 1:30) FYI. Both 970/960 I'm using are 1TB...

Anyway, I've placed an order for a 970 PRO, hope it works

Guess it isn't, I just had HFSPlus.efi in Clover, still getting exact 1:30 boot time. :(

I don't have HFSPlus.efi nor VBoxHfs-64.efi in my Clover folder. Just did a quick search and Clover wiki says it's HFS+ file system driver that's necessary for booting. I'm all in APFS so I guess I don't need that, right?

Hmmm... That's odd, based on the thread I posted above, not only a few people have this long boot issue with 960 PRO/EVO drives.