On Wed, 4 Aug 2004 13:46:19 -0500 flesh.99 disseminated the following: > When you press the sync button on your visor (button for lack of a > better word) have a terminal window open and running (as root) tail -f > /var/log/messages this will show you what it is doing. It could be > just not creating /dev/pilot in which case you would need to try and > and connect to the actual port, which for my Sony Clie is > /dev/ttyUSB0. This would be due to usb hotplug having gone sideways, I > can't help you fix that, but I may be able to help you connect to your > device again. Just let us see the messages from /var/log/messages when > you click sync on the device and we can go from there.
Hey, thanks for replying, but I got all petulant and impatient (shirley not me!) and rebooted and it 'solved' the problem <sigh>. Anyhow, I did some digging after I posted, subscribed to the JPilot list and checked out their archives, and there was a suggestion to unload and reload the visor module, ie. 'rmmod' (new one to me) and then 'insmod' or 'modprobe'. That did not work for me, hence the knee-jerk reaction to reboot. Of course, following your suggestion now, all is peachy-keen: Aug 4 15:53:09 node1 kernel: hub.c: new USB device 00:07.2-2, assigned address 5 Aug 4 15:53:09 node1 kernel: usbserial.c: Handspring Visor / Treo / Palm 4.0 / Clié 4.x converter detected Aug 4 15:53:09 node1 kernel: visor.c: Handspring Visor / Treo / Palm 4.0 / Clié 4.x: Number of ports: 2 Aug 4 15:53:09 node1 kernel: visor.c: Handspring Visor / Treo / Palm 4.0 / Clié 4.x: port 1, is for Generic use and is bound to ttyUSB0 Aug 4 15:53:09 node1 kernel: visor.c: Handspring Visor / Treo / Palm 4.0 / Clié 4.x: port 2, is for HotSync use and is bound to ttyUSB1 Aug 4 15:53:09 node1 kernel: usbserial.c: Handspring Visor / Treo / Palm 4.0 / Clié 4.x converter now attached to ttyUSB0 (or usb/tts/0 for devfs) Aug 4 15:53:09 node1 kernel: usbserial.c: Handspring Visor / Treo / Palm 4.0 / Clié 4.x converter now attached to ttyUSB1 (or usb/tts/1 for devfs) Aug 4 15:53:14 node1 /etc/hotplug/usb.agent: Setup visor for USB product 82d/100/100 When you say 'This would be due to usb hotplug having gone sideways', is this a fault in devfs? In the future (if this ever happens again, knock wood), would be possible to 'restart' just devfs? Or does that in itself require a reboot? Is there a kernel version less prone to this problem (other than 2.6, tried that with monumental failure)? I am currently running 2.4.22-21.tmb.1mdk. In any case, many thanks for the reply! I will make a greater effort at patience next time...really ;-) -- JoeHill RLU #282046 / www.freeyourmachine.org 15:47:04 up 15:28, 6 users, load average: 2.13, 2.11, 2.10 +++++++++++++++++++++++++++ "Apartheid will be dismantled, and its victims will remember those who helped to destroy this evil system. And President Reagan will be judged harshly by history." -- Archbishop Desmond Tutu, after Reagan vetoed a measure by Republicans and Democrats to impose economic sanctions on the government of South Africa
____________________________________________________ Want to buy your Pack or Services from MandrakeSoft? Go to http://www.mandrakestore.com Join the Club : http://www.mandrakeclub.com ____________________________________________________
