Granted that auto loading is nice. However, on my current Linux system, which does automatically load visor and has always synced correctly, we have: [/home/tom] > uname -a Linux linux 2.6.13-15.11-smp #1 SMP Mon Jul 17 09:43:01 UTC 2006 i686 i686 i386 GNU/Linux [/home/tom] > lsmod | grep visor visor 23308 0 usbserial 35176 1 visor usbcore 126720 8 visor,usbserial,usb_storage,usbhid,usblp,ehci_hcd,uhci_hcd [/home/tom] > ls /etc/modules ls: /etc/modules: No such file or directory [/home/tom] > ls /etc/modprobe.d ibm_acpi ipw2200 nvidia prism2 sound tv In fact, the only reference to visor found by grepping the entire /etc tree was the following: hotplug/usb.rc: rmmod visor >/dev/null 2>&1 In summary, it works (visor loads automatically at startup) but I sure wouldn't know why. It would be kind of nice to know, in case I ever have trouble with it again. TR On Saturday 25 November 2006 08:36, Peter Jay Salzman wrote: > What *should* happen is that a kernel module should auto-load when the > device file representing the hardware is accessed (opened, read, or written > to). > > This may not work here for visor.o because the device file for the pda is a > very general device (a USB tty device could and can represent any number of > things). > > So if you want visor.o to be available on demand without having to load the > module every time you reboot, you have two options: > > 1. rebuild the kernel with visor set to "y" (yes) instead of "m" (module). > 2. put the word "visor" in /etc/modules. > > The 2nd option is definitely the easier of the two, especially if you > haven't begun compiling custom kernels. > > Peter > > On Sat 25 Nov 06, 7:46 AM, TR <tmst at nethere.com> said: > > Eamann, > > > > If you've rebooted the system since running the modprobe command, you'll > > need to run it again to reload the visor module. Also, I'm not sure where > > you changed the timeout, but I know that, on my Zire, it defaults to > > around 20 sec - plenty of time to mouse over and click the JP sync > > button. > > > > -TR > > > > On Saturday 25 November 2006 00:22, Eamann O Ruairc wrote: > > > TR, > > > > > > Thank you for that suggestion. I changed the time out to 60 seconds but > > > alas that did not make any difference. > > > > > > This time I kept my finger pressed on the Zire sync button and JP gave > > > me the following information: > > > > > > J-Pilot: sync PID = 5888 > > > J-Pilot: press the hotsync button on the cradle or "kill 5888" > > > > > > Does that throw any further light on the question? > > > > > > Wishing you and yours a peaceful and enjoyable Thanksgiving weekend, > > > > > > and thanking you once again for trying to help! > > > > > > Eamann > > > > > > TR wrote: > > > > Eamann, > > > > > > > > Sounds like it should work but maybe you just waited too long to hit > > > > the JP sync button after hitting the one on the Zire, and the > > > > connection timed out. > > > > > > > > -TR > > > > > > > > On Wednesday 22 November 2006 13:55, Eamann O Ruairc wrote: > > > >> Hello TR, > > > >> > > > >> Thank you too for taking time to try and help me! > > > >> > > > >> I have followed your suggestion but it has not produced the hoped > > > >> for results: > > > >> > > > >> When I executed the command "modprobe visor" the terminal did not > > > >> give me any output. > > > >> > > > >> root at eamann-laptop:/home/eamann# modprobe visor > > > >> root at eamann-laptop:/home/eamann# > > > >> > > > >> Was that OK? > > > >> > > > >> Then when I pressed the sync button on the Zire the Palm did an > > > >> "empty" sync, that is it went into motion, said "Sync completed", or > > > >> words to that effect, but I did not see any activity. Then the > > > >> processor of my laptop began to whizz and the only way I could get > > > >> it to stop was by restarting the machine. > > > >> > > > >> When I pressed the sync button in JP, it reacted with "Syncing on > > > >> device /dev/ttyUSB1 - Press the HotSync button now" but when I did > > > >> so nothing happened. > > > >> > > > >> Any further suggestions? > > > >> > > > >> Thanks anyway! > > > >> > > > >> Best wishes, > > > >> > > > >> Eamann > > > >> > > > >> TR wrote: > > > >>> On Tuesday 21 November 2006 14:03, Eamann O Ruairc wrote: > > > >>>> Hello all! > > > >>>> > > > >>>> On 14 Nov. I posted a message explaining that I could not sync my > > > >>>> Palm Zire 71 to my Acer laptop where I run Ubuntu 6.10. > > > >>>> > > > >>>> Unfortunately for me, nobody replied. > > > >>>> > > > >>>> I have spent hours googling and trying the various bits of advice > > > >>>> on offer, but so far to no avail. > > > >>>> > > > >>>> Do any of you JP "experts" know of a definitive "howto" which > > > >>>> would throw light on the problem? > > > >>>> > > > >>>> I have tried without success deleting JP entirely and then > > > >>>> reinstalling it. But the laptop and the cradle still do not > > > >>>> communicate... > > > >>>> > > > >>>> Thank you in advance to the person(s) who will kindly reply to > > > >>>> this message! > > > >>>> > > > >>>> Best wishes, > > > >>>> > > > >>>> Eamann O Ruairc > > > >>> > > > >>> Since it's kind of quiet in JP land, guess I'll throw out the old > > > >>> suggestion that solved my problem for me on a SuSE system and a > > > >>> Zire 31. If you know anything about using the command line, you can > > > >>> issue a 'modprobe visor' command and see if that gets you anywhere. > > > >>> You'll have to do it as root. I don't think it can hurt to give it > > > >>> a try. First verify that JP is pointing to /dev/ttyUSB1, which > > > >>> should be created when you hit the sync button on your device. > > > >>> > > > >>> So, the sequence goes: > > > >>> 1. Set the JP path to /dev/ttyUSB1 > > > >>> 2. Type "modprobe visor" on the command line > > > >>> 3. Hit the sync button on the Zire > > > >>> 4. Hit the JP sync button > > > >>> > > > >>> That's the closest thing I have to a panacea. Let us know how it > > > >>> goes. > > > >>> > > > >>> -TR > > > >>> _______________________________________________ > > > >>> jpilot mailing list > > > >>> jpilot at jpilot.org > > > >>> http://www.jpilot.org/mailman/listinfo/jpilot > > > >> > > > >> _______________________________________________ > > > >> jpilot mailing list > > > >> jpilot at jpilot.org > > > >> http://www.jpilot.org/mailman/listinfo/jpilot > > > > > > > > _______________________________________________ > > > > jpilot mailing list > > > > jpilot at jpilot.org > > > > http://www.jpilot.org/mailman/listinfo/jpilot > > > > > > _______________________________________________ > > > jpilot mailing list > > > jpilot at jpilot.org > > > http://www.jpilot.org/mailman/listinfo/jpilot > > > > _______________________________________________ > > jpilot mailing list > > jpilot at jpilot.org > > http://www.jpilot.org/mailman/listinfo/jpilot -------------- next part -------------- An HTML attachment was scrubbed... URL: http://lists.jpilot.org/pipermail/jpilot/attachments/20061125/4be529b1/attachment.htm
More information about the jpilot mailing list