[sane-devel] Canon LiDE 50 not working on recently installed Debian Lenny

Well it sounded like the scanner started; it made two short scanning sounds, then this message: h# scanimage > test.pnm scanimage: sane_start: Invalid argument On Mon, October 26, 2009 9:04 am, m. allan noah wrote: > sure looks like it is found. what does > > scanimage > test.pnm > > do? > > all

[sane-devel] Unknown SANE status code -1081075667

run >> the >> >>> >> >> command i gave you." >> >>> >> >> >> >>> >> >> Does not work. I am using Windows XP and after executing the >> >>> command, >> >>> >> the >> >>> >> >> log is empty. >> >>> >> >> Command I used: >> >>> >> >> C:\sane\bin>xsane 2>net.log >> >>> >> > >> >>> >> > ahh- somewhere along the way you should have mentioned that >> windows >> >>> >> > was involved. You might try asking the author of xsane... >> >>> >> > >> >>> >> >> "SANE_DEBUG_NET=10" Where do I have to execute this command? It >> > only >> >>> >> works >> >>> >> >> on my router. >> >>> >> > >> >>> >> > this sets an enviroment variable in unix, you put it on the same >> >>> >> > command line right before you call the program, just like i typed >> it >> >>> >> > before. >> >>> >> > >> >>> >> >> "what about scanimage on the client machine?" >> >>> >> >> Works! >> >>> >> >> >> >>> >> >> "if you maintain the package, you should know how to modify the >> .bb >> >>> >> >> file to add arguments to the gcc call. Something like >> CFLAGS="-Wall >> >>> >> >> -Werror" >> >>> >> >> Yes, no problem to set the flags, but I did not understand what >> >>> effect >> >>> >> it >> >>> >> >> will have. Is this option for debugging or to solve the problem >> >>> after >> >>> >> >> compiling? >> >>> >> > >> >>> >> > the -W options to gcc make it give more warnings at compile time. >> > you >> >>> >> > will have to find the bitbake logfile to see the noise. >> >>> >> > >> >>> >> > but frankly, I am now thinking the windows compile of xsane might >> be >> >>> >> > part of the problem. The easiest way to know would be for you to >> >>> >> > install a real OS on your machine (i.e. Linux, perhaps in a VM), >> and >> >>> >> > make sure that you can scan over the network. >> >>> >> > >> >>> >> > allan >> >>> >> > >> >>> >> >> >> >>> >> >> Regards >> >>> >> >> Oliver >> >>> >> >> >> >>> >> >> >> >>> >> >> >> >>> >> >> >> >>> >> >> -Urspr?ngliche Nachricht- >> >>> >> >> Von: m. allan noah [mailto:kitno455 at gmail.com] >> >>> >> >> Gesendet: Dienstag, 20. Oktober 2009 14:41 >> >>> >> >> An: carterbueford at gmx.net >> >>> >> >> Cc: Olaf Meeuwissen; sane-devel at lists.alioth.debian.org >> >>> >> >> Betreff: Re: [sane-devel] Unknown SANE status code -1081075667 >> >>> >> >> >> >>> >> >> On Tue, Oct 20, 2009 at 2:49 AM, ? >> wrote: >> >>> >> >>> Hi, >> >>> >> >>> >> >>> >> >>> @allan: I do not run xsane on the same mashine like the >> >>> sane-server, >> >>> >> so I >> >>> >> >> do not understand how to write the log you want me to. >> >>> >> >>> "xsane... 2>net.log" >> >>> >> >> >> >>> >> >> easy, open a terminal window on the scanning client, and run the >> >>> >> >> command i gave you. >> >>> >> >> >> >>> >> >>> sanimage on the mashine where the sane-server runs, works fine. >> >>> >> >> >> >>> >> >> what about scanimage on the client machine? >> >>> >> >> >> >>> >> >> Tthere are three likely sources for this error: >> >>> >> >> >> >>> >> >> 1. xsane makes different API calls than scanimage, and triggers >> a >> >>> bug >> >>> >> in >> >>> >> >> epson2 >> >>> >> >> 2. net backend munges the data >> >>> >> >> 3. saned munges the data >> >>> >> >> >> >>> >> >>> @Olaf:"Compile the backend with gcc -Wall -Werror should give a >> >>> >> cluebat." >> >>> >> >> What is meant by that? >> >>> >> >>> I'm using the optware package, so it is not compiled on my >> router. >> >>> I >> >>> >> am >> >>> >> >> maintainer of the package, so I can patch it to be compiled in a >> >>> >> different >> >>> >> >> way, but how? >> >>> >> >> >> >>> >> >> if you maintain the package, you should know how to modify the >> .bb >> >>> >> >> file to add arguments to the gcc call. Something like >> CFLAGS="-Wall >> >>> >> >> -Werror" >> >>> >> >> >> >>> >> >> bitbake puts its compilation output someplace funny, you'll have >> to >> >>> >> >> look for the log... >> >>> >> >> >> >>> >> >> allan >> >>> >> >> -- >> >>> >> >> "The truth is an offense, but not a sin" >> >>> >> >> >> >>> >> >> >> >>> >> > >> >>> >> > >> >>> >> > >> >>> >> > -- >> >>> >> > "The truth is an offense, but not a sin" >> >>> >> > >> >>> >> > >> >>> >> >> >>> >> >> >>> >> >> >>> >> -- >> >>> >> "The truth is an offense, but not a sin" >> >>> > >> >>> > -- >> >>> > Jetzt kostenlos herunterladen: Internet Explorer 8 und Mozilla >> Firefox >> >>> 3.5 - >> >>> > sicherer, schneller und einfacher! >> > http://portal.gmx.net/de/go/chbrowser >> >>> > >> >>> >> >>> >> >>> >> >>> -- >> >>> "The truth is an offense, but not a sin" >> >> >> >> -- >> >> Neu: GMX DSL bis 50.000 kBit/s und 200,- Euro Startguthaben! >> >> http://portal.gmx.net/de/go/dsl02 >> >> >> > >> > >> > >> > -- >> > "The truth is an offense, but not a sin" >> > >> >> >> >> -- >> "The truth is an offense, but not a sin" > > -- > Jetzt kostenlos herunterladen: Internet Explorer 8 und Mozilla Firefox 3.5 - > sicherer, schneller und einfacher! http://portal.gmx.net/de/go/atbrowser > -- "The truth is an offense, but not a sin" -- next part -- An embedded and charset-unspecified text was scrubbed... Name: epson2.txt URL: <http://lists.alioth.debian.org/pipermail/sane-devel/attachments/20091026/317b756b/attachment-0001.txt>

[sane-devel] Unknown SANE status code -1081075667

Hi at all, I've got the following error trying to scan with my Epson Stylus Photo RX640 over XSane. >> >> [sanei_debug] Setting debug level of epson2 to 128. >> >> [epson2] sane_epson2_init: sane-backends 1.0.19 >> >> [epson2] sane_epson2_init: reading config file, epson2.conf >> >> [epson2] scs

[sane-devel] Unknown SANE status code -1081075667

On Mon, Oct 26, 2009 at 1:12 PM, wrote: > Hi at all, > > I've got the following error trying to scan with my Epson Stylus Photo RX640 > over XSane. > >>> >> [sanei_debug] Setting debug level of epson2 to 128. >>> >> [epson2] sane_epson2_init: sane-backends 1.0.19 >>> >> [epson2] sane_epson2_init:

[sane-devel] Canon LiDE 50 not working on recently installed Debian Lenny

On Mon, Oct 26, 2009 at 4:45 AM, wrote: > Well it sounded like the scanner started; it made two short scanning > sounds, then this message: > > h# scanimage > test.pnm > scanimage: sane_start: Invalid argument > well, that is something better- does this thing have a physical carriage lock on th

[sane-devel] Canon LiDE 50 not working on recently installed Debian Lenny

Thank you for your help, Allan. Here is the output to the recommended command: h# SANE_DEBUG_GENESYS=255 scanimage -L [sanei_debug] Setting debug level of genesys to 255. [genesys] SANE Genesys backend version 1.0 build 9 from sane-backends 1.0.19 [genesys] sane_init: authorize != null [genesys]