Bugzilla – Bug 130167
fail to create a usb link
Last modified: 2006-02-08 19:09:45 UTC
Hi, every time I have to sync my Handspring Visor (or to any palm device for that matter - just have a look in the discussion forums!), I had to log as root (through su) and create a link to /dev/ttyUSB1 (ln -s /dev/ttyUSB1 /dev/pilot) even though /dev/ttyUSB1 does not exist; and this happens EVERY TIME. The link vanishes after each session so, every session I have do create the same link. This didn't happen with Suse 9.3, since there was a /dev/ttyUSB1. What happened with Suse 10? Why there is no /dev/ttyUSB1? This is very, very annoying!!
please attach output of lshal.
I sent the output directly to "Danny Kukawka <dkukawka@novell.com>" due to the limit in the number of characters.
attach the 'hwinfo | gzip -v9 > hwinfo.txt.gz' when the link is gone. You may want to look at the dmesg output for usb related errors.
Not a problem with HAL, maybe with udev.
Danny, care to share your knowledge with us?
Created attachment 55311 [details] output of lshal
Created attachment 55498 [details] output of "dmesg | egrep usb"
Created attachment 55499 [details] output of "lshal" just an correction. The first one I sent was done with 9.3 system; this one is with the 10.0 system.
Created attachment 55500 [details] output of "tail -f /var/log/messages" before sync This is the output of "tail -f /var/log/messages" before sync button is pressed.
Created attachment 55501 [details] output of "tail -f /var/log/messages" after This is the output of "tail -f /var/log/messages" after the sync buttom is pressed.
Created attachment 55502 [details] hw info hwinfo | gzip -v9 > hwinfo.txt.gz
If I interpret this correctly is just the link /dev/ttyUSB1 -> /dev/pilot missing, correct? As we're using dynamic device node generation via udev with 10.0, there are several options to fix this: - Edit the configuration of the affected programs to _not_ use /dev/pilot but rather /dev/ttyUSB1. - Create the link statically; add the following line to /etc/udev/static_devices.txt: pilot l /dev/ttyUSB1 - Add a udev rule to create the symlink automatically once ttyUSB1 is created. E.g. SUBSYSTEM=="usb", KERNEL=="ttyUSB1", ACTION=="add", SYMLINK+="pilot"
/dev/pilot was hardcoded in old usb or tty agent.
Kay, should we add it per default?
to Comment #12: affected programs dont'use use only usb devices, but also ttySx, ircomx and so on, therefore we can't change configuration to use /dev/ttyUSB1 instead /dev/pilot.
Care to add this line: BUS=="usb", KERNEL=="ttyUSB*", SYSFS{product}=="Palm Handheld*", SYMLINK+="pilot" to: /etc/udev/rules.d/50-udev.rules and see if that creates the link for the device?
Created attachment 55658 [details] output of "dmesg | egrep usb" after modified "/etc/udev/rules.d/50-udev.rules", did "dmesg | egrep usb". Nothing changed.
Created attachment 55659 [details] output of "tail -f /var/log/messages" before sync after modified "/etc/udev/rules.d/50-udev.rules", did "tail -f /var/log/messages" and then, pressed the sync button. Nothing changed.
Created attachment 55660 [details] output of "tail -f /var/log/messages" after sync after modified "/etc/udev/rules.d/50-udev.rules", issued "tail -f /var/log/messages", pressed the sync button. Nothing changed.
Sorry, I have no idea how to debug that. I'm closing the bug.