Hm, you are right, I don't have a real good Idea. But a few thoughts:
- You didn't make accidentally a firmware "upgrade" on the other
machine (the revision was also 2.21 before)? (don't know if this
could happen, probably not)
- Try scanning with Windows and then boot Linux without switching off
the scanner and the computer in between
- Try scanning with and without backend calibration
-Try my newest backend (microtek2_200104018) at
http://home.t-online.de/home/karsten.festag
-There was a patch for scanners that hang at the same command as yours
now, I have to look at home after it (I'm at work now).
all in all it's a little bit strange. The programs on your machine
(kernel, modules, SANE) were the same before and after you moved the scanner
around?
Karsten
> ...
> Yes, it is applied.
> Seems that didn't help for me.
>
> I have a few options I could try.
> 1. Use an old kernel, and an older version of Sane, see how that
works
> out.
> 2. I could Freebsd here, and see if I can get it going then.
> Maybe i can then get wiser about if it is sane or the kernel.
>
> The stupid thing is, when moving it to another machine it stopped
> working, and moving it back didn't help. So there wasn't a real
excuse
> for the scanner to stop working.
>
> Reading your answer, I assume you don't have an idea how to deal with
it
> :-)
> Then I guess I'm gonna have to try some of the options to see if
that
> gives anything.
>
> Greetings,
> Marcel Pol
>
-- Source code, list archive, and docs: http://www.mostang.com/sane/ To unsubscribe: echo unsubscribe sane-devel | mail majordomo@mostang.com
This archive was generated by hypermail 2b29 : Wed Apr 25 2001 - 23:34:58 PDT