[sane-devel] CanoScan 4400F
Hi all, I am trying to connect a CanoScan 4400F to mu Ubuntu 7.10 distro. I have compiled and installed the following: - sane-backends-1.0.18 - libusb-0.1.8 After updating /etc/fstab with 'usbfs' parameters I obtained the following result freom sane-find-scanner: found USB scanner (vendor=0x04a9 [Canon], product=0x2228 [CanoScan], chip=GL841) at libusb:005:002 Now I read on sane main page that GL841 is referred to Genesys backend, so I have updated /etc/sane.d/genesys.conf and /etc/hotplug/usb/libsane.usermap with the parameters read back by sane-find-scanner. But, when I try to run Xsane, nothing happens, the unique message is "No device found". Just to complete, this is the output of /proc/usb/devices == T: Bus=05 Lev=01 Prnt=01 Port=00 Cnt=01 Dev#= 2 Spd=480 MxCh= 0 D: Ver= 2.00 Cls=ff(vend.) Sub=ff Prot=ff MxPS=64 #Cfgs= 1 P: Vendor=04a9 ProdID=2228 Rev= 5.00 S: Manufacturer=Canon S: Product=CanoScan C:* #Ifs= 1 Cfg#= 1 Atr=c0 MxPwr= 10mA I:* If#= 0 Alt= 0 #EPs= 3 Cls=ff(vend.) Sub=ff Prot=ff Driver=(none) E: Ad=81(I) Atr=02(Bulk) MxPS= 512 Ivl=0ms E: Ad=02(O) Atr=02(Bulk) MxPS= 512 Ivl=0ms E: Ad=83(I) Atr=03(Int.) MxPS= 1 Ivl=16ms == I don't have any idea in how to proceed further. Can someone help me? Thanks
[sane-devel] Microtek ScanMaker 4900 (USB2400) and Qemu
Ok, so I got the Microtek ScanMaker 4900 (USB2400) to work under Linux as follows: Linux Fedora 8 -> Qemu 0.9.0 -> Windows 98 SE -> Microtek ScanWizard 5 What would be the next step? Any idea? -- Adam Sulmicki http://www.eax.com The Supreme Headquarters of the 32 bit registers
[sane-devel] CanoScan LiDE30 problem
Am Montag, 3. Dezember 2007 11:08:15 schrieb Johannes Ranke: > Hi, > > My Canoscan LiDE30 used to work nicely under Debian unstable for more > than a year. Since about half a year it makes problems: If I scan from a > frontend like quiteinsane, I can select the device (I am using libusb), > and the frontend pretends to scan, but the scanner does nothing, so I > end up with a black image. The scanner works under Windows. Last week, > after I tested under Windows, it worked under Linux, too. This is a know issue and relatet to the suspend feature on the kernel you are using, disable the CONFIG_USB_SUSPEND kernel config option and recompile the kernel. Thought this has been fixed in more recent versions. Maybe there are some motr better ideas around - or check this list for USB_SUSPEND... HTH Gerhard
[sane-devel] CanoScan LiDE30 problem
On Mon, 2007-12-03 at 11:08 +0100, Johannes Ranke wrote: > Hi, > > My Canoscan LiDE30 used to work nicely under Debian unstable for more > than a year. Since about half a year it makes problems: If I scan from a > frontend like quiteinsane, I can select the device (I am using libusb), > and the frontend pretends to scan, but the scanner does nothing, so I > end up with a black image. The scanner works under Windows. Last week, > after I tested under Windows, it worked under Linux, too. > > $ scanimage -L > device `v4l:/dev/video0' is a Noname BT878 video (AVerMedia AVerTV D > virtual device > device `plustek:libusb:003:003' is a Canon CanoScan N1240U/LiDE30 > flatbed scanner > > I discovered that I can scan from the command line as normal user: > > $ SANE_DEBUG_PLUSTEK=128 scanimage -d 'plustek:libusb:003:003' \ > > image.pnm \ > 2> canoscanLiDE30.err > > I am attaching the output of this. Graphical frontends still don't work, > even when specifying the device on the command line for xscanimage, or > selecting it in quiteinsane. > > I also noticed the following dmesg output after trying to scan with > xscanimage: > > usb 3-2: usbfs: interface 0 claimed by usbfs while 'xscanimage' sets > config #1 > > I don't know which (combination of) software is reponsible for the > problems, otherwise I would file a bug report in the Debian BTS. > > My kernel is: > $ uname -a > Linux stiller 2.6.20-1-amd64 #1 SMP Tue Apr 24 21:10:58 UTC 2007 > x86_64 GNU/Linux > > Sane version is: > > $ scanimage -V > scanimage (sane-backends) 1.0.18-cvs; backend version 1.0.18 > > Best regards, > > Johannes Add a # before the v4l line in /etc/sane.d/dll.conf this will disable the v4l backend and will prevent that your video device is selected. > > > m.vr.gr. > Gerard Klaver
[sane-devel] CanoScan 4400F
it appears your scanner is unsupported: http://www.sane-project.org/lists/sane-mfgs-cvs.html http://www.sane-project.org/unsupported/canon-4400.html Mike C > From: lorenzo.travaglio at fastwebnet.it > To: sane-devel at lists.alioth.debian.org > Date: Mon, 3 Dec 2007 23:11:47 +0100 > Subject: [sane-devel] CanoScan 4400F > > Hi all, > I am trying to connect a CanoScan 4400F to mu Ubuntu 7.10 distro. > > I have compiled and installed the following: > > - sane-backends-1.0.18 > - libusb-0.1.8 > > After updating /etc/fstab with 'usbfs' parameters I obtained the > following result freom sane-find-scanner: > > found USB scanner (vendor=0x04a9 [Canon], product=0x2228 [CanoScan], > chip=GL841) at libusb:005:002 > > Now I read on sane main page that GL841 is referred to Genesys backend, > so I have updated /etc/sane.d/genesys.conf > and /etc/hotplug/usb/libsane.usermap with the parameters read back by > sane-find-scanner. > > But, when I try to run Xsane, nothing happens, the unique message is "No > device found". > > Just to complete, this is the output of /proc/usb/devices > > == > T: Bus=05 Lev=01 Prnt=01 Port=00 Cnt=01 Dev#= 2 Spd=480 MxCh= 0 > D: Ver= 2.00 Cls=ff(vend.) Sub=ff Prot=ff MxPS=64 #Cfgs= 1 > P: Vendor=04a9 ProdID=2228 Rev= 5.00 > S: Manufacturer=Canon > S: Product=CanoScan > C:* #Ifs= 1 Cfg#= 1 Atr=c0 MxPwr= 10mA > I:* If#= 0 Alt= 0 #EPs= 3 Cls=ff(vend.) Sub=ff Prot=ff Driver=(none) > E: Ad=81(I) Atr=02(Bulk) MxPS= 512 Ivl=0ms > E: Ad=02(O) Atr=02(Bulk) MxPS= 512 Ivl=0ms > E: Ad=83(I) Atr=03(Int.) MxPS= 1 Ivl=16ms > == > > I don't have any idea in how to proceed further. Can someone help me? > Thanks > > > -- > sane-devel mailing list: sane-devel at lists.alioth.debian.org > http://lists.alioth.debian.org/mailman/listinfo/sane-devel > Unsubscribe: Send mail with subject "unsubscribe your_password" > to sane-devel-request at lists.alioth.debian.org _ Your smile counts. The more smiles you share, the more we donate.? Join in. www.windowslive.com/smile?ocid=TXT_TAGLM_Wave2_oprsmilewlhmtagline
[sane-devel] CanoScan LiDE30 problem
Hi, My Canoscan LiDE30 used to work nicely under Debian unstable for more than a year. Since about half a year it makes problems: If I scan from a frontend like quiteinsane, I can select the device (I am using libusb), and the frontend pretends to scan, but the scanner does nothing, so I end up with a black image. The scanner works under Windows. Last week, after I tested under Windows, it worked under Linux, too. $ scanimage -L device `v4l:/dev/video0' is a Noname BT878 video (AVerMedia AVerTV D virtual device device `plustek:libusb:003:003' is a Canon CanoScan N1240U/LiDE30 flatbed scanner I discovered that I can scan from the command line as normal user: $ SANE_DEBUG_PLUSTEK=128 scanimage -d 'plustek:libusb:003:003' \ > image.pnm \ 2> canoscanLiDE30.err I am attaching the output of this. Graphical frontends still don't work, even when specifying the device on the command line for xscanimage, or selecting it in quiteinsane. I also noticed the following dmesg output after trying to scan with xscanimage: usb 3-2: usbfs: interface 0 claimed by usbfs while 'xscanimage' sets config #1 I don't know which (combination of) software is reponsible for the problems, otherwise I would file a bug report in the Debian BTS. My kernel is: $ uname -a Linux stiller 2.6.20-1-amd64 #1 SMP Tue Apr 24 21:10:58 UTC 2007 x86_64 GNU/Linux Sane version is: $ scanimage -V scanimage (sane-backends) 1.0.18-cvs; backend version 1.0.18 Best regards, Johannes -- Dr. Johannes Ranke jranke at uni-bremen.de Key ID: F649AF90 UFT Bremen, Leobenerstr. 1 +49 421 218 63373 D-28359 Bremen http://www.uft.uni-bremen.de/chemie/ranke -- next part -- [sanei_debug] Setting debug level of plustek to 128. [plustek] Plustek backend V0.52-3, part of sane-backends 1.0.18-cvs [plustek] Retrieving all supported and conntected devices [plustek] Checking for 0x07b3-0x0010 [plustek] Checking for 0x07b3-0x0011 [plustek] Checking for 0x07b3-0x0017 [plustek] Checking for 0x07b3-0x0015 [plustek] Checking for 0x07b3-0x0015 [plustek] Checking for 0x07b3-0x0017 [plustek] Checking for 0x07b3-0x0013 [plustek] Checking for 0x07b3-0x0013 [plustek] Checking for 0x07b3-0x0011 [plustek] Checking for 0x07b3-0x0010 [plustek] Checking for 0x07b3-0x0014 [plustek] Checking for 0x07b3-0x0014 [plustek] Checking for 0x07b3-0x0016 [plustek] Checking for 0x07b3-0x0017 [plustek] Checking for 0x07b3-0x0017 [plustek] Checking for 0x07b3-0x0007 [plustek] Checking for 0x07b3-0x000f [plustek] Checking for 0x07b3-0x000f [plustek] Checking for 0x07b3-0x0005 [plustek] Checking for 0x07b3-0x0014 [plustek] Checking for 0x07b3-0x0012 [plustek] Checking for 0x0400-0x1000 [plustek] Checking for 0x0400-0x1001 [plustek] Checking for 0x0400-0x1001 [plustek] Checking for 0x0458-0x2007 [plustek] Checking for 0x0458-0x2008 [plustek] Checking for 0x0458-0x2009 [plustek] Checking for 0x0458-0x2013 [plustek] Checking for 0x0458-0x2015 [plustek] Checking for 0x0458-0x2016 [plustek] Checking for 0x03f0-0x0505 [plustek] Checking for 0x03f0-0x0605 [plustek] Checking for 0x04b8-0x010f [plustek] Checking for 0x04b8-0x011d [plustek] Checking for 0x1606-0x0050 [plustek] Checking for 0x1606-0x0060 [plustek] Checking for 0x1606-0x0160 [plustek] Checking for 0x049f-0x001a [plustek] Checking for 0x04a9-0x2206 [plustek] Checking for 0x04a9-0x2207 [plustek] Checking for 0x04a9-0x2208 [plustek] Checking for 0x04a9-0x220d [plustek] Checking for 0x04a9-0x220e [plustek] Checking for 0x04a9-0x2220 [plustek] Checking for 0x0a82-0x6620 [plustek] Checking for 0x0a53-0x1000 [plustek] Available and supported devices: [plustek] Device: >libusb:003:003< - 0x04a9x0x220e [plustek] ># Plustek-SANE Backend configuration file< [plustek] ># For use with LM9831/2/3 based USB scanners< [plustek] >#< [plustek] >< [plustek] ># each device needs at least two lines:< [plustek] ># - [usb] vendor-ID and product-ID< [plustek] ># - device devicename< [plustek] ># i.e. for Plustek (0x07B3) UT12/16/24 (0x0017)< [plustek] ># [usb] 0x07B3 0x0017< [plustek] ># device /dev/usbscanner< [plustek] ># or< [plustek] ># device libusb:bbb:ddd< [plustek] ># where bbb is the busnumber and ddd the device number< [plustek] ># make sure that your user has access to /proc/bus/usb/bbb/ddd< [plustek] >#< [plustek] ># additionally you can specify some options< [plustek] ># warmup, lOffOnEnd, lampOff< [plustek] >#< [plustek] ># For autodetection use< [plustek] ># [usb]< [plustek] ># device /dev/usbscanner< [plustek] >#< [plustek] ># or simply< [plustek] ># [usb]< [plustek] >#< [plustek] ># or if you want a specific device but you have no idea about the< [plustek] ># device node or you use libusb, simply set vendor- and product-ID< [plustek] ># [usb] 0x07B3 0x0017< [plustek] ># device auto< [plustek] >#< [plustek] ># NOTE: autodetection is safe, as it uses the info it got< [plustek] ># from the USB subsystem. If you're not using the< [plus
