Bug 246637
Summary: | udev no longer creates /dev/pilot symlinks for Palm devices | ||
---|---|---|---|
Product: | [Fedora] Fedora | Reporter: | Jesse Keating <jkeating> |
Component: | pilot-link | Assignee: | Ivana Varekova <varekova> |
Status: | CLOSED ERRATA | QA Contact: | Fedora Extras Quality Assurance <extras-qa> |
Severity: | low | Docs Contact: | |
Priority: | low | ||
Version: | 7 | CC: | adellam, brianmury, craigwhite, dcantrell, gk4, redhat-bugzilla |
Target Milestone: | --- | ||
Target Release: | --- | ||
Hardware: | All | ||
OS: | Linux | ||
Whiteboard: | |||
Fixed In Version: | pilot-link-0.12.2-4.fc7 | Doc Type: | Bug Fix |
Doc Text: | Story Points: | --- | |
Clone Of: | Environment: | ||
Last Closed: | 2007-08-23 10:03:57 UTC | Type: | --- |
Regression: | --- | Mount Type: | --- |
Documentation: | --- | CRM: | |
Verified Versions: | Category: | --- | |
oVirt Team: | --- | RHEL 7.3 requirements from Atomic Host: | |
Cloudforms Team: | --- | Target Upstream Version: | |
Embargoed: |
Description
Jesse Keating
2007-07-03 15:53:41 UTC
you may change SYSFS to ATTRS.. does that help? Hrm, maybe I'm not clear. When I add the above custom rule things work just fine. Without the rule I never get the /dev/pilot device nor do I get correct permissions to the /dev/ttyUSB0/1. pilot rules removed due to complexity... udev cannot know which of the two devices a palm can provide is the correct line. pilot-link should have some logic about this.. creating /etc/udev/rules/60-libpisock.rules KERNEL=="ttyUSB*", SYSFS{idVendor}=="0830", SYSFS{idProduct}=="0061", SYMLINK+="pilot", GROUP="uucp", MODE="0664" per above worked for me with Palm T|X All this above is Greek to me. I have a Palm Z22 which worked fine on FC6 but fails to do anything on F7. I hoped the experts could see what changed and understand why. As far as I know all Palm PDA's fail when used with F7. Karl Larsen (In reply to comment #3) > pilot rules removed due to complexity... udev cannot know which of the two > devices a palm can provide is the correct line. > > pilot-link should have some logic about this.. With the latest pilot-link package, if I create the file /etc/udev/rules.d/60-libpisock.rules as in "README.libusb" (from the pilot-link distribution, not installed by the pilot-link package), add to every entry 'SYMLINK+="pilot"' and then choose 'usb:' as the device, it works well every time I try to sync or install some software. There is a strange behaviour, still: a popup from gnome-pilot states that the visor module should not be loaded when libusb is used but that's not the case for me. Note: the popup appeared while I was experimenting with the udev rules and the connection with my palm failed. Hope it helps The last fc7 version of pilot-link package (pilot-link-0.12.2-4.fc7) fixes these problem. *** Bug 250948 has been marked as a duplicate of this bug. *** (In reply to comment #7) > The last fc7 version of pilot-link package > (pilot-link-0.12.2-4.fc7) fixes these problem. With that package I still needed the udev rules when I tried, see comment #6. I'll check again tonight. I can confirm that also with package pilot-link-0.12.2-4.fc7 I still need the udev rules to sync my treo 650. Without the rules, gnome-pilot says that it cannot connect to the device via libusb even if I selected the 'usb:' device, because the visor module is loaded. I blacklisted the 'visor' kernel module too, but with the only effect to have the treo not recognized anymore. Well I just tried my Z22 on my F7 fully updated and it failed to make contact. I tried both ways saying it had worked and no never worked. It just was impossible to connect. My Palm says connection between this palm and your computer could not be made. Of course it works fine on Windows, and worked on FC6. |