SlackwareThis Forum is for the discussion of Slackware Linux.
Notices
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.
Get a virtual cloud desktop with the Linux distro that you want in less than five minutes with Shells! With over 10 pre-installed distros to choose from, the worry-free installation life is here! Whether you are a digital nomad or just looking for flexibility, Shells can put your Linux machine on the device that you want to use.
Exclusive for LQ members, get up to 45% off per month. Click here for more info.
ok so i tryed to recompile my kernel, simple remove pcmcia and isa support. i use /dev/sda1 as my root partition. my motherboard doesnt support sata, so i have a pata boot drive with lilo to tell my machine to boot the sata drive.
/usr/src/linux kernel recompile frys my machine upon first try. i am informed of incomplete kernel headers. next, i will try /usr/src/$ rm linux
/usr/src/$ ln -s kernel2.6.26.5 linux
will this also fry my machine? any notes on how to retard proof kernel compilation for my specific machine? like to retard proof remove trash drivers that i do not need? like to foolproof insuring installing the drivers i am using for my hardware? all i know is that my system freaks out over 4 apps running at the same time, and would like to be able to watch some divx video, and not feel so over loaded slow. THX =D
Last edited by XavierP; 09-10-2008 at 03:00 PM.
Reason: also fixed words
First, did you copy the old config into /usr/src/linux-2.6.26.5 ?
if not, do:
cd /usr/src/linux-2.6.26.5
make mrproper
zcat /proc/config.gz > .config
make oldconfig (usually default answer is ok for the config questions)
Then you can add or remove features in kernel
make xconfig
(do it slowly, make sure you read the help, and ask question here if you don't know about kernel option in config)
Last edited by keefaz; 09-10-2008 at 07:30 AM.
Reason: added make mrproper, just in case
Hope I'm not stepping on any toes, but I recommend you build under
the normal user's home directory. Your concern is only one good
reason, but good enough in itself. I've built custom kernels for
Slackware for over 5 years, and have never touched /usr/src.
I use /home/build/kernels instead of /usr/src for my part, but the OP used /usr/src and I think Alien Bob's kernel compilation tutorial uses this directory too, so...
Distribution: slackware64 13.37 and -current, Dragonfly BSD
Posts: 1,810
Rep:
I too hope I'm not treading on any toes here. This is a quote from Linus Torvalds.The full mail is available here
This is the relevant bit ..
Quote:
I would suggest that people who compile new kernels should:
* NOT do so in /usr/src. Leave whatever kernel (probably only the header files) that the distribution came with there, but don't touch it.
* compile the kernel in their own home directory, as their very own selves. No need to be root to compile the kernel. You need to be root to install the kernel, but that's different.
Admittedly sometimes I have gone against his advice when it's given me some odd problems but that's only been through my own stupidity and wanting a quick fix to my predicament.
It seems the man would like it done this way, (in ~/), though..
edit: Thankfully I haven't had a need to compile my kernel for some time as the stock generic works great for me.
thanks for all of the responses. i learned my lesson about using /usr/src the first time =) sucks i lost 1000 gigs of data in the process. now the deal with the boot drive, should i move my boot images to the ide drive that boots the computer, or even install the kernels to that drive??? should i install the kernel to both drives?
You want a lilo chainloader I think, the lilo from pata boot drive loads the lilo from the sata drive which loads the kernel also on the sata drive, dunno if I am clear
I am not a lilo user, hopefully someone more qualified would chime in
[edit]
It is somewhat not clear to me what you call the 'pata boot', if you mean your /boot partition of Slackware system is on the pata drive, you don't need a chainloader
i mean i have a full blown 10gb slackware 12.1 drive on the ide channel. i just setup the lilo on that drive to point to /dev/sda1 as its root. when the lilo comes up its the lilo from the pata drive, and never shows the lilo setup on the sata drive. im not 100% positive but i believe it is using the huge-smp kernel from the ide drive, NOT the sata.
cd /usr/src/linux-2.6.26.5
make mrproper
zcat /proc/config.gz > .config
make silentoldconfig
silentoldconfig was just as loud as oldconfig.
what i seek is a script that automatically generates a "all.config" file to automate cutting out the kernel options that i do not need, and to easily get my kernel very fast with out having to reconfigure the kernel 50 thousand times.
i was under the impression that the zcat line would do that, and it might. oh well, im installing this kernel i just compiled.
i am getting ideas, such as booting into the ide drive, setting it to mount the sata drive, and soft linking to the new kernel. this huge smp kernel is quite a drag on my 850mhz system, the 500mhz system was unacceptable. the 500 could not write a cd it was so freaked out from the overloaded kernel.
it would be nice for the distros to just include such things and run them upon initial install so that the kernel could be less crazy for newbies first installs. huge smp is no problemo on a dual core, not so on the 500.
im starting to get the idea to make an all module kernel to run these scripts since it does nothing to compiled in modules.
i would take a 500k script over a 4mb bloated turtle kernel any day.
LinuxQuestions.org is looking for people interested in writing
Editorials, Articles, Reviews, and more. If you'd like to contribute
content, let us know.