On Sun, 20 May 2001, Greg KH wrote: > On Sun, May 20, 2001 at 08:52:13PM +0200, Alf C Stockton wrote: > > Greg, I made the changes you suggested and now when I issue the > > "pilot-xfer -l" command with /dev/pilot a soft link to /dev/ttyUSB0 after > > pressing the hotsink button I get the following messages > > May 20 20:42:58 K9Pad kernel: usbserial.c: serial_open > > May 20 20:42:58 K9Pad kernel: usb-serial.h: serial_open - serial == NULL > > > > pilot-xfer returns > > Unable to bind to port /dev/pilot > > pi_bind: No such device > > > > but if I ls -al /dev/pilot I get :- > > lrwxrwxrwx 1 root root 12 May 20 20:47 /dev/pilot -> /dev/ttyUSB0 > > and if I ls -al /dev/ttyUSB0 I get :- > > crw-rw-rw- 1 root root 188, 1 May 18 07:49 /dev/ttyUSB0 > > > > What do you suggest that I try next ? > > What does the kernel log say before those two messages? Does it show > the device being bound to ttyUSB0 and ttyUSB1? You also need to point > /dev/pilot to /dev/ttyUSB1 if this is like the Visor (which it looks to > be.) > dmesg shows usb.c: registered new driver usbdevfs usb.c: registered new driver hub usbserial.c: USB Serial support registered for Generic usb.c: registered new driver serial usbserial.c: USB Serial support registered for Handspring Visor but I see no device being bound to /dev/ttyUSB at boot time ? However if I ls -al /dev/pilot I get lrwxrwxrwx 1 root root 12 May 20 20:47 /dev/pilot -> /dev/ttyUSB1 I created /dev/ttyUSB0 and /dev/ttyUSB1 and linked them both in turn to /dev/pilot without changing which USB hardware port I had plugged into but in both cases I got the same result. --- Regards, Alf Stockton www.stockton.co.za Who messed with my anti-paranoia shot? _______________________________________________ Pilot-unix mailing list [EMAIL PROTECTED] http://hcirisc.cs.binghamton.edu/mailman/listinfo/pilot-unix
