689
you are viewing a single comment's thread
view the rest of the comments
view the rest of the comments
this post was submitted on 16 Jul 2023
689 points (91.7% liked)
Memes
45536 readers
308 users here now
Rules:
- Be civil and nice.
- Try not to excessively repost, as a rule of thumb, wait at least 2 months to do it if you have to.
founded 5 years ago
MODERATORS
Dude, they disabled a capability of the hardware it shipped with, with a firmware update in the OD update. I have one of the affected Minis. I bought a computer that shipped with gigabit Ethernet and they removed that feature. I don't care if I could buy an external adapter. Would you think it was ok of Nvidia retroactively capped you 120fps GPU at 12fps because you can just buy another GPU?
I have a 2012 Mac Mini. It runs gigabit just fine. Might be a firmware bug that they never patched?
Edit: And no, I would not take that from Nvidia. But, I don’t think this is intentional, or else my mini would also be affected.
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.