694
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
694 points (91.7% liked)
Memes
45656 readers
881 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
Windows is shit, but the days where you have to do configuration if you don't use some obscure notebook in one of the most used linux distros is over. I'd say gnome e.g. is pretty close to macos UI wise. There is also Hackintosh if you can't live without it.
As for why I particularly hate apple:
There are surely more / other points to make.
Arch Linux Desktop for coding and gaming, MacBook for mobile productivity. Best of both worlds.
I know with 100% certainty that if my MacBook did a thing last week, it will do it tomorrow. No lost files due to updates, no weird crashes, no ads, no candy crush. If I’m out somewhere, that reliability is worth the premium. And, at least on Mac computers, you can unlock the walled garden if you really need to.
There is no use case for windows in my workflow. Might not be true for everyone though.
I had the exact same setup before switching to fedora
To be fair, using Arch is kind of a different thing entirely. If you want to compare something to OSX UX/reliability, Mint or the like would be a more fair comparison. They're way more stable than rolling release, and even rr doesn't have that many issues.
You would be wrong. They disabled gigabit ethernet in 2012/203 iMacs/Minis with an OS update, 100mbps only after that. They broke PTP for Android phones with an OS update.
I have a late 2012 mini on Catalina still. I’m like 99% sure it still runs gigabit. Let me check the switch port it’s on.
Any report?
Sorry. yeah was on my way home super late and fell asleep. Its definately 1Gb.
Arp Lookup
Mac Address lookup on switch
Switch Port is def 1gb. Port right under it is 100 Mb as an example.
Genuinely happy for you to have escaped this issue. I had mine on wifi when the OS update that killed it rolled out, because I couldn't run a cable to that part of my house, so I didn't notice until a couple of years after the fact. Even booting Linux or Windows it was still stuck at 100Mbps. There used to be a lot more threads on the Apple forums and they inevitably ended in people being content to just buying external thunderbolt adapters to get the speed back.
Was it ever just flagged as a bug, or some intentional planned obsolescence on the part of Apple?
I will likely need to upgrade this mac at some point. May just make it a server for plex or something. I purposefully bought it because its literally the last user serviceable Mac on the market.
I think there are some workarounds to get past the "supported OS" thing using something like this: https://dortania.github.io/OpenCore-Legacy-Patcher/
Though at this point, i No longer use it on the greater internet. its mostly just for me to record music with. I probably dont even need it on network anymore.
Mine was out of support by the time I noticed. And for whatever reason I was in the vast ~~majority~~ minority of people who didn't think buying a new external NIC was an acceptable solution, like that other guy who replied to me here.
Exactly what I was going to do with it when I moved it to somewhere wired. I now instead have a Synology Diskstation that can do hardware encoding/decoding. I still use the Mini, but after the PTP thing I wiped the disk and run Windows on it (for Lightroom Classic, and honestly the Gb would still be welcome with the media stored on the NAS, and I use Synology Drive to sync the Catalog folders)
If I remember correctly, with the first OS update that had the downgrade, you could roll back to the previous OS version (or boot Windows or Linux) and get it back, so it was just in the driver. But then at some point that stopped working too, so maybe an on-chip firmware update had been applied too. I tried store-bought and home-made Cat 5e/6 cables, different switch ports, hot-swapping different computers to confirm they would negotiate to Gb, and even loading the vendor OEM drivers and utilities after installing Windows.
Yeah thats really shitty. Im in the same boat as you to think just using some USB nic is not acceptable.
Maybe you should read your own sources before making unsubstantiated claims. If it had been intentional, using an adapter would not have solved the problem.
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.