Dirk Meyer wrote:
>Peter B wrote:
>
>> I have a "Epson Perfection 1250" USB scanner. It works fine under "Windows Me"
>> I'm trying to get it to work under FreeBSD-4.7 and have patched usbdevs, 
>> usbdevs.h, usbdevs_data.h, uscanner.c in /usr/src/sys/dev/usb
>
>without patches:
>FreeBSD 4.8-PRERELEASE #22: Thu Feb 27 20:03:38 CET 2003
>
>Mar  5 17:33:28 net3 /kernel: uscanner0: EPSON EPSON Scanner, rev 1.10/1.00, addr 2
>
>but scanimage hangs here.

Any traces what could be the reason?

With 4.7 (i386) and my patches it works now ..kind of..
And modifying /usr/local/etc/sane.d/plustek.conf as follows:
  [usb]                   ->  [usb] 0x04B8 0x010F
  device /dev/usbscanner  ->  device /dev/uscanner0

But it should not be neccessary.. USB.. Plug & PRAY! :)

xscanimage  works ok.
scanimage   works (stepper motor goes beyond physical limit in this case).
xsane       crashes after scan, but won't hang anything.

One real nasty thing I discovered is that if one cancels a scan it can happen
that the step motor continues to drive the scanner wagon beyond physical limit
*until* you cancel it by requesting a new scan or disconnect power.
Something that ought to be fixed..

>I tested on:
>FreeBSD 5.0-CURRENT #0: Fri Jan 31 13:42:19 CET 2003
>everything runs there smoothly.
>
>mdodify: /usr/local/etc/sane.d/plustek.conf
>
>$ /usr/local/bin/scanimage --verbose --device plustek:/dev/uscanner0 \
>       --format tiff --mode Color -x 210 -y 297 > test.tif
..........

There is also a speed issue:

                      Windoze     FreeBSD
Preview               26 sec      50 sec
300 dpi, 24 bpp, A4   45 sec      66 sec

Windoze system:
  Toshiba laptop, CPU-Intel Celeron 650, 64 MB Ram, Windoze Me

FreeBSD system:
  Motherboard A7V333, CPU-AMD XP1800, 256 MB Ram, FreeBSD 4.7

One can clearly hear (audiowise) that the freebsd system does the scanning in 
chunks while windoze does most tasks in one "sweep".

    /P


To Unsubscribe: send mail to [EMAIL PROTECTED]
with "unsubscribe freebsd-questions" in the body of the message

Reply via email to