aerogate Posted October 11, 2006 Report Share Posted October 11, 2006 Hi there, been using kpilot to hotsync Palm Tunsten E2 with Kontact since version 10.0 of Mandriva. All of a sudden, in Mandriva 2007, it no longer works. The setting I have always used in Kpilot device settings is /dev/ttyusb0 Interestingly I notice that there is no longer ttyusb* in /dev or /dev/usb Has something changed? Mike [moved from Software by spinynorman] Quote Link to comment Share on other sites More sharing options...
Gowator Posted October 11, 2006 Report Share Posted October 11, 2006 Its probably just the device association.... The best thing to diagnose is open a terminal and tail -f dmesg when you poress the hotsynch it should tell you the correct device.... if you have a memory card it might show you two devices though so you have to kinds try both.... if you keep pressing it they seem to just increment .... and the way I found to reset this was rmmod visor (Im guessing its still the visor module) and then modprobe visor (you can check the exact name using lsmod) Quote Link to comment Share on other sites More sharing options...
aerogate Posted October 11, 2006 Author Report Share Posted October 11, 2006 Output from dmesg when hotsync is pressed is :- usb 2-1: new full speed USB device using uhci_hcd and address 4 usb 2-1: configuration #1 chosen from 1 choice weired! :) Quote Link to comment Share on other sites More sharing options...
ianw1974 Posted October 11, 2006 Report Share Posted October 11, 2006 I had to look in /var/log/messages when I connected something once that was a USB --> Serial (COM) port. Maybe see if this shows anything. When connected, do you see anything appear in /dev that might relate to usb? Quote Link to comment Share on other sites More sharing options...
aerogate Posted October 11, 2006 Author Report Share Posted October 11, 2006 var/log/messages shows same as dmesg Oct 11 12:41:20 localhost kernel: usb 2-1: configuration #1 chosen from 1 choice Oct 11 12:42:26 localhost kernel: usb 2-1: USB disconnect, address 4 But I think I found the device, it`s in /dev/bus/usb/002/011 the last part /011 increments each time I press hotsync. Thanks for help so far Gowata, Ianw1974 :) Quote Link to comment Share on other sites More sharing options...
Gowator Posted October 11, 2006 Report Share Posted October 11, 2006 ohci_hcd 0000:00:02.1: wakeupusb 2-3: new full speed USB device using ohci_hcd and address 2 usb 2-3: configuration #1 chosen from 1 choice usbcore: registered new driver usbserial drivers/usb/serial/usb-serial.c: USB Serial support registered for generic usbcore: registered new driver usbserial_generic drivers/usb/serial/usb-serial.c: USB Serial Driver core drivers/usb/serial/usb-serial.c: USB Serial support registered for Handspring Visor / Palm OS drivers/usb/serial/usb-serial.c: USB Serial support registered for Sony Clie 3.5 drivers/usb/serial/usb-serial.c: USB Serial support registered for Sony Clie 5.0 visor 2-3:1.0: Handspring Visor / Palm OS converter detected usb 2-3: Handspring Visor / Palm OS converter now attached to ttyUSB0 usb 2-3: Handspring Visor / Palm OS converter now attached to ttyUSB1 usbcore: registered new driver visor drivers/usb/serial/visor.c: USB HandSpring Visor / Palm OS driver This is what I get BUT..... its not connecting..... So i have to find the device string for the Palm, in my case its a Zire 72 So I press the synch and lsusb gives me Bus 002 Device 004: ID 0830:0061 Palm, Inc. Now I edit /etc/modules.conf (might be slightly different on Mandriva) options visor vendor=0x0830 product=0x061 just add that line to the end then update-modules This then adds this to the real modules file in Debian.... root@Kanotix32:/l# rmmod visor root@Kanotix32:/# modprobe visor repeat dmesg ohci_hcd 0000:00:02.1: wakeup usb 2-3: new full speed USB device using ohci_hcd and address 5 usb 2-3: configuration #1 chosen from 1 choice visor 2-3:1.0: Handspring Visor / Palm OS converter detected usb 2-3: Handspring Visor / Palm OS converter now attached to ttyUSB0 usb 2-3: Handspring Visor / Palm OS converter now attached to ttyUSB1 hmmm... the module only unloads when kpilot is stopped fully (icon on task bar) Now I have ttyUSB2 and ttyUSB3 so i unload kpilot and ........ rmmod visor :D Now Im going to try setting it to the ttyUSB1 kpilot tells me WARNING: KPilot error: Pilot device /dev/ttyUSB1 does not exist. Probably it is a USB device and will appear during a HotSync. So time to try again Success ... It needs to be the ttyUSB1 So its now synched.... You need to find the correct strings from lsusb (the first is manufacturer and the second is the device and use the modules.conf format to add them so that the module visor knows what to do.... Wow... hope that helps, at least mie is working again after my reinstall... Quote Link to comment Share on other sites More sharing options...
ianw1974 Posted October 11, 2006 Report Share Posted October 11, 2006 Might be modprobe.conf in mandy, as there's no modules.conf. Quote Link to comment Share on other sites More sharing options...
aerogate Posted October 11, 2006 Author Report Share Posted October 11, 2006 Success!!!! Did same as above apart from edited modprobe.conf now kpilot syncs sweet on /dev/ttyUSB1 Thanks, Mike Quote Link to comment Share on other sites More sharing options...
Gowator Posted October 11, 2006 Report Share Posted October 11, 2006 yahooooooo I guess i should write it up properly for mandriva.... what usb device strings sis you get (manufacturer should be the same) but the model might be different?? Quote Link to comment Share on other sites More sharing options...
aerogate Posted October 11, 2006 Author Report Share Posted October 11, 2006 what usb device strings sis you get (manufacturer should be the same) but the model might be different?? Same, Bus 002 Device 025: ID 0830:0061 Palm, Inc. :) Quote Link to comment Share on other sites More sharing options...
Gowator Posted October 11, 2006 Report Share Posted October 11, 2006 (edited) note edited (correced for mandy) First off we need to check its being seen when plugged in... this seems to be based on pressing the hotsynch on the device itself. Here is what I get from dmesg ohci_hcd 0000:00:02.1: wakeupusb 2-3: new full speed USB device using ohci_hcd and address 2 usb 2-3: configuration #1 chosen from 1 choice usbcore: registered new driver usbserial drivers/usb/serial/usb-serial.c: USB Serial support registered for generic usbcore: registered new driver usbserial_generic drivers/usb/serial/usb-serial.c: USB Serial Driver core drivers/usb/serial/usb-serial.c: USB Serial support registered for Handspring Visor / Palm OS drivers/usb/serial/usb-serial.c: USB Serial support registered for Sony Clie 3.5 drivers/usb/serial/usb-serial.c: USB Serial support registered for Sony Clie 5.0 visor 2-3:1.0: Handspring Visor / Palm OS converter detected usb 2-3: Handspring Visor / Palm OS converter now attached to ttyUSB0 usb 2-3: Handspring Visor / Palm OS converter now attached to ttyUSB1 usbcore: registered new driver visor drivers/usb/serial/visor.c: USB HandSpring Visor / Palm OS driver This is what I get BUT..... its not connecting..... So i have to find the device string for the Palm, in my case its a Zire 72 So I press the synch and lsusb gives me Bus 002 Device 004: ID 0830:0061 Palm, Inc. This needs reformating for hex so it becomes 0x0830 product=0x061 Now edit /etc/modprobe.conf and add the following line so the visor module knows to handle this device. options visor vendor=0x0830 product=0x061 just add that line to the end thenhowever if you keep pressing the synch it keeps incrementing the /dev/ttyUSB so you must unload it....and reload it root@Kanotix32:/l# rmmod visor root@Kanotix32:/# modprobe visor However if kpilot is open this won't work.... since its locking the visor module... Now Im going to try setting it to the ttyUSB1 (since ttyUSB0 doesn't work on the Zire72 it must be the SD storage) I set kpliot to /dev/ttyUSB1 kpilot tells me WARNING: KPilot error: Pilot device /dev/ttyUSB1 does not exist. Probably it is a USB device and will appear during a HotSync. So its OK... it should appear when the synch is pressed.... So time to try again Success ... It needs to be the ttyUSB1 So its now synched.... You need to find the correct strings from lsusb (the first is manufacturer and the second is the device and use the modules.conf format to add them so that the module visor knows what to do.... Update: Oops, according to 2007 release notes this doesn't work PalmOS based PDAs Pilot-link (software used to access PalmOS based PDAs) has been upgraded to version 0.12 and has been configured to use only libusb to communicate with USB PalmOS based PDAs. The 'visor' kernel module will no longer be loaded and software used to synchronize with such PDAs should be reconfigured to use the usb: port, instead of the deprecated /dev/pilot , /dev/ttyUSB0 or /dev/ttyUSB1 device nodes. Edited October 12, 2006 by Gowator Quote Link to comment Share on other sites More sharing options...
sjaglin Posted October 20, 2006 Report Share Posted October 20, 2006 Hi, I applied that to my Palm Tungsten T2 and it works fine. Thanks for that great work, I might keep 2007 after all! Stef :D Quote Link to comment Share on other sites More sharing options...
Padma Posted October 30, 2006 Report Share Posted October 30, 2006 Hi,I applied that to my Palm Tungsten T2 and it works fine. Thanks for that great work, I might keep 2007 after all! Stef :D Sorry to bump a thread that is "solved", but I'm struggling with getting my Tungsten T3 working with 2007. (It worked fine in 2006 and before.) When you say "I applied that", what is "that"? the modprobe visor, /dev/ttyUSBx, etc., or the usb:port thing? So far I haven't gotten it to work correctly using /dev/ttyUSBx, and I have no idea how to do the usb:port thing. :sad: Quote Link to comment Share on other sites More sharing options...
sjaglin Posted January 21, 2007 Report Share Posted January 21, 2007 Sorry to bump a thread that is "solved", but I'm struggling with getting my Tungsten T3 working with 2007. (It worked fine in 2006 and before.) When you say "I applied that", what is "that"? the modprobe visor, /dev/ttyUSBx, etc., or the usb:port thing? So far I haven't gotten it to work correctly using /dev/ttyUSBx, and I have no idea how to do the usb:port thing. :sad: Hi, Sorry for the late reply but i am trying to replicate what I did before : replace /dev/visor by /dev/ttyUSB1 and add the lines to modprobe.conf, and it doesn t work anymore. Smthg to do with the recent kernel upgrade?? Stef Quote Link to comment Share on other sites More sharing options...
Recommended Posts
Join the conversation
You can post now and register later. If you have an account, sign in now to post with your account.
Note: Your post will require moderator approval before it will be visible.