I'm really out of ideas ... Even though the device is recognized at=20 boot time, it's not available when you try to scan.
You can rescan your SCSI bus to detect new (or in this case old)=20 devices with the script at http://www.garloff.de/kurt/linux/rescan-scsi-bus.sh Save this script to your disk, make it executable (chmod 755=20 rescan-scsi-bus.sh) and run it as root user. Does this report your scanner? Did you power down the scanner while Linux was running? On Feb 29, 2004, at 4:53 PM, Paul Frisson wrote: > Hello again :-( > > About SCSI, I checked with dmesg | more > > which answered this among others : > > scsi1: <fdomain> No BIOS; using scsi id 7 > scsi1: <fdomain> TMC-36C70 (PCI bus) chip at 0xe400 irq 11 > scsi1 : Future Domain 16-bit SCSI Driver Version 5.50 > Vendor: EPSON Model: SCANNER GT-5000 Rev: 1.07 > Type: Processor ANSI SCSI revision: 01 > Attached scsi CD-ROM sr0 at scsi0, channel 0, id 0, lun 0 > sr0: scsi3-mmc drive: 32x/32x writer cd/rw xa/form2 cdda tray > Attached scsi generic sg1 at scsi1, channel 0, id 6, lun 0, type 3 > scsi : 1 host left. > > So there is a scanner recognised, and the fdomain driver (the one=20 > needed for > the AHA-2920) seems to be there at least at boot time, I suppose. > > What's next ? > > Thank you again for your help, I'm beginning to feel more at ease in=20= > linux. > > PF > > > > > Le Dimanche 29 F=E9vrier 2004 21:11, Karl Heinz Kremer a =E9crit : >> The CD-R shows up as SCSI device because the CD burning software can >> only >> work with SCSI devices. You are using the ide2scsi pseudo SCSI = adapter >> for >> this. As you can see, it does not see the scanner. THis means that=20 >> it's >> not >> a Sane problem, but a problem with the SCSI system (cabling, driver, >> adapter, >> termination...). Did you configure your SCSI controller? >
