plustek: Thread: unresolved symbols

On Sonntag, 23. Juni 2002 20:50, Karsten Giesow wrote:
> Hi Gerhard,
>
> sorry, but it don't work. :-(

BAD! But it should...

[SNIP]

> nathan:/home/karsten # insmod pt_drv
> Using /lib/modules/2.4.18-4GB/misc/pt_drv.o
> nathan:/home/karsten # lsmod
> Module                  Size  Used by    Tainted: P
> pt_drv                135392   0  (unused)
> snd-pcm-oss            45152   1  (autoclean)
[SNAP]

The driver is loaded! But cannot be accessed by scanimage:

[SNIP]
> [plustek] drvopen()
> [plustek] open: can't open /dev/pt_drv as a device
> [plustek] open failed: -1
[SNAP]

Check your device nodes as I told you in my previous
mails:

ls -l /dev/pt_drv*
should show up something like this:
crw-rw-r--   1 root     root      40,   0 Jul 19  2001 /dev/pt_drv
crw-rw-r--   1 root     root      40,   0 Dec  6  2000 /dev/pt_drv0
crw-rw-r--   1 root     root      40,   1 Dec  6  2000 /dev/pt_drv1
crw-rw-r--   1 root     root      40,   2 Dec  6  2000 /dev/pt_drv2
crw-rw-r--   1 root     root      40,   3 Dec  6  2000 /dev/pt_drv3

If they don't exist, use the make load command, to create the nodes
automatically or do it on your own:
mknod /dev/pt_drv c 40 0 -m 664


[SNIP]
> Still one question
> I've made a copy of the lines during the installation
> Waht does the following line mean:
> ---------------
> nathan:/home/karsten/Plustek-Treiber0.41/plustek_driver # make install
> mkdir -p /lib/modules/2.4.18-4GB/misc
> install -c -m "644" pt_drv.o /lib/modules/2.4.18-4GB/misc
> /sbin/depmod -a
> depmod: *** Unresolved symbols in /lib/modules/misc/pt_drv.o
> nathan:/home/karsten/Plustek-Treiber0.41/plustek_driver #
> ---------------
[SNAP]

I've no idea, where the problem is, you might try depmod -aev to
find out which unresolved symbols there are. But I think this can
be ignored, as the driver will be loaded...

Gerhard

Hi Gerhard,
thanks for your help and patience.
It's working now. :-)

Am Montag, 24. Juni 2002 09:08 schrieb Jaeger, Gerhard:
> On Sonntag, 23. Juni 2002 20:50, Karsten Giesow wrote:
> > Hi Gerhard,
> >
> > sorry, but it don't work. :-(
>
> BAD! But it should...
>
> [SNIP]
>
> > nathan:/home/karsten # insmod pt_drv
> > Using /lib/modules/2.4.18-4GB/misc/pt_drv.o
> > nathan:/home/karsten # lsmod
> > Module                  Size  Used by    Tainted: P
> > pt_drv                135392   0  (unused)
> > snd-pcm-oss            45152   1  (autoclean)
>
> [SNAP]
>
> The driver is loaded! But cannot be accessed by scanimage:
>
> [SNIP]
>
> > [plustek] drvopen()
> > [plustek] open: can't open /dev/pt_drv as a device
> > [plustek] open failed: -1
>
> [SNAP]
>
> Check your device nodes as I told you in my previous
> mails:
>
> ls -l /dev/pt_drv*
----------------------
karsten@nathan:~>  ls -l /dev/pt_drv*
crw-rw-r--    1 root     root      40,   0 Jun 24 20:53 /dev/pt_drv
karsten@nathan:~>

----------------------
> should show up something like this:
> crw-rw-r--   1 root     root      40,   0 Jul 19  2001 /dev/pt_drv
> crw-rw-r--   1 root     root      40,   0 Dec  6  2000 /dev/pt_drv0
> crw-rw-r--   1 root     root      40,   1 Dec  6  2000 /dev/pt_drv1
> crw-rw-r--   1 root     root      40,   2 Dec  6  2000 /dev/pt_drv2
> crw-rw-r--   1 root     root      40,   3 Dec  6  2000 /dev/pt_drv3
>
> If they don't exist, use the make load command, to create the nodes
> automatically or do it on your own:
> mknod /dev/pt_drv c 40 0 -m 664

There is still one question.
During the installation I made at least "make load", normally the driver and 
device must automatically load, but it was not on this way.
Now I made it with the command
"mknod /dev/pt_drv c 40 0 -m 664"
and now it's looking as if the driver, modul and device is load if I start 
"XSane"
Can you explain me why it is now going on, also if I shut down the pc and 
later after the boot I start XSane it is working, without a new command?
Perhaps you will say that's a silly question, but I can't find any explanation 
for this.

>
>
> [SNIP]
>
> > Still one question
> > I've made a copy of the lines during the installation
> > Waht does the following line mean:
> > ---------------
> > nathan:/home/karsten/Plustek-Treiber0.41/plustek_driver # make install
> > mkdir -p /lib/modules/2.4.18-4GB/misc
> > install -c -m "644" pt_drv.o /lib/modules/2.4.18-4GB/misc
> > /sbin/depmod -a
> > depmod: *** Unresolved symbols in /lib/modules/misc/pt_drv.o
> > nathan:/home/karsten/Plustek-Treiber0.41/plustek_driver #
> > ---------------
>
> [SNAP]
>
> I've no idea, where the problem is, you might try depmod -aev to
> find out which unresolved symbols there are. But I think this can
> be ignored, as the driver will be loaded...

I have checked it, look the output
--------------
depmod: *** Unresolved symbols in /lib/modules/misc/pt_drv.o
depmod:         get_fast_time
/lib/modules/misc/pt_drv.o
nathan:/home/karsten #
--------------
What does it mean?

Again.
Thanks for your help!

mfg

Karsten

-- 
Karsten Giesow
Adolf-Donders-Allee 32
46419 Isselburg-Anholt
Tel.: 0172/1655696
Fax: 02874/902680

Hello,

I think I have a well known problem: during the installation I got the
error message:

depmod: *** Unresolved symbols in /lib/modules/2.4.2-2/misc/pt_drv.o

When I check the unresolved symbols I see:

depmod: 	add_timer_Rsmp_a19eacf8
depmod: 	del_timer_Rsmp_fc62f16d
depmod: 	create_proc_entry_Rsmp_b5e3694a
depmod: 	__generic_copy_to_user_Rsmp_d523fdd3
depmod: 	parport_claim_Rsmp_dc843753
depmod: 	parport_register_device_Rsmp_75a20b73
depmod: 	unregister_chrdev_Rsmp_c192d491
depmod: 	proc_root_Rsmp_1fb67437
depmod: 	__vmalloc_Rsmp_79995c5b
depmod: 	parport_unregister_device_Rsmp_0cffd5b6
depmod: 	sprintf_Rsmp_1d26aa98
depmod: 	parport_release_Rsmp_e2338255
depmod: 	printk_Rsmp_1b7d4074
depmod: 	kfree_Rsmp_037a0cba
depmod: 	vfree_Rsmp_2fd1d81c
depmod: 	remove_proc_entry_Rsmp_dd4655a7
depmod: 	kmalloc_Rsmp_93d4cfe6
depmod: 	parport_enumerate_Rsmp_b88956ae
depmod: 	schedule_Rsmp_4292364c
depmod: 	__const_udelay_Rsmp_eae3dfd6
depmod: 	register_chrdev_Rsmp_fd911478
depmod: 	__udelay_Rsmp_9e7d6bd0
depmod: 	proc_mkdir_Rsmp_5d29064b
depmod: 	__generic_copy_from_user_Rsmp_116166aa
depmod: 	jiffies_Rsmp_0da02d67
depmod: 	do_gettimeofday_Rsmp_72270e35
message

Formerly I've found a guy with the same problem in the mailing list but
the answer to him was 

       "This looks to me, as your kernel-configuration
       does not match the really installed and unsed kernel!

       You might recompile and install the kernel, and then recompile the
       driver".

OK. But I use the originally installed kernel and I didn't change 
configuration. Then could you any idea what's wrong?
Any help you can offer would be appreciated!

Zoltan Kovacs

Hi,

the answer is the same, even if you have installed the original
kernel (what ever this means), it is possible, that the configuration
is wrong. i.e. SuSE provides three files which can be found in
/boot:
vmlinuz_24.autoconf.h
vmlinuz_24.config
vmlinuz_24.version.h
They have used these config file to build the kernel and these
files are needed (and of course the other headers) to build a driver,
that fits the kernel.

Gerhard

-------------------------
gerhard AT gjaeger DOT de

On Tuesday, 9. July 2002 18:19, Zoltan Kovacs wrote:
> Hello,
>
> I think I have a well known problem: during the installation I got the
> error message:
>
> depmod: *** Unresolved symbols in /lib/modules/2.4.2-2/misc/pt_drv.o
>
> When I check the unresolved symbols I see:
>
> depmod: 	add_timer_Rsmp_a19eacf8
> depmod: 	del_timer_Rsmp_fc62f16d
> depmod: 	create_proc_entry_Rsmp_b5e3694a
> depmod: 	__generic_copy_to_user_Rsmp_d523fdd3
> depmod: 	parport_claim_Rsmp_dc843753
> depmod: 	parport_register_device_Rsmp_75a20b73
> depmod: 	unregister_chrdev_Rsmp_c192d491
> depmod: 	proc_root_Rsmp_1fb67437
> depmod: 	__vmalloc_Rsmp_79995c5b
> depmod: 	parport_unregister_device_Rsmp_0cffd5b6
> depmod: 	sprintf_Rsmp_1d26aa98
> depmod: 	parport_release_Rsmp_e2338255
> depmod: 	printk_Rsmp_1b7d4074
> depmod: 	kfree_Rsmp_037a0cba
> depmod: 	vfree_Rsmp_2fd1d81c
> depmod: 	remove_proc_entry_Rsmp_dd4655a7
> depmod: 	kmalloc_Rsmp_93d4cfe6
> depmod: 	parport_enumerate_Rsmp_b88956ae
> depmod: 	schedule_Rsmp_4292364c
> depmod: 	__const_udelay_Rsmp_eae3dfd6
> depmod: 	register_chrdev_Rsmp_fd911478
> depmod: 	__udelay_Rsmp_9e7d6bd0
> depmod: 	proc_mkdir_Rsmp_5d29064b
> depmod: 	__generic_copy_from_user_Rsmp_116166aa
> depmod: 	jiffies_Rsmp_0da02d67
> depmod: 	do_gettimeofday_Rsmp_72270e35
> message
>
> Formerly I've found a guy with the same problem in the mailing list but
> the answer to him was
>
>        "This looks to me, as your kernel-configuration
>        does not match the really installed and unsed kernel!
>
>        You might recompile and install the kernel, and then recompile the
>        driver".
>
> OK. But I use the originally installed kernel and I didn't change
> configuration. Then could you any idea what's wrong?
> Any help you can offer would be appreciated!
>
> Zoltan Kovacs
>

On Wed, 10 Jul 2002, Jaeger, Gerhard wrote:

> Hi,
> 
> the answer is the same, even if you have installed the original
> kernel (what ever this means), it is possible, that the configuration
> is wrong. i.e. SuSE provides three files which can be found in
> /boot:
> vmlinuz_24.autoconf.h
> vmlinuz_24.config
> vmlinuz_24.version.h
> They have used these config file to build the kernel and these
> files are needed (and of course the other headers) to build a driver,
> that fits the kernel.
> 
> Gerhard
> 
> -------------------------
> gerhard AT gjaeger DOT de
> 
> On Tuesday, 9. July 2002 18:19, Zoltan Kovacs wrote:
> > Hello,
> >
> > I think I have a well known problem: during the installation I got the
> > error message:
> >
> > depmod: *** Unresolved symbols in /lib/modules/2.4.2-2/misc/pt_drv.o
> >
> > When I check the unresolved symbols I see:
> >
> > depmod: 	add_timer_Rsmp_a19eacf8
> > depmod: 	del_timer_Rsmp_fc62f16d
> > depmod: 	create_proc_entry_Rsmp_b5e3694a
> > depmod: 	__generic_copy_to_user_Rsmp_d523fdd3
> > depmod: 	parport_claim_Rsmp_dc843753
> > depmod: 	parport_register_device_Rsmp_75a20b73
> > depmod: 	unregister_chrdev_Rsmp_c192d491
> > depmod: 	proc_root_Rsmp_1fb67437
> > depmod: 	__vmalloc_Rsmp_79995c5b
> > depmod: 	parport_unregister_device_Rsmp_0cffd5b6
> > depmod: 	sprintf_Rsmp_1d26aa98
> > depmod: 	parport_release_Rsmp_e2338255
> > depmod: 	printk_Rsmp_1b7d4074
> > depmod: 	kfree_Rsmp_037a0cba
> > depmod: 	vfree_Rsmp_2fd1d81c
> > depmod: 	remove_proc_entry_Rsmp_dd4655a7
> > depmod: 	kmalloc_Rsmp_93d4cfe6
> > depmod: 	parport_enumerate_Rsmp_b88956ae
> > depmod: 	schedule_Rsmp_4292364c
> > depmod: 	__const_udelay_Rsmp_eae3dfd6
> > depmod: 	register_chrdev_Rsmp_fd911478
> > depmod: 	__udelay_Rsmp_9e7d6bd0
> > depmod: 	proc_mkdir_Rsmp_5d29064b
> > depmod: 	__generic_copy_from_user_Rsmp_116166aa
> > depmod: 	jiffies_Rsmp_0da02d67
> > depmod: 	do_gettimeofday_Rsmp_72270e35
> > message
> >
> > Formerly I've found a guy with the same problem in the mailing list but
> > the answer to him was
> >
> >        "This looks to me, as your kernel-configuration
> >        does not match the really installed and unsed kernel!
> >
> >        You might recompile and install the kernel, and then recompile the
> >        driver".
> >
> > OK. But I use the originally installed kernel and I didn't change
> > configuration. Then could you any idea what's wrong?
> > Any help you can offer would be appreciated!
> >
> > Zoltan Kovacs
> >
> 

Hy Gerhard,
 
Thanks for your help. But I have a 7.2 and none of the files you mentioned
can be found in the /boot directory. Thus I  copied 'autoconf.h' and 
'version.h' from /usr/include/linux to /usr/src/linux/include/linux. Well,
the RedHat versions are really different from the original ones. The only
problem is that I cannot find 'something.config' in /boot directory and I
don't know where is the Linux config file which the program 'make' uses to
compile pt_drv.o. 
During the compilation I see some warning messages "linux/malloc.h is
deprecated, use linux/slab.h instead" but pt_drv.o is created. Anyway,
the installation is still unsuccesful. The problem is the same:
Unresolved symbols. The symbols are also the same as formerly.
Do you think the problem is a wrong config file?

regards
Zoltan

On Wed, 10 Jul 2002, Jaeger, Gerhard wrote:

> Hi,
> 
> the answer is the same, even if you have installed the original
> kernel (what ever this means), it is possible, that the configuration
> is wrong. i.e. SuSE provides three files which can be found in
> /boot:
> vmlinuz_24.autoconf.h
> vmlinuz_24.config
> vmlinuz_24.version.h
> They have used these config file to build the kernel and these
> files are needed (and of course the other headers) to build a driver,
> that fits the kernel.
> 
> Gerhard
> 
> -------------------------
> gerhard AT gjaeger DOT de
> 
> On Tuesday, 9. July 2002 18:19, Zoltan Kovacs wrote:
> > Hello,
> >
> > I think I have a well known problem: during the installation I got the
> > error message:
> >
> > depmod: *** Unresolved symbols in /lib/modules/2.4.2-2/misc/pt_drv.o
> >
> > When I check the unresolved symbols I see:
> >
> > depmod: 	add_timer_Rsmp_a19eacf8
> > depmod: 	del_timer_Rsmp_fc62f16d
> > depmod: 	create_proc_entry_Rsmp_b5e3694a
> > depmod: 	__generic_copy_to_user_Rsmp_d523fdd3
> > depmod: 	parport_claim_Rsmp_dc843753
> > depmod: 	parport_register_device_Rsmp_75a20b73
> > depmod: 	unregister_chrdev_Rsmp_c192d491
> > depmod: 	proc_root_Rsmp_1fb67437
> > depmod: 	__vmalloc_Rsmp_79995c5b
> > depmod: 	parport_unregister_device_Rsmp_0cffd5b6
> > depmod: 	sprintf_Rsmp_1d26aa98
> > depmod: 	parport_release_Rsmp_e2338255
> > depmod: 	printk_Rsmp_1b7d4074
> > depmod: 	kfree_Rsmp_037a0cba
> > depmod: 	vfree_Rsmp_2fd1d81c
> > depmod: 	remove_proc_entry_Rsmp_dd4655a7
> > depmod: 	kmalloc_Rsmp_93d4cfe6
> > depmod: 	parport_enumerate_Rsmp_b88956ae
> > depmod: 	schedule_Rsmp_4292364c
> > depmod: 	__const_udelay_Rsmp_eae3dfd6
> > depmod: 	register_chrdev_Rsmp_fd911478
> > depmod: 	__udelay_Rsmp_9e7d6bd0
> > depmod: 	proc_mkdir_Rsmp_5d29064b
> > depmod: 	__generic_copy_from_user_Rsmp_116166aa
> > depmod: 	jiffies_Rsmp_0da02d67
> > depmod: 	do_gettimeofday_Rsmp_72270e35
> > message
> >
> > Formerly I've found a guy with the same problem in the mailing list but
> > the answer to him was
> >
> >        "This looks to me, as your kernel-configuration
> >        does not match the really installed and unsed kernel!
> >
> >        You might recompile and install the kernel, and then recompile the
> >        driver".
> >
> > OK. But I use the originally installed kernel and I didn't change
> > configuration. Then could you any idea what's wrong?
> > Any help you can offer would be appreciated!
> >
> > Zoltan Kovacs
> >
> 

Hy Gerhard,
 
Thanks for your help. But I have a 7.2 and none of the files you mentioned
can be found in the /boot directory. Thus I  copied 'autoconf.h' and 
'version.h' from /usr/include/linux to /usr/src/linux/include/linux. Well,
the RedHat versions are really different from the original ones. The only
problem is that I cannot find 'something.config' in /boot directory and I
don't know where is the Linux config file which is used in the Makefile 
to compile pt_drv.o. Neither can I find a variable containing the path of
a file  'something.config' in the Makefile so I dont't know where it
should be during the compilation. But I tried to compile again. 
During the compilation I see some warning messages "linux/malloc.h is
deprecated, use linux/slab.h instead" but pt_drv.o is, of course,  
created. Anyway, the installation is still unsuccesful. The problem is the
same: Unresolved symbols. The symbols are also the same as formerly.
Do you think the problem is a wrong config file?

regards
Zoltan

On Donnerstag, 11. Juli 2002 12:34, Zoltan Kovacs wrote:
[SNIP]
> Hy Gerhard,
>
> Thanks for your help. But I have a 7.2 and none of the files you mentioned
> can be found in the /boot directory. Thus I  copied 'autoconf.h' and
> 'version.h' from /usr/include/linux to /usr/src/linux/include/linux. Well,
> the RedHat versions are really different from the original ones. The only
> problem is that I cannot find 'something.config' in /boot directory and I
> don't know where is the Linux config file which is used in the Makefile
> to compile pt_drv.o. Neither can I find a variable containing the path of
> a file  'something.config' in the Makefile so I dont't know where it
> should be during the compilation. But I tried to compile again.
> During the compilation I see some warning messages "linux/malloc.h is
> deprecated, use linux/slab.h instead" but pt_drv.o is, of course,
> created. Anyway, the installation is still unsuccesful. The problem is the
> same: Unresolved symbols. The symbols are also the same as formerly.
> Do you think the problem is a wrong config file?
>
> regards
> Zoltan
[SNAP]

This all looks to me like a really bad installation :-(
You might create your own kernel, as the config file will be created
after you made the kernel-configuration (make menuconfig)...

The warning messages can be ignored, if the really disturb, you can
use the file plustek_sysdep.h in the include path to fix this...

Maybe there are some other RedHat users out there to give you some
hints...

Gerhard

 -------------------------
|gerhard AT gjaeger DOT de|
 -------------------------

On Fri, 12 Jul 2002, Jaeger, Gerhard wrote:

> On Donnerstag, 11. Juli 2002 12:34, Zoltan Kovacs wrote:
> [SNIP]
> > Hy Gerhard,
> >
> > Thanks for your help. But I have a 7.2 and none of the files you mentioned
> > can be found in the /boot directory. Thus I  copied 'autoconf.h' and
> > 'version.h' from /usr/include/linux to /usr/src/linux/include/linux. Well,
> > the RedHat versions are really different from the original ones. The only
> > problem is that I cannot find 'something.config' in /boot directory and I
> > don't know where is the Linux config file which is used in the Makefile
> > to compile pt_drv.o. Neither can I find a variable containing the path of
> > a file  'something.config' in the Makefile so I dont't know where it
> > should be during the compilation. But I tried to compile again.
> > During the compilation I see some warning messages "linux/malloc.h is
> > deprecated, use linux/slab.h instead" but pt_drv.o is, of course,
> > created. Anyway, the installation is still unsuccesful. The problem is the
> > same: Unresolved symbols. The symbols are also the same as formerly.
> > Do you think the problem is a wrong config file?
> >
> > regards
> > Zoltan
> [SNAP]
> 
> This all looks to me like a really bad installation :-(
> You might create your own kernel, as the config file will be created
> after you made the kernel-configuration (make menuconfig)...
> 
> The warning messages can be ignored, if the really disturb, you can
> use the file plustek_sysdep.h in the include path to fix this...
> 
> Maybe there are some other RedHat users out there to give you some
> hints...
> 
> Gerhard
> 
>  -------------------------
> |gerhard AT gjaeger DOT de|
>  -------------------------
> 
> 

Hy  Gerhard,

Thanks for your help again! After reinstalling my RH 7.1 I could compile
and install pt_drv.o. Then I set my port to EPP (i.e. the file
/proc/sys/dev/parport/parport0/modes contains PCSPP,TRISTATE,EPP), added
the standard text 

alias char-major-40 pt_drv
post-install pt_drv modprobe -k parport
options pt_drv lampoff=180 warmup=15 lOffonEnd=0 port=0x378 mov=0 slowIO=0
forceMode=0

to the file 'modules.conf' and loaded this module.

But a mysterious problem has arisen. When I type 'scanimage -L' no
information appears on the attached scanner. But the kernel messages are
the following:

SMSC Super-IO detection, now testing Ports 2F0, 370 ...
parport0: PC-style at 0x378 [PCSPP,TRISTATE,EPP]
parport0: cpp_daisy: aa5500ff(38)
parport0: assign_addrs: aa5500ff(38)
parport0: cpp_daisy: aa5500ff(38)
parport0: assign_addrs: aa5500ff(38)
pt_drv0: P12 found on port 0x0378
pt_drv0: Lamp-Timer set to 180 seconds.
pt_drv0: WarmUp period set to 15 seconds.
pt_drv0: Lamp untouched on driver unload.
  
I suppose it means the scanner is detected. Anyway it is not available.
SANE has failed to use it. Anyway, when I run 'scanimage -L' first time
after booting sometimes the lamp of the scanner is turned off or off and
on again. But only the first time. If run  'scanimage -L' again nothing
happens. What could be wrong? Do I set wrong parameters in
modules.conf? Do you have any idea?

Zoltan



  

On Tuesday, 23. July 2002 08:43, you wrote:
[SNIP]
> But a mysterious problem has arisen. When I type 'scanimage -L' no
> information appears on the attached scanner. But the kernel messages are
> the following:
>
> SMSC Super-IO detection, now testing Ports 2F0, 370 ...
> parport0: PC-style at 0x378 [PCSPP,TRISTATE,EPP]
> parport0: cpp_daisy: aa5500ff(38)
> parport0: assign_addrs: aa5500ff(38)
> parport0: cpp_daisy: aa5500ff(38)
> parport0: assign_addrs: aa5500ff(38)
> pt_drv0: P12 found on port 0x0378
> pt_drv0: Lamp-Timer set to 180 seconds.
> pt_drv0: WarmUp period set to 15 seconds.
> pt_drv0: Lamp untouched on driver unload.
>
> I suppose it means the scanner is detected. Anyway it is not available.
> SANE has failed to use it. Anyway, when I run 'scanimage -L' first time
> after booting sometimes the lamp of the scanner is turned off or off and
> on again. But only the first time. If run  'scanimage -L' again nothing
> happens. What could be wrong? Do I set wrong parameters in
> modules.conf? Do you have any idea?

Hi,

the scanner is detected - okay! So what about the device-node
/dev/pt_drv
does it exist?
Is the Plustek backend enabled in sane.d/dll.conf?
Is the parport device enabled in sane.d/plustek.conf?

You might enable the sane debug stuff and send us the output:
export SANE_DEBUG_DLL=255
export SANE_DEBUG_PLUSTEK=12
scanimage -L

Hope this helps
  Gerhard