Re: Palm not being identified (no ttyUSB* being created)
On Tue, Apr 8, 2008 at 4:48 AM, Chris Howie <cdhowie@gmail.com> wrote:
> On Tue, Apr 8, 2008 at 12:26 AM, Mumia W..
> <paduille.4061.mumia.w+nospam@earthlink.net> wrote:
> > I'm having problems syncing my Palm TX. I started using kernel 2.6.24
> > (under Etch), and I see that the 'visor' module is no longer loaded
> > automatically when I hit the hotsync button.
> >
> > I load it manually using "modprobe visor" , yet no communication happens.
> >
> > My only advice would be to manually load visor, since your dmesg.txt
> > doesn't show it being loaded.
>
> Interesting. After loading that I get /dev/ttyUSB nodes and
> /dev/pilot. pilot-link can successfully talk to it using "-p usb:"
> but gpilotd cannot -- in fact it cannot seem to talk to it no matter
> what device I use (ttyUSB0, ttyUSB1, pilot, usb:).
Ok, I spoke too soon. If I switch to Serial (instead of USB) then
ttyUSB0 works. pilot does not (it points to ttyUSB1, which is the
debugger port) and I cannot use usb:, which is a shame since that
seems to be the best option as far as Just Working.
On another note, I have been using 2.6.24 for some time and this just
started happening. So unless a recent upgrade of something else
caused this weird behavior I have no idea where it's coming from.
--
Chris Howie
http://www.chrishowie.com
http://en.wikipedia.org/wiki/User:Crazycomputers
Reply to: