m. allan noah wrote: > On 3/7/07, Steve Brown <[email protected]> wrote: >> Anybody using this combination? > > the driver was tested with a 3096, which uses basically the same > protocol as the 3093, but few of these things are still in use. > >> I just upgraded from 1.0.15 and now get a window error from the scanner. >> Reverting to the old driver at pfeiffer.edu works. >> > > first- which version of the driver did you try- sane 1.0.18, or the > more recent cvs versions? > second- can you try the cvs version? > third- what frontend program did you use? > fourth- what scanning parameters did you use? > fifth- can you get a debug log when the error occurs? >> Also, where can I find the scsi protocol for the scanner? > > docs for these old models used to be available from fujitsu's european > website. not sure if they still are. > > allan >
I used the cvs driver. The scanning parms were the defaults. export SANE_DEBUG_FUJITSU=128 scanimage -d fujitsu:/dev/sg0 >image scanimage: sane_read: Invalid argument The debug log is attached I then replaced the cvs fujitsu driver with the one from pfeiffer.edu (fujitsu-1_0_20.tgz), everything is cvs and got: $scanimage -v -v -v -v -d fujitsu:/dev/sg0 > image.pnm scanimage: rounded value of br-x from 215.9 to 215.893 scanimage: rounded value of br-y from 297 to 296.994 scanimage: scanning image of size 2549x3507 pixels at 8 bits/pixel scanimage: acquiring gray frame scanimage: min/max graylevel value = 25/255 scanimage: read 8939343 bytes in total Closing device Calling sane_exit scanimage: finished As the new driver appears completely restructured, the debug output of it doesn't really compare to that from the new driver. If that is useful, I can post it too. Steve -------------- next part -------------- A non-text attachment was scrubbed... Name: fujitsu.log Type: text/x-log Size: 15262 bytes Desc: not available Url : http://lists.alioth.debian.org/pipermail/sane-devel/attachments/20070307/044d4b29/fujitsu-0001.bin From [email protected] Wed Mar 7 18:46:57 2007 From: [email protected] (Steve Brown) Date: Wed Mar 7 19:08:50 2007 Subject: [sane-devel] Fujitsu M3093DG & new driver In-Reply-To: <[email protected]> References: <[email protected]> <[email protected]> Message-ID: <[email protected]> m. allan noah wrote: > On 3/7/07, Steve Brown <[email protected]> wrote: >> Anybody using this combination? > > the driver was tested with a 3096, which uses basically the same > protocol as the 3093, but few of these things are still in use. > >> I just upgraded from 1.0.15 and now get a window error from the scanner. >> Reverting to the old driver at pfeiffer.edu works. >> > > first- which version of the driver did you try- sane 1.0.18, or the > more recent cvs versions? > second- can you try the cvs version? > third- what frontend program did you use? > fourth- what scanning parameters did you use? > fifth- can you get a debug log when the error occurs? >> Also, where can I find the scsi protocol for the scanner? > > docs for these old models used to be available from fujitsu's european > website. not sure if they still are. > > allan > I used the cvs driver. The scanning parms were the defaults. export SANE_DEBUG_FUJITSU=128 scanimage -d fujitsu:/dev/sg0 >image scanimage: sane_read: Invalid argument The debug log is attached I then replaced the cvs fujitsu driver with the one from pfeiffer.edu (fujitsu-1_0_20.tgz), everything is cvs and got: $scanimage -v -v -v -v -d fujitsu:/dev/sg0 > image.pnm scanimage: rounded value of br-x from 215.9 to 215.893 scanimage: rounded value of br-y from 297 to 296.994 scanimage: scanning image of size 2549x3507 pixels at 8 bits/pixel scanimage: acquiring gray frame scanimage: min/max graylevel value = 25/255 scanimage: read 8939343 bytes in total Closing device Calling sane_exit scanimage: finished As the new driver appears completely restructured, the debug output of it doesn't really compare to that from the new driver. If that is useful, I can post it too. Steve -------------- next part -------------- A non-text attachment was scrubbed... Name: fujitsu.log Type: text/x-log Size: 15262 bytes Desc: not available Url : http://lists.alioth.debian.org/pipermail/sane-devel/attachments/20070307/60f82fae/fujitsu.bin From [email protected] Wed Mar 7 21:04:39 2007 From: [email protected] (=?iso-8859-15?q?St=E9phane_VOLTZ?=) Date: Wed Mar 7 20:02:24 2007 Subject: [sane-devel] Can't use Scanjet 3200c In-Reply-To: <[email protected]> References: <[email protected]> <[email protected]> <[email protected]> Message-ID: <[email protected]> Le mercredi 7 mars 2007, Mauricio Fernandez a ?crit?: > On 3/7/07, St?phane VOLTZ <[email protected]> wrote: > > > Hi Stef, > > > > > > I removed the # from the dll.conf file, and from the > > > dll.conf.rpmsavefile and when I do scanimage -L it says: > > > > > > [umax_pp_low] sanei_umax_pp_InitPort cannot use direct hardware access > > > [umax_pp_low] if not compiled with --enable-parport-directio > > > > > > No scanners were identified. If you were expecting something different, > > > check that the scanner is plugged in, turned on and detected by the > > > sane-find-scanner tool (if appropriate). Please read the documentation > > > which came with this software (README, FAQ, manpages). > > > > > > What do I have to do? > > > > > > Thank you for helping > > > > It seems the ppdev character device isn't working, or the backend > > is > > configured to use direct hardware access, which isn't compiled in. > > Check that th ppdev kernel module is loaded and that your user > > account has > > rights to access the /dev/parport0 device. Then edit umax_pp.conf (in the > > same directory than dll.conf) and change the line: > > > > port some-value > > > > to: > > > > port /dev/parport0 > > > > Things should get better. > > > > Regards, > > Stef > > Hi Stef, > > I ran lsmod, to check if ppdev was loaded, and shows > > Module Size Used by > ppdev 13125 0 > > which means it is. not? > > I'm logged as root, I edited the umax_pp.conf and replaced some-value with > /dev/parport1 (because I'm using an PCI LPT port) and scanimage -L now > instead of showing > > > [umax_pp_low] sanei_umax_pp_InitPort cannot use direct hardware access > > [umax_pp_low] if not compiled with --enable-parport-directio > > > > No scanners were identified. If you were expecting something different, > > check that the scanner is plugged in, turned on and detected by the > > sane-find-scanner tool (if appropriate). Please read the documentation > > which came with this software (README, FAQ, manpages) > > shows only > > > No scanners were identified. If you were expecting something different, > > check that the scanner is plugged in, turned on and detected by the > > sane-find-scanner tool (if appropriate). Please read the documentation > > which came with this software (README, FAQ, manpages) > > I tried putting parport0 also, but the results are the same. > > What's wrong? > > Thank you a lot for helping Hello, in order to see what is going on, you might turn on debug messages with export SANE_DEBUG_UMAX_PP_LOW=255 export SANE_DEBUG_UMAX_PP=255 In the terminal, before running scanimage. Regards, Stef
