On 2016-04-17 13:03, EdaSky wrote:
I have scanner HP scanjet4370
tested on 5.8 RELEASE and 5.9 GENERIC.MP#1690 i386 with the same 
result
scanner is detected

$ dmesg
OpenBSD 5.9-current (GENERIC.MP) #1690: Thu Mar 31 09:41:46 MDT 2016
   dera...@i386.openbsd.org:/usr/src/sys/arch/i386/compile/GENERIC.MP
cpu0: Genuine Intel(R) CPU U2500 @ 1.20GHz ("GenuineIntel" 686-class) 1.20
GHz
.......
ugen1 at uhub0 port 5 "hewlett packard hp scanjet" rev 2.00/1.00 addr 2
$ scanimage -L
device `hp3900:libusb:000:002' is a Hewlett-Packard Scanjet 4370 flatbed
scanner

But the scan does not work.
When I start previewing or scanning. Head will start move but stops
immediately.

$ scanimage -T
scanimage: scanning image of size 433x590 pixels at 24 bits/pixel
scanimage: acquiring RGB frame, 8 bits/sample
scanimage: reading one scanline, 1299 bytes... FAIL Error: End of file
reached

$ hp-scan
HP Linux Imaging and Printing System (ver. 3.16.3)
Scan Utility ver. 2.2
..
warning: No destinations specified. Adding 'file' destination by default.
Using device hp3900:libusb:000:002
Opening connection to device...

Resolution: 300dpi
Mode: gray
Compression: JPEG
Scan area (mm):
 Top left (x,y): (0.000000mm, 0.000000mm)
 Bottom right (x,y): (220.000000mm, 300.000000mm)
 Width: 220.000000mm
 Height: 300.000000mm
Destination(s): file
Output file:
warning: File destination enabled with no output file specified.
Setting output format to PNG for greyscale mode.
warning: Defaulting to '/home/edasky/hpscan001.png'.
Warming up...
Scanning...
Reading data: [\
                          ] 0%
error: No data read.
Closing device.

xane the same result.

Please what should I even try?


full debug
$ export SANE_DEBUG_HP3900=4

http://185.47.222.11/scanner-debug.txt


$ pkg_info on snapshot
sane-backends-1.0.25p2
xsane-0.999p2

$ pkg_info on 5.8 release
sane-backends-1.0.24p6
xsane-0.999p2


On Debian linux with sane-backends-1.0.24 and xsane-0.998 works fine.
Don't have OpenBSD here but have you

a) Read /usr/local/share/doc/pkg_readme/cups and any hplip documents?
b) disabled ulpt in the kernel?

Good Luck
Moss

Reply via email to