Re: [sane-devel] Weird behavior in exagear.
Thank you so much for helping me trouble shoot all this. They supposedly have the source code for the driver so I will see if I can compile that and see if I can find the issue with it. Although I'm not so sure how it is suppose to work. It is interesting it gets most of the image and stops near 90+% On Fri, Jan 12, 2018 at 10:13 PM, Jeff Sadowskiwrote: > I tried on my laptop to make sure it wasn't something in exagear and I > got the same results. So I am sure there is a problem with the driver. > > On Fri, Jan 12, 2018 at 6:55 PM, Olaf Meeuwissen > wrote: >> Hi Jeff, >> >> Jeff Sadowski writes: >> >>> My code is simply calling scanimage the way I posted here already. >>> Running the same commands by hand results in the same behaviour. I >>> have my code write the command it runs in a file called ran.txt, so I >>> can examine it and run it. I'm just using php to open a 3 pipe method >>> of running scanimage. it is actually running it under "script" which >>> allows scanimage to continually write to stdout/stderr without >>> blocking which gets written to a stdout.txt and stderr.txt files. I >>> also implemented the ability to send ctrl-c using the 3rd input pipe. >>> So if my loop that is reading the pipes sees that a certain file >>> exists and is still running it will send a ctrl-c. My frontend starts >>> this php script and detaches and then reads it's output files to see >>> what is going on it also continually loads the image being created by >>> scanimage. I get the latest page number from stdout.txt/stderr.txt and >>> the name of the file from my rant.txt looking for '--batch= and the >>> matching quote and replace all %d with the last page number and then I >>> have my image retrieve send that file. :-) >> >> I see. So you're just layering on top of scanimage. I thought you we >> using a PHP layer on top of the SANE C API. Sorry for overthinking >> things. The image acquisition logic in scanimage is correct so the >> problem appears to be in the brother backend. >> >> Sorry for the detour, >> -- >> Olaf Meeuwissen, LPIC-2FSF Associate Member since 2004-01-27 >> GnuPG key: F84A2DD9/B3C0 2F47 EA19 64F4 9F13 F43E B8A4 A88A F84A 2DD9 >> Support Free Softwarehttps://my.fsf.org/donate >> Join the Free Software Foundation https://my.fsf.org/join -- sane-devel mailing list: sane-devel@lists.alioth.debian.org http://lists.alioth.debian.org/cgi-bin/mailman/listinfo/sane-devel Unsubscribe: Send mail with subject "unsubscribe your_password" to sane-devel-requ...@lists.alioth.debian.org
Re: [sane-devel] Weird behavior in exagear.
I tried on my laptop to make sure it wasn't something in exagear and I got the same results. So I am sure there is a problem with the driver. On Fri, Jan 12, 2018 at 6:55 PM, Olaf Meeuwissenwrote: > Hi Jeff, > > Jeff Sadowski writes: > >> My code is simply calling scanimage the way I posted here already. >> Running the same commands by hand results in the same behaviour. I >> have my code write the command it runs in a file called ran.txt, so I >> can examine it and run it. I'm just using php to open a 3 pipe method >> of running scanimage. it is actually running it under "script" which >> allows scanimage to continually write to stdout/stderr without >> blocking which gets written to a stdout.txt and stderr.txt files. I >> also implemented the ability to send ctrl-c using the 3rd input pipe. >> So if my loop that is reading the pipes sees that a certain file >> exists and is still running it will send a ctrl-c. My frontend starts >> this php script and detaches and then reads it's output files to see >> what is going on it also continually loads the image being created by >> scanimage. I get the latest page number from stdout.txt/stderr.txt and >> the name of the file from my rant.txt looking for '--batch= and the >> matching quote and replace all %d with the last page number and then I >> have my image retrieve send that file. :-) > > I see. So you're just layering on top of scanimage. I thought you we > using a PHP layer on top of the SANE C API. Sorry for overthinking > things. The image acquisition logic in scanimage is correct so the > problem appears to be in the brother backend. > > Sorry for the detour, > -- > Olaf Meeuwissen, LPIC-2FSF Associate Member since 2004-01-27 > GnuPG key: F84A2DD9/B3C0 2F47 EA19 64F4 9F13 F43E B8A4 A88A F84A 2DD9 > Support Free Softwarehttps://my.fsf.org/donate > Join the Free Software Foundation https://my.fsf.org/join -- sane-devel mailing list: sane-devel@lists.alioth.debian.org http://lists.alioth.debian.org/cgi-bin/mailman/listinfo/sane-devel Unsubscribe: Send mail with subject "unsubscribe your_password" to sane-devel-requ...@lists.alioth.debian.org
Re: [sane-devel] Weird behavior in exagear.
Hi Jeff, Jeff Sadowski writes: > My code is simply calling scanimage the way I posted here already. > Running the same commands by hand results in the same behaviour. I > have my code write the command it runs in a file called ran.txt, so I > can examine it and run it. I'm just using php to open a 3 pipe method > of running scanimage. it is actually running it under "script" which > allows scanimage to continually write to stdout/stderr without > blocking which gets written to a stdout.txt and stderr.txt files. I > also implemented the ability to send ctrl-c using the 3rd input pipe. > So if my loop that is reading the pipes sees that a certain file > exists and is still running it will send a ctrl-c. My frontend starts > this php script and detaches and then reads it's output files to see > what is going on it also continually loads the image being created by > scanimage. I get the latest page number from stdout.txt/stderr.txt and > the name of the file from my rant.txt looking for '--batch= and the > matching quote and replace all %d with the last page number and then I > have my image retrieve send that file. :-) I see. So you're just layering on top of scanimage. I thought you we using a PHP layer on top of the SANE C API. Sorry for overthinking things. The image acquisition logic in scanimage is correct so the problem appears to be in the brother backend. Sorry for the detour, -- Olaf Meeuwissen, LPIC-2FSF Associate Member since 2004-01-27 GnuPG key: F84A2DD9/B3C0 2F47 EA19 64F4 9F13 F43E B8A4 A88A F84A 2DD9 Support Free Softwarehttps://my.fsf.org/donate Join the Free Software Foundation https://my.fsf.org/join -- sane-devel mailing list: sane-devel@lists.alioth.debian.org http://lists.alioth.debian.org/cgi-bin/mailman/listinfo/sane-devel Unsubscribe: Send mail with subject "unsubscribe your_password" to sane-devel-requ...@lists.alioth.debian.org
Re: [sane-devel] Weird behavior in exagear.
Response from brother. "Hi Jeff. Any type of sharing feature on a USB model is not supported by brother. Most questions we received for this are of a Microsoft nature, but the same policy applies to other OS's as well. If you are looking to have a machine work on multiple PC's, I recommend looking into a Network model like MFC-J485DW or something from the same series." Hmmm, looks like I need to restate the problem. On Fri, Jan 12, 2018 at 7:55 AM, Jeff Sadowskiwrote: > My code is simply calling scanimage the way I posted here already. > Running the same commands by hand results in the same behaviour. I > have my code write the command it runs in a file called ran.txt, so I > can examine it and run it. I'm just using php to open a 3 pipe method > of running scanimage. it is actually running it under "script" which > allows scanimage to continually write to stdout/stderr without > blocking which gets written to a stdout.txt and stderr.txt files. I > also implemented the ability to send ctrl-c using the 3rd input pipe. > So if my loop that is reading the pipes sees that a certain file > exists and is still running it will send a ctrl-c. My frontend starts > this php script and detaches and then reads it's output files to see > what is going on it also continually loads the image being created by > scanimage. I get the latest page number from stdout.txt/stderr.txt and > the name of the file from my rant.txt looking for '--batch= and the > matching quote and replace all %d with the last page number and then I > have my image retrieve send that file. :-) > > On Fri, Jan 12, 2018 at 4:07 AM, Olaf Meeuwissen > wrote: >> Hi again, >> >> Jeff Sadowski writes: >> >>> uning sane -l -d128 -e I am able to see the following error. >> >> This >> >>> [saned] do_scan: done, status=End of file reached >>> [saned] process_request: waiting for request >>> [saned] process_request: bad status 22 >>> [saned] quit: exiting >> >> is probably due to the error you get on the other end >> >>> scanimage: scanning image of size 1648x2314 pixels at 24 bits/pixel >>> scanimage: acquiring RGB frame >>> Progress:98.8% >>> scanimage: min/max graylevel value = 11/255 >>> Application transferred too few scanlines >> >> which indicates that the image acquisition loop ended prematurely for >> some reason. While saned will happily continue to serve requests, how >> the backend and scanner react to this depends on the scanner's firmware >> and the backend's implementation. It may very well be that the scanner >> expects more read requests and refuses to reply to anything else while >> the backend won't send any of those but instead tries to start a new >> scan in vain. >> >> Based on what you wrote so far, I think this is a bug in the third party >> brother backend you seem to be using. The only people that can help you >> with that are the brother backend developers. There is nothing the SANE >> developers can do about it. >> >> That said, are you sure *your* code is doing the right thing? That is, >> does it read data until sane_read() returns SANE_STATUS_EOF? Or is it >> just reading the number of pixels expected based on the results of a >> sane_get_parameters() before you call sane_start()? The latter is the >> *wrong* way to read image data. >> >> Hope this helps, >> -- >> Olaf Meeuwissen, LPIC-2FSF Associate Member since 2004-01-27 >> GnuPG key: F84A2DD9/B3C0 2F47 EA19 64F4 9F13 F43E B8A4 A88A F84A 2DD9 >> Support Free Softwarehttps://my.fsf.org/donate >> Join the Free Software Foundation https://my.fsf.org/join -- sane-devel mailing list: sane-devel@lists.alioth.debian.org http://lists.alioth.debian.org/cgi-bin/mailman/listinfo/sane-devel Unsubscribe: Send mail with subject "unsubscribe your_password" to sane-devel-requ...@lists.alioth.debian.org
Re: [sane-devel] Weird behavior in exagear.
My code is simply calling scanimage the way I posted here already. Running the same commands by hand results in the same behaviour. I have my code write the command it runs in a file called ran.txt, so I can examine it and run it. I'm just using php to open a 3 pipe method of running scanimage. it is actually running it under "script" which allows scanimage to continually write to stdout/stderr without blocking which gets written to a stdout.txt and stderr.txt files. I also implemented the ability to send ctrl-c using the 3rd input pipe. So if my loop that is reading the pipes sees that a certain file exists and is still running it will send a ctrl-c. My frontend starts this php script and detaches and then reads it's output files to see what is going on it also continually loads the image being created by scanimage. I get the latest page number from stdout.txt/stderr.txt and the name of the file from my rant.txt looking for '--batch= and the matching quote and replace all %d with the last page number and then I have my image retrieve send that file. :-) On Fri, Jan 12, 2018 at 4:07 AM, Olaf Meeuwissenwrote: > Hi again, > > Jeff Sadowski writes: > >> uning sane -l -d128 -e I am able to see the following error. > > This > >> [saned] do_scan: done, status=End of file reached >> [saned] process_request: waiting for request >> [saned] process_request: bad status 22 >> [saned] quit: exiting > > is probably due to the error you get on the other end > >> scanimage: scanning image of size 1648x2314 pixels at 24 bits/pixel >> scanimage: acquiring RGB frame >> Progress:98.8% >> scanimage: min/max graylevel value = 11/255 >> Application transferred too few scanlines > > which indicates that the image acquisition loop ended prematurely for > some reason. While saned will happily continue to serve requests, how > the backend and scanner react to this depends on the scanner's firmware > and the backend's implementation. It may very well be that the scanner > expects more read requests and refuses to reply to anything else while > the backend won't send any of those but instead tries to start a new > scan in vain. > > Based on what you wrote so far, I think this is a bug in the third party > brother backend you seem to be using. The only people that can help you > with that are the brother backend developers. There is nothing the SANE > developers can do about it. > > That said, are you sure *your* code is doing the right thing? That is, > does it read data until sane_read() returns SANE_STATUS_EOF? Or is it > just reading the number of pixels expected based on the results of a > sane_get_parameters() before you call sane_start()? The latter is the > *wrong* way to read image data. > > Hope this helps, > -- > Olaf Meeuwissen, LPIC-2FSF Associate Member since 2004-01-27 > GnuPG key: F84A2DD9/B3C0 2F47 EA19 64F4 9F13 F43E B8A4 A88A F84A 2DD9 > Support Free Softwarehttps://my.fsf.org/donate > Join the Free Software Foundation https://my.fsf.org/join -- sane-devel mailing list: sane-devel@lists.alioth.debian.org http://lists.alioth.debian.org/cgi-bin/mailman/listinfo/sane-devel Unsubscribe: Send mail with subject "unsubscribe your_password" to sane-devel-requ...@lists.alioth.debian.org
Re: [sane-devel] Weird behavior in exagear.
Hi again, Jeff Sadowski writes: > uning sane -l -d128 -e I am able to see the following error. This > [saned] do_scan: done, status=End of file reached > [saned] process_request: waiting for request > [saned] process_request: bad status 22 > [saned] quit: exiting is probably due to the error you get on the other end > scanimage: scanning image of size 1648x2314 pixels at 24 bits/pixel > scanimage: acquiring RGB frame > Progress:98.8% > scanimage: min/max graylevel value = 11/255 > Application transferred too few scanlines which indicates that the image acquisition loop ended prematurely for some reason. While saned will happily continue to serve requests, how the backend and scanner react to this depends on the scanner's firmware and the backend's implementation. It may very well be that the scanner expects more read requests and refuses to reply to anything else while the backend won't send any of those but instead tries to start a new scan in vain. Based on what you wrote so far, I think this is a bug in the third party brother backend you seem to be using. The only people that can help you with that are the brother backend developers. There is nothing the SANE developers can do about it. That said, are you sure *your* code is doing the right thing? That is, does it read data until sane_read() returns SANE_STATUS_EOF? Or is it just reading the number of pixels expected based on the results of a sane_get_parameters() before you call sane_start()? The latter is the *wrong* way to read image data. Hope this helps, -- Olaf Meeuwissen, LPIC-2FSF Associate Member since 2004-01-27 GnuPG key: F84A2DD9/B3C0 2F47 EA19 64F4 9F13 F43E B8A4 A88A F84A 2DD9 Support Free Softwarehttps://my.fsf.org/donate Join the Free Software Foundation https://my.fsf.org/join -- sane-devel mailing list: sane-devel@lists.alioth.debian.org http://lists.alioth.debian.org/cgi-bin/mailman/listinfo/sane-devel Unsubscribe: Send mail with subject "unsubscribe your_password" to sane-devel-requ...@lists.alioth.debian.org
Re: [sane-devel] Weird behavior in exagear.
Hi Jeff, Jeff Sadowski writes: > Progress. I am now able to scan jpeg files :-) Good! > it is odd that -V reports as so > > root@raspberrypi:~/sane/sane-backends:x86$ scanimage -V > scanimage (sane-backends) 1.0.27git; backend version 1.0.24 > > Is this something I should be worried about? > Where would it be getting 1.0.24 This is not something to be worried about. All backends have their own version, independent of the sane-backends version. The epson2 backend for example is at 1.0.124! The scanimage utility gets it version directly from sane-backends, hence 1.0.27git for a development version after 1.0.27. Some backends, and probably third party ones in particular, use the version of the sane-backend's release that they were built against. Hope this clarifies, -- Olaf Meeuwissen, LPIC-2FSF Associate Member since 2004-01-27 GnuPG key: F84A2DD9/B3C0 2F47 EA19 64F4 9F13 F43E B8A4 A88A F84A 2DD9 Support Free Softwarehttps://my.fsf.org/donate Join the Free Software Foundation https://my.fsf.org/join -- sane-devel mailing list: sane-devel@lists.alioth.debian.org http://lists.alioth.debian.org/cgi-bin/mailman/listinfo/sane-devel Unsubscribe: Send mail with subject "unsubscribe your_password" to sane-devel-requ...@lists.alioth.debian.org
Re: [sane-devel] Weird behavior in exagear.
usbreset that I get here allows me to start another scan https://askubuntu.com/questions/645/how-do-you-reset-a-usb-device-from-the-command-line It is just the last bit of the scan that stops. On Thu, Jan 11, 2018 at 1:46 PM, Jeff Sadowskiwrote: > I wonder it it works the same on a true x86 architecture it could be > something with the brother driver. After those messages are generated > the saned program stays running and tries to process other requests. > However I need to reboot for it to start working again. > I should be able to reset the usb port to get it working again somehow. > > > On Thu, Jan 11, 2018 at 12:03 PM, Jeff Sadowski > wrote: >> uning sane -l -d128 -e I am able to see the following error. >> >> root@raspberrypi:~:arm$ saned -l -d128 -e >> >> [saned] do_scan: wrote 8192 bytes to client >> [saned] do_scan: trying to read 8188 bytes from scanner >> [saned] do_scan: read 8188 bytes from scanner >> [saned] do_scan: trying to write 8192 bytes to client >> [saned] do_scan: wrote 8192 bytes to client >> [saned] do_scan: trying to read 8188 bytes from scanner >> [saned] do_scan: read 7488 bytes from scanner >> [saned] do_scan: trying to write 7492 bytes to client >> [saned] do_scan: wrote 7492 bytes to client >> [saned] do_scan: trying to read 696 bytes from scanner >> [saned] do_scan: read 0 bytes from scanner >> [saned] do_scan: status = `End of file reached' >> [saned] do_scan: statuscode `End of file reached' was added to buffer >> [saned] do_scan: trying to write 9 bytes to client >> [saned] do_scan: wrote 9 bytes to client >> [saned] do_scan: done, status=End of file reached >> [saned] process_request: waiting for request >> [saned] process_request: bad status 22 >> [saned] quit: exiting >> >> on the other end I get the following error >> >> scanimage '-v' '-p' '--batch=preview.jpg' '--batch-count' '1' >> '--format' 'jpeg' '-l' '0' '-t' '0' '-x' '215.9' '-y' '355.6' '-d' >> 'net:192.168.1.27:brother2:bus1;dev1' >> scanimage: rounded value of br-x from 215.9 to 215.88 >> scanimage: rounded value of br-y from 355.6 to 355.567 >> Scanning 1 page, incrementing by 1, numbering from 1 >> Scanning page 1 >> scanimage: scanning image of size 1648x2314 pixels at 24 bits/pixel >> scanimage: acquiring RGB frame >> Progress:98.8% >> scanimage: min/max graylevel value = 11/255 >> Application transferred too few scanlines >> >> On Thu, Jan 11, 2018 at 11:33 AM, Jeff Sadowski >> wrote: >>> ah looks like I need the -l flag >>> >>> On Thu, Jan 11, 2018 at 11:21 AM, Jeff Sadowski >>> wrote: Progress. I am now able to scan jpeg files :-) And test out more of my phpsaneng program. My preview worked awesome. I was able to watch the image as it was being scanned. I redid git as recommended in INSTALL.linux apt remove sane sane-utils git clone git://git.debian.org/sane/sane-backends.git ./configure --prefix=/usr --libdir=/usr/lib --sysconfdir=/etc --localstatedir=/var --enable-avahi make make install it is odd that -V reports as so root@raspberrypi:~/sane/sane-backends:x86$ scanimage -V scanimage (sane-backends) 1.0.27git; backend version 1.0.24 Is this something I should be worried about? Where would it be getting 1.0.24 I tried removing all sane files I could find and then make install from my git repo and I still get the same output. Now to try and get saned working saned use to at least connect to the port but now I get nothing root@raspberrypi:~/sane/sane-backends:x86$ saned -d128 root@raspberrypi:~/sane/sane-backends:x86$ root@raspberrypi:~/sane/sane-backends:x86$ saned -d128 -b 192.168.1.27 root@raspberrypi:~/sane/sane-backends:x86$ any suggestions on how to get it to report more? maybe a compile flag to get something from it? On Thu, Jan 11, 2018 at 8:19 AM, Jeff Sadowski wrote: > root@raspberrypi:~:arm$ dpkg -c brscan2-0.2.5-1.i386.deb |grep lib|grep so > -rwxr-xr-x root/root 11444 2009-12-01 18:38 > ./usr/lib/libbrcolm2.so.1.0.0 > -rwxr-xr-x root/root 27912 2009-12-01 18:38 > ./usr/lib/libbrscandec2.so.1.0.0 > -rwxr-xr-x root/root 94516 2009-12-01 18:38 > ./usr/lib/sane/libsane-brother2.so.1.0.7 > lrwxrwxrwx root/root 0 2009-12-01 18:38 > ./usr/lib/libbrcolm2.so -> /usr/lib/libbrcolm2.so.1 > lrwxrwxrwx root/root 0 2009-12-01 18:38 > ./usr/lib/libbrscandec2.so.1 -> /usr/lib/libbrscandec2.so.1.0.0 > lrwxrwxrwx root/root 0 2009-12-01 18:38 > ./usr/lib/libbrscandec2.so -> /usr/lib/libbrscandec2.so.1 > lrwxrwxrwx root/root 0 2009-12-01 18:38 > ./usr/lib/libbrcolm2.so.1 -> /usr/lib/libbrcolm2.so.1.0.0 > lrwxrwxrwx root/root 0 2009-12-01 18:38 >
Re: [sane-devel] Weird behavior in exagear.
I wonder it it works the same on a true x86 architecture it could be something with the brother driver. After those messages are generated the saned program stays running and tries to process other requests. However I need to reboot for it to start working again. I should be able to reset the usb port to get it working again somehow. On Thu, Jan 11, 2018 at 12:03 PM, Jeff Sadowskiwrote: > uning sane -l -d128 -e I am able to see the following error. > > root@raspberrypi:~:arm$ saned -l -d128 -e > > [saned] do_scan: wrote 8192 bytes to client > [saned] do_scan: trying to read 8188 bytes from scanner > [saned] do_scan: read 8188 bytes from scanner > [saned] do_scan: trying to write 8192 bytes to client > [saned] do_scan: wrote 8192 bytes to client > [saned] do_scan: trying to read 8188 bytes from scanner > [saned] do_scan: read 7488 bytes from scanner > [saned] do_scan: trying to write 7492 bytes to client > [saned] do_scan: wrote 7492 bytes to client > [saned] do_scan: trying to read 696 bytes from scanner > [saned] do_scan: read 0 bytes from scanner > [saned] do_scan: status = `End of file reached' > [saned] do_scan: statuscode `End of file reached' was added to buffer > [saned] do_scan: trying to write 9 bytes to client > [saned] do_scan: wrote 9 bytes to client > [saned] do_scan: done, status=End of file reached > [saned] process_request: waiting for request > [saned] process_request: bad status 22 > [saned] quit: exiting > > on the other end I get the following error > > scanimage '-v' '-p' '--batch=preview.jpg' '--batch-count' '1' > '--format' 'jpeg' '-l' '0' '-t' '0' '-x' '215.9' '-y' '355.6' '-d' > 'net:192.168.1.27:brother2:bus1;dev1' > scanimage: rounded value of br-x from 215.9 to 215.88 > scanimage: rounded value of br-y from 355.6 to 355.567 > Scanning 1 page, incrementing by 1, numbering from 1 > Scanning page 1 > scanimage: scanning image of size 1648x2314 pixels at 24 bits/pixel > scanimage: acquiring RGB frame > Progress:98.8% > scanimage: min/max graylevel value = 11/255 > Application transferred too few scanlines > > On Thu, Jan 11, 2018 at 11:33 AM, Jeff Sadowski > wrote: >> ah looks like I need the -l flag >> >> On Thu, Jan 11, 2018 at 11:21 AM, Jeff Sadowski >> wrote: >>> Progress. I am now able to scan jpeg files :-) >>> And test out more of my phpsaneng program. >>> My preview worked awesome. I was able to watch the image as it was >>> being scanned. >>> >>> I redid git as recommended in INSTALL.linux >>> >>> apt remove sane sane-utils >>> git clone git://git.debian.org/sane/sane-backends.git >>> ./configure --prefix=/usr --libdir=/usr/lib --sysconfdir=/etc >>> --localstatedir=/var --enable-avahi >>> make >>> make install >>> >>> it is odd that -V reports as so >>> >>> root@raspberrypi:~/sane/sane-backends:x86$ scanimage -V >>> scanimage (sane-backends) 1.0.27git; backend version 1.0.24 >>> >>> Is this something I should be worried about? >>> Where would it be getting 1.0.24 >>> I tried removing all sane files I could find and then >>> make install from my git repo and I still get the same output. >>> >>> >>> Now to try and get saned working >>> saned use to at least connect to the port but now I get nothing >>> >>> root@raspberrypi:~/sane/sane-backends:x86$ saned -d128 >>> root@raspberrypi:~/sane/sane-backends:x86$ >>> >>> root@raspberrypi:~/sane/sane-backends:x86$ saned -d128 -b 192.168.1.27 >>> root@raspberrypi:~/sane/sane-backends:x86$ >>> >>> any suggestions on how to get it to report more? >>> maybe a compile flag to get something from it? >>> >>> On Thu, Jan 11, 2018 at 8:19 AM, Jeff Sadowski >>> wrote: root@raspberrypi:~:arm$ dpkg -c brscan2-0.2.5-1.i386.deb |grep lib|grep so -rwxr-xr-x root/root 11444 2009-12-01 18:38 ./usr/lib/libbrcolm2.so.1.0.0 -rwxr-xr-x root/root 27912 2009-12-01 18:38 ./usr/lib/libbrscandec2.so.1.0.0 -rwxr-xr-x root/root 94516 2009-12-01 18:38 ./usr/lib/sane/libsane-brother2.so.1.0.7 lrwxrwxrwx root/root 0 2009-12-01 18:38 ./usr/lib/libbrcolm2.so -> /usr/lib/libbrcolm2.so.1 lrwxrwxrwx root/root 0 2009-12-01 18:38 ./usr/lib/libbrscandec2.so.1 -> /usr/lib/libbrscandec2.so.1.0.0 lrwxrwxrwx root/root 0 2009-12-01 18:38 ./usr/lib/libbrscandec2.so -> /usr/lib/libbrscandec2.so.1 lrwxrwxrwx root/root 0 2009-12-01 18:38 ./usr/lib/libbrcolm2.so.1 -> /usr/lib/libbrcolm2.so.1.0.0 lrwxrwxrwx root/root 0 2009-12-01 18:38 ./usr/lib/sane/libsane-brother2.so.1 -> /usr/lib/sane/libsane-brother2.so.1.0.7 lrwxrwxrwx root/root 0 2009-12-01 18:38 ./usr/lib/sane/libsane-brother2.so -> /usr/lib/sane/libsane-brother2.so.1 so I will recompile to with libdir=/usr/lib and see if that works. On Thu, Jan 11, 2018 at 5:28 AM, Olaf Meeuwissen wrote: > Hi,
Re: [sane-devel] Weird behavior in exagear.
uning sane -l -d128 -e I am able to see the following error. root@raspberrypi:~:arm$ saned -l -d128 -e [saned] do_scan: wrote 8192 bytes to client [saned] do_scan: trying to read 8188 bytes from scanner [saned] do_scan: read 8188 bytes from scanner [saned] do_scan: trying to write 8192 bytes to client [saned] do_scan: wrote 8192 bytes to client [saned] do_scan: trying to read 8188 bytes from scanner [saned] do_scan: read 7488 bytes from scanner [saned] do_scan: trying to write 7492 bytes to client [saned] do_scan: wrote 7492 bytes to client [saned] do_scan: trying to read 696 bytes from scanner [saned] do_scan: read 0 bytes from scanner [saned] do_scan: status = `End of file reached' [saned] do_scan: statuscode `End of file reached' was added to buffer [saned] do_scan: trying to write 9 bytes to client [saned] do_scan: wrote 9 bytes to client [saned] do_scan: done, status=End of file reached [saned] process_request: waiting for request [saned] process_request: bad status 22 [saned] quit: exiting on the other end I get the following error scanimage '-v' '-p' '--batch=preview.jpg' '--batch-count' '1' '--format' 'jpeg' '-l' '0' '-t' '0' '-x' '215.9' '-y' '355.6' '-d' 'net:192.168.1.27:brother2:bus1;dev1' scanimage: rounded value of br-x from 215.9 to 215.88 scanimage: rounded value of br-y from 355.6 to 355.567 Scanning 1 page, incrementing by 1, numbering from 1 Scanning page 1 scanimage: scanning image of size 1648x2314 pixels at 24 bits/pixel scanimage: acquiring RGB frame Progress:98.8% scanimage: min/max graylevel value = 11/255 Application transferred too few scanlines On Thu, Jan 11, 2018 at 11:33 AM, Jeff Sadowskiwrote: > ah looks like I need the -l flag > > On Thu, Jan 11, 2018 at 11:21 AM, Jeff Sadowski > wrote: >> Progress. I am now able to scan jpeg files :-) >> And test out more of my phpsaneng program. >> My preview worked awesome. I was able to watch the image as it was >> being scanned. >> >> I redid git as recommended in INSTALL.linux >> >> apt remove sane sane-utils >> git clone git://git.debian.org/sane/sane-backends.git >> ./configure --prefix=/usr --libdir=/usr/lib --sysconfdir=/etc >> --localstatedir=/var --enable-avahi >> make >> make install >> >> it is odd that -V reports as so >> >> root@raspberrypi:~/sane/sane-backends:x86$ scanimage -V >> scanimage (sane-backends) 1.0.27git; backend version 1.0.24 >> >> Is this something I should be worried about? >> Where would it be getting 1.0.24 >> I tried removing all sane files I could find and then >> make install from my git repo and I still get the same output. >> >> >> Now to try and get saned working >> saned use to at least connect to the port but now I get nothing >> >> root@raspberrypi:~/sane/sane-backends:x86$ saned -d128 >> root@raspberrypi:~/sane/sane-backends:x86$ >> >> root@raspberrypi:~/sane/sane-backends:x86$ saned -d128 -b 192.168.1.27 >> root@raspberrypi:~/sane/sane-backends:x86$ >> >> any suggestions on how to get it to report more? >> maybe a compile flag to get something from it? >> >> On Thu, Jan 11, 2018 at 8:19 AM, Jeff Sadowski >> wrote: >>> root@raspberrypi:~:arm$ dpkg -c brscan2-0.2.5-1.i386.deb |grep lib|grep so >>> -rwxr-xr-x root/root 11444 2009-12-01 18:38 >>> ./usr/lib/libbrcolm2.so.1.0.0 >>> -rwxr-xr-x root/root 27912 2009-12-01 18:38 >>> ./usr/lib/libbrscandec2.so.1.0.0 >>> -rwxr-xr-x root/root 94516 2009-12-01 18:38 >>> ./usr/lib/sane/libsane-brother2.so.1.0.7 >>> lrwxrwxrwx root/root 0 2009-12-01 18:38 >>> ./usr/lib/libbrcolm2.so -> /usr/lib/libbrcolm2.so.1 >>> lrwxrwxrwx root/root 0 2009-12-01 18:38 >>> ./usr/lib/libbrscandec2.so.1 -> /usr/lib/libbrscandec2.so.1.0.0 >>> lrwxrwxrwx root/root 0 2009-12-01 18:38 >>> ./usr/lib/libbrscandec2.so -> /usr/lib/libbrscandec2.so.1 >>> lrwxrwxrwx root/root 0 2009-12-01 18:38 >>> ./usr/lib/libbrcolm2.so.1 -> /usr/lib/libbrcolm2.so.1.0.0 >>> lrwxrwxrwx root/root 0 2009-12-01 18:38 >>> ./usr/lib/sane/libsane-brother2.so.1 -> >>> /usr/lib/sane/libsane-brother2.so.1.0.7 >>> lrwxrwxrwx root/root 0 2009-12-01 18:38 >>> ./usr/lib/sane/libsane-brother2.so -> >>> /usr/lib/sane/libsane-brother2.so.1 >>> >>> so I will recompile to with libdir=/usr/lib and see if that works. >>> >>> On Thu, Jan 11, 2018 at 5:28 AM, Olaf Meeuwissen >>> wrote: Hi, Jeff Sadowski writes: > It seems to be wanting .la files when I have .so files so is there a > flag to support shared object files over .la? The dynamic loading should look for .la files first and failing to find those, look for .so files. You don't need any flag for that (and AFAIK there isn't one). > On Wed, Jan 10, 2018 at 1:36 PM, Jeff Sadowski > wrote: >> I pulled the current git of sane-backend from >> https://anonscm.debian.org/git/sane/sane-backends.git >>
Re: [sane-devel] Weird behavior in exagear.
ah looks like I need the -l flag On Thu, Jan 11, 2018 at 11:21 AM, Jeff Sadowskiwrote: > Progress. I am now able to scan jpeg files :-) > And test out more of my phpsaneng program. > My preview worked awesome. I was able to watch the image as it was > being scanned. > > I redid git as recommended in INSTALL.linux > > apt remove sane sane-utils > git clone git://git.debian.org/sane/sane-backends.git > ./configure --prefix=/usr --libdir=/usr/lib --sysconfdir=/etc > --localstatedir=/var --enable-avahi > make > make install > > it is odd that -V reports as so > > root@raspberrypi:~/sane/sane-backends:x86$ scanimage -V > scanimage (sane-backends) 1.0.27git; backend version 1.0.24 > > Is this something I should be worried about? > Where would it be getting 1.0.24 > I tried removing all sane files I could find and then > make install from my git repo and I still get the same output. > > > Now to try and get saned working > saned use to at least connect to the port but now I get nothing > > root@raspberrypi:~/sane/sane-backends:x86$ saned -d128 > root@raspberrypi:~/sane/sane-backends:x86$ > > root@raspberrypi:~/sane/sane-backends:x86$ saned -d128 -b 192.168.1.27 > root@raspberrypi:~/sane/sane-backends:x86$ > > any suggestions on how to get it to report more? > maybe a compile flag to get something from it? > > On Thu, Jan 11, 2018 at 8:19 AM, Jeff Sadowski > wrote: >> root@raspberrypi:~:arm$ dpkg -c brscan2-0.2.5-1.i386.deb |grep lib|grep so >> -rwxr-xr-x root/root 11444 2009-12-01 18:38 ./usr/lib/libbrcolm2.so.1.0.0 >> -rwxr-xr-x root/root 27912 2009-12-01 18:38 >> ./usr/lib/libbrscandec2.so.1.0.0 >> -rwxr-xr-x root/root 94516 2009-12-01 18:38 >> ./usr/lib/sane/libsane-brother2.so.1.0.7 >> lrwxrwxrwx root/root 0 2009-12-01 18:38 >> ./usr/lib/libbrcolm2.so -> /usr/lib/libbrcolm2.so.1 >> lrwxrwxrwx root/root 0 2009-12-01 18:38 >> ./usr/lib/libbrscandec2.so.1 -> /usr/lib/libbrscandec2.so.1.0.0 >> lrwxrwxrwx root/root 0 2009-12-01 18:38 >> ./usr/lib/libbrscandec2.so -> /usr/lib/libbrscandec2.so.1 >> lrwxrwxrwx root/root 0 2009-12-01 18:38 >> ./usr/lib/libbrcolm2.so.1 -> /usr/lib/libbrcolm2.so.1.0.0 >> lrwxrwxrwx root/root 0 2009-12-01 18:38 >> ./usr/lib/sane/libsane-brother2.so.1 -> >> /usr/lib/sane/libsane-brother2.so.1.0.7 >> lrwxrwxrwx root/root 0 2009-12-01 18:38 >> ./usr/lib/sane/libsane-brother2.so -> >> /usr/lib/sane/libsane-brother2.so.1 >> >> so I will recompile to with libdir=/usr/lib and see if that works. >> >> On Thu, Jan 11, 2018 at 5:28 AM, Olaf Meeuwissen >> wrote: >>> Hi, >>> >>> Jeff Sadowski writes: >>> It seems to be wanting .la files when I have .so files so is there a flag to support shared object files over .la? >>> >>> The dynamic loading should look for .la files first and failing to find >>> those, look for .so files. You don't need any flag for that (and AFAIK >>> there isn't one). >>> On Wed, Jan 10, 2018 at 1:36 PM, Jeff Sadowski wrote: > I pulled the current git of sane-backend from > https://anonscm.debian.org/git/sane/sane-backends.git > > I did > ./configure --prefix=/usr --libdir=/usr/lib/i386-linux-gnu > --sysconfdir=/etc --localstatedir=/var -- > make > make install > > now when I run "scanimage -L" it can't see my scanner. Is there a flag > I need to use other drivers than the ones it compiles as the brother > printer driver is a binary package? >>> >>> The backends you built are installed below /usr/lib/i386-linux-gnu/sane/ >>> as libsane-$backendname.$extension, right? Where is the backend of that >>> brother binary package installed? >>> >>> If it's not in the same directory, you need to tell the loader to look >>> in the directory where the brother binary package installed its >>> backend. Let's say that is /opt/brother/sane, then you'd have to run >>> >>> LD_LIBRARY_PATH=/opt/brother/sane scanimage -L >>> >>> Alternatively, you can make a symbolic link to the brother backend from >>> /usr/lib/i386-linux-gnu/sane/. Using the same example location >>> >>> cd /usr/lib/i386-linux-gnu/sane >>> ln -s /opt/brother/sane/libsane-$backendname.$extension >>> >>> Hope this helps, >>> -- >>> Olaf Meeuwissen, LPIC-2FSF Associate Member since 2004-01-27 >>> GnuPG key: F84A2DD9/B3C0 2F47 EA19 64F4 9F13 F43E B8A4 A88A F84A 2DD9 >>> Support Free Softwarehttps://my.fsf.org/donate >>> Join the Free Software Foundation https://my.fsf.org/join -- sane-devel mailing list: sane-devel@lists.alioth.debian.org http://lists.alioth.debian.org/cgi-bin/mailman/listinfo/sane-devel Unsubscribe: Send mail with subject "unsubscribe your_password" to sane-devel-requ...@lists.alioth.debian.org
Re: [sane-devel] Weird behavior in exagear.
Progress. I am now able to scan jpeg files :-) And test out more of my phpsaneng program. My preview worked awesome. I was able to watch the image as it was being scanned. I redid git as recommended in INSTALL.linux apt remove sane sane-utils git clone git://git.debian.org/sane/sane-backends.git ./configure --prefix=/usr --libdir=/usr/lib --sysconfdir=/etc --localstatedir=/var --enable-avahi make make install it is odd that -V reports as so root@raspberrypi:~/sane/sane-backends:x86$ scanimage -V scanimage (sane-backends) 1.0.27git; backend version 1.0.24 Is this something I should be worried about? Where would it be getting 1.0.24 I tried removing all sane files I could find and then make install from my git repo and I still get the same output. Now to try and get saned working saned use to at least connect to the port but now I get nothing root@raspberrypi:~/sane/sane-backends:x86$ saned -d128 root@raspberrypi:~/sane/sane-backends:x86$ root@raspberrypi:~/sane/sane-backends:x86$ saned -d128 -b 192.168.1.27 root@raspberrypi:~/sane/sane-backends:x86$ any suggestions on how to get it to report more? maybe a compile flag to get something from it? On Thu, Jan 11, 2018 at 8:19 AM, Jeff Sadowskiwrote: > root@raspberrypi:~:arm$ dpkg -c brscan2-0.2.5-1.i386.deb |grep lib|grep so > -rwxr-xr-x root/root 11444 2009-12-01 18:38 ./usr/lib/libbrcolm2.so.1.0.0 > -rwxr-xr-x root/root 27912 2009-12-01 18:38 > ./usr/lib/libbrscandec2.so.1.0.0 > -rwxr-xr-x root/root 94516 2009-12-01 18:38 > ./usr/lib/sane/libsane-brother2.so.1.0.7 > lrwxrwxrwx root/root 0 2009-12-01 18:38 > ./usr/lib/libbrcolm2.so -> /usr/lib/libbrcolm2.so.1 > lrwxrwxrwx root/root 0 2009-12-01 18:38 > ./usr/lib/libbrscandec2.so.1 -> /usr/lib/libbrscandec2.so.1.0.0 > lrwxrwxrwx root/root 0 2009-12-01 18:38 > ./usr/lib/libbrscandec2.so -> /usr/lib/libbrscandec2.so.1 > lrwxrwxrwx root/root 0 2009-12-01 18:38 > ./usr/lib/libbrcolm2.so.1 -> /usr/lib/libbrcolm2.so.1.0.0 > lrwxrwxrwx root/root 0 2009-12-01 18:38 > ./usr/lib/sane/libsane-brother2.so.1 -> > /usr/lib/sane/libsane-brother2.so.1.0.7 > lrwxrwxrwx root/root 0 2009-12-01 18:38 > ./usr/lib/sane/libsane-brother2.so -> > /usr/lib/sane/libsane-brother2.so.1 > > so I will recompile to with libdir=/usr/lib and see if that works. > > On Thu, Jan 11, 2018 at 5:28 AM, Olaf Meeuwissen > wrote: >> Hi, >> >> Jeff Sadowski writes: >> >>> It seems to be wanting .la files when I have .so files so is there a >>> flag to support shared object files over .la? >> >> The dynamic loading should look for .la files first and failing to find >> those, look for .so files. You don't need any flag for that (and AFAIK >> there isn't one). >> >>> On Wed, Jan 10, 2018 at 1:36 PM, Jeff Sadowski >>> wrote: I pulled the current git of sane-backend from https://anonscm.debian.org/git/sane/sane-backends.git I did ./configure --prefix=/usr --libdir=/usr/lib/i386-linux-gnu --sysconfdir=/etc --localstatedir=/var -- make make install now when I run "scanimage -L" it can't see my scanner. Is there a flag I need to use other drivers than the ones it compiles as the brother printer driver is a binary package? >> >> The backends you built are installed below /usr/lib/i386-linux-gnu/sane/ >> as libsane-$backendname.$extension, right? Where is the backend of that >> brother binary package installed? >> >> If it's not in the same directory, you need to tell the loader to look >> in the directory where the brother binary package installed its >> backend. Let's say that is /opt/brother/sane, then you'd have to run >> >> LD_LIBRARY_PATH=/opt/brother/sane scanimage -L >> >> Alternatively, you can make a symbolic link to the brother backend from >> /usr/lib/i386-linux-gnu/sane/. Using the same example location >> >> cd /usr/lib/i386-linux-gnu/sane >> ln -s /opt/brother/sane/libsane-$backendname.$extension >> >> Hope this helps, >> -- >> Olaf Meeuwissen, LPIC-2FSF Associate Member since 2004-01-27 >> GnuPG key: F84A2DD9/B3C0 2F47 EA19 64F4 9F13 F43E B8A4 A88A F84A 2DD9 >> Support Free Softwarehttps://my.fsf.org/donate >> Join the Free Software Foundation https://my.fsf.org/join -- sane-devel mailing list: sane-devel@lists.alioth.debian.org http://lists.alioth.debian.org/cgi-bin/mailman/listinfo/sane-devel Unsubscribe: Send mail with subject "unsubscribe your_password" to sane-devel-requ...@lists.alioth.debian.org
Re: [sane-devel] Weird behavior in exagear.
root@raspberrypi:~:arm$ dpkg -c brscan2-0.2.5-1.i386.deb |grep lib|grep so -rwxr-xr-x root/root 11444 2009-12-01 18:38 ./usr/lib/libbrcolm2.so.1.0.0 -rwxr-xr-x root/root 27912 2009-12-01 18:38 ./usr/lib/libbrscandec2.so.1.0.0 -rwxr-xr-x root/root 94516 2009-12-01 18:38 ./usr/lib/sane/libsane-brother2.so.1.0.7 lrwxrwxrwx root/root 0 2009-12-01 18:38 ./usr/lib/libbrcolm2.so -> /usr/lib/libbrcolm2.so.1 lrwxrwxrwx root/root 0 2009-12-01 18:38 ./usr/lib/libbrscandec2.so.1 -> /usr/lib/libbrscandec2.so.1.0.0 lrwxrwxrwx root/root 0 2009-12-01 18:38 ./usr/lib/libbrscandec2.so -> /usr/lib/libbrscandec2.so.1 lrwxrwxrwx root/root 0 2009-12-01 18:38 ./usr/lib/libbrcolm2.so.1 -> /usr/lib/libbrcolm2.so.1.0.0 lrwxrwxrwx root/root 0 2009-12-01 18:38 ./usr/lib/sane/libsane-brother2.so.1 -> /usr/lib/sane/libsane-brother2.so.1.0.7 lrwxrwxrwx root/root 0 2009-12-01 18:38 ./usr/lib/sane/libsane-brother2.so -> /usr/lib/sane/libsane-brother2.so.1 so I will recompile to with libdir=/usr/lib and see if that works. On Thu, Jan 11, 2018 at 5:28 AM, Olaf Meeuwissenwrote: > Hi, > > Jeff Sadowski writes: > >> It seems to be wanting .la files when I have .so files so is there a >> flag to support shared object files over .la? > > The dynamic loading should look for .la files first and failing to find > those, look for .so files. You don't need any flag for that (and AFAIK > there isn't one). > >> On Wed, Jan 10, 2018 at 1:36 PM, Jeff Sadowski >> wrote: >>> I pulled the current git of sane-backend from >>> https://anonscm.debian.org/git/sane/sane-backends.git >>> >>> I did >>> ./configure --prefix=/usr --libdir=/usr/lib/i386-linux-gnu >>> --sysconfdir=/etc --localstatedir=/var -- >>> make >>> make install >>> >>> now when I run "scanimage -L" it can't see my scanner. Is there a flag >>> I need to use other drivers than the ones it compiles as the brother >>> printer driver is a binary package? > > The backends you built are installed below /usr/lib/i386-linux-gnu/sane/ > as libsane-$backendname.$extension, right? Where is the backend of that > brother binary package installed? > > If it's not in the same directory, you need to tell the loader to look > in the directory where the brother binary package installed its > backend. Let's say that is /opt/brother/sane, then you'd have to run > > LD_LIBRARY_PATH=/opt/brother/sane scanimage -L > > Alternatively, you can make a symbolic link to the brother backend from > /usr/lib/i386-linux-gnu/sane/. Using the same example location > > cd /usr/lib/i386-linux-gnu/sane > ln -s /opt/brother/sane/libsane-$backendname.$extension > > Hope this helps, > -- > Olaf Meeuwissen, LPIC-2FSF Associate Member since 2004-01-27 > GnuPG key: F84A2DD9/B3C0 2F47 EA19 64F4 9F13 F43E B8A4 A88A F84A 2DD9 > Support Free Softwarehttps://my.fsf.org/donate > Join the Free Software Foundation https://my.fsf.org/join -- sane-devel mailing list: sane-devel@lists.alioth.debian.org http://lists.alioth.debian.org/cgi-bin/mailman/listinfo/sane-devel Unsubscribe: Send mail with subject "unsubscribe your_password" to sane-devel-requ...@lists.alioth.debian.org
Re: [sane-devel] Weird behavior in exagear.
Hi, Jeff Sadowski writes: > It seems to be wanting .la files when I have .so files so is there a > flag to support shared object files over .la? The dynamic loading should look for .la files first and failing to find those, look for .so files. You don't need any flag for that (and AFAIK there isn't one). > On Wed, Jan 10, 2018 at 1:36 PM, Jeff Sadowski> wrote: >> I pulled the current git of sane-backend from >> https://anonscm.debian.org/git/sane/sane-backends.git >> >> I did >> ./configure --prefix=/usr --libdir=/usr/lib/i386-linux-gnu >> --sysconfdir=/etc --localstatedir=/var -- >> make >> make install >> >> now when I run "scanimage -L" it can't see my scanner. Is there a flag >> I need to use other drivers than the ones it compiles as the brother >> printer driver is a binary package? The backends you built are installed below /usr/lib/i386-linux-gnu/sane/ as libsane-$backendname.$extension, right? Where is the backend of that brother binary package installed? If it's not in the same directory, you need to tell the loader to look in the directory where the brother binary package installed its backend. Let's say that is /opt/brother/sane, then you'd have to run LD_LIBRARY_PATH=/opt/brother/sane scanimage -L Alternatively, you can make a symbolic link to the brother backend from /usr/lib/i386-linux-gnu/sane/. Using the same example location cd /usr/lib/i386-linux-gnu/sane ln -s /opt/brother/sane/libsane-$backendname.$extension Hope this helps, -- Olaf Meeuwissen, LPIC-2FSF Associate Member since 2004-01-27 GnuPG key: F84A2DD9/B3C0 2F47 EA19 64F4 9F13 F43E B8A4 A88A F84A 2DD9 Support Free Softwarehttps://my.fsf.org/donate Join the Free Software Foundation https://my.fsf.org/join -- sane-devel mailing list: sane-devel@lists.alioth.debian.org http://lists.alioth.debian.org/cgi-bin/mailman/listinfo/sane-devel Unsubscribe: Send mail with subject "unsubscribe your_password" to sane-devel-requ...@lists.alioth.debian.org
Re: [sane-devel] Weird behavior in exagear.
It seems to be wanting .la files when I have .so files so is there a flag to support shared object files over .la? On Wed, Jan 10, 2018 at 1:36 PM, Jeff Sadowskiwrote: > I pulled the current git of sane-backend from > https://anonscm.debian.org/git/sane/sane-backends.git > > I did > ./configure --prefix=/usr --libdir=/usr/lib/i386-linux-gnu > --sysconfdir=/etc --localstatedir=/var -- > make > make install > > now when I run "scanimage -L" it can't see my scanner. Is there a flag > I need to use other drivers than the ones it compiles as the brother > printer driver is a binary package? > > On Wed, Jan 10, 2018 at 10:58 AM, Jeff Sadowski > wrote: >> root@raspberrypi:~:x86$ scanimage --version >> scanimage (sane-backends) 1.0.24; backend version 1.0.24 >> >> ugh that is old debian-8 image from exagear is a bit dated. >> >> I'll get the current backend and compile that and see if that works. >> I have no idea how or if this will work since it is an emulated x86 >> architecture. >> running on arm >> >> >> >> On Sun, Jan 7, 2018 at 8:19 PM, Olaf Meeuwissen >> wrote: >>> Hi Jeff, >>> >>> Jeff writes: >>> On 07/01/18 05:53, Jeff Sadowski wrote: > I'm using debian in exagear do they compile scanimage without support > for jpeg and png? It is looking like I have to try and put some other > virtual os on my raspberry pi 3 system. Isn't it just easier to use ImageMagick or GraphicsMagick to convert from pnm to what you want? >>> >>> Support for JPEG and PNG output was added to scanimage in 1.0.25. So if >>> you have that (and your distribution enabled it), you don't need either >>> of the *Magick's. Note that there were some bugfixes to the JPEG and >>> PNG support in 1.0.27. >>> >>> Hope this helps, >>> -- >>> Olaf Meeuwissen, LPIC-2FSF Associate Member since 2004-01-27 >>> GnuPG key: F84A2DD9/B3C0 2F47 EA19 64F4 9F13 F43E B8A4 A88A F84A 2DD9 >>> Support Free Softwarehttps://my.fsf.org/donate >>> Join the Free Software Foundation https://my.fsf.org/join >>> >>> -- >>> sane-devel mailing list: sane-devel@lists.alioth.debian.org >>> http://lists.alioth.debian.org/cgi-bin/mailman/listinfo/sane-devel >>> Unsubscribe: Send mail with subject "unsubscribe your_password" >>> to sane-devel-requ...@lists.alioth.debian.org -- sane-devel mailing list: sane-devel@lists.alioth.debian.org http://lists.alioth.debian.org/cgi-bin/mailman/listinfo/sane-devel Unsubscribe: Send mail with subject "unsubscribe your_password" to sane-devel-requ...@lists.alioth.debian.org
Re: [sane-devel] Weird behavior in exagear.
I pulled the current git of sane-backend from https://anonscm.debian.org/git/sane/sane-backends.git I did ./configure --prefix=/usr --libdir=/usr/lib/i386-linux-gnu --sysconfdir=/etc --localstatedir=/var -- make make install now when I run "scanimage -L" it can't see my scanner. Is there a flag I need to use other drivers than the ones it compiles as the brother printer driver is a binary package? On Wed, Jan 10, 2018 at 10:58 AM, Jeff Sadowskiwrote: > root@raspberrypi:~:x86$ scanimage --version > scanimage (sane-backends) 1.0.24; backend version 1.0.24 > > ugh that is old debian-8 image from exagear is a bit dated. > > I'll get the current backend and compile that and see if that works. > I have no idea how or if this will work since it is an emulated x86 > architecture. > running on arm > > > > On Sun, Jan 7, 2018 at 8:19 PM, Olaf Meeuwissen > wrote: >> Hi Jeff, >> >> Jeff writes: >> >>> On 07/01/18 05:53, Jeff Sadowski wrote: I'm using debian in exagear do they compile scanimage without support for jpeg and png? It is looking like I have to try and put some other virtual os on my raspberry pi 3 system. >>> >>> Isn't it just easier to use ImageMagick or GraphicsMagick to convert >>> from pnm to what you want? >> >> Support for JPEG and PNG output was added to scanimage in 1.0.25. So if >> you have that (and your distribution enabled it), you don't need either >> of the *Magick's. Note that there were some bugfixes to the JPEG and >> PNG support in 1.0.27. >> >> Hope this helps, >> -- >> Olaf Meeuwissen, LPIC-2FSF Associate Member since 2004-01-27 >> GnuPG key: F84A2DD9/B3C0 2F47 EA19 64F4 9F13 F43E B8A4 A88A F84A 2DD9 >> Support Free Softwarehttps://my.fsf.org/donate >> Join the Free Software Foundation https://my.fsf.org/join >> >> -- >> sane-devel mailing list: sane-devel@lists.alioth.debian.org >> http://lists.alioth.debian.org/cgi-bin/mailman/listinfo/sane-devel >> Unsubscribe: Send mail with subject "unsubscribe your_password" >> to sane-devel-requ...@lists.alioth.debian.org -- sane-devel mailing list: sane-devel@lists.alioth.debian.org http://lists.alioth.debian.org/cgi-bin/mailman/listinfo/sane-devel Unsubscribe: Send mail with subject "unsubscribe your_password" to sane-devel-requ...@lists.alioth.debian.org
Re: [sane-devel] Weird behavior in exagear.
root@raspberrypi:~:x86$ scanimage --version scanimage (sane-backends) 1.0.24; backend version 1.0.24 ugh that is old debian-8 image from exagear is a bit dated. I'll get the current backend and compile that and see if that works. I have no idea how or if this will work since it is an emulated x86 architecture. running on arm On Sun, Jan 7, 2018 at 8:19 PM, Olaf Meeuwissenwrote: > Hi Jeff, > > Jeff writes: > >> On 07/01/18 05:53, Jeff Sadowski wrote: >>> I'm using debian in exagear do they compile scanimage without support >>> for jpeg and png? It is looking like I have to try and put some other >>> virtual os on my raspberry pi 3 system. >> >> Isn't it just easier to use ImageMagick or GraphicsMagick to convert >> from pnm to what you want? > > Support for JPEG and PNG output was added to scanimage in 1.0.25. So if > you have that (and your distribution enabled it), you don't need either > of the *Magick's. Note that there were some bugfixes to the JPEG and > PNG support in 1.0.27. > > Hope this helps, > -- > Olaf Meeuwissen, LPIC-2FSF Associate Member since 2004-01-27 > GnuPG key: F84A2DD9/B3C0 2F47 EA19 64F4 9F13 F43E B8A4 A88A F84A 2DD9 > Support Free Softwarehttps://my.fsf.org/donate > Join the Free Software Foundation https://my.fsf.org/join > > -- > sane-devel mailing list: sane-devel@lists.alioth.debian.org > http://lists.alioth.debian.org/cgi-bin/mailman/listinfo/sane-devel > Unsubscribe: Send mail with subject "unsubscribe your_password" > to sane-devel-requ...@lists.alioth.debian.org -- sane-devel mailing list: sane-devel@lists.alioth.debian.org http://lists.alioth.debian.org/cgi-bin/mailman/listinfo/sane-devel Unsubscribe: Send mail with subject "unsubscribe your_password" to sane-devel-requ...@lists.alioth.debian.org
Re: [sane-devel] Weird behavior in exagear.
Hi Jeff, Jeff writes: > On 07/01/18 05:53, Jeff Sadowski wrote: >> I'm using debian in exagear do they compile scanimage without support >> for jpeg and png? It is looking like I have to try and put some other >> virtual os on my raspberry pi 3 system. > > Isn't it just easier to use ImageMagick or GraphicsMagick to convert > from pnm to what you want? Support for JPEG and PNG output was added to scanimage in 1.0.25. So if you have that (and your distribution enabled it), you don't need either of the *Magick's. Note that there were some bugfixes to the JPEG and PNG support in 1.0.27. Hope this helps, -- Olaf Meeuwissen, LPIC-2FSF Associate Member since 2004-01-27 GnuPG key: F84A2DD9/B3C0 2F47 EA19 64F4 9F13 F43E B8A4 A88A F84A 2DD9 Support Free Softwarehttps://my.fsf.org/donate Join the Free Software Foundation https://my.fsf.org/join -- sane-devel mailing list: sane-devel@lists.alioth.debian.org http://lists.alioth.debian.org/cgi-bin/mailman/listinfo/sane-devel Unsubscribe: Send mail with subject "unsubscribe your_password" to sane-devel-requ...@lists.alioth.debian.org
Re: [sane-devel] Weird behavior in exagear.
Hi Jeff, Jeff Sadowski writes: > I'm using debian in exagear do they compile scanimage without support > for jpeg and png? It is looking like I have to try and put some other > virtual os on my raspberry pi 3 system. That may depend on the Debian version and architecture you're using. You can check the package dependencies with dpkg-query -W -f '${Depends}\n' sane-utils On my machine (Devuan ASCII, approximately Debian 9), I get adduser, lsb-base (>= 3.0-6), update-inetd, debconf (>= 0.5) | debconf-2.0, init-system-helpers (>= 1.18~), libavahi-client3 (>= 0.6.16), libavahi-common3 (>= 0.6.16), libc6 (>= 2.15), libieee1284-3, libjpeg62-turbo (>= 1.3.1), libpng16-16 (>= 1.6.2-1), libsane (>= 1.0.24), libsystemd0, libusb-1.0-0 (>= 2:1.0.8) So, as mentioned already in my previous reply, I can use JPEG and PNG but not TIFF. Hope this helps, -- Olaf Meeuwissen, LPIC-2FSF Associate Member since 2004-01-27 GnuPG key: F84A2DD9/B3C0 2F47 EA19 64F4 9F13 F43E B8A4 A88A F84A 2DD9 Support Free Softwarehttps://my.fsf.org/donate Join the Free Software Foundation https://my.fsf.org/join -- sane-devel mailing list: sane-devel@lists.alioth.debian.org http://lists.alioth.debian.org/cgi-bin/mailman/listinfo/sane-devel Unsubscribe: Send mail with subject "unsubscribe your_password" to sane-devel-requ...@lists.alioth.debian.org
Re: [sane-devel] Weird behavior in exagear.
Hi Jeff, Jeff Sadowski writes: > So, renaming my image from the directly connected method to pmn allows > me to view it. Now to find out what I need to get a jpeg, tiff, png > images. Your scanimage needs to be linked to JPEG, TIFF and PNG libraries. You can check with ldd $(which scanimage) On my machine I get $ ldd $(which scanimage) linux-vdso.so.1 (0x7fffa9f9a000) libsane.so.1 => /usr/lib/x86_64-linux-gnu/libsane.so.1 (0x7f11434ed000) libpng16.so.16 => /usr/lib/x86_64-linux-gnu/libpng16.so.16 (0x7f11432ba000) libjpeg.so.62 => /usr/lib/x86_64-linux-gnu/libjpeg.so.62 (0x7f114304f000) libc.so.6 => /lib/x86_64-linux-gnu/libc.so.6 (0x7f1142cb) libdl.so.2 => /lib/x86_64-linux-gnu/libdl.so.2 (0x7f1142aac000) libz.so.1 => /lib/x86_64-linux-gnu/libz.so.1 (0x7f1142892000) libm.so.6 => /lib/x86_64-linux-gnu/libm.so.6 (0x7f114258e000) /lib64/ld-linux-x86-64.so.2 (0x7f1143902000) So I can scan directly to JPEG and PNG but not to TIFF. If you're compiling scanimage yourself from source, you need to have the development packages installed before you ./configure. Hope this helps, -- Olaf Meeuwissen, LPIC-2FSF Associate Member since 2004-01-27 GnuPG key: F84A2DD9/B3C0 2F47 EA19 64F4 9F13 F43E B8A4 A88A F84A 2DD9 Support Free Softwarehttps://my.fsf.org/donate Join the Free Software Foundation https://my.fsf.org/join -- sane-devel mailing list: sane-devel@lists.alioth.debian.org http://lists.alioth.debian.org/cgi-bin/mailman/listinfo/sane-devel Unsubscribe: Send mail with subject "unsubscribe your_password" to sane-devel-requ...@lists.alioth.debian.org
Re: [sane-devel] Weird behavior in exagear.
On 07/01/18 05:53, Jeff Sadowski wrote: > I'm using debian in exagear do they compile scanimage without support > for jpeg and png? It is looking like I have to try and put some other > virtual os on my raspberry pi 3 system. Isn't it just easier to use ImageMagick or GraphicsMagick to convert from pnm to what you want? Regards Jeff signature.asc Description: OpenPGP digital signature -- sane-devel mailing list: sane-devel@lists.alioth.debian.org http://lists.alioth.debian.org/cgi-bin/mailman/listinfo/sane-devel Unsubscribe: Send mail with subject "unsubscribe your_password" to sane-devel-requ...@lists.alioth.debian.org
Re: [sane-devel] Weird behavior in exagear.
I'm using debian in exagear do they compile scanimage without support for jpeg and png? It is looking like I have to try and put some other virtual os on my raspberry pi 3 system. On Sat, Jan 6, 2018 at 9:17 PM, Jeff Sadowskiwrote: > So, renaming my image from the directly connected method to pmn allows > me to view it. Now to find out what I need to get a jpeg, tiff, png > images. > > On Sat, Jan 6, 2018 at 8:54 PM, Jeff Sadowski wrote: >> interesting I searched for "scanimage # sane data follows" and came across >> >> https://github.com/kkaempf/sane-backends/blob/master/frontend/scanimage.c >> >> and looking at that it looks like I was getting a pnm header even >> though I asked for a jpg. >> maybe I need to install jpg packages to use scanimage to output a jpeg? >> >> On Fri, Jan 5, 2018 at 2:53 PM, Jeff Sadowski >> wrote: >>> Server side with saned >>> >>> root@raspberrypi:~:x86$ while [ 1 ];do saned -d 128;done >>> [saned] main: starting debug mode (level 2) >>> [saned] saned (AF-indep+IPv6) from sane-backends 1.0.24 starting up >>> [saned] do_bindings: [0] bind failed: Address already in use >>> [saned] check_host: access by remote host: :::192.168.1.252 >>> [saned] init: access granted to apache@:::192.168.1.252 >>> >>> gets to 96%ish then >>> >>> [saned] process_request: bad status 22 >>> [saned] bailing out, waiting for children... >>> [saned] bail_out: all children exited >>> [saned] main: starting debug mode (level 2) >>> [saned] saned (AF-indep+IPv6) from sane-backends 1.0.24 starting up >>> [saned] do_bindings: [0] bind failed: Address already in use >>> ^C >>> >>> >>> >>> On Fri, Jan 5, 2018 at 2:44 PM, Jeff Sadowski >>> wrote: I started my scanner testing with my project. :-) My project phpsaneng seems to be working. The way I want to use my scanner, not so much. Maybe one of you would know what is happening here. I currently have 2 ways to connect to my scanner. Via saned or using scanimage directly. I was surprised that both methods fail in two different ways. using saned from a second server: /usr/bin/scanimage "-v" "-p" "--batch=preview.jpg" "--batch-count" "1" "--format" "jpeg" "-l" "0" "-t" "0" "-x" "215.9" "-y" "355.6" "-d" "net:192.168.1.27:brother2:bus1;dev1" results in scanimage: rounded value of br-x from 215.9 to 215.88 scanimage: rounded value of br-y from 355.6 to 355.567 Scanning 1 page, incrementing by 1, numbering from 1 Scanning page 1 scanimage: scanning image of size 1648x2314 pixels at 24 bits/pixel scanimage: acquiring RGB frame Progress: 96% scanimage: min/max graylevel value = 11/255 Application transferred too few scanlines hexdump -c preview.jpg.part|head looks like so 000 377 330 377 340 \0 020 J F I F \0 001 001 001 \0 310 010 \0 310 \0 \0 377 333 \0 C \0 \b 006 006 \a 006 005 \b 020 \a \a \a \t \t \b \n \f 024 \r \f \v \v \f 031 022 030 023 017 024 035 032 037 036 035 032 034 034 $ . ' 040 " , # 034 034 ( 7 ) , 0 1 4 4 4 037 ' 050 9 = 8 2 < . 3 4 2 377 333 \0 C 001 \t \t 060 \t \f \v \f 030 \r \r 030 2 ! 034 ! 2 2 2 2 070 2 2 2 2 2 2 2 2 2 2 2 2 2 2 2 2 * 090 2 2 2 2 2 2 2 2 2 2 2 2 2 2 377 300 I can view this file in most image viewers directly from the server connected to the printer (a raspberry pi with exagear to run the brother software) using /usr/bin/scanimage "-v" "-p" "--batch=preview.jpg" "--batch-count" "1" "--format" "jpeg" "-l" "0" "-t" "0" "-x" "215.9" "-y" "355.6" "-d" "brother2:bus1;dev1" results in scanimage: rounded value of br-x from 215.9 to 215.88 scanimage: rounded value of br-y from 355.6 to 355.567 Scanning 1 pages, incrementing by 1, numbering from 1 Scanning page 1 scanimage: scanning image of size 1648x2314 pixels at 24 bits/pixel scanimage: acquiring RGB frame Progress: 100% scanimage: min/max graylevel value = 11/255 scanimage: read 11440416 bytes in total Scanned page 1. (scanner status = 5) hexdump -c preview.jpg|head 000 P 6 \n # S A N E d a t a f 010 o l l o w s \n 1 6 4 8 2 3 1 4 020 \n 2 5 5 \n \f 021 031 \r 022 032 \f 021 030 \f 021 030 030 \f 021 030 \f 021 030 \f 021 030 \r 022 031 \r 022 031 040 \f 023 031 \f 021 030 \f 021 030 \f 021 030 \f 021 031 \f 050 021 030 \f 021 030 \f 021 030 \v 020 027 \f 021 030 \r 022
Re: [sane-devel] Weird behavior in exagear.
So, renaming my image from the directly connected method to pmn allows me to view it. Now to find out what I need to get a jpeg, tiff, png images. On Sat, Jan 6, 2018 at 8:54 PM, Jeff Sadowskiwrote: > interesting I searched for "scanimage # sane data follows" and came across > > https://github.com/kkaempf/sane-backends/blob/master/frontend/scanimage.c > > and looking at that it looks like I was getting a pnm header even > though I asked for a jpg. > maybe I need to install jpg packages to use scanimage to output a jpeg? > > On Fri, Jan 5, 2018 at 2:53 PM, Jeff Sadowski wrote: >> Server side with saned >> >> root@raspberrypi:~:x86$ while [ 1 ];do saned -d 128;done >> [saned] main: starting debug mode (level 2) >> [saned] saned (AF-indep+IPv6) from sane-backends 1.0.24 starting up >> [saned] do_bindings: [0] bind failed: Address already in use >> [saned] check_host: access by remote host: :::192.168.1.252 >> [saned] init: access granted to apache@:::192.168.1.252 >> >> gets to 96%ish then >> >> [saned] process_request: bad status 22 >> [saned] bailing out, waiting for children... >> [saned] bail_out: all children exited >> [saned] main: starting debug mode (level 2) >> [saned] saned (AF-indep+IPv6) from sane-backends 1.0.24 starting up >> [saned] do_bindings: [0] bind failed: Address already in use >> ^C >> >> >> >> On Fri, Jan 5, 2018 at 2:44 PM, Jeff Sadowski >> wrote: >>> I started my scanner testing with my project. :-) My project phpsaneng >>> seems to be working. >>> >>> The way I want to use my scanner, not so much. >>> >>> Maybe one of you would know what is happening here. I currently have 2 >>> ways to connect to my scanner. Via saned or using scanimage directly. >>> >>> I was surprised that both methods fail in two different ways. >>> >>> using saned from a second server: >>> >>> /usr/bin/scanimage "-v" "-p" "--batch=preview.jpg" "--batch-count" >>> "1" "--format" "jpeg" "-l" "0" "-t" "0" "-x" "215.9" "-y" "355.6" "-d" >>> "net:192.168.1.27:brother2:bus1;dev1" >>> >>> results in >>> >>> scanimage: rounded value of br-x from 215.9 to 215.88 >>> scanimage: rounded value of br-y from 355.6 to 355.567 >>> Scanning 1 page, incrementing by 1, numbering from 1 >>> Scanning page 1 >>> scanimage: scanning image of size 1648x2314 pixels at 24 bits/pixel >>> scanimage: acquiring RGB frame >>> Progress: 96% >>> scanimage: min/max graylevel value = 11/255 >>> Application transferred too few scanlines >>> >>> hexdump -c preview.jpg.part|head looks like so >>> >>> 000 377 330 377 340 \0 020 J F I F \0 001 001 001 \0 310 >>> 010 \0 310 \0 \0 377 333 \0 C \0 \b 006 006 \a 006 005 \b >>> 020 \a \a \a \t \t \b \n \f 024 \r \f \v \v \f 031 022 >>> 030 023 017 024 035 032 037 036 035 032 034 034 $ . ' >>> 040 " , # 034 034 ( 7 ) , 0 1 4 4 4 037 ' >>> 050 9 = 8 2 < . 3 4 2 377 333 \0 C 001 \t \t >>> 060 \t \f \v \f 030 \r \r 030 2 ! 034 ! 2 2 2 2 >>> 070 2 2 2 2 2 2 2 2 2 2 2 2 2 2 2 2 >>> * >>> 090 2 2 2 2 2 2 2 2 2 2 2 2 2 2 377 300 >>> >>> I can view this file in most image viewers >>> >>> directly from the server connected to the printer (a raspberry pi with >>> exagear to run the brother software) >>> >>> using >>> >>> /usr/bin/scanimage "-v" "-p" "--batch=preview.jpg" "--batch-count" >>> "1" "--format" "jpeg" "-l" "0" "-t" "0" "-x" "215.9" "-y" "355.6" "-d" >>> "brother2:bus1;dev1" >>> >>> results in >>> >>> scanimage: rounded value of br-x from 215.9 to 215.88 >>> scanimage: rounded value of br-y from 355.6 to 355.567 >>> Scanning 1 pages, incrementing by 1, numbering from 1 >>> Scanning page 1 >>> scanimage: scanning image of size 1648x2314 pixels at 24 bits/pixel >>> scanimage: acquiring RGB frame >>> Progress: 100% >>> scanimage: min/max graylevel value = 11/255 >>> scanimage: read 11440416 bytes in total >>> Scanned page 1. (scanner status = 5) >>> >>> hexdump -c preview.jpg|head >>> >>> 000 P 6 \n # S A N E d a t a f >>> 010 o l l o w s \n 1 6 4 8 2 3 1 4 >>> 020 \n 2 5 5 \n \f 021 031 \r 022 032 \f 021 030 \f 021 >>> 030 030 \f 021 030 \f 021 030 \f 021 030 \r 022 031 \r 022 031 >>> 040 \f 023 031 \f 021 030 \f 021 030 \f 021 030 \f 021 031 \f >>> 050 021 030 \f 021 030 \f 021 030 \v 020 027 \f 021 030 \r 022 >>> 060 031 \v 020 027 \r 022 031 \f 023 031 \f 021 030 \f 021 030 >>> 070 \v 020 027 \r 022 032 \r 022 031 \f 021 030 \f 021 030 \f >>> 080 021 030 \f 021 030 \f 021 030 \v 020 027 \f 021 030 \f 021 >>> 090 030 \f 021 030 \f 021 030 \r 022 031 \r 024 032 \f 023 031 >>> >>> And I can clearly see text in the file that doesn't look right. >>> >>> P6
Re: [sane-devel] Weird behavior in exagear.
interesting I searched for "scanimage # sane data follows" and came across https://github.com/kkaempf/sane-backends/blob/master/frontend/scanimage.c and looking at that it looks like I was getting a pnm header even though I asked for a jpg. maybe I need to install jpg packages to use scanimage to output a jpeg? On Fri, Jan 5, 2018 at 2:53 PM, Jeff Sadowskiwrote: > Server side with saned > > root@raspberrypi:~:x86$ while [ 1 ];do saned -d 128;done > [saned] main: starting debug mode (level 2) > [saned] saned (AF-indep+IPv6) from sane-backends 1.0.24 starting up > [saned] do_bindings: [0] bind failed: Address already in use > [saned] check_host: access by remote host: :::192.168.1.252 > [saned] init: access granted to apache@:::192.168.1.252 > > gets to 96%ish then > > [saned] process_request: bad status 22 > [saned] bailing out, waiting for children... > [saned] bail_out: all children exited > [saned] main: starting debug mode (level 2) > [saned] saned (AF-indep+IPv6) from sane-backends 1.0.24 starting up > [saned] do_bindings: [0] bind failed: Address already in use > ^C > > > > On Fri, Jan 5, 2018 at 2:44 PM, Jeff Sadowski wrote: >> I started my scanner testing with my project. :-) My project phpsaneng >> seems to be working. >> >> The way I want to use my scanner, not so much. >> >> Maybe one of you would know what is happening here. I currently have 2 >> ways to connect to my scanner. Via saned or using scanimage directly. >> >> I was surprised that both methods fail in two different ways. >> >> using saned from a second server: >> >> /usr/bin/scanimage "-v" "-p" "--batch=preview.jpg" "--batch-count" >> "1" "--format" "jpeg" "-l" "0" "-t" "0" "-x" "215.9" "-y" "355.6" "-d" >> "net:192.168.1.27:brother2:bus1;dev1" >> >> results in >> >> scanimage: rounded value of br-x from 215.9 to 215.88 >> scanimage: rounded value of br-y from 355.6 to 355.567 >> Scanning 1 page, incrementing by 1, numbering from 1 >> Scanning page 1 >> scanimage: scanning image of size 1648x2314 pixels at 24 bits/pixel >> scanimage: acquiring RGB frame >> Progress: 96% >> scanimage: min/max graylevel value = 11/255 >> Application transferred too few scanlines >> >> hexdump -c preview.jpg.part|head looks like so >> >> 000 377 330 377 340 \0 020 J F I F \0 001 001 001 \0 310 >> 010 \0 310 \0 \0 377 333 \0 C \0 \b 006 006 \a 006 005 \b >> 020 \a \a \a \t \t \b \n \f 024 \r \f \v \v \f 031 022 >> 030 023 017 024 035 032 037 036 035 032 034 034 $ . ' >> 040 " , # 034 034 ( 7 ) , 0 1 4 4 4 037 ' >> 050 9 = 8 2 < . 3 4 2 377 333 \0 C 001 \t \t >> 060 \t \f \v \f 030 \r \r 030 2 ! 034 ! 2 2 2 2 >> 070 2 2 2 2 2 2 2 2 2 2 2 2 2 2 2 2 >> * >> 090 2 2 2 2 2 2 2 2 2 2 2 2 2 2 377 300 >> >> I can view this file in most image viewers >> >> directly from the server connected to the printer (a raspberry pi with >> exagear to run the brother software) >> >> using >> >> /usr/bin/scanimage "-v" "-p" "--batch=preview.jpg" "--batch-count" >> "1" "--format" "jpeg" "-l" "0" "-t" "0" "-x" "215.9" "-y" "355.6" "-d" >> "brother2:bus1;dev1" >> >> results in >> >> scanimage: rounded value of br-x from 215.9 to 215.88 >> scanimage: rounded value of br-y from 355.6 to 355.567 >> Scanning 1 pages, incrementing by 1, numbering from 1 >> Scanning page 1 >> scanimage: scanning image of size 1648x2314 pixels at 24 bits/pixel >> scanimage: acquiring RGB frame >> Progress: 100% >> scanimage: min/max graylevel value = 11/255 >> scanimage: read 11440416 bytes in total >> Scanned page 1. (scanner status = 5) >> >> hexdump -c preview.jpg|head >> >> 000 P 6 \n # S A N E d a t a f >> 010 o l l o w s \n 1 6 4 8 2 3 1 4 >> 020 \n 2 5 5 \n \f 021 031 \r 022 032 \f 021 030 \f 021 >> 030 030 \f 021 030 \f 021 030 \f 021 030 \r 022 031 \r 022 031 >> 040 \f 023 031 \f 021 030 \f 021 030 \f 021 030 \f 021 031 \f >> 050 021 030 \f 021 030 \f 021 030 \v 020 027 \f 021 030 \r 022 >> 060 031 \v 020 027 \r 022 031 \f 023 031 \f 021 030 \f 021 030 >> 070 \v 020 027 \r 022 032 \r 022 031 \f 021 030 \f 021 030 \f >> 080 021 030 \f 021 030 \f 021 030 \v 020 027 \f 021 030 \f 021 >> 090 030 \f 021 030 \f 021 030 \r 022 031 \r 024 032 \f 023 031 >> >> And I can clearly see text in the file that doesn't look right. >> >> P6 >> # SANE data follows >> >> Image viewers say it isn't an image. >> >> Any ideas what is going on given that data? >> >> Is there anything I can run to get more debug data? -- sane-devel mailing list: sane-devel@lists.alioth.debian.org http://lists.alioth.debian.org/cgi-bin/mailman/listinfo/sane-devel Unsubscribe: Send mail with subject
Re: [sane-devel] Weird behavior in exagear.
Server side with saned root@raspberrypi:~:x86$ while [ 1 ];do saned -d 128;done [saned] main: starting debug mode (level 2) [saned] saned (AF-indep+IPv6) from sane-backends 1.0.24 starting up [saned] do_bindings: [0] bind failed: Address already in use [saned] check_host: access by remote host: :::192.168.1.252 [saned] init: access granted to apache@:::192.168.1.252 gets to 96%ish then [saned] process_request: bad status 22 [saned] bailing out, waiting for children... [saned] bail_out: all children exited [saned] main: starting debug mode (level 2) [saned] saned (AF-indep+IPv6) from sane-backends 1.0.24 starting up [saned] do_bindings: [0] bind failed: Address already in use ^C On Fri, Jan 5, 2018 at 2:44 PM, Jeff Sadowskiwrote: > I started my scanner testing with my project. :-) My project phpsaneng > seems to be working. > > The way I want to use my scanner, not so much. > > Maybe one of you would know what is happening here. I currently have 2 > ways to connect to my scanner. Via saned or using scanimage directly. > > I was surprised that both methods fail in two different ways. > > using saned from a second server: > > /usr/bin/scanimage "-v" "-p" "--batch=preview.jpg" "--batch-count" > "1" "--format" "jpeg" "-l" "0" "-t" "0" "-x" "215.9" "-y" "355.6" "-d" > "net:192.168.1.27:brother2:bus1;dev1" > > results in > > scanimage: rounded value of br-x from 215.9 to 215.88 > scanimage: rounded value of br-y from 355.6 to 355.567 > Scanning 1 page, incrementing by 1, numbering from 1 > Scanning page 1 > scanimage: scanning image of size 1648x2314 pixels at 24 bits/pixel > scanimage: acquiring RGB frame > Progress: 96% > scanimage: min/max graylevel value = 11/255 > Application transferred too few scanlines > > hexdump -c preview.jpg.part|head looks like so > > 000 377 330 377 340 \0 020 J F I F \0 001 001 001 \0 310 > 010 \0 310 \0 \0 377 333 \0 C \0 \b 006 006 \a 006 005 \b > 020 \a \a \a \t \t \b \n \f 024 \r \f \v \v \f 031 022 > 030 023 017 024 035 032 037 036 035 032 034 034 $ . ' > 040 " , # 034 034 ( 7 ) , 0 1 4 4 4 037 ' > 050 9 = 8 2 < . 3 4 2 377 333 \0 C 001 \t \t > 060 \t \f \v \f 030 \r \r 030 2 ! 034 ! 2 2 2 2 > 070 2 2 2 2 2 2 2 2 2 2 2 2 2 2 2 2 > * > 090 2 2 2 2 2 2 2 2 2 2 2 2 2 2 377 300 > > I can view this file in most image viewers > > directly from the server connected to the printer (a raspberry pi with > exagear to run the brother software) > > using > > /usr/bin/scanimage "-v" "-p" "--batch=preview.jpg" "--batch-count" > "1" "--format" "jpeg" "-l" "0" "-t" "0" "-x" "215.9" "-y" "355.6" "-d" > "brother2:bus1;dev1" > > results in > > scanimage: rounded value of br-x from 215.9 to 215.88 > scanimage: rounded value of br-y from 355.6 to 355.567 > Scanning 1 pages, incrementing by 1, numbering from 1 > Scanning page 1 > scanimage: scanning image of size 1648x2314 pixels at 24 bits/pixel > scanimage: acquiring RGB frame > Progress: 100% > scanimage: min/max graylevel value = 11/255 > scanimage: read 11440416 bytes in total > Scanned page 1. (scanner status = 5) > > hexdump -c preview.jpg|head > > 000 P 6 \n # S A N E d a t a f > 010 o l l o w s \n 1 6 4 8 2 3 1 4 > 020 \n 2 5 5 \n \f 021 031 \r 022 032 \f 021 030 \f 021 > 030 030 \f 021 030 \f 021 030 \f 021 030 \r 022 031 \r 022 031 > 040 \f 023 031 \f 021 030 \f 021 030 \f 021 030 \f 021 031 \f > 050 021 030 \f 021 030 \f 021 030 \v 020 027 \f 021 030 \r 022 > 060 031 \v 020 027 \r 022 031 \f 023 031 \f 021 030 \f 021 030 > 070 \v 020 027 \r 022 032 \r 022 031 \f 021 030 \f 021 030 \f > 080 021 030 \f 021 030 \f 021 030 \v 020 027 \f 021 030 \f 021 > 090 030 \f 021 030 \f 021 030 \r 022 031 \r 024 032 \f 023 031 > > And I can clearly see text in the file that doesn't look right. > > P6 > # SANE data follows > > Image viewers say it isn't an image. > > Any ideas what is going on given that data? > > Is there anything I can run to get more debug data? -- sane-devel mailing list: sane-devel@lists.alioth.debian.org http://lists.alioth.debian.org/cgi-bin/mailman/listinfo/sane-devel Unsubscribe: Send mail with subject "unsubscribe your_password" to sane-devel-requ...@lists.alioth.debian.org
[sane-devel] Weird behavior in exagear.
I started my scanner testing with my project. :-) My project phpsaneng seems to be working. The way I want to use my scanner, not so much. Maybe one of you would know what is happening here. I currently have 2 ways to connect to my scanner. Via saned or using scanimage directly. I was surprised that both methods fail in two different ways. using saned from a second server: /usr/bin/scanimage "-v" "-p" "--batch=preview.jpg" "--batch-count" "1" "--format" "jpeg" "-l" "0" "-t" "0" "-x" "215.9" "-y" "355.6" "-d" "net:192.168.1.27:brother2:bus1;dev1" results in scanimage: rounded value of br-x from 215.9 to 215.88 scanimage: rounded value of br-y from 355.6 to 355.567 Scanning 1 page, incrementing by 1, numbering from 1 Scanning page 1 scanimage: scanning image of size 1648x2314 pixels at 24 bits/pixel scanimage: acquiring RGB frame Progress: 96% scanimage: min/max graylevel value = 11/255 Application transferred too few scanlines hexdump -c preview.jpg.part|head looks like so 000 377 330 377 340 \0 020 J F I F \0 001 001 001 \0 310 010 \0 310 \0 \0 377 333 \0 C \0 \b 006 006 \a 006 005 \b 020 \a \a \a \t \t \b \n \f 024 \r \f \v \v \f 031 022 030 023 017 024 035 032 037 036 035 032 034 034 $ . ' 040 " , # 034 034 ( 7 ) , 0 1 4 4 4 037 ' 050 9 = 8 2 < . 3 4 2 377 333 \0 C 001 \t \t 060 \t \f \v \f 030 \r \r 030 2 ! 034 ! 2 2 2 2 070 2 2 2 2 2 2 2 2 2 2 2 2 2 2 2 2 * 090 2 2 2 2 2 2 2 2 2 2 2 2 2 2 377 300 I can view this file in most image viewers directly from the server connected to the printer (a raspberry pi with exagear to run the brother software) using /usr/bin/scanimage "-v" "-p" "--batch=preview.jpg" "--batch-count" "1" "--format" "jpeg" "-l" "0" "-t" "0" "-x" "215.9" "-y" "355.6" "-d" "brother2:bus1;dev1" results in scanimage: rounded value of br-x from 215.9 to 215.88 scanimage: rounded value of br-y from 355.6 to 355.567 Scanning 1 pages, incrementing by 1, numbering from 1 Scanning page 1 scanimage: scanning image of size 1648x2314 pixels at 24 bits/pixel scanimage: acquiring RGB frame Progress: 100% scanimage: min/max graylevel value = 11/255 scanimage: read 11440416 bytes in total Scanned page 1. (scanner status = 5) hexdump -c preview.jpg|head 000 P 6 \n # S A N E d a t a f 010 o l l o w s \n 1 6 4 8 2 3 1 4 020 \n 2 5 5 \n \f 021 031 \r 022 032 \f 021 030 \f 021 030 030 \f 021 030 \f 021 030 \f 021 030 \r 022 031 \r 022 031 040 \f 023 031 \f 021 030 \f 021 030 \f 021 030 \f 021 031 \f 050 021 030 \f 021 030 \f 021 030 \v 020 027 \f 021 030 \r 022 060 031 \v 020 027 \r 022 031 \f 023 031 \f 021 030 \f 021 030 070 \v 020 027 \r 022 032 \r 022 031 \f 021 030 \f 021 030 \f 080 021 030 \f 021 030 \f 021 030 \v 020 027 \f 021 030 \f 021 090 030 \f 021 030 \f 021 030 \r 022 031 \r 024 032 \f 023 031 And I can clearly see text in the file that doesn't look right. P6 # SANE data follows Image viewers say it isn't an image. Any ideas what is going on given that data? Is there anything I can run to get more debug data? -- sane-devel mailing list: sane-devel@lists.alioth.debian.org http://lists.alioth.debian.org/cgi-bin/mailman/listinfo/sane-devel Unsubscribe: Send mail with subject "unsubscribe your_password" to sane-devel-requ...@lists.alioth.debian.org