Hi, On Tue, Jun 10, 2003 at 11:17:58PM +0200, Nakal wrote: > Well, how to say... it doesn't work. > > I compiled xsane-0.90 from ports. I tried to set 'norealcal' and/or > 'noprecal'. The scanner always causes a timeout (see attachment) while > starting "scanimage -d 'microtek:/dev/scanner'".
Looks like a SCSI problem (either hardware or kernel driver). My Mustek SCSI scanners work fine with FreeBSD/386 so I don't think there is a general bug in the SCSI code of SANE. Maybe you need to disable automatic disconnect/reconnect and/or synchronous transfers. Some scanners don't like that. > Starting xsane or even scanimage without the correct '-d' option will freeze > the system completely. Even --help will freeze it, I wonder why. Kernel bug mist probably. User space programs should never be able to freeze the kernel. You can try to find out by which backend causes the problem by running SANE_DEBUG_DLL=255 scanimage -L and checking the last lines of the output. Disable that backend in dll.conf. That doesn't happen here either so it's either related to your SCSI adapter (driver) or the scanner. Well, I used FreeBSD 5.0 but I don't remeber such problems with older versions. > Am I doing something wrong? Probably not, but maybe your kernel :-) > xxx@xxx:/usr/home/xxx> camcontrol devlist > <PLEXTOR CD-ROM PX-40TS 1.10> at scbus0 target 3 lun 0 (pass0,cd0) > <TEAC CD-R58S 1.0H> at scbus0 target 4 lun 0 (pass1,cd1) > <PIONEER DVD-ROM DVD-303 1.10> at scbus0 target 5 lun 0 (pass2,cd2) > <MICROTEK ScanMaker II 5.61> at scbus0 target 6 lun 0 (pass3) > <MICROTEK ScanMaker II 5.61> at scbus0 target 6 lun 1 (pass4) > <MICROTEK ScanMaker II 5.61> at scbus0 target 6 lun 2 (pass5) > <MICROTEK ScanMaker II 5.61> at scbus0 target 6 lun 3 (pass6) > <MICROTEK ScanMaker II 5.61> at scbus0 target 6 lun 4 (pass7) > <MICROTEK ScanMaker II 5.61> at scbus0 target 6 lun 5 (pass8) > <MICROTEK ScanMaker II 5.61> at scbus0 target 6 lun 6 (pass9) > <MICROTEK ScanMaker II 5.61> at scbus0 target 6 lun 7 (pass10) Bah, it shows up on all LUNs. I don't think it's important but maybe the SCSI driver has an option to disable that behaviour. > Part of dmesg: > sym0: <875> port 0xc400-0xc4ff mem > 0xe7002000-0xe7002fff,0xe7001000-0xe70010ff > irq 11 at device 11.0 on pci0 > sym0: Tekram NVRAM, ID 7, Fast-20, SE, parity checking Fast-20? I guess the scanner wil do 10 MHz at most. Maybe reducing the max speed will work together with the other options mentioned. > I get some errors in my dmesg like this (probably not important): > Waiting 15 seconds for SCSI devices to settle > (probe6:sym0:0:6:0): phase change 6-7 6@0f71418c resid=4. > sym0: unexpected disconnect Ah, try disabling reconnect/disconnect. Bye, Henning
