[sane-devel] "a second try" the thread I had had started a while ago

2005-08-13 Thread Dieter Jurzitza
Dear listmembers, to come back to the issue I found (and thanks to Henning somewhat solved). My situation: a scanner and a zipdrive (SCSI) sitting on the same SCSI bus on ID5 (zipdrive) and ID6 (scanner / MUSTEK 12000SP). Problem description: if the light of the scanner is off (after several min

[sane-devel] a second try

2005-08-03 Thread Dieter Jurzitza
Dear Henning, dear listmembers, I think you caught it. It is actually not the scanner causing this abort, it is the zip-drive. This actually makes me wonder; in fact I do nothing with it (it is not mounted). Turning it off and running rescan-scsi-bus.sh solves the problem, no more abort messages

[sane-devel] a second try

2005-08-02 Thread Henning Meier-Geinitz
Hi, On Mon, Aug 01, 2005 at 08:48:31PM +0200, Dieter Jurzitza wrote: > Dear Henning, > with pleasure :-) > I wrote a short batch and echoed start / stop sequences into > /var/log/messages > so the excerpt of /var/log/messages I have attached relates exactly to the > script I used to start scani

[sane-devel] a second try

2005-07-31 Thread Dieter Jurzitza
Dear Mr. Meier-Geinitz, is there any means to send a command to the scanner in order to make him wake up - but do nothing else? I could probably do that prior to actually scanning - maybe that would help with the problem I have been running into. Many thanks for any inputs, take care Dieter Ju

[sane-devel] a second try

2005-07-31 Thread Henning Meier-Geinitz
Hi, On Tue, Jul 26, 2005 at 05:35:06PM +0200, Dieter Jurzitza wrote: > Mr. Meier - Geinitz, yes, you are right, the code did not change. But this > could be the problem. I've tried to reproduce your problem with the Mustek ScanExpress 6000 SP and all worked well. Unfortunately that scanner doesn

[sane-devel] a second try

2005-07-26 Thread Martin Collins
On Mon, 25 Jul 2005 19:21:18 +0200 Henning Meier-Geinitz wrote: > The current setting is 120 seconds. Shouldn't this be enough even > for warming up? It's a while since I used my Mustek but ISTR that sometimes that would be long enough but sometimes it took a bit longer. Unfortunately I can't cu

[sane-devel] a second try

2005-07-25 Thread Henning Meier-Geinitz
Hi, On Mon, Jul 25, 2005 at 07:57:52AM +0100, Martin Collins wrote: > I used to get this (or something similar) with my Mustek. The lamp has > to warm up and this can take longer than the SCSI timeout. This > timeout was reduced at some time in the past, older versions of SANE > worked fine. The s

[sane-devel] a second try

2005-07-24 Thread Dieter Jurzitza
Dear Listmembers, der Mr. Meier-Geinitz "fall asleep" means that the light is turned off after some time of pause. In this case I get the issues with the scanner when trying to scan something. If the light is "on" (whatever that means for the status of the scanner) I can scan whatever I want, no

[sane-devel] a second try

2005-07-24 Thread Henning Meier-Geinitz
Hi, On Sun, Jul 24, 2005 at 09:50:08PM +0200, Dieter Jurzitza wrote: > Dear listmembers, > a second try. I have an old Mustek SCSI-Scanner that used to work smoothly > with my old SuSE 8.1 and kernel 2.4. As far as I remember, (almost) nothing has been changed in the mustek SCSI backend in recen

[sane-devel] a second try

2005-07-24 Thread Dieter Jurzitza
Dear listmembers, a second try. I have an old Mustek SCSI-Scanner that used to work smoothly with my old SuSE 8.1 and kernel 2.4. Now I have SuSE 9.3 and kernel 2.6.11, and I have some trouble. The scanner is connected to a separate AHA 2940 card (I tested different ones). Termination is set to