Kernel PAE on openSuSE 11.1

Similar Questions

• No bluetooth on Satellite C870 using OpenSuse Linux

  First of all, thanks for reading and eventually respond to this message

  I installed opensuse 12.3 x86_64 on a Toshiba Satellite C870 - 1 HR with a wifi/bluetooth adapter realtek 8723. The rtl8723ae module is running.
  Wifi works with kernel 3.10 provided by opensuse kernel team, but not the BT. bt kernel modules are loaded, kde recognizes the bt stack, but not access.

  hcitool dev
  Feature:

  and

  rfkill list
  0: hci0: Bluetooth
  Soft blocked: no
  Hard blocked: no

  However, I have discovered with dmesg:

  8.347377: HCI device and connection manager Bluetooth Initialise
  8.347389 Bluetooth: socket initialized HCI layer
  8.347391 Bluetooth: L2CAP initialized SSL
  [Bluetooth 8.347399: initialized SCO socket layer]
  8.350732 ACPI WARNING: 0 x 0000000000004040-0x000000000000405f SystemIO comes into conflict with the \_SB_ region. PCI0. SBUS. SMBI 1 (20130328/utaddress-251)
  8.350739] ACPI: If an ACPI driver is available for this device, you must use it instead of the native driver
  8.356121] usbcore: registered new interface driver btusb

  rtl8723ae 8.759901: using the rtlwifi/rtl8723fw_B.bin firmware
  8.875659 ACPI WARNING: 0 x 0000000000000428-0x000000000000042f SystemIO comes into conflict with the \PMIO region 1 (20130328/utaddress-251)
  8.875666 ACPI: If an ACPI driver is available for this device, you must use it instead of the native driver
  8.875670 ACPI WARNING: 0 x 0000000000000530-0x000000000000053f SystemIO comes into conflict with the \GPIO region 1 (20130328/utaddress-251)
  8.875674 ACPI WARNING: 0 x 0000000000000530-0x000000000000053f SystemIO comes into conflict with the \GPXX region 2 (20130328/utaddress-251)
  8.875677 ACPI: If an ACPI driver is available for this device, you must use it instead of the native driver
  8.875679 ACPI WARNING: 0 x 0000000000000500-0x000000000000052f SystemIO comes into conflict with the \GPIO region 1 (20130328/utaddress-251)
  8.875681 ACPI WARNING: 0 x 0000000000000500-0x000000000000052f SystemIO comes into conflict with the \GPXX region 2 (20130328/utaddress-251)
  8.875684 ACPI: If an ACPI driver is available for this device, you must use it instead of the native driver
  lpc_ich 8.875686: resource found on gpio_ich
  8.888936 ieee80211 phy0: rate control algorithm selected "rtl_rc".
  rtlwifi 8.889107: wireless switch is on

  Any idea?

  Hello

  Your problem is a little weird!

  Your wireless network card is a BT / WLAN combo and should be supported by the kernel used in openSuse 12.3.
  Check the functionality in Windows or any other end Linux distribution?

  I would say to download Fedora 19 and run as a direct medium OS to check the operation of BT.
  If it works fine, I belive there is a bug in the distro openSuse.
  If this isn't the case, I really think you should consider checking your hardware.

  I have the same card in my works C850 and BT just perfect in Fedora 19.

  Hope this helps you out

  Tom BR

• Installation of VMWare in Fedora 17 (guest operating system) tools

  Hi all

  I'm trying to install VMWare tools in Fedora 17 and receive an error message

  The path "" is not a valid path to the core of 3.3.4 - 5.fc17.x86_64 headers.

  I have installed gcc, binutils, and brand.

  Kernel-heads are at the same level. However, I still get the above error.

  Any help would be appreciated.

  Thank you

  Here are the details

  ---------------

  Looking for a CCG...
  Detected binary of the GCC to "/ bin/gcc".
  The path ' / bin/gcc "seems to be a valid path to the GCC binary.
  You want to change it? [None]

  Looking for a valid kernel header path...
  The path "" is not a valid path to the core of 3.3.4 - 5.fc17.x86_64 headers.
  You want to change it? [Yes] ^ C
  The execution is canceled.

  [bpmdev@fedora17v1 3.3.4 - 5.fc17.x86_64] $ uname - r
  3.3.4 - 5.fc17.x86_64 Linux

  [bpmdev@fedora17v1 3.3.4 - 5.fc17.x86_64] $ list of installed yum | grep 'core'
  kernel.x86_64 3.3.4 - 5.fc17 @koji-override-0 / $ releasever
  kernel - headers.x86_64 3.3.4 - 5.fc17 @fedora

  
  [bpmdev@fedora17v1 3.3.4 - 5.fc17.x86_64] $ sudo yum install kernel-PAE kernel-PAE-devel
  Loaded extensions: last, presto, refresh-packagekit
  No kernel-PAE package available.
  No available kernel-PAE-devel package.
  Error: Nothing to do
  [bpmdev@fedora17v1 3.3.4 - 5.fc17.x86_64] $

  First... you seem to tell the difference between x86_64 and i686 iso image of Fedora. I couldn't find an i686 image. Of course, I must be on 64 bit system. If I'm wrong, then please direct me in the right direction.

  If you want to use the x86_64 image that's good, assuming that your system supports.  I just used the i686 for example image in the scenario either will not lead the same way.  Then the essence is in the error message that it reported a string zero to locate the core of 3.3.4 - 5.fc17.x86_64 by default and this means that the necessary header files for the kernel were not on the system.  I introduced him as I did so we would understand that if they made a default installation and no upgrade and is not used "-"uname - r"" is then added to "kernel-devel" with yum install the last header of kernel files not by default and would always be a null string error message.

  Secondly, I've upgraded to the latest version of the kernel, and I download these errors right now. Should I go down.

  The latest kernel, I do not think that it is officially supported by VMware again and tools VMware would need to be patched with the third-party patch before installing with the kernels more later then the default kernel.  So you need to apply one of the hotfixes that are here on the web or use a core of support for VMware, it's your choice.

  BTW, it is quite common with the Linux distro once one updated the default kernel will generally use one of the third party patches for VMware Tools install properly and you should be able to find it in the forums and via Google.  In General, VMware is and has always been extremely slow in support of new kernels, where the need to use third-party patches for VMware Tools to properly install on any Linux distro and kernel which is not yet officially supported!

• Have a problem when installing packages Asmlib

  Hi all
  
  I have a problem when installing packages ASMlib.
  
  My OS = Redhat linux 5.3
  kenel version using this command uname - r = 2.6.18 - 128.el5
  
  I downloaded the package and installed successfully after 4
  
  oracleasm-support - 2.1.7 - 1.el5.i386.rpm
  oracleasmlib - 2.0.4 - 1.el5.i386.rpm
  oracleasm - 2.6.18 - 128.el5 - 2.0.5 - 1.el5.i686.rpm
  oracleasm-2.6.18-128.EL5-DebugInfo-2.0.5-1.EL5.i686.rpm
  
  But while the installation following received the error
  
  RPM - ivh oracleasm - 2.6.18 - 128.el5debug - 2.0.5 - 1.el5.i686.rpm
  
  kernel debugging = 2.6.18 - 128.el5 is necessary for oracleasm - 2.6.18 - 128.el5debug - 2.0.5 - 1.el5.i686
  
  RPM - ivh oracleasm - 2.6.18 - 128.el5PAE - 2.0.5 - 1.el5.i686.rpm
  
  kernel-PAE = 2.6.18 - 128.el5 is necessary for oracleasm - 2.6.18 - 128.el5PAE - 2.0.5 - 1.el5.i686
  
  RPM - ivh oracleasm - 2.6.18 - 128.el5xen - 2.0.5 - 1.el5.i686.rpm
  
  kernel-xen = 2.6.18 - 128.el5 is necessary for oracleasm - 2.6.18 - 128.el5xen - 2.0.5 - 1.el5.i686
  
  Thanks in advance

  xuv500 wrote:
  kernel debugging = 2.6.18 - 128.el5 is necessary for oracleasm - 2.6.18 - 128.el5debug - 2.0.5 - 1.el5.i686
  kernel-PAE = 2.6.18 - 128.el5 is necessary for oracleasm - 2.6.18 - 128.el5PAE - 2.0.5 - 1.el5.i686
  kernel-xen = 2.6.18 - 128.el5 is necessary for oracleasm - 2.6.18 - 128.el5xen - 2.0.5 - 1.el5.i686

  Then install the packages. You can find them on installtion DVD

• ERROR with 2.6.29.4 - 167.fc11.i686.PAE kernel FEDORA 11 & VMware-server - 2.0.1 - 156745.i386.rpm

  I was unable to boot VMware-server - 2.0.1 - 156745.i386.rpm with my new fedora 11 due to the following error... any idea?

  -error-

  /usr/bin/vmware-config.pl

  Ensuring services for VMware Server are stopped.

  Stopping VMware services:

  VMware authentication daemon

  Virtual machine monitor

  None of the vmmon modules pre-built for VMware Server is suitable for your

  kernel running.  Do you want this program to try to build the vmmon module for

  your system (you must have a C compiler installed on your system)?

  Using compiler "/ usr/bin/gcc". Environment variable CC to override.

  What is the location of the directory of C header files that match your running

  kernel?

  /lib/modules/2.6.29.4-167.FC11.i686.PAE/build/include

  Extract the sources of the vmmon module.

  The construction of the vmmon module.

  Using 2.6.x kernel build system.

  do: enter the directory ' / tmp/vmware-config3/vmmon-only '.

  do /lib/modules/2.6.29.4-167.fc11.i686.PAE/build/include/ - C... SUBDIRS = $PWD SRCROOT = $PWD. modules of

  make [1]: Entering directory ' / usr/src/kernels/2.6.29.4-167.fc11.i686.PAE'

  CC /tmp/vmware-config3/vmmon-only/linux/driver.o

  In file included from /tmp/vmware-config3/vmmon-only/linux/driver.c:31:

  /tmp/vmware-config3/vmmon-only/./include/compat_wait.h:78: error: conflicting types for 'poll_initwait '.

  include/Linux/poll.h:67: Note: previous declaration of 'poll_initwait' is here

  In file included from tmp/vmware-config3/vmmon-only/./include/vmware.h:38,

  from /tmp/vmware-config3/vmmon-only/linux/driver.c:99:

  /tmp/vmware-config3/vmmon-only/./include/vm_basic_types.h:108:7: warning: "__FreeBSD__" is not defined

  In file included from tmp/vmware-config3/vmmon-only/./include/vcpuset.h:103,

  of tmp/vmware-config3/vmmon-only/./include/modulecall.h:37.

  of tmp/vmware-config3/vmmon-only/./common/vmx86.h:33.

  of tmp/vmware-config3/vmmon-only/linux/driver.h:29.

  from /tmp/vmware-config3/vmmon-only/linux/driver.c:101:

  /tmp/vmware-config3/vmmon-only/./include/vm_atomic.h:329:7: warning: "_MSC_VER" is not defined

  /tmp/vmware-config3/vmmon-only/./include/vm_atomic.h:333:7: warning: "_MSC_VER" is not defined

  /tmp/vmware-config3/vmmon-only/./include/vm_atomic.h:401:7: warning: "_MSC_VER" is not defined

  /tmp/vmware-config3/vmmon-only/./include/vm_atomic.h:407:7: warning: "_MSC_VER" is not defined

  /tmp/vmware-config3/vmmon-only/./include/vm_atomic.h:506:7: warning: "_MSC_VER" is not defined

  /tmp/vmware-config3/vmmon-only/./include/vm_atomic.h:595:7: warning: "_MSC_VER" is not defined

  /tmp/vmware-config3/vmmon-only/./include/vm_atomic.h:684:7: warning: "_MSC_VER" is not defined

  /tmp/vmware-config3/vmmon-only/./include/vm_atomic.h:773:7: warning: "_MSC_VER" is not defined

  /tmp/vmware-config3/vmmon-only/./include/vm_atomic.h:775:7: warning: "_MSC_VER" is not defined

  /tmp/vmware-config3/vmmon-only/./include/vm_atomic.h:860:7: warning: "_MSC_VER" is not defined

  /tmp/vmware-config3/vmmon-only/./include/vm_atomic.h:862:7: warning: "_MSC_VER" is not defined

  /tmp/vmware-config3/vmmon-only/./include/vm_atomic.h:945:7: warning: "_MSC_VER" is not defined

  /tmp/vmware-config3/vmmon-only/./include/vm_atomic.h:947:7: warning: "_MSC_VER" is not defined

  /tmp/vmware-config3/vmmon-only/./include/vm_atomic.h:1028:7: warning: "_MSC_VER" is not defined

  /tmp/vmware-config3/vmmon-only/./include/vm_atomic.h:1030:7: warning: "_MSC_VER" is not defined

  /tmp/vmware-config3/vmmon-only/./include/vm_atomic.h:1223:7: warning: "_MSC_VER" is not defined

  /tmp/vmware-config3/vmmon-only/./include/vm_atomic.h:1227:7: warning: "_MSC_VER" is not defined

  /tmp/vmware-config3/vmmon-only/./include/vm_atomic.h:1536:7: warning: "_MSC_VER" is not defined

  /tmp/vmware-config3/vmmon-only/./include/vm_atomic.h:1663:7: warning: "_MSC_VER" is not defined

  In file included from tmp/vmware-config3/vmmon-only/./include/vm_basic_asm.h:46,

  of tmp/vmware-config3/vmmon-only/./include/rateconv.h:45.

  of tmp/vmware-config3/vmmon-only/./include/modulecall.h:40.

  of tmp/vmware-config3/vmmon-only/./common/vmx86.h:33.

  of tmp/vmware-config3/vmmon-only/linux/driver.h:29.

  from /tmp/vmware-config3/vmmon-only/linux/driver.c:101:

  /tmp/vmware-config3/vmmon-only/./include/vm_basic_asm_x86.h:62:7: warning: "_MSC_VER" is not defined

  /tmp/vmware-config3/vmmon-only/./include/vm_basic_asm_x86.h:177:7: warning: "_MSC_VER" is not defined

  /tmp/vmware-config3/vmmon-only/./include/vm_basic_asm_x86.h:346:7: warning: "_MSC_VER" is not defined

  /tmp/vmware-config3/vmmon-only/./include/vm_basic_asm_x86.h:453:7: warning: "_MSC_VER" is not defined

  In file included from tmp/vmware-config3/vmmon-only/./include/vm_asm.h:43,

  from /tmp/vmware-config3/vmmon-only/linux/driver.c:103:

  /tmp/vmware-config3/vmmon-only/./include/vm_asm_x86.h:486:7: warning: "_MSC_VER" is not defined

  /tmp/vmware-config3/vmmon-only/./include/vm_asm_x86.h:779:7: warning: "_MSC_VER" is not defined

  /tmp/vmware-config3/vmmon-only/./include/vm_asm_x86.h:820:7: warning: "_MSC_VER" is not defined

  /tmp/vmware-config3/vmmon-only/./include/vm_asm_x86.h:922:7: warning: "_MSC_VER" is not defined

  In file included from /tmp/vmware-config3/vmmon-only/linux/driver.c:119:

  /tmp/vmware-config3/vmmon-only/./common/hostif.h:53:7: warning: 'WINNT_DDK' is undefined

  /tmp/vmware-config3/vmmon-only/Linux/driver.c: in function 'LinuxDriverSyncCallOnEachCPU ':

  /tmp/vmware-config3/vmmon-only/Linux/driver.c:1423: error: too many arguments to function 'smp_call_function '.

  /tmp/vmware-config3/vmmon-only/Linux/driver.c: in function 'LinuxDriver_Ioctl ':

  /tmp/vmware-config3/vmmon-only/Linux/driver.c:1987: error: 'struct task_struct' has no member named 'euid.

  /tmp/vmware-config3/vmmon-only/Linux/driver.c:1987: error: 'struct task_struct' has no member named 'uid '.

  /tmp/vmware-config3/vmmon-only/Linux/driver.c:1988: error: 'struct task_struct' has no member named 'fsuid '.

  /tmp/vmware-config3/vmmon-only/Linux/driver.c:1988: error: 'struct task_struct' has no member named 'uid '.

  /tmp/vmware-config3/vmmon-only/Linux/driver.c:1989: error: 'struct task_struct' has no member named 'egid.

  /tmp/vmware-config3/vmmon-only/Linux/driver.c:1989: error: 'struct task_struct' has no member named 'gid '.

  /tmp/vmware-config3/vmmon-only/Linux/driver.c:1990: error: 'struct task_struct' has no member named 'fsgid '.

  /tmp/vmware-config3/vmmon-only/Linux/driver.c:1990: error: 'struct task_struct' has no member named 'gid '.

  /tmp/vmware-config3/vmmon-only/Linux/driver.c:2007: error: too many arguments to function 'smp_call_function '.

  make [2]: * /tmp/vmware-config3/vmmon-only/linux/driver.o error 1

  make [1]: * error 2

  make [1]: leaving directory ' / usr/src/kernels/2.6.29.4-167.fc11.i686.PAE'

  make: * http://vmmon.ko error 2

  make: leaving directory ' / tmp/vmware-config3/vmmon-only '.

  Unable to build the vmmon module.

  For more information about how to troubleshoot module, please

  visit our Web site at " " http://www.VMware.com/go/UNSUP-Linux-products "and "

  " http://www.VMware.com/go/UNSUP-Linux-tools ". "

  The execution is canceled.

  Look here for the patch to module 2629 vmware servers: http://communities.vmware.com/message/1261181

  It worked for me with F11, although I'm not 64-bit.

  Jeff

• VMware on OpenSuSE 11 installation fails

  Hello

  I am a long time VMware user and grew up in short by the absence of vmware - config.pl in the latest version. Anyhow, as the product to be compiled at the start is a good thing (or so I thought) in any case, the loading of vmware, I get the following error log.

  09:43:26.134 15 Dec: app | Journal for VMware Workstation pid = version 13716 = 6.5.1 build = build-126130 option = output

  09:43:26.135 15 Dec: app | Host codepage = UTF-8 encoding = UTF-8

  09:43:26.135 15 Dec: app | Login to /tmp/vmware-root/setup-13716.log

  09:43:32.297 15 Dec: app | Do not make required utilities, tar, echo, grep, rmmod, insmod

  Operating system is OpenSuSE 11 (32-bit)

  Linux imager5 2.6.25.18 - 0.2 - pae #1 SMP 2008 - 10 - 21 16:30:26 + 0200 i686 athlon i386 GNU/Linux

  I tried to run as root and su-

  Someone at - it suggestions?

  Chris

  You will need to install a few packages of development.  This probably will fix you all:

  YaST-i do tar grep gcc module-init-tools

  You will also need the kernel headers or source for your running kernel

  YaST-i kernel-source

  Then run as root once and exit vmware and go back to the race as your normal user and if things work out.

• Firefox 15.0 hangs out (12.1 opensuse)

  Recently (maybe since v14) firefox starts to crash whenever I close. I debugged and found that it can be resolved if I do not install some extension or if I reset the preference by deleting the directory preference. But when updated to 15.0, firefox takes up the problem again and again, even as it works in mode safe without any extension or I'll take the .mozilla / directory in my home directory completely. In addition, I tried to uninstall and reinstall firefox, but the problem remains. A share the same problem or has a suggestion? Thank you very much.

  My OS Info
  12.1 openSUSE
  3.1.10 linux kernel - 1.16
  GNOME 3.2.1

  Sorry, but this answer does not really solve the problem.
  There are about 300 reports of incidents in a week
  https://crash-stats.Mozilla.com/report/list?signature=libmozjs185.so.1.0.0%400xa694b

  and here is also a bug report:
  https://Bugzilla.Novell.com/show_bug.cgi?id=759123

  My solution:
  Uninstall libproxy1-pacrunner-mozjs (zypper rm libproxy1-pacrunner-mozjs)
  but I'm not sure what side effects there.

• on the problem of openSUSE 12.1 ni4882 3.1.10 - 1.19 - Office

  After you install the package kernel-source and kernel-syms and following the steps described in the file README.txt for the preparation of openSUSE for NI4882 installation, the installation hangs at post installation steps. gpibtsw indicates the auto-run is not properly installed and gpibexplorer suggest updateNIDrivers running. updateNIDrivers output stops and freezes at "funtion pte_offset:

  The output of niSystemReport follows:

  / usr/local/bin/niSystemReport version 2.3.1f0

  ********************************************************************************
  / bin/uname-r:
  Linux vtvax_linux 3.1.10 - 1.19 - desktop #1 SMP PREEMPT Thu Feb 25 10:32:50 UTC 2013 (f0b13a3) x86_64 x86_64 x86_64 GNU/Linux
  ********************************************************************************

  ********************************************************************************
  / etc/SUSE-Release:
  12.1 openSUSE (x86_64)
  VERSION = 12.1
  CODE name = asparagus
  ********************************************************************************

  ********************************************************************************
  / etc/OS-Release:
  NAME = openSUSE
  VERSION = 12.1 (asparagus)
  VERSION_ID = '12.1.
  PRETTY_NAME = "openSUSE 12.1 (sprinkles) (x86_64).
  ID = opensuse
  ********************************************************************************

  Configuration for linux kernel version 3.1.10 - 1.19 - desktop.

  ********************************* NOTE *********************************
  With the help of the kernel headers found in lib/modules/3.1.10-1.19-desktop/build.
  If this does not match the location of the headers 3.1.10 - 1.19 - desktop,.
  Then set KERNELHEADERS in your environment to point to the location
  headers for the kernel to set KERNELTARGET as the version of the
  kernel for which compile and run him again. / configure.
  ********************************* NOTE *********************************

  A-team reparent_to_init(): no
  Number of arguments for do_munmap(): 3
  function pte_offset: ^ C

  Help someone?

  Thank you

  Charles

  Charles

  Here is the solution:

  Bang head on the desk.

  . / UNINSTALL

  declare - x KERNELHEADERS/usr/src/linux-$(uname-r)

  declare - x KERNELTARGER $(uname-r)

  . / INSTALL

  All right.

  Thank you Charles for the great solution.

• DAQmx installation fails on openSuSE 11.1

  Hello

  I've been test driving openSuSE 11.1 today, and I discovered that DAQmx will not install correctly. It looks like the /lib/modules/2.6.xx/source for headers instead of lib/modules/2.6.xx/build. openSuSE install the headers for the construction and the packets from the kernel to the source source.

  John

  I've never understood how the modules version, so I just rebuilt the kernel with management module disabled versions. Now, it works fine.

  # CONFIG_MODVERSIONS is not defined
  # CONFIG_MODULE_SRCVERSION_ALL is not set

• All-in-one j6480 using linux, problems during the update of the kernel

  I have a platform of linux opensuse 11.0 (printer was working fine before the update) and updated the linux kernel and lost the connection to a printer, is the hpj6480 all-in-one printer, then updated to hplip 3.9.2

  using auto-install in the terminal, installed latest driver hplip 3.9.2, by checking installed software packages poster old version 2.8.4 printer hplip currently works as a USB direct connect but not wireless

  other than the obvious question how do I solve this problem... What is the plan for the installation of the printer basic logic (IE... direct connect USB - wireless - cable) or install also completely wireless?  ... I should completely uninstall the printer and system drivers and re - install as a new system... And are there associated lib files that it removed the old driver of 2.8 and 2.10?

  It turns out that the hplip should be reinstalled... but which has also compounded the problem was that the firewall should be removed to complete installation... Thank you for your help

• Failure of vmnet after last update of openSUSE

  Hi all

  I just made an update of opensuse Factory tonight zypper mega - v13.2 goes live Monday so I thought that I would avoid the rush.

  It was a big mistake that VMware Workstation is concerned because after update packages ~ 530 (new kernal etc) VMware Workstation can compile is no longer the vmnet module.

  ERROR: Failure of vmnet.  Cannot run the command build.

  I've been running Vmware Workstation very well with zero problems on the factory for the past 3 weeks

  Side note: I've just updated to VMware yesterday.

  I am running: VMware-Workstation-Full - 10.0.4 - 2249910.x86_64.bundle

  Everything worked fine for 24 hours before updating major openSUSE tonight (20141031)

  # OS details follow

  Linux Asus 3.17.1 - 1.g5c4d099 - desktop #1 SMP PREEMPT Sat Oct 18 23:36:23 UTC 2014 (5c4d099) x86_64 x86_64 x86_64 GNU/Linux

  # List the versions of installed packages support...

  kernel-source - 3.17.1 - 1.2.g5c4d099.noarch

  kernel-desktop - 3.17.1 - 1.2.g5c4d099.x86_64

  kernel-desktop-devel - 3.17.1 - 1.2.g5c4d099.x86_64

  GCC - 4, 8 - 8.1.x86_64

  Make - 4.0 - 4.4.x86_64

  GCC-c++-4, 8 - 8.1.x86_64

  Cat vmware-modconfig - 19171.log

  ... snip

  2014 10-31 T 20: 25:32.487 + 01:00 | modconfig | I120: "/ usr/lib/vmware-installer/2.1.0/vmware-installer" came out with a status of 0.

  2014 10-31 T 20: 25:32.487 + 01:00 | modconfig | I120: The setting for vmnet destination path to ' / lib/modules/3.17.1-1.g5c4d099-desktop/misc/vmnet.ko '.

  2014 10-31 T 20: 25:32.487 + 01:00 | modconfig | I120: Extraction of the source vmnet "/ usr/lib/vmware/modules/source/vmnet.tar".

  2014 10-31 T 20: 25:32.490 + 01:00 | modconfig | I120: Extract successfully the vmnet source.

  2014 10-31 T 20: 25:32.490 + 01:00 | modconfig | I120: Module construction with the command ' / usr/bin/make - j6/tmp/modconfig-Kua8Vn/vmnet-only - C-automatic generation HEADER_DIR=/lib/modules/3.17.1-1.g5c4d099-desktop/build/include CC = / usr/bin/gcc IS_GCC_3 = no ".

  2014 10-31 T 20: 25:33.649 + 01:00 | modconfig | W110: Vmnet failed.  Cannot run the command build.

  2014 10-31 T 20: 25:33.654 + 01:00 | modconfig | I120: We now stop.  Ready to die!

  See the attachment for details

  Question: Is there available patches or a beta version of the next version of VMware Workstation?

  Concerning

  James

  Hi all

  Just a little note to say that I solved this problem by applying the attached patch (vmware-for - 3.17.patch.zip) that I found on this forum. Sorry, but I forgot on what post I found it.

  Note: Make sure that you have installed on your system to fix GNU!

  # The instructions to respect

  Working directory new # make

  RM - r/tmp/vmware

  mkdir/tmp/vmware/source Pei & cd/tmp/vmware/source

  #

  # Copy files from source to the VMware

  CP r/usr/lib/vmware/modules/source / *.

  I'm in. / * .tar. tar - xf $i; fact

  I'm in. / * .tar. make $ mv i.orginal $i; fact

  #

  # copy patch_to_603_r40_lc.zip* file to 3.17 kernel in/tmp/vmware/source /.

  CP Pei your.path.goes.here/vmware-for-3.17.patch.zip.

  # Decompressez./vmware-for-3.17.patch.zip

  decompresser./VMware-for-3.17.patch.zip

  #

  # apply the patch

  patch - p1<>

  tar vmnet.tar - cf vmnet-only.

  MV - vfi./vmnet.tar/usr/lib/vmware/modules/source /.

  # recompile vmware modules using new patched

  VMware-modconfig - console - install-all

  #

  # VMware Workstation 10.0.4 build-2249910 now works great on openSUSE 13.2/factory using a 3.17.1 kernel

  Linux version 3.17.1 - 1.g5c4d099 - desktop (geeko@buildhost) (gcc 4.8.3 version 20140627 [CCG-4_8-branch revision 212064] (SUSE Linux)) #1 SMP PREEMPT Sat Oct 18 23:36:23 UTC 2014 (5c4d099)

  Hope this helps someone

  Concerning

  James

• Problems to install VMWare Tools - OpenSUSE 12.3

  Hello

  With the help of VMWare Workstation 8.0.6 build 1035888.

  S | Name                           | Type | Version | Ark | Repository
  --+--------------------------------+---------+--------------+--------+-----------
  I have | by default-kernel-devel | the package | 3.7.10 - 1.1.1 | x86_64 | OSS
  I have | core office | the package | 3.7.10 - 1.1.1 | x86_64 | OSS
  I have | kernel-desktop-devel | the package | 3.7.10 - 1.1.1 | x86_64 | OSS
  I have | kernel-devel | the package | 3.7.10 - 1.1.1 | noarch | OSS
  I have | kernel-source | the package | 3.7.10 - 1.1.1 | noarch | OSS
  I have | kernel-syms | the package | 3.7.10 - 1.1.1 | x86_64 | OSS
  I have | Xen-kernel-devel | the package | 3.7.10 - 1.1.1 | x86_64 | OSS
  I have | models-openSUSE-devel_kernel | the package | 12.3 - 7.10.1 | x86_64 | OSS
  
  
  # ls/usr/src
  Linux
  Linux - 3.7.10 - 1.1
  Linux - 3.7.10 - 1.1 - obj
  Linux-obj
  Packages

  #./vmware-install.pl

  ...

  
  

  Looking for a valid kernel header path...

  The path "" is not a valid path to the headers of the core of 3.7.10 - 1.1 - desktop.

  You want to change it? [Yes]

  
  

  Enter the path to the files of headers of the kernel for the core of 3.7.10 - 1.1 - desktop?

  I tried "/ usr/src/linux-3.7.10-1.1" but that has not worked.
  What should you specify the path to the kernel headers?
  Thank you
  Paul

  Ok

  It was always a pain in the neck... forever.

  Why vmware can't put a clear message on what the vmware - install.pl seek (or log)?

  My settings are:

  • $(uname-r)' => 3.7.10 - 1.1 - desktop
  • $(uname-m)'-online x86_64

  In any case, I assume you have the following packages (Please adjust for your config):

  • kernel-desktop - 3.7.10 - 1.1.1.x86_64
  • kernel-desktop-devel - 3.7.10 - 1.1.1.x86_64

  You need not what anyone else.

  And don't forget, you have not installed: libvmtools0, open-vm-tools, open-vm-tools-gui.

  So proceed like this:

  $> mkdir-p/lib/modules/3.7.10-1.1-desktop/build/include/linux

  $> cp/usr/src/linux -3.7.10 - 1.1-obj /x86_64/Office/include/generated/uapi/linux/version.h.

  / lib/modules/$(uname-r)/Build/include/linux

  $>./vmware-install.pl

  Restart and you should now be fine.

• Helps the installer kernel panic

  WS Preview installation on openSUSE 12.2 milestone with kernel 3.3.0 worked great (that I posted).  When you try to install VMware in Ubuntu 12.04 with kernel 3.3.0 I lived what "seemed" to be a required (video completely unreadable and frozen - mhard rfebootg) kernel panic.  I have attached the vmware Installer log and may not know where the accident occurred.  The compliation seems like he has not finished, but aren't errors (with the exception of the permissions that does not stop the compilation).

  Is there a way to install WS directly depui the CLI?  I remember messages that discussed this but I can't find it on google (for this product - no esxi or vvshere.

  All libraries and files seem to be/etc/in/usr/lib seem to be present.  What I'm missing here? It's very close.  Where could I seek failure?

  Fix vmware-Installer/going/log log

  Moved thread from VMware Fusion Technology Preview 2012 to VMware Workstation Technology Preview 2012.

• Is there a workaround for OpenSUSE 11.4

  Hello, I tried to install VMWare Player version 3.1.4 in OpenSUSE 11.4. After installation, when I'm launching the vmplayer, I had a guest complain that cannot find the version of the kernel header 2.6.37.1. I installed the kernel sources are 2.6.37.6, I would like to know is really important where I had a newer version of the installed source.

  Is there a workaround to use the new version of the header source?

  Thank you @!

  http://forums.openSUSE.org/English/get-technical-help-here/install-boot-login/455377-where-Linux-kernel-headers-11-4-a-2.html

  who could help

• 6.5.5 workstation does not compile with the 2.6.37 kernel (os11.4)

  Hi all

  I have to stay with VMware Workstation 6.5.5 because of my lack of EAP robot. 6.5.5 workstation has worked well with a patch on openSUSE 11.3. Now I want to migrate to oS 11.4. But I could not find a patch to date. If someone knows something about a patch or how to solve the error message following (ioctl to the end), then please send me the Info:

  Stopping VMware services:
  Virtual machine communication interface is
  Virtual machine monitor makes
  File system is blocking
  Using 2.6.x kernel build system.
  do: enter the directory ' / tmp/vmware-root/modules/vmmon-only '.
  do /lib/modules/2.6.37.1-1.2-default/build/include/ - C... SUBDIRS = $PWD SRCROOT = $PWD. \
  MODULEBUILDDIR = modules
  make [1]: Entering directory ' / usr/src/linux-2.6.37.1-1.2-obj/i386/default'
  make - C /... /.. /Linux-2.6.37.1-1.2 O=/usr/src/linux-2.6.37.1-1.2-obj/i386/default/. modules of
  CC [M] /tmp/vmware-root/modules/vmmon-only/linux/driver.o
  In file included from tmp/vmware-root/modules/vmmon-only/./include/vmware.h:38:0,
  from /tmp/vmware-root/modules/vmmon-only/linux/driver.c:100:
  /tmp/vmware-root/modules/vmmon-only/./include/vm_basic_types.h:108:7: warning: "__FreeBSD__" is not defined
  In file included from tmp/vmware-root/modules/vmmon-only/./common/vmx86.h:32:0,
  of tmp/vmware-root/modules/vmmon-only/linux/driver.h:29.
  from /tmp/vmware-root/modules/vmmon-only/linux/driver.c:102:
  /tmp/vmware-root/modules/vmmon-only/./include/x86msr.h:164:0: warning: 'MSR_THERM2_CTL' redefined
  /usr/src/linux-2.6.37.1-1.2/arch/x86/include/ASM/MSR-index.h:235:0: Note: this is the location of the previous definition
  In file included from tmp/vmware-root/modules/vmmon-only/./include/vcpuset.h:103:0,
  of tmp/vmware-root/modules/vmmon-only/./include/modulecall.h:37.
  of tmp/vmware-root/modules/vmmon-only/./common/vmx86.h:33.
  of tmp/vmware-root/modules/vmmon-only/linux/driver.h:29.
  from /tmp/vmware-root/modules/vmmon-only/linux/driver.c:102:
  /tmp/vmware-root/modules/vmmon-only/./include/vm_atomic.h:329:7: warning: "_MSC_VER" is not defined
  /tmp/vmware-root/modules/vmmon-only/./include/vm_atomic.h:333:7: warning: "_MSC_VER" is not defined
  /tmp/vmware-root/modules/vmmon-only/./include/vm_atomic.h:401:7: warning: "_MSC_VER" is not defined
  /tmp/vmware-root/modules/vmmon-only/./include/vm_atomic.h:407:7: warning: "_MSC_VER" is not defined
  /tmp/vmware-root/modules/vmmon-only/./include/vm_atomic.h: in function 'Atomic_And ':
  /tmp/vmware-root/modules/vmmon-only/./include/vm_atomic.h:506:7: warning: "_MSC_VER" is not defined
  /tmp/vmware-root/modules/vmmon-only/./include/vm_atomic.h: in function 'Atomic_Or ':
  /tmp/vmware-root/modules/vmmon-only/./include/vm_atomic.h:595:7: warning: "_MSC_VER" is not defined
  /tmp/vmware-root/modules/vmmon-only/./include/vm_atomic.h: in function 'Atomic_Xor ':
  /tmp/vmware-root/modules/vmmon-only/./include/vm_atomic.h:684:7: warning: "_MSC_VER" is not defined
  /tmp/vmware-root/modules/vmmon-only/./include/vm_atomic.h: in function 'Atomic_Add ':
  /tmp/vmware-root/modules/vmmon-only/./include/vm_atomic.h:773:7: warning: "_MSC_VER" is not defined
  /tmp/vmware-root/modules/vmmon-only/./include/vm_atomic.h:775:7: warning: "_MSC_VER" is not defined
  /tmp/vmware-root/modules/vmmon-only/./include/vm_atomic.h: in function 'Atomic_Sub ':
  /tmp/vmware-root/modules/vmmon-only/./include/vm_atomic.h:860:7: warning: "_MSC_VER" is not defined
  /tmp/vmware-root/modules/vmmon-only/./include/vm_atomic.h:862:7: warning: "_MSC_VER" is not defined
  /tmp/vmware-root/modules/vmmon-only/./include/vm_atomic.h: in function 'Atomic_Inc ":
  /tmp/vmware-root/modules/vmmon-only/./include/vm_atomic.h:945:7: warning: "_MSC_VER" is not defined
  /tmp/vmware-root/modules/vmmon-only/./include/vm_atomic.h:947:7: warning: "_MSC_VER" is not defined
  /tmp/vmware-root/modules/vmmon-only/./include/vm_atomic.h: in function 'Atomic_Dec ':
  /tmp/vmware-root/modules/vmmon-only/./include/vm_atomic.h:1028:7: warning: "_MSC_VER" is not defined
  /tmp/vmware-root/modules/vmmon-only/./include/vm_atomic.h:1030:7: warning: "_MSC_VER" is not defined
  /tmp/vmware-root/modules/vmmon-only/./include/vm_atomic.h: at the highest level:
  /tmp/vmware-root/modules/vmmon-only/./include/vm_atomic.h:1223:7: warning: "_MSC_VER" is not defined
  /tmp/vmware-root/modules/vmmon-only/./include/vm_atomic.h:1227:7: warning: "_MSC_VER" is not defined
  /tmp/vmware-root/modules/vmmon-only/./include/vm_atomic.h:1536:7: warning: "_MSC_VER" is not defined
  /tmp/vmware-root/modules/vmmon-only/./include/vm_atomic.h:1663:7: warning: "_MSC_VER" is not defined
  In file included from tmp/vmware-root/modules/vmmon-only/./include/vm_basic_asm.h:46:0,
  of tmp/vmware-root/modules/vmmon-only/./include/rateconv.h:45.
  of tmp/vmware-root/modules/vmmon-only/./include/modulecall.h:40.
  of tmp/vmware-root/modules/vmmon-only/./common/vmx86.h:33.
  of tmp/vmware-root/modules/vmmon-only/linux/driver.h:29.
  from /tmp/vmware-root/modules/vmmon-only/linux/driver.c:102:
  /tmp/vmware-root/modules/vmmon-only/./include/vm_basic_asm_x86.h:62:7: warning: "_MSC_VER" is not defined
  /tmp/vmware-root/modules/vmmon-only/./include/vm_basic_asm_x86.h:177:7: warning: "_MSC_VER" is not defined
  /tmp/vmware-root/modules/vmmon-only/./include/vm_basic_asm_x86.h:346:7: warning: "_MSC_VER" is not defined
  /tmp/vmware-root/modules/vmmon-only/./include/vm_basic_asm_x86.h:453:7: warning: "_MSC_VER" is not defined
  In file included from tmp/vmware-root/modules/vmmon-only/./include/vm_asm.h:43:0,
  from /tmp/vmware-root/modules/vmmon-only/linux/driver.c:104:
  /tmp/vmware-root/modules/vmmon-only/./include/vm_asm_x86.h:486:7: warning: "_MSC_VER" is not defined
  /tmp/vmware-root/modules/vmmon-only/./include/vm_asm_x86.h:779:7: warning: "_MSC_VER" is not defined
  /tmp/vmware-root/modules/vmmon-only/./include/vm_asm_x86.h:820:7: warning: "_MSC_VER" is not defined
  /tmp/vmware-root/modules/vmmon-only/./include/vm_asm_x86.h:922:7: warning: "_MSC_VER" is not defined
  In file included from /tmp/vmware-root/modules/vmmon-only/linux/driver.c:120:0:
  /tmp/vmware-root/modules/vmmon-only/./common/hostif.h:53:7: warning: 'WINNT_DDK' is undefined
  /tmp/vmware-root/modules/vmmon-only/Linux/driver.c: in function 'init_module(2) ':
  /tmp/vmware-root/modules/vmmon-only/Linux/driver.c:427:15: error: 'struct file_operations' has no member named 'ioctl '.
  make [4]: * [/ tmp/vmware-root/modules/vmmon-only/linux/driver.o] error 1
  make [3]: * [_module_/tmp/vmware-root/modules/vmmon-only] error 2
  make [2]: * [branded] error 2
  make [1]: * [all] error 2
  make [1]: leaving directory ' / usr/src/linux-2.6.37.1-1.2-obj/i386/default'
  make: * [vmmon.ko] error 2
  make: leaving directory ' / tmp/vmware-root/modules/vmmon-only '.
  Cannot install vmmon

  15/04/2011

  I wrote a patch for the kernel 2.6.37.1 - 1.2. Now, all modules compile without error. But the application does not start!

  Error message:

  / usr/bin/VMware: line 31: 1372 Segmentation fault "$BINDIR" / vmware-modconfig - appname = "VMware Workstation" - icon = "vmware-workstation.

  Someone at - it ideas? Any help is the apprecated!

  The patch file and the output of the compiler are attached.

  Thanks a lot for the patch! Works very well with 6.5.5 on suse 11.4 (2.6.37.1 - 1.2 - desktop)

  Search for your VMWARE_USE_SHIPPED_GTK = yes environment variables

  When that was settled, I had the same problem (segmentation fault). Set to = no or been completely just unplugged

  Hope this works for you, as your patch worked for me