[sane-devel] FreeBSD 5.1R, SANE, Canon 1240U scanner
On Tue, 10 Feb 2004, Gerhard Jaeger wrote: Hi, the 1240 is supported by the backend, but there are several issues with FreeBSD... The only issue I could find was that you had to disable the uscanner kernel module and use libusb instead. This was FreeBSD 5.1. I'm unaware of whether uscanner now supports the commands sane wants under 5.2. Charles There are some reports, that using the libusb does not work correctly, there's also a description for making a CanoScan device work with FreeBSD 4.8: http://gja.space4me.com/things/CanoScan_LiDE20_FreeBSD.html Maybe this helps... Ciao, Gerhard BTW: The LM9833 and the LM9832 are using the same internal version... On Monday 09 February 2004 21:01, Doug Carter wrote: Allan, 1. Double checking the man page for plustek, I find my scanner: sane-plustek(5) SANE Scanner Access Now Easy sane-plustek(5) Vendor CANON - ID: 0x04A9 -- USB Model: ASIC: Properties: Prod-ID -- CanoScan N1240ULM9833 1200x2400dpi 48bit 512Kb 0x220E 2. I make sure its plugged in to the usb port. 3. #SANE_DEBUG_PLUSTEK=255;export SANE_DEBUG_PLUSTEK 4. #scanimage -L 2 logfile and I get: [plustek] Plustek backend V0.46-9, part of sane-backends 1.0.13 snip, a bunch of stuff that I don't think matters at this point [plustek] drvopen() [plustek] usbDev_open(auto,0x04A9-0x220E) [plustek] Found device at libusb:/dev/usb0:/dev/ugen0 [plustek] Vendor ID=0x04A9, Product ID=0x220E [plustek] usbio_DetectLM983x [plustek] UIO error [plustek] This is not a LM9831 or LM9832 chip based scanner. [plustek] open failed: -1 [plustek] sane_get_devices (0xbfbff3e8, 0) [plustek] sane_exit ... so, perhaps the scanner is not supported despite the man page entry? Or, I notice it refers to LM9831 LM9832 but not LM9833 which the table notes for this scanner... Doug _ Click here for a FREE online computer virus scan from McAfee. http://clinic.mcafee.com/clinic/ibuy/campaign.asp?cid=3963 -- sane-devel mailing list: sane-devel@lists.alioth.debian.org http://lists.alioth.debian.org/mailman/listinfo/sane-devel Unsubscribe: Send mail with subject unsubscribe your_password to sane-devel-requ...@lists.alioth.debian.org
[sane-devel] UMAX backend with sanei_thread, Mac OS-X users please try, OS/2 users please try!
On Mon, 12 Jan 2004, Oliver Rauch wrote: Hello. I just replaced the fork() calls by sanei_thread_*() calls for the sane-umax backend. I tested it wirk fork() and threads on linux. This version is in the sane cvs now. Please could some Mac OS-X and OS/2 users test this version! I would love to give this a shot... Anyone else who's built the OS-X version: do you have a step-by-step guide? I generally build stuff on my Mac from Fink, are all the dependencies in Fink (ie: libusb, etc?). Thanks, Charles Best regards Oliver -- http://www.xsane.org http://www.mostang.com/sane http://www.rauch-domain.de mailto:oliver.ra...@rauch-domain.de -- sane-devel mailing list: sane-devel@lists.alioth.debian.org http://lists.alioth.debian.org/mailman/listinfo/sane-devel Unsubscribe: Send mail with subject unsubscribe your_password to sane-devel-requ...@lists.alioth.debian.org
[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] Umax 2200 (USB) failing
On Mon, 29 Dec 2003, Klaus Dahlke wrote: The lesson I learned is: - switch quality calibration off - use only libusb, I have deleted scanner.o from /lib/modules or did compile the kernel without scanner support for USB at another machine to have connection only via libusb. I just built and booted a kernel without the uscanner driver, and this takes me a little further. scanimage -L finds the scanner: root@green[/home/spork]# scanimage -L device `umax:libusb:/dev/usb0:/dev/ugen0' is a UMAX Astra 2200 flatbed scanner 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. The following is the debug output up to the point where the command hangs: root@green[/home/spork]# scanimage -d umax:libusb:/dev/usb0:/dev/ugen0 --format tiff test.tiff [sanei_debug] Setting debug level of umax to 255. [umax] sane_init [umax] This is sane-umax version 1.0 build 40 [umax] compiled with USB support for Astra 2200 [umax] (C) 1997-2002 by Oliver Rauch [umax] EMAIL: oliver.ra...@rauch-domain.de [umax] reading configure file umax.conf [umax] option handle-bad-sense-error = 3 [umax] option connection-type = 2 [umax] sanei_usb_attach_matching_devices(usb 0x1606 0x0230) [umax] attach_scanner: libusb:/dev/usb0:/dev/ugen0, connection_type 2 [umax] attach_scanner: opening usb device libusb:/dev/usb0:/dev/ugen0 [umax] Initializing the PV8630 [umax] PV8630 initialized [umax] attach_scanner: allocating SCSI buffer[0] [umax] init [umax] setting request_scsi_maxqueue = 1 for USB connection [umax] request_scsi_maxqueue = 1 [umax] request_preview_lines = 10 [umax] request_scan_lines = 40 [umax] handle_bad_sense_error = 3 [umax] execute_request_sense = 0 [umax] scsi_buffer_size_min = 32768 [umax] scsi_buffer_size_max = 131072 [umax] force_preview_bit_rgb = 0 [umax] slow = -1 [umax] smear = -1 [umax] calibration_area = -1 [umax] calibration_width_offset = -9 [umax] calibration_width_offset_batch = -9 [umax] calibration_bytespp= -1 [umax] exposure_time_rgb_bind = -1 [umax] invert_shading_data= -1 [umax] lamp_control_available = 0 [umax] backend runs on little endian machine [umax] variable scsi buffer size (usage of sanei_scsi_open_extended) [umax] initialize_values [umax] identify_scanner [umax] do_inquiry [umax] Sending SCSI cmd 0x12 cdb len 6, param len 0, result len 5 [umax] SCSI cmd returned 5 bytes [umax] SCSI command successfully executed [umax] Sending SCSI cmd 0x12 cdb len 6, param len 0, result len 160 [umax] SCSI cmd returned 160 bytes [umax] SCSI command successfully executed [umax] Found UMAX scanner Astra 2200 version V2.1 on device libusb:/dev/usb0:/dev/ugen0 [umax] umax_correct_inquiry(UMAX Astra 2200 V2.1) [umax] setting up special options for Astra 2200 [umax] - lamp control enabled [umax] - calibration by driver is done for each CCD pixel [umax] - setting calibration_bytespp = 2 [umax] - common x and y resolution [umax] get_inquiry_values [umax] INQUIRY: [umax] [umax] [umax] vendor: 'UMAX' [umax] product...: 'Astra 2200 ' [umax] version...: 'V2.1' [umax] peripheral qualifier..: 0 [umax] peripheral device type: 6 [umax] [umax] CBHS value range..: 0-255 [umax] scanmode..: flatbed (FB) [umax] UTA (transparency): available [umax] UTA lamp status ..: on [umax] [umax] inquiry block length..: 160 bytes [umax] [umax] ISO Version (reserved)...: 0 [umax] ECMA Version (reserved)...: 0 [umax] ANSI Version .: 2 [umax] [umax] reserved byte 0x05 = 0 [umax] reserved byte 0x06 = 0 [umax] [umax] scsi features (00): [umax] --- [umax] [umax] f/w support function: [umax] - [umax] - quality calibration [umax] - fast preview function [umax] [umax] reserved byte 0x36 = 0 [umax] reserved byte 0x37 = 0 [umax] [umax] scan modes (76): [umax] [umax] - single pass color mode [umax] - lineart mode [umax] - gray mode [umax] - color mode [umax] - transparency (UTA) [umax] [umax] scanner capability (be, 00, 00): [umax] [umax] - send high byte first [umax] - bi-level image reverse [umax] - multi-level image reverse [umax] - paper length can reach to 14 inch [umax] [umax] gamma download available [umax] gamma download type 2 [umax] lines of gamma curve: one line (gray), three lines (color) download [umax] gamma input 8 bits/pixel support [umax] gamma input 12 bits/pixel support [umax] gamma output 8 bits/pixel support [umax] gamma output 12 bits/pixel support [umax] [umax] reserved byte 0x65 = 0 [umax] reserved byte 0x67 = 0 [umax] [umax]
[sane-devel] Umax 2200 (USB) failing
Hi, I just installed Sane 1.0.13 on FreeBSD 5.1. I have a Umax Astra 2200-US scanner (scsi and usb), but only have a USB interface on my workstation. The OS detects that there's a scanner plugged in: uscanner0: UMAX Data Systems Astra 2200U Scanner, rev 1.00/1.00, addr 2 sane-find-scanner also sees something there: root@green[/usr/local/etc/sane.d]# 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. found USB scanner (vendor=0x1606, product=0x0230) at /dev/uscanner0 # Your USB scanner was detected. It may or may not be supported by # SANE. Try scanimage -L and read the backend's manpage. However running a test with scanimage (specifying the device/driver directly) just hangs. Enabling debug output shows the following: root@green[/usr/local/etc/sane.d]# scanimage -d umax:/dev/uscanner0 -T [sanei_debug] Setting debug level of umax to 255. [umax] sane_init [umax] This is sane-umax version 1.0 build 40 [umax] compiled with USB support for Astra 2200 [umax] (C) 1997-2002 by Oliver Rauch [umax] EMAIL: oliver.ra...@rauch-domain.de [umax] reading configure file umax.conf [umax] option handle-bad-sense-error = 3 [umax] option connection-type = 2 [umax] sanei_usb_attach_matching_devices(usb 0x1606 0x0230) [umax] attach_scanner: /dev/uscanner0, connection_type 2 [umax] attach_scanner: opening usb device /dev/uscanner0 [umax] Initializing the PV8630 [umax] PV8630 initialized [umax] attach_scanner: allocating SCSI buffer[0] [umax] init [umax] setting request_scsi_maxqueue = 1 for USB connection [umax] request_scsi_maxqueue = 1 [umax] request_preview_lines = 10 [umax] request_scan_lines = 40 [umax] handle_bad_sense_error = 3 [umax] execute_request_sense = 0 [umax] scsi_buffer_size_min = 32768 [umax] scsi_buffer_size_max = 131072 [umax] force_preview_bit_rgb = 0 [umax] slow = -1 [umax] smear = -1 [umax] calibration_area = -1 [umax] calibration_width_offset = -9 [umax] calibration_width_offset_batch = -9 [umax] calibration_bytespp= -1 [umax] exposure_time_rgb_bind = -1 [umax] invert_shading_data= -1 [umax] lamp_control_available = 0 [umax] backend runs on little endian machine [umax] variable scsi buffer size (usage of sanei_scsi_open_extended) [umax] initialize_values [umax] identify_scanner [umax] do_inquiry [umax] Sending SCSI cmd 0x12 cdb len 6, param len 0, result len 5 And there it sits, for hours... First of all, is this an officially supported scanner? Looking at the mailing lists it seems others have it working. Secondly, is there any other information I can provide to debug this? And lastly, I also have an iBook running OS-X 10.3.2. Is this scanner known to work under OS-X and Sane (Umax abandoned all support for these older models for OS-X)? Thanks! Charles
