[sane-devel] Canoscan LiDE 30 getting stuck on usbio_DetectLM983x
On Fri, Apr 12, 2013 at 10:41:38AM +0200, Gerhard J?ger wrote: [...] hmmm, doesn't look good. We have some similar issues reported here: https://alioth.debian.org/tracker/index.php?func=detailaid=314021group_id=30186atid=410366 In that case a HP2200. Tried it on two older machines (RHEL 5.6 and 5.8, amd64) today. Scanning (LiDE 30/N1240U) worked perfectly on both. That was sane-1.0.18.
[sane-devel] Canoscan LiDE 30 getting stuck on usbio_DetectLM983x
On Friday 19 April 2013 13:12:45 Serge Klink wrote: On Fri, Apr 12, 2013 at 10:41:38AM +0200, Gerhard J?ger wrote: [...] hmmm, doesn't look good. We have some similar issues reported here: https://alioth.debian.org/tracker/index.php?func=detailaid=314021group_id=30186atid=410366 In that case a HP2200. Tried it on two older machines (RHEL 5.6 and 5.8, amd64) today. Scanning (LiDE 30/N1240U) worked perfectly on both. That was sane-1.0.18. Interesting. Just a wild guess - I think the problem is related to then newer libusb1... - we need to check this. Thanks for digging deeper, Gerhard
[sane-devel] Canoscan LiDE 30 getting stuck on usbio_DetectLM983x
On Fri, Apr 19, 2013 at 08:11:55AM +0200, Gerhard J?ger wrote:
On Friday 19 April 2013 13:12:45 Serge Klink wrote:
On Fri, Apr 12, 2013 at 10:41:38AM +0200, Gerhard J?ger wrote:
[...]
hmmm, doesn't look good. We have some similar issues reported here:
https://alioth.debian.org/tracker/index.php?func=detailaid=314021group_id=30186atid=410366
In that case a HP2200.
Tried it on two older machines (RHEL 5.6 and 5.8, amd64) today.
Scanning (LiDE 30/N1240U) worked perfectly on both.
That was sane-1.0.18.
Interesting. Just a wild guess - I think the problem is related to then newer
libusb1... - we need to check this.
Indeed... Installing 1.0.18 on the newer Debian machine made no
difference. (It's a Sony laptop with a USB3.0 controller - perhaps
it's some obscure issue with the xhci_hcd module or something.)
Just for kicks, I ran strace scanimage -L and got stuff like:
...
read(3, # Plustek-SANE Backend configura..., 4096) = 4096
read(3, uto\n\n#\n# to define a new device,..., 4096) = 70
read(3, , 4096) = 0
close(3)= 0
munmap(0x7fd7aaccf000, 4096)= 0
open(/dev/bus/usb/003/003, O_RDWR)= 3
ioctl(3, USBDEVFS_SETCONFIGURATION, 0x7fff20d6be3c) = 0
ioctl(3, USBDEVFS_CLAIMINTERFACE, 0x7fff20d6be3c) = 0
ioctl(3, USBDEVFS_SUBMITURB or USBDEVFS_SUBMITURB32, 0x7fff20d6bd70) = 0
ioctl(3, USBDEVFS_REAPURBNDELAY or USBDEVFS_REAPURBNDELAY32, 0x7fff20d6bd38) = 0
ioctl(3, USBDEVFS_SUBMITURB or USBDEVFS_SUBMITURB32, 0x7fff20d6bd70) = 0
ioctl(3, USBDEVFS_REAPURBNDELAY or USBDEVFS_REAPURBNDELAY32, 0x7fff20d6bd38) =
-1 EAGAIN (Resource temporarily unavailable)
select(4, NULL, [3], NULL, {0, 1000}) = 0 (Timeout)
ioctl(3, USBDEVFS_REAPURBNDELAY or USBDEVFS_REAPURBNDELAY32, 0x7fff20d6bd38) =
-1 EAGAIN (Resource temporarily unavailable)
select(4, NULL, [3], NULL, {0, 1000}) = 0 (Timeout)
ioctl(3, USBDEVFS_REAPURBNDELAY or USBDEVFS_REAPURBNDELAY32, 0x7fff20d6bd38) =
-1 EAGAIN (Resource temporarily unavailable)
select(4, NULL, [3], NULL, {0, 1000}) = 0 (Timeout)
ioctl(3, USBDEVFS_REAPURBNDELAY or USBDEVFS_REAPURBNDELAY32, 0x7fff20d6bd38) =
-1 EAGAIN (Resource temporarily unavailable)
select(4, NULL, [3], NULL, {0, 1000}) = 0 (Timeout)
ioctl(3, USBDEVFS_REAPURBNDELAY or USBDEVFS_REAPURBNDELAY32, 0x7fff20d6bd38) =
-1 EAGAIN (Resource temporarily unavailable)
select(4, NULL, [3], NULL, {0, 1000}) = 0 (Timeout)
...the last two lines repeating endlessly.
Also, scanimage *does* detect the scanner (before getting stuck on
usbio_DetectLM983x), but only the *first* time it is ran after
plugging in the scanner... or so it seems.
[sane-devel] Canoscan LiDE 30 getting stuck on usbio_DetectLM983x
Hi, On Thursday 11 April 2013 12:20:27 Serge Klink wrote: [...] I've got a Canoscan LiDE 30 here that just won't play nicely with SANE... This is what happens when plugging it in and trying scanimage -L: http://pastebin.com/PnaGaJU1 ... [plustek] usbDev_open(auto,) - 0x10dc7b0 [plustek] Vendor ID=0x04A9, Product ID=0x220E [plustek] usbio_DetectLM983x (after waiting for a while) [plustek] * could not read version register! [plustek] open failed: -1 [plustek] sane_get_devices (0x7fff275a03c8, 0) hmmm, doesn't look good. We have some similar issues reported here: https://alioth.debian.org/tracker/index.php?func=detailaid=314021group_id=30186atid=410366 In that case a HP2200. Now, if I plug it in, start VirtualBox/WinXP, let it take over/initialize the scanner, THEN repeat: [...] Could you be more precise. Do you simply start the VirtualBox, or do you start also inside the CanoScan device driver or similar? - Gerhard
[sane-devel] Canoscan LiDE 30 getting stuck on usbio_DetectLM983x
On 2013-04-12 17:41, Gerhard J?ger wrote: [..] Now, if I plug it in, start VirtualBox/WinXP, let it take over/initialize the scanner, THEN repeat: [...] Could you be more precise. Do you simply start the VirtualBox, or do you start also inside the CanoScan device driver or similar? Hi, It's a 32-bit WinXP virtual machine with Canon's drivers installed inside, running on a 64-bit Linux (Debian Wheezy) host. The procedure is: 1. Plug in the scanner (physically). (Scanner is recognized by the host Linux kernel. No external signs of life - lamp does not turn on, motor does not move, etc.) 2. Run scanimage -L (on the host). (Still no signs of life, error on usbio_DetectLM983x) 3. Start VBox, boot up the virtual machine normally. 4. Connect the scanner to the virtual machine (from Virtualbox's menu). (Scanner starts moving, calibrating (?) itself, etc.) 5. Disconnect the scanner from the virtual machine (but leave it connected physically to the host), power the VM down. 6. Run scanimage -L again (on the host). (Finds the scanner quickly, no errors.) Also tried installing 32-bit libsane and sane-utils (1.0.22 from the i386 repo) - no difference. Haven't tried it with a full 32-bit system yet.
