On Wednesday 08 March 2006 13:03, Bob Chiodini wrote: > > I have had somewhat similar problems with a Umax 1200S SCSI scanner. It > is supported by SANE, when it's detected by the SCSI driver. However, > it is rarely detected. I found that cycling the power on the scanner > prior to loading the SCSI module (Adaptec or BusLogic, in my case) seems > to make things work until the scanner goes into power saving mode, or > whatever turns off the light. After that, the scanner no longer appears > to exist. In my case the scanner is not detected during the BIOS scan, > unless I cycle the scanner's power prior to booting the computer. > > Prior to Fedora it "just worked". I've relocated residences a couple of > times and feel that something has happened to the scanner, as opposed to > a S/W problem. I'll try exchanging the terminator and interface cable. > I cannot see why that would make a difference, since traditionally this > should just be a pass-thru. But, SCSI interfacing has usually been > black magic anyway. I haven't unpacked the SCSI voodoo talismans and > can't remember the incantations :-) > > I've since bought a multi-function Brother (MFC-420CN) that was supposed > to have Linux support and indeed it does as long as you stick with a 32 > bit distro, and can tolerate the lack of udev/hotplug support. > > Brother has GPL'd the SANE backend, but there seems to be a proprietary > library (no source code) that is only compiled for a 32 bit > architecture. Brother afforded no help other than telling me to wait > for the 64 bit SANE driver. Hi, Bob. From what I've read, it's not unusual for scanners to be too slow announcing themselves. You've nothing to lose by going through the steps to get it recognised then inserting the sleep line into your start-up scripts. The rescan script that I mentioned was very helpful too. Anne
Attachment:
pgpu37O1QZ0Dt.pgp
Description: PGP signature
