On Wed 22 Nov 06, 9:37 PM, Donn Washburn <n5xwb at hal-pc.org> said: > Peter Jay Salzman wrote: > > On Wed 22 Nov 06, 8:50 PM, Donn Washburn <n5xwb at hal-pc.org> said: > >> Peter Jay Salzman wrote: > >>> On Wed 22 Nov 06, 7:26 PM, Donn Washburn <n5xwb at hal-pc.org> said: > >>>> You may have just reminded me why mine has been failing -> "visor" > >>>> "lsmod | grep visor" showed nothing. Thanks for the reminder. > >>> You can check to see if it's built directly into the kernel (as opposed to a > >>> loadable module) with: > >>> > >>> $ zcat /proc/config.gz | grep -i visor > >>> > >>> Pete > >> Neat thing is you pointed out another way to for a problem. > >> I am running a home built custom non SuSE kernel - it also has > >> "CONFIG_SYS_HYPERVISOR=m" > >> > >> Yes it is part of SuSE10.1 kernel modules. However, as usual they > >> didn't put "visor" in /etc/modprobe.conf. I fought this problem about 5 > >> years ago and just forgot it. > > > > What is hypervisor? Never heard of it! > > > > Pete > > it is the only VISOR that came from > "zcat /proc/config.gz | grep -i visor" That doesn't tell me what it is. It only tells me where you saw the word, and I gathered you found it in /proc/config.gz from the context of the our conversation. :) > So if 2.6.18.1 made config.gz then that is where it came from. > Otherwise it was from SuSE 10.1 2.6.16.21-0.25-default > > As for where it comes from period - it is the kernel variable set to > modules (=m) which can be found in /usr/src/linux-$[version}source/.config OK. You forced me to download the latest stable Linux kernel, 2.6.18. >From reading the kernel source, I don't think hypervisor has anything to do with Handspring or PDA's at all. It appears to be a unified virtual console driver developed by IBM. Peter
More information about the jpilot mailing list