FAQ Search Today's Posts Mark Forums Read
» Video Reviews

» Linux Archive

Linux-archive is a website aiming to archive linux email lists and to make them easily accessible for linux users/developers.

» Sponsor

» Partners

» Sponsor

Go Back   Linux Archive > Debian > Debian User

LinkBack Thread Tools
Old 07-12-2010, 04:49 PM
Default Re (2): output from udevadm

From: Tom H <tomh0665@gmail.com>
Date: Mon, 12 Jul 2010 03:43:02 -0400
>From a filesystem perspective, there is an assumed /sys "in front of" /class/...

OK, thanks. This confirms.

joule:/home/peter# cd /sys/class/ieee1394_protocol
joule:/sys/class/ieee1394_protocol# ls -l
total 0
drwxr-xr-x 3 root root 0 2010-07-05 17:46 raw1394
drwxr-xr-x 3 root root 0 2010-07-12 07:48 video1394-0

After the camera is plugged in, the video1394 module is loaded.

peter@joule:~$ tail --lines=20 /var/log/syslog | grep 1394
Jul 12 08:53:49 joule kernel: [ 2243.967829] IEEE 1394 device has ROM CRC error
Jul 12 08:53:49 joule kernel: [ 2243.967954] ieee1394: Node added: ID:BUS[0-00:1
023] GUID[0814436102632a2b]
Jul 12 08:53:49 joule kernel: [ 2243.969136] ieee1394: Node changed: 0-00:1023 -
> 0-01:1023
Jul 12 08:53:49 joule kernel: [ 2243.970482] IEEE 1394 device has ROM CRC error
Jul 12 08:53:50 joule kernel: [ 2244.223149] video1394: Installed video1394 modu
Jul 12 08:53:50 joule kernel: [ 2244.249614] ieee1394: raw1394: /dev/raw1394 dev
ice initialized

So udevadm should also tell something about /dev/video1394/0.

joule:/home/peter# udevadm info --name=/dev/video1394/0 --attribute-walk

Udevinfo starts with the device specified by the devpath and then
walks up the chain of parent devices. It prints for every device
found, all possible attributes in the udev rules key format.
A rule to match, can be composed by the attributes of the device
and the attributes from one single parent device.

looking at device '/class/ieee1394_protocol/video1394-0':

These points in the above strike me as problematic or puzzling.
* syslog reports a ROM CRC error while the
camera was new & Coriander gets a live image.
* syslog reports "Node changed".
* udevadm reports an empty DRIVER.
* syslog reports a GUID but udevadm reports nothing
specific to the device. An example in a Ubuntu
document has BUS=="usb", SYSFS{product}=="TS128MJFLASHA"
and many other attributes.

Any further ideas?

Thanks, ... Peter E.

Carnot is down, waiting for installation of NetBSD.
Personal site works; http://members.shaw.ca/peasthope/ .

To UNSUBSCRIBE, email to debian-user-REQUEST@lists.debian.org
with a subject of "unsubscribe". Trouble? Contact listmaster@lists.debian.org
Archive: 171056556.40006.40159.@heaviside.invalid">http://lists.debian.org/171056556.40006.40159.@heaviside.invalid

Thread Tools

All times are GMT. The time now is 10:12 AM.

VBulletin, Copyright ©2000 - 2014, Jelsoft Enterprises Ltd.
Content Relevant URLs by vBSEO ©2007, Crawlability, Inc.
Copyright 2007 - 2008, www.linux-archive.org