Results 1 to 10 of 11
Anyone do this? I decided to try it awhile ago on my Athlon 2000+. The difference was amazing. It was so much faster than before, and even the boot time ...
Enjoy an ad free experience by logging in. Not a member yet? Register.
- 08-19-2003 #1
Recompiling your kernel for your processor?
I decided to try it awhile ago on my Athlon 2000+. The difference was amazing. It was so much faster than before, and even the boot time lessened. So now, everytime I install linux, the first thing I do is recompile the kernel for the specific computers processor. Anyone else do this?Live in the sunshine, swim the sea, drink the wild air...
- 08-19-2003 #2
- 08-19-2003 #3
It took me about 25-35 minutes, but I'm running a fast cpu. it should take that long, but building the modules and installing them can take a little bit.Live in the sunshine, swim the sea, drink the wild air...
- 08-19-2003 #4
25 minutes? Do you have a precompiled gcc or have you compiled it self?
- 08-19-2003 #5
- Join Date
- Jul 2003
- Dayton, OH
how could one go about doing this if they were interested in trying it out? cause with my processor being a "mere" 733mhz, anyway to seemingly make it run smoother and faster would be ... well ... excellent.Quickdraw returns ... more news at 11!
I like to try all flavors of the rainbow. Running SuSE 10.1 on my laptop, Windows XP on my desktop, and an Mac OS X on my Mac powerbook.
- 08-19-2003 #6
That is long it takes my xp2200+ about 2 minutes to compile a kernel but i strip mine right down so that would make it faster. Still seems long.
- 08-19-2003 #7
interesting. Here's the commands I did:
cd [location of kernel source] make menuconfig make dep make clean make bzImage make modules make modules_install
the make menuconfig takes you to a menu configuration of the kernel where you can select your CPU. I also turned of some other stuff. (like support for NON-IDE/NON-SCSI cdrom drives)
after that I rebooted and in lilo there was a new option called kernel-cutsom or something like that.Live in the sunshine, swim the sea, drink the wild air...
- 08-19-2003 #8
You really shouldnt use the "make clean" because it deletes the compiled source stuff, so when you are going to recompile your kernel with the same kernel source, it will be as if you where compiling it all over again, instead of just compiling the new stuff. If you skip "make clean" I'm shure a kernel compile takes < 5 minutes. No reason to waste resources
Probably bad explained, but I hope you guys got my point
- 08-19-2003 #9
Originally Posted by Kriss
- Join Date
- Apr 2003
- London, UK
- 08-19-2003 #10
Yeah...I agree with J. You never know what COULD go wrong when you don't use make clean. It's a minimal resource hit for a better chance at everything working correctly. BTW it takes me about 15m to compile a kernel on my Athlon XP2000+"Time is an illusion. Lunchtime, doubly so."
~Douglas Adams, The Hitchhiker's Guide to the Galaxy