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#25441 - [linux] VmWare fails with linux-3.0.1

Attached to Project: Arch Linux
Opened by A.F.G. (TuxLin) - Sunday, 07 August 2011, 23:32 GMT
Last edited by Ionut Biru (wonder) - Monday, 08 August 2011, 19:52 GMT
Task Type Bug Report
Category Kernel
Status Closed
Assigned To No-one
Architecture All
Severity High
Priority Normal
Reported Version
Due in Version Undecided
Due Date Undecided
Percent Complete 100%
Votes 0
Private No

Details

Description:

Vmware unable to compile modules with linux-3.0.1-1

Perhaps, uou must NOT CLEAR subversion field from makefile.

The vmware config suddenly can't configure modconf library.


Kernel-version is 3.0.1, nor 3.0


ago 08 00:56:29.092: app-140006621726464| Log for VMware Workstation pid=2412 version=7.1.4 build=build-385536 option=Release
ago 08 00:56:29.092: app-140006621726464| The process is 64-bit.
ago 08 00:56:29.092: app-140006621726464| Host codepage=UTF-8 encoding=UTF-8
ago 08 00:56:29.092: app-140006621726464| Logging to /tmp/vmware-root/setup-2412.log
ago 08 00:56:29.177: app-140006621726464| Unable to initialize modconf query library


No problem with 2.6.39 and previous kernels.







This task depends upon

Closed by  Ionut Biru (wonder)
Monday, 08 August 2011, 19:52 GMT
Reason for closing:  Not a bug
Additional comments about closing:  not our bug, report to vmware
Comment by Ionut Biru (wonder) - Monday, 08 August 2011, 07:07 GMT
report to vmware. there is nothing we can do here
Comment by A.F.G. (TuxLin) - Monday, 08 August 2011, 09:20 GMT
Are you sure it is not an Arch's issue ?

This morning, I've compile modules by hand without any problem.

I can load modules, but vmware fails test-config. If I skip this test, then vmware loads and run Ok.

User kishi says:

Recompile the testing/linux-3.0 Package (and dependencies, as mentioned before) using the Arch Build System
(see https://wiki.archlinux.org/index.php/ABS). Before running makepkg edit the appropriate kernel config file
(config or config.x86_64) and change CONFIG_LOCALVERSION="-ARCH" to CONFIG_LOCALVERSION=".0-ARCH".
(https://bbs.archlinux.org/viewtopic.php?pid=970689)

I can't do not to test in another distro now. We only work with Arch, but if it is an Arch issue ...

Comment by Ionut Biru (wonder) - Monday, 08 August 2011, 09:28 GMT
that is simply a workaround to bring back the two digits from version, from 3.0-ARCH to 3.0.0-ARCH, which is kinda silly

all the other external modules build fine against our kernel, like nvidia,virtualbox,open-vm-tools and many more without doing anything. Clearly is a bug in their detection script
Comment by A.F.G. (TuxLin) - Monday, 08 August 2011, 10:43 GMT

Do you think so?
Well, if clearly is a vmware bug, you must close this task now.

My problem is solved. Perhaps, in the future, vmware change his config test.

Regards and thanks.


Comment by Alex Fleming (Ethnochemist) - Monday, 08 August 2011, 17:55 GMT
Forgive me for my ignorance, I am a little new: the task closure request states that the "VMWare script should be fixed." Where in the wiki does it state how to do this?

I am able to compile the modules against the new kernel manually; however, I do not understand how to utilize them (where to put them, how to install them..).

If someone could update the wiki on how to get the modules working with the new kernel, this would be a tremendous help to those of us with much less experience. :)

Thanks, guys.
Comment by Igor Saric (karabaja4) - Monday, 08 August 2011, 18:52 GMT
"VMWare script should be fixed, the wiki states how todo this."

Where, exactly? I can't seem to find anything about fixing this in the wiki article.
The program responsible, vmware-modconfig-console, is a BINARY, not a script, so I doubt it's fixable...
Comment by A.F.G. (TuxLin) - Monday, 08 August 2011, 19:45 GMT
Shane Belcroft (Ethnochemist):

If You have the modules compiled:

mkdir /lib/modules/3.0-ARCH/misc
cp vmblock.o /lib/modules/3.0-ARCH/misc/vmblock.ko
cp vmci.o /lib/modules/3.0-ARCH/misc/vmci.ko
cp vmmon.o /lib/modules/3.0-ARCH/misc/vmmon.ko
cp vmnet.o /lib/modules/3.0-ARCH/misc/vmnet.ko
cp vsock.o /lib/modules/3.0-ARCH/misc/vsock.ko

depmod -a

/etc/rc.d/vmware start

nano /usr/bin/vmware

change the next lines:

## if "$BINDIR"/vmware-modconfig --appname="VMware Workstation" --icon="vmware" &&
## /sbin/modinfo vmmon; then
exec "$libdir"/bin/"vmware" "$@"
## fi

nano /usr/bin/vmware-player

change the next lines:

## if "$BINDIR"/vmware-modconfig --appname="VMware Player" --icon="vmware-player" &&
## /sbin/modinfo vmmon; then
exec "$libdir"/bin/"vmplayer" "$@"
## fi




Comment by A.F.G. (TuxLin) - Monday, 08 August 2011, 19:50 GMT
Dule (karabaja4):

Anything in the wiki says about fixing this.

IMHO this IS an ARCH issue related to the kernel version 3.0 nor 3.0.1

If they like close the task I am able to solve this problem.

Regards

Loading...