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

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 Meeuwissen wrote: > Hi Jeff, > > Jeff Sadowski writes: > >> My code is simply calling

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

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

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

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

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? >

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 Sadowski wrote: > I wonder it it works

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

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

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 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. > >

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

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

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

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 Sadowski wrote: > I pulled the current git of sane-backend from >

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

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

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

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

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

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

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 Sadowski wrote: > So, renaming my image from the

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 Sadowski wrote: > interesting I searched for "scanimage # sane data follows" and came

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

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: