User talk:Feydaykyn

From ArchWiki
Jump to navigation Jump to search

VMware '-I' switch

What do you mean by adding the -I flag to ignore errors with the .bundle so that errors in building the modules are ignored? The module builds are _supposed_ to produce errors in case they don't build right. You can't just ignore these. --Det 12:01, 6 March 2012 (EST)

The bundle (both 8.0.0 and 8.0.2 versions) wouldn't install, it was failing when compiling the vmnet module. Using the -I switch, we forced the bundle to install, so that we could patch the sources and have all modules compiled successfully later with the vmware bin. In this particular case, ignoring the compiling errors is necessary, but I agree it shouldn't be default. --Feydaykyn 14:43, 6 March 2012 (EST)
It doesn't even compile the modules until _after_ the install. You can _then_ patch them and let them (the modules) install. --Det 01:25, 8 March 2012 (EST)
This issue happened to me, here are the details. A few days ago, with a 3.2.* kernel and modules patched, the alert to upgrade ws from 8.0.1 to 8.0.2 prompted and I accepted it. During the installation, upgrade script removed ws 8.0.1, and tried to re-build all modules. This build failed and the reason was:
2012-02-29T18:24:01.692+01:00| modconfig| I120: Building module with command: /usr/bin/make -j -C /tmp/vmware-root/modules/vmnet-only auto-build SUPPORT_SMP=1 HEADER_DIR=/lib/modules/3.2.6-2-ARCH/build/include CC=/usr/bin/gcc GREP=/usr/bin/make IS_GCC_3=no VMCCVER=4.6.2
2012-02-29T18:24:04.866+01:00| modconfig| I120: Failed to compile module vmnet!
Then, I extracted the bundle to try to install by hand ws. I passed 1 day patching the installer to make it use modules sources that were already on my computer instead of those it extracted from the bundle.

I knew there wasn't any error extracting ws binaries from the bundle so when Feydaykyn told me about -I option, I used it then I re-patched modules (vmware-installer replaced mine) and launched vmware-modconfig --console --install-all. That was the solution, better than mine and much better than what vmware said to me (downgrade my kernel to a version that works with their bundle (2.6 - 2.7) install ws and upgrade my kernel, patching modules...). --Vianney 12:21, 8 March 2012 (EST)
Well that's _never_ happened to me or anybody else I know (nor did Googling come up with anything). You sure the update didn't actually finish and then just try to update the modules? Did you even try opening VMware afterwards? --Det 05:47, 8 March 2012 (EST)
I know there is nothing on google, I tried a lot of keyword atempting to see if anybody before me had the same problem. I can now say that one other colleague had it (with approximately the same kernel).
About trying to run vmware: the update script deleted the 8.0.1 version and wasn't able to install the 8.0.2. So... I had no more ws. --Vianney 15:20, 8 March 2012 (EST)
This is still a bit hard to believe but I'll add this to the Troubleshooting section
E: Wait, so even when trying to manually install 8.0.2 you still got the module compilation error? _During_ the install? --Det 10:55, 8 March 2012 (EST)
That's right: modules' source code contained in the bundle doesn't support our kernel and must be patched in order to compile.
E: You have to remember that modules' sources are extracted from the bundle. -- Vianney 20:38, 8 March 2012 (EST)
It seems like you're missing the point. When VMware starts building the modules the installer has already finished. You can't make the _.bundle_ compile the modules. --Det 14:33, 8 March 2012 (EST)
That's what I thought, "but in practice, the theory is always different from the practice". On my computer (and I read vmware-installer's source code), the installer extracted modules' sources from the bundle (even if I already had these modules installed) and tried to build it.
E: (and then it failed and removed all it already copied on my disk) -- Vianney 01:44, 9 March 2012
I don't understand how could your installer possibly be different from mine. I don't even know what I'm supposed to put in the Wiki. "Some people have different VMware installers downloaded from the same source so some of you guys can get one that tries to install the modules even before finishing the actual installation".
By the way, the installer's _supposed_ to extract the module sources from the .bundle to make you compile the new ones (whether you already had the ones from the _previous_ version or not). --Det 04:41, 9 March 2012 (EST)
Maybe this only occurs when upgrading ? That may explain why the bundle tries to build the module instead of just extracting the sources ? -- Vianney 12:20, 9 March 2012
But still doesn't explain why it happened with just you and this "colleague" of yours because the update itself has never rebuilt the modules with me or anybody else I know.
It's like you guys got a different update - as if VMware uploaded the wrong one by mistake and swapped it back to the right one again. Lol. --Det 15:41, 9 March 2012 (EST)