MacOS – Just installed Maverick and the Canon MP780 will print but no longer scan, would a new driver help

canondrivermacosscanning

I get a message in the Image Capture window saying: No camera or scanner detected.

Scanner worked with Mountain Lion, but is not working with Mavericks.
On Canons website, this is the message on Canon's MP780 for Mavericks OS:
"There is no driver for the OS Version you selected. The driver may be included in your OS or you may not need a driver."

I know the hardware (Canon MP780) works as I tried VueScan, and the hardware scanned with this program – but I would have to pay $40.00 for VueScan.
Hoping there is a driver that would allow me to use my current software, without purchasing VueScan.

Best Answer

There are four options at present and being told you can't have the new thing without paying for an old thing to work means many people will resent the $40 option and be angry:

Pay the money and keep running Mavericks with VueScan to scan.
Don't pay the money and revert to Mountain Lion (or whatever previous OS works with your peripherals).
Get a new scanner.
Wait for someone else to provide a driver that either does more than VueScan or costs less than VueScan.

Related Solutions

MacOS – Will the Canon CanoScan 500F scanner work with Lion

It looks like some old saved settings were causing the scanner to hang indefinitely - pressing scan over and over wasn't working.

I pressed the show details button a few times but didn't realize things were working slowly in the background. After a minute or so - I was able to get into the details, change some settings, and it has been working well.

enter image description here Those TWAIN errors are not logging now either. Life is good again in Lion scan land.

MacOS – Troublesome kext or driver causing system to hang

Here is a method to hunt the kext which may cause you a hang system.

Boot in safe mode & make a capture of the minimal safe set of extenions loaded with:
```
mkdir ~/tmp
kextstat >~/tmp/safe.kextstat
```
Boot in normal mode & make a capture of the full set of extensions loaded with:
```
kextstat >~/tmp/full.kextstat
```

Compare them:

cd ~/tmp
diff full.kextstat safe.kextstat

and from this difference, which is including the faulty kext, extract the culprit by checking its installation date:

ls -dlT /System/Library/Extensions/<extension_folder_name…>

The faulty extension will be the one installed at the time of the start of your kernel hang.

Beware: the extension_folder_name… is not the extension name as displayed by kexstat.

Here is an example:

on_my_mac$ kextstat | egrep 'Addr|ThunderboltDPA'
Index Refs Address            Size       Wired      Name (Version) <Linked Against>
   70    4 0xffffff7f8125e000 0x8000     0x8000     com.apple.driver.AppleThunderboltDPAdapterFamily (1.8.2) <45 9 8 5 4 3>
on_my_mac$

is coming from:

on_my_mac$ cd /System/Library/Extensions
on_my_mac$ ls -dlT AppleThunderboltDPAdapters.kext
drwxr-xr-x  3 root  wheel  102 Aug 31 05:39:06 2011 AppleThunderboltDPAdapters.kext
on_my_mac$

Make a backup copy of the suspected extension:

mkdir ~/Extensions_backup
cd /System/Library/Extensions
/usr/bin/sudo mv faulty_extension_folder_name ~/Extensions_backup

and test this system with one missing kernel extension:

reboot

If it is OK. You got the right culprit.

If not. Just reverse step 4, reboot and repeat from step 4 to test the next potential extension.

Best Answer

Related Solutions

MacOS – Will the Canon CanoScan 500F scanner work with Lion

MacOS – Troublesome kext or driver causing system to hang

Related Question