# Re: SYM22801 & HP Scanjet 5P Sane problems...

From: Rogier Stam (rogier@wight.penguinpowered.com)
Date: Sat Apr 01 2000 - 23:38:48 PST

- Next message: Henning Meier-Geinitz: "Re: xscanimage, xsane and 3-pass scanners"
  - Previous message: Rogier Stam: "Re: SYM22801 & HP Scanjet 5P Sane problems..."
  - Messages sorted by: [ date ] [ thread ] [ subject ] [ author ]

  > /dev/sg0 and /dev/sga are synonymous (with the former now preferred).
  > /dev/scanner, if present, should be a symbolic link to the preferred
  > scanner device.
  Correct. It's just a symbolic link.

  > In lk 2.4 the sg driver will announce seeing a
  > scanner device with a message like:
  > Detected scsi generic sg0 at scsi1, channel 0, id 5, lun 0, type 6
  >
  > where as in lk 2.2 it will say:
  > Detected scsi generic sga at scsi1, channel 0, id 5, lun 0
  >
  > [Note that HP use type 3 ("Processor") for scanners.]
  >
  > To further confuse things lk 2.4 optionally supports a device pseudo
  > file system in which the actual device will be found at:
  > /dev/scsi/host1/bus0/target5/lun0/generic
  > With luck most distros will set up the devfs daemon to make /dev/sg0 ,
  > /dev/sga be symbolic links to the appropriate generic device. Ide
  > devices (and perhaps usb devices, I haven't checked) use a similar
  > naming convention.
  >
  > > Another odd thing I found (I don't know if it's related), is when I run
  > > the scsi_info tool on /dev/sga. The result is the following :
  > >
  > > SCSI_ID="0,3,0"
  > > MODEL="Direct-A "
  > > FW_REV="SCSI"
  > >
  > > That should say something like what can be found in the /proc/scsi/scsi
  > > file as far as I know, which would make me expect that model would be
  > > C5110A instead of Direct-A .....
  >
  > This is confusing. Eric Youngdale has written a tool called
  > "scsiinfo" that outputs mode page information about scsi
  > devices (and I have a variant called "sginfo" which is
  > equivalent). "scsiinfo -i /dev/sg0" yields the correct
  > inquiry information.
  >
  > The "scsi_info" (1.12 1999/07/20 16:04:26) is an unrelated
  > program that tries to analyse the output of /proc/scsi/scsi.
  > On my system (running a 2.3.99-pre3 kernel):
  >
  > $ cat /proc/scsi/scsi
  > Attached devices:
  > Host: scsi0 Channel: 00 Id: 06 Lun: 00
  > Vendor: YAMAHA Model: CRW4416S Rev: 1.0g
  > Type: CD-ROM ANSI SCSI revision: 02
  > Host: scsi1 Channel: 00 Id: 00 Lun: 00
  > Vendor: IBM Model: DCHS04U Rev: 2727
  > Type: Direct-Access ANSI SCSI revision: 02
  > Host: scsi1 Channel: 00 Id: 02 Lun: 00
  > Vendor: IBM Model: DCHS04U Rev: 2727
  > Type: Direct-Access ANSI SCSI revision: 02
  > Host: scsi3 Channel: 00 Id: 02 Lun: 00
  > Vendor: PIONEER Model: DVD-ROM DVD-303 Rev: 1.10
  > Type: CD-ROM ANSI SCSI revision: 02
  >
  > Now let's try scsi_info on the 4 scsi devices:
  >
  > $ ./scsi_info /dev/sg0
  > could not find SCSI host in /proc/scsi: Success
  > SCSI_ID="0,6,0"
  > MODEL="CD-ROM "
  > FW_REV="SCSI"
  >
  > $ ./scsi_info /dev/sg1
  > SCSI_ID="0,0,0"
  > MODEL="CD-ROM "
  > FW_REV="SCSI"
  >
  > $ ./scsi_info /dev/sg2
  > SCSI_ID="0,2,0"
  > MODEL="CD-ROM "
  > FW_REV="SCSI"
  >
  > $ ./scsi_info /dev/sg3
  > could not find SCSI host in /proc/scsi: Success
  > SCSI_ID="0,2,0"
  > MODEL="CD-ROM "
  > FW_REV="SCSI"
  >
  > The output is wrong and/or misleading in all 4 cases.
  > "scsi_info" needs to be retired or fixed. I'll take
  > the subject up with its author.
  You seem to get similar results too. I'm glad it's not just my system.

  > I don't think this has any bearing on your problem.
  Correct. Thanks to a tip from peter the problem is now solved on my
  system.
  Thanks for your help.

  Rogier

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

  - Next message: Henning Meier-Geinitz: "Re: xscanimage, xsane and 3-pass scanners"
  - Previous message: Rogier Stam: "Re: SYM22801 & HP Scanjet 5P Sane problems..."
  - Messages sorted by: [ date ] [ thread ] [ subject ] [ author ]

  This archive was generated by hypermail 2b29 : Sun Apr 02 2000 - 00:38:33 PST