Vuescan FS4000 Linux, scanner not ready
Joe
I'm going to leave Windows for a Linux system. So I was looking for a
canon FS4000 scanner driver, and Ed Hamrick's vuescan seems to be very
nice. I didn't have problems to test the Windows version, but on Linux
the FS4000 doesn't work.
My system: Redhat 8.0, Tekram DC-315, vuescan 7.6.1, FS4000 (ID2),
Snapscan 1236 (ID3).
Vuescan works with Snapscan, he knows that there is a canon scanner,
but when I trie to use him, I have the message « scanner not ready ».
After this, the green light of the scanner is blinking. When I now
restart vuescan, he don't find the canon scanner anymore.
The « cat /proc/scsi/scsi » output for the fs4000 model is IX-40015G
Anybody can help me ?
Thank's a lot,
Joe
Ed Hamrick
> I'm going to leave Windows for a Linux system. So I was looking for a
> canon FS4000 scanner driver, and Ed Hamrick's vuescan seems to be very
> nice. I didn't have problems to test the Windows version, but on Linux
> the FS4000 doesn't work.
You need a newer scanner.c driver. I forget the version number,
but you need the one that supports SCANNER_IOCTL_CTRLMSG
Regards,
Ed Hamrick
wally
You also need newer CD burning software as RedHat 8.0 shipped
with a broken version of Xcdroast and old cdr-tools :-(
--wally.
Joe
Thank's,
Joe
Leonard Evens
You can download scanner.c, but compiling a separate kernel module can
be complicated because it needs the entire environment. Probably the
easiest way is to replace the existing module with the new one and do a
make modules, which is part of the process for making a new kernel. But
that can also be complicated. So either upgrade to the latest kernel
you can find for your system which is part of say an RPM package, or if
necessary just make your own kernel following the instructions for doing
so that come with your system. I've done it and it works fine.
--
Leonard Evens l...@math.northwestern.edu 847-491-5537
Dept. of Mathematics, Northwestern Univ., Evanston, IL 60208
Joe
I'm sorry again, I'm a newbie. I did upgrade my kernel to 2.4.20, but
the scanner.c driver is still the same: 0.4.8. But I still don't
understand the role of a usb-driver in my scsi configuration...
Joe
wally
I inherited an Epson 636 here at work, after verifying it works in W2K I downloaded
VueScan7.6.5.tgz and tried it on my RedHat 8.0 Linux box. No Go :-(
Doesn't find the scanner.
After doing (as root): modprobe sg
I see:
Attached scsi generic sg2 at scsi0, channel 0, id 5, lun 0, type 3
in /var/log/messages.
/proc/scsi/scsi shows:
Host: scsi0 Channel: 00 Id: 05 Lun: 00
Vendor: EPSON Model: Expression636 Rev: 1.12
Type: Processor ANSI SCSI revision: 0
grep SCANNER_IOCTL_CTRLMSG scanner.*
gives (in usr/src/linux/drivers/usb):
scanner.c: case SCANNER_IOCTL_CTRLMSG:
scanner.h: * SCANNER_IOCTL_CTRLMSG ioctl.
scanner.h:#define SCANNER_IOCTL_CTRLMSG _IOWR('U', 0x22, devrequest )
modeprobe scanner makes scanner.o appear in lsmod (unused).
So my scanner.c appears up to date according to Ed's comment.
I'm running 2.4.18 kernel as distributed by RedHat.
If scanner.c is really the culprit, any clues as to where to get the
updated version that'll work with RedHat 8.0 kernel 2.4.18?
If it helps, Xsane doesn't find it either, but I've never used Xsane before.
TIA
--wally.
PS just before I sent this, I did another dmesg and saw a bunch of:
kernel: scanner.c: open_scanner(6): Unable to access minor data
error messages.
Running ./vuescan as root seems to work!
Looks like /dev/sg2 (what gets assigned to the scanner in my system)
needs world rw permissions!
As root: chmod o+rw /dev/sg2 does the trick.
Posting this it case it helps someone else.
Joe
Hello,
I always trie to work with vuescan and Canon FS4000 in Linux, and I
tested the things above... with the same messages. But even when I
load vuescan, my Canon scanner get lost. I'm new on Linux, and it
seems very difficult to use. Otherwise: sane-find-scanner find both
scanners (Agfa and Canon), but scanimage find only Agfa.
Joe
wally
> "wally" <wa...@nomail.com> wrote in message news:<pan.2003.01.16....@nomail.com>...
>> PS just before I sent this, I did another dmesg and saw a bunch of:
>> kernel: scanner.c: open_scanner(6): Unable to access minor data
>> error messages.
>>
>> Running ./vuescan as root seems to work!
>> Looks like /dev/sg2 (what gets assigned to the scanner in my system)
>> needs world rw permissions!
>>
>> As root: chmod o+rw /dev/sg2 does the trick.
>>
>> Posting this it case it helps someone else.
>
>
> Hello,
> I always trie to work with vuescan and Canon FS4000 in Linux, and I
> tested the things above... with the same messages. But even when I
> load vuescan, my Canon scanner get lost. I'm new on Linux, and it
> seems very difficult to use. Otherwise: sane-find-scanner find both
> scanners (Agfa and Canon), but scanimage find only Agfa.
> Joe
Are you using USB or SCSI for your FS4000?
I've not tried my FS4000 on Linux yet, but I tried the
Epson 636 on a different Linux box (same RH8) that had two SCSI
controllers and its not found. I don't know if the problem is in VueScan
handling multiple SCSI controllers or the my second controller not working
with scanners.
Boot with the scanner attached and powered up and then post what the dmesg.txt
file says about your USB or SCSI busses and devices, use the command:
dmesg >dmesg.txt
and edit out the appropiate parts, maybe someone will see something to
provide a clue, in my case the sg devices lacked non-root rw access, the
second system I've not figured out yet -- its not a priority.
--wally.
Joe
Hello,
my scsi-card appears twice in dmesg:
first:
>DC395x (TRM-S1040) SCSI driver 1.40, 2002-05-10
>PCI: Found IRQ 11 for device 00:11.0
>PCI: Sharing IRQ 11 with 00:0b.0
>DC395x: Used settings: AdapterID=07, Speed=0(20.0MHz), DevMode=0x57
>DC395x: AdaptMode=0x0f, Tags=4(16), DelayReset=1s
>DC395 : Connectors: Termination: Auto Low High
>DC395: Performing initial SCSI bus reset
>DC395x (TRM-S1040): 1 adapters found
>scsi1 : Tekram DC395U/UW/F DC315/U V1.40, 2002-05-10
> Vendor: CANON Model: IX-40015G Rev: 1.07
> Type: Scanner ANSI SCSI revision: 02
> Vendor: AGFA Model: SNAPSCAN 1236 Rev: 1.50
> Type: Scanner ANSI SCSI revision: 02
>DC395x: Shutdown ...<6>scsi : 1 host left.
>parport0: PC-style at 0x378 [PCSPP,TRISTATE]
second:
>DC395x (TRM-S1040) SCSI driver 1.40, 2002-05-10
>PCI: Found IRQ 11 for device 00:11.0
>PCI: Sharing IRQ 11 with 00:0b.0
>DC395x: Used settings: AdapterID=07, Speed=0(20.0MHz), DevMode=0x57
>DC395x: AdaptMode=0x0f, Tags=4(16), DelayReset=1s
>DC395 : Connectors: Termination: Auto Low High
>DC395: Performing initial SCSI bus reset
>DC395x (TRM-S1040): 1 adapters found
>scsi1 : Tekram DC395U/UW/F DC315/U V1.40, 2002-05-10
> Vendor: CANON Model: IX-40015G Rev: 1.07
> Type: Scanner ANSI SCSI revision: 02
> Vendor: AGFA Model: SNAPSCAN 1236 Rev: 1.50
> Type: Scanner ANSI SCSI revision: 02
>DC395x: Shutdown ...<6>scsi : 1 host left.
The last line with Shutdown is new!!!
In an older dmesg, I had:
>scsi0 : Tekram DC395U/UW/F DC315/U V1.40, 2002-05-10
> Vendor: CANON Model: IX-40015G Rev: 1.07
> Type: Scanner ANSI SCSI revision: 02
> Vendor: AGFA Model: SNAPSCAN 1236 Rev: 1.50
> Type: Scanner ANSI SCSI revision: 02
>scsi1 : SCSI host adapter emulation for IDE ATAPI devices
> Vendor: PLEXTOR Model: CD-R PX-W8432T Rev: 1.09
> Type: CD-ROM ANSI SCSI revision: 02
>Attached scsi generic sg0 at scsi0, channel 0, id 2, lun 0, type 6
>Attached scsi generic sg1 at scsi0, channel 0, id 3, lun 0, type 6
But it's always possible to load the Tekram driver after booting and
than both scanners are recognized.
Scanning with Agfa scanner is possible.
I also tried the scanner-driver-2.4.21-patch
Last, there are many lines this:
>usbdevfs: USBDEVFS_CONTROL failed dev 3 rqt 128 rq 6 len 486 ret -110
>usb_control/bulk_msg: timeout
I was testing the usb-connection also. No problem for recognizing by
the system, but no way to scan with vuescan or Sane.
Joe.
wally
Having the SCSI controller show up twice might be a problem if it messes
up the sg device assignment.
Here's what's I get on my Redhat 8 system
with an Epson 636 SCSI scanner:
after:
modprobe scanner
modprobe sg
I get:
in /var/log/messages:
usb.c: registered new driver usbscanner
scanner.c: 0.4.6:USB Scanner Driver
Attached scsi generic sg2 at scsi0, channel 0, id 5, lun 0, type 3
cat /proc/scsi/scsi:
Attached devices:
Host: scsi0 Channel: 00 Id: 00 Lun: 00
Vendor: COMPAQPC Model: DDRS-39130W Rev: S95E
Type: Direct-Access ANSI SCSI revision: 02
Host: scsi0 Channel: 00 Id: 01 Lun: 00
Vendor: IBM Model: DORS-32160 Rev: S82C
Type: Direct-Access ANSI SCSI revision: 02
Host: scsi0 Channel: 00 Id: 05 Lun: 00
Vendor: EPSON Model: Expression636 Rev: 1.12
Type: Processor ANSI SCSI revision: 01
Host: scsi1 Channel: 00 Id: 00 Lun: 00
Vendor: SanDisk Model: Imagemate CF-MS1 Rev: 0100
Type: Direct-Access ANSI SCSI revision: 02
Host: scsi2 Channel: 00 Id: 00 Lun: 00
Vendor: HITACHI Model: GD-2000 Rev: 0056
Type: CD-ROM ANSI SCSI revision: 02
Host: scsi3 Channel: 00 Id: 00 Lun: 00
Vendor: LITE-ON Model: LTR-12101B Rev: LS3G
Type: CD-ROM ANSI SCSI revision: 02
ls -ls /dev/sg* :
crw-rw---- 1 root disk 21, 0 Aug 30 18:31 /dev/sg0
crw-rw---- 1 root disk 21, 1 Aug 30 18:31 /dev/sg1
crw-rw---- 1 root disk 21, 10 Aug 30 18:31 /dev/sg10
crw-rw---- 1 root disk 21, 11 Aug 30 18:31 /dev/sg11
crw-rw---- 1 root disk 21, 12 Aug 30 18:31 /dev/sg12
crw-rw---- 1 root disk 21, 13 Aug 30 18:31 /dev/sg13
crw-rw---- 1 root disk 21, 14 Aug 30 18:31 /dev/sg14
crw-rw---- 1 root disk 21, 15 Aug 30 18:31 /dev/sg15
crw-rw---- 1 root disk 21, 16 Aug 30 18:31 /dev/sg16
crw-rw---- 1 root disk 21, 17 Aug 30 18:31 /dev/sg17
crw-rw---- 1 root disk 21, 18 Aug 30 18:31 /dev/sg18
crw-rw---- 1 root disk 21, 19 Aug 30 18:31 /dev/sg19
crw-rw-rw- 1 root disk 21, 2 Aug 30 18:31 /dev/sg2
crw-rw---- 1 root disk 21, 20 Aug 30 18:31 /dev/sg20
Note that I had to manually chmod o+rw /dev/sg2 after learning that's
where my scanner ended up.
My Redhat 8 seems to have the correct scanner.c version based on Ed's
remark and the fact my scanner works great.
Are you sure you SCSI chain is terminated correctly? Devices can be found
but may not work correctly if its wrong. Since it appears you have no
internal SCSI devices make sure your Tekram card and the last scanner in
the chain are heve termination enabled. The one in the middle needs
termination disabled.
Beyond this you need to find someone who knows more about scanners on
Linux than I do.
Good luck!
--wally.