Hi Oskar, Am Dienstag, 7. September 2010, 12:29:07 schrieb Oskar Schirmer: > Trying to get the plustek 9636T work > on an Ubuntu 10.04 500MHz x86 installation, > but it fails during detection. With > export SANE_DEBUG_PLUSTEK_PP=255 set, > scanimage run with root permissions says: > > [...] > [plustek_pp] attach (parport0, 0xbf84e5e0, (nil)) > [plustek_pp] Device configuration: > [plustek_pp] device name : >parport0< > [plustek_pp] direct I/O : yes > [plustek_pp] warmup : -1s > [plustek_pp] lampOff : -1 > [plustek_pp] lampOffOnEnd : yes > [plustek_pp] model override: 0 > [plustek_pp] --------------------- [...] > [plustek_pp] ioP98ReadWriteTest() > [plustek_pp] Moving 1280 bytes to scanner, IODELAY = 4... > [plustek_pp] ... done. > [plustek_pp] Error in memory test at pos 0 (0 != 255) > [plustek_pp] detectScannerConnection() returns -9020. > [plustek_pp] *** DETECTION DONE, result: -9020 *** > [plustek_pp] ptdrvClose() > [plustek_pp] MiscRestorePort() > [plustek_pp] Releasing parport > [plustek_pp] ptdrvShutdown() > [plustek_pp] cleanup device 0 > [plustek_pp] open: PtDrvInit failed: -9020 > [plustek_pp] open failed: -1 > [plustek_pp] sane_get_devices (0xbf8506ec, 0) > scanimage: no SANE devices found > [plustek_pp] sane_exit > > With comments dropped, /etc/sane.d/plustek_pp.conf is: [...] > What's going wrong, > what does the memory test and IODELAY thing tell?
during startup the driver tries to connect to the scanner and to detect the type - seems this works. Next step is to checkec wether data can be written to and retrieved from the scanner. This fails. This test (ioP98ReadWriteTest()), tries that with several delay settings. It turned out, that it's not always possible to access the device as fast as possible and that's why there's an IODELAY setting. In your case it's not possible to access the memory, that's why the procedure fails. You might check the BIOS settings for the parallel port, play with the modes. Try different settings (SPP, EPP) Cheers, Gerhard
