[sane-devel] Recent NM-1000
stef
stef.dev at free.fr
Sat Jun 4 06:58:32 UTC 2011
Le jeudi 2 juin 2011 20:05:25 Paul Ericson, vous avez écrit :
> Removed all old sane and compiled and installed 1.0.22.
> Tried a couple of different things.
> The mods in /var/lib/misc/usb.ids are adding two lines:
> 1ebb NuCORE Technology, Inc.Added-> 1f44 The
> Neat CompanyAdded-> 0001 NM-1000 Mobile Scanner
> 2001 D-Link Corp. [hex] 0001 DWL-120
> WIRELESS ADAPTER #1 Left mods in /var/lib/misc/usb.ids. Here is what
> "sane-find-scanner -v -v" shows: Couldn't set configuration: could not set
> config 1: Operation not permitted<This USB chip looks like a GL846?
> (result from sane-backends 1.0.22)> found USB scanner (vendor=0x1f44,
> product=0x0001, chip=GL846?) at libusb:002:004 #2 Left mods in
> /var/lib/misc/usb.ids. Here is what "sudo sane-find-scanner -v -v" shows:
> <Couldn't determine the type of the USB chip (result from sane-backends
> 1.0.22)> found USB scanner (vendor=0x1f44 [The Neat Company ],
> product=0x0001 [Neat Mobile Scanner]) at libusb:002:004
>
> #3 Commented out the two added lines above, ran "sane-find-scanner -v -v",
> it says: Couldn't set configuration: could not set config 1: Operation not
> permitted<This USB chip looks like a GL846? (result from sane-backends
> 1.0.22)> found USB scanner (vendor=0x1f44, product=0x0001, chip=GL846?) at
> libusb:002:004
>
> #4 Commented out the two added lines above, ran "sudo sane-find-scanner -v
> -v", it says:
> <Couldn't determine the type of the USB chip (result from sane-backends
> 1.0.22)> found USB scanner (vendor=0x1f44 [The Neat Company ],
> product=0x0001 [Neat Mobile Scanner]) at libusb:002:004 Interestingly,
> when I run sudo sane-find-scanner, it appears to check for more chipsets.
> Where as when I run it normally, it stops on GL84x.
>
> Is "Couldn't set configuration: could not set config 1: Operation not
> permitted" as permissions issue or a configuration issue? (Or should I
> ignore it?) Thanks,
> Paul
> I do not authorize any party to give away, publish or sell this e-mail
> address. Its use is only for correspondence with me. I also do not consent
> to receiving any unsolicited e-mail from any parties.
>
>
>
>
>
> Help Can the SPAM!
>
> --- On Thu, 6/2/11, stef <stef.dev at free.fr> wrote:
>
> From: stef <stef.dev at free.fr>
> Subject: Re: [sane-devel] Recent NM-1000
> To: sane-devel at lists.alioth.debian.org
> Cc: "Paul Ericson" <paulsonntagericson at yahoo.ca>
> Received: Thursday, June 2, 2011, 4:13 AM
>
> Le mercredi 1 juin 2011 22:52:26 Paul Ericson, vous avez écrit :
> > I recently got a NM-1000 mobile scanner. I have not been able to get it
> > working under sane. I've attached the output from sane-find-scanner -v -v
> > and usb-devices (I'm running Ubuntu 10.04 which has no /proc/bus/usb).
> > The scanner wouldn't even show up in lsusb until I modified
> > /var/lib/misc/usb.ids. Any thoughts on which sane driver and firmware
> > file I should try? (I've tried a couple
>
> with no
> luck) Thanks,
>
> > Paul
> >
> > I do not authorize any party to give away, publish or sell this e-mail
> > address. Its use is only for correspondence with me. I also do not
> > consent to receiving any unsolicited e-mail from any parties.
> >
> >
> >
> >
> >
> > Help Can the SPAM!
>
> Hello,
>
> to help find the exact chip it is, can you run sane-find-scanner from
> SANE 1.0.22 (just need to compile it and run the freshly compiled
> sane-find- scanner from local directory without installing it). The
> version you used is older. There is a possibility it is gl124 based.
>
> Another source of information is using usbsnoop under windows and send
> me the log generated when scanner is plugged in. I'd be able to check if
> it is a genesys chip.
>
> Such scanners are often clones of gt68xx supported scanner. In
> that case,
> an USB log will also tell it.
>
> Regards,
> Stef
Hello,
I checked -with proper permissions- that my optic slim M12 is detected by
sane-find-scanner. Since this hasn't been the case for you, I think we may
rule out a gt68xx clone. With a gl124 based scanner, the chip is correctly
detected. So I relally think that the last option is to use usbsnoop under
windows to have a chance of identifying the asic in your scanner.
Regards,
Stef
More information about the sane-devel
mailing list