[sane-devel] re:re: Problem with Acer 640UT, worked before

Matts kivik at firstlinux.net
Sat Jul 20 12:32:20 BST 2002


I was going to run scanimage in gdb, but to do that I thought I should compile it with debug info. I compiled it, and replaced the mandrake cooker 1.0.8 binaries, and ... it worked. Dont know why, or why the mandrake binaries did not work for me, but now it is ok!



Hi,

> Thanks for your help. I have followed ypur instructions, and this is what
scanimage -L
> dumps: (There is one thing: I have not got a Acer620 scanner...but an
640UT, I dont
> know the vendor and product numbers for it, but it has worked in previsous
versions of > sane)

That's o.k. - the 640 models are treated as 620 models, since they only
differ in some smaller details.

> [snapscan] sane_snapscan_get_devices (0xbffff404, 0)
> Segmenteringsfel (core dumped)

I'll have to look into this in more detail. Can you run scanimage in gdb and
find out where exactly the crash occurs?

For the time being you could also try to remove the line

/dev/usb/scanner0 bus=usb

from snapscan.conf. Your scanner should be autodetected.

Regards,

Oliver



--- Matts <kivik at firstlinux.net> wrote:
>Hi,henning at meier-geinitz.de
>
>On Wed, Jul 17, 2002 at 02:16:19PM -0700, Matts wrote:
>> I have had this scanner working fine in a previous Mandrake and sane
>> version. What happens after a compleete system upgrade is that xsane
>> searches for units forever at start. I have upgraded Mandrake 8.2's
>> sane 1.0.7 to 1.0.8, but the same problem exactly was there before
>> the upgrade too. 
>
>I'm not a SnapScan expert...
>
>> My devices list looks like this:
>> I:  If#= 0 Alt= 0 #EPs= 3 Cls=ff(vend.) Sub=ff Prot=ff Driver=usbscanner
>
>Detected by the USB scanner driver, fine.
>
>> And I have a symlink:
>> 
>> [root at localhost root]# ls /dev/scanner -l
>> lr-xr-xr-x    1 root     root           17 jul 18  2002 /dev/scanner -> /dev/usb
>> /scanner0
>
>Ouch! Never do that. You have just advised all the SCSI drivers to
>send SCSI commands to your USB scanner. Your scanner probably doesn't
>like SCSI commands :-)
>
>With SANE 1.0.8 this shouldn't matter, but you should remove the link
>nevertheless. With fairly recent Linux kernels USB scanners are
>detected automatically by most SANE backends.
>
>Does sane-find-scanner find your scanner?
>
>> and /dev/usb/scanner0 does exist, when the scanner is plugged in.
>
>So you use devfs (device file system)? Are the premissions set up
>correctly? For testing, try as root.
>
>Try removing/commenting out everything from dll.conf but "snapscan".
>Run scanimage -L and scanimage -T. If it still hangs, try to set the
>debug variables, e.g.:
>
>export SANE_DEBUG_SNAPSCAN=255
>
>and run scanimage again. Maybe you can see what's going on.
>
>Bye,
>  Henning
>
>
>
>
>_____________________________________________________________
>Want a new web-based email account ? ---> http://www.firstlinux.net
>
>_____________________________________________________________
>Promote your group and strengthen ties to your members with email at yourgroup.org by Everyone.net  http://www.everyone.net/?btn=tag

_____________________________________________________________
Want a new web-based email account ? ---> http://www.firstlinux.net

_____________________________________________________________
Promote your group and strengthen ties to your members with email at yourgroup.org by Everyone.net  http://www.everyone.net/?btn=tag



More information about the sane-devel mailing list