Subject:
Re: driver for LM983x based scanners next shot
From:
Kyrian ####@####.####
Date:
24 Nov 2001 16:13:22 -0000
Message-Id: <3BFFC74B.BE49D395@ore.org>
All,
Sorry if this is a SANE problem, rather than a Plustek USB problem, but
anyway, here goes...
I've got a Plustek UT12, and am testing SANE 1.0.6, the 0_40_6 snapshot
of the USB driver code... Oh, and various 2.4 kernel versions, with the
USB stuff modular, or compiled in.
[ I'm using an RPM I built from a spec file, which includes the Plustek
USB patch, which seems to have built okay, ie. it dumped out
plustek.conf, modified dll.conf, and dumped out a
libsane-plustek.so.1.0.6, which I think is all it needs do... People are
welcome to have those RPM's if I can prove that my scanner works with
them... ]
This is what I am getting, or rather not getting as the case may be.
The scanner (and my USB QuickCam, although this problem occurs even with
just the scanner plugged into the USB ports) are recognised fine in
/proc/bus/usb/devices, and reflected in /var/log/messages as well.
However, I just can't get the damned thing working.
Without:
options scanner vendor=0x07b3 product=0x0017
in my /etc/conf.modules, sane-find-scanner does not recognise my scanner
(curious!). With it included, sane-find-scanner does recognise it.
It recognises is as "sane-find-scanner: found USB scanner (UNKNOWN
vendor and product) at device /dev/usb/scanner0".
But then even when sane-find-scanner recognises the device, running
scanimage and pointing it explicitly at the correct devide always gets
me:
scanimage: open of device plustek:/dev/usc/scanner0 failed: Invalid
argument
And having thrown strace at the problem, I get some results that are
probably quite curious...
With /etc/sane.d/plustek.conf as:
/dev/usb/scanner0
usb 0x07b3 0x0017
I get:
[root@marius sane.d]# strace scanimage --device
plustek:/dev/usc/scanner0 2>&1 | tail -20
open("/usr/lib/sane/libsane-plustek.so.1", O_RDONLY) = 3
close(3) = 0
open("/usr/lib/sane/libsane-plustek.so.1", O_RDONLY) = 3
read(3, "\177ELF\1\1\1\0\0\0\0\0\0\0\0\0\3\0\3\0\1\0\0\0\0\33\0"...,
1024) = 1024
fstat64(3, {st_mode=S_IFREG|0755, st_size=36587, ...}) = 0
old_mmap(NULL, 31044, PROT_READ|PROT_EXEC, MAP_PRIVATE, 3, 0) =
0x40016000
mprotect(0x4001d000, 2372, PROT_NONE) = 0
old_mmap(0x4001d000, 4096, PROT_READ|PROT_WRITE, MAP_PRIVATE|MAP_FIXED,
3, 0x6000) = 0x4001d000
close(3) = 0
open("./plustek.conf", O_RDONLY) = 3
fstat64(3, {st_mode=S_IFREG|0644, st_size=36, ...}) = 0
old_mmap(NULL, 4096, PROT_READ|PROT_WRITE, MAP_PRIVATE|MAP_ANONYMOUS,
-1, 0) = 0x4001e000
read(3, "usb 0x07b3 0x0017\n/dev/usb/scann"..., 4096) = 36
read(3, "", 4096) = 0
close(3) = 0
munmap(0x4001e000, 4096) = 0
write(2, "scanimage: open of device pluste"..., 77scanimage: open of
device plustek:/dev/usc/scanner0 failed: Invalid argument
) = 77
munmap(0x40016000, 31044) = 0
_exit(1) = ?
[root@marius sane.d]# vi /etc/sane.d/plustek.conf
With /etc/sane.d/plustek.conf as:
/dev/usb/scanner0
usb 0x07b3 0x0017
I get:
[root@marius sane.d]# strace scanimage --device
plustek:/dev/usc/scanner0 2>&1 | tail -20
read(3, "\177ELF\1\1\1\0\0\0\0\0\0\0\0\0\3\0\3\0\1\0\0\0\0\33\0"...,
1024) = 1024
fstat64(3, {st_mode=S_IFREG|0755, st_size=36587, ...}) = 0
old_mmap(NULL, 31044, PROT_READ|PROT_EXEC, MAP_PRIVATE, 3, 0) =
0x40016000
mprotect(0x4001d000, 2372, PROT_NONE) = 0
old_mmap(0x4001d000, 4096, PROT_READ|PROT_WRITE, MAP_PRIVATE|MAP_FIXED,
3, 0x6000) = 0x4001d000
close(3) = 0
open("./plustek.conf", O_RDONLY) = 3
fstat64(3, {st_mode=S_IFREG|0644, st_size=36, ...}) = 0
old_mmap(NULL, 4096, PROT_READ|PROT_WRITE, MAP_PRIVATE|MAP_ANONYMOUS,
-1, 0) = 0x4001e000
read(3, "/dev/usb/scanner0\nusb 0x07b3 0x0"..., 4096) = 36
open("/dev/usb/scanner0", O_RDONLY) = 4
ioctl(4, 0x40027801, 0xbfffe39a) = -1 ENOTTY (Inappropriate ioctl
for device)
close(4) = 0
read(3, "", 4096) = 0
close(3) = 0
munmap(0x4001e000, 4096) = 0
write(2, "scanimage: open of device pluste"..., 77scanimage: open of
device plustek:/dev/usc/scanner0 failed: Invalid argument
) = 77
munmap(0x40016000, 31044) = 0
_exit(1) = ?
[root@marius sane.d]#
I assume that the latter is the correct syntax of the plustek.conf file,
because it actually attempts to open up the device itself, rather than
fail on something else which doesn't attempt to open it...
Oh, and also, I've tried as suggested by various people putting "options
connect-device", or "connect-device" into the SANE plustek.conf file,
among other things, which has had no effect.
I hope this is of some help to Gerhard, or someone can help me sort out
my scanner. Please? Help! I don't want to have to reload Win2k! :-(
Yours,
Kev.
Michael Häckel wrote:
>
> Hi,
>
> On Thursday 22 November 2001 09:58, Jaeger, Gerhard wrote:
> >
> > There's no need to load a specific driver (only the usb-stuff like
> > scanner!)
> >
> > The other one is for using the parport!
>
> Thanks for the fast answer!
>
> > Make sure that the plustek.conf file looks like:
> >
> > usb 0x07b3-0x0017
> > /dev/usbscanner
>
> It was already there, but seems, I simply loaded the wrong module.
>
> I also had to insert "options scanner vendor=0x07b3 product=0x0017" in
> modules.conf. Now the scanner is found.
>
> However it doesn't really work.
> If I select color mode in xscanimage and click the scan button the scanner
> light switches on and off, the CPU usage goes to 100% (according to the
> cooler speed) and then the system locks solid (not even remote login
> possible).
> The same for preview, just there the light remains on.
>
> Linux-2.4.14, Sane-1.0.6.
>
> Regards,
> Michael Häckel
>
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: ####@####.####
> For additional commands, e-mail: ####@####.####
