I had a few problems getting my Canon FB630U scanner working in Mandrake 9.1, so I thought I would share the solution here in case others have a similar problem. This might apply to other scanners as well, although this scanner is the only one I can vouch for.
I installed the scanner using Mandrake Control Center->Hardware->ScannerDrake. It identified the scanner and told me it installed the packages sane-backends, xsane and xsane-gimp. I started MCC->Software>-RpmDrake, did a search on sane packages and found one for sane-frontends. After installing that, RpmDrake reported the following sane packages as installed:
libsane1-1.0.11-5mdk
sane-backends-1.0.11-5mdk
sane-frontends-1.0.10-1mdk
xsane-0.90-2mdk
xsane-gimp-0.90-2mdk
I first tried using Kooka in KDE, but after clicking on 'Preview' and a long period (>2 mins) of inactivity with no noises from the scanner, all I got was a Segv11 dialog. I went into a console and from 'man sane', found a few commands to run to check the scanner. They were:
Output of 'sane-find-scanner':
found USB scanner (vendor=0x04a9, product=0x2204) at /dev/usb/scanner0
found USB scanner (vendor=0x04a9, product=0x2204) at libusb:001:004
Output of 'scanimage -L':
device `canon630u:/dev/usb/scanner0' is a CANON Canoscan FB630U flatbed scanner
Output of 'scanimage -d canon630u:/dev/usb/scanner0 -h':
Usage: scanimage [OPTION]...
...plus the rest of the help information. (ie, this was working.)
Output of 'scanimage -d test -T':
...Lots of PASS messages. (ie, this was working.)
Output of 'scanimage -d canon630u:/dev/usb/scanner0 >t.pnm':
Segmentation fault. (ie, this was NOT working.)
This appeared after about 2 mins of inactivity. ~/geoff/t.pnm (0 Byte file) was created.
Output of 'ls -l /dev/usb/scanner0':
crw-rw---- 1 geoff usb 180, 48 Jan 1 1970 /dev/usb/scanner0
(ie, the device exists)
I then ran the same scanner test as before, but turned on the DEBUG switches first:
export SANE_DEBUG_USB=128
export SANE_DEBUG_DLL=128
export SANE_DEBUG_CANON630U=128
scanimage -d canon630u:/dev/usb/scanner0 >t.pnm
The output was lots of messages about reading and writing to the scanner device, ending in the same error message: 'Segmentation fault'. All this meant that the scanner existed, it was a valid device, but it didn't scan.
Then I found a statement in sane-backends-1.0.12 README:
'idescsi:
The Linux kernel "Emulation of a SCSI host adapter for IDE ATAPI
devices" (idescsi) is reported to cause problems in connection with
SANE. If your scanner isn't found or you encounter segmentation faults
try to disable idescsi.'
I was certainly getting a segmentation fault, and I do have ide-scsi present in my CD-RW setup. In fact, I had also been trying to get K3b to recognise my DVD-ROM drive by changing it from an ide-cd device to an ide-scsi device. I put this scanner issue aside for a few days; I concentrated more on getting my DVD-ROM drive to be recognised by K3b. More info on that issue here:
http://www.linuxquestions.org/questi...5&pagenumber=1
However, while Googling on the K3b issue, I came across a thread at
http://www.ussg.iu.edu/hypermail/lin...03.0/0274.html regarding a question about disabling ide-cd when configuring for ide-scsi use of a CD-ROM:
--------------------------------------------------------------------------------------------------
The standard solution, supported by all major distributions, is to supply
hdX=ide-scsi
on the kernel command line.
There is no need to completely disable IDE-CD. IDE-CD and IDE-SCSI can
and do interoperate all the time. (my emphasis)
Jeff
--------------------------------------------------------------------------------------------------
In setting up my DVD-ROM to cooperate with K3b, I had followed advice to add 'option ide-cd hdc=ignore' as the last line in /etc/modules.conf (my DVD-ROM is attached as hdc). So, given the statement about possibility of emulation of ide-scsi causing segmentation faults, and the fact that I had introduced this change to /etc/modules.conf before I installed the scanner, I decided to remove that line, re-boot, and see what would happen. Well, the DVD-ROM continued to work with K3b, and the scanner then began to work. I double-checked by adding 'option ide-cd hdc=ignore' back to /etc/modules.conf and re-booting, and the scanner then showed the same segmentation fault, which really confirmed 'option ide-cd hdc=ignore' as the culprit.
So if you have swapped your DVD-ROM or CD-ROM from ide-cd to ide-scsi to make it work with CD burner programs, and you are also having trouble getting your scanner to work, this fix might apply to you.
