| 1 |
On Tue, Oct 20, 2009 at 12:21 AM, Jim Cunning <jcunning@×××××××××××.org> wrote: |
| 2 |
> I upgraded to kernel 2.6.30 and now cannot build the vmware kernel- |
| 3 |
> modules-1.0.0.15-r2 that I need for vmware-workstation-5.5.9. I've seen |
| 4 |
> references on google searches that kernel-modules-1.0.0.25 will work for |
| 5 |
> vmware-5.3 up to vmware-6.something. |
| 6 |
> |
| 7 |
> vmware-workstation-5.5.9 seems to require *only* vmware-modules-1.0.0.15. Is |
| 8 |
> there a way I can change this and rebuild both vmware and its kernel modules? |
| 9 |
|
| 10 |
You could perhaps emerge the newer modules with --nodeps and see if it |
| 11 |
works. You might have to put the old vmware-modules package into |
| 12 |
package.provided so emerge doesn't complain about it. |
| 13 |
|
| 14 |
There are patches to supposedly make it work (it requires patching |
| 15 |
your kernel as well as your vmware-module sources): |
| 16 |
http://www.insecure.ws/2009/04/21/vmware-specific-specific-55x-and-kernel-2629 |
| 17 |
|
| 18 |
Other possible actions would be to go back to older kernel or upgrade |
| 19 |
to newer vmware-workstation. :) |
| 20 |
|
| 21 |
Good luck |
Archives