[sane-devel] Help needed diagnosing strange failure to scan with Samsung SCX-4500W

I have a strange scanner failure to try to resolve, and I am hoping that an expert on this list may be able to help me fix the problem. I have a Samsung SCX-4500W multifunction printer that is plugged in to the usb port of my main machine running arch linux x86_64. The printer part works fine wit

[sane-devel] Help needed diagnosing strange failure to scan with Samsung SCX-4500W

On Mon, May 6, 2013 at 9:12 PM, Mike Cloaked wrote: > I have a strange scanner failure to try to resolve, and I am hoping that > an expert on this list may be able to help me fix the problem. > > I have a Samsung SCX-4500W multifunction printer that is plugged in to the > usb

[sane-devel] Help needed diagnosing strange failure to scan with Samsung SCX-4500W

Hi Theodore Thank you very much for your long reply - much of what you say sounds right to me, and indeed I had wondered myself whether there was a conflict "somewhere" between the printer and scanner support within the system but I don't know how to resolve it. I have googled and found a number o

[sane-devel] Help needed diagnosing strange failure to scan with Samsung SCX-4500W

On Thu, May 9, 2013 at 7:49 PM, Mike Cloaked wrote: > Hi Theodore > > >> When you successfully scan on the laptop, when did you hook up the >> scanner? Before booting? Or after? >> >> After booting. > I just ran a new test with the printer already plugged in d

[sane-devel] Help needed diagnosing strange failure to scan with Samsung SCX-4500W

On Thu, May 9, 2013 at 8:00 PM, Mike Cloaked wrote: > > As above - printer is hooked up to laptop which is then booted - scanning > works fine. The printer is not set up on that machine. > > When I plugged the printer back into the desktop after running the laptop test the syst

[sane-devel] Help needed diagnosing strange failure to scan with Samsung SCX-4500W

On Fri, May 10, 2013 at 1:58 AM, Theodore Kilgore < kilgota at banach.math.auburn.edu> wrote: > > This is weird. The "configuration and setup of the printer allegedly > fails, but it works? > Indeed! However I am now wondering if this is due to a udev conflict - I will add details further down.

[sane-devel] Help needed diagnosing strange failure to scan with Samsung SCX-4500W

On Fri, May 10, 2013 at 9:20 AM, Mike Cloaked wrote: I made a typo in my last post which I will correct below: > > I am wondering now about udev more than libusb - > > In /lib/udev/rules.d/53-sane.rules > > there is a rule for the scanner: > > # Samsung SCX-4500W > ATT

[sane-devel] Help needed diagnosing strange failure to scan with Samsung SCX-4500W

On Fri, Jun 14, 2013 at 5:20 PM, Mike Cloaked wrote: > Hi Thorsten > > > On Fri, Jun 14, 2013 at 11:25 AM, Thorsten M?ller < > thorsten at mueller-kleinheinz.de> wrote: > >> >> I just did a quick google search. Since I don't know how archlinux >> h

[sane-devel] Canon LiDE 210 scans only once before needing its USB cable replugged

On Sat, Jun 29, 2013 at 7:41 PM, Sean Whitton wrote: > Hello, > > I am using a Canon LiDE 210 with SANE 1.0.22, backends 1.0.22 on > Debian Wheezy. I can perform one scan just fine, but then in order to > do another I have to unplug and then reconnect the scanner's USB > cable. I have attached

[sane-devel] Canon LiDE 210 scans only once before needing its USB cable replugged

On Sat, Jun 29, 2013 at 10:16 PM, Simon Matter wrote: > > > Do you connect it via USB 3 port? > > Is there a known problem connecting via usb3? -- mike c -- next part -- An HTML attachment was scrubbed... URL:

[sane-devel] Canonscan N 650U LIDE Scanner does not scan but makes terrible noise

On Sat, Aug 10, 2013 at 11:45 AM, wrote: > Hi, > > my Canonscan N 650U LIDE Scanner does not scan but makes terrible noise, > as if the scan unit is going in the wrong direction. The scanner works fine > with Win XP 32-bit > > OS: Linux Kanotix Dragonfire (Debian based) 64-bit > scanimage (sane-

[sane-devel] Scanner failure when connected via USB3

For some time I have been having an issue with xsane hanging when connecting to a Canoscan LIDE 210 flatbed scanner with a laptop that only has USB3 ports, when the same scanner works flawlessly when connected to a laptop which only has USB2 ports. I have seen similar issues reported for other sca

Re: [sane-devel] Scanner failure when connected via USB3

On Tue, Sep 23, 2014 at 11:57 PM, Olaf Meeuwissen wrote: > > m. allan noah writes: > > > Mike- when you get back to the machine, maybe you could make some > > logs. If we could see a usb log of what scanimage does and what > > vuescan does, we might be able to find a difference. The problem will

Re: [sane-devel] Scanner failure when connected via USB3

On Mon, Oct 27, 2014 at 10:25 AM, Mike Cloaked wrote: > On Sun, Oct 26, 2014 at 4:28 PM, Mike Cloaked > wrote: > >> On Tue, Sep 23, 2014 at 11:57 PM, Olaf Meeuwissen < >> olaf.meeuwis...@avasys.jp> wrote: >> >>> >>> m. allan noah writes: >

Re: [sane-devel] Scanner failure when connected via USB3

On Mon, Oct 27, 2014 at 3:36 PM, Mike Cloaked wrote: > On Mon, Oct 27, 2014 at 11:20 AM, m. allan noah > wrote: > >> try compressing your attachments. >> >> allan >> >> > Here are the two attachments gzipped. Hopefully this will be within the > file

Re: [sane-devel] Scanner failure when connected via USB3

On Mon, Oct 27, 2014 at 3:45 PM, Mike Cloaked wrote: > On Mon, Oct 27, 2014 at 3:36 PM, Mike Cloaked > wrote: > >> On Mon, Oct 27, 2014 at 11:20 AM, m. allan noah >> wrote: >> >>> try compressing your attachments. >>> >>> allan >>&

Re: [sane-devel] Scanner failure when connected via USB3

On Tue, Oct 28, 2014 at 12:02 AM, Olaf Meeuwissen wrote: > > The idea is that you start/stop capturing USB traffic with wireshark > rather than cat whatever is left in the /sys/kernel/debug/usb/usbmon/ > files. Wireshark will read off that and presents you with an easier to > digest view of what

Re: [sane-devel] Scanner failure when connected via USB3

On Tue, Oct 28, 2014 at 1:21 PM, m. allan noah wrote: > I was able to somewhat parse the logs using a bit of perl. I am > suprised about the difference in file size. Where you making the scans > with the same parameters in both cases? > > allan > > > OK - I have been working on this with a bit of

Re: [sane-devel] Scanner failure when connected via USB3

On Tue, Oct 28, 2014 at 4:00 PM, Mike Cloaked wrote: > > OK - I have been working on this with a bit of free time today. First to > answer your question the vuescan scan of the sample document completed > without error whereas the scan with xsane failed to complete and hung >

Re: [sane-devel] Scanner failure when connected via USB3

On Tue, Oct 28, 2014 at 11:28 PM, Olaf Meeuwissen wrote: > > Mike Cloaked writes: > > > Secondly i set up wireshark this afternoon, and got it all running to > > capture usb data on the bus that the scanner is connected to. Having > > completed a capture for a vu

Re: [sane-devel] Scanner failure when connected via USB3

On Wed, Oct 29, 2014 at 9:48 AM, Mike Cloaked wrote: > > > Yes I do have the full list of packages that were updated in the pacman > log - I am away from that laptop at the moment, but later today I will post > the full list of updated packages from the pacman log. Yes it was bo

Re: [sane-devel] Scanner failure when connected via USB3

I have run some more tests this evening - after starting the wireshark program, I set the systemd journal to log with -f to watch output, and first simply plugged in the scanner. Journal log gave: ct 29 19:39:51 lenovo2 kernel: usb 3-4: new high-speed USB device number 4 using xhci_hcd Oct 29 19:3

Re: [sane-devel] Scanner failure when connected via USB3

Here is the text packet dissector file for when xsane was started and hung at acquire preview. It is gzipped to stay within the size limit. The packet stream file was too big even if gzipped but if needed I can put it on a cloud file. -- mike c wireshark-packet-dissection-xsane-acquire-preview

Re: [sane-devel] Scanner failure when connected via USB3

On Wed, Oct 29, 2014 at 8:01 PM, Mike Cloaked wrote: > I have run some more tests this evening - after starting the wireshark > program, I set the systemd journal to log with -f to watch output, and > first simply plugged in the scanner. > > Journal log gave: > ct 29 19:39:51 l

Re: [sane-devel] Scanner failure when connected via USB3

> I have also been googling for similar issues and there are a number of similar bug reports in the mailing lists of various linux distributions where people have found sb2 scanners failing to work when connected to usb3 ports in the past year. One such report is in the kernel bugzilla at https://

Re: [sane-devel] Scanner failure when connected via USB3

On Wed, Oct 29, 2014 at 9:09 PM, Mike Cloaked wrote: > > I have also been googling for similar issues and there are a number of > similar bug reports in the mailing lists of various linux distributions > where people have found sb2 scanners failing to work when connected to usb3 &g

Re: [sane-devel] Scanner failure when connected via USB3

On Fri, Oct 31, 2014 at 8:58 AM, Olaf Meeuwissen wrote: > Hi Mike, > > First of all, apologies for the somewhat belated reply. I will try to > piece all the bits from your flurry of mails that followed this one > together in this reply. > > snip > I had an admittedly cursory look at your USB c

Re: [sane-devel] Scanner failure when connected via USB3

On Fri, Oct 31, 2014 at 12:36 PM, Simon Matter wrote: > > The key point here, and the reason I asked for these logs initially, > > was your ability to scan properly with vuescan, and not with sane. My > > hope was that you could make the absolute smallest scan with identical > > parameters in bot

Re: [sane-devel] Scanner failure when connected via USB3

On Tue, Nov 4, 2014 at 1:52 AM, m. allan noah wrote: > I've tried to make sense of these logs, but they seem to contain data > from multiple devices, and none of it looks like commands for a > fujitsu scanner. Can you try again to capture something from the > scanner specifically, instead of the

Re: [sane-devel] Scanner failure when connected via USB3

It looks like there is long standing related work still continuing to make progress on a possible fix in the xhci usb kernel code for usb2 scanners being problematic when plugged into usb3 ports - see the thread at: http://www.spinics.net/lists/linux-usb/msg120507.html Maybe at some point there

Re: [sane-devel] Scanner failure when connected via USB3

On Wed, Feb 4, 2015 at 9:00 PM, m. allan noah wrote: > I hit send before I finished writing: I also am hopeful that we can > fix this issue for real in the kernel- the patch discussed in that > thread seems to perform the same action as my workaround. An in-kernel > fix will correct this for many