[Date Prev][Date Next] [Thread Prev][Thread Next] [Date Index] [Thread Index]

Re: Changed device for camera..



On Tue, 19 Feb 2008, cothrige shared this with us all:
>--} to write the udev rules for it they won't write but choke on the
> attributes --} > of:
>--} >
>--} > * ATTRS{serial} command not found
>--} > * ATTRS{model} command not found
>--} > * ATTRS{modalias} command not found
>--}
>--} Why so many ATTRS?

Thanks for that very extensive explanation Patrick. It is much appreciated and 
though I was going to leave the whole thing as is till another time. I am 
prompted by the time you have taken to explain this to write more.

I didn't try all those attributes in one hit, I tried them individually one 
after the other and they all choked. I wasn't very clear about that. :-)

I don't have /etc/udev/rules.d/10-local.rules But do 
have /etc/udev/rules.d/udev.rules

I did:

# udevinfo -a -p $(udevinfo -q path -n /dev/sda1)

I get two entries for the Olympus camera:

looking at parent 
device '/devices/pci0000:00/0000:00:1d.7/usb5/5-1/5-1.2/5-1.2:1.0/host0/target0:0:0/0:0:0:0':
    KERNELS=="0:0:0:0"
    SUBSYSTEMS=="scsi"
    DRIVERS=="sd"
    ATTRS{modalias}=="scsi:t-0x00"
    ATTRS{ioerr_cnt}=="0x1"
    ATTRS{iodone_cnt}=="0xd4"
    ATTRS{iorequest_cnt}=="0xd4"
    ATTRS{iocounterbits}=="32"
    ATTRS{timeout}=="30"
    ATTRS{state}=="running"
    ATTRS{rev}=="    "
    ATTRS{model}=="FE110/X705      "
    ATTRS{vendor}=="OLYMPUS "
    ATTRS{scsi_level}=="0"
    ATTRS{type}=="0"
    ATTRS{queue_type}=="none"
    ATTRS{queue_depth}=="1"
    ATTRS{device_blocked}=="0"
    ATTRS{max_sectors}=="240"

As well, I get this:

looking at parent device '/devices/pci0000:00/0000:00:1d.7/usb5/5-1/5-1.2':
    KERNELS=="5-1.2"
    SUBSYSTEMS=="usb"
    DRIVERS=="usb"
    ATTRS{serial}=="X11017714"
    ATTRS{product}=="FE110/X705"
    ATTRS{manufacturer}=="OLYMPUS"
    ATTRS{quirks}=="0x0"
    ATTRS{maxchild}=="0"
    ATTRS{version}==" 1.10"
    ATTRS{devnum}=="3"
    ATTRS{busnum}=="5"
    ATTRS{speed}=="12"
    ATTRS{bMaxPacketSize0}=="64"
    ATTRS{bNumConfigurations}=="1"
    ATTRS{bDeviceProtocol}=="00"
    ATTRS{bDeviceSubClass}=="00"
    ATTRS{bDeviceClass}=="00"
    ATTRS{bcdDevice}=="0000"
    ATTRS{idProduct}=="0109"
    ATTRS{idVendor}=="07b4"
    ATTRS{bMaxPower}=="  0mA"
    ATTRS{bmAttributes}=="c0"
    ATTRS{bConfigurationValue}=="1"
    ATTRS{bNumInterfaces}==" 1"
    ATTRS{configuration}==""
    ATTRS{dev}=="189:514"

Then did:

KERNEL=="sda1", SUBSYSTEMS=="usb", {serial}=="X11017714", SYMLINK+="cam"

This was the error message:

-su: {serial}==X11017714,: command not found

I then tried the other attributes mentioned above.

As far as uuid is concerned, I get an id, but not a uuid, so I tried to enter 
the appropriate id into /etc/fstab but it didn't take there either. Not the 
id. There was no uuid i could discover, but forget what command I used to 
find the id.

Thanks again,
Charlie

-- 
Registered Linux User:- 329524
**********************************************************
I have always known that at last I would take this road but yesterday I did 
not know it would be today. ------------------ NARIHARA
<<<<<<<<<<<<<<<<<<<<<<<<<<<>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>
Debian - Just the best way to do magic.


Reply to: