Razer Core X Chroma / MacOS / Ethernet
Hello eGPU.io community!
My new eGPU is all set up and I am exploring the potential benefits in MacOS. I am running a Vega 64 in a Razer Core X Chroma enclosure. I chose the Chroma over the standard Core X because of the I/O. Right now, USB seems to be functioning on a rudimentary level. Stress tests to come.
Trying to connect to my home network over Ethernet has been a fail, however. Does anyone out there have any advice on using Gigabit Ethernet / Core X Chroma and MacOS? I am running Catalina 10.15.5
I'm sorry if this thread is redundant and this has been discussed elsewhere!
Thanks a ton!
@mo_oi, is it working for you?
I tried the driver from Razer dated July 2019 and as soon as I plug in an ethernet cable, my mac can't connect to anything; pings to the default gateway throw a "host is down" or "request timeout" - I tried downloading the updated driver version from ASIX, and it was able to connect to the 'net, but only for about a minute before dropping out.
I'd be interested to hear if you had more luck!
Sorry, I don’t use the Ethernet port on Mac.
My conclusion is nothing solves that problem now, sorry.
I googled some sites and many people complained about the same problem.
One Japanese blog mentioned about the same problem in detail.
He says ASIX new driver 2.16.0 (30/01/2020) make things a bit better, but large file transfer causes errors.
I have the similar setup. The large file transfer issue seems more related to the Catalina OS itself rather than the ethernet port on the Razer Core X.
Have a read on the below.
Quick update on mac ethernet on the core x chroma, ASIX has posted beta drivers for big sur using driverkit instead of a kernel extension. I haven't tried it, and it looks like it requires disabling SIP for now. On Razer's support page for the Core X Chroma, They no longer have a link to the (non-working) driver, but a vague statement about contacting support for a "repair". I was curious what this meant so I contacted Razer support via chat today. It took the rep a while to figure out what I was talking about and his answer was basically that razer was still working on a solution and to check back later.