Am Mittwoch, 3. Oktober 2007 schrieb abel deuring:
Hi,
> It is very weird that the SG_GET_SCSI_ID ioctl does not work: Could you
> check, if /dev/scanner -- should be a symlink -- indeed points to a
> device file of some SCSI device (ideally, to the scanner's device file)?
I wrote this udev rule to create /dev/scanner:
SUBSYSTEMS=="scsi", SYSFS{vendor}=="SCANNER ", OWNER="saned", GROUP="jplatte",
MODE="660", NAME="scanner"
root at jako:~> ls -la /dev/scanner
crw-rw---- 1 saned jplatte 254, 5 2007-10-03 14:37 /dev/scanner
> And if so, do you see any "suspicious" output in /var/log/messages?
No.
> Finally, can you run sane-find-scaner with SANE_DEBUG_SANEI_SCSI=255 and
> send us the output?
Here it is:
root at jako:~> SANE_DEBUG_SANEI_SCSI=255 sane-find-scanner
# sane-find-scanner will now attempt to detect your scanner. If the
# result is different from what you expected, first make sure your
# scanner is powered up and properly connected to your computer.
[sanei_debug] Setting debug level of sanei_scsi to 255.
[sanei_debug] Setting debug level of sanei_scsi to 255.
[sanei_scsi] sanei_scsi_find_devices: vendor=(null) model=(null) type=Scanner
bus=0 chan=0 id=6 lun=0 num=5
[sanei_scsi] lx_chk_id: 0,0 0,0 6,4 0,0
[sanei_scsi] lx_scan_sg: k=0, exclude=5, missed=0
[sanei_scsi] lx_chk_id: 0,0 0,0 6,4 0,0
[sanei_scsi] lx_scan_sg: k=1, exclude=5, missed=1
[sanei_scsi] lx_chk_id: 0,1 0,0 6,0 0,0
[sanei_scsi] lx_scan_sg: k=2, exclude=5, missed=1
[sanei_scsi] lx_chk_id: 0,1 0,0 6,1 0,0
[sanei_scsi] lx_scan_sg: k=3, exclude=5, missed=1
[sanei_scsi] lx_chk_id: 0,2 0,0 6,0 0,0
[sanei_scsi] lx_scan_sg: k=4, exclude=5, missed=1
[sanei_scsi] lx_chk_id: 0,2 0,0 6,1 0,0
[sanei_scsi] lx_scan_sg: k=5, exclude=5, missed=1
[sanei_scsi] lx_scan_sg: k=6, exclude=5, missed=1
[sanei_scsi] lx_scan_sg: k=7, exclude=5, missed=2
[sanei_scsi] lx_scan_sg: k=8, exclude=5, missed=3
[sanei_scsi] lx_scan_sg: k=9, exclude=5, missed=4
[sanei_debug] Setting debug level of sanei_scsi to 255.
[sanei_scsi] sanei_scsi_open: sanei_scsi_max_request_size=131072 bytes
[sanei_scsi] sanei_scsi_open: SG driver version: 30527
[sanei_scsi] sanei_scsi_open: The device found for /dev/scanner does not look
like a scanner
[sanei_debug] Setting debug level of sanei_scsi to 255.
[sanei_scsi] sanei_scsi_open: SG driver version: 30534
[sanei_scsi] sanei_scsi_open: The device found for /dev/sg0 does not look like
a scanner
[sanei_debug] Setting debug level of sanei_scsi to 255.
[sanei_scsi] sanei_scsi_open: SG driver version: 30534
[sanei_scsi] sanei_scsi_open: The device found for /dev/sg1 does not look like
a scanner
[sanei_debug] Setting debug level of sanei_scsi to 255.
[sanei_scsi] sanei_scsi_open: SG driver version: 30534
[sanei_scsi] sanei_scsi_open: The device found for /dev/sg2 does not look like
a scanner
[sanei_debug] Setting debug level of sanei_scsi to 255.
[sanei_scsi] sanei_scsi_open: SG driver version: 30534
[sanei_scsi] sanei_scsi_open: The device found for /dev/sg3 does not look like
a scanner
[sanei_debug] Setting debug level of sanei_scsi to 255.
[sanei_scsi] sanei_scsi_open: SG driver version: 30534
[sanei_scsi] sanei_scsi_open: The device found for /dev/sg4 does not look like
a scanner
[sanei_debug] Setting debug level of sanei_scsi to 255.
[sanei_scsi] sanei_scsi_open: open of `/dev/sg5' failed: No such file or
directory
[sanei_debug] Setting debug level of sanei_scsi to 255.
[sanei_scsi] sanei_scsi_open: open of `/dev/sg6' failed: No such file or
directory
[sanei_debug] Setting debug level of sanei_scsi to 255.
[sanei_scsi] sanei_scsi_open: open of `/dev/sg7' failed: No such file or
directory
[sanei_debug] Setting debug level of sanei_scsi to 255.
[sanei_scsi] sanei_scsi_open: open of `/dev/sg8' failed: No such file or
directory
[sanei_debug] Setting debug level of sanei_scsi to 255.
[sanei_scsi] sanei_scsi_open: open of `/dev/sg9' failed: No such file or
directory
[sanei_debug] Setting debug level of sanei_scsi to 255.
[sanei_scsi] sanei_scsi_open: open of `/dev/sga' failed: No such file or
directory
[sanei_debug] Setting debug level of sanei_scsi to 255.
[sanei_scsi] sanei_scsi_open: open of `/dev/sgb' failed: No such file or
directory
[sanei_debug] Setting debug level of sanei_scsi to 255.
[sanei_scsi] sanei_scsi_open: open of `/dev/sgc' failed: No such file or
directory
[sanei_debug] Setting debug level of sanei_scsi to 255.
[sanei_scsi] sanei_scsi_open: open of `/dev/sgd' failed: No such file or
directory
[sanei_debug] Setting debug level of sanei_scsi to 255.
[sanei_scsi] sanei_scsi_open: open of `/dev/sge' failed: No such file or
directory
[sanei_debug] Setting debug level of sanei_scsi to 255.
[sanei_scsi] sanei_scsi_open: open of `/dev/sgf' failed: No such file or
directory
[sanei_debug] Setting debug level of sanei_scsi to 255.
[sanei_scsi] sanei_scsi_open: open of `/dev/sgg' failed: No such file or
directory
[sanei_debug] Setting debug level of sanei_scsi to 255.
[sanei_scsi] sanei_scsi_open: open of `/dev/sgh' failed: No such file or
directory
[sanei_debug] Setting debug level of sanei_scsi to 255.
[sanei_scsi] sanei_scsi_open: open of `/dev/sgi' failed: No such file or
directory
[sanei_debug] Setting debug level of sanei_scsi to 255.
[sanei_scsi] sanei_scsi_open: open of `/dev/sgj' failed: No such file or
directory
[sanei_debug] Setting debug level of sanei_scsi to 255.
[sanei_scsi] sanei_scsi_open: open of `/dev/sgk' failed: No such file or
directory
[sanei_debug] Setting debug level of sanei_scsi to 255.
[sanei_scsi] sanei_scsi_open: open of `/dev/sgl' failed: No such file or
directory
[sanei_debug] Setting debug level of sanei_scsi to 255.
[sanei_scsi] sanei_scsi_open: open of `/dev/sgm' failed: No such file or
directory
[sanei_debug] Setting debug level of sanei_scsi to 255.
[sanei_scsi] sanei_scsi_open: open of `/dev/sgn' failed: No such file or
directory
[sanei_debug] Setting debug level of sanei_scsi to 255.
[sanei_scsi] sanei_scsi_open: open of `/dev/sgo' failed: No such file or
directory
[sanei_debug] Setting debug level of sanei_scsi to 255.
[sanei_scsi] sanei_scsi_open: open of `/dev/sgp' failed: No such file or
directory
[sanei_debug] Setting debug level of sanei_scsi to 255.
[sanei_scsi] sanei_scsi_open: open of `/dev/sgq' failed: No such file or
directory
[sanei_debug] Setting debug level of sanei_scsi to 255.
[sanei_scsi] sanei_scsi_open: open of `/dev/sgr' failed: No such file or
directory
[sanei_debug] Setting debug level of sanei_scsi to 255.
[sanei_scsi] sanei_scsi_open: open of `/dev/sgs' failed: No such file or
directory
[sanei_debug] Setting debug level of sanei_scsi to 255.
[sanei_scsi] sanei_scsi_open: open of `/dev/sgt' failed: No such file or
directory
[sanei_debug] Setting debug level of sanei_scsi to 255.
[sanei_scsi] sanei_scsi_open: open of `/dev/sgu' failed: No such file or
directory
[sanei_debug] Setting debug level of sanei_scsi to 255.
[sanei_scsi] sanei_scsi_open: open of `/dev/sgv' failed: No such file or
directory
[sanei_debug] Setting debug level of sanei_scsi to 255.
[sanei_scsi] sanei_scsi_open: open of `/dev/sgw' failed: No such file or
directory
[sanei_debug] Setting debug level of sanei_scsi to 255.
[sanei_scsi] sanei_scsi_open: open of `/dev/sgx' failed: No such file or
directory
[sanei_debug] Setting debug level of sanei_scsi to 255.
[sanei_scsi] sanei_scsi_open: open of `/dev/sgy' failed: No such file or
directory
[sanei_debug] Setting debug level of sanei_scsi to 255.
[sanei_scsi] sanei_scsi_open: open of `/dev/sgz' failed: No such file or
directory
# No SCSI scanners found. If you expected something different, make sure
that
# you have loaded a kernel SCSI driver for your SCSI adapter.
# No USB scanners found. If you expected something different, make sure that
# you have loaded a kernel driver for your USB host controller and have
setup
# the USB system correctly. See man sane-usb for details.
# Not checking for parallel port scanners.
# Most Scanners connected to the parallel port or other proprietary ports
# can't be detected by this program.
> And which SCSI adapter and which adapter driver are you using?
An old Symbios based card
02:07.0 SCSI storage controller: LSI Logic / Symbios Logic 53c875 (rev 26)
with this driver:
sym53c8xx 66964 0
scsi_transport_spi 20864 1 sym53c8xx
scsi_mod 122124 8
sg,sr_mod,st,sd_mod,osst,sym53c8xx,scsi_transport_spi,libata
After some reboots I discovered, that the scanner is recognized by
sane-add-scanner if it is turned on during system boot. It is not detected
after executing the following script to rescan all SCSI busses (I'm using
ata_piix, hence there is more than one SCSI bus):
for device in /sys/class/scsi_host/host*/scan ; do
echo "0 - -" > $device
done
With this script the kernel detects the scanner according to /proc/scsi/scsi
and the device node is created:
Host: scsi0 Channel: 00 Id: 06 Lun: 00
Vendor: SCANNER Model: Rev: 2.02
Type: Scanner ANSI SCSI revision: 01 CCS
but then sane-add-scanner is not able to find it. Looks more like a kernel
bug, because this script worked fine with older kernels.
regards,
J?rg
--
PGP Key: send mail with subject 'SEND PGP-KEY' PGP Key-ID: FD 4E 21 1D
PGP Fingerprint: 388A872AFC5649D3 BCEC65778BE0C605
