First of all, let's address #1.
There are several steps to compiling a kernel. I'm not a C++
programmer, so that leaves the requirement to being a programmer out in
the wind. First of all, you might find it easier to muck around the
menued version of the kernel config by using "make menuconfig". This will
give you a text/menu interface to use. Even us seasoned linux-ites use it
(at least I do), and prefer it over the scrolling config process.
Next, if you're changing kernel versions or adding/deleting modules
from the config, under "Loadable module support" make sure you enable
"Enable loadable module support". If you're reusing modules from a former
kernel version, turn on "Set version information on all symbols for
modules", and for good measure also turn on "Kernel module loader". The
"Set version..." is not a necessity.
Lastly, make sure you are following the kernel's installation and make
menus for handling your installations. If not, you're in for not only a
rough ride, but also a lot of work. The module install process does a lot
more than just move files into a directory.
For clearing up your symbol problems, follow the module info in the
previous paragraph. Then do a "make modules" and a "make modules_install"
which will install modules for you and setup the System.map file. When
compiling a newer kernel (2.2.x), it will tell you when you leave the menu
what to run. Depending on what it tells you, usually it will say "make
dep". The usual compile process is of 3 commands:
make clean
make dep
make bzImage
(older books say "zImage", but if the kernel is over a certain
size, it will not fit into lower RAM at initial boot, it's safe
to always say "bzImage")
And to install, just use:
make install
You will see after the install process completes something like:
Added linux *
Added dos
(this will display "Added" for partitions you have to choose from at boot)
This last step (part of the kernel "make install") runs lilo for you
automatically, and installs the kernel in the location referenced by your
/etc/lilo.conf, and renames the old kernel to save as a backup.
-------------------
For #2, we need to know what kernel version you just compiled and which
one you *were* on. We also need to know what networking options you
changed. Did you enable or disable any module or kernel support for
network cards? Initially, without more information, I suspect if you
compiled your network card as a module, the module is not loading based on
what's occurring in your #1 question below.
Hope this helps!
JR
On Mon, 22 May 2000, Dominik The Newbie wrote:
> Date: Mon, 22 May 2000 10:40:02 +1000
> From: Dominik The Newbie <[EMAIL PROTECTED]>
> To: Linux Newbie <[EMAIL PROTECTED]>
> Subject: Kernel Customization
>
> Hi there,
>
> I re-compiled the kernel, wen through the whole "make config", etc.
> Everything compiled successfully. Moved all the modules to the proper
> directory (well, ok, I was following a book :-) I then edited lilo.conf, add
> the new kernel, and ran /sbin/lilo.
>
> Restarted the machine, chose the new kernel during boot. No problem at all
> except for 2 things:
>
> 1) A whole bunch of dependency errors come up during startup (PCMCIA
> mostly - this is a server not a notebook).
> 2) I can no longer telnet into the machine. I can ping out from the machine
> console (physically on the machine), but it no longer replies to pings.
> Weird. Checked the default gateway, IP, etc, all looks ok.
>
> Any thoughts?
>
> Thanks everyone!
> Dominik.
>
>
> -
> To unsubscribe from this list: send the line "unsubscribe linux-newbie" in
> the body of a message to [EMAIL PROTECTED]
> Please read the FAQ at http://www.linux-learn.org/faqs
>
-
To unsubscribe from this list: send the line "unsubscribe linux-newbie" in
the body of a message to [EMAIL PROTECTED]
Please read the FAQ at http://www.linux-learn.org/faqs
