[opensuse-factory] Tumbleweed VMware Workstation 12 shows a prompt that gcc version 6.2.1 was not found
Hi all, I installed VMware Workstation 12.5 on Tumbleweed on 20161108. However, when I try to initialize it, I', getting a prompt that GNU C Compiler (gcc) version 6.2.1 was not found. Tumbleweed provides gcc 6.2.1. Is there a workaround for this? See the screenshot. -- Cheers! Roman
* Roman Bysh <rbtc1@rogers.com> [11-10-16 19:21]:
Hi all,
I installed VMware Workstation 12.5 on Tumbleweed on 20161108. However, when I try to initialize it, I', getting a prompt that GNU C Compiler (gcc) version 6.2.1 was not found.
Tumbleweed provides gcc 6.2.1. Is there a workaround for this?
See the screenshot.
Tw provides gcc-6-2.4.x86_64 -- (paka)Patrick Shanahan Plainfield, Indiana, USA @ptilopteri http://en.opensuse.org openSUSE Community Member facebook/ptilopteri http://wahoo.no-ip.org Photo Album: http://wahoo.no-ip.org/gallery2 Registered Linux User #207535 @ http://linuxcounter.net -- To unsubscribe, e-mail: opensuse-factory+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse-factory+owner@opensuse.org
Am Donnerstag, 10. November 2016, 19:20:47 schrieb Roman Bysh:
Hi all,
I installed VMware Workstation 12.5 on Tumbleweed on 20161108. However, when I try to initialize it, I', getting a prompt that GNU C Compiler (gcc) version 6.2.1 was not found.
You can try to compile the modules manually. Unpack the tar file in /usr/lib/vmware/modules/source , cd to the directory with the source and run make, then copy the generated module (.ko) to /lib/modules/`uname - r`/kernel/drivers/misc. -- To unsubscribe, e-mail: opensuse-factory+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse-factory+owner@opensuse.org
Am 2016-11-11 um 04:20 schrieb Markus Koßmann:
Am Donnerstag, 10. November 2016, 19:20:47 schrieb Roman Bysh:
However, when I try to initialize it, I', getting a prompt that GNU C Compiler (gcc) version 6.2.1 was not found.
You can try to compile the modules manually. Unpack the tar file in /usr/lib/vmware/modules/source , cd to the directory with the source and run make, then copy the generated module (.ko) to /lib/modules/`uname - r`/kernel/drivers/misc.
yes, this is currently the only way. you have to do this at least for vmmon.tar and vmnet.tar. vmblock.tar, vsock.tar and vmci.tar don't compile with current kernel. but it seems, that it still works without them. -- Best Regards | Freundliche Grüße | Cordialement | Cordiali Saluti | *DI Rainer Klier* Research & Development, Technical Sales Consultant Namirial GmbH -- To unsubscribe, e-mail: opensuse-factory+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse-factory+owner@opensuse.org
Am Freitag, 11. November 2016, 08:21:27 schrieb Rainer Klier:
vmblock.tar, vsock.tar and vmci.tar don't compile with current kernel. but it seems, that it still works without them. There are opensourced versions of vsock and vmci called vmw_vsock and vmw_vmci included in current kernels for some time now. An the vmblock functionality can be replaced by vmware-vmblock-fuse included in Open-VM-Tools -- To unsubscribe, e-mail: opensuse-factory+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse-factory+owner@opensuse.org
On 11/11/2016 08:19 AM, Markus Koßmann wrote:
Am Freitag, 11. November 2016, 08:21:27 schrieb Rainer Klier:
vmblock.tar, vsock.tar and vmci.tar don't compile with current kernel. but it seems, that it still works without them. There are opensourced versions of vsock and vmci called vmw_vsock and vmw_vmci included in current kernels for some time now. An the vmblock functionality can be replaced by vmware-vmblock-fuse included in Open-VM-Tools
If I install open-vm-tools it will not disable the pop up complaining that I don't have gcc 6.2.1 installed. Wouldn't it be much easier to find and install gcc 6.2.1? I have switched to Leap 42.2. It doesn't show any gcc 6.2.1 pop up - even though I have gcc 4.9 installed. -- To unsubscribe, e-mail: opensuse-factory+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse-factory+owner@opensuse.org
On Friday, 11 November 2016 14:19 Markus Koßmann wrote:
Am Freitag, 11. November 2016, 08:21:27 schrieb Rainer Klier:
vmblock.tar, vsock.tar and vmci.tar don't compile with current kernel. but it seems, that it still works without them.
There are opensourced versions of vsock and vmci called vmw_vsock and vmw_vmci included in current kernels for some time now.
Well, "opensourced" is not the right word, they were open source even before that, otherwise you wouldn't get source tarballs to build. The right term would be "in-tree". Michal Kubeček -- To unsubscribe, e-mail: opensuse-factory+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse-factory+owner@opensuse.org
Am 2016-11-11 um 14:19 schrieb Markus Koßmann:
but it seems, that it still works without them. There are opensourced versions of vsock and vmci called vmw_vsock and vmw_vmci included in current kernels for some time now.
ah, interesting. i didn't know this. great.
An the vmblock functionality can be replaced by vmware-vmblock-fuse included in Open-VM-Tools
great. i will try asap. thanks for the info. -- Best Regards | Freundliche Grüße | Cordialement | Cordiali Saluti | *DI Rainer Klier* Research & Development, Technical Sales Consultant Namirial GmbH -- To unsubscribe, e-mail: opensuse-factory+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse-factory+owner@opensuse.org
Hello
I installed VMware Workstation 12.5 on Tumbleweed on 20161108. However, when I try to initialize it, I', getting a prompt that GNU C Compiler (gcc) version 6.2.1 was not found.
I downloaded and installed the latest Tumbleweed snapshot today : openSUSE-Tumbleweed-DVD-x86_64-Snapshot20161111-Media.iso Then I downloaded and installed the lastest version of VMware-Workstation: VMware-Workstation-Full-12.5.1-4542065.x86_64.bundle Then I manually compiled the vmnet and vmmon as per usual VMware-Workstation ran fine The following works for me. cd /usr/src/linux make menuconfig make clean && make mrproper && make cloneconfig make scripts && make prepare # cd /usr/lib/vmware/modules/source tar -xvf ./vmnet.tar cd vmnet-only make cd .. ls -l vmnet.o cp ./vmnet.o /lib/modules/`uname -r`/kernel/drivers/misc/vmnet.ko # cd /usr/lib/vmware/modules/source tar -xvf ./vmmon.tar cd vmmon-only make cd .. ls -l vmmon.o cp vmmon.o /lib/modules/`uname -r`/kernel/drivers/misc/vmmon.ko depmod -a Hope this helps Regards James -- To unsubscribe, e-mail: opensuse-factory+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse-factory+owner@opensuse.org
On 11/13/2016 02:33 PM, James PEARSON wrote:
Hello
I installed VMware Workstation 12.5 on Tumbleweed on 20161108. However, when I try to initialize it, I', getting a prompt that GNU C Compiler (gcc) version 6.2.1 was not found.
I downloaded and installed the latest Tumbleweed snapshot today : openSUSE-Tumbleweed-DVD-x86_64-Snapshot20161111-Media.iso
Then I downloaded and installed the lastest version of VMware-Workstation: VMware-Workstation-Full-12.5.1-4542065.x86_64.bundle
Then I manually compiled the vmnet and vmmon as per usual VMware-Workstation ran fine
The following works for me.
cd /usr/src/linux make menuconfig make clean && make mrproper && make cloneconfig make scripts && make prepare # cd /usr/lib/vmware/modules/source tar -xvf ./vmnet.tar cd vmnet-only make cd .. ls -l vmnet.o cp ./vmnet.o /lib/modules/`uname -r`/kernel/drivers/misc/vmnet.ko # cd /usr/lib/vmware/modules/source tar -xvf ./vmmon.tar cd vmmon-only make cd .. ls -l vmmon.o cp vmmon.o /lib/modules/`uname -r`/kernel/drivers/misc/vmmon.ko depmod -a
Hope this helps
Regards James
I'll try your steps and get back with my results. -- To unsubscribe, e-mail: opensuse-factory+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse-factory+owner@opensuse.org
13.11.2016 22:33, James PEARSON пишет:
The following works for me.
cd /usr/src/linux make menuconfig make clean && make mrproper && make cloneconfig make scripts && make prepare
You should not need to do it. Actually you should not even need kernel-source to be installed to compile external modules - that is what kernel-(-flavor)-devel package is for. Which allows you to have multiple different kernel packages at the same time and compile for each one. -- To unsubscribe, e-mail: opensuse-factory+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse-factory+owner@opensuse.org
14.11.2016 06:29, Andrei Borzenkov пишет:
13.11.2016 22:33, James PEARSON пишет:
The following works for me.
cd /usr/src/linux make menuconfig make clean && make mrproper && make cloneconfig make scripts && make prepare
You should not need to do it. Actually you should not even need kernel-source to be installed to compile external modules - that is what kernel-(-flavor)-devel package is for. Which allows you to have multiple different kernel packages at the same time and compile for each one.
Ans yes, I just tested compiling VMware modules without all these voodoo dances and it works just fine. I do not even have kernel sources installed so I (fortunately) cannot even try these steps. -- To unsubscribe, e-mail: opensuse-factory+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse-factory+owner@opensuse.org
On Monday 2016-11-14 04:29, Andrei Borzenkov wrote:
13.11.2016 22:33, James PEARSON пишет:
The following works for me.
cd /usr/src/linux make menuconfig make clean && make mrproper && make cloneconfig make scripts && make prepare
You should not need to do it. Actually you should not even need kernel-source to be installed to compile external modules - that is what kernel-(-flavor)-devel package is for. Which allows you to have multiple different kernel packages at the same time and compile for each one.
In fact, it [cloneconfig] even *breaks* building modules. http://inai.de/2007/04/12 -- To unsubscribe, e-mail: opensuse-factory+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse-factory+owner@opensuse.org
On Mon, Nov 14, 2016 at 10:57 AM, Jan Engelhardt <jengelh@inai.de> wrote:
On Monday 2016-11-14 04:29, Andrei Borzenkov wrote:
13.11.2016 22:33, James PEARSON пишет:
The following works for me.
cd /usr/src/linux make menuconfig make clean && make mrproper && make cloneconfig make scripts && make prepare
You should not need to do it. Actually you should not even need kernel-source to be installed to compile external modules - that is what kernel-(-flavor)-devel package is for. Which allows you to have multiple different kernel packages at the same time and compile for each one.
In fact, it [cloneconfig] even *breaks* building modules. http://inai.de/2007/04/12
Old habits die hard ... -- To unsubscribe, e-mail: opensuse-factory+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse-factory+owner@opensuse.org
On Monday 2016-11-14 09:07, Andrei Borzenkov wrote:
In fact, it [cloneconfig] even *breaks* building modules. http://inai.de/2007/04/12
Old habits die hard ...
I am tempted to just actively prohibit running cloneconfig by a patch to the kernel-*devel RPM. -- To unsubscribe, e-mail: opensuse-factory+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse-factory+owner@opensuse.org
On 2016-11-14 08:57, Jan Engelhardt wrote:
On Monday 2016-11-14 04:29, Andrei Borzenkov wrote:
13.11.2016 22:33, James PEARSON пишет:
The following works for me.
cd /usr/src/linux make menuconfig make clean && make mrproper && make cloneconfig make scripts && make prepare
You should not need to do it. Actually you should not even need kernel-source to be installed to compile external modules - that is what kernel-(-flavor)-devel package is for. Which allows you to have multiple different kernel packages at the same time and compile for each one.
In fact, it [cloneconfig] even *breaks* building modules. http://inai.de/2007/04/12
Well, the use of cloneconfig is documented by SUSE Labs. /usr/src/linux/README.SUSE -- Cheers / Saludos, Carlos E. R. (from 13.1 x86_64 "Bottle" at Telcontar)
On 2016-11-13 20:33, James PEARSON wrote:
The following works for me.
cd /usr/src/linux make menuconfig make clean && make mrproper && make cloneconfig
make mrproper should never be used on the sources tree as prepared by openSUSE. Even "make clean" is not needed on a freshly installed kernel sources rpm. In fact this is enough: install kernel sources from rpm make cloneconfig && make scripts && make prepare and then proceed to the vmware part. -- Cheers/Saludos Carlos E. R. (testing openSUSE Leap 42.2, at Minas-Anor) -- To unsubscribe, e-mail: opensuse-factory+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse-factory+owner@opensuse.org
14.11.2016 06:40, Carlos E. R. пишет:
On 2016-11-13 20:33, James PEARSON wrote:
The following works for me.
cd /usr/src/linux make menuconfig make clean && make mrproper && make cloneconfig
make mrproper should never be used on the sources tree as prepared by openSUSE. Even "make clean" is not needed on a freshly installed kernel sources rpm. In fact this is enough:
install kernel sources from rpm
Once more - you should not need kernel sources to build external modules.
make cloneconfig && make scripts && make prepare
and then proceed to the vmware part.
-- To unsubscribe, e-mail: opensuse-factory+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse-factory+owner@opensuse.org
On 2016-11-14 04:50, Andrei Borzenkov wrote:
14.11.2016 06:40, Carlos E. R. пишет:
install kernel sources from rpm
Once more - you should not need kernel sources to build external modules.
That's the theory, yes, but it doesn't always work for me. I don't know why. Anyway, I have the kernel sources because sometimes I do build the kernel. -- Cheers / Saludos, Carlos E. R. (from 13.1 x86_64 "Bottle" at Telcontar)
Отправлено с iPhone
14 нояб. 2016 г., в 7:24, Carlos E. R. <robin.listas@telefonica.net> написал(а):
On 2016-11-14 04:50, Andrei Borzenkov wrote: 14.11.2016 06:40, Carlos E. R. пишет:
install kernel sources from rpm
Once more - you should not need kernel sources to build external modules.
That's the theory, yes, but it doesn't always work for me. I don't know why. Anyway, I have the kernel sources because sometimes I do build the kernel.
Which you should never do inside of /usr/src/linux.
-- Cheers / Saludos,
Carlos E. R. (from 13.1 x86_64 "Bottle" at Telcontar)
-- To unsubscribe, e-mail: opensuse-factory+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse-factory+owner@opensuse.org
On 2016-11-14 05:58, Andrei Borzenkov wrote:
That's the theory, yes, but it doesn't always work for me. I don't know why. Anyway, I have the kernel sources because sometimes I do build the kernel.
Which you should never do inside of /usr/src/linux.
Well, that's new to me. They never told me that. In fact, I tried once and it was a nightmare. Is the procedure explained somewhere in our wiki? Will NVidia .run script find the needed things? -- Cheers / Saludos, Carlos E. R. (from 13.1 x86_64 "Bottle" at Telcontar)
On Mon, Nov 14, 2016 at 2:17 PM, Carlos E. R. <robin.listas@telefonica.net> wrote:
On 2016-11-14 05:58, Andrei Borzenkov wrote:
That's the theory, yes, but it doesn't always work for me. I don't know why. Anyway, I have the kernel sources because sometimes I do build the kernel.
Which you should never do inside of /usr/src/linux.
Well, that's new to me. They never told me that.
Really? (2) Create a build directory for use in configuring and building the kernel. Using /usr/src/linux directly requires root priviledges and will cause problems if you need to build kernel modules for other installed kernels. The file /usr/src/linux/README.SUSE you just mentioned. Granted, this is Kernel:HEAD though.
In fact, I tried once and it was a nightmare.
Is the procedure explained somewhere in our wiki?
I do not know. /usr/src/linux/REAME.SUSE again looks pretty promising.
Will NVidia .run script find the needed things?
Yes. If you find any module Makefile today that fails - scream loud at module maintainer. New kbuild framework has been around for 10+ years. -- To unsubscribe, e-mail: opensuse-factory+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse-factory+owner@opensuse.org
Hello This thread has been extremely interesting - many thanks for all the comebacks ! I did another fresh install of Tumbleweed tonight : openSUSE-Tumbleweed-DVD-x86_64-Snapshot20161111-Media.iso Then I downloaded and installed the lastest version of VMware-Workstation (which BTW has changed since yesterday - the 13th of Nov.): VMware-Workstation-Full-12.5.2-4638234.x86_64.bundle Then I manually compiled the vmnet and vmmon using your suggestions :) VMware-Workstation ran fine : # required rpms rpm -q kernel-default kernel-devel gcc make # Next mkdir /tmp/vmware && cd /tmp/vmware cd /tmp/vmware/source tar -xvf ./vmnet.tar cd vmnet-only make ls -l vmnet.o cp ./vmnet.o /lib/modules/`uname -r`/kernel/drivers/misc/vmnet.ko # cd /tmp/vmware/source echo "Compiling the vmmon module... " tar -xvf ./vmmon.tar cd vmmon-only make cd .. ls -l vmmon.o cp vmmon.o /lib/modules/`uname -r`/kernel/drivers/misc/vmmon.ko # cp vmmon.o /lib/modules/`uname -r`/misc/vmmon.ko # depmod -a # Note : /tmp is mounted as tmpfs Many thanks for the new knowledge! Regards James -- To unsubscribe, e-mail: opensuse-factory+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse-factory+owner@opensuse.org
James PEARSON wrote: [...]
Then I manually compiled the vmnet and vmmon using your suggestions :) VMware-Workstation ran fine :
# required rpms rpm -q kernel-default kernel-devel gcc make
# Next mkdir /tmp/vmware && cd /tmp/vmware cd /tmp/vmware/source tar -xvf ./vmnet.tar cd vmnet-only make
ls -l vmnet.o cp ./vmnet.o /lib/modules/`uname -r`/kernel/drivers/misc/vmnet.ko
[...]
ls -l vmmon.o cp vmmon.o /lib/modules/`uname -r`/kernel/drivers/misc/vmmon.ko
You're sure to copy the *.o files instead of the created *.ko files? Is there a reason to do so? Just wondering Andreas -- To unsubscribe, e-mail: opensuse-factory+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse-factory+owner@opensuse.org
On Thursday, 10 November 2016 19:20 Roman Bysh wrote:
I installed VMware Workstation 12.5 on Tumbleweed on 20161108. However, when I try to initialize it, I', getting a prompt that GNU C Compiler (gcc) version 6.2.1 was not found.
This usually happens when the kernel you are building the modules against (by default the currently running one, unless VM_UNAME is set) was built by different version of gcc than one you are using to build modules. I have the same problem on a 13.1 system with kernels from Kernel:HEAD or Kernel:stable. On Tumbleweed, I guess fully updating the system should fix it. If not, it should settle down within few days (as soon as both new gcc and a kernel built by it get into TW).
Tumbleweed provides gcc 6.2.1. Is there a workaround for this?
As others suggested: - install kernel-$flavor-devel, kernel-devel and kernel-macros (zypper install kernel-$flavor-devel will suffice, $flavor is most likely "default") - unpack vmmon.tar and vmnet.tar from /usr/lib/vmware/modules/source - optionally, some patching might be needed for recent kernels (but if it is, it would be needed for "vmware-modconfig" as well) - run "make" in each vmmon-only/ and vmnet-only/ - create /lib/modules/$(uname -r)/misc and copy vmmon.ko and vmnet.ko into it It's not 100% safe but the risk that kernel and modules built by a different gcc versions would be incompatible is rather low (even lower if the versions are this close). Michal Kubeček -- To unsubscribe, e-mail: opensuse-factory+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse-factory+owner@opensuse.org
Am 2016-11-14 um 07:08 schrieb Michal Kubecek:
As others suggested:
- install kernel-$flavor-devel, kernel-devel and kernel-macros (zypper install kernel-$flavor-devel will suffice, $flavor is most likely "default")
at this stage i additionally do: * cd to /usr/src/linux-obj/x86_64/default/ * and then do a "make prepare" * and a "make modules_prepare". then i continue as Michal Kubecek wrote:
- unpack vmmon.tar and vmnet.tar from /usr/lib/vmware/modules/source - optionally, some patching might be needed for recent kernels (but if it is, it would be needed for "vmware-modconfig" as well) - run "make" in each vmmon-only/ and vmnet-only/ - create /lib/modules/$(uname -r)/misc and copy vmmon.ko and vmnet.ko into it
and after this i do a "depmod -a". this works well for me. -- Best Regards | Freundliche Grüße | Cordialement | Cordiali Saluti | *DI Rainer Klier* Research & Development, Technical Sales Consultant Namirial GmbH -- To unsubscribe, e-mail: opensuse-factory+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse-factory+owner@opensuse.org
On Mon, Nov 14, 2016 at 1:55 PM, Rainer Klier <rainer.klier@xyzmo.com> wrote:
Am 2016-11-14 um 07:08 schrieb Michal Kubecek:
As others suggested:
- install kernel-$flavor-devel, kernel-devel and kernel-macros (zypper install kernel-$flavor-devel will suffice, $flavor is most likely "default")
at this stage i additionally do: * cd to /usr/src/linux-obj/x86_64/default/ * and then do a "make prepare" * and a "make modules_prepare".
Why? This package is already prepared for external modules build. Do you have any evidence that you *need* it? As I already wrote, this is not needed to manually compile vmware modules. -- To unsubscribe, e-mail: opensuse-factory+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse-factory+owner@opensuse.org
Am 2016-11-14 um 12:05 schrieb Andrei Borzenkov:
On Mon, Nov 14, 2016 at 1:55 PM, Rainer Klier <rainer.klier@xyzmo.com> wrote:
at this stage i additionally do: * cd to /usr/src/linux-obj/x86_64/default/ * and then do a "make prepare" * and a "make modules_prepare".
Why? This package is already prepared for external modules build.
Do you have any evidence that you *need* it? As I already wrote, this is not needed to manually compile vmware modules.
there are some reasons why i keep doing this: * i also recompile my wifi-driver wl.ko for my broadcom wifi card (hybrid-v35_64-nodebug-pcoem-6_30_223_271) * i also recompile the displaylink driver displaylink-driver-1.2.58 * i also recompile the proprietary nvidia driver (but i think this one doesn't need it also...) * i remeber, that last time, i tried recompiling vmware modules without it, it didn' work. but maybe that happened at a time long ago, where it really was needed. * last but not least: it doesn't hurt doing it. and since all these kernel modules compiles are working without problems, i keep doing the "make prepare" and "make modules_prepare". -- Best Regards | Freundliche Grüße | Cordialement | Cordiali Saluti | *DI Rainer Klier* Research & Development, Technical Sales Consultant Namirial GmbH -- To unsubscribe, e-mail: opensuse-factory+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse-factory+owner@opensuse.org
On Mon, Nov 14, 2016 at 3:24 PM, Rainer Klier <rainer.klier@xyzmo.com> wrote:
Am 2016-11-14 um 12:05 schrieb Andrei Borzenkov:
On Mon, Nov 14, 2016 at 1:55 PM, Rainer Klier <rainer.klier@xyzmo.com> wrote:
at this stage i additionally do: * cd to /usr/src/linux-obj/x86_64/default/ * and then do a "make prepare" * and a "make modules_prepare".
Why? This package is already prepared for external modules build.
Do you have any evidence that you *need* it? As I already wrote, this is not needed to manually compile vmware modules.
there are some reasons why i keep doing this: * i also recompile my wifi-driver wl.ko for my broadcom wifi card (hybrid-v35_64-nodebug-pcoem-6_30_223_271) * i also recompile the displaylink driver displaylink-driver-1.2.58
Care to provide link to both?
* i also recompile the proprietary nvidia driver (but i think this one doesn't need it also...) * i remeber, that last time, i tried recompiling vmware modules without it, it didn' work. but maybe that happened at a time long ago, where it really was needed. * last but not least: it doesn't hurt doing it.
It does. What you have there no more matches your running kernel.
and since all these kernel modules compiles are working without problems, i keep doing the "make prepare" and "make modules_prepare".
-- To unsubscribe, e-mail: opensuse-factory+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse-factory+owner@opensuse.org
hi, Am 2016-11-14 um 13:46 schrieb Andrei Borzenkov:
On Mon, Nov 14, 2016 at 3:24 PM, Rainer Klier <rainer.klier@xyzmo.com> wrote:
Am 2016-11-14 um 12:05 schrieb Andrei Borzenkov:
On Mon, Nov 14, 2016 at 1:55 PM, Rainer Klier <rainer.klier@xyzmo.com> wrote:
there are some reasons why i keep doing this: * i also recompile my wifi-driver wl.ko for my broadcom wifi card (hybrid-v35_64-nodebug-pcoem-6_30_223_271) * i also recompile the displaylink driver displaylink-driver-1.2.58
Care to provide link to both?
here are links to prepatched archives, so that the kernel modules can be built on tumbleweed with kernel 4.8.x: displaylink-driver-1.2.58: https://drive.google.com/open?id=0Bwpj5Wm8iVh-RHJVQmUtYWpEWDg hybrid-v35_64-nodebug-pcoem-6_30_223_271: https://drive.google.com/open?id=0Bwpj5Wm8iVh-VFZab1FLQVUzdGM
* last but not least: it doesn't hurt doing it.
It does. What you have there no more matches your running kernel.
why should it hurt? what do you mean? why should it not match the runing kernel? if it would be this case, all 4 kernel modules (nvidia, vmware, wl and displaylink) would not work. all i do is just prepare the /usr/src/linux-obj/x86_64/default folder for kernel module compiling. but when the next kernel update 4.8.8 arrives, i will try to make all 4 kernel modules WITHOUT the "make prepare" and "make modules_prepare". if it still works, then it is great to not need doing this on every kernel update. maybe this is not needed any more today for these 4 kernel modules. but it surely was. but i stll don't understand why it should be a problem doing it. -- Best Regards | Freundliche Grüße | Cordialement | Cordiali Saluti | *DI Rainer Klier* Research & Development, Technical Sales Consultant Namirial GmbH -- To unsubscribe, e-mail: opensuse-factory+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse-factory+owner@opensuse.org
On Mon, Nov 14, 2016 at 3:24 PM, Rainer Klier <rainer.klier@xyzmo.com> wrote:
Am 2016-11-14 um 12:05 schrieb Andrei Borzenkov:
On Mon, Nov 14, 2016 at 1:55 PM, Rainer Klier <rainer.klier@xyzmo.com> wrote:
at this stage i additionally do: * cd to /usr/src/linux-obj/x86_64/default/ * and then do a "make prepare" * and a "make modules_prepare".
Why? This package is already prepared for external modules build.
Do you have any evidence that you *need* it? As I already wrote, this is not needed to manually compile vmware modules.
there are some reasons why i keep doing this: * i also recompile my wifi-driver wl.ko for my broadcom wifi card (hybrid-v35_64-nodebug-pcoem-6_30_223_271)
I briefly tested this one from Broadcom site using 4.8.6 TW kernel-default-devel and it happily starts to build without any prior magic incantations. It fails, but that is unrelated and known issue (IEEE80211_BAND_2G e.g. is missing) - see e.g. https://build.opensuse.org/package/view_file/home:X0F:HSF:Kernel/broadcom-wl.... -- To unsubscribe, e-mail: opensuse-factory+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse-factory+owner@opensuse.org
Am 2016-11-14 um 15:00 schrieb Andrei Borzenkov:
On Mon, Nov 14, 2016 at 3:24 PM, Rainer Klier <rainer.klier@xyzmo.com> wrote:
Am 2016-11-14 um 12:05 schrieb Andrei Borzenkov:
On Mon, Nov 14, 2016 at 1:55 PM, Rainer Klier <rainer.klier@xyzmo.com> wrote:
there are some reasons why i keep doing this: * i also recompile my wifi-driver wl.ko for my broadcom wifi card (hybrid-v35_64-nodebug-pcoem-6_30_223_271)
I briefly tested this one from Broadcom site using 4.8.6 TW kernel-default-devel and it happily starts to build without any prior magic incantations. It fails, but that is unrelated and known issue (IEEE80211_BAND_2G e.g. is missing) - see e.g. https://build.opensuse.org/package/view_file/home:X0F:HSF:Kernel/broadcom-wl....
here is a prepatched archive, so that the kernel modules can be built on tumbleweed with kernel 4.8.x: hybrid-v35_64-nodebug-pcoem-6_30_223_271: https://drive.google.com/open?id=0Bwpj5Wm8iVh-VFZab1FLQVUzdGM -- Best Regards | Freundliche Grüße | Cordialement | Cordiali Saluti | *DI Rainer Klier* Research & Development, Technical Sales Consultant Namirial GmbH -- To unsubscribe, e-mail: opensuse-factory+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse-factory+owner@opensuse.org
On Monday, 14 November 2016 11:55 Rainer Klier wrote:
Am 2016-11-14 um 07:08 schrieb Michal Kubecek:
As others suggested: - install kernel-$flavor-devel, kernel-devel and kernel-macros
(zypper install kernel-$flavor-devel will suffice, $flavor is most likely "default")
at this stage i additionally do: * cd to /usr/src/linux-obj/x86_64/default/ * and then do a "make prepare" * and a "make modules_prepare".
You shouldn't. The kernel-$flavor-devel package is prepared exactly so that you do not need to do this.
then i continue as Michal Kubecek wrote:
- unpack vmmon.tar and vmnet.tar from /usr/lib/vmware/modules/source - optionally, some patching might be needed for recent kernels
(but if it is, it would be needed for "vmware-modconfig" as well)
- run "make" in each vmmon-only/ and vmnet-only/ - create /lib/modules/$(uname -r)/misc and copy vmmon.ko and vmnet.ko
into it
and after this i do a "depmod -a".
Ah, yes, of course. I knew I forgot something :-) Thinking about it, running "/etc/init.d/vmware restart" after all this may be another step I forgot. Michal Kubeček -- To unsubscribe, e-mail: opensuse-factory+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse-factory+owner@opensuse.org
Am 2016-11-14 um 12:40 schrieb Michal Kubecek:
On Monday, 14 November 2016 11:55 Rainer Klier wrote:
Am 2016-11-14 um 07:08 schrieb Michal Kubecek:
As others suggested: - install kernel-$flavor-devel, kernel-devel and kernel-macros
(zypper install kernel-$flavor-devel will suffice, $flavor is most likely "default")
at this stage i additionally do: * cd to /usr/src/linux-obj/x86_64/default/ * and then do a "make prepare" * and a "make modules_prepare".
You shouldn't. The kernel-$flavor-devel package is prepared exactly so that you do not need to do this.
ok. i will avoid it on the next kernel update 4.8.8 if this is true, i will be able to build all my needed external kernel modules (nvidia, wl, displaylink, vmware) without it. but is there a problem doing it?
and after this i do a "depmod -a".
Ah, yes, of course. I knew I forgot something :-) Thinking about it, running "/etc/init.d/vmware restart" after all this may be another step I forgot.
correct. but these days this is done with systemctl restart vmware.service ;-) -- Best Regards | Freundliche Grüße | Cordialement | Cordiali Saluti | *DI Rainer Klier* Research & Development, Technical Sales Consultant Namirial GmbH -- To unsubscribe, e-mail: opensuse-factory+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse-factory+owner@opensuse.org
On 2016-11-15 16:39, Rainer Klier wrote:
Ah, yes, of course. I knew I forgot something :-) Thinking about it, running "/etc/init.d/vmware restart" after all this may be another step I forgot.
correct.
but these days this is done with systemctl restart vmware.service ;-)
Actually, the call to "vmplayer" as root in a terminal, does the vmware kernel module compile and start services. -- Cheers / Saludos, Carlos E. R. (from 13.1 x86_64 "Bottle" at Telcontar)
15.11.2016 18:39, Rainer Klier пишет:
Am 2016-11-14 um 12:40 schrieb Michal Kubecek:
On Monday, 14 November 2016 11:55 Rainer Klier wrote:
Am 2016-11-14 um 07:08 schrieb Michal Kubecek:
As others suggested: - install kernel-$flavor-devel, kernel-devel and kernel-macros
(zypper install kernel-$flavor-devel will suffice, $flavor is most likely "default")
at this stage i additionally do: * cd to /usr/src/linux-obj/x86_64/default/ * and then do a "make prepare" * and a "make modules_prepare".
You shouldn't. The kernel-$flavor-devel package is prepared exactly so that you do not need to do this.
ok. i will avoid it on the next kernel update 4.8.8 if this is true, i will be able to build all my needed external kernel modules (nvidia, wl, displaylink, vmware) without it.
but is there a problem doing it?
Because it depends on your personal environment and may change compile parameters in unpredictable way. As trivial example linux-ffk5:/usr/src/linux-4.8.6-2-obj/x86_64/default # make -n V=1 prepare make -C ../../../linux-4.8.6-2 O=/usr/src/linux-4.8.6-2-obj/x86_64/default/. prepare make -C /usr/src/linux-4.8.6-2-obj/x86_64/default KBUILD_SRC=/usr/src/linux-4.8.6-2 -f /usr/src/linux-4.8.6-2/Makefile prepare /usr/src/linux-4.8.6-2/Makefile:1052: "Cannot use CONFIG_STACK_VALIDATION, please install libelf-dev, libelf-devel or elfutils-libelf-devel" So it will continue but with disabled STACK_VALIDATION. And of course it requires full kernel-source that is not needed normally and that I do not have. make -f /usr/src/linux-4.8.6-2/scripts/Makefile.build obj=arch/x86/entry/syscalls all make[3]: *** No rule to make target '/usr/src/linux-4.8.6-2/arch/x86/entry/syscalls/syscall_32.tbl', needed by 'arch/x86/entry/syscalls/../../include/generated/asm/syscalls_32.h'. Stop. make[2]: *** [arch/x86/Makefile:193: archheaders] Error 2 make[1]: *** [Makefile:150: sub-make] Error 2 make: *** [Makefile:24: __sub-make] Error 2 bor@bor-Latitude-E5450:~/src/linux$ -- To unsubscribe, e-mail: opensuse-factory+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse-factory+owner@opensuse.org
Am 2016-11-15 um 19:05 schrieb Andrei Borzenkov:
15.11.2016 18:39, Rainer Klier пишет:
but is there a problem doing it?
Because it depends on your personal environment and may change compile parameters in unpredictable way. As trivial example
linux-ffk5:/usr/src/linux-4.8.6-2-obj/x86_64/default # make -n V=1 prepare make -C ../../../linux-4.8.6-2 O=/usr/src/linux-4.8.6-2-obj/x86_64/default/. prepare make -C /usr/src/linux-4.8.6-2-obj/x86_64/default KBUILD_SRC=/usr/src/linux-4.8.6-2 -f /usr/src/linux-4.8.6-2/Makefile prepare /usr/src/linux-4.8.6-2/Makefile:1052: "Cannot use CONFIG_STACK_VALIDATION, please install libelf-dev, libelf-devel or elfutils-libelf-devel"
sorry, but i don't understand. when i do the "make prepare" and "make modules_prepare" inside of /usr/src/linux-obj/x86_64/default it runs without any problems.
And of course it requires full kernel-source that is not needed normally and that I do not have.
ah, ok. i have full kernel source package installed. so, what you are saying is, that when having installed these packages: kernel-default-4.8.7-2.1.g91441e5.x86_64 kernel-default-devel-4.8.7-2.1.g91441e5.x86_64 kernel-devel-4.8.7-2.1.g91441e5.noarch kernel-macros-4.8.7-2.1.g91441e5.noarch it is simply not necessary to: * install also kernel-source-4.8.7-2.1.g91441e5.noarch * do a "make prepare" and "make modules_prepare" after kernel update to be able to compile kernel modules like nvidia, vmware, wl and displaylink? -- Best Regards | Freundliche Grüße | Cordialement | Cordiali Saluti | *DI Rainer Klier* Research & Development, Technical Sales Consultant Namirial GmbH -- To unsubscribe, e-mail: opensuse-factory+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse-factory+owner@opensuse.org
Am 2016-11-15 um 19:32 schrieb Rainer Klier:
Am 2016-11-15 um 19:05 schrieb Andrei Borzenkov:
15.11.2016 18:39, Rainer Klier пишет:
And of course it requires full kernel-source that is not needed normally and that I do not have.
ah, ok. i have full kernel source package installed.
so, what you are saying is, that when having installed these packages: kernel-default-4.8.7-2.1.g91441e5.x86_64 kernel-default-devel-4.8.7-2.1.g91441e5.x86_64 kernel-devel-4.8.7-2.1.g91441e5.noarch kernel-macros-4.8.7-2.1.g91441e5.noarch
it is simply not necessary to: * install also kernel-source-4.8.7-2.1.g91441e5.noarch * do a "make prepare" and "make modules_prepare" after kernel update
to be able to compile kernel modules like nvidia, vmware, wl and displaylink?
you are right! today i updated kernel to 4.8.8 and deleted kernel-source package. after update, i DID NOT my usual "make prepare" stuff, but simply compiled all the needed kernel modules (nvidia, wl, displaylink, vmawre), and it worked! this is great. it saves me drive-space (kernel-source package is huge!) and time.. -- Best Regards | Freundliche Grüße | Cordialement | Cordiali Saluti | *DI Rainer Klier* Research & Development, Technical Sales Consultant Namirial GmbH -- To unsubscribe, e-mail: opensuse-factory+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse-factory+owner@opensuse.org
On 16/11/16 04:47 AM, Rainer Klier wrote:
Am 2016-11-15 um 19:32 schrieb Rainer Klier:
Am 2016-11-15 um 19:05 schrieb Andrei Borzenkov:
15.11.2016 18:39, Rainer Klier пишет:
And of course it requires full kernel-source that is not needed normally and that I do not have.
ah, ok. i have full kernel source package installed.
so, what you are saying is, that when having installed these packages: kernel-default-4.8.7-2.1.g91441e5.x86_64 kernel-default-devel-4.8.7-2.1.g91441e5.x86_64 kernel-devel-4.8.7-2.1.g91441e5.noarch kernel-macros-4.8.7-2.1.g91441e5.noarch
it is simply not necessary to: * install also kernel-source-4.8.7-2.1.g91441e5.noarch * do a "make prepare" and "make modules_prepare" after kernel update
to be able to compile kernel modules like nvidia, vmware, wl and displaylink?
you are right!
today i updated kernel to 4.8.8 and deleted kernel-source package. after update, i DID NOT my usual "make prepare" stuff, but simply compiled all the needed kernel modules (nvidia, wl, displaylink, vmawre), and it worked!
this is great. it saves me drive-space (kernel-source package is huge!) and time..
N.B Do not run any of the make commands in /usr/src/linux. It has nothing to do with running make in vmware. Only follow the commands regarding vmware. However, a couple of commands are needed to clean up two directories and two files that were extracted to /usr/lib/vmware/modules/source/. vmmon-only, vmnet-only, vmmon.o and vmnet.o Roman -- To unsubscribe, e-mail: opensuse-factory+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse-factory+owner@opensuse.org
participants (10)
-
Andrei Borzenkov -
Carlos E. R. -
James PEARSON -
Jan Engelhardt -
Kyek, Andreas, Vodafone DE -
Markus Koßmann -
Michal Kubecek -
Patrick Shanahan -
Rainer Klier -
Roman Bysh