[sane-devel] diffs sent to support MP810, MP960, Canoscan 9000F
Hello all, I have submitted unified diffs for the following files to the maintainer: pixma_common.h pixma_common.c pixma.h (revised version sent after initial one) pixma.c (revied version sent after initial one) pixma_mp150.c pixma_mp750.c (only difference was modification of debug statement to use PRIu64) If I should send something to the list as well, please let me know. Best regards, Gernot Hassenpflug
[sane-devel] HP Deskjet Ink Advantage 2060 (K110)
Hi, Guys than you for the responses. To be clear, I don't have a problem with printing with this printer/scanner/copier, it is only with scanning. hpaio in the /etc/sane.d/dll.conf file is un-commented. I have attached the outputs of : sane-find-scanner -vv usb-devices Hopefully, there is a solution. Regards, Roger -- next part -- roger at roger-laptop:~$ sane-find-scanner -vv This is sane-find-scanner from sane-backends 1.0.20 # sane-find-scanner will now attempt to detect your scanner. If the # result is different from what you expected, first make sure your # scanner is powered up and properly connected to your computer. searching for SCSI scanners: checking /dev/scanner... failed to open (Invalid argument) checking /dev/sg0... failed to open (Access to resource has been denied) checking /dev/sg1... failed to open (Invalid argument) checking /dev/sg2... failed to open (Invalid argument) checking /dev/sg3... failed to open (Invalid argument) checking /dev/sg4... failed to open (Invalid argument) checking /dev/sg5... failed to open (Invalid argument) checking /dev/sg6... failed to open (Invalid argument) checking /dev/sg7... failed to open (Invalid argument) checking /dev/sg8... failed to open (Invalid argument) checking /dev/sg9... failed to open (Invalid argument) checking /dev/sga... failed to open (Invalid argument) checking /dev/sgb... failed to open (Invalid argument) checking /dev/sgc... failed to open (Invalid argument) checking /dev/sgd... failed to open (Invalid argument) checking /dev/sge... failed to open (Invalid argument) checking /dev/sgf... failed to open (Invalid argument) checking /dev/sgg... failed to open (Invalid argument) checking /dev/sgh... failed to open (Invalid argument) checking /dev/sgi... failed to open (Invalid argument) checking /dev/sgj... failed to open (Invalid argument) checking /dev/sgk... failed to open (Invalid argument) checking /dev/sgl... failed to open (Invalid argument) checking /dev/sgm... failed to open (Invalid argument) checking /dev/sgn... failed to open (Invalid argument) checking /dev/sgo... failed to open (Invalid argument) checking /dev/sgp... failed to open (Invalid argument) checking /dev/sgq... failed to open (Invalid argument) checking /dev/sgr... failed to open (Invalid argument) checking /dev/sgs... failed to open (Invalid argument) checking /dev/sgt... failed to open (Invalid argument) checking /dev/sgu... failed to open (Invalid argument) checking /dev/sgv... failed to open (Invalid argument) checking /dev/sgw... failed to open (Invalid argument) checking /dev/sgx... failed to open (Invalid argument) checking /dev/sgy... failed to open (Invalid argument) checking /dev/sgz... failed to open (Invalid argument) # No SCSI scanners found. If you expected something different, make sure that # you have loaded a kernel SCSI driver for your SCSI adapter. searching for USB scanners: checking /dev/usb/scanner... failed to open (Invalid argument) checking /dev/usb/scanner0... failed to open (Invalid argument) checking /dev/usb/scanner1... failed to open (Invalid argument) checking /dev/usb/scanner2... failed to open (Invalid argument) checking /dev/usb/scanner3... failed to open (Invalid argument) checking /dev/usb/scanner4... failed to open (Invalid argument) checking /dev/usb/scanner5... failed to open (Invalid argument) checking /dev/usb/scanner5... failed to open (Invalid argument) checking /dev/usb/scanner7... failed to open (Invalid argument) checking /dev/usb/scanner8... failed to open (Invalid argument) checking /dev/usb/scanner9... failed to open (Invalid argument) checking /dev/usb/scanner10... failed to open (Invalid argument) checking /dev/usb/scanner11... failed to open (Invalid argument) checking /dev/usb/scanner12... failed to open (Invalid argument) checking /dev/usb/scanner13... failed to open (Invalid argument) checking /dev/usb/scanner14... failed to open (Invalid argument) checking /dev/usb/scanner15... failed to open (Invalid argument) checking /dev/usbscanner... failed to open (Invalid argument) checking /dev/usbscanner0... failed to open (Invalid argument) checking /dev/usbscanner1... failed to open (Invalid argument) checking /dev/usbscanner2... failed to open (Invalid argument) checking /dev/usbscanner3... failed to open (Invalid argument) checking /dev/usbscanner4... failed to open (Invalid argument) checking /dev/usbscanner5... failed to open (Invalid argument) checking /dev/usbscanner6... failed to open (Invalid argument) checking /dev/usbscanner7... failed to open (Invalid argument) checking /dev/usbscanner8... failed to open (Invalid argument) checking /dev/usbscanner9... failed to open (Invalid argument) checking /dev/usbscanner10... failed to open (Invalid argument) checking /dev/usbscanner11... failed to open (Invalid argument) checking /dev/usbscanner12... failed to open (Invalid argument) checking /dev/usbscanner13... failed to open (Invalid argument) checking
[sane-devel] diffs sent to support MP810, MP960, Canoscan 9000F
Is PRlu64 C89? If not, you will have to drop that change. Someday sane will use C99 :) allan On Sat, Jan 15, 2011 at 7:56 PM, Gernot Hassenpflug aikishugyo at gmail.com wrote: Hello all, I have submitted unified diffs for the following files to the maintainer: pixma_common.h pixma_common.c pixma.h (revised version sent after initial one) pixma.c (revied version sent after initial one) pixma_mp150.c pixma_mp750.c (only difference was modification of debug statement to use PRIu64) If I should send something to the list as well, please let me know. Best regards, Gernot Hassenpflug -- sane-devel mailing list: sane-devel at lists.alioth.debian.org http://lists.alioth.debian.org/mailman/listinfo/sane-devel Unsubscribe: Send mail with subject unsubscribe your_password ? ? ? ? ? ? to sane-devel-request at lists.alioth.debian.org -- The truth is an offense, but not a sin
[sane-devel] Canon PIXMA MX870
OK, I did some playing around, trying things, reading logs, and looking at the code. I think I'm seeing a few different problems. First, if I place more than one page in the ADF and then try to scan only a single page (scanimage without --batch), then sane will leave the scanner hanging after the first page. The scanner loads page 2 and waits for commands, but scanimage returns success. This isn't just a matter of scanimage being oblivious, though: if only one page is physically present, scanimage sends the EndJob XML message after scanning that page, but if a second page is present, then no EndJob is sent. I believe I tracked this down to: pixma_mp150.c line 1506: /* FIXME: to process several pages ADF scan, must not send * abort_session and start_session between pages (last_block=0x28) */ if (mp-generation = 2 || !is_scanning_from_adf (s) || mp-last_block == 0x38) The EndJob message is sent in this branch. I'm guessing what the comment is telling me is that last_block is 0x28 when additional pages are available, instead of 0x38, and therefore the branch won't be taken. That said, this is arguably a case of incorrect usage anyway. If I have loaded multiple pages into the ADF, I really ought to be using --batch. And when I do, scanimage is able to scan multiple pages OK. == Unfortunately, there is another, less-deterministic problem. It seems that the scanner very frequently refuses sane's TCP connections: [pixma] Reader task terminated Scanned page 1. (scanner status = 5) Scanning page 2 [pixma] Reader task id=14568 (forked) [pixma] Reader task started [pixma] sanei_bjnp_activate (0) [pixma] udp_command: Sending UDP command to 10.0.1.22:8612 *[pixma] bjnp_open_tcp: Can not connect to scanner: Connection refused* [pixma] sanei_bjnp_deactivate (0) [pixma] udp_command: Sending UDP command to 10.0.1.22:8612 [pixma] [pixma] Reader task terminated: EINVAL read_image():reader task closed the pipe:0 bytes received, 10718400 bytes expected scanimage: sane_read: Invalid argument Scanned page 2. (scanner status = 4) [pixma] pixma_close(): Canon PIXMA MX870 [pixma] sanei_bjnp_close(0): It's hard to pin down a pattern describing when this happens, but: - It never happens if the scanner was just powered on (and had time to boot). Or in other words, power cycling the scanner fixes problems, suggesting that the scanner is getting into a bad state. - It always happens when the ADF runs out of paper. sane appears to form a new connection for each page. After the last page, sane tries to connect again even though there are no more pages, and this connection always fails AFAICT. This causes scanimage to exit with an error code even though technically it completed its task successfully. - After having completed a batch, the scanner is sometimes (but not always) left in a state where all further connections are refused until the device is power-cycled. Sometimes the device will recover from this state magically without a power cycle, if I retry a few times. Sometimes running Scangear MP can revive the device from this state, but not always. - I changed the TCP connection code to retry once, and the result is even odder: The retry sometimes succeeds, but then the scanner apparently does not reply to any requests on the new connection. I tried comparing network dumps between SANE and Scangear MP, but they were completely different. Scangear MP appears to make only one TCP connection for the whole batch, rather than one per page. Any ideas? On Sat, Jan 15, 2011 at 9:13 PM, Kenton Varda temporal at gmail.com wrote: Hi Nicolas and sane-devel, Back in July there was a thread on the Canon PIXMA MX870 that ended here: http://lists.alioth.debian.org/pipermail/sane-devel/2010-July/027197.html Using the latest sources from git, I find myself stuck at basically the same place as Matthais. When using the scanner over ethernet, I can sometimes scan one page from the ADF, but multiple pages fail. In general the device is very finicky. Over USB, scanimage -T just hangs. (I also had the same conflict with usblp that Matthias mentioned, but that went away when I did modprobe -r usblp usb_storage.) What can I do to help get this working? Note that the scanner works in Linux with Canon's Scangear MP, but I'd rather use sane. Thanks, -Kenton -- next part -- An HTML attachment was scrubbed... URL: http://lists.alioth.debian.org/pipermail/sane-devel/attachments/20110116/88a02a8a/attachment.htm
[sane-devel] Test report of HP ScanJet G2410 (genesys)
Hi, I have come across an HP ScanJet G2410 scanner (03f0:0a01) at work which I have connected to my Debian Squeeze box to scan some pages (I was tired of having to scan under Windows where the scanner usually is connected at my work place). Anyway, since this scanner is not yet fully supported by SANE, I have decided to test as much as possible and report the results since the SANE backend listing at [1] still lists the scanner as Untested. Basically, the scanner works perfectly when scanning lineart or greyscale which is I what I need most of the time to scan documents. However, only scans with 300 dpi work fine, all other resolutions either produce scrambled results (50, 100, 600 dpi) or don't work at all (75, 150, 1200 dpi), error message Invalid argument. I have made several test scans and uploaded the results into a folder at the university, please find them here [2]. I am also going to place a reference scan at 300dpi, color with the Windows software since scanning color images with SANE results in errorneous colors. Since scanning documents with lineart and greyscale at 300dpi works flawlessly, the status of this scanner should be changed to Basic. Thus: Resolution Color Mode Works? 50 line artscrambled output 50 grey scale scrambled ouput 50 color scrambled output 75 line artNO, (Invalid argument) 75 grey scale NO, (Invalid argument) 75 color NO, (Invalid argument) 100 line artscrambled output 100 grey scale scrambled output 100 color scrambled output 150 line artNO, (Invalid argument) 150 grey scale NO, (Invalid argument) 150 color NO, (Invalid argument) 300 line artYES, output OK 300 grey scale YES, output OK 300 color YES, but wrong colors 600 line artscrambled output 600 grey scale scrambled output 600 color NO, scan takes forever All scans were made with 8 bit depth. Results were the same for 16 bit depth. I wasn't sure which debug information to provide, so I just paste the verbose of scanimage and sane-find-scanner. If you need anything else, please let me know. Adrian [1] http://www.sane-project.org/sane-mfgs.html [2] http://www.fys.uio.no/~adriang/scanjet-g2410/ Other debug output: [glaubitz at sulphur:~]$ sane-find-scanner |grep found\ USB found USB scanner (vendor=0x03f0 [Hewlett-Packard], product=0x0a01 [hp scanjet scanner], chip=GL646_HP?) at libusb:002:015 [glaubitz at sulphur:~]$ scanimage -vvv | pnmtopng scanimage_testscan.png [genesys] WARNING: Your scanner is not fully supported or at least [genesys] had only limited testing. Please be careful and [genesys] report any failure/success to [genesys] sane-devel at lists.alioth.debian.org. Please provide as many [genesys] details as possible, e.g. the exact name of your [genesys] scanner and what does (not) work. scanimage: scanning image of size 2549x3510 pixels at 8 bits/pixel scanimage: acquiring gray frame scanimage: min/max graylevel value = 0/255 scanimage: read 8946990 bytes in total Closing device Calling sane_exit scanimage: finished pnmtopng: 255 colors found
[sane-devel] plustek opticpro st28, genesys backend
Could someone please give some advice on scanners in genesys backend? I own a Plustek OpticPro ST28, and so, for it to work in SANE, I would have to program GL841 ASIC, L6219 motor controller, Sony ILX 569 CCD and WM8196 digitizer (this latter I'm unsure of and would have to re-check). I'd like to have some model for my work on ST28. Are there any GL84* scanners in genesys backend, which use this motor controller and already work (or at least move the caret correctly)? In my previous attempts, I was able to either lock the caret (and so had to open the scanner and unlock), or to move the caret by very small steps. Yury
[sane-devel] diffs sent to support MP810, MP960, Canoscan 9000F
I checked that it currently compiles with gcc 4.4.3, but this statement gies a warning message telling %llu is not supported. If this is not advisable to leave PRIu64 here, for compatibility with all systems, then we will need to remove it. Nicolas Le lundi 17 janvier 2011 ? 02:17 +0900, Gernot Hassenpflug a ?crit : On Sun, Jan 16, 2011 at 7:58 PM, m. allan noah kitno455 at gmail.com wrote: Is PRlu64 C89? If not, you will have to drop that change. Someday sane will use C99 :) Hi Allan, Nicolas already added the PRIu64 to the pixma backend, so I guess it is okay. I think it is C90, but have not checked myself. Regards, Gernot -- sane-devel mailing list: sane-devel at lists.alioth.debian.org http://lists.alioth.debian.org/mailman/listinfo/sane-devel Unsubscribe: Send mail with subject unsubscribe your_password to sane-devel-request at lists.alioth.debian.org
[sane-devel] Test report of HP ScanJet G2410 (genesys)
On Jan 16, 2011, at 3:21 PM, Adrian Glaubitz wrote: I have made several test scans and uploaded the results into a folder at the university, please find them here [2]. I am also going to place a reference scan at 300dpi, color with the Windows software since scanning color images with SANE results in errorneous colors. I showed the resulting color image (color_300dpi.tif) to a friend of mine, and he quickly figured out that the colors are fixed by interchanging the blue and red channels and by shifting the red color layer 8 pixels downwards and the blue layer 8 pixels upwards. The shifting of the channels to be performed after swapping blue and red channels. The resulting image can be found here after swapping the channels and correcting their offset of color_300dpi.tif: http://www.fys.uio.no/~adriang/scanjet-g2410/color-fixed.png Adrian
[sane-devel] problem with canoscan 5600F
Any progress on this front yet? I have a Canoscan 5600F too and unfortunately it won't work in Ubuntu 10.10. Any help would be greatly appreciated. Thanks! -- Avinash stef-22 wrote: Le Wednesday 15 September 2010 13:40:38 Denis Jallat, vous avez ?crit : I have a canoscan 5600 too and the same problem as Catelin (probalely the same problem or an identical problem); I contacted stef and I gave him data so he can identify the problem. Denis Jallat (excuse my english) Hello, the usbsnoop you sent gave lots of useful information. First the analog frontend used is different form the LiDE 100 and 200. Then the 5600f is using a CCD sensor while only CIS sensor are currently supported for gl847. I'll come up with a test patch, but real development can only be done when having the device to test. Maybe you or David may have a try at it and I would assist you. Since motor seems to work alright, what is left is some modification for CCD and analog frontend. There is already existing code for the gl841/gl843 parts which can be a good basis. In fact the most tedious is testing. Regards, Stef -- sane-devel mailing list: sane-devel at lists.alioth.debian.org http://lists.alioth.debian.org/mailman/listinfo/sane-devel Unsubscribe: Send mail with subject unsubscribe your_password to sane-devel-request at lists.alioth.debian.org -- View this message in context: http://old.nabble.com/problem-with-canoscan-5600F-tp29245455p30676166.html Sent from the SANE - Dev mailing list archive at Nabble.com.
[sane-devel] canon_dr and DR-7090C
I've started to test the canon-dr backed with my DR-7090C scanner, with latest snapshot (libsane-canon.so.1.0.22). I'm using xsane V.0.997 and scanimage V.1.0.21. ADF Duplex and ADF Front works fine, as does all of the scanner's supported resolutions, and Color/Grey/Halftone/Lineart. I'm fortunate that ADF Front and ADF Duplex is working, but neither xsane nor scanimage provides a Flatbed option. I have included a list of all scanimage options detected. There is no flatbed option. == root at borg:/tmp# scanimage --help -d canon_dr:libusb:001:007 Usage: scanimage [OPTION]... Start image acquisition on a scanner device and write image data to standard output. Parameters are separated by a blank from single-character options (e.g. -d epson) and by a = from multi-character options (e.g. --device-name=epson). -d, --device-name=DEVICE use a given scanner device (e.g. hp:/dev/scanner) --format=pnm|tiff file format of output file -i, --icc-profile=PROFILE include this ICC profile into TIFF file -L, --list-devices show available scanner devices -f, --formatted-device-list=FORMAT similar to -L, but the FORMAT of the output can be specified: %d (device name), %v (vendor), %m (model), %t (type), %i (index number), and %n (newline) -b, --batch[=FORMAT] working in batch mode, FORMAT is `out%d.pnm' or `out%d.tif' by default depending on --format --batch-start=#page number to start naming files with --batch-count=#how many pages to scan in batch mode --batch-increment=#increase page number in filename by # --batch-double increment page number by two, same as --batch-increment=2 --batch-prompt ask for pressing a key before scanning a page --accept-md5-only only accept authorization requests using md5 -p, --progress print progress messages -n, --dont-scanonly set options, don't actually scan -T, --test test backend thoroughly -h, --help display this help message and exit -v, --verbose give even more status messages -B, --buffer-size=#change input buffer size (in kB, default 32) -V, --version print version information Options specific to device `canon_dr:libusb:001:007': Standard: --source ADF Front|ADF Duplex [ADF Front] Selects the scan source (such as a document-feeder). --mode Lineart|Halftone|Gray|Color [Lineart] Selects the scan mode (e.g., lineart, monochrome, or color). --resolution 100|150|200|240|300|400|600dpi [600] Sets the resolution of the scanned image. Geometry: -l 0..215.872mm (in steps of 0.0211639) [0] Top-left x position of scan area. -t 0..279.364mm (in steps of 0.0211639) [0] Top-left y position of scan area. -x 0..215.872mm (in steps of 0.0211639) [215.872] Width of scan-area. -y 0..279.364mm (in steps of 0.0211639) [279.364] Height of scan-area. --page-width 0..298.158mm (in steps of 0.0211639) [215.872] Specifies the width of the media. Required for automatic centering of sheet-fed scans. --page-height 0..431.744mm (in steps of 0.0211639) [279.364] Specifies the height of the media. Enhancement: --brightness -127..127 (in steps of 1) [0] Controls the brightness of the acquired image. --contrast -127..127 (in steps of 1) [0] Controls the contrast of the acquired image. --threshold 0..255 (in steps of 1) [90] Select minimum-brightness to get a white point Advanced: --df-thickness[=(yes|no)] [no] Detect double feeds using thickness sensor --df-length[=(yes|no)] [no] Detect double feeds by comparing document lengths --rollerdeskew[=(yes|no)] [no] Request scanner to correct skewed pages mechanically --swdeskew[=(yes|no)] [no] Request driver to rotate skewed pages digitally --swdespeck 0..9 (in steps of 1) [0] Maximum diameter of lone dots to remove from scan --swcrop[=(yes|no)] [no] Request driver to remove border from pages digitally --stapledetect[=(yes|no)] [no] Request scanner to halt if stapled pages are detected --dropout-front None|Red|Green|Blue|Enhance Red|Enhance Green|Enhance Blue [None] One-pass scanners use only one color during gray or binary scanning, useful for colored paper or ink --dropout-back None|Red|Green|Blue|Enhance Red|Enhance Green|Enhance Blue [None] One-pass scanners use only one color during gray or binary scanning, useful for colored paper or ink --buffermode[=(yes|no)] [no] Request scanner to read pages async into internal memory --side[=(yes|no)] [no] [read-only] Tells which side (0=front, 1=back) of a duplex scan
No subject
the backend but with the USB layer. [1] http://lists.alioth.debian.org/pipermail/sane-devel/2011-January/028060.html [2] http://lists.alioth.debian.org/pipermail/sane-devel/2011-January/028091.html Hope this helps, -- Olaf Meeuwissen, LPIC-2 FLOSS Engineer -- AVASYS CORPORATION FSF Associate Member #1962 Help support software freedom http://www.fsf.org/jf?referrer=1962
No subject
0x0090
No subject
This is sane-find-scanner from sane-backends 1.0.21 # sane-find-scanner will now attempt to detect your scanner. If the # result is different from what you expected, first make sure your # scanner is powered up and properly connected to your computer. searching for SCSI scanners: checking /dev/scanner... failed to open (Invalid argument) checking /dev/sg0... failed to open (Access to resource has been denied) checking /dev/sg1... failed to open (Access to resource has been denied) checking /dev/sg2... failed to open (Access to resource has been denied) checking /dev/sg3... failed to open (Invalid argument) checking /dev/sg4... failed to open (Invalid argument) checking /dev/sg5... failed to open (Invalid argument) checking /dev/sg6... failed to open (Invalid argument) checking /dev/sg7... failed to open (Invalid argument) checking /dev/sg8... failed to open (Invalid argument) checking /dev/sg9... failed to open (Invalid argument) checking /dev/sga... failed to open (Invalid argument) checking /dev/sgb... failed to open (Invalid argument) checking /dev/sgc... failed to open (Invalid argument) checking /dev/sgd... failed to open (Invalid argument) checking /dev/sge... failed to open (Invalid argument) checking /dev/sgf... failed to open (Invalid argument) checking /dev/sgg... failed to open (Invalid argument) checking /dev/sgh... failed to open (Invalid argument) checking /dev/sgi... failed to open (Invalid argument) checking /dev/sgj... failed to open (Invalid argument) checking /dev/sgk... failed to open (Invalid argument) checking /dev/sgl... failed to open (Invalid argument) checking /dev/sgm... failed to open (Invalid argument) checking /dev/sgn... failed to open (Invalid argument) checking /dev/sgo... failed to open (Invalid argument) checking /dev/sgp... failed to open (Invalid argument) checking /dev/sgq... failed to open (Invalid argument) checking /dev/sgr... failed to open (Invalid argument) checking /dev/sgs... failed to open (Invalid argument) checking /dev/sgt... failed to open (Invalid argument) checking /dev/sgu... failed to open (Invalid argument) checking /dev/sgv... failed to open (Invalid argument) checking /dev/sgw... failed to open (Invalid argument) checking /dev/sgx... failed to open (Invalid argument) checking /dev/sgy... failed to open (Invalid argument) checking /dev/sgz... failed to open (Invalid argument) # No SCSI scanners found. If you expected something different, make sure that # you have loaded a kernel SCSI driver for your SCSI adapter. searching for USB scanners: checking /dev/usb/scanner... failed to open (Invalid argument) checking /dev/usb/scanner0... failed to open (Invalid argument) checking /dev/usb/scanner1... failed to open (Invalid argument) checking /dev/usb/scanner2... failed to open (Invalid argument) checking /dev/usb/scanner3... failed to open (Invalid argument) checking /dev/usb/scanner4... failed to open (Invalid argument) checking /dev/usb/scanner5... failed to open (Invalid argument) checking /dev/usb/scanner5... failed to open (Invalid argument) checking /dev/usb/scanner7... failed to open (Invalid argument) checking /dev/usb/scanner8... failed to open (Invalid argument) checking /dev/usb/scanner9... failed to open (Invalid argument) checking /dev/usb/scanner10... failed to open (Invalid argument) checking /dev/usb/scanner11... failed to open (Invalid argument) checking /dev/usb/scanner12... failed to open (Invalid argument) checking /dev/usb/scanner13... failed to open (Invalid argument) checking /dev/usb/scanner14... failed to open (Invalid argument) checking /dev/usb/scanner15... failed to open (Invalid argument) checking /dev/usbscanner... failed to open (Invalid argument) checking /dev/usbscanner0... failed to open (Invalid argument) checking /dev/usbscanner1... failed to open (Invalid argument) checking /dev/usbscanner2... failed to open (Invalid argument) checking /dev/usbscanner3... failed to open (Invalid argument) checking /dev/usbscanner4... failed to open (Invalid argument) checking /dev/usbscanner5... failed to open (Invalid argument) checking /dev/usbscanner6... failed to open (Invalid argument) checking /dev/usbscanner7... failed to open (Invalid argument) checking /dev/usbscanner8... failed to open (Invalid argument) checking /dev/usbscanner9... failed to open (Invalid argument) checking /dev/usbscanner10... failed to open (Invalid argument) checking /dev/usbscanner11... failed to open (Invalid argument) checking /dev/usbscanner12... failed to open (Invalid argument) checking /dev/usbscanner13... failed to open (Invalid argument) checking /dev/usbscanner14... failed to open (Invalid argument) checking /dev/usbscanner15... failed to open (Invalid argument) trying libusb: device descriptor of 0x1d6b/0x0001 at 008:001 bLength 18 bDescriptorType 1 bcdUSB1.10 bDeviceClass 9 bDeviceSubClass 0 bDeviceProtocol 0 bMaxPacketSize0 64 idVendor
No subject
When I use the following command, that is Legal size (8.5 X 14) scanimage --source ADF --mode Gray --format=pdf -l 0 -t 0 -x 216 -y 356 --resolution 150 image.pdf It show me this error output: [hp5590] Top Y (0) + pixels Y (2102) exceedes max Y 1758 scanimage: sane_start: Invalid argument I use xsane as frontend: sane1.0.14-9 libsane 1.0.20-13ubuntu2 xsane 0.996-2ubuntu3 Ubunt Hardy Heron 8.04 Let me know, if you need the debug log. Thanks in advance.
No subject
When I use the following command, that is Legal size (8.5 X 14) scanimage --source ADF --mode Gray --format=pdf -l 0 -t 0 -x 216 -y 356 --resolution 150 image.pdf It show me this error output: [hp5590] Top Y (0) + pixels Y (2102) exceedes max Y 1758 scanimage: sane_start: Invalid argument I use xsane as frontend: sane1.0.14-9 libsane 1.0.20-13ubuntu2 xsane 0.996-2ubuntu3 Ubunt Hardy Heron 8.04 I Have the debug log too. Thanks in advance.
