On Tue, May 23, 2006 at 10:47:09PM +0200, Martin Larsson wrote:
> On 5/23/06, Ryan Tandy <[EMAIL PROTECTED]> wrote:
> ># uname -r
> ># ls -l /usr/src/linux
> >
> >Make sure the /usr/src/linux symlink points to the sources for the
> >kernel you're currently running.
>
> They seem to be:
>
> martin # uname -r
> 2.6.16-gentoo-r7
>
> martin # ls -l /usr/src/linux
> lrwxrwxrwx 1 root root 22 2006-05-14 13:23 /usr/src/linux ->
> linux-2.6.16-gentoo-r7
This is a bug with newer kernels. I fixed it by editing the
vmware-config.pl script and basically commenting out the section around
that error message.
# vi `which vmware-config.pl`
Then around line 1979 you'll see this:
if ($header_page_offset =~ /[0-9a-fA-F]{8,}/) {
# # We found a valid page offset
# if (defined($gSystem{'page_offset'}) and
# not (lc($header_page_offset) eq lc($gSystem{'page_offset'}))) {
# if ($source eq 'user') {
# print wrap('The kernel defined by this directory of header files does '
# . 'not have the same address space size as your running '
# . 'kernel.' . "\n\n", 0);
# }
# return '';
# }
}
I inserted the '#' at the beginning of the lines to basically ignore
this check. I haven't had any problems with vmware when it's built.
Alan
--
Alan <[EMAIL PROTECTED]> - http://arcterex.net
--------------------------------------------------------------------
"Backups are for people who don't pray." -- big Mike
--
[email protected] mailing list