[jp] Re: JPilot, T3 and Fedora 2

David A. Desrosiers hacker at gnu-designs.com
Tue Jun 15 08:12:06 EDT 2004


> > lsusb gives me:
> > Bus 004 Device 001: ID 0000:0000
> > Bus 003 Device 001: ID 0000:0000
> > Bus 002 Device 001: ID 0000:0000
> > Bus 001 Device 001: ID 0000:0000
> >
> > Which looks suspicious to me.
>
> 	That's because you haven't connected any devices yet. If you hit
> HotSync on your T3, then ru lsusb in another window, you should see
> different results.

	As a comparison, here's what running lsusb produces on my
development laptop. I'm not sure what that "Texas Instruments, Inc. Hub"
device is, unless it is inside one of the other usb devices I use, but
here's what shows up during a "normal" day:

Bus 004 Device 002: ID 1058:0200 Western Digital Technologies, Inc.
Bus 004 Device 001: ID 0000:0000
Bus 003 Device 001: ID 0000:0000
Bus 002 Device 010: ID 0a16:9903 Trek Technology (S) PTE, Ltd
Bus 002 Device 009: ID 0830:0060 Palm, Inc. Palm Tungsten T
Bus 002 Device 008: ID 082d:0200 Handspring
Bus 002 Device 007: ID 0c0b:a109 Dura Micro, Inc. (Acomdata) CF/SM Reader
and Writer
Bus 002 Device 006: ID 0c0b:a10c Dura Micro, Inc. (Acomdata) SD/MS Reader
and Writer
Bus 002 Device 005: ID 0451:2046 Texas Instruments, Inc. TUSB2046 Hub
Bus 002 Device 004: ID 0781:8889 SanDisk Corp.
Bus 002 Device 003: ID 067b:2303 Prolific Technology, Inc. PL2303 Serial
Port
Bus 002 Device 002: ID 050d:0237 Belkin Components
Bus 002 Device 001: ID 0000:0000
Bus 001 Device 001: ID 0000:0000

d.



More information about the Jpilot mailing list