Kernel Compile

[Jeepsta]

After compiling my first kernel (2.4.0-Test 11) last night I realized that I made a few wrong choices during the config stage. Would I be right to say that all I need to do is just run the config program and then recompile the kernel?

Zach

------------------
Its a jeep thing... You wouldn't understand.

[Mikenell]

Yeah thats all you do just go back the the make config, make menuconfig, make xconfig or whatever it was you used stage. Reselect what you want, then make dep, makes clean, make modules, and then make modules install. Then recopy the System.map and bzImage files.
Mikenell

[rod]

yes

[klamath]

What steps have you done so far?

All you'll probably need to do is run 'make clean' and then restart the config (i.e. 'make menuconfig', 'make xconfig', whatever). It will use your previous choices as defaults (BTW, your config choices are stored in a file called '.config' in the root directory of the Linux kernel source tree).

------------------
- Klamath
Get my GnuPG Key Here (http://klamath.dyndns.org/mykey.asc)
Looking for an open source project to contribute to? Check out the Better Bulletin Board (http://bbb.sourceforge.net)

[Jeepsta]

HOLY SH!T....that only took 7 minutes. I love this place.

Do I run make clean before or after make config? Does it make a difference? What order do I need to go in?

Mikenell--Wouldnt I throw in a make bzImage in there somewhere?

Zach

------------------
Its a jeep thing... You wouldn't understand.

[Mikenell]

I do it after. Thats what the NHF says and I follow that. But I do menu config, then make dep, then make clean, then make bzImage, make modules and finally make modules_install then copy the necessary files. (Also, I doubt this is required, but I tend to delete the folder containing the modules from a previous compile of that verion or rename is to <version>.old as it says in the NHF.
Mikenell

[witman]

Originally posted by Mikenell:
I do it after. Thats what the NHF says and I follow that. But I do menu config, then make dep, then make clean, then make bzImage, make modules and finally make modules_install then copy the necessary files. (Also, I doubt this is required, but I tend to delete the folder containing the modules from a previous compile of that verion or rename is to <version>.old as it says in the NHF.
Mikenell


Do you need to do a make modules and make modules_install if you don't use modules? I like to compile the support for my hardware right into the kernel.

I always do the two, but always wonder if it's necessary


------------------
Use the source!
The WITMAN Cometh!

[Jeepsta]

How exactly do you compile support directly into the kernel? Sounds like that might be something that I would want to do.

Zach

------------------
Its a jeep thing... You wouldn't understand.

[witman]

Originally posted by Jeepsta:
How exactly do you compile support directly into the kernel? Sounds like that might be something that I would want to do.

Zach




When you're doing the menuconfig, it usually gives you the option of Y, N and M the Y(Yes) will compile directly into the kernel while M(Module) will give you a modular approach. I choose Y. I don't need a modular kernel setup.

If you've ever noticed, most 'out of the box' kernels support everything and are like 1-2 MB. This includes modular support for everything (it would be huge if it was right in the kernel). My streamed down kernel with the network and sound support is about 500-600 kB. I prefer this approach.



------------------
Use the source!
The WITMAN Cometh!

[Jeepsta]

I understand ya now. One quick question. I compiled my sound support (SBLive) right into the kernel but when i boot up it tries to load the sound module. Sound still works and everything but why does it try to load the module? Is this normal?

Also, I dont have any SCSI drives but from what I know my CD-Writer has to trick the kernel into thinking that it is. This would involve me loading SCSI support right??

------------------
Its a jeep thing... You wouldn't understand.

[witman]

Originally posted by Jeepsta:
I understand ya now. One quick question. I compiled my sound support (SBLive) right into the kernel but when i boot up it tries to load the sound module. Sound still works and everything but why does it try to load the module? Is this normal?

Also, I dont have any SCSI drives but from what I know my CD-Writer has to trick the kernel into thinking that it is. This would involve me loading SCSI support right??



You need to check the System.map. It should reflect your current setup. My kernel complains about not finding mosules for the Sound Blaster and it still works.

I know nothing about the way CD-Writers work.

------------------
Use the source!
The WITMAN Cometh!

[Strike]

Originally posted by Jeepsta:
Also, I dont have any SCSI drives but from what I know my CD-Writer has to trick the kernel into thinking that it is. This would involve me loading SCSI support right??

Yeah, you can do it as a module, though.

Here (http://www.maximumlinux.com/howtos/howto/2000_11_02/learn_01.html) is a good article (from Maximum Linux mag) on how to do CD-RW/CD-R stuff.

[Jeepsta]

My problem is that I dont have a clue what I need to load. I read the help files about all the options but it seems as though they are written in another language. Most stuff I understand but some is just way to advanced. I understand computers but not in this kind of detail yet.

Strike: My current setup has the CD-Writer as SCSI although it is IDE. To me this means that I need SCSI support in the kernel (or as a module). I just dont know what options do what and what needs to be enabled as well. I guess its just trial and error.

------------------
Its a jeep thing... You wouldn't understand.

[Strike]

The default choices are generally pretty safe ones. Also, a lot of the help files have things at the end saying "If unsure, say Y" or "Say N unless you know what you are doing" (or something similar). Follow those and you will be okay. As far as the CD-R(W) stuff, the actual kernel config step is in that article I linked.

[Jeepsta]

Whoops....I actually forgot to click it and then forgot about it. I will check it out now. Thanx for the help.

Zach

------------------
Its a jeep thing... You wouldn't understand.