Solved

recompile for 386 --- not!

Posted on 2001-06-11
4
263 Views
Last Modified: 2013-12-15
After installing slackware 7.1 on a hard drive in a P2 and moving the drive to a 386DX with a 387, the kernel (2.2) panics with 'recompile for a 386!'.  So I put the drive back in the P2, select all the 386 related options and compile with 'make bzlilo'.  

The kernel gives the same complaint back in the 386 every time.  Is there some option that I might be missing that isn't in the 'processor options' section of the kernel's make config?  Or does something else special need to be done when compiling on one platform and moving to another?  I've done this successfully with a MUCH older slackware distro without any special changes between the P2 and the 386, but something is stopping this particular release.

Thanks for any help,
magarity
0
Comment
Question by:magarity
[X]
Welcome to Experts Exchange

Add your voice to the tech community where 5M+ people just like you are talking about what matters.

  • Help others & share knowledge
  • Earn cash & points
  • Learn & ask questions
  • 2
  • 2
4 Comments
 
LVL 40

Accepted Solution

by:
jlevie earned 100 total points
ID: 6179846
Did you do a "make mrproper" before configuring the kernel for a 386 CPU type? If not, the build process is probably picking up other CPU type information. Be aware that "make mrproper" will delete the existing .config file. If you want to save that kernel config copy the .config file to some other name.
0
 
LVL 13

Author Comment

by:magarity
ID: 6181575
No, I haven't tried mrproper.  I'll give it a try tonight.  Should I do mrproper and then make config?
0
 
LVL 13

Author Comment

by:magarity
ID: 6188673
Ah, that actually worked...  From a blank install, where the heck was it getting the wrong CPU type info???  Anyway, thanks for the tip; my little firewall box is now on a 2.4.4 kernel, whee!
0
 
LVL 40

Expert Comment

by:jlevie
ID: 6189378
It got the incorrect CPU type because the kernel source tree had been used to compile a kernel before it was packaged for distribution. Whether the kernel should be distributed that way or not is something of a moot question. The kernel building docs that I've seen all say to do a "make mrproper" the first time you build a kernel and each time that you change the CPU type or mode.
0

Featured Post

Independent Software Vendors: We Want Your Opinion

We value your feedback.

Take our survey and automatically be enter to win anyone of the following:
Yeti Cooler, Amazon eGift Card, and Movie eGift Card!

Question has a verified solution.

If you are experiencing a similar issue, please ask a related question

Suggested Solutions

Title # Comments Views Activity
RHEL7 - Error installing docker compose 2 218
lunix and unix command 21 155
RHEL installation problems on HP Proliant DL 360 G6 server 20 148
Apache module 5 87
Using 'screen' for session sharing, The Simple Edition Step 1: user starts session with command: screen Step 2: other user (logged in with same user account) connects with command: screen -x Done. Both users are connected to the same CLI sessio…
In the first part of this tutorial we will cover the prerequisites for installing SQL Server vNext on Linux.
Learn how to find files with the shell using the find and locate commands. Use locate to find a needle in a haystack.: With locate, check if the file still exists.: Use find to get the actual location of the file.:
How to Install VMware Tools in Red Hat Enterprise Linux 6.4 (RHEL 6.4) Step-by-Step Tutorial
Suggested Courses

751 members asked questions and received personalized solutions in the past 7 days.

Join the community of 500,000 technology professionals and ask your questions.

Join & Ask a Question