[Date Prev][Date Next] [Thread Prev][Thread Next] [Date Index] [Thread Index]

[Fwd: Re: m130 USB connection]



-----Forwarded Message-----

> From: chris cotsapas <chris@nodalpoint.org>
> To: Jerome Acks Jr <jracksjr@bellatlantic.net>
> Subject: Re: m130 USB connection
> Date: 16 Oct 2002 13:11:45 +1000
> 
> On Sat, 2002-10-12 at 12:58, Jerome Acks Jr wrote:
> > On Fri, Oct 11, 2002 at 02:50:16PM +1000, chris cotsapas wrote:
> > > 
> > >  Hi again,
> > > > 
> > > > On Wed, 2002-09-25 at 17:30, Mario Camou wrote:
> > > > > Hi,
> > > > > 
> > > > > One of the weird things with many PalmOS USB devices, is that the device
> > > > > itself appears on the USB bus only during the HotSync operation itself.
> > > > > Try pressing HotSync and checking the contents of /proc/bus/usb while
> > > > > the Palm is trying to sync.
> > > > > 
> > > > > The device you want is /dev/ttyUSB1 (ttyUSB0 is reserved for something
> > > > > or other, I don't remember. ttyUSB1 is the HotSync port). You can create
> > > > > a softlink from /dev/pilot to /dev/ttyUSB1.
> > > 
> > >  The softlink is there... /dev/ttyUSB1 is not, however. Any thoughts? I'm
> > >  probably doing something stupid, but I'm a newbie to Linux.....
> > 
> > Since you are using a 2.4.19 kernel, if you have mounted devfs on
> > /dev, pressing the hotsync button will make the devfs daemon, devfsd,
> > create the device when it is needed and remove it when it is not
> > needed. If you have not mounted devfs on /dev, you will need to create
> > the /dev/ttyUSB0 and /dev/ttyUSB1.
> > 
> > # mknod /dev/usb/ttyUSB0 c 188 0
> > # mknod /dev/usb/ttyUSB1 c 188 1
> > 
> > Check /var/log/messages to see if USB registers the device when you
> > press the hotsync button.
> 
> Hi Jerome, these are the relevant entries from /var/log/messages:
> 
> Oct 16 12:06:28 mirage kernel: hub.c: USB new device connect on bus1/2,
> assigned device number 8
> Oct 16 12:06:28 mirage kernel: usbserial.c: Palm 4.0 converter detected
> Oct 16 12:06:28 mirage kernel: visor.c: Palm 4.0: Number of ports: 1
> Oct 16 12:06:28 mirage kernel: visor.c: Palm 4.0: port 1, is for HotSync
> use and is bound to ttyUSB0
> Oct 16 12:06:28 mirage kernel: usbserial.c: Palm 4.0 converter now
> attached to ttyUSB0 (or usb/tts/0 for devfs)
> Oct 16 12:06:28 mirage kernel: usbserial.c: Palm 4.0 converter now
> attached to ttyUSB1 (or usb/tts/1 for devfs)
> Oct 16 12:06:31 mirage /etc/hotplug/usb.agent: Setup visor for USB
> product 830/50/100
> Oct 16 12:06:46 mirage kernel: usb.c: USB disconnect on device 8
> Oct 16 12:06:46 mirage kernel: usbserial.c: Palm 4.0 converter now
> disconnected from ttyUSB0
> Oct 16 12:06:46 mirage kernel: usbserial.c: Palm 4.0 converter now
> disconnected from ttyUSB1
> 
> This is after attempting a Hotsync. The Palm eventually returns an
> error, saying it's unable to connect to the desktop. Running (after
> pressing the HotSync button on the cradle):
> 
>  chris@mirage:~$ coldsync -p /dev/ttyUSB1 -mb temp
> Error: Can't open "/dev/ttyUSB1".
> open: No such file or directory
> 
> chris@mirage:~$ coldsync -p /dev/pilot -mb temp
> Error: Can't open "/dev/pilot".
> open: No such file or directory
> Error: Can't open connection.
> Error: Can't open connection.
> 
> 
> chris@mirage:~$ sudo pilot-xfer -p /dev/ttyUSB1 -b temp
> 
>    ERROR: No such file or directory
>    Unable to bind to port '/dev/ttyUSB1'
>    Please use --help for more information
> 
> chris@mirage:~$ sudo pilot-xfer -p /dev/pilot -b temp
> 
>    ERROR: No such file or directory
>    Unable to bind to port '/dev/pilot'
>    Please use --help for more information
> 
> Any thoughts? I appreciate your help
> 
> Thanks
> 
> Chris
> 
> 
> > 
> > >  
> > >  Thanks 
> > >  
> > >  Chris
> > >  
> > > > > 
> > > > > Hope this helps,
> > > > > -Mario Camou.
> > > > > 
> > > > > On Wed, 2002-09-25 at 09:18, chris cotsapas wrote:
> > > > > 
> > > > >     Hi all, a newbie question here: 
> > > > >     
> > > > >     I'm trying to sync my new m130 on a USB port. The first problem I seem
> > > > >     to be encountering is that the device is not recognised - /proc/bus/usb/
> > > > >     is empty. There is also no dev/pilot or ttyUSB . My guess is that the
> > > > >     cradle is not talking to the computer at all?
> > > > >     
> > > > >     Kernel: 2.4.19 
> > > > >     jpilot: 0.99.2-2 
> > > > >     pilot-link: 0.9.5.0-8
> > > > >     
> > > > >     Any comments on how to proceed would be appreciated. is there a
> > > > >     newbie-proof howto I should look at? The standard PalmOS howto doesn't
> > > > >     deal with this.
> > > > >     
> > > > >     Many thanks
> > > > >     
> > > > >     Chris Cotsapas
> > > > >     
> > > > > 
> > > > > 
> > > > 
> > 
> > -- 
> > Jerome
> -- 
> Chris Cotsapas
> 
> "In theory, there is no difference between theory and practice; 
> In practice, there is."
> 
> Chuck Reid
-- 
Chris Cotsapas

"In theory, there is no difference between theory and practice; 
In practice, there is."

Chuck Reid



Reply to: