hp3300backend-devel — Development of SANE backend for HP ScanJet 3300/3400/4300 scanners

[Hp3300backend-devel] problems compiling with libusb 0.1.8b

[Rainer L. <La...@in...>]

Hi,

I tried to compile the driver an a SuSE 9.0 machine:

cd ../testtool
./patch-sane.sh ../sane-backends-1.0.13
Adding new files to the SANE source tree...      DONE
Modifying doc/Makefile.in...                     DONE
Modifying backend/Makefile.in...                 DONE
Relocating files...                              DONE
Modifying backend/dll.conf...                    DONE
SANE patched with success!
+ make clean
rm -f *.o testtool *~
+ make
gcc -Wall -g -DLINUX_USB_SUPPORT -DLIBUSB_SUPPORT   -c -o main.o main.c
In file included from hp3300c_libusb.c:33,
                  from main.c:36:
/usr/include/usb.h:55: error: redefinition of `struct usb_descriptor_header'
/usr/include/usb.h:61: error: redefinition of `struct usb_string_descriptor'
/usr/include/usb.h:78: error: redefinition of `struct 
usb_endpoint_descriptor'
/usr/include/usb.h:103: error: redefinition of `struct 
usb_interface_descriptor'
/usr/include/usb.h:129: error: redefinition of `struct 
usb_config_descriptor'
/usr/include/usb.h:146: error: redefinition of `struct 
usb_device_descriptor'
make: *** [main.o] Fehler 1

I am using SuSEs libusb-0.1.8beta-39 version of libusb.
Any hints?

kind regards,
Rainer

[Hp3300backend-devel] Hp3300C on RH9

[Franco S. <fr...@ti...>]

I have get latest version of testtool and rebuild RH9.0 rpm for
sane-backends (1.0.9 version). Now all is working ok but, starting
Xsane, I get 2 devices: one for USB from kernel and one for USB from
libusb (/dev/usb/scanner0 and libusb:001:003). Can I remove second
device or define first as default ?
In Xsane there is no "scanmode" button and I can't use Lineart or Gray
scan mode but only full color. Is a niash drive limitation or I am
missing some piece ?

Regards
Franco

[Hp3300backend-devel] New module in cvs: backend

[Bertrik S. <be...@zo...>]

Hi all,

I just checked in a new module, named simply 'backend'.
It is based on the 'testtool' module, but now with
emphasis on being a sane backend.

I renamed all hp3300* files into niash*, also renamed
functions from hp3300* to niash*.

The multiple USB access method mechanism is now pulled
out and replaced by the built-in usb functions from
sane (which will also try to use both libusb and the
scanner kernel module).

It compiles and works as a backend. The testtool does
currently not work yet.
For compatibility with the testtool, we can add the
multiple USB access method back in by creating a
sanei_usb stub. This should be mostly a copy/paste/
rename action from the original hp3300c_xfer.c file.

Since this conversion started some time ago, the files
are not completely in sync with the 'testtool' files.
(On the other hand, the latest changes seem to be related
to Kooka compatibility and I'm not sure if we should add
explicit code to make the backend work with Kooka, i.o.w.
work around Kooka bugs.)

All the best,
Bertrik

[Hp3300backend-devel] Re: What do you think?

[Bertrik S. <be...@zo...>]

(cc: to hp3300-devel)

Hi Ullrich,

Indeed sane inclusion is long due now.

What I think needs to be done is:
* renaming files to niash
* remove USB plugin mechanism and rely on the sanei_usb functions
(for the testtool we can keep the USB plugin mechanism when we
re-implement sanei-usb)

Less critical:
* implement coarse calibration
* simplify functions by removing a lot of function arguments
and placing them somewhere in the scanparams or hwprops
structures.

I'll make a start with this this week.

Regards,
Bertrik

Ullrich Sigwanz wrote:
> There are still some small tasks,
> 
> but the main issue is installation now.
> 
> I would suggest that  we (mainly I) will implement the main
> 
> missing parts after my holidays next week and hand the
> 
> bundle over to the sane guys.
> 
> 
> 
> Is this ok for you?
> 
> 
> 
> Kind regards
> 
> 
> 
> Ullrich
> 

Re: [Hp3300backend-devel] HP 3400Cse scanner WORKING!

[Steven A. D. <lin...@mi...>]

YAHOO! It works! or at least I actually got a PPM data file out and the scanner did not
"lock up"

Instead of giving it a command like:

./testtool -u /dev/usb/scanner0 -s 4,5

I tried:

./testtool -u /dev/usb/scanner0 -s 400,500

and it seemed to work. I got a 600K data file out and the scanner shut off when it was done.

Perhaps somewhere in the project documentation or the testtool usage message there should
be some mention of "units' or relative size suggestions for the arguments to the "-s"
option to testtool.
-- 
Steven A. DuChene     lin...@mi...
                      sdu...@mi...

[Hp3300backend-devel] Re: HP 3400Cse scanner not working

[Steven A. D. <lin...@mi...>]

Sorry, I did not see the reply below:

My next question is for testtool when you try to give it an area to scan what units
should the arguments to the "-s" option be? Are were talking pixels, inches, millimeters,
or what? When I executed the following:

./testtool -u /dev/usb/scanner0 -s 4,5

perhaps I am assuming the wrong units and therefor my assigned scan "strip" is too narrow.
Steven A. DuChene wrote:
 > I just pulled the latest cvs sources and tried them on a HP 3400Cse (what it says on
outside
 > of the box) and it does not respond as expected. I am using linux kernel method with
kernel
 > from Mandrake (2.4.19-16mdk) since it has support for Win4Lin modules I also run. They
are
 > not loaded BTW when I do these tests.
 > 
 > Product number from the scanner box is C7720A  ABA  CN1281F06Y
 > 
 > If I do any commands with testtool I get the following in the dmesg output:
 > 
 > scanner.c: open_scanner(1): Unable to access minor data
 > scanner.c: open_scanner(2): Unable to access minor data
 > scanner.c: open_scanner(3): Unable to access minor data
 > scanner.c: open_scanner(4): Unable to access minor data
 > scanner.c: open_scanner(5): Unable to access minor data
 > scanner.c: open_scanner(6): Unable to access minor data
 > scanner.c: open_scanner(7): Unable to access minor data
 > scanner.c: open_scanner(8): Unable to access minor data
 > scanner.c: open_scanner(9): Unable to access minor data
 > scanner.c: open_scanner(10): Unable to access minor data
 > scanner.c: open_scanner(11): Unable to access minor data
 > scanner.c: open_scanner(12): Unable to access minor data
 > scanner.c: open_scanner(13): Unable to access minor data
 > scanner.c: open_scanner(14): Unable to access minor data
 > scanner.c: open_scanner(15): Unable to access minor data
  >
  > and it repeats over and over.
  >
 
 As far as I know, this is just a noisy warning message, not
 a real error. I remember seeing this fixed in the latest versions
 of the scanner module (perhaps only in kernel 2.5.x yet).
 This seems to be caused by attempts to open 
 /dev/usb/scanner0../dev/usb/scanner16
 Anyway, the message is harmless and is no reason to upgrade the kernel.
 
 > If I run "./testtool -u /dev/usb/scanner0 -ov"
 > the output looks like:
 > 
 > Initializing scanner
 > Registering transfer method 0: Linux scanner kernel module
 > VendorId 0x03F0, ProductId 0x0405
 > Matching USB device 0x03F0-0x0405 ... found Hewlett-Packard ScanJet 3400C
 > _ReportDevice '/dev/usb/scanner0'
 > Hp3300cXferOpen '/dev/usb/scanner0'
 > probing Linux scanner kernel module
 > Matching USB device 0x03F0-0x0405 ... found Hewlett-Packard ScanJet 3400C
 > Setting params for Hp3400c/Hp4300c
 > Probing scanner...
 >   Gamma table entries are 16 bit
 >   NIASH version > 00014
 > Creating calibration file
 > _iScaleDown (Dpi,Lpi) = (1,1)
 > _iBytesPerLine = 15900
 > _iLinesPerCircBuf = 12
 > Allocated 190800 bytes for circular buffer
 > _iLinesPerXferBuf = 3
 > Xfer block size = 47700
 > buffer level =  69, <reading 47700 bytes>, buffer level =  72
 > Black level (11,6,5), White level (40,27,25)
 
 This looks OK.
 
 > If I do a register dump it appears to have different register contents
 > from what is shown for the 3400C at:
 > 
 > http://home.kabelfoon.nl/~bertrik/hp3300c/devel.html
 > 
 > (bottom of the page)
 > 
 > Anyway when I do a register dump I get:
 > 
 >  ./testtool -u /dev/usb/scanner0 -p
 > 
 > 0000 0D 0D 0D 4C 07 0D 40 02
 > 0008 0D 0D 0D 0D 0D 0D 0D 0D
 > 0010 0D 0D 0D 0D 0D 0D 0D 0D
 > 0018 0D 0D 0D 0D 0D 0D 0D 0D
 > 0020 00 0D 0D 0D 21 00 00 22
 > 0028 01 03 79 00 00 00 00 00
 > 0030 00 00 00 00 00 00 00 00
 > 0038 3B 0C 43 01 01 01 00 00
 
 This also seems to be OK.
 Some registers are write-only and return garbage when read.
 
 > I can turn the lamp on and off but when I try "./testtool -u /dev/usb/scanner0 -s 4,5 >
stufferty"
 > it "looks like it is scanning but I get a zero length file. Also once I have tried the
above scan
 > command I can no longer access the scanner. When I do I get an error message about:
 > 
 > ./testtool -u /dev/usb/scanner0 -l
 >   No NIASH chipset found!
 > _ProbeRegisters failed!
 > 
 > If I unplug the USB cable and plug it back in then I can do stuff again until I actually
try a
 > scan again.
 > 
 > BTW, when I try a scan it move the bar about half way do the track, it pauses, and then
it
 > moves to the end of the track but does not stop! It grinds a while and then stops. It
will
 > try to move beyond the end of the track again a few seconds later until I end the above
 > command with a Ctrl-C    Also the scan command never returns and I HAVE to Ctrl-C it.
 > Is it supposed to scan and then return?
 
 I think the testtool does not behave really well when trying to scan
 very narrow strips. I'm not sure why, maybe this is a hardware
 limitation.
 The grinding noise is probably caused by the transfer buffer mechanism
 in the software. This mechanism tries to read data from the scanner in
 blocks of size 0xF000 (to optimise USB transfer overhead). When scanning
 a narrow strip, it needs to scan too far in order to read the full
 0xF000 block and so it goes past the scan area.
 This probably needs a fix, or some mechanism to prevent it (like
 imposing a minimum to the width).
 
 Basically, it seems that your scanner mostly works.
 Please just try it with a bigger width (like 1000 pixels)
 
 Kind regards,
 Bertrik

-- 
Steven A. DuChene     lin...@mi...
                      sdu...@mi...

[Hp3300backend-devel] is this project dead?

[Steven A. D. <lin...@mi...>]

On June 14, 2003 12:52 am, you wrote:
> On the 8th of June I wrote a fairly detailed E-mail talking about the
> problems I was having trying to get the testtool working with a HP
> 3400Cse scanner but I have yet to see any messages back. Is the author of
> this driver still around?

I have not seen any more E-mail or activity around this driver for quite some time.
Is any still looking into additional development? As I stated above I have a
3400Cse scanner that does not work with the March version of the code tree and
I would be willing to try additional tests or data captures to see if some
progress could be made.
-- 
Steven A. DuChene     lin...@mi...
                      sdu...@mi...

Re: [Hp3300backend-devel] HP 3400Cse scanner not working

[Bertrik S. <be...@zo...>]

Steven A. DuChene wrote:
> I just pulled the latest cvs sources and tried them on a HP 3400Cse (what it says on outside
> of the box) and it does not respond as expected. I am using linux kernel method with kernel
> from Mandrake (2.4.19-16mdk) since it has support for Win4Lin modules I also run. They are
> not loaded BTW when I do these tests.
> 
> Product number from the scanner box is C7720A  ABA  CN1281F06Y
> 
> If I do any commands with testtool I get the following in the dmesg output:
> 
> scanner.c: open_scanner(1): Unable to access minor data
> scanner.c: open_scanner(2): Unable to access minor data
> scanner.c: open_scanner(3): Unable to access minor data
> scanner.c: open_scanner(4): Unable to access minor data
> scanner.c: open_scanner(5): Unable to access minor data
> scanner.c: open_scanner(6): Unable to access minor data
> scanner.c: open_scanner(7): Unable to access minor data
> scanner.c: open_scanner(8): Unable to access minor data
> scanner.c: open_scanner(9): Unable to access minor data
> scanner.c: open_scanner(10): Unable to access minor data
> scanner.c: open_scanner(11): Unable to access minor data
> scanner.c: open_scanner(12): Unable to access minor data
> scanner.c: open_scanner(13): Unable to access minor data
> scanner.c: open_scanner(14): Unable to access minor data
> scanner.c: open_scanner(15): Unable to access minor data
 >
 > and it repeats over and over.
 >

As far as I know, this is just a noisy warning message, not
a real error. I remember seeing this fixed in the latest versions
of the scanner module (perhaps only in kernel 2.5.x yet).
This seems to be caused by attempts to open 
/dev/usb/scanner0../dev/usb/scanner16
Anyway, the message is harmless and is no reason to upgrade the kernel.

> If I run "./testtool -u /dev/usb/scanner0 -ov"
> the output looks like:
> 
> Initializing scanner
> Registering transfer method 0: Linux scanner kernel module
> VendorId 0x03F0, ProductId 0x0405
> Matching USB device 0x03F0-0x0405 ... found Hewlett-Packard ScanJet 3400C
> _ReportDevice '/dev/usb/scanner0'
> Hp3300cXferOpen '/dev/usb/scanner0'
> probing Linux scanner kernel module
> Matching USB device 0x03F0-0x0405 ... found Hewlett-Packard ScanJet 3400C
> Setting params for Hp3400c/Hp4300c
> Probing scanner...
>   Gamma table entries are 16 bit
>   NIASH version > 00014
> Creating calibration file
> _iScaleDown (Dpi,Lpi) = (1,1)
> _iBytesPerLine = 15900
> _iLinesPerCircBuf = 12
> Allocated 190800 bytes for circular buffer
> _iLinesPerXferBuf = 3
> Xfer block size = 47700
> buffer level =  69, <reading 47700 bytes>, buffer level =  72
> Black level (11,6,5), White level (40,27,25)

This looks OK.

> If I do a register dump it appears to have different register contents
> from what is shown for the 3400C at:
> 
> http://home.kabelfoon.nl/~bertrik/hp3300c/devel.html
> 
> (bottom of the page)
> 
> Anyway when I do a register dump I get:
> 
>  ./testtool -u /dev/usb/scanner0 -p
> 
> 0000 0D 0D 0D 4C 07 0D 40 02
> 0008 0D 0D 0D 0D 0D 0D 0D 0D
> 0010 0D 0D 0D 0D 0D 0D 0D 0D
> 0018 0D 0D 0D 0D 0D 0D 0D 0D
> 0020 00 0D 0D 0D 21 00 00 22
> 0028 01 03 79 00 00 00 00 00
> 0030 00 00 00 00 00 00 00 00
> 0038 3B 0C 43 01 01 01 00 00

This also seems to be OK.
Some registers are write-only and return garbage when read.

> I can turn the lamp on and off but when I try "./testtool -u /dev/usb/scanner0 -s 4,5 > stufferty"
> it "looks like it is scanning but I get a zero length file. Also once I have tried the above scan
> command I can no longer access the scanner. When I do I get an error message about:
> 
> ./testtool -u /dev/usb/scanner0 -l
>   No NIASH chipset found!
> _ProbeRegisters failed!
> 
> If I unplug the USB cable and plug it back in then I can do stuff again until I actually try a
> scan again.
> 
> BTW, when I try a scan it move the bar about half way do the track, it pauses, and then it
> moves to the end of the track but does not stop! It grinds a while and then stops. It will
> try to move beyond the end of the track again a few seconds later until I end the above
> command with a Ctrl-C    Also the scan command never returns and I HAVE to Ctrl-C it.
> Is it supposed to scan and then return?

I think the testtool does not behave really well when trying to scan
very narrow strips. I'm not sure why, maybe this is a hardware
limitation.
The grinding noise is probably caused by the transfer buffer mechanism
in the software. This mechanism tries to read data from the scanner in
blocks of size 0xF000 (to optimise USB transfer overhead). When scanning
a narrow strip, it needs to scan too far in order to read the full
0xF000 block and so it goes past the scan area.
This probably needs a fix, or some mechanism to prevent it (like
imposing a minimum to the width).

Basically, it seems that your scanner mostly works.
Please just try it with a bigger width (like 1000 pixels)

Kind regards,
Bertrik

Re: [Hp3300backend-devel] anyone still around???

[Bertrik S. <be...@zo...>]

Steven A. DuChene wrote:
> On the 8th of June I wrote a fairly detailed E-mail talking about the
> problems I was having trying to get the testtool working with a HP
> 3400Cse scanner but I have yet to see any messages back. Is the
> author of this driver still around?

Yes, I'm still around and I'll get back to your previous question later
this weekend.

Regards,
Bertrik Sikken

Re: [Hp3300backend-devel] anyone still around???

[Ian T. <its...@ya...>]

On June 14, 2003 12:52 am, you wrote:
> On the 8th of June I wrote a fairly detailed E-mail talking about the
> problems I was having trying to get the testtool working with a HP
> 3400Cse scanner but I have yet to see any messages back. Is the author of
> this driver still around?
=========

Steven the activity seems sporadic.. I'm not sure how much is going on but 
I'm certainly listening..  I suppose more testing would be of more use 
thought.  <g>  His contact information might be available through 
sourceforge if that's any help.
Cheers!  Ian.
-- 
http://www.amical.net  - The Friendly IRC Network. 
 

[Hp3300backend-devel] anyone still around???

[Steven A. D. <lin...@mi...>]

On the 8th of June I wrote a fairly detailed E-mail talking about the problems I was having
trying to get the testtool working with a HP 3400Cse scanner but I have yet to see any messages
back. Is the author of this driver still around?
-- 
Steven A. DuChene     lin...@mi...
                      sdu...@mi...

[Hp3300backend-devel] HP 3400Cse scanner not working

[Steven A. D. <lin...@mi...>]

I just pulled the latest cvs sources and tried them on a HP 3400Cse (what it says on outside
of the box) and it does not respond as expected. I am using linux kernel method with kernel
from Mandrake (2.4.19-16mdk) since it has support for Win4Lin modules I also run. They are
not loaded BTW when I do these tests.

Product number from the scanner box is C7720A  ABA  CN1281F06Y

If I do any commands with testtool I get the following in the dmesg output:

scanner.c: open_scanner(1): Unable to access minor data
scanner.c: open_scanner(2): Unable to access minor data
scanner.c: open_scanner(3): Unable to access minor data
scanner.c: open_scanner(4): Unable to access minor data
scanner.c: open_scanner(5): Unable to access minor data
scanner.c: open_scanner(6): Unable to access minor data
scanner.c: open_scanner(7): Unable to access minor data
scanner.c: open_scanner(8): Unable to access minor data
scanner.c: open_scanner(9): Unable to access minor data
scanner.c: open_scanner(10): Unable to access minor data
scanner.c: open_scanner(11): Unable to access minor data
scanner.c: open_scanner(12): Unable to access minor data
scanner.c: open_scanner(13): Unable to access minor data
scanner.c: open_scanner(14): Unable to access minor data
scanner.c: open_scanner(15): Unable to access minor data

and it repeats over and over.

If I run "./testtool -u /dev/usb/scanner0 -ov"
the output looks like:

Initializing scanner
Registering transfer method 0: Linux scanner kernel module
VendorId 0x03F0, ProductId 0x0405
Matching USB device 0x03F0-0x0405 ... found Hewlett-Packard ScanJet 3400C
_ReportDevice '/dev/usb/scanner0'
Hp3300cXferOpen '/dev/usb/scanner0'
probing Linux scanner kernel module
Matching USB device 0x03F0-0x0405 ... found Hewlett-Packard ScanJet 3400C
Setting params for Hp3400c/Hp4300c
Probing scanner...
  Gamma table entries are 16 bit
  NIASH version > 00014
Creating calibration file
_iScaleDown (Dpi,Lpi) = (1,1)
_iBytesPerLine = 15900
_iLinesPerCircBuf = 12
Allocated 190800 bytes for circular buffer
_iLinesPerXferBuf = 3
Xfer block size = 47700
buffer level =  69, <reading 47700 bytes>, buffer level =  72
Black level (11,6,5), White level (40,27,25)

If I do a register dump it appears to have different register contents
from what is shown for the 3400C at:

http://home.kabelfoon.nl/~bertrik/hp3300c/devel.html

(bottom of the page)

Anyway when I do a register dump I get:

 ./testtool -u /dev/usb/scanner0 -p

0000 0D 0D 0D 4C 07 0D 40 02
0008 0D 0D 0D 0D 0D 0D 0D 0D
0010 0D 0D 0D 0D 0D 0D 0D 0D
0018 0D 0D 0D 0D 0D 0D 0D 0D
0020 00 0D 0D 0D 21 00 00 22
0028 01 03 79 00 00 00 00 00
0030 00 00 00 00 00 00 00 00
0038 3B 0C 43 01 01 01 00 00

I can turn the lamp on and off but when I try "./testtool -u /dev/usb/scanner0 -s 4,5 > stufferty"
it "looks like it is scanning but I get a zero length file. Also once I have tried the above scan
command I can no longer access the scanner. When I do I get an error message about:

./testtool -u /dev/usb/scanner0 -l
  No NIASH chipset found!
_ProbeRegisters failed!

If I unplug the USB cable and plug it back in then I can do stuff again until I actually try a
scan again.

BTW, when I try a scan it move the bar about half way do the track, it pauses, and then it
moves to the end of the track but does not stop! It grinds a while and then stops. It will
try to move beyond the end of the track again a few seconds later until I end the above
command with a Ctrl-C    Also the scan command never returns and I HAVE to Ctrl-C it.
Is it supposed to scan and then return?
-- 
Steven A. DuChene     lin...@mi...
                      sdu...@mi...

[Hp3300backend-devel] testtool-20030401

[Jacques C. <Jac...@wa...>]

Good morning,

merely for information :
the combination
-Scanner scanjet 4300c
-testtool-20030401_1
-gimp-1.3
-sane-backends-1.0.12-pre1
-sane-frontends-1.0.11

works very fine here at home.
Best regards.
------
Jac...@wa... f6cwo
Quelques HOWTO en français http://perso.wanadoo.fr/jacques.chion/

Re: [Hp3300backend-devel] hp3300c under FreeBSD

[Bertrik S. <be...@zo...>]

Géczi Szabolcs wrote:
> Hello,
> 
> I use FreeBSD 4.8, I downloaded the testtool (20030401_1), the
> sane-backends (1.0.11), compiled them but I cannot use my scanner.
> The scanimage says - no SANE devices found, the testtool says -
> USB_GET_DEVICEINFO not supported, check version of the uscanner
> driverCannot open : No such file or directory
> Hp3300cXferOpen failed for ''
> Hp3300cOpen failed.
> kldstat says my uscanner.ko is loaded :  9    1 0xc05e8000 34f0    
> uscanner.ko.
> I try to edit testtool's Makefile to use libusb (0.1.7) or use kernel's
> uscanner support, but the result was the same, sane cannot locate the
> device.
> Btw, sane-find-scanner's output here: found USB scanner (UNKNOWN vendor
> and product) at device /dev/uscanner0
> -su-2.05b# scanimage -L
> No scanners were identified
> 
> What should I do?

I don't have any experience with FreeBSD, but it sounds indeed like
something is missing in the uscanner driver.
 From sane version 1.0.8 upwards, sane should be able to provide USB
access through libusb, so you don't need to edit any Makefiles.

Scanimage -L should be able to detect the scanner through libusb,
otherwise the solution seems quite hard.

Kind regards,
Bertrik Sikken

[Hp3300backend-devel] hp3300c under FreeBSD

[S. <cs...@ma...>]

Hello,

I use FreeBSD 4.8, I downloaded the testtool (20030401_1), the
sane-backends (1.0.11), compiled them but I cannot use my scanner.
The scanimage says - no SANE devices found, the testtool says -
USB_GET_DEVICEINFO not supported, check version of the uscanner
driverCannot open : No such file or directory
Hp3300cXferOpen failed for ''
Hp3300cOpen failed.
kldstat says my uscanner.ko is loaded :  9    1 0xc05e8000 34f0    
uscanner.ko.
I try to edit testtool's Makefile to use libusb (0.1.7) or use kernel's
uscanner support, but the result was the same, sane cannot locate the
device.
Btw, sane-find-scanner's output here: found USB scanner (UNKNOWN vendor
and product) at device /dev/uscanner0
-su-2.05b# scanimage -L
No scanners were identified

What should I do?

thx

szabszi

Re: [Hp3300backend-devel] 3400C -- probing scanner failed, hiash chip not found

[Bertrik S. <be...@zo...>]

I don't see anything obvious that is going wrong.
The testtool is somehow not able to verify the presence of the
niash chipset.

One thing you could try is to use a different usb controller
driver, usb-uhci instead of uhci:
	modprobe -r uhci
	modprobe usb-uhci
(as root)
Sometimes one driver works better, sometimes the other, I guess
it depends a bit on the version of the kernel you're using.

Regards,
Bertrik


Florian Mickler wrote:
> Hi again!
> 
> disconnect the usb-plug and then reconnect gives me the following output...
> =============================================================
> uhci.c: root-hub INT complete: port1: 48a port2: 480 data: 2
> uhci.c: dc00: suspend_hc
> hub.c: port 1, portstatus 100, change 3, 12 Mb/s
> hub.c: port 1 connection change
> hub.c: port 1, portstatus 100, change 3, 12 Mb/s
> usb.c: USB disconnect on device 00:11.3-1 address 9
> usb.c: kusbd: /sbin/hotplug remove 9
> hub.c: port 2, portstatus 100, change 0, 12 Mb/s
> uhci.c: root-hub INT complete: port1: 488 port2: 480 data: 2
> hub.c: port 1, portstatus 100, change 2, 12 Mb/s
> hub.c: port 1 enable change, status 100
> hub.c: port 2, portstatus 100, change 0, 12 Mb/s
> uhci.c: dc00: wakeup_hc
> uhci.c: root-hub INT complete: port1: 49b port2: 480 data: 2
> hub.c: port 1, portstatus 101, change 3, 12 Mb/s
> hub.c: port 1 connection change
> hub.c: port 1, portstatus 101, change 3, 12 Mb/s
> hub.c: port 1, portstatus 101, change 2, 12 Mb/s
> hub.c: port 1, portstatus 101, change 2, 12 Mb/s
> uhci.c: root-hub INT complete: port1: 499 port2: 480 data: 2
> hub.c: port 1, portstatus 101, change 2, 12 Mb/s
> hub.c: port 1, portstatus 101, change 2, 12 Mb/s
> hub.c: port 1, portstatus 103, change 0, 12 Mb/s
> hub.c: new USB device 00:11.3-1, assigned address 10
> usb.c: kmalloc IF c6da6580, numif 1
> usb.c: new device strings: Mfr=10, Product=11, SerialNumber=12
> usb.c: USB device number 10 default language ID 0x409
> Manufacturer: Hewlett-Packard
> Product: Hewlett-Packard ScanJet 3400C
> SerialNumber: CN0AO1D0P8TG
> usb.c: usbscanner driver claimed interface c6da6580
> usb.c: kusbd: /sbin/hotplug add 10
> hub.c: port 2, portstatus 100, change 0, 12 Mb/s
> hub.c: port 1, portstatus 103, change 0, 12 Mb/s
> hub.c: port 2, portstatus 100, change 0, 12 Mb/s
> usb_control/bulk_msg: timeout
> usbdevfs: USBDEVFS_CONTROL failed dev 10 rqt 128 rq 6 len 9 ret -110
> ... snip (last 2 message repeatet 50 or so times) ...
> ====================================================================
> then i run testtool -v
> 
> in dmesg there are then dozens of:
> ======================================
> scanner.c: ioctl_scanner(0): control_msg returned -110
> 
> usb_control/bulk_msg: timeout
> scanner.c: ioctl_scanner(0): control_msg returned -110
> 
> usb_control/bulk_msg: timeout
> ======================================
> 
> lsusb:
> =======================================
> Unknown line at line 1809
> Duplicate HUT Usage Spec at line 2650
> Bus 003 Device 001: ID 0000:0000 Virtual Hub
> Bus 002 Device 001: ID 0000:0000 Virtual Hub
> Bus 002 Device 010: ID 03f0:0405 Hewlett-Packard ScanJet 3400cse
> Bus 001 Device 001: ID 0000:0000 Virtual Hub
> =======================================
> 
> so.. where could be the problem?
> 
> i think it is clear now that it is no testtool-problem... so im sorry to bother you... but ... is there someone who has an idea where i could look for solving this problem?
> 
> i will try (next week or so) to reach an windows-machine and test the usb-interface of the scanner with the official hp-scanner driver
> 
> but in the meantime... could it be some other error?
> someone a guess perhaps? 
> 
> 
> greetings, 
> Florian Mickler
> 
> On Wed, 23 Apr 2003 14:30:54 +0200
> Florian Mickler <mi...@d-...> wrote:
> 
> 
>>Hi,
>>
>>i have some problems using the testtool...
>>
>>every execution of testtool produces this error:
>># ./testtool -ov
>>Initializing scanner
>>Registering transfer method 0: Linux scanner kernel module
>>VendorId 0x03F0, ProductId 0x0405
>>Matching USB device 0x03F0-0x0405 ... found Hewlett-Packard ScanJet 3400C
>>_ReportDevice '/dev/usb/scanner0'
>>Hp3300cXferOpen '/dev/usb/scanner0'
>>probing Linux scanner kernel module
>>Matching USB device 0x03F0-0x0405 ... found Hewlett-Packard ScanJet 3400C
>>Setting params for Hp3400c/Hp4300c
>>Probing scanner...
>>  No NIASH chipset found!
>>_ProbeRegisters failed!
>>Hp3300cOpen failed
>>
>>
>>i was wondering whats wrong...
>>
>>i hope someone can give me a hint or a reason why this happens,

Re: [Hp3300backend-devel] 3400C -- probing scanner failed, hiash chip not found

[Florian M. <fmi...@gm...>]

Hi again!

disconnect the usb-plug and then reconnect gives me the following output...
=============================================================
uhci.c: root-hub INT complete: port1: 48a port2: 480 data: 2
uhci.c: dc00: suspend_hc
hub.c: port 1, portstatus 100, change 3, 12 Mb/s
hub.c: port 1 connection change
hub.c: port 1, portstatus 100, change 3, 12 Mb/s
usb.c: USB disconnect on device 00:11.3-1 address 9
usb.c: kusbd: /sbin/hotplug remove 9
hub.c: port 2, portstatus 100, change 0, 12 Mb/s
uhci.c: root-hub INT complete: port1: 488 port2: 480 data: 2
hub.c: port 1, portstatus 100, change 2, 12 Mb/s
hub.c: port 1 enable change, status 100
hub.c: port 2, portstatus 100, change 0, 12 Mb/s
uhci.c: dc00: wakeup_hc
uhci.c: root-hub INT complete: port1: 49b port2: 480 data: 2
hub.c: port 1, portstatus 101, change 3, 12 Mb/s
hub.c: port 1 connection change
hub.c: port 1, portstatus 101, change 3, 12 Mb/s
hub.c: port 1, portstatus 101, change 2, 12 Mb/s
hub.c: port 1, portstatus 101, change 2, 12 Mb/s
uhci.c: root-hub INT complete: port1: 499 port2: 480 data: 2
hub.c: port 1, portstatus 101, change 2, 12 Mb/s
hub.c: port 1, portstatus 101, change 2, 12 Mb/s
hub.c: port 1, portstatus 103, change 0, 12 Mb/s
hub.c: new USB device 00:11.3-1, assigned address 10
usb.c: kmalloc IF c6da6580, numif 1
usb.c: new device strings: Mfr=10, Product=11, SerialNumber=12
usb.c: USB device number 10 default language ID 0x409
Manufacturer: Hewlett-Packard
Product: Hewlett-Packard ScanJet 3400C
SerialNumber: CN0AO1D0P8TG
usb.c: usbscanner driver claimed interface c6da6580
usb.c: kusbd: /sbin/hotplug add 10
hub.c: port 2, portstatus 100, change 0, 12 Mb/s
hub.c: port 1, portstatus 103, change 0, 12 Mb/s
hub.c: port 2, portstatus 100, change 0, 12 Mb/s
usb_control/bulk_msg: timeout
usbdevfs: USBDEVFS_CONTROL failed dev 10 rqt 128 rq 6 len 9 ret -110
... snip (last 2 message repeatet 50 or so times) ...
====================================================================
then i run testtool -v

in dmesg there are then dozens of:
======================================
scanner.c: ioctl_scanner(0): control_msg returned -110

usb_control/bulk_msg: timeout
scanner.c: ioctl_scanner(0): control_msg returned -110

usb_control/bulk_msg: timeout
======================================

lsusb:
=======================================
Unknown line at line 1809
Duplicate HUT Usage Spec at line 2650
Bus 003 Device 001: ID 0000:0000 Virtual Hub
Bus 002 Device 001: ID 0000:0000 Virtual Hub
Bus 002 Device 010: ID 03f0:0405 Hewlett-Packard ScanJet 3400cse
Bus 001 Device 001: ID 0000:0000 Virtual Hub
=======================================

so.. where could be the problem?

i think it is clear now that it is no testtool-problem... so im sorry to bother you... but ... is there someone who has an idea where i could look for solving this problem?

i will try (next week or so) to reach an windows-machine and test the usb-interface of the scanner with the official hp-scanner driver

but in the meantime... could it be some other error?
someone a guess perhaps? 


greetings, 
Florian Mickler

On Wed, 23 Apr 2003 14:30:54 +0200
Florian Mickler <mi...@d-...> wrote:

> Hi,
> 
> i have some problems using the testtool...
> 
> every execution of testtool produces this error:
> # ./testtool -ov
> Initializing scanner
> Registering transfer method 0: Linux scanner kernel module
> VendorId 0x03F0, ProductId 0x0405
> Matching USB device 0x03F0-0x0405 ... found Hewlett-Packard ScanJet 3400C
> _ReportDevice '/dev/usb/scanner0'
> Hp3300cXferOpen '/dev/usb/scanner0'
> probing Linux scanner kernel module
> Matching USB device 0x03F0-0x0405 ... found Hewlett-Packard ScanJet 3400C
> Setting params for Hp3400c/Hp4300c
> Probing scanner...
>   No NIASH chipset found!
> _ProbeRegisters failed!
> Hp3300cOpen failed
> 
> 
> i was wondering whats wrong...
> 
> i hope someone can give me a hint or a reason why this happens,
> 
> greets,
> Florian Mickler
> 
> 
> -- 
> http://www.d-labs.de -- Webspace & Domains
> 
> 
> -------------------------------------------------------
> This sf.net email is sponsored by:ThinkGeek
> Welcome to geek heaven.
> http://thinkgeek.com/sf
> _______________________________________________
> Hp3300backend-devel mailing list
> Hp3...@li...
> https://lists.sourceforge.net/lists/listinfo/hp3300backend-devel
> 


-- 
http://www.d-labs.de -- Webspace & Domains

[Hp3300backend-devel] 3400C -- probing scanner failed, hiash chip not found

[Florian M. <mi...@d-...>]

Hi,

i have some problems using the testtool...

every execution of testtool produces this error:
# ./testtool -ov
Initializing scanner
Registering transfer method 0: Linux scanner kernel module
VendorId 0x03F0, ProductId 0x0405
Matching USB device 0x03F0-0x0405 ... found Hewlett-Packard ScanJet 3400C
_ReportDevice '/dev/usb/scanner0'
Hp3300cXferOpen '/dev/usb/scanner0'
probing Linux scanner kernel module
Matching USB device 0x03F0-0x0405 ... found Hewlett-Packard ScanJet 3400C
Setting params for Hp3400c/Hp4300c
Probing scanner...
  No NIASH chipset found!
_ProbeRegisters failed!
Hp3300cOpen failed


i was wondering whats wrong...

i hope someone can give me a hint or a reason why this happens,

greets,
Florian Mickler


-- 
http://www.d-labs.de -- Webspace & Domains

[Hp3300backend-devel] scanjet 4300c

[Jacques C. <Jac...@wa...>]

Hello,
i just tried the last version of testtool with my
scanjet 4300c.
I used it with gimp and xsane.
Absolutely no problems. Now my scanner works like a
"normal" scanner.
Congratulations to Bertrik. Very good job.
Best regards.

------
Jac...@wa... f6cwo
Quelques HOWTO en français http://perso.wanadoo.fr/jacques.chion/

[Hp3300backend-devel] Scanning with my Hp 3400c

[Constant B. v. N. <con...@in...>]

Thanks to the backend and emails I have read in the archives I have now
finaly a working scanner.
I am using SuSe 8.0 with KDE and I found Gimp a nice program to get me a
scan.

If I make a preview scan I can nicely reduce the size of the image to
scan to what I want.
One thing which I have not been able to solve is the white band on top
of whatever image I scan.
Even if I exclude that part with the geometry sliders I will find it on
my saved image.

Is  there a way to get rid of this band or do I have to live with it for
the moment?

[Hp3300backend-devel] Scanning with my Hp 3400c

[Constant B. v. N. <con...@in...>]

Thanks to the backend and emails I have read in the archives I have now 
finaly a working scanner.
I am using SuSe 8.0 with KDE and I found Gimp a nice program to get me a 
scan.

If I make a preview scan I can nicely reduce the size of the image to 
scan to what I want.
One thing which I have not been able to solve is the white band on top 
of whatever image I scan.
Even if I exclude that part with the geometry sliders I will find it on 
my saved image.

Is  there a way to get rid of this band or do I have to live with it for 
the moment?

Re: [Hp3300backend-devel] testtool-20021120_2.tar.gz

[Ian T. <its...@ya...>]

Ok.. well then I'm not going to be of much use to you... sorry.
	Ian.

On November 29, 2002 04:02 pm, you wrote:
> Yes, of course but i can find only testtool-20021120_1.tar.gz and not
> testtool-20021120_2.tar.gz
>
> Il ven, 2002-11-29 alle 22:51, Ian Timshel ha scritto:
> > Did you check at the link below at sourceforge?
> >
> > On November 29, 2002 03:34 pm, you wrote:
> > > Is testtool-20021120_1.tar.gz the last version ?
> > > Where is testtool-20021120_2.tar.gz, if there is ?
> > >
> > >
> > >
> > > -------------------------------------------------------
> > > This SF.net email is sponsored by: Get the new Palm Tungsten T
> > > handheld. Power & Color in a compact size!
> > > http://ads.sourceforge.net/cgi-bin/redirect.pl?palm0002en
> > > _______________________________________________
> > > Hp3300backend-devel mailing list
> > > Hp3...@li...
> > > https://lists.sourceforge.net/lists/listinfo/hp3300backend-devel
> >
> > --
> > http://www.amical.net  - The Friendly IRC Network.
> >
> >
> > -------------------------------------------------------
> > This SF.net email is sponsored by: Get the new Palm Tungsten T
> > handheld. Power & Color in a compact size!
> > http://ads.sourceforge.net/cgi-bin/redirect.pl?palm0002en
> > _______________________________________________
> > Hp3300backend-devel mailing list
> > Hp3...@li...
> > https://lists.sourceforge.net/lists/listinfo/hp3300backend-devel

-- 
http://www.amical.net  - The Friendly IRC Network. 

Re: [Hp3300backend-devel] testtool-20021120_2.tar.gz

[Ian T. <its...@ya...>]

Did you check at the link below at sourceforge?

On November 29, 2002 03:34 pm, you wrote:
> Is testtool-20021120_1.tar.gz the last version ?
> Where is testtool-20021120_2.tar.gz, if there is ?
>
>
>
> -------------------------------------------------------
> This SF.net email is sponsored by: Get the new Palm Tungsten T
> handheld. Power & Color in a compact size!
> http://ads.sourceforge.net/cgi-bin/redirect.pl?palm0002en
> _______________________________________________
> Hp3300backend-devel mailing list
> Hp3...@li...
> https://lists.sourceforge.net/lists/listinfo/hp3300backend-devel

-- 
http://www.amical.net  - The Friendly IRC Network. 

[Hp3300backend-devel] testtool-20021120_2.tar.gz

[Michele V. <da...@da...>]

Is testtool-20021120_1.tar.gz the last version ?
Where is testtool-20021120_2.tar.gz, if there is ?

Re: [Hp3300backend-devel] sane-backends 1.0.9 sources

[Ian T. <its...@ya...>]

On November 29, 2002 01:12 pm, you wrote:
> sane-backends 1.0.9 sources

Is this what you are after?
ftp://ftp.mostang.com/pub/sane/sane-1.0.9/

Cheers!  Ian.
-- 
http://www.amical.net  - The Friendly IRC Network.