[sane-devel] Mustek 1200 CP not working with sane 1.0.17 on FreeBSD

2006-07-30 Thread Dura-Zell
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1

Jochen Eisinger wrote:
 Hi,
 
 Dura-Zell wrote:
 To exclude any hardwarproblems I tested the parallelport with some other
  devices:
 you don't happen to have the possibility to try your scanner with the
 original drivers?
 
 regards
 -- jochen


Hi

Sorry, at the moment this is not possible I'm afraid. Currently I've got
only an FreeBSD Computer. The last time I used the scanner with its
original drivers (ca 3 weeks ago) it worked as normal.

greetings,
Sven
-BEGIN PGP SIGNATURE-
Version: GnuPG v1.4.2 (FreeBSD)
Comment: Using GnuPG with Mozilla - http://enigmail.mozdev.org

iD8DBQFEzQQ1oqizRZ7rzU8RAkaCAJoDUgXS4zGbZat5DcXFWQWy2lY2CQCg99oX
FpyMmGsYAFgNuKRqb4RydoQ=
=dU1F
-END PGP SIGNATURE-


[sane-devel] Mustek 1200 CP not working with sane 1.0.17 on FreeBSD

2006-07-28 Thread Dura-Zell
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1

Jochen Eisinger wrote:
 Hi,
 
 Dura-Zell wrote:
 [sanei_pa4s2] pa4s2_open: device `0x378` opened...
 this looks good...
 
 [sanei_pa4s2] pa4s2_readbyte_nib: reading value 0x77 from '0x378'
 and this looks very bad. should be A5 or A8 or similar.
 
 is your parallel port configured in EPP mode (maybe you can configure
 that in the BIOS?
 
 regards
 -- jochen

Hi

My port is configured for EPP, 0x378 and IRQ 7. I tried different modes
(ECP and SPP) and portnumbers (0x278) also.

To exclude any hardwarproblems I tested the parallelport with some other
 devices:
A Kyocera FS1000+ Laserprinter (with cups) and a 4x20 LCD (with
lcdproc) are working with it, the scanner is working with win, so I
think the hardware is ok. Meanwhile I have deinstalled both, lcdproc and
cups, to be sure none of them are running and blocking my parallelport.

So what does
[sanei_pa4s2] pa4s2_readbyte_nib: reading value 0x77 from '0x378'
exactly mean and what can I do about it?


greetings,
Sven

-BEGIN PGP SIGNATURE-
Version: GnuPG v1.4.2 (FreeBSD)
Comment: Using GnuPG with Mozilla - http://enigmail.mozdev.org

iD8DBQFEybygoqizRZ7rzU8RAohcAJ9eoQkazwBm7S6dWBVK/BMdY4+okACg7jdH
bIDJnMIMWMY3sF38oqE2PpY=
=UcRI
-END PGP SIGNATURE-


[sane-devel] Mustek 1200 CP not working with sane 1.0.17 on FreeBSD

2006-07-27 Thread Dura-Zell
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1

Hi

I've got an Mustek 1200 CP Scanner wich is connected to my computers
parallelport. I'm using FreeBSD 6.0 and the sane-version from the ports
collection. This is actually version 1.0.17. According to
http://sane-project.org/sane-backends.html#S-MUSTEK-PP the scanner
should be supported good.

I have libieee1284 on my system installed.

I compiled my sane with libieee1284 and --enable-parport-directio

Now, when I run sane-find-scanner -p it can't find my scanner. I get
same result when I run scanimage -L

I'm doing all this as root, so there should no access/rights problem.
Parallelport support is enabled in my kernel and according to dmesg my
port (0x378 / EPP (tried without EPP too)) is recognized by the system.
I modified dll.conf to activate mustek_pp and made an entry in
mustek_pp.conf:

scanner mustek * cis1200

I also tried 0x378, ppi0, /dev/ppi0 instead of the asterisk for the device.

After fiddeling with the debuglevels I got the result following result.
Sorry for the large block: I didn't know wich part is important. This
run was with autoprobing in my mustek_pp.conf.

If anyone has an idea what to do I would appreciate this very much.

Greetings, Sven

su-2.05b# scanimage -L
[sanei_debug] Setting debug level of mustek_pp to 128.
[mustek_pp] sane-mustek_pp, version 0.13-beta. build for SANE 1.0.17
[mustek_pp] backend by Jochen Eisinger jochen.eisin...@gmx.net
[sanei_debug] Setting debug level of sanei_pa4s2 to 128.
[sanei_pa4s2] sanei_pa4s2_devices: interface called for the first time
[sanei_pa4s2] sanei_pa4s2_devices: invoked
[sanei_pa4s2] pa4s2_init: static int first_time = 1
[sanei_pa4s2] pa4s2_init: called for the first time
[sanei_pa4s2] pa4s2_init: initializing libieee1284
[sanei_pa4s2] pa4s2_init: 3 ports reported by IEEE 1284 library
[sanei_pa4s2] pa4s2_init: port 0 is `0x278`
[sanei_pa4s2] pa4s2_init: port 1 is `0x378`
[sanei_pa4s2] pa4s2_init: port 2 is `0x3bc`
[sanei_pa4s2] pa4s2_init: allocating port list
[sanei_pa4s2] pa4s2_init: initialized successfully
[mustek_pp] sanei_init: auto probing port
[sanei_pa4s2] sanei_pa4s2_open: called for device '0x278'
[sanei_pa4s2] sanei_pa4s2_open: trying to connect to port
[sanei_pa4s2] pa4s2_open: trying to attach dev `0x278`
[sanei_pa4s2] pa4s2_init: static int first_time = 0
[sanei_pa4s2] pa4s2_init: sanei already initalized
[sanei_pa4s2] pa4s2_open: looking up port in list
[sanei_pa4s2] pa4s2_open: port is in list at port[0]
[sanei_pa4s2] pa4s2_open: setting up port data
[sanei_pa4s2] pa4s2_open: name=0x278 in_use=SANE_TRUE
[sanei_pa4s2] pa4s2_open: enabled=SANE_FALSE mode=PA4S2_MODE_NIB
[sanei_pa4s2] pa4s2_open: opening device
[sanei_pa4s2] pa4s2_open: device `0x278` opened...
[sanei_pa4s2] pa4s2_open: returning SANE_STATUS_GOOD
[sanei_pa4s2] pa4s2_open: open dev `0x278` as fd 0
[sanei_pa4s2] sanei_pa4s2_open: connected to device using fd 0
[sanei_pa4s2] sanei_pa4s2_open: checking for scanner
[sanei_pa4s2] sanei_pa4s2_enable: called for fd 0 with value 1
[sanei_pa4s2] sanei_pa4s2_enable: enable port '0x278'
[sanei_pa4s2] pa4s2_enable: prelock[] = {0xf8, 0xf8, 0x05}
[sanei_pa4s2] sanei_pa4s2_enable: returning SANE_STATUS_GOOD
[sanei_pa4s2] sanei_pa4s2_open: reading ASIC id
[sanei_pa4s2] sanei_pa4s2_readbegin: called for fd 0 and register 0
[sanei_pa4s2] sanei_pa4s2_readbegin: NIB readbegin
[sanei_pa4s2] pa4s2_readbegin_nib: selecting register 0 at '0x278'
[sanei_pa4s2] sanei_pa4s2_readbegin: returning SANE_STATUS_GOOD
[sanei_pa4s2] sanei_pa4s2_readbyte: called with fd 0
[sanei_pa4s2] sanei_pa4s2_readbyte: we hope, the backend called
[sanei_pa4s2] sanei_pa4s2_readbyte: readbegin, so the port is ok...
[sanei_pa4s2] sanei_pa4s2_readbyte: this means, I did not check it - it's
[sanei_pa4s2] sanei_pa4s2_readbyte: not my fault, if your PC burns down.
[sanei_pa4s2] sanei_pa4s2_readbyte: read in NIB mode
[sanei_pa4s2] pa4s2_readbyte_nib: reading value 0x77 from '0x278'
[sanei_pa4s2] sanei_pa4s2_readbyte: read finished
[sanei_pa4s2] sanei_pa4s2_readbyte: got value 0x77
[sanei_pa4s2] sanei_pa4s2_readbyte: returning SANE_STATUS_GOOD
[sanei_pa4s2] sanei_pa4s2_readend: called for fd 0
[sanei_pa4s2] sanei_pa4s2_readend: we hope, the backend called
[sanei_pa4s2] sanei_pa4s2_readend: readbegin, so the port is ok...
[sanei_pa4s2] sanei_pa4s2_readend: this means, I did not check it - it's
[sanei_pa4s2] sanei_pa4s2_readend: not my fault, if your PC burns down.
[sanei_pa4s2] sanei_pa4s2_readend: NIB mode readend
[sanei_pa4s2] pa4s2_readend_nib: end of reading sequence for fd 0
[sanei_pa4s2] sanei_pa4s2_readend: returning SANE_STATUS_GOOD
[sanei_pa4s2] sanei_pa4s2_open: could not find scanner
[sanei_pa4s2] sanei_pa4s2_open: reported ASIC id 0x77
[sanei_pa4s2] sanei_pa4s2_enable: called for fd 0 with value 0
[sanei_pa4s2] sanei_pa4s2_enable: disable port '0x278'
[sanei_pa4s2] pa4s2_disable: state restored
[sanei_pa4s2] sanei_pa4s2_enable: returning SANE_STATUS_GOOD
[sanei_pa4s2] sanei_pa4s2_open: closing port