[sane-devel] Umax 2200 smearing/dangerous options
Hello all, This will hopefully be the last time I bother the list. My Umax 2200 is now basically working, but the scans look pretty bad. They have what I could best describe as "banding" or "smearing". An example from a 300dpi scan is here (white areas on the left are the scanner lid and show the pattern rather well - looks like the output of a really bad inkjet printer): http://home.manymonkeys.com/out.png (approx. 1MB png) I've poked around the archives and don't see much mention of general quality issues. Any ideas? There are plenty of lightly-documented options in the umax.conf file, and some fairly interesting ones that carry the following warnings (without further explanation): # BE CAREFUL WITH THIS OPTION, IT MAY DESTROY YOUR SCANNER WHEN SET FALSE Of course, I'm itching to try these. Also, is there a wiki-type thing somewhere where people can share information about their particular models? It seems that I stumbled all over things that just aren't documented on the site, but are common knowledge once you're on the list for a while (ie: don't use the OS driver, use libusb, scanner won't work w/o quality control disabled, etc.) Thanks, Charles
[sane-devel] strange thread code?
i am converting the fujitsu backend to use sanei_thread instead of fork. in reading the threading code, i found something that i dont understand, and was hoping someone who knows a bit more could explain it to me: in the function sanei_thread_waitpid(), the #ifdef PTHREAD section always returns pid (around line 354). but farther down, in the #else section, the return val from the waitpid() call is returned (which is the pid on success, but 0 or -1 otherwise) so if you are calling sanei_thread_waitpid() and there is an error, you might, or might not, get a negative return value? am i not reading this code correctly? allan -- "so don't tell us it can't be done, putting down what you don't know. money isn't our god, integrity will free our souls" - Max Cavalera
[sane-devel] Epson GT-7400U not detected
Hi, On Wed, Dec 31, 2003 at 09:09:56AM +0900, Julian Gough wrote: > Under windows it is reported as an Epson Perfection 1270, and seems to > work, but the software is in Japanese. > > I can see that the 1250 and 1260 use the plustek driver. I've configured > /etc/sane.d/plustek.conf as follows: > [usb] 0x04B8 0x0120 > device auto > > but still I get nothing detected. I can see no way to try to *force* the > plustek driver to be used so that I can see if it works. You may also try the snapscan backend. At least the 1670 is supported by that backend. Maybe these scanners are similar? But you will need the latest development version of SANE. Maybe the manintainer of the snapscan backend has heard baout that scanner: Oliver Schwartz Bye, Henning
[sane-devel] Umax 2200 (USB) failing
Hi, On Tue, Dec 30, 2003 at 06:02:36PM -0500, Charles Sprickman wrote: > However on actually trying to scan something it hangs. Looking at the > umax.conf file and manpage I don't see any "quality calibration" options, > so I have not turned that off. "scanimage --help" should print alll options. Or run a frontend like "xsane". If there is an option to disable calibration, it should be shown. > The following is the debug output up to the point where the command hangs: > [umax] do_calibration > [umax] wait_scanner > [umax] Sending SCSI cmd 0x00 cdb len 6, param len 0, result len 0 > [umax] error in sanei_pv8630_bulkread (got 02) > [umax] scanner reports Error during device I/O, waiting ... > [umax] Sending SCSI cmd 0x00 cdb len 6, param len 0, result len 0 Really looks like a problem with calibration for me. Bye, Henning
[sane-devel] Umax 2200 (USB) failing
Hi, On Tue, Dec 30, 2003 at 06:10:44PM -0500, Charles Sprickman wrote: > > The UMAX backend has not been converted to sanei_thread yet and fork() > > doesn't work correctly on MacOS X. So you won't have luck with SANE > > 10.13. But if you look at our bug-tracking system, there is a patch > > that may work (untested): > > > > https://alioth.debian.org/tracker/index.php?func=detail&aid=300397&group_id=1308&atid=410366 > > Are there any FAQs floating around on building sane and libusb(?) under > OS-X? I don't think that there is a FAQ but at least current README.darwin files contain some info. The problem is that MacOS X is not a "typical Unix". That means that the "everything is a file" view is not correct for MacOS X. So we can't sue functions like fork() because e.g. USB access permissions aren't inherited. That breaks all backends which use fork on MacOS X. The solution is to use threads instead of sub-processes. That's what the sanei_usb API does. However, all the backends that may be of interest on MacOS X have to be converted to that API. That's not trivial in all cases. > > Please tell us about your success/failure on FreeBSD and MacOS X. > > So far FreeBSD isn't going very well, but I'd be more than happy to try > OS-X if the build process is documented somewhere. README.darwin (+ the general README). If something doesn't work, please tell us. Bye, Henning
[sane-devel] Epson GT-7400U not detected
On Wed, 2003-12-31 at 08:23, Karl Heinz Kremer wrote: > The scanner uses three USB pipes: Two bulk pipes for input and output > and one > interrupt pipe. This means it's not a "standard" EPSON scanner (meaning > that > it cannot be supported by the EPSON backend). I don't know this device, > it > seems to be a new scanner. > > Maybe Olaf can shed some light on this. > > Karl Heinz Under windows it is reported as an Epson Perfection 1270, and seems to work, but the software is in Japanese. I can see that the 1250 and 1260 use the plustek driver. I've configured /etc/sane.d/plustek.conf as follows: [usb] 0x04B8 0x0120 device auto but still I get nothing detected. I can see no way to try to *force* the plustek driver to be used so that I can see if it works. Julian
[sane-devel] MacOSX 10.3.2 and Fujitsu fi-4120C
Hi, Allan, are you still interested in converting the fujitsu backend to work with threading? In a post on the list Henning mentioned a patch that fixes the 'fork()' bug in another backend: https://alioth.debian.org/tracker/index.php? func=detail&aid=300397&group_id=1308&atid=410366 is it a first step? bye, giovanni
[sane-devel] Epson GT-7400U not detected
Dear list, I have just purchased an Epson scanner, model GT-7400U with the express purpose of getting it to work under Linux. I had hoped it would work since Epson was recommended and this is not a particularly advanced model (1200dpi CCD 16bit in/out USB2.0 [EPSON Scan] PRINT image matching II). I cannot work out what is the equivalent non-Japanese model number I'm afraid. I have RedHat with: sane-frontends-1.0.9-2, sane-backends-1.0.9-5.1, and iscan-1.5.2-1. Running xsane reports "no devices available", iscan reports "Could not send command to scanner", and scanimage -L reports "No scanners were identified". The outputs of lsusb and /proc are listed below. sane-find-scanner yields one of these: found USB scanner (vendor=0x04b8, product=0x0120) at /dev/usb/scanner0 found USB scanner (vendor=0x04b8, product=0x0120) at libusb:001:004 found USB scanner (vendor=0x04b8 [EPSON], product=0x0120 [EPSON Scanner]) at libusb:001:005 ... depending on how I configure /etc/modules.conf and /etc/sane.d/epson.conf I am assuming this is not a supported scanner, however I would like to try using one of the Epson drivers anyway to see if I can get it to work. Is this reasonable? The documentation suggests that this is a possibility, but if I follow the documentation I still get the same problem: scanner not detected. I don't think I can return this to the shop, so I would be very very grateful for any advice on how to try to get this functioning. [root@invigiator gough]# cat /proc/bus/usb/devices T: Bus=04 Lev=00 Prnt=00 Port=00 Cnt=00 Dev#= 1 Spd=12 MxCh= 2 B: Alloc= 0/900 us ( 0%), #Int= 0, #Iso= 0 D: Ver= 1.00 Cls=09(hub ) Sub=00 Prot=00 MxPS= 8 #Cfgs= 1 P: Vendor= ProdID= Rev= 0.00 S: Product=USB UHCI Root Hub S: SerialNumber=ec00 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=03 Lev=00 Prnt=00 Port=00 Cnt=00 Dev#= 1 Spd=12 MxCh= 2 B: Alloc= 0/900 us ( 0%), #Int= 0, #Iso= 0 D: Ver= 1.00 Cls=09(hub ) Sub=00 Prot=00 MxPS= 8 #Cfgs= 1 P: Vendor= ProdID= Rev= 0.00 S: Product=USB UHCI Root Hub S: SerialNumber=e800 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=02 Lev=00 Prnt=00 Port=00 Cnt=00 Dev#= 1 Spd=12 MxCh= 2 B: Alloc= 0/900 us ( 0%), #Int= 0, #Iso= 0 D: Ver= 1.00 Cls=09(hub ) Sub=00 Prot=00 MxPS= 8 #Cfgs= 1 P: Vendor= ProdID= Rev= 0.00 S: Product=USB UHCI Root Hub S: SerialNumber=e400 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=00 Prnt=00 Port=00 Cnt=00 Dev#= 1 Spd=480 MxCh= 6 B: Alloc= 0/800 us ( 0%), #Int= 0, #Iso= 0 D: Ver= 2.00 Cls=09(hub ) Sub=00 Prot=01 MxPS= 8 #Cfgs= 1 P: Vendor= ProdID= Rev= 2.04 S: Manufacturer=Linux 2.4.20-24.9 ehci-hcd S: Product=Intel Corp. 82801DB USB EHCI Controller S: SerialNumber=00:1d.7 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= 2 Ivl=256ms T: Bus=01 Lev=01 Prnt=01 Port=04 Cnt=01 Dev#= 5 Spd=480 MxCh= 0 D: Ver= 2.00 Cls=ff(vend.) Sub=ff Prot=ff MxPS=64 #Cfgs= 1 P: Vendor=04b8 ProdID=0120 Rev= 1.10 S: Manufacturer=EPSON S: Product=EPSON Scanner C:* #Ifs= 1 Cfg#= 1 Atr=c0 MxPwr=100mA I: If#= 0 Alt= 0 #EPs= 3 Cls=ff(vend.) Sub=ff Prot=ff Driver=(none) E: Ad=81(I) Atr=02(Bulk) MxPS= 512 Ivl=0ms E: Ad=02(O) Atr=02(Bulk) MxPS= 512 Ivl=0ms E: Ad=83(I) Atr=03(Int.) MxPS= 8 Ivl=4096ms [root@invigiator gough]# cat /proc/bus/usb/drivers usbdevfs hub 96-111: hiddev hid [root@invigiator gough]# sane-find-scanner # No SCSI scanners found. If you expected something different, make sure that # you have loaded a SCSI driver for your SCSI adapter. # Also you need support for SCSI Generic (sg) in your operating system. # If using Linux, try "modprobe sg". found USB scanner (vendor=0x04b8, product=0x0120) at libusb:001:004 # A USB device was detected. This program can't be sure if it's really # a scanner. If it is your scanner, it may or may not be supported by # SANE. Try scanimage -L and read the backend's manpage. # Scanners connected to the parallel port or other proprietary ports can't be # detected by this program. [root@invigiator gough]# lsusb Unknown line at line 58 Unknown line at line 2296 Unknown line at line 2297 Unknown line at line 2298 Unknown line at line 2299 Unknown line at line 2300 Unknown line at line 2301 Unknown line at line 2302 Unknown line at line 2303 Unknown line at line 2304 Unknown line at line 2305 Unknown line at line 2306 Unknown line at line 2307 Unknown line at line 2308 Unknown line at line 2309 Unknown line at line 2310 Unknown line at line 2311 Unknown line at line 2312 Unknow
