[sane-devel] ScanJet 4C
New to Sane, I am trying to configure an old HP ScanJet 4C on my Linux box = running FC2. Dmesg suggests that FC found the SCSI controller: scsi0 : Adaptec AIC7XXX EISA/VLB/PCI SCSI HBA DRIVER, Rev 6.2.36 Adaptec 2940 SCSI adapter aic7870: Single Channel A, SCSI Id=3D7, 16/253 SCBs =20 Vendor: HPModel: C2520ARev: 3503 Type: Processor ANSI SCSI revision: 02 Vendor: HPModel: C2520ARev: 3503 Type: Processor ANSI SCSI revision: 02 Vendor: HPModel: C2520ARev: 3503 Type: Processor ANSI SCSI revision: 02 Vendor: HPModel: C2520ARev: 3503 Type: Processor ANSI SCSI revision: 02 Vendor: HPModel: C2520ARev: 3503 Type: Processor ANSI SCSI revision: 02 Vendor: HPModel: C2520ARev: 3503 Type: Processor ANSI SCSI revision: 02 Vendor: HPModel: C2520ARev: 3503 Type: Processor ANSI SCSI revision: 02 Attached scsi generic sg0 at scsi0, channel 0, id 0, lun 0, type 3 Attached scsi generic sg1 at scsi0, channel 0, id 1, lun 0, type 3 Attached scsi generic sg2 at scsi0, channel 0, id 2, lun 0, type 3 Attached scsi generic sg3 at scsi0, channel 0, id 3, lun 0, type 3 Attached scsi generic sg4 at scsi0, channel 0, id 4, lun 0, type 3 Attached scsi generic sg5 at scsi0, channel 0, id 5, lun 0, type 3 Attached scsi generic sg6 at scsi0, channel 0, id 6, lun 0, type 3 But, when I run sane-find-scanner, sane reports that there are no SCSI scan= ners attached, instead finding a USB scanner that does not exist. I created= a symbolic link between /dev/scanner and /dev/sg0.=20=20 What am I doing wrong? Thanks, Ted Parks --=20 __ Check out the latest SMS services @ http://www.linuxmail.org=20 This allows you to send and receive SMS through your mailbox. Powered by Outblaze
[sane-devel] ScanJet 4C
On Sun, 27 Mar 2005 08:41:42 +0800 Ted Parks tpa...@linuxmail.org wrote: Attached scsi generic sg0 at scsi0, channel 0, id 0, lun 0, type 3 ... Attached scsi generic sg6 at scsi0, channel 0, id 6, lun 0, type 3 But, when I run sane-find-scanner, sane reports that there are no SCSI scanners attached, instead finding a USB scanner that does not exist. I created a symbolic link between /dev/scanner and /dev/sg0. What am I doing wrong? The scanner should only be found once not seven times. Have you set the ID on the scanner and terminated the chain properly? Martin
[sane-devel] Canon CanoScan LiDE20, SuSE and red faces
Hello, my partner is not linguistic, so I post the question: she's running SuSE 9.0 with KDE 3.1.4, Kooka 0.41, SANE 1.0.10; the Canon CanoScan LiDE20 was first recognized by the hotplug and problemless installed by SuSE's YaST2 installer-tool. But after a few trials, after she increases the dpi resolution for scanning an image (from default 50 to 600 dpi): - the scanned result became red, as red-face as possible - and Kooka refused since then to do previews or real scanning. We read about a bug in Kooka, but ignore if this come from there, or from the Sane version SuSE installed itslef? Note: under another (non-free) O S it works of course, perfectly, even if she scans images on 300 dpi, just to say there is no problems with the LiDE20 itself. But: - is the problem coming from Kooka? - now Kooka is dead and SuSE no longer connects to the scanner, does she better migrate to a newer distrib / SuSE version? A last note: I tried to find Kooka 0.411 in rpm, to overwrite the broken one; not found. Now SuSE no longer connects to the scanner I completely ignore how to help her. Aldo (Debian and console-mode + braille only user). -- ~~ ~~ ~~ ~~ ~~ ~~ ~~ ~~ ~~ ~~ ~~ ~~ ~~ ~~ ~~ ~~ ~~ ~~ ~~ ~~ ~~ ~~ ~~ ~~ ~~ Osvaldo La Rosa ~~ http://www.brlspeak.net ~~ GNU/Linux? 2B FREE ~~ ~~ No individual should be discriminated against on the basis of ~~ ~~ disability in the full and equal enjoyment of the goods, services, ~~ ~~ facilities, privileges, advantages, or accommodations of any place of ~~ ~~ public accommodation (American Disability Act - 42. U.S.C. 12182[a]) ~~ ~~ ~~ ~~ ~~ ~~ ~~ ~~ ~~ ~~ ~~ ~~ ~~ ~~ ~~ ~~ ~~ ~~ ~~ ~~ ~~ ~~ ~~ ~~ ~~
[sane-devel] Canon CanoScan LiDE20, SuSE and red faces
On Sun, 2005-03-27 at 11:11 +0200, Aldo wrote: Hello, my partner is not linguistic, so I post the question: she's running SuSE 9.0 with KDE 3.1.4, Kooka 0.41, SANE 1.0.10; the Canon CanoScan LiDE20 was first recognized by the hotplug and problemless installed by SuSE's YaST2 installer-tool. But after a few trials, after she increases the dpi resolution for scanning an image (from default 50 to 600 dpi): - the scanned result became red, as red-face as possible - and Kooka refused since then to do previews or real scanning. We read about a bug in Kooka, but ignore if this come from there, or from the Sane version SuSE installed itslef? Note: under another (non-free) O S it works of course, perfectly, even if she scans images on 300 dpi, just to say there is no problems with the LiDE20 itself. But: - is the problem coming from Kooka? - now Kooka is dead and SuSE no longer connects to the scanner, does she better migrate to a newer distrib / SuSE version? A last note: I tried to find Kooka 0.411 in rpm, to overwrite the broken one; not found. Now SuSE no longer connects to the scanner I completely ignore how to help her. Aldo (Debian and console-mode + braille only user). Try first to upgrade your sane packages: sane-backends (present version 1.0.15), sane-frontends (present version 1.0.13) Also with dpi values check if you have enough memory. A4 format at 300 dpi = 25 Mbyte, at 600 dpi = 100 Mbyte. -- m.vr.gr. Gerard Klaver
[sane-devel] Failed to start scanner : Error during device I/O on Canon N656U on Debian sid
--=-AOi7DWgU4BQ6spw3F5ex Content-Type: text/plain; charset=ISO-8859-15 Content-Transfer-Encoding: quoted-printable Hi,=20 I would like use my Canon N656U scanner on Debian sid. I use kernel=20 2.6.10 on Laptop Acer TravelMate 292LMi.=20 I've do my test with Debian package (apt-get install sane xsane=20 sane-utils) and I also do test on compiled version of=20 sane-backends-1.0.15, sane-frontends-1.0.13 and xsane-0.97=20 When I launch sane-find-scanner I've this :=20 Harobed:/usr/local/src# sane-find-scanner=20 # No SCSI scanners found. If you expected something different, make=20 sure that=20 # you have loaded a SCSI driver for your SCSI adapter.=20 # Also you need support for SCSI Generic (sg) in your operating system.=20 # If using Linux, try modprobe sg.=20 found USB scanner (vendor=3D0x04a9 [Canon], product=3D0x2206 [CanoScan],=20 chip=3DLM9832/3) at libusb:002:022=20 # Your USB scanner was (probably) detected. It may or may not be=20 supported by=20 # SANE. Try scanimage -L and read the backend's manpage.=20 # Not checking for parallel port scanners.=20 # Most Scanners connected to the parallel port or other proprietary ports=20 # can't be detected by this program.=20 When I start scanimage -L, I've this :=20 Harobed:/usr/local/src# scanimage -L=20 device `plustek:libusb:002:022' is a Canon N650U/N656U USB flatbed scanner=20 When I launch xsane, and I click on Acquire preview I've this popup dialog error : Failed to start scanner: Error during device I/O.=20 The attach file is log file of debug environement variable : SANE_DEBUG_PLUSTEK=3D128=20 Thanks for your help,=20 St=E9phane KLEIN=20 --=-AOi7DWgU4BQ6spw3F5ex Content-Disposition: attachment; filename=xsane.log Content-Type: text/x-log; name=xsane.log; charset=ISO-8859-15 Content-Transfer-Encoding: 7bit [sanei_debug] Setting debug level of plustek to 128. [plustek] Plustek backend V0.48-10, part of sane-backends 1.0.15 [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 [plustek] # autodetection, you MUST have attached that device [plustek] # at your USB-port, that you have specified... [plustek] # [plustek] [plustek] [usb] [plustek] next device uses autodetection [plustek] ... next device [plustek] [plustek] # [plustek] # options for the previous USB entry [plustek] # [plustek] # switch lamp off after xxx secs, 0 disables the feature [plustek] # (can also be set via frontend) [plustek] option lampOff 300 [plustek] Decoding option lampOff [plustek] [plustek] # warmup period in seconds, 0 means no warmup, -1 means auto-warmup [plustek] # (can also be set via frontend) [plustek] option warmup -1 [plustek] Decoding option warmup [plustek] [plustek] # 0 means leave lamp-status untouched, not 0 means switch off [plustek] # on sane_close [plustek] # (can also be set via frontend) [plustek] option lOffOnEnd 1 [plustek] Decoding option lOffOnEnd [plustek] [plustek] # [plustek] # options to tweak the image start-position [plustek] # (WARNING: there's no internal range check!!!) [plustek] # [plustek] # for the normal scan area [plustek] # [plustek] option posOffX 0 [plustek] Decoding option posOffX [plustek] option posOffY 0 [plustek] Decoding option posOffY [plustek] [plustek] # for transparencies [plustek] option tpaOffX 0 [plustek] Decoding option tpaOffX [plustek] option tpaOffY 0 [plustek] Decoding option tpaOffY [plustek] [plustek] # for negatives [plustek] option negOffX 0 [plustek] Decoding option negOffX [plustek] option negOffY 0 [plustek] Decoding option negOffY [plustek] [plustek] # [plustek] # for setting the calibration strip position [plustek] # (WARNING: there's no internal range check!!!) [plustek] # -1 means use built in [plustek] # (can also be set via frontend) [plustek] option posShadingY -1 [plustek] Decoding option posShadingY [plustek] option tpaShadingY -1
[sane-devel] ScanJet 4C
Did you reboot or at least rmmod/modprobe your scsi card beore changing the scanner's scsi id? On Mon, 2005-03-28 at 07:04 +0800, Ted Parks wrote: Checking the place in the SCSI chain indicated on the small dial on my ScanJet 4C, I discovered the scanner was set on 7. I changed it to 0 and 1, but Sane still cannot find the scanner. My continuing questions: 1) What should the SCSI setting be for the ScanJet? 0? It is the only device I have connected to the SCSI port. As Martin suggested, changing the setting from 7 cleared up the repetitions in dmesg, where the machine found the scanner 7 times! But Sane still does not see the ScanJet. 2) Dmesg still has two entries associated with the scanner: First: SCSI subsystem initialized PCI: Found IRQ 9 for device :00:10.0 PCI: Sharing IRQ 9 with :00:07.2 scsi0 : Adaptec AIC7XXX EISA/VLB/PCI SCSI HBA DRIVER, Rev 6.2.36 Adaptec 2940 SCSI adapter aic7870: Single Channel A, SCSI Id=7, 16/253 SCBs Vendor: HPModel: C2520ARev: 3503 Type: Processor ANSI SCSI revision: 02 Attached scsi generic sg0 at scsi0, channel 0, id 0, lun 0, type 3 Then: Vendor: HPModel: C2520ARev: 3503 Type: Processor ANSI SCSI revision: 02 Attached scsi generic sg0 at scsi1, channel 0, id 0, lun 0, type 3 This seems to me, perhaps because of my inexperience with SCSI, that FedoraCore is attaching the scanner in two places. Why is sg0 found at scsi0 in the first entry, then at scsi1 in the second? If this is an error, how do I correct it? 3) Finally, to provide a fuller account of my problem, the output from sane-find-scanner follows. Is it normal for a usb scanner to appear, even though none is attached? [root@localhost tparks]# sane-find-scanner # No SCSI scanners found. If you expected something different, make sure that # you have loaded a SCSI driver for your SCSI adapter. found USB scanner (vendor=0x049f, product=0x505a) at libusb:001:002 # Your USB scanner was (probably) detected. It may or may not be supported by # SANE. Try scanimage -L and read the backend's manpage. # Scanners connected to the parallel port or other proprietary ports can't be # detected by this program. Thanks, Ted Parks - Original Message - From: Martin Collins mar...@mkcollins.org To: sane-devel@lists.alioth.debian.org Subject: Re: [sane-devel] ScanJet 4C Date: Sun, 27 Mar 2005 04:34:16 +0100 On Sun, 27 Mar 2005 08:41:42 +0800 Ted Parks tpa...@linuxmail.org wrote: Attached scsi generic sg0 at scsi0, channel 0, id 0, lun 0, type 3 ... Attached scsi generic sg6 at scsi0, channel 0, id 6, lun 0, type 3 But, when I run sane-find-scanner, sane reports that there are no SCSI scanners attached, instead finding a USB scanner that does not exist. I created a symbolic link between /dev/scanner and /dev/sg0. What am I doing wrong? The scanner should only be found once not seven times. Have you set the ID on the scanner and terminated the chain properly? Martin -- sane-devel mailing list: sane-devel@lists.alioth.debian.org http://lists.alioth.debian.org/mailman/listinfo/sane-devel Unsubscribe: Send mail with subject unsubscribe your_password to sane-devel-requ...@lists.alioth.debian.org -- __ Check out the latest SMS services @ http://www.linuxmail.org This allows you to send and receive SMS through your mailbox. Powered by Outblaze
[sane-devel] film scanner in linux?
Hello, and sorry if this is slightly off-topic. I've been thinking about buying a dedicated slide/negative scanner, but none of the models I've seen in the market seem to be supported by SANE. Could anyone give me recommendations about which film scanners work well under Linux? Work well is defined both as having functional drivers and getting a good image quality. Thanks a lot -- Ivan Fernández ivan.fernan...@yale.edu
