Can't compile kernel modules for VMware Player on F16
Hi, I am trying to compile new kernel modules for VMware Player version 4.0.3.703057 on F16 with new kernel. I succeded to compile kernel modules on some previous kernels, 3.1.x or 3.2.x, but fail to compile them for kernel 3.3.x. I have google for this but have not found a solution and are wandering if someone on this list has had any luck compiling kernel modules for VMware Player 4.0.3.x for kernel 3.3.x? -- Regards Jon Ingason -- users mailing list users@lists.fedoraproject.org To unsubscribe or change subscription options: https://admin.fedoraproject.org/mailman/listinfo/users Guidelines: http://fedoraproject.org/wiki/Mailing_list_guidelines Have a question? Ask away: http://ask.fedoraproject.org
Re: Can't compile kernel modules for VMware Player on F16
Am 24.05.2012 18:12, schrieb Jon Ingason: Hi, I am trying to compile new kernel modules for VMware Player version 4.0.3.703057 on F16 with new kernel. I succeded to compile kernel modules on some previous kernels, 3.1.x or 3.2.x, but fail to compile them for kernel 3.3.x. I have google for this but have not found a solution and are wandering if someone on this list has had any luck compiling kernel modules for VMware Player 4.0.3.x for kernel 3.3.x? http://access.thelounge.net/harry/usr-lib-vmware-modules-source.tar.bz2 replace the - with / to find out the real path dunno now where i found the patch months ago (also needed for 3.2 and still working) patched sources from my running installation AFAIR even the patch itself contained VMware Player is included and also installed in the Workstation Software VMwareWorkstation 8.0.3 doe snot fix the compile issues so i had to backup and move back this working ones after update _ [harry@srv-rhsoft:~]$ uname -r 3.3.7-1.fc16.x86_64 #1 SMP Tue May 22 13:59:39 UTC 2012 [harry@srv-rhsoft:~]$ vmrun Total running VMs: 4 /mnt/data/fileserver/vmware/centos/centos.vmx /mnt/data/fileserver/vmware/Buildserver64/config.vmx /mnt/data/fileserver/vmware/testserver/config.vmx /mnt/data/fileserver/vmware/arrakis/arrakis.vmx signature.asc Description: OpenPGP digital signature -- users mailing list users@lists.fedoraproject.org To unsubscribe or change subscription options: https://admin.fedoraproject.org/mailman/listinfo/users Guidelines: http://fedoraproject.org/wiki/Mailing_list_guidelines Have a question? Ask away: http://ask.fedoraproject.org
Re: Can't compile kernel modules for VMware Player on F16
2012-05-24 19:01, Reindl Harald skrev: Am 24.05.2012 18:12, schrieb Jon Ingason: Hi, I am trying to compile new kernel modules for VMware Player version 4.0.3.703057 on F16 with new kernel. I succeded to compile kernel modules on some previous kernels, 3.1.x or 3.2.x, but fail to compile them for kernel 3.3.x. I have google for this but have not found a solution and are wandering if someone on this list has had any luck compiling kernel modules for VMware Player 4.0.3.x for kernel 3.3.x? http://access.thelounge.net/harry/usr-lib-vmware-modules-source.tar.bz2 replace the - with / to find out the real path dunno now where i found the patch months ago (also needed for 3.2 and still working) Thank it works now. -- Regards Jon Ingason -- users mailing list users@lists.fedoraproject.org To unsubscribe or change subscription options: https://admin.fedoraproject.org/mailman/listinfo/users Guidelines: http://fedoraproject.org/wiki/Mailing_list_guidelines Have a question? Ask away: http://ask.fedoraproject.org
Re: Compile kernel
On 08/19/2010 07:45 PM, jarmo wrote: Konstantin Svist kirjoitti torstai, 19. elokuuta 2010 22:58:24: And it's not really all that much hassle -- and you get a fully working RPM which you can manage with rpm/yum/etc. Ok, understand, but what is kernel-PAE- devel-2.6.33.6-147.2.4.fc13.i686 for ? Jarmo kernel should be obvious PAE stands for Physical Address Extension -- it's a trick to allow x86 architectures access 4GB. If you have x64 capable hardware, x86_64 version is recommended. devel means it's a development package - it has all necessary sources to build the package 2.6.33.6 is the mainline kernel version 147.2.4 is the fedora/redhat version of the package (built with all patches, etc.) fc13 means it's a package for Fedora 13. and, finally, i686 is the hardware architecture this package is meant for HTH -- users mailing list users@lists.fedoraproject.org To unsubscribe or change subscription options: https://admin.fedoraproject.org/mailman/listinfo/users Guidelines: http://fedoraproject.org/wiki/Mailing_list_guidelines
Re: Compile kernel
On 08/20/2010 05:57 PM, Konstantin Svist wrote: On 08/19/2010 07:45 PM, jarmo wrote: Konstantin Svist kirjoitti torstai, 19. elokuuta 2010 22:58:24: And it's not really all that much hassle -- and you get a fully working RPM which you can manage with rpm/yum/etc. Ok, understand, but what is kernel-PAE- devel-2.6.33.6-147.2.4.fc13.i686 for ? Jarmo kernel should be obvious PAE stands for Physical Address Extension -- it's a trick to allow x86 architectures access 4GB. If you have x64 capable hardware, x86_64 version is recommended. devel means it's a development package - it has all necessary sources to build the package No, it means it has headers, build scripts, symlinks and other bits needed to build _against_ that package. Most -devel packages are for packages that provide libraries and allow building of applications that link against those libraries. The kernel-devel package is slightly different - it has the bits needed to build kernel modules against that version of the kernel (so for e.g. you can compile 3rd-party kernel modules or different versions of the modules included in the kernel package). The packages that contain all the sources required to build a binary backage are SRPMs (source RPMs). Regards, Bryn. -- users mailing list users@lists.fedoraproject.org To unsubscribe or change subscription options: https://admin.fedoraproject.org/mailman/listinfo/users Guidelines: http://fedoraproject.org/wiki/Mailing_list_guidelines
Re: Compile kernel
Konstantin Svist fry@gmail.com wrote: Sent: Aug 20, 2010 9:57 AM To: users@lists.fedoraproject.org Subject: Re: Compile kernel On 08/19/2010 07:45 PM, jarmo wrote: Konstantin Svist kirjoitti torstai, 19. elokuuta 2010 22:58:24: And it's not really all that much hassle -- and you get a fully working RPM which you can manage with rpm/yum/etc. Ok, understand, but what is kernel-PAE- devel-2.6.33.6-147.2.4.fc13.i686 for ? Jarmo kernel should be obvious PAE stands for Physical Address Extension -- it's a trick to allow x86 architectures access 4GB. If you have x64 capable hardware, x86_64 version is recommended. devel means it's a development package - it has all necessary sources to build the package 2.6.33.6 is the mainline kernel version 147.2.4 is the fedora/redhat version of the package (built with all patches, etc.) fc13 means it's a package for Fedora 13. and, finally, i686 is the hardware architecture this package is meant for Does this apply to any Fedora/RH package? James McKenzie -- users mailing list users@lists.fedoraproject.org To unsubscribe or change subscription options: https://admin.fedoraproject.org/mailman/listinfo/users Guidelines: http://fedoraproject.org/wiki/Mailing_list_guidelines
Re: Compile kernel
On 08/20/2010 10:02 AM, Bryn M. Reeves wrote: On 08/20/2010 05:57 PM, Konstantin Svist wrote:version is recommended. devel means it's a development package - it has all necessary sources to build the package No, it means it has headers, build scripts, symlinks and other bits needed to build _against_ that package. Most -devel packages are for packages that provide libraries and allow building of applications that link against those libraries. The kernel-devel package is slightly different - it has the bits needed to build kernel modules against that version of the kernel (so for e.g. you can compile 3rd-party kernel modules or different versions of the modules included in the kernel package). The packages that contain all the sources required to build a binary backage are SRPMs (source RPMs). Oops, brain fart. You're right, of course :) -- users mailing list users@lists.fedoraproject.org To unsubscribe or change subscription options: https://admin.fedoraproject.org/mailman/listinfo/users Guidelines: http://fedoraproject.org/wiki/Mailing_list_guidelines
Re: Compile kernel
Konstantin Svist kirjoitti perjantai, 20. elokuuta 2010 19:57:53: and, finally, i686 is the hardware architecture this package is meant for HTH Oh, propably asked wrongly. I know all that, what you explained. I ment, what for is that -devel source, if I can't compile it directly? By make menuconfic etc. When I started with linux 1996, from since I have compiled kernels that way. This moment I don't need any rpm from this kernel, because I know, that there's coming at least that bug correction soon. I'd like to test, if there's noticeable difference between pentium pro and pentium 4 optimizion. So why is this -devel for, if it's patched already, but you can't compile it? Jarmo -- users mailing list users@lists.fedoraproject.org To unsubscribe or change subscription options: https://admin.fedoraproject.org/mailman/listinfo/users Guidelines: http://fedoraproject.org/wiki/Mailing_list_guidelines
Compile kernel
Hi, I try compile kernel 2.6.33.6-147.2.4.fc13.i686.PAE just for optimize prosessor. There is now prosessor type pentium pro in use, but I'd like compile pentium p4. But when try after make menuconfig do make I get: make scripts/kconfig/conf -s arch/x86/Kconfig CHK include/linux/version.h CHK include/generated/utsrelease.h scripts/kconfig/conf -s arch/x86/Kconfig scripts/kconfig/conf -s arch/x86/Kconfig make[1]: *** No rule to make target `missing-syscalls'. Stop. make: *** [prepare0] Error 2 Any ideas what I'm missing :D ? I can compile vanilla kernel without any errors. Jarmo -- users mailing list users@lists.fedoraproject.org To unsubscribe or change subscription options: https://admin.fedoraproject.org/mailman/listinfo/users Guidelines: http://fedoraproject.org/wiki/Mailing_list_guidelines
Re: Compile kernel
On 08/19/2010 09:47 AM, jarmo wrote: Hi, I try compile kernel 2.6.33.6-147.2.4.fc13.i686.PAE just for optimize prosessor. There is now prosessor type pentium pro in use, but I'd like compile pentium p4. But when try after make menuconfig do make I get: make scripts/kconfig/conf -s arch/x86/Kconfig CHK include/linux/version.h CHK include/generated/utsrelease.h scripts/kconfig/conf -s arch/x86/Kconfig scripts/kconfig/conf -s arch/x86/Kconfig make[1]: *** No rule to make target `missing-syscalls'. Stop. make: *** [prepare0] Error 2 Any ideas what I'm missing :D ? I can compile vanilla kernel without any errors. Jarmo Are you following this HOWTO? You should be... http://fedoraproject.org/wiki/Docs/CustomKernel -- users mailing list users@lists.fedoraproject.org To unsubscribe or change subscription options: https://admin.fedoraproject.org/mailman/listinfo/users Guidelines: http://fedoraproject.org/wiki/Mailing_list_guidelines
Re: Compile kernel
Konstantin Svist kirjoitti torstai, 19. elokuuta 2010 20:46:01: Are you following this HOWTO? You should be... http://fedoraproject.org/wiki/Docs/CustomKernel No, I tried as I used with vanillas, easy way :D make menuconfig make make modules_install make install All that howto-hassle, that man can change one thing in config ? Jarmo -- users mailing list users@lists.fedoraproject.org To unsubscribe or change subscription options: https://admin.fedoraproject.org/mailman/listinfo/users Guidelines: http://fedoraproject.org/wiki/Mailing_list_guidelines
Re: Compile kernel
On 08/19/2010 11:20 AM, jarmo wrote: All that howto-hassle, that man can change one thing in config ? No, all that hassle is for the extra patches that RedHat took time to apply to the kernel. Some are backported from a newer version, some are not in the mainline yet... Many fixes there, all designed to make your Fedora experience better. And it's not really all that much hassle -- and you get a fully working RPM which you can manage with rpm/yum/etc. -- users mailing list users@lists.fedoraproject.org To unsubscribe or change subscription options: https://admin.fedoraproject.org/mailman/listinfo/users Guidelines: http://fedoraproject.org/wiki/Mailing_list_guidelines
Re: Compile kernel
Konstantin Svist kirjoitti torstai, 19. elokuuta 2010 22:58:24: And it's not really all that much hassle -- and you get a fully working RPM which you can manage with rpm/yum/etc. Ok, understand, but what is kernel-PAE- devel-2.6.33.6-147.2.4.fc13.i686 for ? Jarmo -- users mailing list users@lists.fedoraproject.org To unsubscribe or change subscription options: https://admin.fedoraproject.org/mailman/listinfo/users Guidelines: http://fedoraproject.org/wiki/Mailing_list_guidelines
How to compile kernel module for a new kernel before reboot?
Hello All, I have a vt6656 WiFi adapter that needs a separate driver to work in Linux. The driver is neither in native Fedora repos, nor in rpmfusion (at least I don't know how to search for it, so I think it's not there). So whenever I do a 'yum update' and get a new kernel, I have to compile a new kernel module as well. Currently, I first reboot to a new kernel, then compile a module and then do another reboot just to check everything is loading properly on bootup. How do I compile my driver for a new kernel _before_ actually booting into that new kernel, so that I could be prepared with the new kernel module already on first reboot? -- Best regards, Andrew -- users mailing list users@lists.fedoraproject.org To unsubscribe or change subscription options: https://admin.fedoraproject.org/mailman/listinfo/users Guidelines: http://fedoraproject.org/wiki/Mailing_list_guidelines
Re: How to compile kernel module for a new kernel before reboot?
On Sat, 2010-04-03 at 23:04 +0400, Andrew Junev wrote: Hello All, I have a vt6656 WiFi adapter that needs a separate driver to work in Linux. The driver is neither in native Fedora repos, nor in rpmfusion (at least I don't know how to search for it, so I think it's not there). So whenever I do a 'yum update' and get a new kernel, I have to compile a new kernel module as well. Currently, I first reboot to a new kernel, then compile a module and then do another reboot just to check everything is loading properly on bootup. How do I compile my driver for a new kernel _before_ actually booting into that new kernel, so that I could be prepared with the new kernel module already on first reboot? unless something radically changed in the kernel, you could probably just copy the module from /lib/modules/kernel-x to /lib/modules/kernel-y or you could use Matt Domsch's dkms Craig -- This message has been scanned for viruses and dangerous content by MailScanner, and is believed to be clean. -- users mailing list users@lists.fedoraproject.org To unsubscribe or change subscription options: https://admin.fedoraproject.org/mailman/listinfo/users Guidelines: http://fedoraproject.org/wiki/Mailing_list_guidelines
Re: How to compile kernel module for a new kernel before reboot?
On 3 April 2010 20:04, Andrew Junev a...@a-j.ru wrote: I have a vt6656 WiFi adapter that needs a separate driver to work in Linux. The driver is neither in native Fedora repos, nor in rpmfusion (at least I don't know how to search for it, so I think it's not there). So whenever I do a 'yum update' and get a new kernel, I have to compile a new kernel module as well. Currently, I first reboot to a new kernel, then compile a module and then do another reboot just to check everything is loading properly on bootup. How do I compile my driver for a new kernel _before_ actually booting into that new kernel, so that I could be prepared with the new kernel module already on first reboot? My advice is to investigate whether you can package it to work with DKMS: http://linux.dell.com/dkms/ http://linux.dell.com/dkms/manpage.html You can write infrastructure yourself, you can probably use akmods, but I have done exactly what you require for other kernel modules using DKMS as the infrastructure. FWIW, DKMS doesn't normally pre-build the module, it builds it on first boot into the kernel - so it's not exactly what you want. -- Sam -- users mailing list users@lists.fedoraproject.org To unsubscribe or change subscription options: https://admin.fedoraproject.org/mailman/listinfo/users Guidelines: http://fedoraproject.org/wiki/Mailing_list_guidelines
Re: How to compile kernel module for a new kernel before reboot?
On Sat, Apr 3, 2010 at 3:04 PM, Andrew Junev a...@a-j.ru wrote: Hello All, I have a vt6656 WiFi adapter that needs a separate driver to work in Linux. The driver is neither in native Fedora repos, nor in rpmfusion (at least I don't know how to search for it, so I think it's not there). So whenever I do a 'yum update' and get a new kernel, I have to compile a new kernel module as well. Currently, I first reboot to a new kernel, then compile a module and then do another reboot just to check everything is loading properly on bootup. How do I compile my driver for a new kernel _before_ actually booting into that new kernel, so that I could be prepared with the new kernel module already on first reboot? Depending on your source tree there are a few different ways. Most kernel module sources will use 'uname -r' to find the path to the kernel source tree. You may need to set a variable explicitly. For example, I grabbed a vt6656 build from git and saw in the mk.sh script: KDIR=/lib/modules/`uname -r`/build You can try passing the kernel version you want to build instead of running uname. -- users mailing list users@lists.fedoraproject.org To unsubscribe or change subscription options: https://admin.fedoraproject.org/mailman/listinfo/users Guidelines: http://fedoraproject.org/wiki/Mailing_list_guidelines
Re: How to compile kernel module for a new kernel before reboot?
Hello Kwan, Saturday, April 3, 2010, 11:57:04 PM, you wrote: How do I compile my driver for a new kernel _before_ actually booting into that new kernel, so that I could be prepared with the new kernel module already on first reboot? Depending on your source tree there are a few different ways. Most kernel module sources will use 'uname -r' to find the path to the kernel source tree. You may need to set a variable explicitly. For example, I grabbed a vt6656 build from git and saw in the mk.sh script: KDIR=/lib/modules/`uname -r`/build You can try passing the kernel version you want to build instead of running uname. Ok, I see. So there's no common method to do this, right? It may differ from module to module... Initially I thought that's a really simple task... And now it doesn't seem to be like that, especially for those who use multiple custom kernel modules... Ok, thanks a lot! I'll try it first, while starting to read about DKMS... Anyway, I'm curious to do it the right way. -- Best regards, Andrew -- users mailing list users@lists.fedoraproject.org To unsubscribe or change subscription options: https://admin.fedoraproject.org/mailman/listinfo/users Guidelines: http://fedoraproject.org/wiki/Mailing_list_guidelines
Re: How to compile kernel module for a new kernel before reboot?
On Sat, Apr 03, 2010 at 08:21:34PM +0100, Sam Sharpe wrote: FWIW, DKMS doesn't normally pre-build the module, it builds it on first boot into the kernel - so it's not exactly what you want. There is now a kernel install-time hook, such that when a new kernel is installed, DKMS can build its modules for that kernel. You don't have to wait for a reboot for the dkms_autoinstaller service to do it then. Thanks for the plugs. -- Matt Domsch Technology Strategist Dell | Office of the CTO -- users mailing list users@lists.fedoraproject.org To unsubscribe or change subscription options: https://admin.fedoraproject.org/mailman/listinfo/users Guidelines: http://fedoraproject.org/wiki/Mailing_list_guidelines
