Re: Aargh! Can't build 2.4.22!
From: Matt Gibson (gothick_at_gothick.org.uk)
Date: 10/20/03
- Next message: Runar Furenes: "Kmail nad columns"
- Previous message: fishears: "Suse help in Suse 9"
- In reply to: Bill Sheppard: "Aargh! Can't build 2.4.22!"
- Next in thread: Gerhard W. Gruber: "Re: Aargh! Can't build 2.4.22!"
- Messages sorted by: [ date ] [ thread ] [ subject ] [ author ]
Date: Mon, 20 Oct 2003 17:38:40 +0100
Bill Sheppard wrote:
> OK, I'm lacking significant sleep due to this problem. I recently
> installed
> 9.0 Pro and it's running quite nicely. I'd like to install 2.4.22 in
> order to
> get software suspend. I've downloaded the full tree, applied the swsusp
> patches, done:
Well, I'm not familiar with 2.4.22 specifically, but...
> make mrproper
> make oldconfig (answering new questions)
I believe that "make oldconfig" requires the old .config file from the last
version of the kernel you built. Even if you had one, which I'm guessing
you didn't, "make mrproper" will have deleted it. Were you, perchance,
asked quite a lot of questions by "make oldconfig"?
Various flavours of the kernel have ways of getting the currently running
config. SuSE used to provide a "make cloneconfig" target that they built
into their own kernels. I can't remember where it grabbed the current
config info from, but if it's still there then you can find out by checking
the Makefile.
Here, with 2.6.0-test8, I have a compressed copy of the config file for the
running kernel available as /proc/config.gz. Boot with the old kernel and
see what you can find.
> make dep
> make bzImage
> make modules
> make modules_install
That's all fine. If you don't want to bother copying the kernel to /boot
yourself, then edit the bit of the Makefile that defines "INSTALL_PATH" and
change it to "export INSTALL_PATH=/boot". After that, "make install" will
do a make bzImage for you and then stick the kernel and System.map in the
right place.
> Can someone PLEASE suggest what I'm missing or doing wrong? Looking in
> /lib/modules/2.4.22 I note that most of the modules.xxx files are
> substantially smaller, and in particular modules.generic_string is only
> one line whereas with the 2.4.21-99 kernel it's 54K or so.
Do the make modules_install again. You should be able to see from the
output which modules are being installed where. If 2.4.22 uses the recent,
less verbose build output, try "make V=1 modules_install".
Well, that should be enough to get you started. Apologies if some of this
isn't relevant, but I jumped from an early 2.4 kernel right up to 2.6.0,
and a lot has changed.
M
--
"It's the small gaps between the rain that count,
and learning how to live amongst them."
-- Jeff Noon
- Next message: Runar Furenes: "Kmail nad columns"
- Previous message: fishears: "Suse help in Suse 9"
- In reply to: Bill Sheppard: "Aargh! Can't build 2.4.22!"
- Next in thread: Gerhard W. Gruber: "Re: Aargh! Can't build 2.4.22!"
- Messages sorted by: [ date ] [ thread ] [ subject ] [ author ]
Relevant Pages
|
