| 1 |
On Thu, Jun 12, 2008 at 7:41 AM, David Relson <relson@×××××××××××××.com> wrote: |
| 2 |
> On Thu, 12 Jun 2008 01:42:50 -0400 |
| 3 |
> Andrey Falko wrote: |
| 4 |
> |
| 5 |
> ...[snip]... |
| 6 |
> |
| 7 |
>> >> |
| 8 |
>> >> Attempted to upgrade vmware-modules from 1.0.0.15-r1 to |
| 9 |
>> >> 1.0.0.17-r1 and found it blocked by vmware-server-1.0.5.80187: |
| 10 |
>> >> |
| 11 |
>> >> emerge --oneshot vmware-modules |
| 12 |
>> >> Calculating dependencies... done! |
| 13 |
>> >> [ebuild U ] app-emulation/vmware-modules-1.0.0.17-r1 |
| 14 |
>> >> [1.0.0.15-r1] [blocks B ] |
| 15 |
>> >> >=app-emulation/vmware-modules-1.0.0.16 (is blocking |
| 16 |
>> >> >app-emulation/vmware-server-1.0.5.80187) |
| 17 |
>> > You need to emerge -C =app-emulation/vmware-modules-1.0.0.16 |
| 18 |
>> > first...I think. |
| 19 |
>> Sorry, I meant vmware-modules-1.0.0.15-r1. |
| 20 |
>> >> |
| 21 |
>> >> It seems that the vmware-server ebuild only permits |
| 22 |
>> >> modules-1.0.0.15 ... |
| 23 |
>> >> |
| 24 |
>> >> Is any of this ringing any bells??? |
| 25 |
>> >> |
| 26 |
>> >> Also, reading the google translation of the German posting, it |
| 27 |
>> >> seems to say there was a conflict with dual core and vmmon and |
| 28 |
>> >> (perhaps) disabling SMP, then building vmmon, then enabling SMP |
| 29 |
>> >> gave a working module. This is a guess and I've not yet tried it. |
| 30 |
> |
| 31 |
> OK. I've removed all vmware builds. "emerge -C vmware-modules" reports |
| 32 |
> |
| 33 |
> --- Couldn't find 'vmware-modules' to unmerge. |
| 34 |
> |
| 35 |
> and 'find /var/db/pkg/ -name "*vmware*"' doesn't find anything. |
| 36 |
> |
| 37 |
> Doing a new "emerge -aDtqv vmware-server" brings in: |
| 38 |
> |
| 39 |
> [ebuild N ] app-emulation/vmware-server-1.0.5.80187 |
| 40 |
> [ebuild N ] app-emulation/vmware-modules-1.0.0.15-r1 |
| 41 |
> |
| 42 |
> Then "modprobe vmmon" reports (as before): |
| 43 |
> |
| 44 |
> FATAL: Error inserting vmmon |
| 45 |
> (/lib/modules/2.6.25-gentoo-r4/misc/vmmon.ko): Invalid module format |
| 46 |
> |
| 47 |
> with /var/log/messages saying: |
| 48 |
> |
| 49 |
> Jun 12 07:26:15 osage vmmon: disagrees about version of symbol |
| 50 |
> struct_module |
| 51 |
> |
| 52 |
> I've googled the above message and found this thread (from last night) |
| 53 |
> and another thread in which the running kernel version didn't match the |
| 54 |
> installed version of linux-headers. I've running the 2.6.25-gentoo-r4 |
| 55 |
> kernel and have the same versions of linux-headers and gentoo-sources |
| 56 |
> installed. |
| 57 |
> |
| 58 |
> Looking for more ideas as to what's wrong :-> |
| 59 |
> |
| 60 |
> Regards, |
| 61 |
> |
| 62 |
> David |
| 63 |
> -- |
| 64 |
> gentoo-user@l.g.o mailing list |
| 65 |
> |
| 66 |
> |
| 67 |
|
| 68 |
Opps, it was my mistake. I have 1.0.0.17 installed with ~x86 |
| 69 |
workstation, server. According to vmware-server ebuild, only 1.0.0.15 |
| 70 |
will work with the latest vmware-server. I'd file a bug in |
| 71 |
bugs.gentoo.org that vmware-server does not work for you with 2.6.25. |
| 72 |
As a work around, try to use 2.6.24 kernel or earlier. |
| 73 |
|
| 74 |
Sorry for my blunder. |
| 75 |
-- |
| 76 |
gentoo-user@l.g.o mailing list |
Archives