[sane-devel] Can't build SANE on Ubuntu Feisty 7.04

2007-06-26 Thread Simon Glass
Hi,

I am keen to test out my new Fujitsu FI-5750C but it doesn't seem to
work out of the box. While trying to build SANE from CVS I initially got
an error about md5 which I got around by adding a library explicitly to
the Makefile.

making all in frontend
make[1]: Entering directory
`/pub/software/drivers/sane/sane-backends/frontend'
make[1]: Warning: File `Makefile' has modification time 0.83 s in the future
gcc -o .libs/scanimage scanimage.o stiff.o  ../lib/liblib.a
../backend/.libs/libsane.so -ldl /usr/lib/libusb.so -lpthread
/usr/lib/libtiff.so /usr/lib/libjpeg.so -lz -lm -lc
/usr/lib/libieee1284.so -Wl,--rpath -Wl,/usr/local/lib
scanimage.o: In function `auth_callback':
/pub/software/drivers/sane/sane-backends/frontend/scanimage.c:291:
undefined reference to `md5_buffer'
collect2: ld returned 1 exit status
make[1]: *** [scanimage] Error 1
make[1]: Leaving directory
`/pub/software/drivers/sane/sane-backends/frontend'


But now I get:

...
making all in frontend
make[1]: Entering directory
`/pub/software/drivers/sane/sane-backends/frontend'
make[1]: Warning: File `Makefile' has modification time 0.4 s in the future
gcc-4.0 -o .libs/saned saned.o  ../sanei/libsanei.a ../lib/liblib.a
../backend/.libs/libsane.so -ldl /usr/lib/libusb.so -lpthread
/usr/lib/libtiff.so /usr/lib/libjpeg.so -lz -lm -lc
/usr/lib/libieee1284.so -Wl,--rpath -Wl,/usr/local/lib
saned.o: In function `decode_handle':
/pub/software/drivers/sane/sane-backends/frontend/saned.c:461: undefined
reference to `sanei_w_word'
saned.o: In function `init':
/pub/software/drivers/sane/sane-backends/frontend/saned.c:1254:
undefined reference to `sanei_w_set_dir'
/pub/software/drivers/sane/sane-backends/frontend/saned.c:1261:
undefined reference to `sanei_w_word'
...

It seems that the tools are not producing object files properly or
something. Before I dive into something I don't understand does anyone
have a simple solution?

I did see this from ./configure

checking whether the g++ linker (/usr/bin/ld) supports shared
libraries... yes
checking dynamic linker characteristics... cat:
/etc/ld.so.conf.d/*.conf: No such file or directory
GNU/Linux ld.so

Regards,
Simon





[sane-devel] fujitsu 5120c --souce error invalid argument

2007-06-26 Thread Skorous
I'm sure allan will respond to this shortly as he's pretty active on
the list but since I'm here right now: are you sure you're using the
argument properly? Have you tried quoting the argument ( i.e. --source
ADF Duplex )? I use those options with the 3091DC and it works fine
( same backend ).

Marty

On 6/25/07, patrick blanchard dspcypher at gmail.com wrote:
 Hi,
 first, thanks to the sane team and the fujitsu backenders.

 1.0.18 builds on ubuntu 6.06.1 and scanimage works well w/ most options that
 i tested so far - color, batch... and i'm still testing different options to
 scanimage.

 however, the ADF Front, ADF Back, ADF Duplex option of course defaults to
 ADF Front and any option passed to scanimage --source foo returns an invalid
 arg. I think this is the reason why xscanner is broken btw, because it tries
 to pass --source and returns an error. also, i am using scsi, and have set
 scsi eeprom to the lowest async settings available. i'm testing for
 synchronous and higher speeds right now

 so here is my question. will you help me configure or change makefile to
 build just for fujitsu 5120c? or, even better, to help me debug the backend
 so the --source option works?

 fwiw, i work w/ embedded systems and use simple makefiles only. however, i
 am reading the auto* toolset documentation because i have an interest in
 porting some of my projects. i plan on working this fujitsu backend as a
 learning tool for the auto* toolset.

 also, this fujitsu 5120c was chosen for it's duplex and insurance card
 scanning ability - and specifically requested by a client for intallation
 into a medical clinic. i don't really need xscanner to work but it would be
 nice and i think once the --source option is working then xscanner will too.

 thanks again to any and all replies.

 --
 sane-devel mailing list: sane-devel at lists.alioth.debian.org
 http://lists.alioth.debian.org/mailman/listinfo/sane-devel
 Unsubscribe: Send mail with subject unsubscribe your_password
  to sane-devel-request at lists.alioth.debian.org




[sane-devel] Scanner 'reset scan head' utilities (plustek, Canon Lide20)

2007-06-26 Thread Gerhard Jaeger
On Montag, 25. Juni 2007, Jeff Kowalczyk wrote:
 Jeff Kowalczyk wrote:
  My everyday flatbed scanner ((vendor=0x04a9 [Canon], product=0x220d
  [CanoScan], chip=LM9832/3) at libusb:002:002) got out of sorts today.
  The scan head wasn't returned to the home position (it is now), but
  XSane scans now just return solid black data.
 
 I see that it's a known problem, since I have (recently) enabled
 CONFIG_USB_SUSPEND to try powertop, and this is using the plustek backend.
 
In fact it's not only a Plustek problem - it's a problem of all ASICs, that
support someting like a suspend mode. The LM983x enters that mode, when there
is no activity on the USB-bus for 3ms. Most of the registers will be reset
during that...

I will try and focus on that during the next days...

Cheers
Gerhard




[sane-devel] FI-5750C Error 4?

2007-06-26 Thread Simon Glass
Hi,

Now that I am able to build SANE (thanks Alan, but no I have no idea
about libtool) I have the FI-5750C working. It's a wonder to behold.
However, I am puzzled by an error that I get. It seems that if I try to
scan a page larger than the setting I have for the ADF size then I get
an error 4 (Unknown Error).

Further to that, if I try to scan A3 (even with the right ADF setting) I
get error 4. Maybe it is something slightly wrong with the paper size.

Any ideas on this one?

Another point is that the scanner seems to pause after some pages. Not
every time, it might scan 6 pages and then pause for a second. But it is
quite noticeable. I wonder if that is SANE or Fujitsu...

Thanks,
Simon




[sane-devel] fujitsu 5120c --souce error invalid argument

2007-06-26 Thread m. allan noah
On 6/25/07, Skorous skorous at gmail.com wrote:
 I'm sure allan will respond to this shortly as he's pretty active on
 the list but since I'm here right now: are you sure you're using the
 argument properly? Have you tried quoting the argument ( i.e. --source
 ADF Duplex )? I use those options with the 3091DC and it works fine
 ( same backend ).


yes- if you find that quoting the source option does not help, then
you will need to get a debug log so we can troubleshoot.

the backend should work with scsi just fine, though i dont know what
the scanner will think about low speeds.

you probably want to use the cvs version of sane, there have been some
updates since 1.0.18 was released.

allan

 Marty

 On 6/25/07, patrick blanchard dspcypher at gmail.com wrote:
  Hi,
  first, thanks to the sane team and the fujitsu backenders.
 
  1.0.18 builds on ubuntu 6.06.1 and scanimage works well w/ most options that
  i tested so far - color, batch... and i'm still testing different options to
  scanimage.
 
  however, the ADF Front, ADF Back, ADF Duplex option of course defaults to
  ADF Front and any option passed to scanimage --source foo returns an invalid
  arg. I think this is the reason why xscanner is broken btw, because it tries
  to pass --source and returns an error. also, i am using scsi, and have set
  scsi eeprom to the lowest async settings available. i'm testing for
  synchronous and higher speeds right now
 
  so here is my question. will you help me configure or change makefile to
  build just for fujitsu 5120c? or, even better, to help me debug the backend
  so the --source option works?
 
  fwiw, i work w/ embedded systems and use simple makefiles only. however, i
  am reading the auto* toolset documentation because i have an interest in
  porting some of my projects. i plan on working this fujitsu backend as a
  learning tool for the auto* toolset.
 
  also, this fujitsu 5120c was chosen for it's duplex and insurance card
  scanning ability - and specifically requested by a client for intallation
  into a medical clinic. i don't really need xscanner to work but it would be
  nice and i think once the --source option is working then xscanner will too.
 
  thanks again to any and all replies.
 
  --
  sane-devel mailing list: sane-devel at lists.alioth.debian.org
  http://lists.alioth.debian.org/mailman/listinfo/sane-devel
  Unsubscribe: Send mail with subject unsubscribe your_password
   to sane-devel-request at lists.alioth.debian.org
 

 --
 sane-devel mailing list: sane-devel at lists.alioth.debian.org
 http://lists.alioth.debian.org/mailman/listinfo/sane-devel
 Unsubscribe: Send mail with subject unsubscribe your_password
  to sane-devel-request at lists.alioth.debian.org



-- 
The truth is an offense, but not a sin



[sane-devel] FI-5750C Error 4?

2007-06-26 Thread m. allan noah
On 6/26/07, Simon Glass sglass at bluewatersys.com wrote:
 Hi,

 Now that I am able to build SANE (thanks Alan, but no I have no idea
 about libtool) I have the FI-5750C working. It's a wonder to behold.
 However, I am puzzled by an error that I get. It seems that if I try to
 scan a page larger than the setting I have for the ADF size then I get
 an error 4 (Unknown Error).

 Further to that, if I try to scan A3 (even with the right ADF setting) I
 get error 4. Maybe it is something slightly wrong with the paper size.

 Any ideas on this one?

error 4 is SANE_STATUS_INVAL, indicating that the scanner was unhappy
with your choice of options. try setting the pagewidth and height
before the x and y values, in case order of operations is important.
show us the exact command line you are using.


 Another point is that the scanner seems to pause after some pages. Not
 every time, it might scan 6 pages and then pause for a second. But it is
 quite noticeable. I wonder if that is SANE or Fujitsu...


do you have the buffermode option? try turning that on. does the
windows driver behave this way?

also- can you verify that color scans look correct, and can you tell
the usb productID for this machine?

thanks-

allan

-- 
The truth is an offense, but not a sin



[sane-devel] FI-5750C Error 4?

2007-06-26 Thread Oliver Schirrmeister
Am Dienstag, 26. Juni 2007 11:15 schrieb Simon Glass:
 Hi,
 
 Now that I am able to build SANE (thanks Alan, but no I have no idea
 about libtool) I have the FI-5750C working. It's a wonder to behold.
 However, I am puzzled by an error that I get. It seems that if I try to
 scan a page larger than the setting I have for the ADF size then I get
 an error 4 (Unknown Error).
 
 Further to that, if I try to scan A3 (even with the right ADF setting) I
 get error 4. Maybe it is something slightly wrong with the paper size.
 
 Any ideas on this one?
 
 Another point is that the scanner seems to pause after some pages. Not
 every time, it might scan 6 pages and then pause for a second. But it is
 quite noticeable. I wonder if that is SANE or Fujitsu...

That's a fujitsu problem. You'll see the same behaviour with windows and twain. 
I guess the scanner scans faster than it can transmit the data via usb/scsi. 
The 
scanner has some memory where it can buffer some data. If it's full the scanner 
pauses
an recalibrates. 

Oliver

Geschaeftsfuehrer: Dipl.-Inform. Christopher Asp
Amtsgericht Mannheim HRB 105845



[sane-devel] Scanner 'reset scan head' utilities (plustek, Canon Lide20)

2007-06-26 Thread Gerhard Jaeger
On Montag, 25. Juni 2007, Jeff Kowalczyk wrote:
 Jeff Kowalczyk wrote:
  My everyday flatbed scanner ((vendor=0x04a9 [Canon], product=0x220d
  [CanoScan], chip=LM9832/3) at libusb:002:002) got out of sorts today.
  The scan head wasn't returned to the home position (it is now), but
  XSane scans now just return solid black data.
 
 I see that it's a known problem, since I have (recently) enabled
 CONFIG_USB_SUSPEND to try powertop, and this is using the plustek backend.
 
Hi,

which kernel did you use? I've currently checked that on a SuSE10,
kernel 2.6.13 and turned on CONFIG_USB_SUSPEND - no problems so far.

I tried to put the LiDE20 into suspend - no problems. Next thing
I need to check is my laptop, running a SuSE10.2 - kernel2.6.18

It's quite strange - from reviewing the code there's only one
point which could cause the mentioned problems - but not on
a Lide :(

- Gerhard




[sane-devel] Scanner 'reset scan head' utilities (plustek, Canon Lide20)

2007-06-26 Thread Jeff Kowalczyk
On Tue, 26 Jun 2007 16:32:24 +0200, Gerhard Jaeger wrote:
 which kernel did you use? I've currently checked that on a SuSE10,
 kernel 2.6.13 and turned on CONFIG_USB_SUSPEND - no problems so far.
 
 I tried to put the LiDE20 into suspend - no problems. Next thing
 I need to check is my laptop, running a SuSE10.2 - kernel2.6.18
 
 It's quite strange - from reviewing the code there's only one
 point which could cause the mentioned problems - but not on
 a Lide :(

I'm running a newer kernel on Gentoo Linux ~x86:

Linux 2.6.21-gentoo-r3 #1 PREEMPT Mon Jun 25 16:01:36 EDT 2007 i686
mobile AMD Athlon(tm) XP-M 2000+ AuthenticAMD GNU/Linux

The kernel has been recompiled without USB_SUSPEND, and the scanner is
working fine today.

 # grep USB kernel-config-x86-2.6.21-gentoo-r3
 
 # CONFIG_USB_ZD1201 is not set
 # CONFIG_USB_DABUSB is not set
 # USB devices
 CONFIG_SND_USB_AUDIO=m
 # CONFIG_SND_USB_USX2Y is not set
 # USB support
 CONFIG_USB_ARCH_HAS_HCD=y
 CONFIG_USB_ARCH_HAS_OHCI=y
 CONFIG_USB_ARCH_HAS_EHCI=y
 CONFIG_USB=m
 # CONFIG_USB_DEBUG is not set
 # Miscellaneous USB options
 CONFIG_USB_DEVICEFS=y
 # CONFIG_USB_DYNAMIC_MINORS is not set
 # CONFIG_USB_SUSPEND is not set
 # CONFIG_USB_OTG is not set
 # USB Host Controller Drivers
 CONFIG_USB_EHCI_HCD=m
 # CONFIG_USB_EHCI_SPLIT_ISO is not set
 # CONFIG_USB_EHCI_ROOT_HUB_TT is not set
 # CONFIG_USB_EHCI_TT_NEWSCHED is not set
 # CONFIG_USB_EHCI_BIG_ENDIAN_MMIO is not set
 # CONFIG_USB_ISP116X_HCD is not set
 CONFIG_USB_OHCI_HCD=m
 # CONFIG_USB_OHCI_BIG_ENDIAN_DESC is not set
 # CONFIG_USB_OHCI_BIG_ENDIAN_MMIO is not set
 CONFIG_USB_OHCI_LITTLE_ENDIAN=y
 CONFIG_USB_UHCI_HCD=m
 CONFIG_USB_SL811_HCD=m
 # CONFIG_USB_SL811_CS is not set
 # USB Device Class drivers
 # CONFIG_USB_ACM is not set
 CONFIG_USB_PRINTER=m
 # NOTE: USB_STORAGE enables SCSI, and 'SCSI disk support'
 # may also be needed; see USB_STORAGE Help for more information
 CONFIG_USB_STORAGE=m
 # CONFIG_USB_STORAGE_DEBUG is not set
 # CONFIG_USB_STORAGE_DATAFAB is not set
 # CONFIG_USB_STORAGE_FREECOM is not set
 # CONFIG_USB_STORAGE_ISD200 is not set
 # CONFIG_USB_STORAGE_DPCM is not set
 # CONFIG_USB_STORAGE_USBAT is not set
 # CONFIG_USB_STORAGE_SDDR09 is not set
 # CONFIG_USB_STORAGE_SDDR55 is not set
 # CONFIG_USB_STORAGE_JUMPSHOT is not set
 # CONFIG_USB_STORAGE_ALAUDA is not set
 CONFIG_USB_STORAGE_KARMA=y
 # CONFIG_USB_LIBUSUAL is not set
 # USB Input Devices
 CONFIG_USB_HID=m
 # CONFIG_USB_HIDINPUT_POWERBOOK is not set
 CONFIG_USB_HIDDEV=y
 # USB HID Boot Protocol drivers
 # CONFIG_USB_KBD is not set
 # CONFIG_USB_MOUSE is not set
 # CONFIG_USB_AIPTEK is not set
 # CONFIG_USB_WACOM is not set
 # CONFIG_USB_ACECAD is not set
 # CONFIG_USB_KBTAB is not set
 # CONFIG_USB_POWERMATE is not set
 # CONFIG_USB_TOUCHSCREEN is not set
 # CONFIG_USB_YEALINK is not set
 # CONFIG_USB_XPAD is not set
 # CONFIG_USB_ATI_REMOTE is not set
 # CONFIG_USB_ATI_REMOTE2 is not set
 # CONFIG_USB_KEYSPAN_REMOTE is not set
 # CONFIG_USB_APPLETOUCH is not set
 # CONFIG_USB_GTCO is not set
 # USB Imaging devices
 # CONFIG_USB_MDC800 is not set
 # CONFIG_USB_MICROTEK is not set
 # USB Network Adapters
 # CONFIG_USB_CATC is not set
 # CONFIG_USB_KAWETH is not set
 # CONFIG_USB_PEGASUS is not set
 # CONFIG_USB_RTL8150 is not set
 # CONFIG_USB_USBNET_MII is not set
 # CONFIG_USB_USBNET is not set
 # CONFIG_USB_MON is not set
 # USB port drivers
 # USB Serial Converter support
 # CONFIG_USB_SERIAL is not set
 # USB Miscellaneous drivers
 # CONFIG_USB_EMI62 is not set
 # CONFIG_USB_EMI26 is not set
 # CONFIG_USB_ADUTUX is not set
 # CONFIG_USB_AUERSWALD is not set
 # CONFIG_USB_RIO500 is not set
 # CONFIG_USB_LEGOTOWER is not set
 # CONFIG_USB_LCD is not set
 # CONFIG_USB_BERRY_CHARGE is not set
 # CONFIG_USB_LED is not set
 # CONFIG_USB_CYPRESS_CY7C63 is not set
 # CONFIG_USB_CYTHERM is not set
 # CONFIG_USB_PHIDGET is not set
 # CONFIG_USB_IDMOUSE is not set
 # CONFIG_USB_FTDI_ELAN is not set
 # CONFIG_USB_APPLEDISPLAY is not set
 # CONFIG_USB_SISUSBVGA is not set
 # CONFIG_USB_LD is not set
 # CONFIG_USB_TRANCEVIBRATOR is not set
 # CONFIG_USB_IOWARRIOR is not set
 # CONFIG_USB_TEST is not set
 # USB DSL modem support
 # USB Gadget Support
 # CONFIG_USB_GADGET is not set
 
 
 Installed versions of: libusb sane-frontends sane-backends
 
 dev-libs/libusb-0.1.12-r1  USE=-debug -doc
 media-gfx/sane-frontends-1.0.14  USE=gimp
 media-gfx/sane-backends-1.0.18-r2  USE=gphoto2 ipv6 usb v4l
 




[sane-devel] Microfilm scanner

2007-06-26 Thread Guido Milanese
Dear experts,
I would like to find a good microfilm scanner supported by Sane (I use Linux 
Mandriva). The one I have, an excellent Epson Perfection 4990, does a good 
job with photos , but only with strips (6 exposures). I know there are 
excellent microfilm scanners, as the Nikon Coolscan family, but they seem non 
supported by Sane. To be clear: the kind of microfilms I have to scan are the 
old kind of microfilms used by libraries e.g. for manuscripts and very old 
books. Now it's normal to send a CD with images, but many libraries still 
have this old kind of media.

Any suggestion greatly appreciated!
guido, italy 

---
Guido Milanese
http://docenti.unicatt.it/milanese_guido
http://www.arsantiqua.org



[sane-devel] LSB DDK: Support for scanner drivers/SANE into LSB 3.2?

2007-06-26 Thread Till Kamppeter
Ren? Rebe wrote:
 
 I take a look into what is necessary to get SANE into the LSB over
 the weekend.
 

Did you already find out something?

Till




[sane-devel] LSB DDK: Support for scanner drivers/SANE into LSB 3.2?

2007-06-26 Thread Gerald Murray

 Ren? Rebe wrote:

 I take a look into what is necessary to get SANE into the LSB over
 the weekend.


 Did you already find out something?

Hi Till,
I took a quick look.  It looks like the lsb project wants headers
--stripped of all comments and programmer remarks;
the library would be empty functions, as 'basic' as possible.

Possibly headers: sane.h, saneopts.h would be enough, as
lsb tools would only test for the presence of sane, so none of
the libraries in /usr/lib/sane/* would be tested?
/usr/lib/libsane.so would be the basic library.

Does the lsb project expect some testing code to be written?
What tests would be needed, or expected, if any?

Regards,
Gerald