plustek: Thread: USB-scanner...

Hi there,

I've currently put on the latest build (40_11) onto the driver page.
This should fix some trouble on newer kernels. I'd like to hear from
you.
What about the UT16: any success so far?
Does the U12 work! 

Can you please send me the product IDs again, as I'Ve lost them?

Thanx
  Gerhard

Hi,

On Monday 10 December 2001 19:23, Jaeger, Gerhard wrote:
> Hi there,
>
> I've currently put on the latest build (40_11) onto the driver page.
> This should fix some trouble on newer kernels. I'd like to hear from
> you.

I still get a system freeze on linux-2.4.16. Unlike with earlier versions not 
when starting with scanning but already when starting xscanimage.

On linux-2.2.20 now all problems I reported seem to be gone, great!

I get the impression, that the light switches a bit more often on and off and 
moves a bit more forwards and backwards than really necessary, but that 
doesn't have an impact on the scanned image of course.

With the software that came with the scanner, the scanner always needs a 
warming up phase. Your driver doesn't seem to do that. I can't see a problem, 
but could the lack of warming up eventually result in slightly less quality 
of the images?

Regards,
Michael Häckel

Michael, Gerhard, et al,

> I still get a system freeze on linux-2.4.16. Unlike with earlier versions not
>  when starting with scanning but already when starting xscanimage.
I see this too.

Curiously though 0_40_10 made the light on my UT12 go on, and then cause a
system hang.

0_40_11 doesn't even seem to make the light go on before hanging.

Noteworthy perhaps as well is that when using the device /dev/usbscanner I get a
system hang, and when using /dev/usb/scanner0 (both devices are configured the
same, as both device files, and in /etc/sane.d/plustek.conf) I only get
scanimage segfaulting on me. I don't know if this is of consequence, so ignore
it if it isn't useful ;-)

I've never done a kernel debug/trace thing before. If someone can point me at
the right resources, I'll give it a go to see if I can help. It might be, errr,
"fun", or something ;-)

> On linux-2.2.20 now all problems I reported seem to be gone, great!
> I get the impression, that the light switches a bit more often on and off and
> moves a bit more forwards and backwards than really necessary, but that
> doesn't have an impact on the scanned image of course.
I'll try this later to see if I can duplicate it (on a different machine,
though... I have just ext3'd all my filesystems on my main linux box here... as
well as having other reasons for staying up to date kernel-wise)

Yours,

Kev.

Gene Heskett sends Greetings to Jaeger, Gerhard;

>Hi there,

>I've currently put on the latest build (40_11) onto the driver page.
>This should fix some trouble on newer kernels. I'd like to hear from
>you.
>What about the UT16: any success so far?
>Does the U12 work! 

>Can you please send me the product IDs again, as I'Ve lost them?

>Thanx
>  Gerhard

Re: Epson Perfectionist 1250U, vender/product=0x04b8/0x010f

I wiped the sane-backends-1.0.6 tree many times tonight thinking I
wasn't unpacking it correctly since ./configure --prefix=/usr
--sysconfdir=/etc was exiting on the ltconfig call if I unpacked 40_11
into the sane-backends-1.0.6 directory first.  Odd.

I finally got it to build by running ./configure before unpacking the
Plustek-40_11 to it, then running configure again.  Making sure the
correct vender/product (usb 0x4b8 0x010f) was listed in
/etc/sane.d/plustek.conf, the finished product still reports via xsane
that no devices are available.

According to an strace, it does open, write and read the device without
reporting any errors, and does 10 or so assorted such operations, and
then it goes on to the next run thru the loop for a different device,
completing it all and reporting no devices available in about 300
milliseconds.  And my USB mouse survives, that was killing it,
requiring a reboot to get it back before, so this is an improvement.

I even went so far as to wipe the /etc/sane.d dir, build the frontends
and re-install, which gave me far fewer example device.conf's than I had
before, and which the rpms had apparently installed.  Then I fixed the
vender/product in the newly installed plustek.conf to match the above.

Here is the scanner section of a cat /proc/bus/usb/devices output, this
after adding its vendor/product to linux/drivers/usb/scanner.h: and
rebuilding the kernel, 2.4.17-pre7, then adding the options to
modules.conf and 'modprobe scanner' by hand after the reboot.

C:* #Ifs= 1 Cfg#= 1 Atr=40 MxPwr=  0mA
I:  If#= 0 Alt= 0 #EPs= 1 Cls=09(hub  ) Sub=00 Prot=00 Driver=hub
E:  Ad=81(I) Atr=03(Int.) MxPS=   8 Ivl=255ms
T:  Bus=01 Lev=01 Prnt=01 Port=00 Cnt=01 Dev#=  2 Spd=12  MxCh= 0
D:  Ver= 1.10 Cls=ff(vend.) Sub=00 Prot=ff MxPS= 8 #Cfgs=  1
P:  Vendor=04b8 ProdID=010f Rev= 1.00
S:  Manufacturer=EPSON

And here are a few lines from the strace of xsane.


open("/usr/lib/sane/libsane-plustek.so.1", O_RDONLY) = 6
close(6)                                = 0
open("/usr/lib/sane/libsane-plustek.so.1", O_RDONLY) = 6
read(6, "\177ELF\1\1\1\0\0\0\0\0\0\0\0\0\3\0\3\0\1\0\0\0 \"\0\000"..., 1024) = 1024
fstat64(6, {st_mode=S_IFREG|0755, st_size=396331, ...}) = 0
old_mmap(NULL, 222244, PROT_READ|PROT_EXEC, MAP_PRIVATE, 6, 0) = 0x4050c000
mprotect(0x4051f000, 144420, PROT_NONE) = 0
old_mmap(0x4051f000, 135168, PROT_READ|PROT_WRITE, MAP_PRIVATE|MAP_FIXED, 6, 0x12000) = 0x4051f000
old_mmap(0x40540000, 9252, PROT_READ|PROT_WRITE, MAP_PRIVATE|MAP_FIXED|MAP_ANONYMOUS, -1, 0) = 0x40540000
close(6)                                = 0
open("./plustek.conf", O_RDONLY)        = -1 EACCES (Permission denied)
open("/etc/sane.d/plustek.conf", O_RDONLY) = 6
fstat64(6, {st_mode=S_IFREG|0644, st_size=532, ...}) = 0
old_mmap(NULL, 4096, PROT_READ|PROT_WRITE, MAP_PRIVATE|MAP_ANONYMOUS, -1, 0) = 0x4002c000
read(6, "# Plustek-SANE Backend configura"..., 4096) = 532
open("/dev/usbscanner", O_RDWR)         = 7
ioctl(7, 0x80045520, 0xbfffd438)        = 0
ioctl(7, 0x80045521, 0xbfffd434)        = 0
write(7, "\0\7\0\1\0", 5)               = 5
write(7, "\0\10\0\1\2", 5)              = 5
write(7, "\1\7\0\1", 4)                 = 4
read(7, "\0", 1)                        = 1
write(7, "\1\10\0\1", 4)                = 4
read(7, "\2", 1)                        = 1
write(7, "\1i\0\1", 4)                  = 4
read(7, "\4", 1)                        = 1
write(7, "\0\7\0\1\0", 5)               = 5
close(7)                                = 0
read(6, "", 4096)                       = 0
close(6)                                = 0
munmap(0x4002c000, 4096)                = 0

And the rest appears to be the next '/etc/sane.d/net.conf' query
section, so it got snipped too in the interests of bandwidth.  The whole
strace file is 70 some kilobytes.

What else can I report that may be helpfull, and which I have the tools
to do?

Cheers, Gene
-- 
  Gene Heskett, CET, UHK       |Amiga A2k Zeus040, 70MB ram, 31 gigs
                               | Linux @ 500mhz, 320MB ram, 50 gigs
 	     email gene underscore heskett at iolinc dot net
#Amiga based X10 home automation program EZHome, see at:#
               <http://www.iolinc.net/gene_heskett>
This messages reply content, but not any previously quoted material,
is © 2001 by Gene Heskett, all rights reserved.
-- 

Hi

On Monday, 10. December 2001 20:44, Michael Häckel wrote:
> Hi,
>
> On Monday 10 December 2001 19:23, Jaeger, Gerhard wrote:
> > Hi there,
> >
> > I've currently put on the latest build (40_11) onto the driver page.
> > This should fix some trouble on newer kernels. I'd like to hear from
> > you.
>
> I still get a system freeze on linux-2.4.16. Unlike with earlier versions
> not when starting with scanning but already when starting xscanimage.

I've problems with my Via686 Mobo...

>
> On linux-2.2.20 now all problems I reported seem to be gone, great!

That's okay.

>
> I get the impression, that the light switches a bit more often on and off
> and moves a bit more forwards and backwards than really necessary, but that
> doesn't have an impact on the scanned image of course.

That's what Plustek calls calibration! Be sure I'm working on that, but 
the Windows driver has the same behaviour...

>
> With the software that came with the scanner, the scanner always needs a
> warming up phase. Your driver doesn't seem to do that. I can't see a
> problem, but could the lack of warming up eventually result in slightly
> less quality of the images?
>
Yup - you're right. Those lamps normaly need some warmup-time...
That's on my TODO list too...

Gerhard

On Tuesday, 11. December 2001 04:21, Gene Heskett wrote:
> Gene Heskett sends Greetings to Jaeger, Gerhard;
[SNIP]
> Re: Epson Perfectionist 1250U, vender/product=0x04b8/0x010f
>
> I wiped the sane-backends-1.0.6 tree many times tonight thinking I
> wasn't unpacking it correctly since ./configure --prefix=/usr
> --sysconfdir=/etc was exiting on the ltconfig call if I unpacked 40_11
> into the sane-backends-1.0.6 directory first.  Odd.
>
> I finally got it to build by running ./configure before unpacking the
> Plustek-40_11 to it, then running configure again.  Making sure the
> correct vender/product (usb 0x4b8 0x010f) was listed in
> /etc/sane.d/plustek.conf, the finished product still reports via xsane
> that no devices are available.
[SNAP]

Hi Gene,

let's try an pin down the problem:
Please enable the debug stuff:
export SANE_DEBUG_PLUSTEK=12

Then make sure, that the /etc/sane.d/dll.conf only contains
the plustek entry...

Then do a simple
scanimage -L

And send me the output.
Thanx
   Gerhard

Hi,

On Monday, 10. December 2001 21:03, Kyrian wrote:
> Michael, Gerhard, et al,
>
> > I still get a system freeze on linux-2.4.16. Unlike with earlier versions
> > not when starting with scanning but already when starting xscanimage.
>
> I see this too.
>
> Curiously though 0_40_10 made the light on my UT12 go on, and then cause a
> system hang.
>
> 0_40_11 doesn't even seem to make the light go on before hanging.
>
> Noteworthy perhaps as well is that when using the device /dev/usbscanner I
> get a system hang, and when using /dev/usb/scanner0 (both devices are
> configured the same, as both device files, and in /etc/sane.d/plustek.conf)
> I only get scanimage segfaulting on me. I don't know if this is of
> consequence, so ignore it if it isn't useful ;-)
>

every hint is useful! Althoug it doesn't make sense. It seems, that the USB 
stuff is somehow buggy, especially on ATHLON/Via Mobos. I've also a problem 
with segfaults and strange kernel messages. If possible use the 2.2.10/20 
kernel - well I even have an 2.4.12 up and running on my Thinkpad, it's hard
to say exactly which combination works and which not...

To pin down the segfault, I suggest to enable the SANE debug output:
export SANE_DEBUG_PLUSTEK=12
Then it's possible to see in which part of the code the driver segfaults.
I case of an segfault, you can also have a look at the output of 
dmesg
If there's noting special, the USB stuff seems to be okay, but in most
cases there are some stange usb messages....

Gerhard