Re: io error on xsane

From: Oliver Rauch (oliver.rauch@Wolfsburg.DE)
Date: Thu Sep 28 2000 - 14:00:25 PDT

  • Next message: Lawrence Glaister: "Re: FIX: color scanning problems with snapscans in sane 1.0.3"

    bob van der Poel wrote:
    >
    > Oliver Rauch wrote:
    > >
    > > bob van der Poel wrote:
    > > >
    > > > Oliver Rauch wrote:
    > > > >
    > > > > bob van der Poel wrote:
    > > > > >
    > > > > > Okay, I now have both my ide-scsi cdrom and the scanner working. It will
    > > > > > not work from boot, I have to manually do a modprobe for both the
    > > > > > ide-scsi and lha152x.... I ended up copying my old conf.modules file to
    > > > > > do this...and I'm sure there's a conflict somewhere. Any ideas
    > > > > > appreaicated.
    > > > > >
    > > > > > But, big problem now is that sane doesn't work. It's not my scanner,
    > > > > > etc: scanimage and xscanimage both work fine. However, xsane comes up,
    > > > > > but when I try to scan (or get a preview) I get a popup saying "i/o
    > > > > > error". Any ideas on this????
    > > > > >
    > > > > > Oh, this is using sane 1.0.3 and xsane .61
    > > > > >
    > > > > >
    > > > >
    > > > > Hi Bob,
    > > > >
    > > > > it looks like the ide via scsi driver makes problems - I already
    > > > > heard of these problems.
    > > > > The problems will not only occur with xsane but it is possible
    > > > > that they occur more often than with xscanimage.
    > > > >
    > > > >
    > > >
    > > > Okay, I disabled all the idi-scsi stuff. There was an append statement
    > > > in my lilo.conf, the fstab file had an automount line, and the
    > > > conf.modules had the ide-scsi stuff as well. I'm pretty convinced that
    > > > there are no idi-scsi modules in memory. This makes absolutely NO change
    > > > to xsane. Same error message "Failed to start scanner...". Still,
    > > > xscanimage works fine.
    > > >
    > > > So, what else can I check?
    > > >
    > >
    > > Do
    > > export SANE_DEBUG_DLL=128
    > > export SANE_DEBUG_UMAX=12
    > > export SANE_DEBUG_SANEI_SCSI=128
    > > xsane 2>debug.txt
    > > and start the scan, then exit xsane

    > [sanei_init_debug]: Setting debug level of dll to 128.
    > [dll] adding backend microtek
    > [dll] loading backend microtek
    > [dll] dlopen()ing `/usr/lib/sane/libsane-microtek.so.1'

    Ok, for the microtek backend you should use
    export SANE_DEBUG_MICROTEK=128
    instead of SANE_DEBUG_UMAX.

    Bye
    Oliver

    -- 
    Homepage:	http://www.wolfsburg.de/~rauch
    sane-umax:	http://www.wolfsburg.de/~rauch/sane/sane-umax.html
    xsane:		http://www.wolfsburg.de/~rauch/sane/sane-xsane.html
    E-Mail:		mailto:Oliver.Rauch@Wolfsburg.DE
    

    -- Source code, list archive, and docs: http://www.mostang.com/sane/ To unsubscribe: echo unsubscribe sane-devel | mail majordomo@mostang.com



    This archive was generated by hypermail 2b29 : Thu Sep 28 2000 - 13:41:19 PDT