View Single Post
Old 12-30-2021, 11:51 PM   #6
davidfor
Grand Sorcerer
davidfor ought to be getting tired of karma fortunes by now.davidfor ought to be getting tired of karma fortunes by now.davidfor ought to be getting tired of karma fortunes by now.davidfor ought to be getting tired of karma fortunes by now.davidfor ought to be getting tired of karma fortunes by now.davidfor ought to be getting tired of karma fortunes by now.davidfor ought to be getting tired of karma fortunes by now.davidfor ought to be getting tired of karma fortunes by now.davidfor ought to be getting tired of karma fortunes by now.davidfor ought to be getting tired of karma fortunes by now.davidfor ought to be getting tired of karma fortunes by now.
 
Posts: 24,905
Karma: 47303824
Join Date: Jul 2011
Location: Sydney, Australia
Device: Kobo:Touch,Glo, AuraH2O, GloHD,AuraONE, ClaraHD, Libra H2O; tolinoepos
Quote:
Originally Posted by ZDR View Post
Was hoping this was a known issue, but it seems not...
There have been plenty of different issues with MACs over the years. Different upgrades of the OS or the hardware have lead to different things. They range from simple things like the OS mounting the device read-only, to something preventing the device being recognised. There were changes in one of the recent firmware (not sure if it was in 4.28.x or 4.30.x) to help them be seen, but, I understood that was with the M1 based MACs, not the older ones. It might be worthwhile rolling back the firmware to test if that was the cause. But, I think it is more like a change on the MAC. Either a "fix" or a change in permissions blocking the device.

Beyond that, I can only suggest searches here to see how people have solved problems. I don't have a MAC, and have no personal experience with them.
davidfor is offline   Reply With Quote