| 1 |
On Thu, 2008-06-12 at 21:16 -0400, David Relson wrote: |
| 2 |
> On Fri, 13 Jun 2008 09:23:51 +0930 |
| 3 |
> Iain Buchanan wrote: |
| 4 |
> |
| 5 |
> > David - at this point I'd try a couple of things. Since you've |
| 6 |
> > upgraded your linux-headers, it's a good idea to recompile your |
| 7 |
> > system libc, as per the elog message. |
| 8 |
> > |
| 9 |
> > Also, since you're getting version error messages, recompile your |
| 10 |
> > kernel and reboot into it. Just to make sure, as you've just done |
| 11 |
> > headers and libc (may be a long shot, but may as well rule it out). |
| 12 |
> > |
| 13 |
> > Then unload all vm* modules and recompile them also. (Say no to all |
| 14 |
> > vmware-config questions first, then second time around say yes!). If |
| 15 |
> > it doesn't work, downgrade to a previous version of modules and try |
| 16 |
> > them. I use vmware-modules-1.0.0.11-r1 because that's the only |
| 17 |
> > version that works with workstation 4, which I have a license for. |
| 18 |
> > |
| 19 |
> > Finally, if this all still fails, try with an earlier kernel and see |
| 20 |
> > if it magically works. Then you know it's probably a new kernal |
| 21 |
> > feature thats bugging you! |
| 22 |
> > |
| 23 |
> > I hope you have a few spare clock cycles for all this compiling :) |
| 24 |
> |
| 25 |
> Hi Iain, |
| 26 |
> |
| 27 |
> I've been using 'uname -r' and its reporting '2.6.25-gentoo-r4' matches |
| 28 |
> the module path, i.e. /lib/modules/2.6.25-gentoo-r4/misc/vmnet.ko, in |
| 29 |
> the "invalid module" message. I'm as certain as can be that there's no |
| 30 |
> mismatch here. |
| 31 |
|
| 32 |
don't be so sure! Do you know that you won't get the same message if, |
| 33 |
for example, you used different compilers for the kernel and the module? |
| 34 |
In my experience, this message can appear when the actual kernel number |
| 35 |
is ok, but it's been compiled differently... |
| 36 |
|
| 37 |
> Also, I've removed all vm* packages and reinstalled vmware-server (and |
| 38 |
> whatever it pulls in, i.e. vmware-modules). This was done after |
| 39 |
> removing all vmware entries from /etc/portage/package*, so the vm* |
| 40 |
> packages are all stable versions -- no ~amd64 versions. |
| 41 |
> |
| 42 |
> Haven't tried rebuilding glibc ... |
| 43 |
> |
| 44 |
> Instead I've installed the latest stable amd64 versions of 2.6.24 |
| 45 |
> sources and headers. The kernel is now being built. I should know |
| 46 |
> before too long whether this helps. |
| 47 |
|
| 48 |
good! Let's see what happens... |
| 49 |
|
| 50 |
> Another possibility not yet tried is to disable CONFIG_MODVERSIONS. |
| 51 |
> |
| 52 |
> That's it for now... |
| 53 |
> |
| 54 |
> Regards, |
| 55 |
> |
| 56 |
> David |
| 57 |
-- |
| 58 |
Iain Buchanan <iaindb at netspace dot net dot au> |
| 59 |
|
| 60 |
Let me assure you that to us here at First National, you're not just a |
| 61 |
number. Youre two numbers, a dash, three more numbers, another dash and |
| 62 |
another number. |
| 63 |
-- James Estes |
| 64 |
|
| 65 |
-- |
| 66 |
gentoo-user@l.g.o mailing list |
Archives