New Mac Mini M2 Pro, Internet Problems

I just spent a frustrating 90 minutes and figured out that the default ethernet configure (automatic) is causing the issue on my ethernet port. I had to set it to manual configuration and then turned off the AVB/EAV mode and also manually set the speed of the port .. Once I did that, everything seems to be working well. I am on MAC OS 13.2

Hi phljoe.

Yes, I adjusted the settings on the replacement.

Your settings are identical to mine, and it works so far.

I actually had another issue with both machines, and that was that activating the touch id on a (brand new) magic keyboard did not work on the first machine, and took forever on the second. Pushing the power button on the mac twice, which is needed for the fingerprint initialization, wasn‘t recognized properly…

Touch ID issues is a different topic, of course, but I am having a similar issue with my new extended Magic keyboard. I've set it up and deleted the fingerprint several times and it will not recognize touch when trying to log into my user. Once logged in with my password, though, it works in every other instance. Annoying but will live with it until I discover a fix.

I also had this issue with my Mac mini M2 Pro 12/19 core 16GB/1TB version with 10Gbps Ethernet. I couldn’t just set the AVB/EAV mode to off, but also had to change my network speed to 2500Base-T (which is what my Ethernet network is). The test I used was Ookla Speedtest, the Mac application, not the web version. When I was having issues, it would fail with no Internet connection part way through the upload test. It never failed on download. Once I made the second setting and rebooted, Speedtest hasn’t failed and I haven’t seen an interruption in the short time I’ve changed it. I suggest turning off the setting and setting the max speed of your network.

My understanding is that AVB/EAV is a QoS mode designed for audio over Ethernet. Most QoS I have ever seen on routers just don’t work and cause issues just like we’ve seen. In fact I’ve yet to see a good QoS mode on any device and always turn it off on every router I’ve ever owned. Leave it off until Apple guarantees it works. This is definitely a software issue if this fixes your problem. Don’t return your Mac for this!

An additional note after the change above.

I run Homebridge on my Mini and noticed network disconnection every minute in the logs for some of the plugins with no other symptoms visible in experience. In my triage I had set the switch port back to auto negotiate. I now specify port speed and it appears to have stopped that drop out.

When setting your hardware configuration to manual it may be that you also need to set your port speed manually to match as well as changing the AVB/EAV setting

My M2 Mac mini pro 32gb 12/19 is having big time ethernet issues. (Web pages load slow3-5 seconds or more), online games have 2-3K ms latency and fortunately my music software isn't affected. Wi-fi works but not fully since I don't have a wi-fi6 router. I have a 1g up/down internet connection and the M1 Mac mini I also own is not suffering any of these issues. tried multiple cables, ports etc. The weird thing is a speed test shows no speed issues. It is just the apps and safari. I can't figure this out. Could there be an ethernet driver issue?

disabling AVB/EAV will be an issue if I buy the interface I need. it did however solve the latency issue immediately. This however is not affecting the M1 Mac mini so I would hope to find a better solution in the near future.

While disabling the AVB/EAV feature and specifying the port speed appears to eliminate the issue. Through future testing and observation it does not eliminate it, just reduces it. I am still seeing network drop outs.

I have the same 2 issues, Wifi is horrible performance. Not looking at that yet. The Ethernet was a little better but still not right, 30-40% packet loss on an extended ping test. Changed the AVB/EAV settings and it's much better but still experiencing around 5-10% packet loss.

I attached a Belkin usb-ethernet adapter, it's been rock solid for over 30 minutes.

Have had no luck with these settings or attaching a USB ethernet adapter. Massive packet loss on both the in-device and usb connected ethernet.

Talked to Apple several times and their answer is "Someone needs to look at it"

While 13.2.1 did someone help with packet loss, the problem is not fixed on my Mac mini (M2 Pro, 12/19 core, 16GB/1TB, 10Gbps ETH). I test it in two ways. I ping apple.com in a Terminal window and run Ookla Speedtest (the app, not the website). I thought it was fixed when the first 20 pings went through just fine, but then it had a timeout. That prompted me to run Speedtest and as before, the upload test failed. With that failure, I restored the AVB/EAV workaround and all works well with the manual configuration. If it fixed it for most, that’s good, but it does not seem to be fixed in all cases.

Thanks a million! I just got my new M2 Pro Mac Mini and was about to

ship it back! I could not even access my router with the local ip

address! Your trick fixed everything! Now I have to find a driver that

works with my old samsung laser printer...

I had a terrible time getting ethernet connection with minute and two Mac mini pro. It turned out to be one of the connections of the airport extreme, or the ethernet cable. I connected it to an ethernet hub that my other two iMac’s are connected to, and everything worked perfectly. I seem to recall I had trouble with that third from the top airport extreme connection before. It was like five years ago, so this time I wrote down a notation concerning the issue notes putting a number of keywords so I’m would be able to find it easily. Seth

Done every step was mentioned above.

Unfortunately, no success.

I'm with Apple representatives over a week.

None of them had a solution.

Should I return my M2 pro mac mini, Or wait for a solution here

i tend to think software. It occurs across wifi, Ethernet and usb Ethernet. Although I have only tested with one other USB Ethernet. And I admit it is likely there is a common hardware element between these the symptoms do not present themselves at the same time across each device

im currently looking at power save functions which could impact this given I’m running headless