Mailinglist Archive: opensuse-amd64 (449 mails)

[Bill Allen <suse@xxxxxxxxxxxxxxxxxx>]

Thanks to all who replied. For the record, I did:

make cloneconfig # this didn't do the trick - at least by itself, then I
make modules

and vmware-config.pl ran through to completion.

Now, I've got a new problem. When I try to create a virtual machine using my 
windows installation on /windows/C, vmware complains that it is a read-only 
system, which given the /etc/fstab line that I have, it certainly appears to 
be:

/dev/hde1            /windows/C           ntfs      
ro,users,gid=users,umask=00
02,nls=utf8 0 0

I tried changing this to:

/dev/hde1            /windows/C           ntfs       
rw,users,gid=users,umask=00
02,nls=utf8 0 0

but, I got the same result. How can I make my WinXP partition read-write?

Regards and thanks again,
Bill

On Sunday 03 October 2004 18:45, Mike Tierney wrote:
> It looks like there's no kernel configuration file (.config), try doing a:
>
> make cloneconfig
>
> This should query your currently running kernel config and generate the
> correct ".config" file for you. Then try it again. If that fail try doing a
> full "make" or make modules/make modules install/make install
>
> Cheers
>
> -----Original Message-----
> From: Bill Allen [mailto:suse@xxxxxxxxxxxxxxxxxx]
> Sent: Monday, 4 October 2004 12:19 a.m.
> To: suse-amd64@xxxxxxxx
> Subject: [suse-amd64] Problem compiling vmware driver
>
>
> Hi. I'm trying to install vmware on suse 9.1 professional for amd64 as the
> host OS. When I run vmware-config.pl I get the following. Any ideas on what
> is wrong. I have seen that there are people who have gotten vmware to work
> for this setup, so I suspect that I'm just missing a package or something.
> Any help appreciated.
>
> Regards,
> Bill
>
>
> -------------- snip ---------------------------
>
>
> What is the location of the directory of C header files that match your
> running
> kernel? [/usr/src/linux/include]
>
> Extracting the sources of the vmmon module.
>
> Building the vmmon module.
>
> Using 2.6.x kernel build system.
> make: Entering directory `/tmp/vmware-config2/vmmon-only'
> make -C /usr/src/linux/include/.. SUBDIRS=$PWD SRCROOT=$PWD/. modules
> make[1]: Entering directory `/usr/src/linux-2.6.5-7.108'
> Makefile:438: .config: No such file or directory
>
> WARNING: Symbol version dump /usr/src/linux-2.6.5-7.108/Module.symvers is  
> missing, modules will have CONFIG_MODVERSIONS disabled.
>
>   CC [M]  /tmp/vmware-config2/vmmon-only/linux/driver.o
>   CC [M]  /tmp/vmware-config2/vmmon-only/linux/hostif.o
>   CC [M]  /tmp/vmware-config2/vmmon-only/common/cpuid.o
>   CC [M]  /tmp/vmware-config2/vmmon-only/common/memtrack.o
>   CC [M]  /tmp/vmware-config2/vmmon-only/common/phystrack.o
>   CC [M]  /tmp/vmware-config2/vmmon-only/common/task.o
>   CC [M]  /tmp/vmware-config2/vmmon-only/common/vmx86.o
>   LD [M]  /tmp/vmware-config2/vmmon-only/vmmon.o
>   Building modules, stage 2.
> /usr/src/linux-2.6.5-7.108/scripts/Makefile.modpost:38: .config: No such
> file
> or directory
> make[2]: *** No rule to make target `.config'.  Stop.
> make[1]: *** [modules] Error 2
> make[1]: Leaving directory `/usr/src/linux-2.6.5-7.108'
> make: *** [vmmon.ko] Error 2
> make: Leaving directory `/tmp/vmware-config2/vmmon-only'
> Unable to build the vmmon module.
>
> For more information on how to troubleshoot module-related problems, please
> visit our Web site at "http://www.vmware.com/download/modules/modules.html";
> and
> "http://www.vmware.com/support/reference/linux/prebuilt_modules_linux.html";
>.
>
> Execution aborted.
>
> ------------------- end snip -------------------
>
> --
> Check the List-Unsubscribe header to unsubscribe
> For additional commands, email: suse-amd64-help@xxxxxxxx