On Sat, Feb 26, 2000 at 05:08:20PM -0800, aphro wrote:
> that brings back a memory..i had a problem like that(with tons of
> unresolved symbols) with one/both of the vmware modules at one time..i
> fixed it by recompiling the kernel and EXCLUDING the option "Set version
> information on all symbo
On Sat, 26 Feb 2000, Bob Nielsen wrote:
nielse >make: Entering directory `/tmp/vmware-config6/vmnet-only'
nielse >make: Leaving directory `/tmp/vmware-config6/vmnet-only'
nielse >Unable to make a vmnet module that can be loaded in the running kernel:
nielse >/tmp/vmware-config6/vmnet.o: unresolved
I have the source from ftp.kernel.org installed and configured/compiled
it (with make-kpkg) to create my kernel. I had an older version of
vmware which was running fine. When I had the problem, I tried
downgrading to build 364 and it wouldn't install the networking module
either (the error messag
what is the error(s) you get? and do you have the complete kernel source
installed? i never really understood how
'pacakged'(deb/rpm/whatever) kernel source trees were laid out, if you
can't get it working i suggest grabbing the 2.2.14 source(tgz
format) extracting it into /usr/src then run a 'make
On Sat, Feb 26, 2000 at 02:47:08PM -0500, Ben Collins wrote:
> On Sat, Feb 26, 2000 at 12:53:13PM -0700, Bob Nielsen wrote:
> > I am running an up-to-date potato system with 2.2.14 and find that when
> > I try to install vmware, I am able to create and install the vmmon.o
> > module, but not the vm
On Sat, Feb 26, 2000 at 12:53:13PM -0700, Bob Nielsen wrote:
> I am running an up-to-date potato system with 2.2.14 and find that when
> I try to install vmware, I am able to create and install the vmmon.o
> module, but not the vmnet.o module. This previously worked fine. I
> suspect it is becaus
6 matches
Mail list logo