[sane-devel] sane 1.0.14 and MD9890: invalid driver name
Eddy De Greef
Mon, 06 Sep 2004 08:22:31 +0000
> I am a newbie to SANE and have a strange problem:
> I installed SANE 1.0.14 from source and it told me after configure that
> mustek_pp will be supported. So I edited
> /usr/local/etc/sane.d/mustek_pp.conf and added:
> scanner "mustek" * cis1200
> But all I get is:
> fafnir:/usr/local/etc/sane.d # SANE_DEBUG_MUSTEK_PP=3D128 scanimage -L
> [sanei_debug] Setting debug level of mustek_pp to 128.
> [mustek_pp] sane-mustek_pp, version 0.13-beta. build for SANE 1.0.14
> [mustek_pp] backend by Jochen Eisinger
> [mustek_pp] sanei_init: auto probing port
> [mustek_pp] sane_init: invalid driver name ``cis1200''
> dll.conf has mustek_pp activated.
My guess is that you did not install libieee1284 before compiling SANE.
You _can_ compile the driver without libieee1284, but then you need
to pass the --enable-parport-directio option to configure (and then
you always need to scan as root, possibly via saned).=20
I'd strongly suggest that you install libieee1284 (and recompile SANE),=20
because it is also the only way to get auto probing to work.
To make sure that this is my guess is right, you can run scanimage
with an extra debug variable:
SANE_DEBUG_SANEI_PA4S2=3D128 SANE_DEBUG_MUSTEK_PP=3D128 scanimage -L
It will probably tell you that A4S2 support is not compiled.
PS: I think we should do something about this. Users should get=20
a warning that the backend isn't functional already during=20