You are not logged in.

#1 2006-05-28 04:49:08

occam
Member
From: Melbourne, Australia
Registered: 2005-01-16
Posts: 82

Stranger udev.rules error

I am trying to use my pda (Palm Tungsten E, but that should be irrelevant) under KDE.  Well, I do not get that far!
According to the standard udev.rules the PDA should be seen as a tty device with the rule
KERNEL=="ttyUSB[0-9]*", NAME="tts/USB%n"
Later there is a rule specifically for Palm Pilots
BUS=="usb", KERNEL=="ttyUSB[0-9]*", SYSFS{product}="Palm Handheld... ", SYMLINK+=pilot
(Should not the later rule be disregarded since a valid rule has already been encountered?)

However, I get nothing.  The messages.log tells
usb 3-2: new full speed USB device using uhci_hcd and address 2
usb 3-2: configuration #1 chosen from 1 choice

That's all. No devices (not even /dev/tts/USB1), no module loaded, nothing (that I can detect).

Connections etc are ok - in Slackware the PDA is connected at /dev/tts/USB1 (later rule disregarded!) and can be used as root. So no positive clue there.

So, what is different in Arch? HAL? and most important, what should I do?


Moduli non sunt multiplicandi praeter necessitatem

Offline

#2 2006-05-28 11:03:41

lanrat
Member
From: Poland
Registered: 2003-10-28
Posts: 1,274

Re: Stranger udev.rules error

I can't help you much because I don't have Palm with USB but I can tell you that these two rules are ok. There were a lot of changes in udev since first versions and now the rules are "aggregated". They should produce both /dev/tts/USBx and /dev/pilot.

Maybe you should load another kernel module?
What is the output of lsmod before and after you plug in the palm?
Do you have usbserial module loaded ? I'm not sure if your palm needs visor module too.

What udev/kernel versions are you using ?

What is the output of lsusb when you plug in the palm?

Are you connecting your palm through some usb hub or directly ? What other usb devices are connected at the same time?

Offline

#3 2006-05-28 15:01:17

brain0
Developer
From: Aachen - Germany
Registered: 2005-01-03
Posts: 1,382

Re: Stranger udev.rules error

Do you use a kernel provided by arch? Is module autoloading enabled? Do you know what module it uses with slackware? <INSERT ANOTHER QUESTION HERE>

Offline

#4 2006-05-28 23:31:32

occam
Member
From: Melbourne, Australia
Registered: 2005-01-16
Posts: 82

Re: Stranger udev.rules error

I use the standard, unmodified Arch-supplied kernel26 and udev (2.6.16.18-1 and 091-6). Autoloading is enabled. Slack uses the visor module.
lsmod shows no difference before and after pressing hotsync, whether I manually modprobed usbserial or not. (what a lot of modules!! thank heavens for grep and Kompare). I hesitate do insert all lsmod output here - the only usb stuff was usbcore and usbhid (and usbserial after manual modprobing).
lsusb shows
Bus 005 Device 001: ID 0000:0000 
Bus 002 Device 002: ID 05d8:4002 Ultima Electronics Corp. Artec Ultima 2000 (GT6801 based)/Lifetec LT9385 Scanner
Bus 002 Device 001: ID 0000:0000 
Bus 004 Device 003: ID 0830:0060 Palm, Inc. Palm Tungsten T / Zire 71
Bus 004 Device 001: ID 0000:0000 
Bus 003 Device 003: ID 045e:001e Microsoft Corp. IntelliMouse Explorer
Bus 003 Device 002: ID 6253:0100 
Bus 003 Device 001: ID 0000:0000 
Bus 001 Device 001: ID 0000:0000 
I attach the Palm directly.

By the way, thanks for the questions - they give me hope that help may be on the way.


Moduli non sunt multiplicandi praeter necessitatem

Offline

#5 2006-05-29 10:23:25

lanrat
Member
From: Poland
Registered: 2003-10-28
Posts: 1,274

Re: Stranger udev.rules error

Ok. Add usbserial and visor modules to the MODULES in /etc/rc.conf (as it seems they are not loaded automatically). Restart machine or run /etc/udevstart and replug your palm. Can you see /dev/tts/USBx now at least? (x might be different number each time you plug in your palm).

Note that the second standard rule that should create /dev/pilot link will not work for you because SYSFS{product} is different than yours and will not match with the rule.

Now create /etc/udev/rules.d/010.udev.rules file and put these rules inside (there are two lines only! watch out for forum line wraps):

KERNEL=="ttyUSB[0-9]*", NAME:="tts/USB%n", GROUP:="users"
BUS=="usb", KERNEL=="ttyUSB[0-9]*", SYSFS{idVendor}=="0830", SYSFS{idProduct}=="0060", SYMLINK:="pilot"

Restart machine or start /etc/udevstart and replug your palm. It should create /dev/tts/USBx and /dev/pilot (which you should use in palm applications). The owner for /dev/tts/USBx should be root:users. If it needs special write permissions you can add

, MODE:="0660"

to the first rule in /etc/010.udev.rules file. You can of course change "users" to any group you like just remember to add your user to this group.

BTW If you have too many modules loaded you can customize /etc/mkinitrd.conf - check wiki for details.

Offline

#6 2006-05-30 01:51:32

occam
Member
From: Melbourne, Australia
Registered: 2005-01-16
Posts: 82

Re: Stranger udev.rules error

Thanks! your solution has given me connection to the PDA (just copy-and-paste, plus adding a " after the NAME field).
I did invoke the "workaround" feature in kpilot - and now it works!
Thanks again.
Occam


Moduli non sunt multiplicandi praeter necessitatem

Offline

#7 2006-05-30 12:26:46

lanrat
Member
From: Poland
Registered: 2003-10-28
Posts: 1,274

Re: Stranger udev.rules error

I'm glad it works for you. I've fixed the missing " in my previous post too.

Offline

Board footer

Powered by FluxBB