On Wednesday 23 May 2007 13:39, David A. Desrosiers wrote: > On Wed, 2007-05-23 at 12:58 -0700, TR wrote: > > Hmm. Is there any way to account for the fact that, on my unmodified > > SuSE 10 box, which syncs reliably with JPilot, the specified 'egrep' > > command produces no output? > > What do they use in /etc/udev/rules.d/ to trigger the device subsystem > to recognize the device and create the appropriate nodes in /dev/? > > Does this show any output at all? > > grep Palm /etc/udev/rules.d/* > > Are you sure you're using usb (visor), and not libusb (no visor)? The 'grep' above produces no output, either. I think it's likely that I'm using libusb. Bit my earlier question/comment was to the effect that, before tinkering around with udev, the user needs to determine whether the visor module, rather than libusb is in use. If it is the case that libusb, rather than visor, is in use, then it might be the case that the 'egrep' command producing no output does not, in fact, signify a problem with udev. Yes?
More information about the jpilot mailing list