SlackwareThis Forum is for the discussion of Slackware Linux.
Welcome to LinuxQuestions.org, a friendly and active Linux Community.
You are currently viewing LQ as a guest. By joining our community you will have the ability to post topics, receive our newsletter, use the advanced search, subscribe to threads and access many other special features. Registration is quick, simple and absolutely free. Join our community today!
Note that registered members see fewer ads, and ContentLink is completely disabled once you log in.
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)?
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 22.214.171.124 with the new gcc and now everything works.
I have always been reluctant to apply this patch, but I've given it a try now.
With a 126.96.36.199 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 188.8.131.52 kernel, without crashes though. I'll stick to this kernel at this point.
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...
When I compiled by 184.108.40.206 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 220.127.116.11 (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 ;-)