Hello, I have some follow up questions included below. Johannes Meixner wrote:
On Oct 20 00:39 Terje J. Hanssen wrote (shortened):
Looks like there is a problem to activate the service "sane-dev" during startup. The scanner is on during startup, but I'm not sure it is detected by the system?
When it is activated for the usual runlevels 3 and 5, it is started during booting.
Yes, the sane-dev service is activated for run lever 3 and 5
But it seems in your particular case it doesn't detect the scanner during boot. For example your scanner may take too long to wake up. There is a timeout in sane-dev to limit how long it waits for scanimage to detect a scanner. If the sane-dev output is "Aborted", the timeout had happened.
Is it possible to check if the sane-dev output has been aborted (how)? Possibly extend the timeout?
Note that the kernel module "sg" must have been loaded to get the device node /dev/sg0 created and to access any SCSI scanner, see http://portal.suse.com/sdb/en/2004/04/thallma_scsiscanner_91.htm
I wasn't able to find that document on this link. Rgds, Terje J. Hanssen