Are you a spammer

Please note, that the first 3 posts you make, will need to be approved by a forum Administrator or Moderator before they are publicly viewable.
Each application to join this forum is checked at the Stop Forum Spam website. If the email or IP address appears there when checked, you will not be allowed to join this forum.
If you get past this check and post spam on this forum, your posts will be immediately deleted and your account inactivated.You will then be banned and your IP will be submitted to your ISP, notifying them of your spamming. So your spam links will only be seen for an hour or two at most. In other words, don't waste your time and ours.

This forum is for the use and enjoyment of the members and visitors looking to learn about and share information regarding the topics listed. It is not a free-for-all advertising venue. Your time would be better spent pursuing legitimate avenues of promoting your websites.

VMware no longer can start after upgrade kernel to 2.6.35 RC

Help & support for Ultimate Edition 2.7
Post a reply


VMware no longer can start after upgrade kernel to 2.6.35 RC

Postby msh3_hate_me » Tue Jun 22, 2010 10:56 pm

I am not sure if it's proper to post the problem here. If not, please advise me where I should post.


I was able to test VMware 7.1 on UE2.7. After installed 2.6.35 kernel, I can't start the program anymore. This is the log:

Jun 22 21:46:03.781: app-140198196205312| Log for VMware Workstation pid=19154 version=7.1.0 build=build-261024 option=Release
Jun 22 21:46:03.781: app-140198196205312| The process is 64-bit.
Jun 22 21:46:03.781: app-140198196205312| Host codepage=UTF-8 encoding=UTF-8
Jun 22 21:46:03.781: app-140198196205312| Logging to /tmp/vmware-root/setup-19154.log
Jun 22 21:46:03.903: app-140198196205312| modconf query interface initialized
Jun 22 21:46:03.903: app-140198196205312| modconf library initialized
Jun 22 21:46:03.916: app-140198196205312| Your GCC version: 4.4
Jun 22 21:46:03.916: app-140198196205312| Searching for GCC 4.2.
Jun 22 21:46:03.916: app-140198196205312| Kernel is new enough; using PROBABLY compatible GCC 4.4 instead of desired 4.2
Jun 22 21:46:03.918: app-140198196205312| Your GCC version: 4.4
Jun 22 21:46:03.918: app-140198196205312| Searching for GCC 4.2.
Jun 22 21:46:03.918: app-140198196205312| Kernel is new enough; using PROBABLY compatible GCC 4.4 instead of desired 4.2
Jun 22 21:46:03.922: app-140198196205312| Your GCC version: 4.4
Jun 22 21:46:03.922: app-140198196205312| Searching for GCC 4.2.
Jun 22 21:46:03.922: app-140198196205312| Kernel is new enough; using PROBABLY compatible GCC 4.4 instead of desired 4.2
Jun 22 21:46:03.928: app-140198196205312| Your GCC version: 4.4
Jun 22 21:46:03.928: app-140198196205312| Searching for GCC 4.2.
Jun 22 21:46:03.928: app-140198196205312| Kernel is new enough; using PROBABLY compatible GCC 4.4 instead of desired 4.2
Jun 22 21:46:03.931: app-140198196205312| Your GCC version: 4.4
Jun 22 21:46:03.931: app-140198196205312| Searching for GCC 4.2.
Jun 22 21:46:03.931: app-140198196205312| Kernel is new enough; using PROBABLY compatible GCC 4.4 instead of desired 4.2
Jun 22 21:46:03.942: app-140198196205312| Trying to find a suitable PBM set for kernel 2.6.35-020635rc3-generic.
Jun 22 21:46:03.943: app-140198196205312| Trying to find a suitable PBM set for kernel 2.6.35-020635rc3-generic.
Jun 22 21:46:03.944: app-140198196205312| Trying to find a suitable PBM set for kernel 2.6.35-020635rc3-generic.
Jun 22 21:46:03.945: app-140198196205312| Trying to find a suitable PBM set for kernel 2.6.35-020635rc3-generic.
Jun 22 21:46:03.946: app-140198196205312| Trying to find a suitable PBM set for kernel 2.6.35-020635rc3-generic.
Jun 22 21:46:03.953: app-140198196205312| Trying to find a suitable PBM set for kernel 2.6.35-020635rc3-generic.
Jun 22 21:46:03.954: app-140198196205312| Trying to find a suitable PBM set for kernel 2.6.35-020635rc3-generic.
Jun 22 21:46:03.955: app-140198196205312| Trying to find a suitable PBM set for kernel 2.6.35-020635rc3-generic.
Jun 22 21:46:03.956: app-140198196205312| Trying to find a suitable PBM set for kernel 2.6.35-020635rc3-generic.
Jun 22 21:46:03.957: app-140198196205312| Trying to find a suitable PBM set for kernel 2.6.35-020635rc3-generic.
Jun 22 21:46:03.958: app-140198196205312| Your GCC version: 4.4
Jun 22 21:46:03.958: app-140198196205312| Searching for GCC 4.2.
Jun 22 21:46:03.958: app-140198196205312| Kernel is new enough; using PROBABLY compatible GCC 4.4 instead of desired 4.2
Jun 22 21:46:03.962: app-140198196205312| Your GCC version: 4.4
Jun 22 21:46:03.962: app-140198196205312| Searching for GCC 4.2.
Jun 22 21:46:03.962: app-140198196205312| Kernel is new enough; using PROBABLY compatible GCC 4.4 instead of desired 4.2
Jun 22 21:46:03.975: app-140198196205312| Trying to find a suitable PBM set for kernel 2.6.35-020635rc3-generic.
Jun 22 21:46:03.976: app-140198196205312| Trying to find a suitable PBM set for kernel 2.6.35-020635rc3-generic.
Jun 22 21:46:03.977: app-140198196205312| Trying to find a suitable PBM set for kernel 2.6.35-020635rc3-generic.
Jun 22 21:46:03.978: app-140198196205312| Trying to find a suitable PBM set for kernel 2.6.35-020635rc3-generic.
Jun 22 21:46:03.979: app-140198196205312| Trying to find a suitable PBM set for kernel 2.6.35-020635rc3-generic.
Jun 22 21:46:03.980: app-140198196205312| Your GCC version: 4.4
Jun 22 21:46:03.980: app-140198196205312| Searching for GCC 4.2.
Jun 22 21:46:03.981: app-140198196205312| Kernel is new enough; using PROBABLY compatible GCC 4.4 instead of desired 4.2
Jun 22 21:46:03.984: app-140198196205312| Your GCC version: 4.4
Jun 22 21:46:03.984: app-140198196205312| Searching for GCC 4.2.
Jun 22 21:46:03.984: app-140198196205312| Kernel is new enough; using PROBABLY compatible GCC 4.4 instead of desired 4.2
Jun 22 21:46:04.001: app-140198196205312| Trying to find a suitable PBM set for kernel 2.6.35-020635rc3-generic.
Jun 22 21:46:04.002: app-140198196205312| Trying to find a suitable PBM set for kernel 2.6.35-020635rc3-generic.
Jun 22 21:46:04.003: app-140198196205312| Trying to find a suitable PBM set for kernel 2.6.35-020635rc3-generic.
Jun 22 21:46:04.004: app-140198196205312| Trying to find a suitable PBM set for kernel 2.6.35-020635rc3-generic.
Jun 22 21:46:04.005: app-140198196205312| Trying to find a suitable PBM set for kernel 2.6.35-020635rc3-generic.
Jun 22 21:46:04.116: app-140198196205312| Trying to find a suitable PBM set for kernel 2.6.35-020635rc3-generic.
Jun 22 21:46:04.116: app-140198196205312| Building module vmmon.
Jun 22 21:46:04.116: app-140198196205312| Extracting the sources of the vmmon module.
Jun 22 21:46:04.121: app-140198196205312| Building module with command: /usr/bin/make -C /tmp/vmware-root/modules/vmmon-only auto-build SUPPORT_SMP=1 HEADER_DIR=/lib/modules/2.6.35-020635rc3-generic/build/include CC=/usr/bin/gcc GREP=/usr/bin/make IS_GCC_3=no VMCCVER=4.4.3
Jun 22 21:46:05.297: app-140198196205312| Failed to compile module vmmon!
msh3_hate_me
U.E. Newbie
U.E. Newbie
 
Posts: 4
Joined: Mon Jun 21, 2010 12:39 am
Operating System: Ultimate Edition 3.1 64 BIT
Top


Re: VMware no longer can start after upgrade kernel to 2.6.3

Postby 2hot6ft2 » Tue Jun 22, 2010 11:31 pm

I think Admin-Amir might be able to help. What I see is the kernel was compiled with a different version of GCC and the module failed to compile. Admin-Amir knows more about VM than I do so I'll leave it for him. Hang in there.
;)
Image
HP G60-125NR - AMD Turion X2 64 - nVidia GeForce 8200M G - 128 GB SSD Dual boot - Ultimate Edition, Win 10 Pro
HP G60-121WM - AMD Sempron SI-40 - nVidia GeForce 8200M G - 128 GB SSD - Dual boot - Ultimate Edition, Win 10 Pro
Custom build, Rosewill Challenger ATX Gaming Case, AMD Phenom II x4 955 C3 rev., MSI 870A-G54, 2x ATI HD4850 512MB /256bit GDDR3 & dual precision, GSkill 8GB 1600 RAM - Multi boot - Ultimate Edition, Win 10 Pro, Beta Testing
User avatar
2hot6ft2
Moderator
 
Posts: 533
Joined: Sun May 25, 2008 12:30 pm
Location: Alabama, USA
Operating System: Ultimate Edition 3.2 64 BIT
Top


Re: VMware no longer can start after upgrade kernel to 2.6.3

Postby Admin-Amir » Sun Jun 27, 2010 1:43 pm

Hello msh3_hate_me .

After you have Upgrade to 2.6.35 RC,The Vbox Version it not Ready for this Kernel,
It is Ready for -"Lucid Lynx" = you will need to go to 2.6.34 Kernel to get it to work.
You have to Understand that software build just for the Released packages.
When you are on the RC,you can Not have package ready for RC.
RC=Tests.
So the solution for you will be to Delete from synaptic the 2.6.35 RC installation,
And to use the Release Kernel of 2.6.34 with the VBox.
The Release is for 10.04, 2.6.35 RC is for 10.10.
Admin-Amir
 
Top
Post a reply

Return to Ultimate Edition 2.7

Who is online

Users browsing this forum: No registered users and 3 guests

Powered by phpBB® Forum Software © phpBB Group
{ ASACP_CREDITS }
cron