# Success!! and, ? about ADF

From: Torsten Howard (torsten@inetw.net)
Date: Mon Mar 20 2000 - 16:01:13 PST

- Next message: Karl Heinz Kremer: "Re: ldconfig screws up my installation"
  - Previous message: Karl Heinz Kremer: "Re: Interesting news, and some questions"
  - In reply to: Karl Heinz Kremer: "Re: Interesting news, and some questions"
  - Messages sorted by: [ date ] [ thread ] [ subject ] [ author ]

  Success!!

  With the usb-backport from http://home.rochester.rr.com/specht/test which is 2.2.39--->2.2.14, the only difference I could tell was there is an option in
  'make menuconfig' which was not there before (under usb stuff), it ws
  'enable support for /proc/bus/usb'

  and support for usbdevfs was still there, as usual, so it was curious to see the separate option from above which was not there before, and does not exist in the {2.3.99pre1,2.3.50backport,2.3.99pre1Backport} kernel options. So, now I can see all the devices, but connection/disconnect of the scanner no longer seems to be reported to the system files (but then again, who cares).

  So, after I did some work to figure out I forgot to load the scanner module, and I had to specify scanner vendor and product id (command 'insmod vendor=0x04b1 produce=0x0101'), then 'scanimage --list-devices' pointed instantly to my scanner, and 'scanimage --help' returned a whole messload of parameters. I'm going to have to play now, and thanks Karl!

  On last thing, I should be receiving my ADF (==automatic document feeder) in about two to three days. Is it supported?

  Thanks,
  Torsten

  Karl Heinz Kremer wrote:
  >
  > On Mon, Mar 20, 2000 at 10:58:04PM +0000, Torsten Howard wrote:
  >
  > Before you invest any more time, there is a chance that the problems
  > you are seeing are caused by the USB system. The several minutes time
  > outs are also seen with e.g. a Kodak camera. That's also the reason
  > why I'm not doing anything in the backend code at this time. I just
  > got confirmation that the latest backend code is still working with
  > a Perfection 610.
  >
  > > Anyways, here are a few questions for the knowledgeable:
  > >
  > > Does scanimage determine the scanner identity from these 'S:' entries, as seen in the usb/devices file?
  >
  > No. The EPSON backend get's the scanner manufacturer and name from
  > a command that's send to the scanner.
  >
  > > What could the access to the scanner driver change, such that the usb susbsystem can no longer identify the scanner?
  >
  > USB errors?
  >
  > > How, exactly, are scanner identities determined? Inside each individual driver code? By standard mechanism? Are there differences between the USB/SCSI command requests (esp. for the epson)?
  >
  > Yes, each backend does this. In the case of the EPSON backend the SCSI and USB
  > scanners are treated the same way. The command set is the same.
  >
  > > Oh well, it's ten pm and I must study for dynamics test. More on this later.
  >
  > Good luck,
  >
  > Karl Heinz
  >
  > --
  > Karl Heinz Kremer khk@khk.net
  > http://www.khk.net
  >
  >
  > Part 1.2Type: application/pgp-signature

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

  - Next message: Karl Heinz Kremer: "Re: ldconfig screws up my installation"
  - Previous message: Karl Heinz Kremer: "Re: Interesting news, and some questions"
  - In reply to: Karl Heinz Kremer: "Re: Interesting news, and some questions"
  - Messages sorted by: [ date ] [ thread ] [ subject ] [ author ]

  This archive was generated by hypermail 2b29 : Mon Mar 20 2000 - 19:59:23 PST