Arrgghhhhh....... I cannot believe it was something so stupid that caused by 2700F not to work.
Okay. Here's what I did. I took Abel's advice. I put the sg module back to the default. I reset the default buffer size to the standard 32K and ran up sane 1.0.13. I duly collected the output and noted the error at the end [sanei_scsi] sanei_scsi_req_wait: read 64 bytes [sanei_scsi] sanei_scsi_req_wait: SCSI command complained: Success [sanei_scsi] sense buffer: f0 00 44 00 00 00 00 06 00 00 00 00 60 00 00 00 [sanei_scsi] target status: 02 host status: 0000 driver status: 0008 [canon] >> sense_handler [canon] canon_sense_handler(3, 0x8055718, (nil)) [canon] sense buffer: f0 00 44 00 00 00 00 06 00 00 00 00 60 00 00 00 [canon] sense message: problem not analyzed (unknown SCSI class) A quick rumage on the net reveals that 44 is hardware error and 60 00 is lamp failure. I'd decoded this two days ago and ignored it because quite clearly the lamp was fine. Just to make sure I stuck my eye to the slot and switched it on and sure enough there was the lamp glowing away during the self test. Nothing wrong there. Then I noticed it was a bit dusty. No! It wasn't possible that I'd spent 4 hours trying to find the software bug and all that was wrong was a little dust. I couldn't have rebuilt an entire linux kernel, 5 versions of sane (1.0.5, 1.0.9, 1.0.11, 1.0.12, 1.0.13) installed and removed RPM packages of sane and xsane and spent hours looking at debug output just because some fluff was clogging a sensor?!? There was only one way to find out, so I took a deep breath and blew into the slot. I tentatively typed the command that occurs 200 times in my command history already "scanimage -L" and sure enough up pops the canon scanner. Nuts! I thought - I'm going to look stupid when I have to admit this on the net. I quickly followed up with "scanimage -d 'canon:/dev/sg3'" which bombed. Hmmmm. Tried xsane which gave a segmentaion failure. Not to worry - I've got five versions of sane ready to test, lets see what the latest version is that works. I can now report that sane-1.0.11 now works perfectly with my 2700F with no messing with the SG module and a default buffer size of 32768. However 1.0.12 and 1.0.13 do not work so something funny happened there. Is anyone fixing the problem or shall I try to make ammends for my foolishness by trying to track down the bug? -- ______ [email protected] Jonathan Knight, / Department of Computer Science / _ __ Telephone: +44 1782 583437 University of Keele, Keele, (_/ (_) / / Fax : +44 1782 713082 Staffordshire. ST5 5BG. U.K.
