Warning: Some posts on this platform may contain adult material intended for mature audiences only. Viewer discretion is advised. By clicking ‘Continue’, you confirm that you are 18 years or older and consent to viewing explicit content.
I don’t have the actual mini on hand right now, its serving as a home server and I am on vacation. I’ll check when I get back. Btw, what version of OSX/macOS are you running on? I had no problem with Catalina and even Ventura (OpenCore).
I said goodbye to MacOS after PTP stopped working for Android phones (Photos, Image Capture, Lightroom), and the Android File Transfer (MTP) app broke around the same Mac OS upgrade. I would assume they eventually fixed some of that, but I just don’t have any trust left in Apple after all that. My mini is running Windows 10 now, with the bootcamp drivers.
edit: I think Catalina was the last release I had used on it before wiping it for Windows. I definitely went up to Mojave, but pretty sure I tried Catalina too.
I’m genuinely glad for you and the other poster here who got by unscathed. Maybe we have slightly different chipsets. Mine is bcm57766/b57nd60a.
I don’t have the actual mini on hand right now, its serving as a home server and I am on vacation. I’ll check when I get back. Btw, what version of OSX/macOS are you running on? I had no problem with Catalina and even Ventura (OpenCore).
I said goodbye to MacOS after PTP stopped working for Android phones (Photos, Image Capture, Lightroom), and the Android File Transfer (MTP) app broke around the same Mac OS upgrade. I would assume they eventually fixed some of that, but I just don’t have any trust left in Apple after all that. My mini is running Windows 10 now, with the bootcamp drivers.
edit: I think Catalina was the last release I had used on it before wiping it for Windows. I definitely went up to Mojave, but pretty sure I tried Catalina too.
Ah, alright. Does gigabit work for you in windows? If it doesn’t, you can try installing Catalina and updating the Bootcamp drivers.
Unfortunately no, hence why I suspect it was a firmware update, not just a driver bug.
maybe. but I wouldn’t want to deal with messing with bootloaders again if it breaks my Windows install.