Hi Perry,
If you are trying to make VMWare work with your SMP enabled kernel then you
will need to make an edit to your vmware-config.pl perl script. There was a
change in how the header files defined some SMP variables that broke the
installation script.
Here are the lines you need to comment out:
# $header_smp = direct_command(shell_string($gHelper{'grep'}) . ' CONFIG_SMP
' . shell_string($answer . '/linux/autoconf.h'));
# if (not ($header_smp eq '')) {
# # linux/autoconf.h contains the up/smp information
# $header_smp = direct_command(shell_string($gHelper{'echo'}) . ' ' .
shell_string('#include <linux/autoconf.h>' . "\n" . $pattern . ' CONFIG_SMP')
.. ' | ' . shell_string($gHelper{'gcc'}) . ' ' . shell_string('-I' . $answer)
.. ' -E - | ' . shell_string($gHelper{'grep'}) . ' ' . shell_string($pattern));
# chop($header_smp);
# $header_smp =~ s/^$pattern (.*)$/$1/;
# $header_smp = ($header_smp eq '1') ? 'yes' : 'no';
# if (not (lc($header_smp) eq lc($gSystem{'smp'}))) {
# if ($source eq 'user') {
# print wrap('The kernel defined by this directory of header files is '
.. (($header_smp eq 'yes') ? 'multiprocessor' : 'uniprocessor') . ', while
your running kernel is ' . (($gSystem{'smp'} eq 'yes') ? 'multiprocessor' :
'uniprocessor') . '.' . "\n\n", 0);
# }
# return '';
# }
# }
They occur at about line 860 in the perl script. I did that and it installed
perfectly. I'm not sure whether that enables SMP in the compiles that it does
as part of the installs but I've got VMWare running NT right now on Man7.2.
Hope that helps.
Mike
On Tuesday 28 November 2000 13:24, you wrote:
> > Hi,
>
> No, this did not solve the problem. It seems that for whatever reason, my
> running an SMP kernel is a problem. I can not get the headers to match up
> to SMP. VM's config script says the following.
>
> The kernel defined by this directory of header files is uniprocessor, while
> yourrunning kernel is multiprocessor.
>
> I even found reference to this problem in there troubleshooting database
> (RedHat 7.x complaint) and there supposed woraround was to change a line in
> /usr/scr/linux/include/autoconf.h to indicate or rather only default to SMP
> 1. This was already this way in my autoconf.h and it doesn't make any
> difference whather I tell it that it is SMP kernel or not... VM sees an SMP
> kernel and sees uP headers. I can't remember having this problem before.
> Please HELP!
>
> Perry
>
> Perry Moon wrote:
> > Thank you,
> >
> > I will let you know how it goes.
> >
> > P.S. the reason for the make mrproper was to allow the application of the
> > kernel patch to support speech synthasizers. It was not something I am
> > accustomed to doing in the past when I compiled my own kernels for SuSE
> > before I switched to Mandrake 7.1 release.
> >
> > David Mihm wrote:
> > > On Tue, 28 Nov 2000, Perry Moon wrote:
> > > > I am looking for a bit of help, and please forgive me if this
> > > > is a dumb question. I compiled a Mandrake flavored kernel for a
> > > > blind friend of mine in Ohio that contained a patch to enable speech
> > > > output from the gitgo to his synth. It was a success. Anyways, during
> > > > the process of building this kernel for him one of the steps was to
> > > > run:
> > > >
> > > > make mrproper
> > > >
> > > > Okay, well now when I went to configure a newer version of
> > > > VMware it needs to rebuild some kernel modules and when it goes to
> > > > look in the /usr/src/linux/include and below directories. It
> > > > complains of missing header files, spacifically version.h . Can
> > > > anyone please tell me how to get back to the original Mandrake 7.1
> > > > source tree with all the
> > >
> > > First off, don't use 'make mrproper', it's not really a needed
> > > step unless you are using alot of non-official patches to the kernel
> > > tree. It not only removes a great deal of need header files (.h) but
> > > also removes your .config file. You will need to completely redo the
> > > 'make xconfig' (or make menuconfig or whatever you used to setup your
> > > kernel) again. After this you will need to do a 'make dep' which then
> > > should get you back to where you want to be - have the version.h files
> > > etc. In the future you can compile your own kernel using the following
> > > -
> > > make xconfig # or make menuconfig or make config - setting up
> > > make dep && make clean && make bzlilo # assuming you edited the
> > > # top Makefile and un-
> > > # commented the /boot
> > > line make modules && make modules_install # module making
> > > depmod -a <kernel version> # ie 2.4.0-test11
> > >
> > > *NOTE: make bzlilo does all the lilo stuff for you; but if you are
> > > unsure, verify everything !before! you reboot with the new kernel. :)
> > >
> > > HTH
> > > --
> > >
> > > | d a v i d @ m i h m
> > > | webmaster @ afterstep.org
> > > | ftpmaster @ afterstep.org
> > >
> > > --
> > >
> > >
> > > -----------------------------------------------------------------------
> > >- Keep in touch with http://mandrakeforum.com:
> > > Subscribe the "[EMAIL PROTECTED]" mailing list.
> >
> >
> > ------------------------------------------------------------------------
> > Keep in touch with http://mandrakeforum.com:
> > Subscribe the "[EMAIL PROTECTED]" mailing list.
----------------------------------------
Content-Type: text/plain; charset="us-ascii"; name="message.footer"
Content-Transfer-Encoding: 8bit
Content-Description:
----------------------------------------
Keep in touch with http://mandrakeforum.com:
Subscribe the "[EMAIL PROTECTED]" mailing list.
