plustek@linuxhacker.org
plustek@linuxhacker.org
Hmm,
it seems, that you have not loaded the parport modules.
try as root user:
modprobe parport parport_pc
Then check the access rights of
/dev/parport0
Should be something like:
crw-rw-rw- 1 root root 99, 0 2003-03-14 14:08 /dev/parport0
If not, change 'em:
chmod 666 /dev/parport*
The options, that I have are (kernel 2.4.23):
#
# Parallel port support
#
CONFIG_PARPORT=m
CONFIG_PARPORT_PC=m
CONFIG_PARPORT_PC_CML1=m
CONFIG_PARPORT_SERIAL=m
CONFIG_PARPORT_PC_FIFO=y
CONFIG_PARPORT_PC_SUPERIO=y
CONFIG_PARPORT_PC_PCMCIA=m
# CONFIG_PARPORT_AMIGA is not set
# CONFIG_PARPORT_MFC3 is not set
# CONFIG_PARPORT_ATARI is not set
# CONFIG_PARPORT_GSC is not set
# CONFIG_PARPORT_SUNBPP is not set
CONFIG_PARPORT_OTHER=y
CONFIG_PARPORT_1284=y
Then try and use the following plustek_pp.conf:
[direct]
decvice parport0
option mov 7
disable or remove all other entries...
In the end this is all!
Please do one tests again:
export SANE_DEBUG_SANEI_PP=4 ; export SANE_DEBUG_PLUSTEK_PP=20 ; scanimage -L
and please send me the logs...
Ciao,
Gerhard
On Thursday 15 January 2004 05:37, Denesh wrote:
> > can you send me the output?
> > i.e.: export SANE_DEBUG_PLUSTEK_PP=20 ; scanimage -L
>
> I compiled sane in my LFS system. And here is the
> output, when I tried 'scanimage -l'. The scanner wasnt
> detected
>
> for sane-backends-1.0.13 the output was
>
> [sanei_debug] Setting debug level of plustek_pp to 20.
> [plustek_pp] PlustekPP backend V0.01-5, part of
> sane-backends 1.0.13
> [plustek_pp] ># Plustek-PP SANE Backend configuration
> file<
> [plustek_pp] ># For use with Plustek parallel-port
> scanners<
> [plustek_pp] >#<
> [plustek_pp] ><
> [plustek_pp] >#<
> [plustek_pp] ># user either [direct] or [kernel] to
> access the scanner<
> [plustek_pp] ># when using [kernel], device specifies
> the device-node, which is created<
> [plustek_pp] ># by the kernel-module loader (applies
> only to Linux)<
> [plustek_pp] ># when using [direct], device is used to
> set the parallel-port base address<
> [plustek_pp] ># or a device-name suitable for
> libieee1284, i.e. parport0<
> [plustek_pp] >#<
> [plustek_pp] >[direct]<
> [plustek_pp] >device 0x378<
> [plustek_pp] Decoding device name >0x378<
> [plustek_pp] ><
> [plustek_pp] >#<
> [plustek_pp] ># leave the default values as specified
> in /etc/modules.conf<
> [plustek_pp] >#<
> [plustek_pp] >option warmup 15<
> [plustek_pp] Decoding option >warmup<
> [plustek_pp] >option lOffOnEnd 1<
> [plustek_pp] Decoding option >lOffOnEnd<
> [plustek_pp] >option lampOff 180<
> [plustek_pp] Decoding option >lampOff<
> [plustek_pp] ><
> [plustek_pp] ># model override switch, mostly for
> cosmetic changes, if the autodetection<
> [plustek_pp] ># does not work or could not work
> correctly<
> [plustek_pp] >option mov 2<
> [plustek_pp] Decoding option >mov<
> [plustek_pp] ><
> [plustek_pp] >#<
> [plustek_pp] ># example for accessing the scanner via
> libieee1284<
> [plustek_pp] >#<
> [plustek_pp] >[direct]<
> [plustek_pp] attach (0x378, 0xbfffcbd0, (nil))
> [plustek_pp] Device configuration:
> [plustek_pp] device name : >0x378<
> [plustek_pp] direct I/O : yes
> [plustek_pp] warmup : 15s
> [plustek_pp] lampOff : 180
> [plustek_pp] lampOffOnEnd : yes
> [plustek_pp] model override: 2
> [plustek_pp] ---------------------
> [plustek_pp] drvopen()
> [plustek_pp] open: PtDrvInit failed: 4
> [plustek_pp] open failed: -1
> [plustek_pp] >device parport0<
> [plustek_pp] Decoding device name >parport0<
> [plustek_pp] ><
> [plustek_pp] >option warmup 15<
> [plustek_pp] Decoding option >warmup<
> [plustek_pp] >option lOffOnEnd 1<
> [plustek_pp] Decoding option >lOffOnEnd<
> [plustek_pp] >option lampOff 180<
> [plustek_pp] Decoding option >lampOff<
> [plustek_pp] ><
> [plustek_pp] >option mov 2<
> [plustek_pp] Decoding option >mov<
> [plustek_pp] >#<
> [plustek_pp] ># example for accessing the scanner via
> the ker
plustek@linuxhacker.org