This is the result of cat /proc/bus/usb/devices around scanner section... T: Bus=02 Lev=02 Prnt=02 Port=00 Cnt=01 Dev#= 10 Spd=12 MxCh= 0 D: Ver= 1.10 Cls=00(>ifc ) Sub=00 Prot=00 MxPS= 8 #Cfgs= 1 P: Vendor=04a7 ProdID=0224 Rev= 1.00 S: Manufacturer=Visioneer S: Product=USB Scanner S: SerialNumber=RTS8801B-0001 C:* #Ifs= 1 Cfg#= 1 Atr=e0 MxPwr= 0mA I: If#= 0 Alt= 0 #EPs= 3 Cls=00(>ifc ) Sub=00 Prot=00 Driver=(none) E: Ad=81(I) Atr=02(Bulk) MxPS= 64 Ivl= 0ms E: Ad=02(O) Atr=02(Bulk) MxPS= 8 Ivl= 0ms E: Ad=83(I) Atr=03(Int.) MxPS= 1 Ivl=250ms
On 2001.12.09 12:49 Henning Meier-Geinitz wrote: > Hi, > > On Sat, Dec 08, 2001 at 09:49:55PM -0600, David Cougle wrote: > > Despite loading usb scanner module in 2.4.16, sane-find-scanner does > not > > find the scanner. Is this bad news? > > This usually means that the scanner module doesn't know your scanner. > You should be able to find out about the vendor and device ids with > "cat /proc/bus/usb/devices". Then unload the scanner module with > "rmmod scanner" (if it was loaded). Load it again with > "modprobe scanner vendor=0x1000 product=0x400". Use the vndor and > product ids you got from the above output. Now "cat > /proc/bus/usb/devices" should list youz scanner with > "Driver=usbscanner". > > However this doesn't mean that there is any SANE backend that provides > support for the scanner. Can you provide more details about which > chipset is used in the scanner? What are the vvvendor and product ids? > > Bye, > Henning > _______________________________________________ > Sane-devel mailing list > [email protected] > http://www.mostang.com/mailman/listinfo/sane-devel > -- http://www.mp3.com/lunarbard ICQ #3795561, Yahoo IM lunarbard1979 lunarbard on AOL(Instant Messenger) Microsoft Messenger dcougle 1 John 4:11
