[sane-devel] usb Scanner always busy

2003-11-07 Thread Henning Meier-Geinitz
Hi,

On Thu, Nov 06, 2003 at 08:07:52PM -0500, Gene Heskett wrote:
> Oops, sorry Henning.  The scanner is an Epson Perfection 1250u. 
> sane-backends is 1.0.11 IIRC.  Present kernel is 2.6.0-test9-mm2.

1.0.12 is the current stable version. There are also snapshots of
1.0.13. However I don't remember such a problem.

> xsane, when launched, appears to be ok.  But click on get preview, or 
> just click on the go button, and the return is that its busy, coming 
> back instantly.
> 
> dmesg seems to indicate its found and linked in the normal manner.

Please show us the output of "scanimage -L".

> But click on get preview gets a message box telling me it failed to 
> start the scanner, and does it in just a few hundred milliseconds.

To be sure that no other backend makes trouble, you can disable
everything but yout backend in dll.conf.

> >You can enebale debug messages by setting the environment variable
> >SANE_DEBUG_BACKENDNAME=255 (BACKENDNAME is the name of the backend
> > you use).
> 
> I'm not sure which backend is showing,

"scanimage -L" shows the backend name.

> but let me run it...  Plustek
> seems to be the choice after it wades past a bunch of bttv stuffs and 
> the test backends.

"plustek" or "epkowa" if you have isntalled the latter.

> Setting the env var doesn't seem to effect things either...

Setting it prints debug messages.

E.g. 

SANE_DEBUG_PLUSTEK=255 scanimage -d plustek >image.pnm

Bye,
  Henning



[sane-devel] usb Scanner always busy

2003-11-07 Thread Gene Heskett
On Friday 07 November 2003 15:22, Henning Meier-Geinitz wrote:
>Hi,
>
>On Thu, Nov 06, 2003 at 08:07:52PM -0500, Gene Heskett wrote:
>> Oops, sorry Henning.  The scanner is an Epson Perfection 1250u.
>> sane-backends is 1.0.11 IIRC.  Present kernel is 2.6.0-test9-mm2.
>
>1.0.12 is the current stable version. There are also snapshots of
>1.0.13. However I don't remember such a problem.
>
>> xsane, when launched, appears to be ok.  But click on get preview,
>> or just click on the go button, and the return is that its busy,
>> coming back instantly.
>>
>> dmesg seems to indicate its found and linked in the normal manner.
>
>Please show us the output of "scanimage -L".

[root@coyote linux-2.6]# scanimage -L
device `v4l:/dev/video0' is a Noname BT878 video (Hauppauge (bt878)) virtual 
device
device `v4l:/dev/bttv0' is a Noname BT878 video (Hauppauge (bt878)) virtual 
device
device `test:0' is a Noname frontend-tester virtual device
device `test:1' is a Noname frontend-tester virtual device
device `plustek:/dev/usb/scanner0' is a Epson Perfection 1250/Photo USB flatbed 
scanner

>> But click on get preview gets a message box telling me it failed
>> to start the scanner, and does it in just a few hundred
>> milliseconds.
>
>To be sure that no other backend makes trouble, you can disable
>everything but your backend in dll.conf.
>
>> >You can enebale debug messages by setting the environment
>> > variable SANE_DEBUG_BACKENDNAME=255 (BACKENDNAME is the name of
>> > the backend you use).

Believe it or not, that (export SANE_DEBUG_PLUSTEK) doesn't do a thing!
Absolutely nothing sane related shows up in the log.

>> I'm not sure which backend is showing,
>
>"scanimage -L" shows the backend name.
>
>> but let me run it...  Plustek
>> seems to be the choice after it wades past a bunch of bttv stuffs
>> and the test backends.
>
>"plustek" or "epkowa" if you have isntalled the latter.
>
>> Setting the env var doesn't seem to effect things either...
>
>Setting it prints debug messages.
>
>E.g.
>
>SANE_DEBUG_PLUSTEK=255 scanimage -d plustek >image.pnm

That, clipped to a cli, would appear to be working, the scanner is
actually in motion.  But it finished  very very quickly once the
lamp warmup timeout had elapsed.  Looks like 33 seconds overall
elapsed time, and the image.pnm file is a hair over 111k.

Humm, I wonder if up2date ignored me again, and installed new rpms.
If thats the case, thats the end of that program on my system, its
happened at least twice before.  Mmm, no, no sane here according to
 rpm -qa|grep sane

Ok, scanimage seems to sort of work, why not xsane?

-- 
Cheers, Gene
AMD K6-III@500mhz 320M
Athlon1600XP@1400mhz  512M
99.27% setiathome rank, not too shabby for a WV hillbilly
Yahoo.com attornies please note, additions to this message
by Gene Heskett are:
Copyright 2003 by Maurice Eugene Heskett, all rights reserved.




[sane-devel] Fujitsu M3093GD

2003-11-07 Thread Andi McLean
Thank you so much, that worked.

scanimage wouldn't save the 2nd image but it wasn't giving an error when
setting the window.

I used 
scanadf -dfujitsu:/dev/sg2 --duplex both  --mode=lineart 
and it just worked. 


Thanks for you time and effort

Andi

On Fri, 2003-11-07 at 17:31, m. allan noah wrote:
> On 7 Nov 2003, Andi McLean wrote:
> 
> > On Thu, 2003-11-06 at 08:57, Oliver Schirrmeister wrote:
> > > Am Mit, 2003-11-05 um 21.40 schrieb m. allan noah:
> > > > On 5 Nov 2003, Andi McLean wrote:
> > > > 
> > > > > Hi,
> > > > > 
> > > > > I'm using 
> > > > > red-hat 8.0 
> > > > > sane-backends 1.0.12
> > > > > scanimage 1.0.12
> > > > > and a M3093GD
> > > > > 
> > > > > Scanning the front of the document works perfectly but if I try to 
> > > > > scan
> > > > > the back page I get about 38 rows of blank image. If I try full 
> > > > > duplex I
> > > > > only get the front side. Does any one have any ideas of what causes 
> > > > > this
> > > > > or how to fix it?
> > > > 
> > > > try using scanadf instead of scanimage, and see what that does for the 
> > > > duplex=both situation. for the duplex=back, i am not sure why the image 
> > > > is 
> > > > truncated. try turning on some debug:
> > > 
> > > I'm not shure if the scanner supports back side only. As far as I remember
> > > the fujitsu windows twain-driver doesn't offer this feature.
> > > Duplex scan works with that scanner at least with sane-backends 1.08 
> > > I havn't tried newer versions.
> > You're right about not being able to scan just the back page. 
> > I've turned on debug as suggested and there seems to be a problem when
> > setting up the window.
> > 
> > Selected output follows :-
> >  truncated
> > [fujitsu] wait_scanner
> > [fujitsu] test_unit_ready
> > [fujitsu] 000: 00 00 00 00 00 00
> > [fujitsu]  > [fujitsu] 000: 00 00 00 00 00 00
> > [fujitsu] sanei_scsi_cmd: returning 0 bytes:
> > [fujitsu] wait_scanner: ok
> > [fujitsu] set_window_param
> > [fujitsu] Window set - front
> > [fujitsu] 000: 00 00 01 2c 01 2c 00 00 00 00 00 00 00 00 00 00
> > [fujitsu] 016: 27 d7 00 00 36 cf 00 00 00 02 08 00 00 00 00 00
> > [fujitsu] 032: 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 a0
> > [fujitsu] 048: 20 00 00 00 00 84 00 00 00 00 00 00 00 00 00 00
> > [fujitsu] Window set - back
> > [fujitsu] 000: 80 00 01 2c 01 2c 00 00 00 00 00 00 00 00 00 00
> > [fujitsu] 016: 27 d7 00 00 36 cf 00 00 00 02 08 00 00 00 00 00
> > [fujitsu] 032: 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 a0
> > [fujitsu] 048: 20 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00
> > [fujitsu]  > [fujitsu] 000: 24 00 00 00 00 00 00 00 88 00 00 00 00 00 00 00
> > [fujitsu] 016: 00 40 00 00 01 2c 01 2c 00 00 00 00 00 00 00 00
> > [fujitsu] 032: 00 00 27 d7 00 00 36 cf 00 00 00 02 08 00 00 00
> > [fujitsu] 048: 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00
> > [fujitsu] 064: 00 a0 20 00 00 00 00 84 00 00 00 00 00 00 00 00
> > [fujitsu] 080: 00 00 80 00 01 2c 01 2c 00 00 00 00 00 00 00 00
> > [fujitsu] 096: 00 00 27 d7 00 00 36 cf 00 00 00 02 08 00 00 00
> > [fujitsu] 112: 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00
> > [fujitsu] 128: 00 a0 20 00 00 00 00 00 00 00 00 00 00 00 00 00
> > [fujitsu] 144: 00 00
> > [fujitsu]   5/38/0: Invalid field in parm list 
> > [fujitsu] sanei_scsi_cmd: returning 0x0004
> > [fujitsu] sanei_scsi_cmd: returning 0 bytes:
> > [fujitsu] sane_start: ERROR: failed to set window
> > [fujitsu] freeScanner
> > [fujitsu] release_unit
> 
> you are trying to do an 8bit grayscale, duplex scan. i notice 1 thing now 
> in the manual for the M3093DG: 'duplex reading supports only 0x01' 
> (lineart)
> 
> try setting --mode=lineart and see if that works. if so, i will update the 
> backend to prevent you from trying :)
> 
> allan
> 
> 
> > 
> >  truncated
> > > 
> > if you need any more of the debug info just ask.
> > 
> > Many thanks for your help 
> > 
> > Andi
> > 
> > 
> > 
> > ___
> > sane-devel mailing list
> > sane-devel@lists.alioth.debian.org
> > http://lists.alioth.debian.org/mailman/listinfo/sane-devel
> > 




[sane-devel] Support Canon LiDE20

2003-11-07 Thread OleksiyO.Loktev
Hi by all!

And since what version sane-backends the scanner Canon CanoScan LiDE20 
is supported?

Beforehand I thank for support.
___
Oleksiy O. Loktev the system engineer a...@shepet-mk.pointclark.net
UKRAINEPh.: +38 (03840) 5 6071/6036
Khmelnitskiy area  Fax: +38 (03840) 5 3711
OJSC of Shepetivka Meat FactoryMob.:+38 (067) 2568555
30430, Sudylkiv of Khmelnitskiy area, 3, Gagarina Street
=== 






[sane-devel] Fujitsu M3093GD

2003-11-07 Thread Andi McLean
On Thu, 2003-11-06 at 08:57, Oliver Schirrmeister wrote:
> Am Mit, 2003-11-05 um 21.40 schrieb m. allan noah:
> > On 5 Nov 2003, Andi McLean wrote:
> > 
> > > Hi,
> > > 
> > > I'm using 
> > > red-hat 8.0 
> > > sane-backends 1.0.12
> > > scanimage 1.0.12
> > > and a M3093GD
> > > 
> > > Scanning the front of the document works perfectly but if I try to scan
> > > the back page I get about 38 rows of blank image. If I try full duplex I
> > > only get the front side. Does any one have any ideas of what causes this
> > > or how to fix it?
> > 
> > try using scanadf instead of scanimage, and see what that does for the 
> > duplex=both situation. for the duplex=back, i am not sure why the image is 
> > truncated. try turning on some debug:
> 
> I'm not shure if the scanner supports back side only. As far as I remember
> the fujitsu windows twain-driver doesn't offer this feature.
> Duplex scan works with that scanner at least with sane-backends 1.08 
> I havn't tried newer versions.
You're right about not being able to scan just the back page. 
I've turned on debug as suggested and there seems to be a problem when
setting up the window.

Selected output follows :-
 truncated
[fujitsu] wait_scanner
[fujitsu] test_unit_ready
[fujitsu] 000: 00 00 00 00 00 00
[fujitsu]  
if you need any more of the debug info just ask.

Many thanks for your help 

Andi





[sane-devel] SANE OS X 10.3 Install Problems

2003-11-07 Thread Erick Schmidt
Hi,

Has anyone been able to successfully install SANE on a OS X box running 
10.3 (Panther)? I tried installing the new version of SANE 1.0.13 and 
SANE 1.0.12 and received the following error:


...
sanei_scsi.c: In function `sanei_scsi_req_wait':
sanei_scsi.c:5935: warning: unused parameter `id'
sanei_scsi.c: In function `sanei_scsi_req_flush_all_extended':
sanei_scsi.c:5944: warning: unused parameter `fd'
make[1]: *** [sanei_scsi.o] Error 1
make: *** [all-recursive] Error 1
g5:/build/sane-backends-1.0.13-pre1 root#

Thanks for the help.




[sane-devel] Fujitsu M3093GD

2003-11-07 Thread m. allan noah
On 7 Nov 2003, Andi McLean wrote:

> On Thu, 2003-11-06 at 08:57, Oliver Schirrmeister wrote:
> > Am Mit, 2003-11-05 um 21.40 schrieb m. allan noah:
> > > On 5 Nov 2003, Andi McLean wrote:
> > > 
> > > > Hi,
> > > > 
> > > > I'm using 
> > > > red-hat 8.0 
> > > > sane-backends 1.0.12
> > > > scanimage 1.0.12
> > > > and a M3093GD
> > > > 
> > > > Scanning the front of the document works perfectly but if I try to scan
> > > > the back page I get about 38 rows of blank image. If I try full duplex I
> > > > only get the front side. Does any one have any ideas of what causes this
> > > > or how to fix it?
> > > 
> > > try using scanadf instead of scanimage, and see what that does for the 
> > > duplex=both situation. for the duplex=back, i am not sure why the image 
> > > is 
> > > truncated. try turning on some debug:
> > 
> > I'm not shure if the scanner supports back side only. As far as I remember
> > the fujitsu windows twain-driver doesn't offer this feature.
> > Duplex scan works with that scanner at least with sane-backends 1.08 
> > I havn't tried newer versions.
> You're right about not being able to scan just the back page. 
> I've turned on debug as suggested and there seems to be a problem when
> setting up the window.
> 
> Selected output follows :-
>  truncated
> [fujitsu] wait_scanner
> [fujitsu] test_unit_ready
> [fujitsu] 000: 00 00 00 00 00 00
> [fujitsu]  [fujitsu] 000: 00 00 00 00 00 00
> [fujitsu] sanei_scsi_cmd: returning 0 bytes:
> [fujitsu] wait_scanner: ok
> [fujitsu] set_window_param
> [fujitsu] Window set - front
> [fujitsu] 000: 00 00 01 2c 01 2c 00 00 00 00 00 00 00 00 00 00
> [fujitsu] 016: 27 d7 00 00 36 cf 00 00 00 02 08 00 00 00 00 00
> [fujitsu] 032: 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 a0
> [fujitsu] 048: 20 00 00 00 00 84 00 00 00 00 00 00 00 00 00 00
> [fujitsu] Window set - back
> [fujitsu] 000: 80 00 01 2c 01 2c 00 00 00 00 00 00 00 00 00 00
> [fujitsu] 016: 27 d7 00 00 36 cf 00 00 00 02 08 00 00 00 00 00
> [fujitsu] 032: 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 a0
> [fujitsu] 048: 20 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00
> [fujitsu]  [fujitsu] 000: 24 00 00 00 00 00 00 00 88 00 00 00 00 00 00 00
> [fujitsu] 016: 00 40 00 00 01 2c 01 2c 00 00 00 00 00 00 00 00
> [fujitsu] 032: 00 00 27 d7 00 00 36 cf 00 00 00 02 08 00 00 00
> [fujitsu] 048: 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00
> [fujitsu] 064: 00 a0 20 00 00 00 00 84 00 00 00 00 00 00 00 00
> [fujitsu] 080: 00 00 80 00 01 2c 01 2c 00 00 00 00 00 00 00 00
> [fujitsu] 096: 00 00 27 d7 00 00 36 cf 00 00 00 02 08 00 00 00
> [fujitsu] 112: 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00
> [fujitsu] 128: 00 a0 20 00 00 00 00 00 00 00 00 00 00 00 00 00
> [fujitsu] 144: 00 00
> [fujitsu]   5/38/0: Invalid field in parm list 
> [fujitsu] sanei_scsi_cmd: returning 0x0004
> [fujitsu] sanei_scsi_cmd: returning 0 bytes:
> [fujitsu] sane_start: ERROR: failed to set window
> [fujitsu] freeScanner
> [fujitsu] release_unit

you are trying to do an 8bit grayscale, duplex scan. i notice 1 thing now 
in the manual for the M3093DG: 'duplex reading supports only 0x01' 
(lineart)

try setting --mode=lineart and see if that works. if so, i will update the 
backend to prevent you from trying :)

allan


> 
>  truncated
> > 
> if you need any more of the debug info just ask.
> 
> Many thanks for your help 
> 
> Andi
> 
> 
> 
> ___
> sane-devel mailing list
> sane-devel@lists.alioth.debian.org
> http://lists.alioth.debian.org/mailman/listinfo/sane-devel
> 

-- 
"so don't tell us it can't be done, putting down what you don't know.
money isn't our god, integrity will free our souls" - Max Cavalera




[sane-devel] HP ScanJet 4100C - assertion failed

2003-11-07 Thread Yves Martin
Selon Henning Meier-Geinitz :

> >   I'm almost sure APIC is enabled. I have no other USB issue with my
> usb-key
> >   for instance... I have two USB hubs and maybe it depends the plug I
> choosed.
> >   I may work-around the issue unloading the ESSCOM module.
> 
> Try without APIC. Isn't it only needed on multi-processor boards?

  Hello Henning and others,

 I'm back again after some weeks. I have more information about my ScanJet
 4100C connected to my HP omnibook xt1000s.

 First, I have succeeded in installing the 4100C driver on my windows XP.
 I have done all the installation process manually (copy files from a old 98),
 apply the HP patch - and the Precision LT tool do not want to work anyway.
 But the copy tool (scanjet -> printer) and the XP scanner wizard are able to
 use the scanner.
 Conclusion: the scanner, the cable and the USB hub are OK.

 Now, on Linux: I have build my kernel many times with different options.

 Finally the USB seems not to work correctly if Local APIC is disabled or
 if ACPI is disabled. In some cases, the bus does not appear in /proc, on
 the bus appears but the USB devices are not detected (scanner, usb storage).

 My config: mandrake 9.1 with a kernel 2.4.21 with patches:
 - ACPI, software suspend (swsusp) with laptop mode, NTFS (ro), supermount

 With that configuration, I have many log in /var/log/messages:
   usb_control/bulk_msg: timeout
 when the scanner is detected - because it is not so obvious.

 Have you got any advice ? I think I will try the 2.6 kernel - it should
 manage USB and ACPI better... What do you think ?

 Thank you for your help
-- 
Yves Martin