Arch Linux

Please read this before reporting a bug:
https://wiki.archlinux.org/title/Bug_reporting_guidelines

Do NOT report bugs when a package is just outdated, or it is in the AUR. Use the 'flag out of date' link on the package page, or the Mailing List.

REPEAT: Do NOT report bugs for outdated packages!
Tasklist

FS#5433 - vmware-config gets a version mismatch with kernel-headers 2.6.18-2 and kernel26 2.6.18-3

Attached to Project: Arch Linux
Opened by Shahar (sweiss) - Friday, 22 September 2006, 07:56 GMT
Last edited by Jan de Groot (JGC) - Saturday, 23 September 2006, 13:34 GMT
Task Type Bug Report
Category Packages: Testing
Status Closed
Assigned To Tobias Powalowski (tpowa)
Architecture not specified
Severity Low
Priority Normal
Reported Version 0.7.2 Gimmick
Due in Version Undecided
Due Date Undecided
Percent Complete 100%
Votes 0
Private No

Details

Hello.
Trying to run vmware-config with the given packages installed and while using kernel 2.6.18 is unable to complete itself due to a bug in the header files, or so it seems. It complains about a certain version mismatch between the kernel and the headers, I believe.

Thank you.
This task depends upon

Closed by  Tobias Powalowski (tpowa)
Sunday, 05 November 2006, 07:31 GMT
Reason for closing:  Fixed
Comment by Jan de Groot (JGC) - Friday, 22 September 2006, 09:46 GMT
If vmware-config is affected by kernel-headers, it is definitely a bug in vmware-config, as kernel-headers is the userspace part of the kernelheaders, which are only to be used by non-kernelmodule things. vmware-config checks the headers in /lib/modules/2.6.18-ARCH/build AFAIK, so it looks like you're running a different kernel than the one you have installed.
Comment by Shahar (sweiss) - Saturday, 23 September 2006, 07:01 GMT
I guess it is not kernel-headers then, my bad.
Still, vmware-config is unable to auto-detect the correct include dir like it usually does, this already seems fishy to me.
Comment by Jan de Groot (JGC) - Saturday, 23 September 2006, 11:26 GMT
Did you reboot after installing the new kernel?
Comment by Shahar (sweiss) - Saturday, 23 September 2006, 12:53 GMT
Yes, I did.
Comment by Shahar (sweiss) - Thursday, 28 September 2006, 16:55 GMT
I've now given it the path: /lib/modules/2.6.18-ARCH/build/include/

I still get the same error message:
The directory of kernel headers (version @@VMWARE@@ UTS_RELEASE) does not match
your running kernel (version 2.6.18-ARCH). Even if the module were to compile
successfully, it would not load into the running kernel.

I believe it has something to do with the EXTRAVERSION, because it is not present, for example, in /lib/modules/2.6.18-ARCH/build/Makefile

I've added it there, but still it is not auto-detected, perhaps it's missing in some other places but I don't know which.

Hope this helps.
Comment by Jan de Groot (JGC) - Thursday, 28 September 2006, 17:08 GMT
Looks like a clear bug in vmware to me. It doesn't update it's @@VMWARE@@ placeholders, so it must be a bug in the vmware-config.pl script itself.
Comment by Tobias Powalowski (tpowa) - Friday, 29 September 2006, 06:45 GMT
as i already posted on the forum, .18 kernel outsourced the uts-release
http://bbs.archlinux.org/viewtopic.php?p=197234#197234
Comment by Shahar (sweiss) - Friday, 29 September 2006, 09:17 GMT
I see. I ran the vmware-any-any-update104, which solved this issue.

Thank you.

Loading...