[sane-devel] HP ScanJet 4100C
Sun, 5 Jan 2003 02:43:56 +0100
On Sat, Jan 04, 2003 at 08:56:30PM +0100, Michel Janssens wrote:
> * - sane-backends and kernel version?
> Sane BackEnds: 1.0.9
> Kernel version : 2.4.18
> * - output of scanimage -L
> [root@gateway root]# scanimage -L
> device `test:0' is a Noname frontend-tester virtual device
> device `test:1' is a Noname frontend-tester virtual device
> device `hp:/dev/usb/scanner0' is a Hewlett-Packard MODELx flatbed scanner
Looks ok. I don't know if the "MODELx" is normal, however.
> * what tests did you do? What files did you change?
> I just succeed in the simple test : scanimage >image.pnm
> SANE produced something ... but I'm still having a communication problem I
Any errors? Does the image look correct (probably gray, low resolution)?
> [root@gateway sane.d]# more dll.conf:
> [root@gateway sane.d]# more hp.conf
> scsi HP
> # uncomment this if you're using a usb scanner
> option connect-device
> usb 0x03f0 0x0101
I don't know the details, but basically it doesn't looks wrong.
> [root@gateway xinetd.d]# more sane
> # default: off
> # description: The sane server accepts requests
> # for network access to a local scanner via the
> # network.
> service sane
> port = 6566
> socket_type = stream
> wait = no
> user = saned
> group = saned
> server = /usr/local/sbin/saned
> I also created user saned and group saned
When you do "telnet localhost 6566" can you type something or do you
get "connection refused" immediately? Any output in syslog after this?
If you get "connection refused", saned can't be started for some
reason. Is the path to saned correct?
> [root@gateway sane.d]# more saned.conf
Please also try that (mentioned in my last email):
> Check on the server if saned runs correctly, e.g. by adding
> "localhost" t o net.conf and running scanimage -L. It should show the
> server not only directly (hp:/dev/usb/scanner) but also "over the net"
> (net:localhost:hp:/dev/usb/scanner0). Please show us this output.
> When this works, try again from the Windows server. If XSane32 still
> fails, I guess it's a problem on the Windows side.