On Thu, Jun 12, 2008 at 5:51 AM, Andrey Falko <[EMAIL PROTECTED]> wrote:
> On Thu, Jun 12, 2008 at 7:41 AM, David Relson <[EMAIL PROTECTED]> > wrote: > > On Thu, 12 Jun 2008 01:42:50 -0400 > > Andrey Falko wrote: > > > > ...[snip]... > > > >> >> > >> >> Attempted to upgrade vmware-modules from 1.0.0.15-r1 to > >> >> 1.0.0.17-r1 and found it blocked by vmware-server-1.0.5.80187: > >> >> > >> >> emerge --oneshot vmware-modules > >> >> Calculating dependencies... done! > >> >> [ebuild U ] app-emulation/vmware-modules-1.0.0.17-r1 > >> >> [1.0.0.15-r1] [blocks B ] > >> >> >=app-emulation/vmware-modules-1.0.0.16 (is blocking > >> >> >app-emulation/vmware-server-1.0.5.80187) > >> > You need to emerge -C =app-emulation/vmware-modules-1.0.0.16 > >> > first...I think. > >> Sorry, I meant vmware-modules-1.0.0.15-r1. > >> >> > >> >> It seems that the vmware-server ebuild only permits > >> >> modules-1.0.0.15 ... > >> >> > >> >> Is any of this ringing any bells??? > >> >> > >> >> Also, reading the google translation of the German posting, it > >> >> seems to say there was a conflict with dual core and vmmon and > >> >> (perhaps) disabling SMP, then building vmmon, then enabling SMP > >> >> gave a working module. This is a guess and I've not yet tried it. > > > > OK. I've removed all vmware builds. "emerge -C vmware-modules" reports > > > > --- Couldn't find 'vmware-modules' to unmerge. > > > > and 'find /var/db/pkg/ -name "*vmware*"' doesn't find anything. > > > > Doing a new "emerge -aDtqv vmware-server" brings in: > > > > [ebuild N ] app-emulation/vmware-server-1.0.5.80187 > > [ebuild N ] app-emulation/vmware-modules-1.0.0.15-r1 > > > > Then "modprobe vmmon" reports (as before): > > > > FATAL: Error inserting vmmon > > (/lib/modules/2.6.25-gentoo-r4/misc/vmmon.ko): Invalid module format > > > > with /var/log/messages saying: > > > > Jun 12 07:26:15 osage vmmon: disagrees about version of symbol > > struct_module > > > > I've googled the above message and found this thread (from last night) > > and another thread in which the running kernel version didn't match the > > installed version of linux-headers. I've running the 2.6.25-gentoo-r4 > > kernel and have the same versions of linux-headers and gentoo-sources > > installed. > > > > Looking for more ideas as to what's wrong :-> > > > > Regards, > > > > David > > -- > > gentoo-user@lists.gentoo.org mailing list > > > > > > Opps, it was my mistake. I have 1.0.0.17 installed with ~x86 > workstation, server. According to vmware-server ebuild, only 1.0.0.15 > will work with the latest vmware-server. I'd file a bug in > bugs.gentoo.org that vmware-server does not work for you with 2.6.25. > As a work around, try to use 2.6.24 kernel or earlier. > > Sorry for my blunder. > -- > gentoo-user@lists.gentoo.org mailing list > > I have been watching this thread and wondering why my vmware keeps working. Then I noticed that all the 2.6.25 kernels are ~x86. If I were you I'd check if they're ~arch for you too, and if so it might be best to go back to stable versions of both vmware and the kernel. -- Kevin O'Gorman, PhD
