LinuxQuestions.org
Visit the LQ Articles and Editorials section
Go Back   LinuxQuestions.org > Forums > Linux Forums > Linux - Distributions > Slackware
User Name
Password
Slackware This Forum is for the discussion of Slackware Linux.

Notices

Reply
 
Search this Thread
Old 09-24-2005, 08:22 AM   #1
uselpa
Senior Member
 
Registered: Oct 2004
Location: Luxemburg
Distribution: Slackware, OS X
Posts: 1,507

Rep: Reputation: 46
stock kernel 2.4.31 compiled with wrong gcc?


This is what I get when configuring VMWare for the stock kernel 2.4.31:
===========================================================
Your kernel was built with "gcc" version "3.3.5", while you are trying to use
"/usr/bin/gcc" version "3.3.6". This configuration is not recommended and VMware
Workstation may crash if you'll continue. Please try to use exactly same
compiler as one used for building your kernel.
===========================================================
Is this a problem or can I ignore this warning (in general, not just for VMWare)?
 
Old 09-24-2005, 01:36 PM   #2
jong357
Senior Member
 
Registered: May 2003
Location: Columbus, OH
Distribution: DIYSlackware
Posts: 1,914

Rep: Reputation: 52
Yea, I just built myself a slak-pak of vmware last night and noticed the same thing. The modules build and insert just fine using 3.3.6....

It's possible there is something in /usr/doc/vmware mentioning it.. Not sure tho..

Last edited by jong357; 09-24-2005 at 01:38 PM.
 
Old 09-24-2005, 03:16 PM   #3
uselpa
Senior Member
 
Registered: Oct 2004
Location: Luxemburg
Distribution: Slackware, OS X
Posts: 1,507

Original Poster
Rep: Reputation: 46
For me, VMWare did not work with the stock 2.4.31 kernel (but it did with the earlier 2.4.29 in Slack 10.1).
Neither did it work with the stock 2.6.13 kernel, it complained about some file missing in the kernel headers - probably a different problem.
I recompiled my kernel 2.6.11.12 with the new gcc and now everything works.
 
Old 09-24-2005, 06:27 PM   #4
jong357
Senior Member
 
Registered: May 2003
Location: Columbus, OH
Distribution: DIYSlackware
Posts: 1,914

Rep: Reputation: 52
I had problems too with 2.6.13

http://ftp.cvut.cz/vmware/vmware-any...pdate94.tar.gz

That fixed it. Who knows, it may solve your 2.4.31 problem as well.
 
Old 09-25-2005, 04:28 AM   #5
uselpa
Senior Member
 
Registered: Oct 2004
Location: Luxemburg
Distribution: Slackware, OS X
Posts: 1,507

Original Poster
Rep: Reputation: 46
I have always been reluctant to apply this patch, but I've given it a try now.
With a 2.6.13.2 kernel from kernel.org, using Pat's config file with very few changes, there's progress: the VMWare modules start correctly and VMWare appears to be working (just did a quick check). However, when shutting down the system, there's some kind of crash ("unable to handle paging request"). Not good, the machine hangs.
The good news is that after the patch VMWare is still working with my 2.6.11.12 kernel, without crashes though. I'll stick to this kernel at this point.
 
Old 09-25-2005, 07:41 PM   #6
jong357
Senior Member
 
Registered: May 2003
Location: Columbus, OH
Distribution: DIYSlackware
Posts: 1,914

Rep: Reputation: 52
I find this slightly odd but I'm having the same problem (2.6.13) only when I boot up. Right before it's supposed to throw you to the prompt I get the "unable to handle kernel paging request" and then the kernel goes into an Oops. I think you jinxed me...

I tracked it down to my initrd tho. Has nothing to do with vmware. I thought it might because it happens right where rc.local executes rc.vmware but it's not. On multiple reboots, the problem goes away when I comment my initrd line out in grub. As soon as I uncomment it, it will Oops on me again....

Don't know if that helps or if you even care, but there it is... This new development/stable kernel branch idea has really been starting to get on my nerves the past half year or so... Bad, bad idea.... Most software devs aren't able to keep up with the changes from what I've seen...
 
Old 09-26-2005, 01:35 AM   #7
uselpa
Senior Member
 
Registered: Oct 2004
Location: Luxemburg
Distribution: Slackware, OS X
Posts: 1,507

Original Poster
Rep: Reputation: 46
When I compiled by 2.6.13.2 I compiled the ReiserFS modules static so I don't even have an initrd there. So I don't get an Oops when booting up, but the same message appears when shutting down (without an Oops, though).

No worries with the 2.6.11.12 (also without initrd).

I agree with you regarding the development process and of course I care. A stable branch is necessary. But then, we should have followed Pat's advice and stick to kernel 2.4* for now ;-)
 
  


Reply


Thread Tools Search this Thread
Search this Thread:

Advanced Search

Posting Rules
You may not post new threads
You may not post replies
You may not post attachments
You may not edit your posts

BB code is On
Smilies are On
[IMG] code is Off
HTML code is Off


Similar Threads
Thread Thread Starter Forum Replies Last Post
Self compiled modules have wrong version id ewschone Linux - General 1 06-20-2004 01:13 PM
Upgrading stock 2.4.22 kernel to 2.5.x then to 2.6.6 with existing stock .config file Kyl3 Slackware 8 06-09-2004 05:34 PM
redhat fedora gcc version (compiled for 2.4.20) doesn't match kernel version 2.4.22 start1000 Linux - Software 0 03-16-2004 08:17 PM
Compiled new kernel ... but somethings wrong Elijah Linux - General 6 03-30-2003 10:06 PM
Java compiled with gcc-3.2 CragStar Linux - Software 5 01-15-2003 01:50 PM


All times are GMT -5. The time now is 01:36 AM.

Main Menu
My LQ
Write for LQ
LinuxQuestions.org is looking for people interested in writing Editorials, Articles, Reviews, and more. If you'd like to contribute content, let us know.
Main Menu
Syndicate
RSS1  Latest Threads
RSS1  LQ News
Twitter: @linuxquestions
identi.ca: @linuxquestions
Facebook: linuxquestions Google+: linuxquestions
Open Source Consulting | Domain Registration