Hi Gerhard, I checked it again. My BIOS tells me, that parallel port was set to EPP. So I tried it again with all available parallel port modes. For kernel messages and output of commands "modprobe pt drv" and "scanimage -L" see the attachement. I used mov=4. It was to late in the evening to try it also with mov=0. I hope this doesn't matter for now. I forgot "export SANE DEBUG PLUSTEK=12". Hopefully it is not needed now. The result: With parallel port set to ECP a scanner was detected. XSANE could make one preview scan. The scanner moved back after this but maybe not exact to the initial position. The preview did not show anything usable - much color. The original was a white paper with black letters. After this no second scan was possible (only noise). Rebooting didn't help. I think using windows would initialize the scanner for a second test, but I did not try this yesterday. I hade a look into the scanner. Here comes something I found there. Maybe this helps. Hopefully I copied the numbers and letters without mistakes. * board (is this the right word here?): MAIDE IN TAIWAN R.O.C. 11-01-421A * circuits (same question: right word?): ----------------- P96003 9739WX030 ----------------- P97007 9806AAK ----------------- GALVANTECH C26015-1 TL9742 GVT72024A8J ----------------- TOSHIBA JAPAN TD62003AP 9804KS ---------------- Best regards, Ulrich -----Original Message----- From: Jaeger, Gerhard To: plustek@linuxhacker.org Sent: 4/3/03 9:29 PM Subject: Re: no device found (9021) Hi Ulrich, your problem is the wrong parallel port setting. You should set this in the BIOS to SPP or EPP, but avoid in any case ECP. With your box, this sometimes seem to work, but not reproducible... The following is from your log: Mar 31 23:27:04 linux kernel: Try to claim the parport Mar 31 23:27:04 linux kernel: parport-modi: SPP PS/2 EPP EPP(ECP) PS/2(ECP) Mar 31 23:27:04 linux kernel: Using EPP-mode This should look like: linux kernel: parport-modi: SPP PS/2 EPP linux kernel: Using EPP-mode Hope this helps Gerhard On Montag, 31. März 2003 23:36, ulrich.moehrke@gmx.de wrote: > Hi Gerhard, > > I come back to an old problem of mine where I have not done the last things > you wrote. Sorry for that. A long time I couldn't work with my scanner > because of many other things to do. I've lost your last mail, but I > remember that I didn't really understand and thought that I had done all > the things you wrote before. > > > > What's going on: > "modprobe pt drv" switches the lamp of my scanner on. > "scanimage -L" does not find a scanner. > "modprobe -r pt drv" does not switch the lamp of. > now "modprobe pt drv" failes. > > > > software: > suse 8.1 > sane 1.0.8 > plustek 0.45-5 > > > > scanner: > OpticPro 9636P > > > > What have I done until now: > > - setting parport to EPP > > - enabled "DEBUG=y" in Makefile > > - added plustek into /etc/modules.conf > --------------------------------------------------- > alias char-major-40 pt drv > pre-install pt drv modprobe -k parport > options pt drv lampoff=180 warmup=15 port=0x378 lOffonEnd=0 mov=0 slowIO=1 > -------------------------------------------------------- > I tried also mov=4 > > - In sane config file /etc/sane.d/dll.conf line "plustek" enabled. > (Have done it myself, can you add this into documentation?) > > > export SANE DEBUG PLUSTEK=12 > > > > modprobe pt drv > > switches lamp of the scanner on (output of "tail -f /var/log/messages" in > attachment) > > > scanimage -L > > no device found (output in attachment) > > > modprobe -r pt drv > > The lamp did not switch off. > > again: > > modprobe -r pt drv > > failed > > > You will find some output in attachments. > > > Thanks for your help. What can I do to find the problem? > > Best regards, > Ulrich --------------------------------------------------------------------- To unsubscribe, e-mail: plustek-unsubscribe@linuxhacker.org For additional commands, e-mail: plustek-help@linuxhacker.org
Hi Gerhard,
I checked it again. My BIOS tells me, that parallel port was set to EPP. So I tried it again with all available parallel port modes. For kernel messages and output of commands "modprobe pt drv" and "scanimage -L" see the attachement.
I used mov=4. It was to late in the evening to try it also with mov=0. I hope this doesn't matter for now.
I forgot "export SANE DEBUG PLUSTEK=12". Hopefully it is not needed now.
The result:
With parallel port set to ECP a scanner was detected. XSANE could make one preview scan. The scanner moved back after this but maybe not exact to the initial position. The preview did not show anything usable - much color. The original was a white paper with black letters.
After this no second scan was possible (only noise). Rebooting didn't help. I think using windows would initialize the scanner for a second test, but I did not try this yesterday.
I hade a look into the scanner. Here comes something I found there. Maybe this helps. Hopefully I copied the numbers and letters without mistakes.
* board (is this the right word here?):
MAIDE IN TAIWAN R.O.C.
11-01-421A
* circuits (same question: right word?):
-----------------
P96003
9739WX030
-----------------
P97007
9806AAK
-----------------
GALVANTECH
C26015-1
TL9742
GVT72024A8J
-----------------
TOSHIBA JAPAN
TD62003AP 9804KS
----------------
Best regards,
Ulrich
-----Original Message-----
From: Jaeger, Gerhard
To: plustek@linuxhacker.org
Sent: 4/3/03 9:29 PM
Subject: Re: no device found (9021)
Hi Ulrich,
your problem is the wrong parallel port setting. You should
set this in the BIOS to SPP or EPP, but avoid in any case ECP.
With your box, this sometimes seem to work, but not reproducible...
The following is from your log:
Mar 31 23:27:04 linux kernel: Try to claim the parport
Mar 31 23:27:04 linux kernel: parport-modi: SPP PS/2 EPP EPP(ECP)
PS/2(ECP)
Mar 31 23:27:04 linux kernel: Using EPP-mode
This should look like:
linux kernel: parport-modi: SPP PS/2 EPP
linux kernel: Using EPP-mode
Hope this helps
Gerhard
On Montag, 31. März 2003 23:36, ulrich.moehrke@gmx.de wrote:
> Hi Gerhard,
>
> I come back to an old problem of mine where I have not done the last
things
> you wrote. Sorry for that. A long time I couldn't work with my scanner
> because of many other things to do. I've lost your last mail, but I
> remember that I didn't really understand and thought that I had done
all
> the things you wrote before.
>
>
>
> What's going on:
> "modprobe pt drv" switches the lamp of my scanner on.
> "scanimage -L" does not find a scanner.
> "modprobe -r pt drv" does not switch the lamp of.
> now "modprobe pt drv" failes.
>
>
>
> software:
> suse 8.1
> sane 1.0.8
> plustek 0.45-5
>
>
>
> scanner:
> OpticPro 9636P
>
>
>
> What have I done until now:
>
> - setting parport to EPP
>
> - enabled "DEBUG=y" in Makefile
>
> - added plustek into /etc/modules.conf
> ---------------------------------------------------
> alias char-major-40 pt drv
> pre-install pt drv modprobe -k parport
> options pt drv lampoff=180 warmup=15 port=0x378 lOffonEnd=0 mov=0
slowIO=1
> --------------------------------------------------------
> I tried also mov=4
>
> - In sane config file /etc/sane.d/dll.conf line "plustek" enabled.
> (Have done it myself, can you add this into documentation?)
>
> > export SANE DEBUG PLUSTEK=12
> >
> > modprobe pt drv
>
> switches lamp of the scanner on (output of "tail -f /var/log/messages"
in
> attachment)
>
> > scanimage -L
>
> no device found (output in attachment)
>
> > modprobe -r pt drv
>
> The lamp did not switch off.
>
> again:
> > modprobe -r pt drv
>
> failed
>
>
> You will find some output in attachments.
>
>
> Thanks for your help. What can I do to find the problem?
>
> Best regards,
> Ulrich
---------------------------------------------------------------------
To unsubscribe, e-mail: plustek-unsubscribe@linuxhacker.org
For additional commands, e-mail: plustek-help@linuxhacker.org