[sane-devel] canoscan 300 scsi scanner not detected

2010-10-28 Thread Roger Davis
An HTML attachment was scrubbed... URL:

[sane-devel] canoscan 300 scsi scanner not detected

2010-10-28 Thread Johannes Meixner
Hello, On Oct 28 09:52 m. allan noah wrote: > I would need to check the code, but I think the canon backend mostly > supports machines who's model name starts with 'IX' so the best > solution might be: > > scsi CANON IX* > > or some such? I do not have a scanner which is supported by the "canon"

[sane-devel] canoscan 300 scsi scanner not detected

2010-10-28 Thread Johannes Meixner
Hello, have in mind that on nowadays systems the generic SCSI device node files /dev/sg* do no longer belong only to real SCSI devices but also to whatever other kind of devices, e.g. on my system with a plugged in "Spaceloop XL 4GB" USB stick -

[sane-devel] canoscan 300 scsi scanner not detected

2010-10-28 Thread m. allan noah
On Thu, Oct 28, 2010 at 1:27 PM, Denis Prost wrote: > ?Yes Allan, with just that line, it works ! > > Denis Well, I think that is the best solution then. (though the backend should still be fixed) allan > > Le 28/10/2010 16:57, m. allan noah a ?crit : >> >> Several comments: >> >> 1. the backen

[sane-devel] canoscan 300 scsi scanner not detected

2010-10-28 Thread Denis Prost
Hi everyone, I've got a problem with my canoscan 300 scsi scanner. though it appears in sane-find-scanner output : -- ... found SCSI scanner "CANON IX-03035B 1.01" at /dev/sg3 # Your SCSI scanner was detected. It may or may not be supported by SANE. Try # scanimage -L and read

[sane-devel] canoscan 300 scsi scanner not detected

2010-10-28 Thread m. allan noah
Several comments: 1. the backend should be changed to look at multiple rows of its config file. 2. The canon backend code does this: if (ibuf[0] != 6 || strncmp ((char *) (ibuf + 8), "CANON", 5) != 0 || strncmp ((char *) (ibuf + 16), "IX-", 3) != 0) { DBG (1, "attach: device doe

[sane-devel] canoscan 300 scsi scanner not detected

2010-10-28 Thread m. allan noah
I would need to check the code, but I think the canon backend mostly supports machines who's model name starts with 'IX' so the best solution might be: scsi CANON IX* or some such? allan On Thu, Oct 28, 2010 at 9:40 AM, Johannes Meixner wrote: > > Hello, > > have in mind that on nowadays syste

[sane-devel] canoscan 300 scsi scanner not detected

2010-10-28 Thread m. allan noah
edit /etc/sane.d/canon.conf put the scanner device file name there. allan On Thu, Oct 28, 2010 at 6:37 AM, Denis Prost wrote: > ?Hi everyone, > > I've got a problem with my canoscan 300 scsi scanner. > though it appears in sane-find-scanner output : > -- > ... > found SCSI scanner "