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