[sane-devel] About the GL646(_HP) and future release of SANE
Le Sunday 03 February 2008 16:20:50 Tourneur Henry-Nicolas, vous avez ?crit?: Hello, I'm a debian user of SANE and I'v got a hp 3690 scanjet. I saw it uses a GL646_HP chipset which is included in the genesys backend as an experimental driver. I would like to know if there is any planed release of sane which will include some support for this chipset. Kind regards. Hello, there is currently no plan to update the genesys backend for the GL646 part. Someone with the hardware has to modify it. In case you feel like trying to do such, there are some informations about doing this at http://stef.dev.free.fr/sane/genesys/index.html You can also aks question to the mailing list. Regards, Stef
[sane-devel] HP 8270 scanjet support
Hi, thanks for the report that it works at all. However, the HP 8270 was reported used with my SANE backend in a 20 scanner installation without any problems. I also do not have lockup or instability issues with the Avision scanner (unlike HP, Avision is even donating scanners, so I can test them ...). Scanning is also known to work with 5400dpi on my Avision based Minolta Elite 5400 film scanner. Would be great if you could devote a little time writing some how to reproduce texts with SANE_DEBUG_AVISION=7 (for a beginning) log messages. That would be a great help. Regarding the high res borderless windoer issue: Maybe just save such huge files to disk instead of letting the built-in image view display it ... Yours, On 04.02.2008, at 04:27, shivers at ccs.neu.edu wrote: I owe this list a followup on my attempt to get sane working with an HP Scanjet 8270. As Rene suggested, I checked out the sane-backend module from the CVS repository, compiled it on my AMD64 ubuntu gutsy system installed it without problems. Once it was installed, sane-find-scanner was able to see it, and I was able to do scans with xsane. That's the good news. The bad news is that it is quite flaky: it locks up and/or crashes frequently enough to be unusable. If I push the scan resolution too high, it locks up. If I do several scans, it eventually locks up. After a high-res scan, xsane will pop up a borderless full-screen window showing the scan that I am unable to dismiss. I'm able to work around all this simply by running the HP software in WinXP in a vmware sandbox and writing the files out to the unix filesystem via samba. But I hope this report is of some use, and if I can submit anything more detailed that would be helpful, let me know what I should do, and I'll try to make it happen. Thanks for all the advice. -Olin -- Ren? Rebe - ExactCODE GmbH - Europe, Germany, Berlin Gesch?ftsf?hrer: Susanne Klaus, Ren? Rebe Sitz: Berlin, Amtsgericht Charlottenburg HRB 105 123 B USt-IdNr.: DE251602478 http://exactcode.de | http://t2-project.org | http://rene.rebe.name
[sane-devel] HP 8270 scanjet support
On Feb 4, 2008 11:57 AM, shivers at ccs.neu.edu wrote: From: =?ISO-8859-1?Q?Ren=E9_Rebe?= rene at exactcode.de Date: Mon, 4 Feb 2008 09:55:19 +0100 thanks for the report that it works at all. However, the HP 8270 was reported used with my SANE backend in a 20 scanner installation without any problems. I also do not have lockup or instability issues with the Avision scanner (unlike HP, Avision is even donating scanners, so I can test them ...). Scanning is also known to work with 5400dpi on my Avision based Minolta Elite 5400 film scanner. Great! Would be great if you could devote a little time writing some how to reproduce texts with SANE_DEBUG_AVISION=7 (for a beginning) log messages. That would be a great help. OK, so what you would like me to do is to set the environment var $SANE_DEBUG_AVISION to 7 and then do a losing xsane run in that environment? Regarding the high res borderless windoer issue: Maybe just save such huge files to disk instead of letting the built-in image view display it ... I'm new to using xsane, so am surely doing things in non-optimal ways. -Olin all on one line: SANE_DEBUG_AVISION=7 xsane 2xsane.8270.log but i wonder if you might try to replicate the problem with the command line program scanimage as well, since it is simpler than xsane, and might make less debugging output. allan -- The truth is an offense, but not a sin
[sane-devel] Canon LiDE 90
Hello,
It's a little bit better with these values.
In Genesys_Sensor I have :
regs_0x08_0x0b : {0x00, 0x21, 0x00, 0x00}
regs_0x10_0x1d : {0x02, 0x8b, 0x02, 0x8b, 0x02, 0x8b, 0x20, 0x06, 0x00,
0xff, 0x24, 0x00, 0x00, 0x04}
regs_0x52_0x5e : {0x02, 0x04, 0x02, 0x04, 0x02, 0x04, 0x0a, 0x71, 0x55,
0x00, 0x00, 0x20, 0x41}
In Genesys_Gpo I have :
{0x02, 0x80}{0x7f, 0xe0}
and now in Genesys_Frontend :
{{0x00, 0x2f, 0x07, 0x26}
, {0x00, 0x00, 0x00}
, {0x50, 0x50, 0x50}
, {0x28, 0x28, 0x28}
, {0x0d, 0x00, 0x00}
}
Are these value acceptable regarding my log
(http://ggastebois.free.fr/lide90_snoop/UsbSnoop_a4_200dpi.log) ?
I very appreciate your help.
Regards
Guillaume
P.S : attached a sample image with my values.
Pierre Willenbrock a ?crit :
Guillaume Gastebois schrieb:
OK, but via which register is it programmed. I find nothing in GL842
datasheet
for frontend.
regards
Guillaume
the analog frontend is programmed through the serial interface accessed
by address registers 0x50(FERDA)/0x51(FEWRA) and data registers
0x46/0x47(FERDDATA)/0x3a/0x3b(FEWRDATA).
I find this sequence in your log:
R/W ! addr ! data ! WM8199 register
+--+---+-
W ! 0x04 ! 0x000 ! reset
R ! 0x07 ! 0x041 ! revision number, ==0x41
W ! 0x04 ! 0x000 ! reset
W ! 0x01 ! 0x02f ! Setup reg 1: mode4==0, pgafs=2, selpd=1, mono=1,
cds=1, en=1
W ! 0x02 ! 0x007 ! Setup reg 2: del=0, rlcdacrng=0, 0=0, vrlcext=0,
invop=1, muxop=3
W ! 0x03 ! 0x026 ! Setup reg 3: chan=0, cdsref=2, rlcv=6
W ! 0x06 ! 0x00d ! Setup reg 4: fm=0, intm=0, rlcint=1, fme=1,
acycnrlc=0, linebyline=1
W ! 0x08 ! 0x000 ! Setup reg 5: 0=0, posnneg=0, vdel=0, vsmpdet=0
W ! 0x20 ! 0x050 ! dac value red(offset value)
W ! 0x21 ! 0x050 ! dac value green(offset value)
W ! 0x22 ! 0x050 ! dac value blue(offset value)
W ! 0x23 ! 0x050 ! dac value rgb(offset value)
W ! 0x28 ! 0x028 ! pga gain red(0x28 is a factor of 0.85)
W ! 0x29 ! 0x028 ! pga gain green
W ! 0x2a ! 0x028 ! pga gain blue
W ! 0x2b ! 0x028 ! pga gain rgb
all WM81xx(at least where datasheets are available) share a similar
register layout, with revision 0x41 at address 7. writing to the rgb
variant of pga gain/dac value results in writes to all the color
specific registers, so it is not needed.
So, you have in Genesys_Frontend: reg[1]=0x2f, reg[2]=0x07, reg[3]=0x26,
reg2[0]=0x0d, reg2[1]=0x00, the rest of reg/reg2 =0, all sign[x]=0,
offset[x]=0x50, gain[x]=0x28.
this does not match anything currently in genesys_devices.c. Just add
one entry to the Wolfson array, #define a DAC_ to 7 in genesys_low.h
and put that in your Genesys_Model.
The gain/offset setting should be good for led calibration and will be
replaced by gain/offset calibration.
After that, get a scan of the calibration area(the area under the
housing at the parking position). For this, put 0 into the x_offset and
y_offset in your Genesys_Model. If this turns out to be similar to the
calibration area of the lide 50, led/offset/gain-calibration should work
with only minor changes.
Regards,
Pierre
-- next part --
A non-text attachment was scrubbed...
Name: toto.jpg
Type: image/jpeg
Size: 14210 bytes
Desc: not available
Url :
http://lists.alioth.debian.org/pipermail/sane-devel/attachments/20080204/32c0a175/attachment.jpg
[sane-devel] scanmaker 4800 still trying...is this the right place to ask for help?
Hi, I am new on this list and new to debian and SANE. I have done the best I can to try and troubleshoot this scanner myself, but have not succeeded. I think the problem is with SANE, but I am not sure this is the appropriate place to ask for help. If it is not, please let me know if there is someplace I can ask for help with this. That said, here is the problem I am having: I am trying to get SANE to work with microtek scanmaker 4800. It opens the front end, whether xscanimage or xsane, but freezes upon trying to scan. Because it fails in both front ends, I am assuming the problem is either with the back end or communication with it. I read sane-problems-doc.html and followed the instructions as best I could. Here is what I've tried so far: uninstalled sane, xsane, and libsane, reinstalled. I did this because I installed the driver for scanmaker 4800 myself rather than through the package installer, so I guessed that uninstalling and reinstalling would write the correct files. I found out later that the driver, sm3840, is included in the distribution for sane or xsane so I did not need to install it seperately. Perhaps I need to do more to uninstall the file I installed, but I don't know if that is the case or how to tell. then I commented out all other scanners and net in /etc/sane.d/dll.conf. The troubleshooting instructions say it should be in /usr/etc/sane.d/dll.conf, but I am assuming the different location is from how the debian package installer installs it. made sure only one version is installed removed config directories from home dir searched for g*-config...found neither gtk-config nor gimp-config ran gdb scanimage with following result: ... Starting program: /usr/bin/xscanimage Failed to read a valid object file image from memory. (no debugging symbols found) ... [Thread debugging using libthread_db enabled] (no debugging symbols found) ... [New Thread -1219606848 (LWP 7249)] (no debugging symbols found) ... (... indicates prior line repeating many times) front end opens, finds scanner sm3840, but freezes when I hit scan or preview, and I have to force a quit. gdb still does not return, so hit ctrl-C, which returned to gdb prompt after giving message: Program received signal SIGTSTP, Stopped (user). [Switching to Thread -1219606848 (LWP 7249)] 0xb7f84410 in ?? () backtrace then gave the following results: (gdb) backtrace #0 0xb7f84410 in ?? () #1 0xbffd8068 in ?? () #2 0xbffd804c in ?? () #3 0xc0105500 in ?? () #4 0xb76ae789 in ioctl () from /lib/tls/i686/cmov/libc.so.6 #5 0xb77b0204 in usb_control_msg () from /lib/libusb-0.1.so.4 #6 0xb74a610f in sanei_usb_control_msg () from /usr/lib/sane/libsane-sm3840.so.1 #7 0xb749a843 in sane_sm3840_get_parameters () from /usr/lib/sane/libsane-sm3840.so.1 #8 0xb749a8ce in sane_sm3840_get_parameters () from /usr/lib/sane/libsane-sm3840.so.1 #9 0xb749ac8e in sane_sm3840_get_parameters () from /usr/lib/sane/libsane-sm3840.so.1 #10 0xb749d932 in sane_sm3840_start () from /usr/lib/sane/libsane-sm3840.so.1 #11 0xb77b6a8f in sane_dll_start () from /usr/lib/libsane.so.1 #12 0xb77b87bd in sane_start () from /usr/lib/libsane.so.1 #13 0x0804f6f4 in ?? () #14 0x080cdda0 in ?? () #15 0x0002 in ?? () #16 0x in ?? () had to kill process before exiting gdb If you need more info, let me know! I would really like to get this thing working. --Thanks for your help ~Rich Rath
[sane-devel] Patch/Fujitsu: add fi-5110eoxm USB ID
Hi,
In case this change is not already in the upcoming release of
the Fujitsu sane back end, here is a patch adding the USB device ID
for the Fujitsu fi-5110eoxm, a color duplex scanner with automatic
document feed which is sometimes sold at low prices from surplus
outlets because it is Macintosh only, although it works fine on my
PC. My understanding is the same as the fi-5110eox (or is
fi-5110eox2?) with only the follow differences:
1. Different USB device ID.
2. Sold in a box containing Macintosh drivers without Microsoft
Windows drivers.
3. Painted white.
I have one of these scanners, which I have been using
regularly for several months, mostly scanning in color at 300dpi,
duplex and simplex in a variety of page sizes.
I believe that the only problem that I have had with the
scanner that probably has a software component appears to be a linux
kernel issue rather than user level code, but I'll mention it here
just for full disclosure. Occasionally, scanimage will not exit
after appearing to have scanned a page, and its process will not exit
even when killed with kill -9 (so, I believe this must involve a
kernel bug).
Anyhow, I have included the patch as a MIME attachment. I
hope it can be integrated.
Adam Richter
-- next part --
--- sane-backends-1.0.18/backend/fujitsu.c 2006-06-26 10:08:38.0
-0700
+++ sane-backends/backend/fujitsu.c 2008-02-04 14:57:26.0 -0800
@@ -502,6 +502,8 @@
DBG (15, find_scanners: looking for 'usb 0x04c5 0x10e7'\n);
sanei_usb_attach_matching_devices(usb 0x04c5 0x10e7, attach_one_usb);
+ DBG (15, find_scanners: looking for 'usb 0x04c5 0x10f2'\n);
+ sanei_usb_attach_matching_devices(usb 0x04c5 0x10f2, attach_one_usb);
}
for (dev = fujitsu_devList; dev; dev=dev-next) {
--- sane-backends-1.0.18/backend/fujitsu.conf.in2006-06-29
10:11:57.0 -0700
+++ sane-backends/backend/fujitsu.conf.in 2008-02-04 14:58:23.0
-0800
@@ -42,5 +42,8 @@
#fi-5900C
usb 0x04c5 0x10e7
+#ScanSnap fi-5110eoxm
+usb 0x04c5 0x10f2
+
#scansnap S500
usb 0x04c5 0x10fe
[sane-devel] Patch/Fujitsu: add fi-5110eoxm USB ID
thanks Adam, it's been included in the development version for nearly a year. Its been a long time since we've had a release :) If you track down the bug, let us know, i am curious. allan On 2/4/08, Adam J. Richter adam at yggdrasil.com wrote: Hi, In case this change is not already in the upcoming release of the Fujitsu sane back end, here is a patch adding the USB device ID for the Fujitsu fi-5110eoxm, a color duplex scanner with automatic document feed which is sometimes sold at low prices from surplus outlets because it is Macintosh only, although it works fine on my PC. My understanding is the same as the fi-5110eox (or is fi-5110eox2?) with only the follow differences: 1. Different USB device ID. 2. Sold in a box containing Macintosh drivers without Microsoft Windows drivers. 3. Painted white. I have one of these scanners, which I have been using regularly for several months, mostly scanning in color at 300dpi, duplex and simplex in a variety of page sizes. I believe that the only problem that I have had with the scanner that probably has a software component appears to be a linux kernel issue rather than user level code, but I'll mention it here just for full disclosure. Occasionally, scanimage will not exit after appearing to have scanned a page, and its process will not exit even when killed with kill -9 (so, I believe this must involve a kernel bug). Anyhow, I have included the patch as a MIME attachment. I hope it can be integrated. Adam Richter -- The truth is an offense, but not a sin
