Kernel 2.6.22 and vmware-player-modules
Just for information:
If someone got problems reinstalling vmware-player-modules after the last Kernel update to 2.6.22, here's a workaround:
1. Get the package vmware-player-modules from the aur..
2. try building vmware-player-modules with makepkg (that's where the problem occurs)
3. download the file vmnet.tar from here, unpack it somewhere
4. copy the .tar and the unpacked folder to the vmware-player-modules source ( cp -r vmnet* /var/abs/local/vmware-player-modules/src/vmware-player-distrib/lib/modules/source )
5. build the package again with makepkg -e and install it
yay.
drfindley wrote:
That fixed my problem. I removed kvm-modules and re-synced my kernel, in case kvm-modules had trashed my kvm.ko files.
Also one thing that would really help would be to add the udev-rules from the kvm-modules and create the group kvm. I don't know if that's appropriate with the mainline kernel or not, though.
We'll have to re-add the rules and some other files in the qemu package (which includes the userspace kvm stuff).
Similar Messages
-
[Solved] Can not build modules for VMware Player after kernel updates
I have a problem generating the modules for VMware Player after kernel updates. I am using VMware Player version 5.02 (without patches) and the softlink according to the Wiki.
When I start the installation of the modules from the GUI, the program just closes. Running vmware-modconfig in the CLI generates the following log file:
2013-04-29T09:49:27.891+01:00| vthread-3| I120: Log for VMware Workstation pid=7478 version=9.0.2 build=build-1031769 option=Release
2013-04-29T09:49:27.891+01:00| vthread-3| I120: The process is 64-bit.
2013-04-29T09:49:27.891+01:00| vthread-3| I120: Host codepage=UTF-8 encoding=UTF-8
2013-04-29T09:49:27.891+01:00| vthread-3| I120: Host is Linux 3.8.10-1-ARCH 2012.11.29
2013-04-29T09:49:27.891+01:00| vthread-3| I120: Msg_Reset:
2013-04-29T09:49:27.891+01:00| vthread-3| I120: [msg.dictionary.load.openFailed] Cannot open file "/usr/lib/vmware/settings": Datei oder Verzeichnis nicht gefunden.
2013-04-29T09:49:27.891+01:00| vthread-3| I120: ----------------------------------------
2013-04-29T09:49:27.891+01:00| vthread-3| I120: PREF Optional preferences file not found at /usr/lib/vmware/settings. Using default values.
2013-04-29T09:49:27.891+01:00| vthread-3| I120: Msg_Reset:
2013-04-29T09:49:27.891+01:00| vthread-3| I120: [msg.dictionary.load.openFailed] Cannot open file "/root/.vmware/config": Datei oder Verzeichnis nicht gefunden.
2013-04-29T09:49:27.891+01:00| vthread-3| I120: ----------------------------------------
2013-04-29T09:49:27.891+01:00| vthread-3| I120: PREF Optional preferences file not found at /root/.vmware/config. Using default values.
2013-04-29T09:49:27.891+01:00| vthread-3| W110: Logging to /tmp/vmware-root/vmware-modconfig-7478.log
2013-04-29T09:49:27.892+01:00| vthread-3| W110: Icon name must be set.
Interestingly, after deinstallation and reinstallation the VMWare Player works fine.
Any hint, what's going wrong?
Last edited by Thomas_Do (2013-08-07 07:25:51)Today, (Kernel 3.10.5-1, VMware Player version 5.02 with kernel patches) the modules could successful be generated from the CLI:
vmware-modconfig --console --install-all
Solved (somehow). -
Updated PKGBUILD for vmware-server-modules 2.0.2
Hi.
I have updated the PKGBUILD for the vmware-server-modules and added patches for kernel 2.6.35 and 2.6.36.
The package is currently marked as an orphan, so I'll have to adopt it do upload the changes, right?
Could someone please take a look at this, and say if it is good enough.
I haven't really made any changes other than adding patches for kernel 2.6.35 and 2.6.36, but since there are some 'not so positive comments' following this package in AUR maybe there is more that should be done?
It works on my x86_64 2.6.36-arch install.
pkgname=vmware-server-modules
pkgver=2.0.2
pkgrel=4
pkgdesc="Kernel modules for VMware Server"
arch=('i686' 'x86_64')
url="http://www.vmware.com/products/server/"
license=('custom')
depends=('kernel26>=2.6.32')
makedepends=('kernel26-headers')
conflicts=('vmware-workstation-modules' 'vmware-player-modules')
install=vmware-server-modules.install
_kernver=`uname -r`
source=(VMware-server-2.0.2-203138-update-2.patch vmware-server-modules-autoconf.patch vmware-server-modules-vsock-kernel2.6.35.patch vmware-server-modules-vmmon-kernel2.6.36.patch)
md5sums=('774a6361a443834205bc0172498bb2c0'
'91ea48c3d4779f531cb942be09248dba'
'3325f1b34eb21ee7d4cceb5f0da852f1'
'bfd62533e023b696cf7ff45379732b71')
case ${CARCH} in
i686)
source=(${source[@]} 'VMware-server-2.0.2-203138.i386.tar.gz')
md5sums=(${md5sums[@]} '6eb844d1ab4aed6128438e5f587d10bb');;
x86_64)
source=(${source[@]} 'VMware-server-2.0.2-203138.x86_64.tar.gz')
md5sums=(${md5sums[@]} 'cc7aef813008eeb7150c21547d431b39');;
esac
build() {
cd "$srcdir/vmware-server-distrib/lib/modules/source"
for module in *.tar; do
tar xf $module
done
cd "$srcdir/vmware-server-distrib"
# patch
patch -p1 < ../VMware-server-2.0.2-203138-update-2.patch
patch -p2 < ../vmware-server-modules-autoconf.patch
if [[ ${_kernver:0:6} == "2.6.35" ]]; then
patch -p1 < ../vmware-server-modules-vsock-kernel2.6.35.patch
fi
if [[ ${_kernver:0:6} == "2.6.36" ]]; then
patch -p1 < ../vmware-server-modules-vsock-kernel2.6.35.patch
patch -p1 < ../vmware-server-modules-vmmon-kernel2.6.36.patch
fi
cd "$srcdir/vmware-server-distrib/lib/modules/source"
for module in vmci vsock vmmon vmnet; do
make -C $module-only HEADER_DIR=/lib/modules/$_kernver/build/include || \
return 1
install -D -m644 $module-only/$module.ko \
"$pkgdir/lib/modules/$_kernver/misc/$module.ko"
done
# License
install -D -m644 "$srcdir/vmware-server-distrib/doc/EULA" \
"$pkgdir/usr/share/licenses/vmware-server-modules/EULA"
install -D -m644 "$srcdir/vmware-server-distrib/doc/open_source_licenses.txt" \
"$pkgdir/usr/share/licenses/vmware-server-modules/open_source_licenses.txt"
sed -i -e "s|KERNEL_VERSION='.*'|KERNEL_VERSION='$_kernver'|" \
"$startdir/vmware-server-modules.install"i don'T think that there will ever be a PKGBUILD for VMWare, because it's commercial software... but i posted alot of hints in the "Package Configuration Problems" Forum...
http://bbs.archlinux.org/viewtopic.php? … highlight=
nearly each posible problem is described there... if u still have problems, post ur errors and anything u got about it there, and i try to help u..... -
Windows 7 DPI scaling causes problems in VMware Player
Hi there,
I'm running Windows 7 x86 Professional and VMware Player 3.0.0. Windows 7 is set to 150% larger fonts (DPI scaling).
If I start VMware Player with this DPI setting the guest VM is scaled aswell. If I set Windows 7 NOT to use DPI scaling only for VMware Player about 25% of the guest's screen is unreachable (lower-right). (See this screenshot: http://pix.sonhult.se/vmware.jpg)
The guest is running Ubuntu 9.10 x86.
Have anyone else been experimenting with DPI scaling and VMware Player? Any ideas?
Thanks in advance!I know this is a thread necro but it's kinda hilarious and sad. I just searched the forums for "player dpi" and here I stumble upon my own post on the subject over five years ago.
This time I'm running VMware Player version 11.1.0.58002 on a Windows 7 SP1 host where I've got the DPI set to 125%. I ran a Visual Studio tool called Spy++ while one of my VMs is compacting and it shows this information for that window:
Window (id) "VMware Player" (Dialog)
--- Window (id) "Compacting virtual disk..." Static
--- Window (id) "" msctls_progress32
--- Window (id) "Cancel" Button
At 125% DPI I've never seen the Cancel button.
Besides continuing to be indifferent to people who don't have perfect eyesight, this problem is going to occur more frequently when 4K displays become more popular with businesses. People will need to use much higher DPI to be able to read the fonts at those super-high resolutions. -
Lenovo T430 - VMware Player - Windows 7 - webcam is not working
Hi,
I have Windows7 and VMware PLayer.
Webcam is working fine on my Host - it is recognized as ThinkVantage Virtual Camera.
On WMware player webcam is not recognized.
I have tried such drivers on VMware player:
g1c814ww.exe - installed - but webcam is not working
grcu07ww.exe - error message on vmware: Not Supported
Saying honestly I need such driver (make a copy from my host): ThinkVantage Virtual camera
But I need *.INF files. Unfortunately on my Host system I have found only *.SYS files for these driver.
Does anybody know how to enable Integrated camera on WMware player?
Regards
PawelHi Manish,
I've done this several times with Win 7 Pro. IIRC the procedure is to not try to activate during installation. Run the full install without a key. Reboot and attempt to activate. If that fails there should be a link or phone number offered that you can call for phone activation.
Here in the US anyway the calling the number gets you an automated activation process.
Z.
The large print: please read the Community Participation Rules before posting. Include as much information as possible: model, machine type, operating system, and a descriptive subject line. Do not include personal information: serial number, telephone number, email address, etc. The fine print: I do not work for, nor do I speak for Lenovo. Unsolicited private messages will be ignored. ... GeezBlog
English Community Deutsche Community Comunidad en Español Русскоязычное Сообщество -
I have had no luck getting WEC7 to run in a virtual machine, either downloading it from Platform Builder or building a standalone. Judging from other posts, it appears at least a couple other people have made it work, I guess it's some simple
setting I'm missing or some secret thing I'm unaware of (yes I'm very frustrated with this). Based on other posts, HyperV appears to be out of the question how about VMWare, anyone able to make that work?@ Cicero564,
I instaled WEC7 to Virtual PC (Windows 7 host), Hyper-V (Windows Server 2008 R2 host) and VMware Player (Windows 7 host) and able to download OS-image/application to target device without problem.
I also know of others using Virtual PC, Hyper-V and VMware Player as the development environment for WEC7 without problem.
It's known to work. Check to make sure the virtual machine is proper installed and configured.
Follow the recommended software installation sequences to install the required software.
Samuel Phung [eMVP] Blog: http://www.embedded101.com/samuelp101/ Twitter: @Samuelp101
Saying you got it to work without linking to any method or anything is basically nothing. -
Vmware-server-modules and kernel 2.6.19 [solved]
I'm trying to rebuild the vmware server modules from AUR for the new kernel. After adjusting the files for the kernel version and doing makepkg I get the following:
==> Validating source files with MD5sums
VMware-server-1.0.1-29996.tar.gz ... Passed
==> Extracting Sources...
==> tar --use-compress-program=gzip -xf VMware-server-1.0.1-29996.tar.gz
==> Starting build()...
Using 2.6.x kernel build system.
make: Entering directory `/home/mars/SRC/vmware-server-modules/src/vmware-server-distrib/lib/modules/source/vmmon-only'
make -C /lib/modules/2.6.19-ARCH/build/include/.. SUBDIRS=$PWD SRCROOT=$PWD/. modules
make[1]: Entering directory `/usr/src/linux-2.6.19-ARCH'
CC [M] /home/mars/SRC/vmware-server-modules/src/vmware-server-distrib/lib/modules/source/vmmon-only/linux/driver.o
CC [M] /home/mars/SRC/vmware-server-modules/src/vmware-server-distrib/lib/modules/source/vmmon-only/linux/hostif.o
CC [M] /home/mars/SRC/vmware-server-modules/src/vmware-server-distrib/lib/modules/source/vmmon-only/common/cpuid.o
CC [M] /home/mars/SRC/vmware-server-modules/src/vmware-server-distrib/lib/modules/source/vmmon-only/common/hash.o
CC [M] /home/mars/SRC/vmware-server-modules/src/vmware-server-distrib/lib/modules/source/vmmon-only/common/memtrack.o
CC [M] /home/mars/SRC/vmware-server-modules/src/vmware-server-distrib/lib/modules/source/vmmon-only/common/phystrack.o
CC [M] /home/mars/SRC/vmware-server-modules/src/vmware-server-distrib/lib/modules/source/vmmon-only/common/task.o
CC [M] /home/mars/SRC/vmware-server-modules/src/vmware-server-distrib/lib/modules/source/vmmon-only/common/vmx86.o
CC [M] /home/mars/SRC/vmware-server-modules/src/vmware-server-distrib/lib/modules/source/vmmon-only/vmcore/moduleloop.o
LD [M] /home/mars/SRC/vmware-server-modules/src/vmware-server-distrib/lib/modules/source/vmmon-only/vmmon.o
Building modules, stage 2.
MODPOST 1 modules
CC /home/mars/SRC/vmware-server-modules/src/vmware-server-distrib/lib/modules/source/vmmon-only/vmmon.mod.o
LD [M] /home/mars/SRC/vmware-server-modules/src/vmware-server-distrib/lib/modules/source/vmmon-only/vmmon.ko
make[1]: Leaving directory `/usr/src/linux-2.6.19-ARCH'
cp -f vmmon.ko ./../vmmon.o
make: Leaving directory `/home/mars/SRC/vmware-server-modules/src/vmware-server-distrib/lib/modules/source/vmmon-only'
Using 2.6.x kernel build system.
make: Entering directory `/home/mars/SRC/vmware-server-modules/src/vmware-server-distrib/lib/modules/source/vmnet-only'
make -C /lib/modules/2.6.19-ARCH/build/include/.. SUBDIRS=$PWD SRCROOT=$PWD/. modules
make[1]: Entering directory `/usr/src/linux-2.6.19-ARCH'
CC [M] /home/mars/SRC/vmware-server-modules/src/vmware-server-distrib/lib/modules/source/vmnet-only/driver.o
CC [M] /home/mars/SRC/vmware-server-modules/src/vmware-server-distrib/lib/modules/source/vmnet-only/hub.o
CC [M] /home/mars/SRC/vmware-server-modules/src/vmware-server-distrib/lib/modules/source/vmnet-only/userif.o
/home/mars/SRC/vmware-server-modules/src/vmware-server-distrib/lib/modules/source/vmnet-only/userif.c: In function 'VNetCopyDatagramToUser':
/home/mars/SRC/vmware-server-modules/src/vmware-server-distrib/lib/modules/source/vmnet-only/userif.c:629: error: 'CHECKSUM_HW' undeclared (first use in this function)
/home/mars/SRC/vmware-server-modules/src/vmware-server-distrib/lib/modules/source/vmnet-only/userif.c:629: error: (Each undeclared identifier is reported only once
/home/mars/SRC/vmware-server-modules/src/vmware-server-distrib/lib/modules/source/vmnet-only/userif.c:629: error: for each function it appears in.)
make[2]: *** [/home/mars/SRC/vmware-server-modules/src/vmware-server-distrib/lib/modules/source/vmnet-only/userif.o] Error 1
make[1]: *** [_module_/home/mars/SRC/vmware-server-modules/src/vmware-server-distrib/lib/modules/source/vmnet-only] Error 2
make[1]: Leaving directory `/usr/src/linux-2.6.19-ARCH'
make: *** [vmnet.ko] Error 2
make: Leaving directory `/home/mars/SRC/vmware-server-modules/src/vmware-server-distrib/lib/modules/source/vmnet-only'
==> ERROR: Build Failed. Aborting...
It seems the userif module breaks. I haven't a clue how to solve this. :?Progress:
AUR
which leads to
http://www.vmware.com/community/thread. … 4&tstart=0
EDIT: package in AUR has been updated. Thnx pizzapunk. -
[Solved] VMWare Player 4.0.0 and kernel 3.1.4-1-ARCH
Hi,
i followed the instructions here https://wiki.archlinux.org/index.php/VM … n.2FPlayer
while running the modconfig command i get this error.
Stopping VMware services:
VMware Authentication Daemon done
VM communication interface socket family done
Virtual machine communication interface done
Virtual machine monitor done
Blocking file system done
Using 2.6.x kernel build system.
make: Entering directory `/tmp/vmware-root/modules/vmmon-only'
make -C /lib/modules/3.1.4-1-ARCH/build/include/.. SUBDIRS=$PWD SRCROOT=$PWD/. \
MODULEBUILDDIR= modules
make[1]: Entering directory `/usr/src/linux-3.1.4-1-ARCH'
CC [M] /tmp/vmware-root/modules/vmmon-only/linux/driver.o
CC [M] /tmp/vmware-root/modules/vmmon-only/linux/iommu.o
CC [M] /tmp/vmware-root/modules/vmmon-only/linux/hostif.o
CC [M] /tmp/vmware-root/modules/vmmon-only/linux/driverLog.o
CC [M] /tmp/vmware-root/modules/vmmon-only/common/memtrack.o
CC [M] /tmp/vmware-root/modules/vmmon-only/common/vmx86.o
CC [M] /tmp/vmware-root/modules/vmmon-only/common/apic.o
CC [M] /tmp/vmware-root/modules/vmmon-only/common/task.o
CC [M] /tmp/vmware-root/modules/vmmon-only/common/cpuid.o
CC [M] /tmp/vmware-root/modules/vmmon-only/common/comport.o
CC [M] /tmp/vmware-root/modules/vmmon-only/common/hashFunc.o
CC [M] /tmp/vmware-root/modules/vmmon-only/common/phystrack.o
CC [M] /tmp/vmware-root/modules/vmmon-only/vmcore/moduleloop.o
LD [M] /tmp/vmware-root/modules/vmmon-only/vmmon.o
Building modules, stage 2.
MODPOST 1 modules
CC /tmp/vmware-root/modules/vmmon-only/vmmon.mod.o
LD [M] /tmp/vmware-root/modules/vmmon-only/vmmon.ko
make[1]: Leaving directory `/usr/src/linux-3.1.4-1-ARCH'
make -C $PWD SRCROOT=$PWD/. \
MODULEBUILDDIR= postbuild
make[1]: Entering directory `/tmp/vmware-root/modules/vmmon-only'
make[1]: »postbuild« ist bereits aktualisiert.
make[1]: Leaving directory `/tmp/vmware-root/modules/vmmon-only'
cp -f vmmon.ko ./../vmmon.o
make: Leaving directory `/tmp/vmware-root/modules/vmmon-only'
No protocol specified
No protocol specified
Built vmmon module
Using 2.6.x kernel build system.
make: Entering directory `/tmp/vmware-root/modules/vmnet-only'
make -C /lib/modules/3.1.4-1-ARCH/build/include/.. SUBDIRS=$PWD SRCROOT=$PWD/. \
MODULEBUILDDIR= modules
make[1]: Entering directory `/usr/src/linux-3.1.4-1-ARCH'
CC [M] /tmp/vmware-root/modules/vmnet-only/driver.o
CC [M] /tmp/vmware-root/modules/vmnet-only/hub.o
CC [M] /tmp/vmware-root/modules/vmnet-only/userif.o
CC [M] /tmp/vmware-root/modules/vmnet-only/netif.o
CC [M] /tmp/vmware-root/modules/vmnet-only/bridge.o
CC [M] /tmp/vmware-root/modules/vmnet-only/filter.o
CC [M] /tmp/vmware-root/modules/vmnet-only/smac.o
CC [M] /tmp/vmware-root/modules/vmnet-only/procfs.o
CC [M] /tmp/vmware-root/modules/vmnet-only/smac_compat.o
CC [M] /tmp/vmware-root/modules/vmnet-only/vnetEvent.o
CC [M] /tmp/vmware-root/modules/vmnet-only/vnetUserListener.o
In file included from /tmp/vmware-root/modules/vmnet-only/bridge.c:51:0:
/tmp/vmware-root/modules/vmnet-only/compat_netdevice.h:186:0: Warnung: »alloc_netdev« redefiniert [standardmäßig aktiviert]
include/linux/netdevice.h:2438:0: Anmerkung: dies ist die Stelle der vorherigen Definition
/tmp/vmware-root/modules/vmnet-only/compat_netdevice.h:187:0: Warnung: »alloc_etherdev« redefiniert [standardmäßig aktiviert]
include/linux/etherdevice.h:53:0: Anmerkung: dies ist die Stelle der vorherigen Definition
/tmp/vmware-root/modules/vmnet-only/compat_netdevice.h:208:1: Fehler: In Konflikt stehende Typen für »netif_start_queue«
include/linux/netdevice.h:1804:20: Anmerkung: Vorherige Definition von »netif_start_queue« war hier
/tmp/vmware-root/modules/vmnet-only/compat_netdevice.h: In Funktion »netif_start_queue«:
/tmp/vmware-root/modules/vmnet-only/compat_netdevice.h:210:21: Fehler: »struct device« hat kein Element namens »tbusy«
/tmp/vmware-root/modules/vmnet-only/compat_netdevice.h: Auf höchster Ebene:
/tmp/vmware-root/modules/vmnet-only/compat_netdevice.h:214:1: Fehler: In Konflikt stehende Typen für »netif_stop_queue«
include/linux/netdevice.h:1869:20: Anmerkung: Vorherige Definition von »netif_stop_queue« war hier
/tmp/vmware-root/modules/vmnet-only/compat_netdevice.h: In Funktion »netif_stop_queue«:
/tmp/vmware-root/modules/vmnet-only/compat_netdevice.h:216:19: Fehler: »struct device« hat kein Element namens »tbusy«
/tmp/vmware-root/modules/vmnet-only/compat_netdevice.h: Auf höchster Ebene:
/tmp/vmware-root/modules/vmnet-only/compat_netdevice.h:220:1: Fehler: In Konflikt stehende Typen für »netif_queue_stopped«
include/linux/netdevice.h:1895:19: Anmerkung: Vorherige Definition von »netif_queue_stopped« war hier
/tmp/vmware-root/modules/vmnet-only/compat_netdevice.h: In Funktion »netif_queue_stopped«:
/tmp/vmware-root/modules/vmnet-only/compat_netdevice.h:222:11: Fehler: »struct device« hat kein Element namens »tbusy«
/tmp/vmware-root/modules/vmnet-only/compat_netdevice.h:222:11: Fehler: »struct device« hat kein Element namens »tbusy«
/tmp/vmware-root/modules/vmnet-only/compat_netdevice.h: Auf höchster Ebene:
/tmp/vmware-root/modules/vmnet-only/compat_netdevice.h:226:1: Fehler: In Konflikt stehende Typen für »netif_wake_queue«
include/linux/netdevice.h:1838:20: Anmerkung: Vorherige Definition von »netif_wake_queue« war hier
/tmp/vmware-root/modules/vmnet-only/compat_netdevice.h: In Funktion »netif_wake_queue«:
/tmp/vmware-root/modules/vmnet-only/compat_netdevice.h:228:21: Fehler: »struct device« hat kein Element namens »tbusy«
/tmp/vmware-root/modules/vmnet-only/compat_netdevice.h:229:4: Fehler: Implizite Deklaration der Funktion »mark_bh« [-Werror=implicit-function-declaration]
/tmp/vmware-root/modules/vmnet-only/compat_netdevice.h:229:12: Fehler: »NET_BH« nicht deklariert (erste Benutzung in dieser Funktion)
/tmp/vmware-root/modules/vmnet-only/compat_netdevice.h:229:12: Anmerkung: jeder nicht deklarierte Bezeichner wird nur einmal für jede Funktion, in der er vorkommt, gemeldet
/tmp/vmware-root/modules/vmnet-only/compat_netdevice.h: Auf höchster Ebene:
/tmp/vmware-root/modules/vmnet-only/compat_netdevice.h:233:1: Fehler: In Konflikt stehende Typen für »netif_running«
include/linux/netdevice.h:1911:19: Anmerkung: Vorherige Definition von »netif_running« war hier
/tmp/vmware-root/modules/vmnet-only/compat_netdevice.h: In Funktion »netif_running«:
/tmp/vmware-root/modules/vmnet-only/compat_netdevice.h:235:14: Fehler: »struct device« hat kein Element namens »start«
/tmp/vmware-root/modules/vmnet-only/compat_netdevice.h: Auf höchster Ebene:
/tmp/vmware-root/modules/vmnet-only/compat_netdevice.h:239:1: Fehler: In Konflikt stehende Typen für »netif_carrier_ok«
include/linux/netdevice.h:2145:19: Anmerkung: Vorherige Definition von »netif_carrier_ok« war hier
/tmp/vmware-root/modules/vmnet-only/compat_netdevice.h:245:1: Fehler: In Konflikt stehende Typen für »netif_carrier_on«
include/linux/netdevice.h:2154:13: Anmerkung: Vorherige Deklaration von »netif_carrier_on« war hier
/tmp/vmware-root/modules/vmnet-only/compat_netdevice.h:250:1: Fehler: In Konflikt stehende Typen für »netif_carrier_off«
include/linux/netdevice.h:2156:13: Anmerkung: Vorherige Deklaration von »netif_carrier_off« war hier
cc1: Einige Warnungen werden als Fehler behandelt
make[2]: *** [/tmp/vmware-root/modules/vmnet-only/bridge.o] Fehler 1
make[2]: *** Warte auf noch nicht beendete Prozesse...
In file included from /tmp/vmware-root/modules/vmnet-only/netif.c:43:0:
/tmp/vmware-root/modules/vmnet-only/compat_netdevice.h:186:0: Warnung: »alloc_netdev« redefiniert [standardmäßig aktiviert]
include/linux/netdevice.h:2438:0: Anmerkung: dies ist die Stelle der vorherigen Definition
/tmp/vmware-root/modules/vmnet-only/compat_netdevice.h:187:0: Warnung: »alloc_etherdev« redefiniert [standardmäßig aktiviert]
include/linux/etherdevice.h:53:0: Anmerkung: dies ist die Stelle der vorherigen Definition
/tmp/vmware-root/modules/vmnet-only/compat_netdevice.h:208:1: Fehler: In Konflikt stehende Typen für »netif_start_queue«
include/linux/netdevice.h:1804:20: Anmerkung: Vorherige Definition von »netif_start_queue« war hier
/tmp/vmware-root/modules/vmnet-only/compat_netdevice.h: In Funktion »netif_start_queue«:
/tmp/vmware-root/modules/vmnet-only/compat_netdevice.h:210:21: Fehler: »struct device« hat kein Element namens »tbusy«
/tmp/vmware-root/modules/vmnet-only/compat_netdevice.h: Auf höchster Ebene:
/tmp/vmware-root/modules/vmnet-only/compat_netdevice.h:214:1: Fehler: In Konflikt stehende Typen für »netif_stop_queue«
include/linux/netdevice.h:1869:20: Anmerkung: Vorherige Definition von »netif_stop_queue« war hier
/tmp/vmware-root/modules/vmnet-only/compat_netdevice.h: In Funktion »netif_stop_queue«:
/tmp/vmware-root/modules/vmnet-only/compat_netdevice.h:216:19: Fehler: »struct device« hat kein Element namens »tbusy«
/tmp/vmware-root/modules/vmnet-only/compat_netdevice.h: Auf höchster Ebene:
/tmp/vmware-root/modules/vmnet-only/compat_netdevice.h:220:1: Fehler: In Konflikt stehende Typen für »netif_queue_stopped«
include/linux/netdevice.h:1895:19: Anmerkung: Vorherige Definition von »netif_queue_stopped« war hier
/tmp/vmware-root/modules/vmnet-only/compat_netdevice.h: In Funktion »netif_queue_stopped«:
/tmp/vmware-root/modules/vmnet-only/compat_netdevice.h:222:11: Fehler: »struct device« hat kein Element namens »tbusy«
/tmp/vmware-root/modules/vmnet-only/compat_netdevice.h:222:11: Fehler: »struct device« hat kein Element namens »tbusy«
/tmp/vmware-root/modules/vmnet-only/compat_netdevice.h: Auf höchster Ebene:
/tmp/vmware-root/modules/vmnet-only/compat_netdevice.h:226:1: Fehler: In Konflikt stehende Typen für »netif_wake_queue«
include/linux/netdevice.h:1838:20: Anmerkung: Vorherige Definition von »netif_wake_queue« war hier
/tmp/vmware-root/modules/vmnet-only/compat_netdevice.h: In Funktion »netif_wake_queue«:
/tmp/vmware-root/modules/vmnet-only/compat_netdevice.h:228:21: Fehler: »struct device« hat kein Element namens »tbusy«
/tmp/vmware-root/modules/vmnet-only/compat_netdevice.h:229:4: Fehler: Implizite Deklaration der Funktion »mark_bh« [-Werror=implicit-function-declaration]
/tmp/vmware-root/modules/vmnet-only/compat_netdevice.h:229:12: Fehler: »NET_BH« nicht deklariert (erste Benutzung in dieser Funktion)
/tmp/vmware-root/modules/vmnet-only/compat_netdevice.h:229:12: Anmerkung: jeder nicht deklarierte Bezeichner wird nur einmal für jede Funktion, in der er vorkommt, gemeldet
/tmp/vmware-root/modules/vmnet-only/compat_netdevice.h: Auf höchster Ebene:
/tmp/vmware-root/modules/vmnet-only/compat_netdevice.h:233:1: Fehler: In Konflikt stehende Typen für »netif_running«
include/linux/netdevice.h:1911:19: Anmerkung: Vorherige Definition von »netif_running« war hier
/tmp/vmware-root/modules/vmnet-only/compat_netdevice.h: In Funktion »netif_running«:
/tmp/vmware-root/modules/vmnet-only/compat_netdevice.h:235:14: Fehler: »struct device« hat kein Element namens »start«
/tmp/vmware-root/modules/vmnet-only/compat_netdevice.h: Auf höchster Ebene:
/tmp/vmware-root/modules/vmnet-only/compat_netdevice.h:239:1: Fehler: In Konflikt stehende Typen für »netif_carrier_ok«
include/linux/netdevice.h:2145:19: Anmerkung: Vorherige Definition von »netif_carrier_ok« war hier
/tmp/vmware-root/modules/vmnet-only/compat_netdevice.h:245:1: Fehler: In Konflikt stehende Typen für »netif_carrier_on«
include/linux/netdevice.h:2154:13: Anmerkung: Vorherige Deklaration von »netif_carrier_on« war hier
/tmp/vmware-root/modules/vmnet-only/compat_netdevice.h:250:1: Fehler: In Konflikt stehende Typen für »netif_carrier_off«
include/linux/netdevice.h:2156:13: Anmerkung: Vorherige Deklaration von »netif_carrier_off« war hier
/tmp/vmware-root/modules/vmnet-only/netif.c: In Funktion »VNetNetIfSetup«:
/tmp/vmware-root/modules/vmnet-only/netif.c:149:7: Fehler: »struct net_device« hat kein Element namens »init«
/tmp/vmware-root/modules/vmnet-only/netif.c:150:7: Fehler: »struct net_device« hat kein Element namens »open«
/tmp/vmware-root/modules/vmnet-only/netif.c:151:7: Fehler: »struct net_device« hat kein Element namens »hard_start_xmit«
/tmp/vmware-root/modules/vmnet-only/netif.c:152:7: Fehler: »struct net_device« hat kein Element namens »stop«
/tmp/vmware-root/modules/vmnet-only/netif.c:153:7: Fehler: »struct net_device« hat kein Element namens »get_stats«
/tmp/vmware-root/modules/vmnet-only/netif.c:154:7: Fehler: »struct net_device« hat kein Element namens »set_mac_address«
/tmp/vmware-root/modules/vmnet-only/netif.c:155:7: Fehler: »struct net_device« hat kein Element namens »set_multicast_list«
/tmp/vmware-root/modules/vmnet-only/netif.c: In Funktion »VNetNetIfNetDeviceToNetIf«:
/tmp/vmware-root/modules/vmnet-only/netif.c:196:14: Fehler: »struct net_device« hat kein Element namens »priv«
/tmp/vmware-root/modules/vmnet-only/netif.c: In Funktion »VNetNetIf_Create«:
/tmp/vmware-root/modules/vmnet-only/netif.c:311:4: Fehler: Implizite Deklaration der Funktion »compat_alloc_netdev« [-Werror=implicit-function-declaration]
/tmp/vmware-root/modules/vmnet-only/netif.c:311:8: Warnung: Zuweisung erzeugt Zeiger von Ganzzahl ohne Typkonvertierung [standardmäßig aktiviert]
/tmp/vmware-root/modules/vmnet-only/netif.c:316:7: Fehler: »struct net_device« hat kein Element namens »priv«
/tmp/vmware-root/modules/vmnet-only/netif.c: In Funktion »VNetNetIfReceive«:
/tmp/vmware-root/modules/vmnet-only/netif.c:397:4: Warnung: Übergabe des Arguments 1 von »netif_running« von inkompatiblem Zeigertyp [standardmäßig aktiviert]
/tmp/vmware-root/modules/vmnet-only/compat_netdevice.h:233:1: Anmerkung: »struct device *« erwartet, aber Argument hat Typ »struct net_device *«
/tmp/vmware-root/modules/vmnet-only/netif.c: In Funktion »VNetNetifOpen«:
/tmp/vmware-root/modules/vmnet-only/netif.c:477:4: Warnung: Übergabe des Arguments 1 von »netif_start_queue« von inkompatiblem Zeigertyp [standardmäßig aktiviert]
/tmp/vmware-root/modules/vmnet-only/compat_netdevice.h:208:1: Anmerkung: »struct device *« erwartet, aber Argument hat Typ »struct net_device *«
/tmp/vmware-root/modules/vmnet-only/netif.c: In Funktion »VNetNetifClose«:
/tmp/vmware-root/modules/vmnet-only/netif.c:525:4: Warnung: Übergabe des Arguments 1 von »netif_stop_queue« von inkompatiblem Zeigertyp [standardmäßig aktiviert]
/tmp/vmware-root/modules/vmnet-only/compat_netdevice.h:214:1: Anmerkung: »struct device *« erwartet, aber Argument hat Typ »struct net_device *«
/tmp/vmware-root/modules/vmnet-only/netif.c: In Funktion »netif_running«:
/tmp/vmware-root/modules/vmnet-only/compat_netdevice.h:236:1: Warnung: Kontrollfluss erreicht Ende von Nicht-void-Funktion [-Wreturn-type]
cc1: Einige Warnungen werden als Fehler behandelt
make[2]: *** [/tmp/vmware-root/modules/vmnet-only/netif.o] Fehler 1
make[1]: *** [_module_/tmp/vmware-root/modules/vmnet-only] Fehler 2
make[1]: Leaving directory `/usr/src/linux-3.1.4-1-ARCH'
make: *** [vmnet.ko] Fehler 2
make: Leaving directory `/tmp/vmware-root/modules/vmnet-only'
Unable to install vmnet
Maybe someone has an idea whats going wrong ?
stubb
Last edited by stubb (2011-12-01 23:45:44)rm /usr/lib/vmware/modules/source/.patched
fixed it -
Trying to install Vmware Player on OEL 4-kernel 2.6.9-78.0.0.0.1.ELhugemem
All
I need to run a preconfigured Vmware VM on one of ours Enterprise Linux servers. I've already installed VMware-Player-3.1.2-301548.i386.bundle on the machine, no error message, but now when I try to run vmplayer I am getting the following message:
before you can run vmware, several modules must be compiled and loaded into the running kernel:
kernel headers 2.6.9-78.0.0.0.1.ELHugemem
kernel headers for version 2.6.9-78.0.0.0.1.ELHugemem were not found...
I've already searched both on google and on Oracle website for a package containing this version of kernel headers, but didn't find them.
I've did an up2date -i kernel-devel, some kernel headers got installed, but it seems they are at the wrong version:
[root@dscdap01 ~]# ls -la /usr/src/kernels/
total 24
drwxr-xr-x 4 root root 4096 Nov 2 06:59 .
drwxr-xr-x 4 root root 4096 Dec 4 2008 ..
drwxr-xr-x 17 root root 4096 Nov 1 09:42 2.6.9-89.31.1.0.1.EL-hugemem-i686
drwxr-xr-x 17 root root 4096 Nov 2 06:59 2.6.9-89.31.1.0.1.EL-i686
As far as I can see, I have two paths for solving this:
1: update the running kernel to 2.6.9-89.31.1.0.1.EL-hugemem-i686 - in order to do that I'll have to restart the machine, which is quite risky because this is an important machine used for many projects and I do not have physical access to it; in case something goes wrong I'll have to make an SR to the GIT guys, and pray for a quick resolution
2. find this particular version on kernel headers (2.6.9-78.0.0.0.1.ELHugemem), install them in a non-standard location and then point vmplayer installer to that location in order to compile and plug them into the running kernel
Questions:
- If I choose the 2nd path:
-- where can I find this particular kernel headers version?
-- after vmplayer compiles them, will it request a machine restart, or plugging them into the running kernel will be possible without restart?
-- I already did an up2date -u, so the entire system excepting the running kernel is updated to whatever is in Oracle's internal repositories. Will this conflict somehow with an older running kernel and modules?
-If I choose the 1th path (update the kernel itself and reboot the machine):
-- will then vmplayer be able to compile and install the kernel modules without asking for another restart?
Thanks a lot for your feedback.
Any idea is appreciated, even pointing me to someone in Oracle that might help (I am an Oracle employee) would be useful.
Regards
SerbanThanks for your reply Joe. I did not realise that I shall search for the package name without "ELHugemem" part since the headers are probably the same. Please correct me if I'm wrong here.
So I downloaded the i686 package, but now I get this message:
[root@dscdap01 ~]# rpm -iv kernel-devel-2.6.9-78.0.1.EL.i686.rpm
warning: kernel-devel-2.6.9-78.0.1.EL.i686.rpm: V3 DSA signature: NOKEY, key ID 82fd17b2
Preparing packages for installation...
package kernel-devel-2.6.9-89.31.1.0.1.EL (which is newer than kernel-devel-2.6.9-78.0.1.EL) is already installed
I am not sure if I shall do a "rpm -ivf" for this package, forcing it to install. Will this command install the package alongside the existing one, or will it overwrite it? My guess is that it will install it alongside the existing one, but since this system is an important one I would prefer to ask before doing any stupid mistake... -
Trying to install Vmware Player on OEL and running into an error
All
I need to run a preconfigured Vmware VM on one of ours Enterprise Linux servers. I've already installed VMware-Player-3.13.*.bundle on the machine, no error message, but now when I try to run vmplayer I am getting the following message :
before you can run vmware, several modules must be compiled and loaded into the running kernel:
kernel headers 2.6.9-89.0.0.0.1ELxenU
kernel headers for version 2.6.9-89.0.0.0.1ELxenU were not found...
Any help would be appreciated.
Thanks and regards
AnilThanks Avi for the pointer.
I did a 'sudo -su ' and ran 'rpm -ivh kernel-xenU-devel-2.6.9-89.0.0.0.1.EL.i686.rpm' and it went through successfully.
But then when I launched VMPlayer, a popup came up saying " Before you run VMWare, several modules must be compiled and loaded into the running kernel.". I clicked on 'Install' to continue.
Another popup came up saying "Failed to run /usr/bin/vmware-gksu '/usr/bin/vmware-modconfig' --icon='vmware-player' --appname='VMware' --gcc='/usr/bin/gcc' --headers='/lib/modules/2.6.9-89.0.0.0.1.ELxenU/build/include' --gcc-ignore-minor as user root. Failed to exec new process. No such file or directory."
And then I had to exit.
This is the log contents when VMPlayer was run :
Dec 01 18:27:11.567: app-3086636736| Log for VMware Workstation pid=11013 version=7.1.3 build=build-324285 option=Release
Dec 01 18:27:11.567: app-3086636736| The process is 32-bit.
Dec 01 18:27:11.567: app-3086636736| Host codepage=UTF-8 encoding=UTF-8
Dec 01 18:27:11.567: app-3086636736| Logging to /tmp/vmware-vmotamar/setup-11013.log
Dec 01 18:27:11.944: app-3086636736| modconf query interface initialized
Dec 01 18:27:11.945: app-3086636736| modconf library initialized
Dec 01 18:27:11.979: app-3086636736| Your GCC version: 3.4
Dec 01 18:27:11.989: app-3086636736| Your GCC version: 3.4
Dec 01 18:27:12.011: app-3086636736| Your GCC version: 3.4
Dec 01 18:27:12.036: app-3086636736| Your GCC version: 3.4
Dec 01 18:27:12.058: app-3086636736| Your GCC version: 3.4
Dec 01 18:27:12.104: app-3086636736| Trying to find a suitable PBM set for kernel 2.6.9-89.0.0.0.1.ELxenU.
Dec 01 18:27:12.108: app-3086636736| Trying to find a suitable PBM set for kernel 2.6.9-89.0.0.0.1.ELxenU.
Dec 01 18:27:12.113: app-3086636736| Trying to find a suitable PBM set for kernel 2.6.9-89.0.0.0.1.ELxenU.
Dec 01 18:27:12.117: app-3086636736| Trying to find a suitable PBM set for kernel 2.6.9-89.0.0.0.1.ELxenU.
Dec 01 18:27:12.121: app-3086636736| Trying to find a suitable PBM set for kernel 2.6.9-89.0.0.0.1.ELxenU.
Dec 01 18:27:12.146: app-3086636736| Trying to find a suitable PBM set for kernel 2.6.9-89.0.0.0.1.ELxenU.
Dec 01 18:27:12.150: app-3086636736| Trying to find a suitable PBM set for kernel 2.6.9-89.0.0.0.1.ELxenU.
Dec 01 18:27:12.154: app-3086636736| Trying to find a suitable PBM set for kernel 2.6.9-89.0.0.0.1.ELxenU.
Dec 01 18:27:12.158: app-3086636736| Trying to find a suitable PBM set for kernel 2.6.9-89.0.0.0.1.ELxenU.
Dec 01 18:27:12.162: app-3086636736| Trying to find a suitable PBM set for kernel 2.6.9-89.0.0.0.1.ELxenU.
Dec 01 18:27:12.168: app-3086636736| Your GCC version: 3.4
Dec 01 18:27:12.184: app-3086636736| Your GCC version: 3.4
Dec 01 18:27:19.720: app-3086636736| Trying to find a suitable PBM set for kernel 2.6.9-89.0.0.0.1.ELxenU.
Dec 01 18:27:19.725: app-3086636736| Trying to find a suitable PBM set for kernel 2.6.9-89.0.0.0.1.ELxenU.
Dec 01 18:27:19.729: app-3086636736| Trying to find a suitable PBM set for kernel 2.6.9-89.0.0.0.1.ELxenU.
Dec 01 18:27:19.733: app-3086636736| Trying to find a suitable PBM set for kernel 2.6.9-89.0.0.0.1.ELxenU.
Dec 01 18:27:19.738: app-3086636736| Trying to find a suitable PBM set for kernel 2.6.9-89.0.0.0.1.ELxenU.
Dec 01 18:27:19.745: app-3086636736| Your GCC version: 3.4
Dec 01 18:27:19.764: app-3086636736| Your GCC version: 3.4
Dec 01 18:27:19.807: app-3086636736| Trying to find a suitable PBM set for kernel 2.6.9-89.0.0.0.1.ELxenU.
Dec 01 18:27:19.812: app-3086636736| Trying to find a suitable PBM set for kernel 2.6.9-89.0.0.0.1.ELxenU.
Dec 01 18:27:19.817: app-3086636736| Trying to find a suitable PBM set for kernel 2.6.9-89.0.0.0.1.ELxenU.
Dec 01 18:27:19.822: app-3086636736| Trying to find a suitable PBM set for kernel 2.6.9-89.0.0.0.1.ELxenU.
Dec 01 18:27:19.827: app-3086636736| Trying to find a suitable PBM set for kernel 2.6.9-89.0.0.0.1.ELxenU.
Dec 01 18:27:19.827: app-3086636736| Relaunching with /usr/bin/vmware-gksu '/usr/bin/vmware-modconfig' icon='vmware-player' appname='VMware' gcc='/usr/bin/gcc' headers='/lib/modules/2.6.9-89.0.0.0.1.ELxenU/build/include' --gcc-ignore-minor
Could you please suggest? -
VMware player won't start after kernel update
Hi,
today I've updated to 3.9.6-1 kernel and all went good. So I wanted to start my vmware player to start a vm. Of course I've done the needed steps in the vmplayer wiki page to setup the new headers and stuff after kernel update for vmplayer. Also I've ran "vmware-patch -f" and ran trough. But still get an error when I wanted to start the player in the "/tmp/vmware-root/vmware-modconfig-11986.log":
2013-06-16T13:03:51.680+01:00| vthread-3| I120: Log for VMware Workstation pid=11986 version=9.0.2 build=build-1031769 option=Release
2013-06-16T13:03:51.680+01:00| vthread-3| I120: The process is 64-bit.
2013-06-16T13:03:51.680+01:00| vthread-3| I120: Host codepage=UTF-8 encoding=UTF-8
2013-06-16T13:03:51.680+01:00| vthread-3| I120: Host is Linux 3.9.6-1-ARCH 2013.04.01
2013-06-16T13:03:51.680+01:00| vthread-3| I120: Msg_Reset:
2013-06-16T13:03:51.680+01:00| vthread-3| I120: [msg.dictionary.load.openFailed] Cannot open file "/usr/lib/vmware/settings": No such file or directory.
2013-06-16T13:03:51.680+01:00| vthread-3| I120: ----------------------------------------
2013-06-16T13:03:51.680+01:00| vthread-3| I120: PREF Optional preferences file not found at /usr/lib/vmware/settings. Using default values.
2013-06-16T13:03:51.680+01:00| vthread-3| I120: Msg_Reset:
2013-06-16T13:03:51.680+01:00| vthread-3| I120: [msg.dictionary.load.openFailed] Cannot open file "/root/.vmware/config": No such file or directory.
2013-06-16T13:03:51.680+01:00| vthread-3| I120: ----------------------------------------
2013-06-16T13:03:51.680+01:00| vthread-3| I120: PREF Optional preferences file not found at /root/.vmware/config. Using default values.
2013-06-16T13:03:51.680+01:00| vthread-3| I120: Msg_Reset:
2013-06-16T13:03:51.680+01:00| vthread-3| I120: [msg.dictionary.load.openFailed] Cannot open file "/root/.vmware/preferences": No such file or directory.
2013-06-16T13:03:51.680+01:00| vthread-3| I120: ----------------------------------------
2013-06-16T13:03:51.680+01:00| vthread-3| I120: PREF Failed to load user preferences.
2013-06-16T13:03:51.680+01:00| vthread-3| W110: Logging to /tmp/vmware-root/vmware-modconfig-11986.log
2013-06-16T13:03:51.687+01:00| vthread-3| I120: Reading in info for the vmmon module.
2013-06-16T13:03:51.687+01:00| vthread-3| I120: Reading in info for the vmnet module.
2013-06-16T13:03:51.687+01:00| vthread-3| I120: Reading in info for the vmblock module.
2013-06-16T13:03:51.687+01:00| vthread-3| I120: Reading in info for the vmci module.
2013-06-16T13:03:51.687+01:00| vthread-3| I120: Reading in info for the vsock module.
2013-06-16T13:03:51.687+01:00| vthread-3| I120: Setting vsock to depend on vmci.
2013-06-16T13:03:51.687+01:00| vthread-3| I120: Created new pathsHash.
2013-06-16T13:03:51.687+01:00| vthread-3| I120: Invoking modinfo on "vmmon".
2013-06-16T13:03:51.689+01:00| vthread-3| I120: "/sbin/modinfo" exited with status 0.
2013-06-16T13:03:51.689+01:00| vthread-3| I120: Invoking modinfo on "vmnet".
2013-06-16T13:03:51.690+01:00| vthread-3| I120: "/sbin/modinfo" exited with status 0.
2013-06-16T13:03:51.690+01:00| vthread-3| I120: Invoking modinfo on "vmblock".
2013-06-16T13:03:51.691+01:00| vthread-3| I120: "/sbin/modinfo" exited with status 0.
2013-06-16T13:03:51.691+01:00| vthread-3| I120: Invoking modinfo on "vmci".
2013-06-16T13:03:51.693+01:00| vthread-3| I120: "/sbin/modinfo" exited with status 0.
2013-06-16T13:03:51.693+01:00| vthread-3| I120: Invoking modinfo on "vsock".
2013-06-16T13:03:51.696+01:00| vthread-3| I120: "/sbin/modinfo" exited with status 0.
Maybe it has something to do with the last filesystem update?
But I don't know what to do really and couldn't found anything on that.
thankssorry, found something now in another thread here. this fix works just fyi:
kokoko3k wrote:
Quick and dirty workaround to fully update your system
sudo pacman -Suy #update everything
sudo mkdir -p /usr/local/lib/gtkmm && cd /usr/local/lib/gtkmm
sudo wget http://arm.konnichi.com/2013/01/05/extra/os/x86_64/gtkmm-2.24.2-2-x86_64.pkg.tar.xz
#sudo wget http://arm.konnichi.com/2013/01/05/extra/os/i686/gtkmm-2.24.2-2-i686.pkg.tar.xz #The bug affects i686 too.
sudo tar -xvf ./gtkmm-2.24.2-2-x86_64.pkg.tar.xz
#sudo tar -xvf ./gtkmm-2.24.2-2-i686.pkg.tar.xz #The bug affects i686 too.
LD_LIBRARY_PATH=/usr/local/lib/gtkmm/usr/lib/ vmplayer #start it with old libraries -
[SOLVED] VMware player update error with kernel 2.6.35
I have WMware player 3.1, it was working fine until I upgrade to kernel 2.6.35. Here is WMware error message:
aoû 24 20:51:34.275: app-3076503232| Log for VMware Workstation pid=6643 version=7.1.0 build=build-261024 option=Release
aoû 24 20:51:34.275: app-3076503232| The process is 32-bit.
aoû 24 20:51:34.275: app-3076503232| Host codepage=UTF-8 encoding=UTF-8
aoû 24 20:51:34.275: app-3076503232| Logging to /tmp/vmware-root/setup-6643.log
aoû 24 20:51:34.377: app-3076503232| modconf query interface initialized
aoû 24 20:51:34.378: app-3076503232| modconf library initialized
aoû 24 20:51:34.468: app-3076503232| Your GCC version: 4.5
aoû 24 20:51:34.477: app-3076503232| Your GCC version: 4.5
aoû 24 20:51:34.509: app-3076503232| Your GCC version: 4.5
aoû 24 20:51:34.553: app-3076503232| Your GCC version: 4.5
aoû 24 20:51:34.585: app-3076503232| Your GCC version: 4.5
aoû 24 20:51:34.695: app-3076503232| Trying to find a suitable PBM set for kernel 2.6.35-ARCH.
aoû 24 20:51:34.700: app-3076503232| Trying to find a suitable PBM set for kernel 2.6.35-ARCH.
aoû 24 20:51:34.705: app-3076503232| Trying to find a suitable PBM set for kernel 2.6.35-ARCH.
aoû 24 20:51:34.710: app-3076503232| Trying to find a suitable PBM set for kernel 2.6.35-ARCH.
aoû 24 20:51:34.714: app-3076503232| Trying to find a suitable PBM set for kernel 2.6.35-ARCH.
aoû 24 20:51:34.779: app-3076503232| Trying to find a suitable PBM set for kernel 2.6.35-ARCH.
aoû 24 20:51:34.783: app-3076503232| Trying to find a suitable PBM set for kernel 2.6.35-ARCH.
aoû 24 20:51:34.788: app-3076503232| Trying to find a suitable PBM set for kernel 2.6.35-ARCH.
aoû 24 20:51:34.793: app-3076503232| Trying to find a suitable PBM set for kernel 2.6.35-ARCH.
aoû 24 20:51:34.797: app-3076503232| Trying to find a suitable PBM set for kernel 2.6.35-ARCH.
aoû 24 20:51:34.803: app-3076503232| Your GCC version: 4.5
aoû 24 20:51:34.837: app-3076503232| Your GCC version: 4.5
aoû 24 20:51:34.948: app-3076503232| Trying to find a suitable PBM set for kernel 2.6.35-ARCH.
aoû 24 20:51:34.953: app-3076503232| Trying to find a suitable PBM set for kernel 2.6.35-ARCH.
aoû 24 20:51:34.958: app-3076503232| Trying to find a suitable PBM set for kernel 2.6.35-ARCH.
aoû 24 20:51:34.962: app-3076503232| Trying to find a suitable PBM set for kernel 2.6.35-ARCH.
aoû 24 20:51:34.967: app-3076503232| Trying to find a suitable PBM set for kernel 2.6.35-ARCH.
aoû 24 20:51:34.973: app-3076503232| Your GCC version: 4.5
aoû 24 20:51:35.013: app-3076503232| Your GCC version: 4.5
aoû 24 20:51:35.187: app-3076503232| Trying to find a suitable PBM set for kernel 2.6.35-ARCH.
aoû 24 20:51:35.192: app-3076503232| Trying to find a suitable PBM set for kernel 2.6.35-ARCH.
aoû 24 20:51:35.198: app-3076503232| Trying to find a suitable PBM set for kernel 2.6.35-ARCH.
aoû 24 20:51:35.203: app-3076503232| Trying to find a suitable PBM set for kernel 2.6.35-ARCH.
aoû 24 20:51:35.208: app-3076503232| Trying to find a suitable PBM set for kernel 2.6.35-ARCH.
aoû 24 20:51:35.656: app-3076503232| Trying to find a suitable PBM set for kernel 2.6.35-ARCH.
aoû 24 20:51:35.657: app-3076503232| Building module vmmon.
aoû 24 20:51:35.657: app-3076503232| Extracting the sources of the vmmon module.
aoû 24 20:51:35.697: app-3076503232| Building module with command: /usr/bin/make -C /tmp/vmware-root/modules/vmmon-only auto-build SUPPORT_SMP=1 HEADER_DIR=/lib/modules/2.6.35-ARCH/build/include CC=/usr/bin/gcc GREP=/usr/bin/make IS_GCC_3=no VMCCVER=4.5.1
aoû 24 20:51:41.031: app-3076503232| Failed to compile module vmmon!
Thanks for help!
Last edited by srivo (2010-10-26 02:05:16)I tried this it didn't work:
% wget http://www.sputnick-area.net/scripts/vm … .6.35.bash
--2011-06-15 11:18:03-- http://www.sputnick-area.net/scripts/vm … .6.35.bash
Resolving www.sputnick-area.net... 91.121.18.134
Connecting to www.sputnick-area.net|91.121.18.134|:80... connected.
HTTP request sent, awaiting response... 200 OK
Length: 6992 (6.8K) [text/plain]
Saving to: “vmware7.1.1-patch-kernel-2.6.35.bash.1”
100%[======================================================================>] 6,992 --.-K/s in 0.07s
2011-06-15 11:18:06 (97.8 KB/s) - “vmware7.1.1-patch-kernel-2.6.35.bash.1” saved [6992/6992]
% ./vmware7.1.1-patch-kernel-2.6.35.bash
This script have been already applied !
% vmware-modconfig --console --install-all
Stopping vmware (via systemctl): [ OK ]
Using 2.6.x kernel build system.
make: Entering directory `/tmp/vmware-root-62598440/modules/vmmon-only'
make -C /lib/modules/2.6.38.7-30.fc15.x86_64/build/include/.. SUBDIRS=$PWD SRCROOT=$PWD/. \
MODULEBUILDDIR= modules
make[1]: Entering directory `/usr/src/kernels/2.6.38.7-30.fc15.x86_64'
CC [M] /tmp/vmware-root-62598440/modules/vmmon-only/linux/driver.o
/tmp/vmware-root-62598440/modules/vmmon-only/linux/driver.c: In function ‘init_module’:
/tmp/vmware-root-62598440/modules/vmmon-only/linux/driver.c:425:15: error: ‘struct file_operations’ has no member named ‘ioctl’
/tmp/vmware-root-62598440/modules/vmmon-only/linux/driver.c: In function ‘LinuxDriver_Ioctl’:
/tmp/vmware-root-62598440/modules/vmmon-only/linux/driver.c:1736:7: error: implicit declaration of function ‘kernel_locked’ [-Werror=implicit-function-declaration]
cc1: some warnings being treated as errors
make[2]: *** [/tmp/vmware-root-62598440/modules/vmmon-only/linux/driver.o] Error 1
make[1]: *** [_module_/tmp/vmware-root-62598440/modules/vmmon-only] Error 2
make[1]: Leaving directory `/usr/src/kernels/2.6.38.7-30.fc15.x86_64'
make: *** [vmmon.ko] Error 2
make: Leaving directory `/tmp/vmware-root-62598440/modules/vmmon-only'
Unable to install vmmon -
Vmware Player in Arch Linux and RFKILL
Hi,
I am a newbie to Arch Linux, I have installed Vmware player in Arch but it doesn't seem to be running. I have followed the guide in the Arch Wiki. This is the output of the related commands.
[root@swallowed Desktop]# uname -r
2.6.35-ARCH
[root@swallowed Desktop]# vmware-installer -l
No protocol specified
No protocol specified
Product Name Product Version
====================== ====================
vmware-player 3.1.2.301548
[root@swallowed Desktop]# /etc/rc.d/vmware
vmware vmware.d/
[root@swallowed Desktop]# /etc/rc.d/vmware start
Starting VMware services:
VMware USB Arbitrator done
Virtual machine monitor failed
Virtual machine communication interface failed
VM communication interface socket family failed
Blocking file system failed
Virtual ethernet failed
[root@swallowed Desktop]# vmplayer
No protocol specified
xprop: unable to open display ':0.0'
GLib-GIO:ERROR:gdbusconnection.c:2270:initable_init: assertion failed: (connection->initialization_error == NULL)
No protocol specified
xprop: unable to open display ':0.0'
GLib-GIO:ERROR:gdbusconnection.c:2270:initable_init: assertion failed: (connection->initialization_error == NULL)
No protocol specified
(vmware-modconfig:5602): Gtk-WARNING **: cannot open display: :0.0
[root@swallowed Desktop]#
Does anyone know how to resolve this problem?
Besides, I installed Arch on Dell Studio XPS 1640 and I don't seem tobe able to remove the hard block on my Wifi card. I installed all the driver already. This is the output of commands.
[root@swallowed Desktop]# rfkill list
0: dell-wifi: Wireless LAN
Soft blocked: yes
Hard blocked: yes
1: phy0: Wireless LAN
Soft blocked: no
Hard blocked: yes
[root@swallowed Desktop]# rfkill unblock 0
[root@swallowed Desktop]# rfkill list
0: dell-wifi: Wireless LAN
Soft blocked: yes
Hard blocked: yes
1: phy0: Wireless LAN
Soft blocked: no
Hard blocked: yes
[root@swallowed Desktop]#
I even try to include this inside modprobe but it doesn't work.
[root@swallowed Desktop]# cat /etc/modprobe.d/modprobe.conf
# /etc/modprobe.d/modprobe.conf (for v2.6 kernels)
options ath_pci rfkill=0
options snd-pcsp index=2
options iwlcore led_mode=1
Thank you so much!vmware products need patching for kernel 2.6.35 - you didn't mention if you did that or not, but if you didn't, that would explain why vmware is not starting.
-
VMware Player and mouse not behaving correctly with the vmmouse driver
I'm running Arch on VMware Player and having problems with the mouse behavior.
- Arch is updated, 32 -bit
- VMware Player 6.0.1
- Host is Windows 8.1 64-bit
- XFCE 4.10
If I install xf86-input-vmmouse, the following happens:
- If cursor touches the edge of the screen when scrolling a window with the scroll bar, scrolling stops. If I continue pressing the mouse button and moving the mouse (and not touching any edges), the scrolling starts working again after two seconds.
- When opening any new window, hovering and clicking will register only after two seconds. This is very noticeable when opening the application menu and trying to launch any app - first click never works.
Uninstalling the vmmouse driver fixes the above problems. The mouse "feeling" gets very bad though, it seems jumpy and the acceleration is crazy and can't be tweaked to be satisfactory with the mouse settings. With vmmouse the mouse feels otherwise just fine.
Installing or uninstalling Open-VM-Tools doesn't do anything.
I tried this, but it had no effect: https://wiki.archlinux.org/index.php/In … s_expected
Happens both in fullscreen and windowed, scrolling behavior happens every time, hover/click lag is not so predictable (seems to happen 50 % of the time).
Might there be any easy fix for this?Hi Sung, Thanks for your reply.
Leonardo:
If I understand your msg correctly, I'm wondering if
the data model as you described is complete.
You state that you have MaintenanceType, Maintenance,
and MaintenanceOrder, but don't you need
MaintenanceOrderLine?MaintenanceOrderLine is what I'm calling Maintenance. A Maintenace record is used just to link a MaintenanceOrder to a MaintenanceType
>
Otherwise, you say that you removed all Maintenance's
in step 2). How did you form a list of all
Maintenance's in step 4)? How do you form this
list?
was raised due to unique constraint violationAt step 3) I'm using a view object, MaintenanceTypeView, to create a list of checkboxes, one for each MaintenanceType.
At step 4), for each MaintenanceType selected in the form, I'm creating a new Maintenance using:
//All codes of maintenance types, that already have a
//respective maintenance record in the db, have already
//been remove from the maintenancesToInsert list at this
//point
for (Iterator iter = maintenancesToInsert.iterator(); iter.hasNext();) {
MaintenanceViewRow maintenanceRow = (MaintenanceViewRow) maintenanceView.createRow();
maintenanceRow.setMaintenanceTypeCode(Integer.valueOf((String)iter.next()));
maintenanceView.insertRow(maintenanceRow);
>
Sung -
Can vmware player be used to create windows pc and mac. Will I need any other software or hardware to do that?(Have Windows and Mac on same computer)
Since you posted this in the iPod Touch forum and didn't provide enough information to contradict that I am going to say the it can't be done. VMWare does work in iPods.
Allan
Maybe you are looking for
-
hey..just wanted to know ..if u all can help with a problem...when i install themes or apps that have pics(which i do..alot)..the pics go in the gallery and make it real annoyin to havin to go through those pics before u get to urs....is the any way
-
J2EE Tutorial Bookstore application
Hello, New to J2EE. I have followed all instructions to deply the bookstore application, or at least I think that I have. When I try to launch from the admin tool, I get the following page: HTTP Status 503 - This application is not currently availabl
-
Error when uploading; the file name is invalid, or the file is too big
Hi, I have posted this topic also in this thread, but we are not getting any answer to this problem. Also, the existing discussion in this thread gives us no idea what to do. We get the a.m. message when using the "FILE-UPLOAD" UI element only for se
-
Hola: Llevo casi un año buscando una placa madre para mi lenovo z400 pero en todos los servicios tecnicos autorizados por la marca me dicen que no la tienen y no llega a chile. Por favor si alguien sabe como conseguirla seria de gran ayuda.
-
HT1349 how do i transfer my i tunes account from my pc to my new laptop
how do i transfer my i tunes account from my pc to my new laptop