> I made this change and ran
> $ make modules
> # make modules_install
> and rebooted. Didn't seem to make any difference for my situation. The
> timeout messages still happen -- and about the same rate.
Sorry not to reply in the same thread: I had deleted everything before
realizing
On Fri, 3 Jan 2003, A E Lawrence wrote:
> I saw the thread in the archives with this subject. And so I attach a note
> on how I have fixed the problem on my system.
>#ifdef CONFIG_USB_LONG_TIMEOUT
>#define GET_TIMEOUT 20 <== This was 4
I made this change and ran
$ make modules
#
This is a multi-part message in MIME format.
--090209090207000603090402
Content-Type: text/plain; charset=us-ascii; format=flowed
Content-Transfer-Encoding: 7bit
I saw the thread in the archives with this subject. And so I attach a note
on how I have fixed the problem on my system.
ae
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
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
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 th
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 a
--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 I
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 diffe
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
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 /etc/sane
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
Hi,
I'm having limited luck scanning on a HP ScanJet 4100C USB. I'm trying to
use xsane.
Running "xscanimage hp" seems to work most of the time, but I still get
the message:
Jan 1 16:14:06 bumby kernel: usb_control/bulk_msg: timeout
Jan 1 16:14:26 bumby kernel: usb_control/bulk_ms
13 matches
Mail list logo
