View previous topic :: View next topic |
Author |
Message |
trumee Guru
Joined: 02 Mar 2003 Posts: 551 Location: London,UK
|
Posted: Sat Oct 25, 2003 2:10 pm Post subject: [Solved] Kernel 2.6, love-sources and Vmware |
|
|
I am running love-sources 2.6.0-test8-love2. Trying to do a vmware-config.pl returns this error:
---------------------------------------------------------------------
grep: /proc/ksyms: No such file or directory
grep: /proc/ksyms: No such file or directory
grep: /proc/ksyms: No such file or directory
Trying to find a suitable vmmon module for your running kernel.
None of VMware Workstation's pre-built vmmon modules is suitable for your
running kernel. Do you want this program to try to build the vmmon module for
your system (you need to have a C compiler installed on your system)? [yes]
Using compiler "/usr/bin/gcc". Use environment variable CC to override.
What is the location of the directory of C header files that match your running
kernel? [/lib/modules/2.6.0-test8-love2/build/include]
Extracting the sources of the vmmon module.
Building the vmmon module.
make: Entering directory `/tmp/vmware-config2/vmmon-only'
make[1]: Entering directory `/tmp/vmware-config2/vmmon-only'
make[2]: Entering directory `/tmp/vmware-config2/vmmon-only/driver-2.6.0-test8-
love2'
make[2]: Leaving directory `/tmp/vmware-config2/vmmon-only/driver-2.6.0-test8-l
ove2'
make[2]: Entering directory `/tmp/vmware-config2/vmmon-only/driver-2.6.0-test8- love2'
../linux/driver.c: In function `init_module':
../linux/driver.c:246: structure has no member named `prev'
../linux/driver.c:247: structure has no member named `next'
make[2]: *** [driver.o] Error 1
make[2]: Leaving directory `/tmp/vmware-config2/vmmon-only/driver-2.6.0-test8-l ove2'
make[1]: *** [driver] Error 2
make[1]: Leaving directory `/tmp/vmware-config2/vmmon-only'
make: *** [auto-build] 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.
-------------------------------------------------------------------------
In short is there any way to run vmware with 2.6?
Thanks
---------------------------------------------------------------------
[EDIT]
Using this patch tp://platan.vc.cvut.cz/pub/vmware/vmware-any-any-update43.tar.gz against test8, sorted out all errors and vmware is working happily.
Last edited by trumee on Mon Oct 27, 2003 1:03 am; edited 1 time in total |
|
Back to top |
|
|
nephros Advocate
Joined: 07 Feb 2003 Posts: 2139 Location: Graz, Austria (Europe - no kangaroos.)
|
Posted: Sat Oct 25, 2003 3:15 pm Post subject: |
|
|
"ksyms" is now called "kallsyms".
I fixed this particular error by editing the vmware-config script (somewhere in /opt/vmware) and replacing all occurences of ksyms with kallsyms.
I have not succeeded to get any networking going with vmware + later 2.6 kernels . vmmon-only works fine though. _________________ Please put [SOLVED] in your topic if you are a moron. |
|
Back to top |
|
|
drjimmy42 Guru
Joined: 03 Feb 2003 Posts: 512 Location: Nashua, NH
|
Posted: Sat Oct 25, 2003 5:18 pm Post subject: grip reports cdrom drive speed, why so slow? |
|
|
I have been ripping a lot of cds recently using grip which uses cdparanoia. While ripping grip reports a read speed of about 5.0x to 5.7x. The thing is i have a 40x cdrom drive. The amount of time it takes to rip an audio disc is consistent with the speed reported by grip, so I don't think that its wrong.
I tried ripping from the command line with cdparanoia with -S 40 (which is supposed to explicitly set the read speed ) and it still takes about as long as a 6x should take.
I am using kernel 2.6.0-test8 with no other problems. I am using scsi emulation. Does anyone know how I can crank up the speed on this cdrom drive? I have a lot of cds and just got an ipod......
Thanks. |
|
Back to top |
|
|
drjimmy42 Guru
Joined: 03 Feb 2003 Posts: 512 Location: Nashua, NH
|
Posted: Sat Oct 25, 2003 5:19 pm Post subject: |
|
|
I have no idea why i posted this here, I was reading this thread and thought i was posting somewhere else. Sorry. |
|
Back to top |
|
|
trumee Guru
Joined: 02 Mar 2003 Posts: 551 Location: London,UK
|
Posted: Sat Oct 25, 2003 5:24 pm Post subject: |
|
|
nephros wrote: | "ksyms" is now called "kallsyms".
I fixed this particular error by editing the vmware-config script (somewhere in /opt/vmware) and replacing all occurences of ksyms with kallsyms.
I have not succeeded to get any networking going with vmware + later 2.6 kernels . vmmon-only works fine though. |
That didnt help much. I replaced ksyms to kallsyms but i am still stuck with this error:
-----------------------------------------------------------------
#vmware-config.pl
Making sure VMware Workstation's services are stopped.
Stopping VMware services:
Virtual machine monitor done
Bridged networking on /dev/vmnet0 done
DHCP server on /dev/vmnet1 done
SMB share server on /dev/vmnet1 done
SMB name server on /dev/vmnet1 done
Host-only networking on /dev/vmnet1 done
DHCP server on /dev/vmnet8 done
NAT networking on /dev/vmnet8 done
Host-only networking on /dev/vmnet8 done
Virtual ethernet done
Trying to find a suitable vmmon module for your running kernel.
None of VMware Workstation's pre-built vmmon modules is suitable for your
running kernel. Do you want this program to try to build the vmmon module for
your system (you need to have a C compiler installed on your system)? [yes]
Using compiler "/usr/bin/gcc". Use environment variable CC to override.
What is the location of the directory of C header files that match your running
kernel? [/lib/modules/2.6.0-test8-love2/build/include]
Extracting the sources of the vmmon module.
Building the vmmon module.
make: Entering directory `/tmp/vmware-config3/vmmon-only'
make[1]: Entering directory `/tmp/vmware-config3/vmmon-only'
make[2]: Entering directory `/tmp/vmware-config3/vmmon-only/driver-2.6.0-test8-love2'
make[2]: Leaving directory `/tmp/vmware-config3/vmmon-only/driver-2.6.0-test8-love2'
make[2]: Entering directory `/tmp/vmware-config3/vmmon-only/driver-2.6.0-test8-love2'
../linux/driver.c: In function `init_module':
../linux/driver.c:246: structure has no member named `prev'
../linux/driver.c:247: structure has no member named `next'
make[2]: *** [driver.o] Error 1
make[2]: Leaving directory `/tmp/vmware-config3/vmmon-only/driver-2.6.0-test8-love2'
make[1]: *** [driver] Error 2
make[1]: Leaving directory `/tmp/vmware-config3/vmmon-only'
make: *** [auto-build] Error 2
make: Leaving directory `/tmp/vmware-config3/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.
----------------------------------------------------------------------
any ideas? |
|
Back to top |
|
|
anfpunk Apprentice
Joined: 29 May 2003 Posts: 275 Location: Columbus, Oh
|
Posted: Mon Oct 27, 2003 5:06 pm Post subject: |
|
|
Why is this marked solved when there is no resolution. I am having this same problem. kallsyms also did not work for me. |
|
Back to top |
|
|
nephros Advocate
Joined: 07 Feb 2003 Posts: 2139 Location: Graz, Austria (Europe - no kangaroos.)
|
Posted: Mon Oct 27, 2003 6:27 pm Post subject: |
|
|
Hmm, the README on the vmware patch site sais:
Quote: |
vmware-any-any-update43.tar.gz
update42 did not work very well for host-guest communication. Apply
necessary changes for < 2.6.0 kernels, and point out that 2.6.0-test7
needs 2.6.0-test7-patch.patch from this directory. 2.6.0-test1 to
2.6.0-test6 are unsupported. |
Now the vmware ebuild pulls in the 43 update, but probably the kernel still needs to be patched. Unfortunately I can not try it out right now, but one of you might hopefully.
The link to the patch in question is here
It's against -test7 but looks small enough that it could apply to later kernels too.
Good luck, and please report.
[EDIT:] scratch that, -test8 should incorporate the fix from that patch.
BTW the thread is marked solved because trumee edited his post after he applied update 43 and it worked. _________________ Please put [SOLVED] in your topic if you are a moron. |
|
Back to top |
|
|
|