[sane-devel] unclear error message
On 07/08/2011 11:20 PM, m. allan noah wrote: > Actually, it might have worked under 1.0.20 and 1.0.22, but been > broken under 1.0.21. > > allan > I guess so. Anyhow, thanks very much to all who replied so quickly Jeremy
[sane-devel] unclear error message
On 07/08/2011 11:06 PM, Richard Ryniker wrote: > You might try an update to 1.0.22, which is in the Fedora 14 "updates" > repository. Either use "yum update" for a general update of your Fedora > system, or "yum update sane-backends" to update just that. > > Alternatively (if your machine has no Internet access) retrieve just the > sane-backends package from: > > > http://download.fedoraproject.org/pub/fedora/linux/updates/14/i386/sane-backends-1.0.22-3.fc14.i686.rpm > > and copy it for local installation on the subject system. > > I expect the SANE maintainers would prefer to diagnose a problem on the > latest version, instead of 1.0.21. > > Seems to work now! Surprise, as I had the scanner working under Ubuntu a year or so ago, long before Fedora 14 arrived, so I didn't think of the possibility that the problem would be due to having old software. Anyway, it works now - thanks very much Jeremy
[sane-devel] unclear error message
On 07/08/2011 10:18 PM, m. allan noah wrote: > What version of sane-backends is this? > > allan This is running on Fedora 14, package name is [jeremy at home2006 ~]$ rpm -q sane-backends sane-backends-1.0.21-3.fc14.i686 hope this includes the info you want - or this looks as though it should do so [jeremy at home2006 ~]$ scanimage -V scanimage (sane-backends) 1.0.21; backend version 1.0.21 Cheers, Jeremy
[sane-devel] unclear error message
On 07/08/2011 08:12 PM, Olaf Meeuwissen wrote: > Jeremy Dawson writes: > >> The equipment is EPSON-Stylus-CX5300 (according to the Printing tool), >> but I get >> [jeremy at home2006 ~]$ scanimage -L >> device `epson2:libusb:003:002' is a Epson CX5400 flatbed scanner > > For SANE backend purposes these are the same. > >> Here is exactly what I did with scanimage: >> >> [jeremy at home2006 ~]$ scanimage>image.pnm >> scanimage: sane_start: Invalid argument >> >> [jeremy at home2006 ~]$ scanimage -d epson2:libusb:003:002>image.pnm >> scanimage: sane_start: Invalid argument > > Not sure whether this is still an issue, but have you tried specifying a > resolution? The CX5300 should be able to do 100 but check the output of > scanimage -h for the `--resolution` option for details. > I tried this - no difference [jeremy at home2006 ~]$ scanimage >a.pnm scanimage: sane_start: Invalid argument [jeremy at home2006 ~]$ scanimage --resolution 100 >b.pnm scanimage: sane_start: Invalid argument > There was a time where the default resolution of 300 wasn't checked > against what the device could actually do. > >> I can't think of any further relevant details but happy to provide >> them if I know exactly what further details are required > > The out.log file that results from > >SANE_DEBUG_EPSON2=255 scanimage> out.pnm 2> out.log [jeremy at home2006 ~]$ SANE_DEBUG_EPSON2=255 scanimage > out.pnm 2> out.log [jeremy at home2006 ~]$ ls -l out.log -rw-r--r--. 1 jeremy jeremy 39927 Jul 8 22:16 out.log Output file is attached > > FWIW, Image Scan! for Linux[1] supports this model just fine. Click the > All-in-Ones icon and use your browser's find functionality (Ctrl+F ?) to > locate the CX5300. > > [1] http://avasys.jp/eng/linux_driver/download/ I'm going away for 2 weeks soon (if I'd known I'd get replies so quickly I would have deferred this until I return - thanks for such speedy replies). I'll try this when I return. thanks again, Jeremy > > Hope this helps, -- next part -- An embedded and charset-unspecified text was scrubbed... Name: out.log URL: <http://lists.alioth.debian.org/pipermail/sane-devel/attachments/20110708/02322bb4/attachment-0001.ksh>
[sane-devel] unclear error message
Jeremy Dawson writes: > The equipment is EPSON-Stylus-CX5300 (according to the Printing tool), > but I get > [jeremy at home2006 ~]$ scanimage -L > device `epson2:libusb:003:002' is a Epson CX5400 flatbed scanner For SANE backend purposes these are the same. > Here is exactly what I did with scanimage: > > [jeremy at home2006 ~]$ scanimage >image.pnm > scanimage: sane_start: Invalid argument > > [jeremy at home2006 ~]$ scanimage -d epson2:libusb:003:002 >image.pnm > scanimage: sane_start: Invalid argument Not sure whether this is still an issue, but have you tried specifying a resolution? The CX5300 should be able to do 100 but check the output of scanimage -h for the `--resolution` option for details. There was a time where the default resolution of 300 wasn't checked against what the device could actually do. > I can't think of any further relevant details but happy to provide > them if I know exactly what further details are required The out.log file that results from SANE_DEBUG_EPSON2=255 scanimage > out.pnm 2> out.log FWIW, Image Scan! for Linux[1] supports this model just fine. Click the All-in-Ones icon and use your browser's find functionality (Ctrl+F ?) to locate the CX5300. [1] http://avasys.jp/eng/linux_driver/download/ 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
[sane-devel] sane-find-scanner OK but scanimage -L KO
> Le jeudi 7 juillet 2011 22:56:18 yohann at rebattu.fr, vous avez ?crit : >> Hello all, >> first thank you, you did great work with sane. >> >> then i have a litle problem to make my scanner (lexmark X1150) works >> with >> sane, and more disturbing i can't figure out where things goes wrong. >> >> first as said in documentation i run sane-find-scanner: >> found USB scanner (vendor=0x043d, product=0x007c, chip=rts8858c) at >> libusb:002:006 >> so it looks good. >> >> then i run scanimage -L but it cannot identify my scanner. >> >> Where thing start to get weird is when i'm looking >> /etc/sane.d/lexmark.conf >> i can see the fallowing line: >> # X11xx series >> usb 0x043d 0x007c >> >> Note that it is the same vendor/product number , it mean my scanner >> *should* be identified doesn't it? >> >> one last thing i looked at was: >> /etc/sane.d/dll.conf to be sure lexmark was present and it was. >> >> i don't know if it is important but i'm on archlinux amd64 and my sane >> version is : 1.0.22. >> One last thing: according to this website : >> http://burogu.makotoworkshop.org/index.php?post/2009/07/14/Backend-Sane-et- >> Scanner-Lexmark-2- this scanner worked with version 1.0.21 of sane >> backend. >> >> Cheers >> Yohann Rebattu >> >> PS: as the site said there are somme french in sane people, you'll found >> another description of the problem in french here: >> http://forums.archlinux.fr/topic8683.html >> >> PPS: i'm not used to mailing list so forgive me if i'm doing something >> wrong, but sane website tell it's ok for sane users to post on >> sane-devel. > > Hello, > > there is no 'sane-user' mailing list so this is the right place for such > reports. > Ca you run scanimage with debug messages so I can have more data on the > problem you have ? In a command shell do: > export SANE_DEBUG_LEXMARK=255 > export SANE_DEBUG_LEXMARK_LOW=255 > scanimage -L 2>probe.log > > then send the probe.log file to the list. > > Regards, > Stef > > Thank you for such a quick answer, The debug info from scanimage -L is attached. i dont know much about sane, but apparently lexmark driver is loaded but doesn't recognize my device Yohann -- next part -- A non-text attachment was scrubbed... Name: probe.log Type: text/x-log Size: 840 bytes Desc: not available URL: <http://lists.alioth.debian.org/pipermail/sane-devel/attachments/20110708/388b7f1e/attachment.bin>
[sane-devel] unclear error message
On 07/08/2011 05:30 PM, Torfinn Ingolfsen wrote: > Hi, > > On Fri, Jul 8, 2011 at 9:23 AM, Jeremy Dawson > wrote: >> >> I'm not sure where the query should go - please advise. >> >> Trying to scan something, xsane give the message >> >> Failed to start scanner: Invalid argument >> >> Also scanimage>image.pnm >> give the message >> scanimage: sane_start: Invalid argument >> >> Where do I find the information to determine what is wrong? > > Have you read the documentation? see http://www.sane-project.org/docs.html > > Please provide more detailed information about your equipment and the > problem, so that people are able to help you. > > HTH Thanks for the prompt reply: Thanks for the pointer to the documentation, I've found http://ljm.home.xs4all.nl/SANE-faq.html#50 which looks most nearly relevant but not quite. The equipment is EPSON-Stylus-CX5300 (according to the Printing tool), but I get [jeremy at home2006 ~]$ scanimage -L device `epson2:libusb:003:002' is a Epson CX5400 flatbed scanner Here is exactly what I did with scanimage: [jeremy at home2006 ~]$ scanimage >image.pnm scanimage: sane_start: Invalid argument [jeremy at home2006 ~]$ scanimage -d epson2:libusb:003:002 >image.pnm scanimage: sane_start: Invalid argument In xsane I just started it up and clicked "Scan" I can't think of any further relevant details but happy to provide them if I know exactly what further details are required Thanks, Jeremy Dawson
[sane-devel] unclear error message
I'm not sure where the query should go - please advise. Trying to scan something, xsane give the message Failed to start scanner: Invalid argument Also scanimage >image.pnm give the message scanimage: sane_start: Invalid argument Where do I find the information to determine what is wrong? Regards, Jeremy Dawson
[sane-devel] Fix for infinte for loop
--- /sane-backends-1.0.21/backend/genesys_gl646.c.orig2011-07-08
11:07:05.0 +0200
+++ /sane-backends-1.0.21/backend/genesys_gl646.c 2011-07-08 11:07:47.0
+0200
@@ -3068,9 +3068,10 @@
/* loop until head parked */
if (wait_until_home)
{
- int loop = 0;
+ int loop;
- while (loop < 3) /* do not wait longer then 30 seconds */
+ /* do not wait longer then 30 seconds */
+ for (loop = 0; loop < 300; loop++)
{
status = sanei_genesys_get_status (dev, &val);
if (status != SANE_STATUS_GOOD)
I'm not suscribed to this list. Please keep me CC'ed.
--HPS
[sane-devel] unclear error message
Hi, On Fri, Jul 8, 2011 at 9:23 AM, Jeremy Dawson wrote: > > I'm not sure where the query should go - please advise. > > Trying to scan something, xsane give the message > > Failed to start scanner: Invalid argument > > Also scanimage >image.pnm > give the message > scanimage: sane_start: Invalid argument > > Where do I find the information to determine what is wrong? Have you read the documentation? see http://www.sane-project.org/docs.html Please provide more detailed information about your equipment and the problem, so that people are able to help you. HTH -- Regards, Torfinn Ingolfsen
[sane-devel] unclear error message
Actually, it might have worked under 1.0.20 and 1.0.22, but been broken under 1.0.21. allan On Fri, Jul 8, 2011 at 9:16 AM, Jeremy Dawson wrote: > On 07/08/2011 11:06 PM, Richard Ryniker wrote: >> >> You might try an update to 1.0.22, which is in the Fedora 14 "updates" >> repository. ?Either use "yum update" for a general update of your Fedora >> system, or "yum update sane-backends" to update just that. >> >> Alternatively (if your machine has no Internet access) retrieve just the >> sane-backends package from: >> >> >> http://download.fedoraproject.org/pub/fedora/linux/updates/14/i386/sane-backends-1.0.22-3.fc14.i686.rpm >> >> and copy it for local installation on the subject system. >> >> I expect the SANE maintainers would prefer to diagnose a problem on the >> latest version, instead of 1.0.21. >> >> > > Seems to work now! ?Surprise, as I had the scanner working under Ubuntu a > year or so ago, long before Fedora 14 arrived, so I didn't think of the > possibility that the problem would be due to having old software. > > Anyway, it works now - thanks very much > > Jeremy > -- "The truth is an offense, but not a sin"
[sane-devel] unclear error message
You might try an update to 1.0.22, which is in the Fedora 14 "updates" repository. Either use "yum update" for a general update of your Fedora system, or "yum update sane-backends" to update just that. Alternatively (if your machine has no Internet access) retrieve just the sane-backends package from: http://download.fedoraproject.org/pub/fedora/linux/updates/14/i386/sane-backends-1.0.22-3.fc14.i686.rpm and copy it for local installation on the subject system. I expect the SANE maintainers would prefer to diagnose a problem on the latest version, instead of 1.0.21.
[sane-devel] sane-devel Digest, Vol 73, Issue 7
That works for me. I will head on over shortly so see you in about 1/2 hr. Cheers, Jim On 7/8/2011 8:26 AM, sane-devel-request at lists.alioth.debian.org wrote: > Send sane-devel mailing list submissions to > sane-devel at lists.alioth.debian.org > > To subscribe or unsubscribe via the World Wide Web, visit > http://lists.alioth.debian.org/cgi-bin/mailman/listinfo/sane-devel > or, via email, send a message with subject or body 'help' to > sane-devel-request at lists.alioth.debian.org > > You can reach the person managing the list at > sane-devel-owner at lists.alioth.debian.org > > When replying, please edit your Subject line so it is more specific > than "Re: Contents of sane-devel digest..." > > > Today's Topics: > > 1. Re: unclear error message (m. allan noah) > 2. Fix for infinte for loop (Hans Petter Selasky) > 3. Re: unclear error message (Jeremy Dawson) > > > -- > > Message: 1 > Date: Fri, 8 Jul 2011 08:18:46 -0400 > From: "m. allan noah" > To: Jeremy Dawson > Cc: sane-devel at lists.alioth.debian.org > Subject: Re: [sane-devel] unclear error message > Message-ID: > > Content-Type: text/plain; charset=ISO-8859-1 > > What version of sane-backends is this? > > allan
[sane-devel] unclear error message
What version of sane-backends is this? allan -- "The truth is an offense, but not a sin"
[sane-devel] sane-find-scanner OK but scanimage -L KO
Le jeudi 7 juillet 2011 22:56:18 yohann at rebattu.fr, vous avez ?crit : > Hello all, > first thank you, you did great work with sane. > > then i have a litle problem to make my scanner (lexmark X1150) works with > sane, and more disturbing i can't figure out where things goes wrong. > > first as said in documentation i run sane-find-scanner: > found USB scanner (vendor=0x043d, product=0x007c, chip=rts8858c) at > libusb:002:006 > so it looks good. > > then i run scanimage -L but it cannot identify my scanner. > > Where thing start to get weird is when i'm looking /etc/sane.d/lexmark.conf > i can see the fallowing line: > # X11xx series > usb 0x043d 0x007c > > Note that it is the same vendor/product number , it mean my scanner > *should* be identified doesn't it? > > one last thing i looked at was: > /etc/sane.d/dll.conf to be sure lexmark was present and it was. > > i don't know if it is important but i'm on archlinux amd64 and my sane > version is : 1.0.22. > One last thing: according to this website : > http://burogu.makotoworkshop.org/index.php?post/2009/07/14/Backend-Sane-et- > Scanner-Lexmark-2- this scanner worked with version 1.0.21 of sane backend. > > Cheers > Yohann Rebattu > > PS: as the site said there are somme french in sane people, you'll found > another description of the problem in french here: > http://forums.archlinux.fr/topic8683.html > > PPS: i'm not used to mailing list so forgive me if i'm doing something > wrong, but sane website tell it's ok for sane users to post on sane-devel. Hello, there is no 'sane-user' mailing list so this is the right place for such reports. Ca you run scanimage with debug messages so I can have more data on the problem you have ? In a command shell do: export SANE_DEBUG_LEXMARK=255 export SANE_DEBUG_LEXMARK_LOW=255 scanimage -L 2>probe.log then send the probe.log file to the list. Regards, Stef
[sane-devel] VEHO film scanner test application started
I got a VuPoint FS-C1-VP-BX2 and I would like to help, however I don't know to code very well and I am a Linux noob, but if you need a tester count with me. > > lsusb returns: > > ID 05a9:1550 OmniVision Technologies, Inc. VEHO Filmscanner The mine gives the same output. >7660APLWb="CameraSetting\SupportCamera\7660APL\DeviceProperties\VideoProcAmp\ >WhiteBalance"" > Which makes me think that these are settings that need to be set on the >camera (by your software?) Any use? That is a very important one and I wonder if it could be implemented in xsane. In the windows app included in the cd (ArcSoft Photoimpresion in my case). According to the manual, you should always calibrate first the white balance before start the converting process, this is done with the negatives/slide tray outside of the scanner and with a special dialog from the app. > > Strangely, the ".SET" comments also seem to include settings for treating it >as a video camera. Puzzled? > Thats right. Even Windows at the first connection detects the VuPoint as a 5Mpx camera, but after the driver install, it becomes "OVT Scanner"
[sane-devel] Nikon Coolscan IV recognized but fails scanimage with "Invalid argument"
*Hello Allan:* I went by this: from: http://www.sane-project.org/source.html *Linux* Most Linux distributions package SANE with modifications required to support their authentication or permissions systems. We recommend you use the vendor's packages. If you need a more updated version of SANE, be prepared to build from source, and ask on a distro-specific forum for advice. synaptic lists the installed and latest versions as the same sane: installed 1.0.14-9 | latest 1.0.14-9 libsane: 1.0.20-13ubuntu2 | 1.0.20-13ubuntu2 sane utils: 1.0.20-13ubuntu2 | 1.0.20-13ubuntu2 From the backends list (https://alioth.debian.org/frs/?group_id=30186), it appears that the "latest version" is from 2004. Well ... argh ... that's how I learn. I did go ahead and download sources for sane 1.0.22. I compiled and installed it (3 times), had to get supporting files (libusb-dev and libsane), and replug the scanner and restart the machine several times. But ... it is now working well enough. Phew. Thank You, *Mike* On 07/07/2011 10:03 AM, m. allan noah wrote: > Start by upgrading to a current version of sane? > > allan > > On Thu, Jul 7, 2011 at 4:00 PM, Michael Hess wrote: >> I am trying to set up a Nikon Coolscan IV >> under Ubuntu 10.04, kernel: 2.6.32-32-generic >> >> sane-find-scanner >> reports: >> scanner (vendor=0x04b0 [Nikon], product=0x4000 [LS-40 ED]) at >> libusb:005:002 >> >> scanimage --version: >> scanimage (sane-backends) 1.0.20; backend version 1.0.20 >> >> scanimage -L: >> device `coolscan3:usb:libusb:005:002' is a Nikon LS-40 ED film scanner >> >> But when I do a test via >> scanimage -T >> I get a: >> scanimage: open of device coolscan3:usb:libusb:005:002 failed: Invalid >> argument >> >> It didn'tt matter what other options I tried setting with scanimage. >> >> I am assuming this is an "obvious" error to somebody, but I could not find >> anything >> to help me resolve this. Any pointers as to what may be going on or where to >> look next? >> >> Thank You, >> >> Mike >> >> >> >> >> -- >> sane-devel mailing list:sane-devel at lists.alioth.debian.org >> http://lists.alioth.debian.org/cgi-bin/mailman/listinfo/sane-devel >> Unsubscribe: Send mail with subject "unsubscribe your_password" >> tosane-devel-request at lists.alioth.debian.org >> -- next part -- An HTML attachment was scrubbed... URL: <http://lists.alioth.debian.org/pipermail/sane-devel/attachments/20110708/8c3de116/attachment.html>
