[jp] KPilot Daemon conflict w/ JPilot
carlo at oddjob.uchicago.edu
Sun Sep 4 23:07:27 EDT 2005
I don't know why this isn't happening automatically for you.
Here's something to try, though: add
alias char-major-188 visor
to your modprobe configuration file (/etc/modprobe.conf or /etc/modules.conf,
depending on your modutils version). Then reboot, or run "depmod -a".
The above should (I believe) alert the kernel that hardware requests involving
/dev/ttyUSB* (char device, major number 188) should be handled by the
I haven't tried this myself, since I don't have this problem, so I'm not
certain that it will work. If it does, it's at best a work-around, and
I would still try to figure out why the module doesn't get loaded automatically.
> Verified that it's not. After several reboots and the necessity to run it each
> time before anything happens using pilot-link, jpilot and/or kpilot, well,
> that's just the case. I'm just thankful for the command, frankly!
> On Tue August 23 2005 11:00, David A. Desrosiers wrote:
>>>Now I just need to figure out where to put the /sbin/modprobe visor
>>>command so it's executed at startup. There's something about init.d
>>>but I haven't grokked it so far.
>> hotplug should be doing that for you..
>>David A. Desrosiers
>>desrod at gnu-designs.com
>>Public archival of this list without notice is prohibited.
>>jpilot mailing list
>>jpilot at jpilot.org
> Public archival of this list without notice is prohibited.
> jpilot mailing list
> jpilot at jpilot.org
Carlo Graziani (773) 702-7973 (Voice)
Department of Astronomy and Astrophysics (773) 702-6645 (FAX)
University of Chicago carlo at oddjob.uchicago.edu
5640 South Ellis Avenue
Chicago, IL 60637 Vive Les Pommes Frites De La Liberte'!
More information about the Jpilot