RE: Recognizing Kernel Update to 2.4.12 -- Inching Closer
Did you 'make config' first? (or make menuconfig, etc?) Otherwise, you are
almost 100% sure to end up with an unusable kernel...
Also, with these options, in `make config`, you can press the `?` key (no
quotes) and it'll tell you what you need to do.
I *highly* suggest your installing at least the libncurses5-dev package and
running `make menuconfig` from your top-level kernel directory,however. it's
much more user-friendly, and you can go back and make changes.
I would also *highly* suggest following along in the kernel-howto as well,
while you're compiling your kernel for the first time.
And you may even find that you dont' need to recompile your kernel. Unless
you need to add device support that isn't in the stock progeny/debian
system, I'm not quite clear exactly why you need to recompile the kernel--
you can run a fine debian system on a 2.2 kernel. So there's no need to
worry that you're not 'fully upgraded' from progeny. Unless you have
specific hardware needs, or want something that's slightly smaller, or
whatever, I'd stick with the kernel you have, at least until you're more
familiar with linux systems in general.
glen
-----Original Message-----
From: eDoc [mailto:e.net@verizon.net]
Sent: Monday, October 29, 2001 12:00 PM
To: Glen S Mehn; debian-user@lists.debian.org
Subject: Re: Recognizing Kernel Update to 2.4.12 -- Inching Closer
> the kernel source directory should contain a listing of files that looks
> something like this: (it'll change slightly, based on where you got your
> kernel source from):
>
> COPYING MAINTAINERS README.Debian arch include kernel net
> CREDITS Makefile REPORTING-BUGS drivers init lib
> scripts
> Documentation README Rules.make fs ipc mm
>
> irf you got the source from kernel.org, then it probably untars into a
> 'linux' directory. You can skip the mv command, and go straight on to the
> make <something>config command.
>
> good luck. glne
OK. Got there and ran the "make-kpkg" command.
A couple of complaints flashed by along with tons of other text, then after
defaulting to "Y" CONFIG_MODULES and CONFIG_MODVERSIONS:
"Kernel module loader (CONFIG_KMOD) [N/y/?] (NEW)"
If I choose "Y" does this require me to load specific modules for
everything or does it merely make such more automated? I did a
search on the Internet but what I need to know is unclear ... sure wish
Linux would document such options alongside the request for a choice!
The default is "N".
Thanks! Doc
Reply to: