[prev in list] [next in list] [prev in thread] [next in thread] 

List:       kdepim-users
Subject:    Re: [kdepim-users] kpilot cannot connect to i500 on USB
From:       Mike <mikeumo () sbcglobal ! net>
Date:       2006-12-31 5:42:09
Message-ID: 200612302342.10062.mikeumo () sbcglobal ! net
[Download RAW message or body]

Thank you all for considering my problem.

> Gah. Another layer of indirection and potential brokenness. Back to the
> original poster: you don't necessarily need to use /dev/pilot. My linux
> machine (ugh) has /dev/ttyUSB0 configured. Since I don't normally have more
> than one USB device attached, this works OK. Similarly, my FreeBSD box is
> configured for /dev/ttyU0 (used to be /dev/ucom0). But you *do* need to
> have the kernel recognizing the device consistently. The way to find that
> out is to take a look at the end of /var/log/messages after you press the
> hotsync button.
 
here is the end of /var/log/messages after several presses of HotSync button

Dec 30 23:08:22 localhost kernel: usb 1-2: USB disconnect, address 4
Dec 30 23:08:23 localhost kernel: usb 1-2: new full speed USB device using 
ohci_hcd and address 5
Dec 30 23:08:23 localhost kernel: usb 1-2: configuration #1 chosen from 1 
choice
Dec 30 23:09:23 localhost kernel: usb 1-2: USB disconnect, address 5
Dec 30 23:09:23 localhost kernel: usb 1-2: new full speed USB device using 
ohci_hcd and address 6
Dec 30 23:09:23 localhost kernel: usb 1-2: configuration #1 chosen from 1 
choice
Dec 30 23:09:23 localhost kernel: cdc_acm 1-2:1.0: ttyACM0: USB ACM device
Dec 30 23:13:05 localhost kernel: usb 1-2: USB disconnect, address 6
Dec 30 23:13:05 localhost kernel: usb 1-2: new full speed USB device using 
ohci_hcd and address 7
Dec 30 23:13:05 localhost kernel: usb 1-2: configuration #1 chosen from 1 
choice
Dec 30 23:14:06 localhost kernel: usb 1-2: USB disconnect, address 7
Dec 30 23:14:06 localhost kernel: usb 1-2: new full speed USB device using 
ohci_hcd and address 8
Dec 30 23:14:06 localhost kernel: usb 1-2: configuration #1 chosen from 1 
choice
Dec 30 23:14:06 localhost kernel: cdc_acm 1-2:1.0: ttyACM0: USB ACM device

Interestingly /dev/ACM0 does not show up. Nor /dev/ttyUSB? not /dev/ttyU?. (I 
have several devices on the hub) What does show up is /dev/bus/usb/001/004, 
006, 008 etc when hotsync is active and 003, 005, 007 ... when the PDA 
disconnects.  here is the output of udevinfo on /dev/bus/usb/001/004        

Udevinfo starts with the device specified by the devpath and then
walks up the chain of parent devices. It prints for every device
found, all possible attributes in the udev rules key format.
A rule to match, can be composed by the attributes of the device
and the attributes from one single parent device.

  looking at device '/class/usb_device/usbdev1.4':
    KERNEL=="usbdev1.4"
    SUBSYSTEM=="usb_device"
    DRIVER==""
    ATTR{dev}=="189:3"

  looking at parent device '/devices/pci0000:00/0000:00:07.4/usb1/1-2':
    KERNELS=="1-2"
    SUBSYTEMS=="usb"
    DRIVERS=="usb"
    ATTRS{configuration}==""
    ATTRS{serial}=="SPHX286A1D20"
    ATTRS{product}=="Palm Handheld"
    ATTRS{manufacturer}=="Palm, Inc."
    ATTRS{maxchild}=="0"
    ATTRS{version}==" 1.00"
    ATTRS{devnum}=="4"
    ATTRS{speed}=="12"
    ATTRS{bMaxPacketSize0}=="8"
    ATTRS{bNumConfigurations}=="1"
    ATTRS{bDeviceProtocol}=="00"
    ATTRS{bDeviceSubClass}=="00"
    ATTRS{bDeviceClass}=="00"
    ATTRS{bcdDevice}=="0100"
    ATTRS{idProduct}=="0001"
    ATTRS{idVendor}=="0830"
    ATTRS{bMaxPower}=="  2mA"
    ATTRS{bmAttributes}=="c0"
    ATTRS{bConfigurationValue}=="1"
    ATTRS{bNumInterfaces}==" 1"

  looking at parent device '/devices/pci0000:00/0000:00:07.4/usb1':
    KERNELS=="usb1"
    SUBSYTEMS=="usb"
    DRIVERS=="usb"
    ATTRS{configuration}==""
    ATTRS{serial}=="0000:00:07.4"
    ATTRS{product}=="OHCI Host Controller"
    ATTRS{manufacturer}=="Linux 2.6.17-5mdv ohci_hcd"
    ATTRS{maxchild}=="4"
    ATTRS{version}==" 1.10"
    ATTRS{devnum}=="1"
    ATTRS{speed}=="12"
    ATTRS{bMaxPacketSize0}=="64"
    ATTRS{bNumConfigurations}=="1"
    ATTRS{bDeviceProtocol}=="00"
    ATTRS{bDeviceSubClass}=="00"
    ATTRS{bDeviceClass}=="09"
    ATTRS{bcdDevice}=="0206"
    ATTRS{idProduct}=="0000"
    ATTRS{idVendor}=="0000"
    ATTRS{bMaxPower}=="  0mA"
    ATTRS{bmAttributes}=="c0"
    ATTRS{bConfigurationValue}=="1"
    ATTRS{bNumInterfaces}==" 1"

  looking at parent device '/devices/pci0000:00/0000:00:07.4':
    KERNELS=="0000:00:07.4"
    SUBSYTEMS=="pci"
    DRIVERS=="ohci_hcd"
    ATTRS{modalias}=="pci:v00001022d0000740Csv00000000sd00000000bc0Csc03i10"
    ATTRS{local_cpus}=="ffffffff"
    ATTRS{irq}=="10"
    ATTRS{class}=="0x0c0310"
    ATTRS{subsystem_device}=="0x0000"
    ATTRS{subsystem_vendor}=="0x0000"
    ATTRS{device}=="0x740c"
    ATTRS{vendor}=="0x1022"

  looking at parent device '/devices/pci0000:00':
    KERNELS=="pci0000:00"
    SUBSYTEMS==""
    DRIVERS==""

the output is different from udevinfo on the odd-numbered (not in hotsync) 
devices.

That's why I created a rule for udev which creates a  /dev/pilot link to 
the /dev/bus/usb/001/004, 006, 008 etc. The link has been working fine. the 
original device file permissions are -rw-rw---- for mike-uucp (user-group). 
Same for the /dev/pilot link, obviously. 

I hope this will clarify the situation on my box. I greatly appreciate your 
thoughts and advice on what I should try to make it work.

Mike.
_______________________________________________
KDE PIM users mailing list
kdepim-users@kde.org
https://mail.kde.org/mailman/listinfo/kdepim-users
[prev in list] [next in list] [prev in thread] [next in thread]