Low Lebel translation of x86 to ARM64 (yes even with Rosetta 2) cab be pretty problematic when it comes to things like printers and other low level hardware. If your just using the disk that came with the printer I'd expect these sorts of issues. Did you make sure that the drivers are for an M1 Mac? They should either specifically say M1 drivers, or have ARM64 somewhere in the file name or on the site you downloaded them from. I didn't need to inst30all any drivers for the Canon MG6300 and you shouldn't need to install any drivers for your scanner either. Are you using any sort of USB-C/Thunderbolt dock or adapter in order to connect the printer to the MacBook Air, or are you using it wirelessly? All of this info will help to try and diagnose your problem. It was easier to access and set it up to use as a wifi printer than it was to plug in and use as a wired printer. Sometimes it's compiled programs causing the issue where Rosetta 2 can't translate a lot of the lower level functions well enough (like printers and scanners which rely on access to the kernel).Īnyway, I'm using a Canon MG6300 printer/scanner with my M1 MacBook Pro and don't have any issues. This is probably because of all sorts of configuration files being moved over and some of them being either contradictory or outright uneeded on the M1 models. People setting up an M1 Air, Mini, Pro, from scratch or just moving important files over normally, or from a file server seem to skip pretty much all of the issues that M1 users are experiencing. Also, Did you restore the MacBook Air from a time machine backup or migration assistant? A lot of people are having all sorts of trouble moving to an M1 from an x86 (intel) MacBook when they use time machine or migration assistant to move all of their files over. Does your scanner have wifi? I'm pretty confident I can get it working over wifi for you without much fuss if it is indeed wifi compatible. So what is the exact scanner model? Without that information it's pretty tough to help you in any meaningful way.
0 Comments
Leave a Reply. |