> the debug script gave me 'no such device' failure. /dev/scanner is linked to
> /dev/sga, and both appear in /usr/local/etc/sane.d/umax.conf.
>
> Again, the scanner shows up in cat /proc/scsi/scsi, and also on the boot screens.
> I should also mention that I have a removable SCSI drive ( /dev/sda4) that is
> working properly. It is on the scsi chain right after the scanner. I don't see a
> syslog entry for a scsi controller.
>
> I have the file sg.c in /usr/src/linux-2.2.14/drivers/scsi/ . Also sg.h exists
> in both /usr/src/linux-2.214/include/scsi and in /usr/include/scsi. Is the
> problem that these have not been compiled? (Puts on flame-proof suit in case this
> is a stupid question).
That is a reason that would result in a failure you describe.
You need to check 'cat/proc/scsi/scsi'
It should like similar to this:
oliver@ghanima:/proc/scsi/sg > cat /proc/scsi/scsi
Attached devices:
Host: scsi0 Channel: 00 Id: 01 Lun: 00
Vendor: PIONEER Model: DVD-ROM DVD-303 Rev: 1.09
Type: CD-ROM ANSI SCSI revision: 02
Host: scsi0 Channel: 00 Id: 02 Lun: 00
Vendor: ARCHIVE Model: Python 27871-XXX Rev: 1214
Type: Sequential-Access ANSI SCSI revision: 02
Host: scsi0 Channel: 00 Id: 03 Lun: 00
Vendor: YAMAHA Model: CRW8424S Rev: 1.0f
Type: CD-ROM ANSI SCSI revision: 02
Host: scsi1 Channel: 00 Id: 00 Lun: 00
Vendor: Model: Scanner 636A4 Rev: 1.50
Type: Scanner ANSI SCSI revision: 02
Then you need to make sure that your scanner is really sga.
sga is the first device listed. My scanner for example is sgd.
Then you can check whether the sg driver is loaded with
'cat /proc/modules'
If it isn't load it 'modprobe sg_mod' (yoi need to be root)
HTH
Oliver
-- Source code, list archive, and docs: http://www.mostang.com/sane/ To unsubscribe: echo unsubscribe sane-devel | mail majordomo@mostang.com
This archive was generated by hypermail 2b29 : Sat Dec 09 2000 - 00:56:27 PST