that switch may be term power, i dont know that scanner. if the device does not show up consistently in /proc/scsi/scsi, dont even bother looking for it with sane. get the low level system stuff working first.
allan On Mon, 28 Mar 2005, Ted Parks wrote: > Peter, > > Thanks so much for your helpful reply, also for the link to the > hp-backend page. > > The problems continue. The scanner does not appear under "Attached Devices" > in /proc/scsi/scsi. And sane-find-scanner fails to list the scanner also. > Should the 4C show up as an attached SCSI device? > > I will follow Allan's advice on the list to get a terminator. However, the 4C > has a terminator switch on the back, which I have tried in both the + and - > positions. > > Thanks, > Ted > > ----- Original Message ----- > From: "Peter Kirchgessner" <[email protected]> > To: "Ted Parks" <[email protected]> > Subject: Re: [sane-devel] ScanJet 4C > Date: Mon, 28 Mar 2005 08:10:29 +0200 > >> >> Hi, >> >> the SCSI-ID 7 has a special meaning. I don't remember what, but >> maybe it is the SCSI-ID of the controller itself. SCSI-ID 0 may >> als be reserved. So I would recommend to use 1 to 6 only. >> Usually the hp-backend is configured to find the SCSI scanner >> automatically or at least at /dev/scanner. This requires that >> /dev/scanner is a link to the device where the scanner is really >> located. Run the tool sane-find-scanner from SANEs >> tools-directory. This will print a list of device names where the >> scanner is found. If for example /dev/sg0 is in that list (this >> is what your log says), become root, create a link and set >> permissions with the commands >> >> ln -s /dev/sg0 /dev/scanner >> chmod 666 /dev/sg0 >> >> You also can try to force scanimage to use the correct device: >> >> scanimage -d hp:/dev/sg0 > scan.ppm >> >> For further informations how to configure the hp-backend have a look at >> >> http://www.kirchgessner.net/sanehpfaq.html#HPFAQ0A >> >> --Peter >> >> Ted Parks schrieb: >>> 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 0000:00:10.0 >>> PCI: Sharing IRQ 9 with 0000: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: HP Model: C2520A Rev: 3503 >>> Type: Processor ANSI SCSI revision: 02 >>> Attached scsi generic sg0 at scsi0, channel 0, id 0, lun 0, type 3 >>> >>> Then: >>> >>> Vendor: HP Model: C2520A Rev: 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" <[email protected]> >>> To: [email protected] >>> 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" <[email protected]> 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: [email protected] >>>> http://lists.alioth.debian.org/mailman/listinfo/sane-devel >>>> Unsubscribe: Send mail with subject "unsubscribe your_password" >>>> to [email protected] >>> >>> >> >> -- Peter Kirchgessner >> http://www.kirchgessner.net >> mailto:[email protected] > > -- "so don't tell us it can't be done, putting down what you don't know. money isn't our god, integrity will free our souls" - Max Cavalera
