I had the same problem after upgrading to Monterey. I ended up replacing my hub with a different (newer) hub, and the issue mostly disappeared. I suspect there was a change in Monterey that broke compatibility with some older chipsets.My macOS is monterey.
Symptoms do not improve with cable replacement.
Haven't tried replacing the storage case though.
I don't see this symptom on my big sur at work.
I think the problem is monterey.
I took your advice and tried it with a newer product and the problem is gone.I had the same problem after upgrading to Monterey. I ended up replacing my hub with a different (newer) hub, and the issue mostly disappeared. I suspect there was a change in Monterey that broke compatibility with some older chipsets.
I’m glad it worked!I took your advice and tried it with a newer product and the problem is gone.
Thanks!
If the devices work directly connected all of the M1 ports but fail when connected via a dock with certain ports it suggests a problem with the M1 Hub connection, either with the hub cable or its firmware/hardware.the moment I connect directly to the port without the hubs, they instantly work great.
thank you for the reply/If the devices work directly connected all of the M1 ports but fail when connected via a dock with certain ports it suggests a problem with the M1 Hub connection, either with the hub cable or its firmware/hardware.
Have you contacted Wavlink or Anker? If the devices work when directly connected I would put the onus on them. Amazon gives the Wavlink Thunderbolt3 a mediocre 3.3 rating. Reviews mention problems with disconnecting devices and no power to displays.
Which Anker hub are you using? Some models have multiple comments about displays and USB-A ports not working.
Darryl, thank you so much for your reply and insight.Leeleo, yours reads like a legit hardware issue with that port #2. Assuming you've tried at least 1 different cable hooked to port 2 to rule out a bad cable (not just plugging what might be ONE bad cable into a variety of things and then assuming the port), I suggest returning that Mac and getting another. However, carefully eyeball the port to make sure nothing is jammed in there that might be affecting connections. Even a little lint could be the culprit.
To mostly rule out the variety of non-Apple hardware that is ejecting: if you have an older Mac running macOS before BigSur, try each attached to that for a while. If they don't eject there, you can mostly rule out the hardware + cable you are using if you move the same combo to your Silicon Mac and get ejections. The U in USB stands for Universal. The fundamental goal of USB is to "just work."
If beyond your return window, take it to an Apple store, demonstrate the issue and see if they can do anything. If not, maybe they will swap anyway or quote repair service.
The bulk of issues described in this and similar threads seem to rule out malfunctioning ports (like you describe). Instead, while the ports seem to work, the "unexpected ejections" happen anyway. I've invested a lot of time in this problem and I'm mostly convinced it is a software problem, not a hardware problem... though there are some related threads about the hardware, particularly that:
Both of those imply a potential HARDWARE issue, though I personally hope this is all related to macOS software needing bug fixes and refinements for Silicon. I wish I could boot this Studio into a macOS version BEFORE Big Sur to put my main hypothesis to the ultimate test. I strongly suspect that the "unexpected ejection" problem would no longer occur... exactly like I experience when the same enclosure with same cable are linked to my two Intel Macs running pre-Big Sur macOS.
- full speeds are not realized on the ports and
- power to the ports seems oddly limited given the big power supply.
If I then decide to connect all drives (SSDs or HDDs or flash drives) directly to that same TB4 port, then they will all work perfectly well with no issues.
Hey HDFanThis points to the hubs and dongles being the problem.
Yea, I highly suspect your issue has to do with software mate. I doubt it it’s got something to do with hardware.I have the problem on my MacBook Pro M1 13 while connected through WiFi. I have no dongles, hubs etc connected. Only TimeMachine is running during charge while 'sleeping'. I believe that my issue is software related. Because it started after Monterey. But it does NOT happen when I disable the automatic TimeMachine backups.
In about two days there will be a new release and I hope that will take care of the problem.
However some users that report their problem was gone after hardware replacement, could ofcourse see this improvement due to a different hardware/software combination that is less problematic.