Arch Linux

phunni

Member

From: Bristol, UK

Registered: 2003-08-13

Posts: 787

UDEV & Sony Clie

I've followed everything I can find about setting UDEV up to get my clie working - and creating a symlink to /dev/pilot

The relevant part of my udev.rules is:

#Sony Clie
BUS="usb", ID="2-2", KERNEL="ttyUSB*", SYMLINK="pilot"

And my udev.permissions is:

# pilot/palm devices
pilot*:root:root:0660

The (relevant) result of

udevinfo -p /sys/class/tty/ttyUSB1 -a

is

  looking at the device chain at '/sys/devices/pci0000:00/0000:00:02.1/usb2/2-2':
    BUS="usb"
    ID="2-2"
    SYSFS{bConfigurationValue}="1"
    SYSFS{bDeviceClass}="00"
    SYSFS{bDeviceProtocol}="00"
    SYSFS{bDeviceSubClass}="00"
    SYSFS{bMaxPower}="  2mA"
    SYSFS{bNumConfigurations}="1"
    SYSFS{bNumInterfaces}=" 1"
    SYSFS{bcdDevice}="0100"
    SYSFS{bmAttributes}="c0"
    SYSFS{detach_state}="0"
    SYSFS{devnum}="12"
    SYSFS{idProduct}="00da"
    SYSFS{idVendor}="054c"
    SYSFS{manufacturer}="Palm, Inc."
    SYSFS{maxchild}="0"
    SYSFS{product}="Palm Handheld"
    SYSFS{speed}="12"
    SYSFS{version}=" 1.00"

can anyone show me where I'm going wrong? Nothing appears in dev when I press the button and I do have the visor module loaded

Moo-Crumpus

Member

From: Hessen / Germany

Registered: 2003-12-01

Posts: 1,488

Re: UDEV & Sony Clie

Use the special rules before the common ones. Here is my set für clie and other usb devices:

BUS="usb", SYSFS{manufacturer}="Palm, Inc.", KERNEL="ttyUSB[0-9]*", NAME="pilot%n"
KERNEL="ttyUSB[0-9]*", NAME="tts/USB%n", SYMLINK="ttyUSB%n"

This gives me pilot1 and pilot2 for the clie, while other usb devices are managed by common rules. Without the pilot rule, I would recieve ttyUSBx and ttyUSBx+1.

Here is the udev permission set:

pilot*:root:palm:0660

I would prefer to use a palm group, doing · groupadd palm · gpasswd -a username palm.

---

Frumpus ♥ addict
[mu'.krum.pus], [frum.pus]

phunni

Member

From: Bristol, UK

Registered: 2003-08-13

Posts: 787

Re: UDEV & Sony Clie

Still getting similar results, I'm assuming that the simlinks appear in /dev?  Also, according to your rules, could you clarify exactly what the symlink should be?  I'm expecting to see pilot(*) appear in /dev but, actually, nothing does...

Also - (hope this isn't a really stupid question) but do I need to have something in modprobe.conf?

Moo-Crumpus

Member

From: Hessen / Germany

Registered: 2003-12-01

Posts: 1,488

Re: UDEV & Sony Clie

Still getting similar results, I'm assuming that the simlinks appear in /dev?  Also, according to your rules, could you clarify exactly what the symlink should be?  I'm expecting to see pilot(*) appear in /dev but, actually, nothing does...

Also - (hope this isn't a really stupid question) but do I need to have something in modprobe.conf?

Udev will create the following pilot nodes, each one getting a number:
/pilot1
/pilot2
Currently, I was using /dev/pilot4 to sync my palm.

Each of it is ruled by your permission set, as pilot* matches pilot3, f.e. I am not sure, you may test the following, modified udev.rule:

BUS="usb", SYSFS{manufacturer}="Palm, Inc.", KERNEL="ttyUSB[0-9]*", NAME="pilot"

Now, you will only have one node be created. It will be /dev/pilot.

---

Frumpus ♥ addict
[mu'.krum.pus], [frum.pus]

phunni

Member

From: Bristol, UK

Registered: 2003-08-13

Posts: 787

Re: UDEV & Sony Clie

That worked - thanks 

Wonder why it wasn't working before...