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.
If you have any problems with the registration process or your account login, please contact us. If you need to reset your password, click here.
Having a problem logging in? Please visit this page to clear all LQ-related cookies.
Introduction to Linux - A Hands on Guide
This guide was created as an overview of the Linux Operating System, geared toward new users as an exploration tour and getting started guide, with exercises at the end of each chapter.
For more advanced trainees it can be a desktop reference, and a collection of the base knowledge needed to proceed with system and network administration. This book contains many real life examples derived from the author's experience as a Linux system and network administrator, trainer and consultant. They hope these examples will help you to get a better understanding of the Linux system and that you feel encouraged to try out things on your own.
Click Here to receive this Complete Guide absolutely free.
I have just installed Slk 12.0 and was configuring the Kernel when i noticed that the processor type Pentium Pro was checked. No biggie i will just change it to Athlon/K8. recompile, reboot, then BAM. i get a whole bunch of Error messages saying that it should be a M686 not a K8 and that it was Unloading all the Modules, etc. So i go back and recompile through the menuconfig and switch it back to the Pentium Pro and now everything works fine. Any sugestions on why it is doing this?
AMD Semperon 3000+ 1.8ghz
other things non-related.
Yeah, it's not that straightforward. The name your CPU "has" might not be the actual name of the thing used. Before changing vital things like that in your kernel, be sure to carefully find out what your processor exactly is, unless there's a choice which matches your (thought) cpu 100%. Shortly, if there is no "Sempron" choice, you can't just pick up some other AMD "close to that", unless you're begging for trouble
The fact is there were 2 flavours of Sempron. One was a stripped down K8 (Athlon 64/X2, Opteron) CPU while the other was based on a K7 architecture (Athlon, Athlon 4, Athlon XP,...). I think you choose the K8 architecture type while your CPU is actually a K7 which then mess up the kernel loading.
You should try to compile your kernel and tell him you've got an Athlon XP.
ok ill give it a try. this is a socket 754 processor (acording to CPUZ) and that was the socket right after the Athlon XPs so i will give the K7 option a try and see how it goes. Thanks for the replies.
There are actually three versions of the Sempron:
1) Socket A K7 Sempron.
2) Socket 754 based on the K8 but with 64-bit extensions disabled Sempron. It has all the capabilities of a K8 except 64-bit so you treat it as a K7.
3) Socket 754 K8 64-bit Sempron.
The reason I know of #2 is because I have a laptop with one
Last edited by the3dfxdude; 07-19-2007 at 12:02 AM.
Well I didn't know there were any socket 939 Sempron. It's also strange, I thought there were a specific socket for the laptop CPU. To add to the confusion, I checked an online store and just discovered some Sempron are available on socket AM2...
Anyway, even if a K8 is a K7 which architectural ameliorations and an integrated memory controller, I think it is still important to try both options and be sure all the modules are compiled and installed in the same time as the kernel itself. Anyway, it's pretty strange; after all, they're all x86 CPU based on more or less the same architecture flavour, you might have misconfigured other options in the kernel which causes all theses problems and might have nothing to do with the target CPU chosen.
well i did try it with both versions. and upon boot up it would (depending on the option i chose) either say <module> Unloading /188.8.131.52-smp/unload-k7(k8) error, should be <module> unloading /184.108.40.206/ unload-686. or something along the lines of that.