Re: USB Visor problems
It turned out that one of the nodes in /dev/ wasn't defined correctly.
Once I deleted and recreated them with mknod, they were fine! I had read
two docs, and one of them was wrong (I'm not used to the mknod command).
I was able to sync with jpilot. Now to try and get Evolution to sync ...
Thanks!
Jen
On Tue, Aug 13, 2002 at 09:26:26PM -0700, nate wrote:
> how long inbetween you hitting the button on the visor to you starting
> the program to transfer? i would wait about 2-3 seconds otherwise it
> may not come up.
>
> also check to be sure your USB does not have any IRQ conflicts or anything,
> on my thinkpad t20 I cannot sync my visor if my sound driver modules
> are loaded since for some reason they use the same IRQ(USB mouse works
> though).
>
> i usually use raw pilot-xfer. I remmeber having to use coldsync when
> i first got my visor about 2 years ago, but haven't had to use it
> for a real long time. also of course be sure you have read/write
> access to the ttyUSB device.
>
> also try both ttyUSB0 and ttyUSB1, for me even though the visor shows
> up on both ports when it connects, only one of the 2 ports work
> (I think it was USB1 but its been a while).
>
> you can also try jpilot, when i first started using my visor
> 2 years ago i used it and in it there was an option to set the
> baud rate, only a couple baud rates worked for me the rest did
> not.
>
> all my systems are 2.2.19, so if your using 2.4.x. the issues may
> be totally different .......!
>
> good luck!!
>
> nate
> (visor deluxe and visor prism owner)
>
>
>
> --
> To UNSUBSCRIBE, email to debian-user-request@lists.debian.org
> with a subject of "unsubscribe". Trouble? Contact listmaster@lists.debian.org
>
>
>
Reply to: