Till Kamppeter wrote:
In 8.2 all drivers were entered into /etc/sane.d/dll.conf, so all drivers which had auto-detection for the scanner model worked without configuration, and so these scanners worked at least as long as one did not touch scannerdrake.i have this scanner trust 19200 usb working now
In 9.0 I had the problem that xsane needed more than a minute to start up, and I found out that this came from the case that all scanner drivers were started to auto-detect appropriate scanners (if they supported auto-detection). Seems that this time was substantially shorter before 9.0 (SANE versions older than 1.0.8). So I removed all driver entries from dll.conf assuming that scannerdrake puts the right ones in. I didn't know that scannerdrake was rather broken and most scanners only worked because their drivers did auto-detection and so the users didn't touch scannerdrake.
Till
Robert Fox wrote:
It worked!! So adding the mustek_usb did it - the question is now, why did it work automatically previously? Scannerdrake was able to find it before . . .
it works on 9.0 but stop work on cooker from the first cooker realse of sane ...
i dont know how i can set it scanner drake daesnt work
but i was able to start from root and now with a suid also with my user too
the problem is that now i have two scanner one from scannerdrke that daesnt work
and a second one with the right path to the device that works but now appear dynamically to the desktop
regard francesco
