On 10/31/2010 04:18 AM, Julien BLACHE wrote:
Karl Schmidt<k...@xtronics.com> wrote:
$ scanimage -L
device `epson2:/dev/sg3' is a Epson GT-9700 flatbed scanner
$ ll /dev/sg3
crw------- 1 root root 21, 3 Oct 30 20:31 /dev/sg3
Did you unplug/replug the scanner after adding the rule?
Yes - just to be sure I just re-ran the test.
Can you send the content of the following files, under
/sys/dev/char/<major>:<minor>/device/ (that'd be 21:3 for /dev/sg3 as
shown above)
- model
- vendor
- type
After retesting it is now /dev/sg7 so:
# cat /sys/dev/char/21\:7/device/model
GT-9700
# cat /sys/dev/char/21\:7/device/vendor
EPSON
# cat /sys/dev/char/21\:7/device/type
3
More output:
# scanimage -L
device `v4l:/dev/video0' is a Noname USB2.0 2MP UVC AF Camera virtual device
device `epson2:/dev/sg7' is a Epson GT-9700 flatbed scanner
(hmm why epson2? not epson? )
# ll /dev/sg7
crw------- 1 root root 21, 7 Oct 31 19:05 /dev/sg7
# grep GT-9700 /lib/udev/rules.d/60-libsane.rules
# Epson Perfection 2450 | Epson GT-9700F | Epson Perfection 2450 PHOTO
#Epson Perfection 2450 | EPSON GT-9700 ?
KERNEL=="sg[0-9]*", ATTRS{type}=="3", ATTRS{vendor}=="EPSON", ATTRS{model}=="EPSON GT-9700",
MODE="0664", GROUP="scanner", ENV{libsane_matched}="yes"
( I noticed that the usb section says GT-9700F instead of EPSON GT-9700 - probably not the issue
The last two lines are what I added)
# hwinfo --scanner
48: SCSI 500.0: 10c04 Scanner
[Created at scsi.1605]
UDI:
/org/freedesktop/Hal/devices/ieee1394_guid48000006ba80_unit0_scsi_host_0_scsi_device_lun0_scsi_generic
Unique ID: IwyZ.MYNrwmd2ROC
Parent ID: Nsxw.hz_XjO39FNC
SysFS ID: /class/scsi_generic/sg7
SysFS BusID: 5:0:0:0
Hardware Class: scanner
Model: "EPSON GT-9700"
Vendor: "EPSON"
Device: "GT-9700"
Revision: "1.04"
Driver: "sbp2"
Driver Modules: "firewire_sbp2"
Device File: /dev/sg7
Device Files: /dev/sg7, /dev/char/21:7
Device Number: char 21:7
Config Status: cfg=new, avail=yes, need=no, active=unknown
Attached to: #41 (FireWire (IEEE 1394))
From /var/log/syslog
Oct 31 19:05:20 singapore kernel: [62282.163930] firewire_ohci: isochronous cycle inconsistent
Oct 31 19:05:21 singapore kernel:
[62282.418268] firewire_ohci: swap not done yet
Oct 31 19:05:21 singapore kernel: [62282.418274] firewire_ohci: swap not done yet
Oct 31 19:05:21 singapore kernel:
[62282.664924] firewire_core: created device fw1: GUID 000048000006ba80, S400
Oct 31 19:05:21 singapore kernel: [62282.664930] firewire_ohci: swap not done yet
Oct 31 19:05:21 singapore kernel:
[62282.664934] firewire_ohci: swap not done yet
Oct 31 19:05:21 singapore kernel: [62282.770852] scsi5 : SBP-2 IEEE-1394
Oct 31 19:05:21 singapore kernel:
[62282.770939] firewire_sbp2: fw1.0: 127s mgt_ORB_timeout limited to 40s
Oct 31 19:05:21 singapore kernel: [62282.971966] firewire_sbp2: fw1.0: logged in to LUN 0000 (0
retries) Oct 31 19:05:21 singapore kernel:
[62282.979724] scsi 5:0:0:0: Processor EPSON GT-9700 1.04 PQ: 0 ANSI: 4
Oct 31 19:05:21 singapore kernel: [62282.979910] scsi 5:0:0:0: Attached scsi
generic sg7 type 3
,.,.
Later in syslog I see a lot of errors (one for each rule using SYSFS or BUS? )
like this:
Oct 31 19:19:59 singapore udevd[496]: SYSFS{}= will be removed in a future udev version, please use
ATTR{}= to match the event device, or ATTRS{}= to match a parent device, in
/etc/udev/rules.d/z60_xserver-xorg-input-wacom.rules:48
Oct 31 19:19:59 singapore udevd[496]: SYSFS{}= will be removed in a future udev version, please use
ATTR{}= to match the event device, or ATTRS{}= to match a parent device, in
/etc/udev/rules.d/z60_xserver-xorg-input-wacom.rules:49
Then there is this?
Oct 31 19:19:59 singapore udevd[496]: GOTO 'acl_end' has no matching label in:
'/lib/udev/rules.d/70-acl.rules'
Oct 31 19:19:59 singapore udevd[496]: GOTO 'acl_end' has no matching label in:
'/lib/udev/rules.d/70-acl.rules'
Oct 31 19:19:59 singapore udevd[496]: BUS= will be removed in a future udev version, please use
SUBSYSTEM= to match the event device, or SUBSYSTEMS= to match a parent device, in
/etc/udev/rules.d/usbdm.rules:3
This box was upgraded from lenny to squeeze - wonder if there is some left over
cruft?
Thanks for your efforts.
Is there a way to trace udev to see which rule(s) it used?
--------------------------------------------------------------------------------
Karl Schmidt EMail k...@xtronics.com
Transtronics, Inc. WEB http://xtronics.com
3209 West 9th Street Ph (785) 841-3089
Lawrence, KS 66049 FAX (785) 841-0434
A suit does not make one a man - nor does a degree make one educated. kps
--------------------------------------------------------------------------------
--
To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org
with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org
