On Sunday 23 March 2003 20:03, Matt T. wrote:

Hi,

I did set up my old scanner canon FB630U with Yast2 (SuSE . After that I could scan with Xscanimage and Xsane, excellent quality scans.

Then, after the first reboot, I cannot scan anymore. Message in Xsane or Xscanimage is "Failed to start scanner, Device busy" in /var/log/messages there are 7 lines with "...kernel: scanner.c: open_scanner(7): Unable to access minor data".

I verified all settings (according to Wolfi's guideline posted here some time ago). usbview shows the scanner, lsmod shows that scanner is loaded etc.

I'm scared this is a sign of poor USB support by the MSI K7N2G nforce2 mobo I'm using. However I had thesame error before, with an older MSI K7 mobo, and no nforce2 yet.

The scanner works fine with my notebook, also SuSE 8.1.

Any ideas how to fix this are highly appreciated.

Thanks, Matt T. (yes, my next scanner will be an Epson only)

I already wanted to blame nvidia's nforce2 for a bad USB support, but then I found the solution, after days of searching, in the January 2003 archive of the sane-devel mailinglist - the calibration cache file /tmp/canon.cal is giving sane a hickup, it needs to get deleted, probably everytime you reboot. Andrew Kovacs: "Eventually Henning suggested I contact Nathan Rutman [nthn1@yahoo.com], the author of the canon630u backend. I did so and Nathan suggested I delete the /tmp/canon.cal file, as this can cause sane to tie up the scanner (or something like that). I tried it and it worked. It creates another error message, but I'll chase that up later, and Nathan thinks that this problem will be fixed in the next release of sane." So thanks to Nathan and Henning and Greg and Andrew Kovacs the hammer had to go back in the drawer without having hammered a kittle on the scanner, or on the mobo, or both. BTW, the messages "open_scanner(x): Unable to access minor data" are no real errors, it is just that the scanner is not on /dev/usb/scanner1 - scanner7, but only on scanner0, so the driver gives this error when finding no scanner on /dev/usb/scanner1 - scanner7, and that's correct, the scanner is only on /dev/usb/scanner0 . I hope this post saves someone the days of searching, which it did cost me to find the workaround. Regards, Matt T.