| Summary: | vmware-modules-1.0.0.1{3,5}-r1 fails on kernel 2.6.19-rc{5,6}-mm{1,2} | ||
|---|---|---|---|
| Product: | Gentoo Linux | Reporter: | Rafael Fortes <rafaelmfortes> |
| Component: | Current packages | Assignee: | Gentoo VMWare Bug Squashers [disabled] <vmware+disabled> |
| Status: | RESOLVED FIXED | ||
| Severity: | normal | CC: | erikrj, fd, ikelos, mdoughty, orzel, pauldv |
| Priority: | High | ||
| Version: | unspecified | ||
| Hardware: | x86 | ||
| OS: | Linux | ||
| Whiteboard: | |||
| Package list: | Runtime testing required: | --- | |
| Attachments: |
new compat_kernel.h
script to build modules Patch for compat_kernel.h corrected script to build modules |
||
|
Description
Rafael Fortes
2006-12-06 04:09:18 UTC
Kindly review http://bugs.gentoo.org/page.cgi?id=fields.html#bug_severity; mm-sources is not a supported kernel. http://www.gentoo.org/doc/en/gentoo-kernel.xml#doc_chap2 Created attachment 103549 [details]
new compat_kernel.h
Created attachment 103551 [details]
script to build modules
Copy compat_kernel.h and build.sh to a new directory and run the script. This builds the modules on my AMD64 machine. If vmware-workstation works --- we'll see. I am still downloading the package. Cheers, Florian In order to get vmware running correctly, I had to modify /etc/vmware/init.d/vmware In vmware_load_module() I had to change the extension from o to ko: /sbin/insmod -s -f "/lib/modules/`uname -r`/misc/$1.ko" || exit 1 Also the ping test did not work, so I commented it out: #if lookForHostOnlyNetwork "$ifIp"; then # echo 'Host-only networking disabled because '"$ifIp" # echo 'appears to be a real, physical, existing address.' # echo 'Please run "'"$vmdb_answer_BINDIR"'/vmware-config.pl" to' # echo 'modify your host-only network configuration.' # exit 1 #fi Besides, /etc/init.d/vmware restart does not work, so issue stop and then start. Cheers, Florian Created attachment 104214 [details, diff]
Patch for compat_kernel.h
A better way than just commenting out _syscall1 would be to move it down into the #else clause.
This bug seems to affect all newer kernels (2.6.20-rc1 in my case).
*** Bug 158694 has been marked as a duplicate of this bug. *** Created attachment 105147 [details] corrected script to build modules the script from comment #3 didn't work for me as it has specified the wrong paths, e.g. "/var/tmp/portage/vmware-modules-..." => should be "/var/tmp/portage/app-emulation/vmware-modules-". after the change the vmware modules build fine on my vanilla 2.6.20-rc2. JG Any movement here? This is affecting anyone using kernels 2.6.19 or newer and a lot of brand-new hardware is forcing the issue. I know I have an Intel Q965 board that requires 2.6.20-RCx for the CD-ROM to work. I'm not too keen on deciding at boot time between VMWare or CD-ROM. I hadn't seen any progress on the issue either, so I created a simple portage overlay with a patch I created that allowed me to get the vmware-modules built with 2.6.20 mm kernel I'm using. http://backups.netradius.com/portage-vmware-modules.tgz Hi guys, First off, thanks for providing that overlay tarball, I hope it works as an interim fix before we're able to get a working version out and available. Secondly, I'm afraid that we're all waiting. The situation is that we're making use of a third party version of the module sources which are far more compatible with the various kernels than those provided directly within the vmware source itself. This single set of sources works with all vmware products and often supports the latest kernels sooner than the official sources. The problem however, is that they do not tend to release new versions for fixes in RC kernels, or in -mm kernels. That in turn makes it very difficult for us to be able to support experimental and -mm kernels ourselves, *whilst still maintaining backwards compatibility* for all the other people using previous kernel versions. What this unfortunately means is that we're not going to be able to update the vmware modules any time soon, until the next vmware-any-any source package becomes available. You can watch the sources at http://ftp.cvut.cz/vmware/ and when it goes up from 105 to 106, that may well include fixes for compiling on 2.6.20 kernels (and 2.6.19-mm kernels). If it does feel free to poke me on IRC or drop me an email or something. Until then I'm afraid it will have to be a specific workaround such as the overlay that Erik very kindly posted. I'm sorry I can't give you any better news... 5:( (In reply to comment #11) > You can watch the sources at http://ftp.cvut.cz/vmware/ and > when it goes up from 105 to 106, that may well include fixes for compiling on > 2.6.20 kernels (and 2.6.19-mm kernels). If it does feel free to poke me on IRC > or drop me an email or something. Until then I'm afraid it will have to be a > specific workaround such as the overlay that Erik very kindly posted. > > I'm sorry I can't give you any better news... 5:( Good News! version 107 seems to be out! Please, save me from QEMU! Hi guys, I've bumped the version in the overlay for testing for a few days, so please could you give that a test? To install the overlay, emerge layman, follow the instructions and then do "layman -a vmware". Please note, this will only work with vmware-server, vmware-workstation will probably start complaining about broken digests, because there isn't a version of it in the overlay. You can either emerge with the --digest flag, or wait for it to hit the main tree. Please report any bugs with it back here for now, and hopefully we'll be able to finally close off this bug... 5:) (In reply to comment #13) > I've bumped the version in the overlay for testing for a few days, so please > could you give that a test? I emerged it, then removed the overlay and used it with vmware-workstation 5.5 just fine. Let's get this thing into portage! Ok, since 2.6.20 just went stable it was time to get this into the main tree. I just pushed the any-any107 update out so give the servers a couple of hours and then resync and please let me know if there are any problems. If there are feel free to reopen this bug. Sorry for the delay... 5:) *** Bug 165972 has been marked as a duplicate of this bug. *** |
