Hi,
your configuration is ok. Otherwise scanimage would not find the
scanner. But you can try to access the scanner by libusb. Insert below
the line scsi HP
# HP ScanJet 4100C
usb 0x03f0 0x0101
--Peter
Bill Moseley schrieb:
Hi,
I'm having limited luck scanning on a HP ScanJet 4100C USB.
On Thu, 2 Jan 2003, Peter Kirchgessner wrote:
Hi,
your configuration is ok. Otherwise scanimage would not find the
scanner. But you can try to access the scanner by libusb. Insert below
the line scsi HP
# HP ScanJet 4100C
usb 0x03f0 0x0101
Ok I tried that:
$ cat
Hi,
seems really to be a problem with the USB-connection. At that point I
can't help further.
Sincerely
Peter
Bill Moseley schrieb:
On Thu, 2 Jan 2003, Peter Kirchgessner wrote:
Hi,
your configuration is ok. Otherwise scanimage would not find the
scanner. But you can try to access the
Hi,
On Thu, Jan 02, 2003 at 10:55:56AM -0800, Bill Moseley wrote:
Still same problem, and I still see the usb_control/bulk_msg: timeout
messages and xsane always fails with an I/O error.
The default timeout is 10 seconds, and it's expected to be enough for
writes. You can try to increase this
On Thu, 2 Jan 2003, Henning Meier-Geinitz wrote:
The default timeout is 10 seconds, and it's expected to be enough for
writes. You can try to increase this limit when loading the driver:
rmmod scanner; modprobe scanner read_timeout=60
Ok. Did that. BTW -- on boot the messages delay for
Hi,
On Thu, Jan 02, 2003 at 12:27:49PM -0800, Bill Moseley wrote:
Ok. Did that. BTW -- on boot the messages delay for about 4 seconds
each.
Could be correct, I remeber that the timeout for control messages i 4
or 5 seconds.
If this doesn't help, or you get more of these messages or if you
On Thu, 2 Jan 2003, Henning Meier-Geinitz wrote:
Do you have any other USb devices? Or maybe you have different USb
root hubs?
Nope, the scanner is the only device. I've tried both ports on the back
of this machine.
I would first check that it's really the scanner, e.g. by
using a
Hi,
On Thu, Jan 02, 2003 at 01:53:06PM -0800, Bill Moseley wrote:
It would be too bad if it's a motherboard. Seems unlikely, though.
If I were able to test the the hardware and find out it's ok, then where
should I focus my debugging?
I guess then it's somewhere in the kernel USb core.
--45Z9DzgjV8m4Oswq
Content-Type: text/plain; charset=us-ascii
Content-Disposition: inline
Content-Transfer-Encoding: quoted-printable
On Thu, Jan 02, 2003 at 01:53:06PM -0800, Bill Moseley wrote:
[ ... ]
Ok, I can try another computer, I guess. I tried Knoppix CD just now and
I got the same
--CE+1k2dSO48ffgeK
Content-Type: text/plain; charset=us-ascii
Content-Disposition: inline
Content-Transfer-Encoding: quoted-printable
On Fri, Jan 03, 2003 at 12:25:39AM +, Neil Skilling wrote:
[ ... ]
=20
Relevant from /etc/modules.conf:
=20
alias char-major-180 usb-serial
10 matches
Mail list logo
